Deploying a frontend used to mean SSH-ing into a server and praying. Now you push to git and the world gets your changes in seconds. The question isn't whether to use a modern deployment platform — it's which one deserves your CI/CD pipeline.
Vercel is the Next.js company that also does hosting. Netlify pioneered the Jamstack deployment model. Cloudflare Pages is the infrastructure giant's play for the edge. Each has a distinct philosophy, and the right choice depends on your framework, your scale, and how much you care about your AWS bill.
The Short Answer
Building with Next.js? Vercel — it's their framework, and the integration is unbeatable. Static sites or Jamstack? Netlify — the DX is excellent and the ecosystem is mature. Cost-sensitive or want edge-first architecture? Cloudflare Pages — the free tier is absurd and the edge network is massive.
Pricing: Where It Gets Interesting
All three have generous free tiers, but the paid plans reveal different strategies:
Vercel
- Hobby: free (personal, non-commercial)
- Pro: $20/user/month
- Enterprise: custom
- 100GB bandwidth on free
- Serverless function limits apply
Netlify
- Starter: free
- Pro: $19/member/month
- Enterprise: custom
- 100GB bandwidth on free
- Generous build minutes
Cloudflare Pages
- Free: unlimited bandwidth (!)
- Free: unlimited requests (!)
- Pro: $20/month (full Cloudflare)
- 500 builds/month on free
- Workers integration included
The Catch
- Vercel: bandwidth overage is expensive
- Netlify: same — watch your bandwidth
- Cloudflare: truly unlimited bandwidth
- All three: serverless has its own limits
- At scale, Cloudflare is cheapest by far
Framework Support
Vercel is the home of Next.js, and it shows. Server components, ISR, middleware, image optimization — all of Next.js's features work perfectly on Vercel because they built both. Vercel also supports other frameworks (Nuxt, SvelteKit, Astro), but Next.js is the first-class citizen.
Netlify takes a framework-agnostic approach. Their build system auto-detects your framework, and they've built adapters for Next.js, Nuxt, SvelteKit, Remix, Astro, and more. The Next.js support has improved but still lags Vercel on bleeding-edge features.
Cloudflare Pages supports static site generators natively and has added full-stack framework support through their integration with Workers. Astro, Next.js (via @cloudflare/next-on-pages), SvelteKit, and Remix all work. The edge runtime is different from Node.js though, so some libraries don't work out of the box.
Performance & Edge
Cloudflare Pages wins on raw edge performance. Their network has 300+ PoPs globally — more than Vercel and Netlify combined. Static assets are fast on all three, but for edge-computed content, Cloudflare's infrastructure is purpose-built for this.
Vercel has invested heavily in edge functions and their Edge Runtime. For Next.js apps using middleware and edge routes, performance is excellent. They use multiple CDN providers under the hood for static assets.
Netlify uses a combination of their own CDN and cloud functions. Edge Functions (powered by Deno) are available but the edge story isn't as mature as Vercel's or Cloudflare's.
Developer Experience
Vercel has the most polished DX for full-stack apps. The dashboard is clean, preview deployments are instant, and the integration with GitHub is seamless. The CLI is fast and well-designed.
Netlify pioneered many DX features that others copied — deploy previews, branch deploys, form handling, identity, and split testing. The ecosystem of plugins and build plugins is robust. The dashboard is intuitive.
Cloudflare Pages has improved dramatically but the DX still has rough edges. The Wrangler CLI is powerful but quirky, and debugging Workers/Pages Functions locally can be frustrating. The dashboard is functional but less polished than Vercel or Netlify.
Serverless & Backend
Vercel offers Serverless Functions and Edge Functions. Easy to create — drop a file in /api and you're done. Cold starts can be noticeable on the free tier.
Netlify has Netlify Functions (AWS Lambda under the hood) and Edge Functions (Deno). Background functions for long-running tasks are a nice touch. The function bundling is smart.
Cloudflare has Workers — which are V8 isolates, not containers. This means near-zero cold starts and true edge compute. Combined with D1 (SQLite), R2 (S3-compatible storage), KV, and Durable Objects, you can build entire backends on Cloudflare's edge.
Lock-In Considerations
Vercel's tight Next.js integration means migrating away requires untangling framework-specific features (Image component, ISR config, middleware). Netlify and Cloudflare are slightly more framework-agnostic, making migration easier.
Cloudflare Workers uses the Service Worker API which is a web standard, making it potentially the most portable — but in practice, the ecosystem (KV, D1, R2) creates its own lock-in.
Our Verdict
For Next.js apps: Vercel is the obvious choice. The integration is unmatched and the DX is best-in-class. You'll pay for it at scale, but the productivity gains are real.
For static sites and Jamstack: Netlify. Mature, reliable, great DX, and the ecosystem of plugins solves common problems out of the box.
For cost-conscious teams or edge-first architecture: Cloudflare Pages. The unlimited free bandwidth is real, the edge network is the best, and the Workers platform is incredibly powerful. Accept some DX roughness for massive infrastructure value.