Cloudflare Pages
Edge-first Jamstack on Cloudflare's 300+ city network. Cheapest at scale, broader runtime constraints.
VISIT CLOUDFLARE PAGESKey takeaway: When bandwidth is your biggest line item, Cloudflare Pages is the answer and the decision is close to arithmetic. Free egress across a 300-plus city network beats Vercel and Netlify on cost at every scale. The price is the runtime: V8 isolates instead of Node, so choose it for greenfield work you can design around the constraint, not for lifting an existing Node app.
Quick facts
- CategoryJamstack
- PricingFreemium
- LicenseProprietary
- Created2020
- GitHub starsclosed
- Edge-readyYes
- Free tierYes
- Egress billingFree
Bundled services: Workers D1 (SQLite) R2 (S3-compat) KV Durable Objects Queues
What it is
Cloudflare Pages deploys static + edge-rendered sites onto Cloudflare's global network. Free unlimited bandwidth, free unlimited requests on the static tier, deep integration with Workers / D1 / R2 / KV / Durable Objects. The runtime constraints (V8 isolates, no Node APIs by default) are the trade-off, projects designed for Cloudflare are at home; projects expecting full Node need adapters.
Best for
- Cost-sensitive Jamstack at any scale, egress is genuinely free
- Projects already invested in Cloudflare Workers / D1 / R2
- Astro / Hugo / Eleventy projects with no heavy Node-runtime needs
- Apps that benefit from 300+ POP global distribution
When not to pick it
Skip Cloudflare Pages for Next.js apps requiring full Node compatibility, the adapters work but feel like a workaround compared to Vercel-native. Skip if your team values polish-first DX over cost.
My take
Cloudflare Pages is the right answer for cost-conscious Jamstack teams in 2026. The free egress alone is worth a serious look. The catch is the runtime constraint; greenfield projects can design around it, migrations have more friction.
The isolate runtime and what it costs you
Cloudflare runs your code in V8 isolates rather than Node processes, which is why cold starts are close to nonexistent and why the platform can afford to put your code in hundreds of cities. The same design is the constraint. Not all Node built-ins are present by default, native modules are out, and anything expecting a long-lived process with a filesystem needs rethinking. Frameworks ship Cloudflare adapters and they work, but an adapter is a translation layer, and translation layers leak at the least convenient moment during a migration. Greenfield projects have the easier time: design around fetch, Web Crypto, and Workers APIs from the start and the constraint stops feeling like one. Lifting an existing Express or Next.js app with heavy Node dependencies is the case where teams give up and go back to Vercel or Render.
The bundled platform, and two caveats
Pages on its own is a static host with edge rendering. What makes it interesting is everything sitting next to it: Workers for compute, D1 for SQLite, R2 for S3-compatible storage without egress fees, KV for edge key-value, Durable Objects for coordinated state, and Queues. Building inside that set gives you a coherent, cheap, globally distributed stack with one bill and one dashboard. Two honest caveats. Cloudflare's own guidance now points new projects at Workers with static assets rather than Pages, so treat Pages as the older of the two front doors. And this is the most specific lock-in on the list, because D1 and Durable Objects have no drop-in equivalent elsewhere. Keep business logic portable, treat the Cloudflare primitives as adapters behind interfaces, and the cost of leaving stays bounded.
Frequently asked questions
Is Cloudflare Pages really free?
The static tier is free with unlimited bandwidth and requests, and that is not a marketing trick. Paid plans arrive when you need more Workers compute, more build concurrency, or the bundled data products at volume. For a static site with an edge function or two, many teams never leave the free tier even at substantial traffic levels.
Cloudflare Pages or Vercel for Next.js?
Vercel, unless bandwidth cost is forcing your hand. Next.js on Cloudflare works through an adapter, and the adapter constrains which framework features you can use, which is a permanent tax on an app that follows Next.js releases. Cloudflare wins outright for Astro, Hugo, and Eleventy, where there is no framework lag and egress is free.
Can I run a Node app on Cloudflare Pages?
Only if it fits the Workers runtime. Cloudflare offers Node compatibility flags covering a growing subset of built-ins, but native modules, long-lived processes, and filesystem access are out. Express-style apps usually need reworking rather than porting. If your app genuinely needs Node, Render, Fly.io, or a plain VPS is the honest answer.
Links
Compare Cloudflare Pages side-by-side
Similar tools you should also consider
If Cloudflare Pages is your pick, the next conversation is short
The 30-min call is where your hosting choice becomes a real architecture, a migration plan if you are switching, and a price range you can take to your stakeholders without surprise bills in month 4. Describe your stack, your traffic shape, your budget. I tell you whether Cloudflare Pages is genuinely your fit.