Comparison
Vercel vs. Cloudflare — what fits your Next.js?
Vercel gives the tightest Next.js experience. Cloudflare wins when DNS, WAF, and edge are already home. Here is how we choose — without a price fight.
The decision
It is about fit to product and ops — not hype.
Vercel is built around Next.js: preview deploys, DX, and platform features that match the framework closely. It is often the fastest path to production with low friction.
Cloudflare is an edge and security ecosystem: DNS, WAF, Workers, Pages, R2. Next.js runs well there via OpenNext patterns — with more runtime constraints to test.
Many serious setups are hybrid. We choose by your existing stack and constraints — not by what trends on Twitter.
Decision points
What we look at in discovery.
The practical questions that usually settle the choice.
Do you already have DNS/WAF on Cloudflare?
That often pulls Cloudflare-first.
Is preview DX critical for the team?
That often pulls Vercel.
Node-heavy dependencies?
Needs testing on Workers — or a Node host.
Long background jobs?
Hybrid: edge in front, workers/containers behind — or AWS.
Compliance and region?
Database and origin can drive more than the CDN choice.
Who operates it in six months?
Choose what you can own — not the prettiest diagram.
Vercel vs. Cloudflare Pages/Workers
Vercel
Next.js-native PaaS with strong preview DX.
- Tightest Next.js integration
- Preview deploys with low friction
- Strong default for marketing + app frontends
- The platform owns much of the runtime
- Heavy background jobs often belong elsewhere
- Watch growing into complexity you do not need
Cloudflare
Edge, DNS, WAF, and Workers in one ecosystem.
- Strong when DNS/security are already there
- Workers/Pages for edge logic and sites
- WAF and bot control close to origin
- Next.js needs OpenNext/runtime testing
- Some Node packages are constrained
- Hybrid with container/AWS is normal
Vercel or Cloudflare?
More left → Vercel. More right → Cloudflare (or hybrid).
Vercel when…
You want least friction on Next.js preview
Cloudflare when…
You already run DNS/WAF on Cloudflare
Vercel when…
The team prioritises DX over edge control
Cloudflare when…
You want to unify edge, security, and storage
Vercel when…
The app fits Node-friendly assumptions
Cloudflare when…
You can test and accept Workers constraints
Vercel when…
You want to avoid building CDN/WAF yourself
Cloudflare when…
You already treat Cloudflare as the perimeter
Tradeoffs
What you accept on both sides.
Vercel: platform convenience
You get delivery speed. You accept the platform’s model and limits.
Cloudflare: edge control
You get DNS/WAF/edge together. You accept more runtime discipline for Next.js.
Neither replaces the database choice
Postgres with RLS is still Postgres — whatever the CDN.
AWS is a third path
When you need private networking, heavy jobs, or compliance AWS already covers.
FAQ
Vercel vs. Cloudflare
Can Next.js run fully on Cloudflare?
Much of it — via OpenNext/Workers. Dependencies must be tested. We do not promise ‘pure edge’ before review.
Should we move just to save money?
No. Move when fit and ops say so. Cost control starts with visibility, not platform shopping.
What about AWS?
When edge/PaaS is not enough. See our AWS landing and insight.
Can we use both?
Yes. E.g. Cloudflare for DNS/WAF and Vercel for the app — or the reverse. Avoid an unnecessary split that makes debugging harder.
Read next
Read next
Deeper cloud guides.
- Cloud4 min read
What is Vercel — and when is it the right choice?
Vercel is the hosting and deploy platform behind Next.js. It's not the same as the framework — but for many teams it's the fastest path from repo to preview URL and edge caching without building the platform yourself.
→What is Vercel — and when is it the right choice? - Cloud4 min read
Cloudflare for production apps — what it gives you, and what it doesn't
Cloudflare is more than a CDN. For many Next.js and SaaS products it's edge, DNS, WAF, storage, and compute in one vendor — but you need to know which pieces you actually need.
→Cloudflare for production apps — what it gives you, and what it doesn't - Cloud5 min read
When is AWS the right call — and when is it too much?
AWS can carry almost anything — but "almost anything" is not the same as "what you need right now". Here is how we choose between AWS, Vercel, and Cloudflare without cloud religion.
→When is AWS the right call — and when is it too much?
Choosing a host?
Let’s match Vercel, Cloudflare, or hybrid to your product.
We map stack, traffic, and constraints — and propose the simplest setup that holds.