Can Cloudflare Pages run a full Next.js 16 app?

Mostly, but with caveats. App Router works; ISR has limitations; some Node-only APIs require shims. If you are on the bleeding edge of Next, Vercel is friction-free; Cloudflare adds compatibility homework. Check the Next-on-Cloudflare compatibility matrix before committing.

When does Vercel get expensive?

Around 1TB+ monthly bandwidth or heavy serverless function execution. The pricing page makes it look fine until your viral launch — then it bites. Set up cost alerts on day one and check usage weekly for the first month.

No. Slower Next.js feature adoption than Vercel and less aggressive marketing than Cloudflare, but the platform is stable, the deploys are reliable, and the support is good. For a JAMstack site or a small SSR app, it is a perfectly fine choice.

What about self-hosting Next.js on a VPS?

Possible, sometimes correct, but underpriced. Saves real money at scale (DigitalOcean droplet at $50/mo vs Vercel at $500/mo for the same workload) but you own the ops — patches, monitoring, SSL renewal, the 2am page. Worth it when you have ops capacity; not worth it for most product teams.

Which one does Creative Brain use for client work?

Vercel for greenfield Next.js builds. Netlify when the client already has it set up. Cloudflare Workers for specific use cases (high-bandwidth public APIs, image transformation pipelines). Hosting is the kind of decision we make in 5 minutes and rarely revisit.

Comparison · Vercel vs Netlify / Cloudflare

Vercel vs Netlify vs Cloudflare: which should host your Next.js app?

TL;DR

Use Vercel if you are on Next.js, want zero-config deploys, and the bill matters less than the developer experience. Use Cloudflare Pages or Workers when egress cost or global edge latency is the binding constraint and you can live with rougher Next.js compatibility. Use Netlify when the team already knows Netlify, the workload is a static site or basic SSR, and the budget is tight. For a brand-new Next.js production app in 2026, Vercel is the safest default; for cost-sensitive scale, Cloudflare is the contender to watch.

How they compare, dimension by dimension

Vercel versus Netlify and Cloudflare Pages — eight to nine dimensions that actually change the decision.

Dimension	Vercel	Netlify / Cloudflare	Edge
Next.js feature support (App Router, ISR, RSC)	First-party, day-1	Netlify good; Cloudflare partial	←
Edge runtime global PoP count	~30+	Cloudflare 330+, Netlify ~30	?
Bandwidth / egress cost	$$$ — surprises at scale	Cloudflare unlimited; Netlify $$	→
Cold start latency (server functions)	Low	Cloudflare Workers near-zero; Netlify variable	→
DX (Git push → deploy)	Best-in-class	Both very good	←
Build minutes pricing	Generous free tier; pricey past	Netlify similar; Cloudflare generous	?
Preview deploys	Per-PR, automatic	Per-PR, automatic	=
Hireability of ops talent	Vercel skills transfer easily	Cloudflare specialty	←
Image optimization	Native, fast	Netlify good; Cloudflare via R2/Polish	←

When to pick which

Pick Vercel if

You are shipping Next.js and want every feature to work on day one.
The team is small and time-to-deploy matters more than monthly cost.
You need first-party support for App Router, RSC, and ISR with no caveats.
You will use Vercel Analytics, KV, or Postgres alongside hosting.

Pick Netlify / Cloudflare if

Egress cost is the binding constraint — Cloudflare bundles unlimited bandwidth.
You need true global edge performance (sub-50ms response from 6 continents) — Cloudflare has 330+ PoPs.
The app is mostly static + a few APIs — Cloudflare Workers cold start in milliseconds.
Your team already runs Netlify and the migration cost is not worth it for a small project.

Our take

We deploy on Netlify (this site runs there because that is what was already set up) and we deploy clients on Vercel when they are starting fresh on Next.js. Cloudflare is genuinely interesting and we will move workloads there when bandwidth bills justify the switching cost. The honest answer for most teams: do not over-think this. Vercel for Next.js, Cloudflare for cost-sensitive scale, Netlify if it is already there. The hosting choice rarely makes or breaks the project.

Book a 30-min call

Common questions

Can Cloudflare Pages run a full Next.js 16 app?: Mostly, but with caveats. App Router works; ISR has limitations; some Node-only APIs require shims. If you are on the bleeding edge of Next, Vercel is friction-free; Cloudflare adds compatibility homework. Check the Next-on-Cloudflare compatibility matrix before committing.
When does Vercel get expensive?: Around 1TB+ monthly bandwidth or heavy serverless function execution. The pricing page makes it look fine until your viral launch — then it bites. Set up cost alerts on day one and check usage weekly for the first month.
Is Netlify dying?: No. Slower Next.js feature adoption than Vercel and less aggressive marketing than Cloudflare, but the platform is stable, the deploys are reliable, and the support is good. For a JAMstack site or a small SSR app, it is a perfectly fine choice.
What about self-hosting Next.js on a VPS?: Possible, sometimes correct, but underpriced. Saves real money at scale (DigitalOcean droplet at $50/mo vs Vercel at $500/mo for the same workload) but you own the ops — patches, monitoring, SSL renewal, the 2am page. Worth it when you have ops capacity; not worth it for most product teams.
Which one does Creative Brain use for client work?: Vercel for greenfield Next.js builds. Netlify when the client already has it set up. Cloudflare Workers for specific use cases (high-bandwidth public APIs, image transformation pipelines). Hosting is the kind of decision we make in 5 minutes and rarely revisit.