The Three Platforms That Define Modern Web Hosting

If you are deploying a frontend application, a JAMstack site, or a full-stack web app in 2026, your shortlist probably includes Cloudflare Pages, Vercel, and Netlify. These three platforms dominate the modern web hosting space, each offering git-connected deployments, edge infrastructure, serverless functions, and generous free tiers.

But they are not interchangeable. Each platform has a distinct philosophy, pricing structure, and set of trade-offs. This three-way comparison covers everything you need to make an informed decision.

Quick Comparison

Feature	Cloudflare Pages	Vercel	Netlify
Free Bandwidth	Unlimited	100 GB/mo	100 GB/mo
Free Build Minutes	500/mo	6,000/mo	300/mo
Paid Plan	$5/mo (Workers Paid)	$20/user/mo (Pro)	$19/member/mo (Pro)
Edge Network	300+ PoPs	~100 PoPs	CDN via partners
Edge Functions	Workers (V8 isolates)	Edge Middleware + Functions	Edge Functions (Deno)
Serverless Functions	Workers	Node.js, Go, Python, Ruby	Node.js, Go
Framework Support	All major frameworks	All (Next.js optimized)	All major frameworks
Build System	Basic	Advanced (Remote Caching)	Solid
Preview Deployments	Yes	Yes	Yes
Storage	R2, D1, KV	KV, Blob, Postgres	Blobs (beta)
Forms	No	No	Yes (built-in)
Analytics	Free (privacy-first)	$10/project/mo (Pro inc.)	$9/site/mo

Build Speed and Deployment

Cloudflare Pages

Cloudflare Pages builds are functional but not the fastest. Build times for a typical Next.js or Astro site run slightly longer than Vercel. The platform supports 500 free build minutes per month, which is adequate for small projects but can feel tight for active development.

Where Cloudflare Pages excels is deployment speed. Once built, your site propagates to Cloudflare’s 300+ data center network almost instantly. There is no waiting for CDN cache invalidation because the content is pushed to the edge, not pulled.

In 2026, Cloudflare has improved its build infrastructure, and build times have gotten noticeably faster compared to a year ago. But if build performance is your top priority, Vercel still leads.

Vercel

Vercel has the most sophisticated build system of the three. Remote Caching shares build artifacts across team members and CI environments, significantly reducing rebuild times for large monorepos. Incremental builds only regenerate changed pages, which is especially effective for Next.js applications with hundreds or thousands of routes.

The 6,000 free build minutes per month are the most generous on this list. Deployments typically complete in under a minute for standard applications, and preview deployments for every pull request are automatic and fast.

Netlify

Netlify’s build system is solid and reliable. Build plugins let you extend the build process with caching optimizations, image processing, and other transformations. The 300 free build minutes per month are the lowest of the three, which can be limiting for active projects.

Netlify’s Deploy Previews were the original implementation that Vercel and Cloudflare later adopted. They work well, with built-in collaboration features that let team members leave comments directly on preview deployments.

Verdict

Vercel leads on build speed and build minutes. Cloudflare Pages leads on deployment propagation speed. Netlify is solid but its lower free build minutes are a drawback.

Edge Functions and Serverless Compute

This is where the three platforms diverge the most.

Cloudflare Workers (Pages Functions)

Cloudflare Workers run on V8 isolates across every one of Cloudflare’s 300+ data centers. Cold start times are essentially zero because isolates are far lighter than containers. Every request runs on the edge location closest to the user.

Workers have access to Cloudflare’s full ecosystem: D1 (SQLite at the edge), KV (key-value storage), R2 (S3-compatible object storage), Durable Objects (stateful edge compute), and Queues (message queues). This makes Cloudflare Pages the most capable platform for building full-stack applications entirely on the edge.

The trade-off is that Workers run in a V8 environment, not Node.js. Many Node.js APIs are now supported through compatibility flags, but some packages that depend on native modules or Node-specific features won’t work.

Vercel Functions

Vercel offers two compute models. Serverless Functions run on AWS Lambda in specific regions, supporting Node.js, Go, Python, and Ruby. Edge Functions and Edge Middleware run on Vercel’s edge network using a lightweight runtime.

For Next.js applications, Vercel’s integration is unmatched. API routes, server components, middleware, and ISR all work seamlessly. The platform automatically determines which routes should run at the edge versus in a regional serverless function.

Vercel’s Fluid Compute model in 2026 improves cold start times by keeping functions warm more intelligently and reusing execution contexts across requests.

Netlify Functions and Edge Functions

Netlify offers Serverless Functions (Node.js, Go on AWS Lambda) and Edge Functions (Deno-based, running on Deno Deploy’s network). The Deno runtime for edge functions means you write TypeScript with Deno’s standard library, which some developers love and others find unfamiliar.

Netlify’s function support is capable but less integrated than Vercel’s Next.js-specific optimizations or Cloudflare’s full edge ecosystem.

Verdict

Cloudflare Pages has the most powerful edge compute with the deepest supporting services (D1, KV, R2, Durable Objects). Vercel has the best integration for Next.js and the most polished serverless experience. Netlify’s edge functions are solid but less differentiated.

Pricing Deep Dive

Pricing is one of the most important factors, and the three platforms have very different models.

Cloudflare Pages

Free: Unlimited bandwidth, 500 builds/month, 1 build at a time
Workers Paid ($5/month): Unlocks Workers with 10M requests included, D1 5GB, R2 10GB, KV reads/writes
Workers Paid ($25/month add-on): Higher limits across all services

Cloudflare’s unlimited bandwidth on the free tier is extraordinary. You will never get a surprise bandwidth bill. The $5/month Workers Paid plan unlocks the full edge compute ecosystem at a price point that undercuts both competitors significantly.

Vercel

Hobby (Free): 100 GB bandwidth, 6,000 build minutes, commercial use not allowed
Pro ($20/user/month): 1 TB bandwidth, 24,000 build minutes, analytics included
Enterprise: Custom pricing, SLA, advanced security

Vercel’s per-user pricing means costs scale linearly with team size. A team of five developers pays $100/month before any usage overages. The Hobby plan’s prohibition on commercial use is important to note: production business sites require the Pro plan.

Netlify

Starter (Free): 100 GB bandwidth, 300 build minutes
Pro ($19/member/month): 1 TB bandwidth, 25,000 build minutes, 3 concurrent builds
Enterprise: Custom pricing, SSO, audit logs

Netlify’s pricing is similar to Vercel’s but slightly cheaper per seat. The lower free build minutes (300 vs 6,000) push active projects to paid plans faster.

Verdict

Cloudflare Pages is the cheapest option by a wide margin, especially at scale. Unlimited free bandwidth and a $5/month paid plan that includes edge compute, storage, and databases is remarkable value. Vercel and Netlify are similarly priced, with Vercel justifying the cost through superior build infrastructure and Next.js optimization.

[Try Cloudflare Pages free] | [Try Vercel free] | [Try Netlify free]

Framework Support

All three platforms support every major frontend framework (React, Vue, Svelte, Astro, Solid, etc.), but the depth of support varies.

Vercel + Next.js

Vercel’s support for Next.js is in a class of its own. App Router, Server Components, Streaming, ISR, Image Optimization, and Edge Middleware all work with zero configuration. Vercel develops Next.js, so new framework features are available on the platform immediately.

Other frameworks work on Vercel, but they don’t get the same level of optimization. An Astro or SvelteKit site will deploy and run fine, but you won’t see the same deep integration.

Cloudflare Pages + Anything

Cloudflare Pages takes a more framework-agnostic approach. Astro, SvelteKit, Nuxt, Remix, SolidStart, and even Next.js (via OpenNext) all deploy to Cloudflare Pages with server-side rendering running on Workers.

The OpenNext adapter for Cloudflare brings Next.js support that covers most features, though it occasionally lags behind Vercel’s native implementation for the newest features.

Netlify + Anything

Netlify also supports a wide range of frameworks with solid adapters. Netlify’s Remix and Astro support is strong. Next.js works through Netlify’s runtime adapter, which handles most features but, like Cloudflare, may trail Vercel for bleeding-edge Next.js capabilities.

Verdict

If you build with Next.js, Vercel is the obvious choice. If you use any other framework, Cloudflare Pages and Netlify are equally capable, with Cloudflare’s edge runtime offering performance advantages.

Developer Experience

Cloudflare Pages

The Cloudflare dashboard has improved significantly but can still feel overwhelming given the breadth of Cloudflare’s product suite. The Wrangler CLI is excellent for local development, letting you run Workers, D1, KV, and R2 locally. Documentation is thorough and well-organized.

The main DX friction is the V8-vs-Node.js environment difference. Some npm packages need workarounds or alternatives to run on Workers.

Vercel

Vercel’s DX is polished to a mirror shine. The dashboard is clean, the CLI is fast, and the integration with GitHub is seamless. The Vercel Toolbar provides in-page feedback, speed insights, and feature flag management. For Next.js developers, the experience of going from git push to production is about as frictionless as it gets.

Netlify

Netlify’s developer experience is warm and well-documented. The CLI supports local development with netlify dev. Built-in features like Netlify Forms (form submissions without a backend) and Netlify Identity (authentication) reduce the number of third-party services you need to integrate.

The collaborative Deploy Previews with visual commenting are a nice touch for teams that include designers and product managers in the review process.

Verdict

Vercel has the most refined DX, especially for Next.js. Netlify’s built-in features (Forms, Identity) reduce integration overhead. Cloudflare Pages offers the most raw power but requires more configuration knowledge.

When to Choose Cloudflare Pages

Cost is a major factor (unlimited bandwidth, $5/mo paid plan)
You need edge compute with supporting services (D1, KV, R2)
You’re building with frameworks other than Next.js
Performance and global latency matter most
You’re already in the Cloudflare ecosystem (DNS, WAF, Zero Trust)

[Try Cloudflare Pages free]

When to Choose Vercel

You build with Next.js and want the best possible integration
Developer experience and deployment speed are top priorities
You need advanced features like ISR, streaming, and edge middleware
Your team values a polished dashboard and built-in analytics
You’re willing to pay per-seat pricing for premium infrastructure

[Try Vercel free]

When to Choose Netlify

You want built-in features like form handling and authentication
Your team includes non-developers who participate in deploy reviews
You work across multiple frameworks without favoring one
You value a strong community and long track record
You need a platform that works with GitHub, GitLab, and Bitbucket

[Try Netlify free]

Final Thoughts

The honest answer is that all three platforms are excellent. You can build and ship a great web application on any of them.

Cloudflare Pages is the best value in web hosting, period. Unlimited bandwidth, edge-native compute, and an expanding suite of storage and database services for $5/month is difficult to argue against.

Vercel is the premium choice for teams that want the best DX and are invested in the Next.js ecosystem. You pay more, but you get a best-in-class deployment pipeline.

Netlify is the reliable all-rounder with thoughtful features that reduce the number of services you need to stitch together. It may not win any single category, but it delivers a well-rounded experience across the board.

Start with the free tier of each to see which workflow clicks for you. The switching cost between these platforms is relatively low, especially for static and JAMstack sites.