Vercel vs Netlify vs Cloudflare Pages: Which Host Fits Your Project?

If you build with Next.js and want the least friction, choose Vercel. If you want a predictable flat price for a team and a generous free tier that allows commercial use, choose Netlify. If your site is mostly static or you expect large traffic on a small budget, choose Cloudflare Pages (or Workers static assets), because static requests and bandwidth are not billed.

The differences that actually matter are not in the marketing pages. They are in how each platform meters usage, what happens when you exceed the free tier, and how much of your framework works out of the box.

Key takeaways

• Vercel Hobby is non-commercial only. Any business site belongs on Pro at $20 per developer seat per month, with $20 of included usage credit (as of October 2026).
• Netlify now bills in credits. Free gets a hard 300-credit monthly limit, Personal is $9/month with 1,000 credits, and Pro starts at $20/month for unlimited members (as of October 2026).
• Cloudflare does not charge for static asset requests or egress. You pay only for dynamic compute, with a $5/month minimum on the Workers Paid plan (as of October 2026).
• Framework fit beats price for most teams. A Next.js app that fights its host costs more in developer hours than any hosting bill.
• Set a spend limit on day one. All three let you cap or control spend; few people turn it on until after a surprise invoice.

How the three platforms differ at a glance

All three deploy from Git, give you preview URLs per branch, issue free SSL certificates and serve from a global CDN. The split is in the business model.

• Vercel is a frontend cloud built around Next.js. You pay a seat fee and draw down a usage credit across many small meters (requests, data transfer, function CPU, image transformations).
• Netlify is framework-agnostic and moved new accounts to a credit system in September 2025. Production deploys, bandwidth, compute and web requests all consume credits from one pool.
• Cloudflare Pages sits on Cloudflare's network and Workers runtime. Static hosting is effectively free; dynamic code is billed as Workers requests and CPU time.

Pricing and plan limits compared (as of October 2026)

Sources for every figure are listed at the end. Prices exclude VAT/GST, which all three add based on your billing address.

Vercel: the default for Next.js

Vercel's advantage is that it builds Next.js. Incremental Static Regeneration, middleware, streaming, the image component and server actions all work on day one without adapters. If your team ships a Next.js product weekly, that saves real debugging time.

What the Pro plan includes. The $20 seat fee comes with $20 of monthly usage credit. Beyond that, usage is billed per meter. Vercel also offers a Flat Rate CDN option on Pro, which bills CDN requests and Fast Data Transfer at a fixed monthly price with traffic spike protection. Extra developer seats cost $20 each; viewer seats are free and unlimited.

Where the bill grows. The meters that usually move first are function CPU time (Fluid Active CPU), image optimization transformations and ISR writes. A content site that regenerates thousands of pages on every CMS edit can burn ISR writes quickly. Enterprise-style features also carry add-on prices on Pro, such as SAML SSO at $300/month and a HIPAA BAA at $350/month (as of October 2026).

Spend control. New Vercel teams get a default on-demand budget of $200 with alerts, and you can configure a hard limit that pauses projects at 100%. Set it to a number you are comfortable losing.

Netlify: credits, predictable tiers and a commercial-friendly free plan

Netlify works well with Astro, Remix, SvelteKit, Hugo, Eleventy and Next.js. It is popular with agencies because one Pro team covers unlimited members, and its deploy previews, form handling and split testing are mature.

How the credit model works. Every metered action draws from your monthly credit pool:

• Production deploy: 15 credits
• Bandwidth: 20 credits per GB
• Compute: 10 credits per GB-hour
• Web requests: 2 credits per 10,000 requests

On the Free plan, 300 credits is a hard ceiling. Twenty production deploys alone would use the whole month, so a busy marketing team pushing content edits through Git can pause its own site. Pro lets you pick a tier from 3,000 to 20,000 credits; tiers above 3,000 roll unused credits over for one extra cycle.

The pause rule matters. Netlify states that when a project on a credit-based plan hits its limit, the site pauses until the next billing cycle, and if one project exceeds its limits, all projects on the account are paused. Auto recharge is off by default. For a client site, either enable auto recharge or keep a paid tier with headroom.

Accounts created before September 4, 2025 can stay on legacy plans, so pricing you see in older blog posts may not apply to new sign-ups.

Cloudflare Pages: near-zero cost for static traffic

Cloudflare's model is the most generous for traffic. Its Workers documentation states that requests to static assets are free and unlimited, and Workers pricing has no data transfer or bandwidth charges. For a brochure site, documentation portal or landing page that suddenly gets heavy traffic, that removes the scariest line on a hosting invoice.

Free plan limits that apply. Pages allows 500 builds per month with one build at a time, a 20-minute build timeout, 20,000 files per site, a 25 MiB maximum file size and 100 custom domains per project. Pages Functions count against Workers quotas: 100,000 requests per day on Free, resetting at midnight UTC.

Paid dynamic usage. Workers Paid starts at $5/month per account and includes 10 million requests and 30 million CPU milliseconds per month, then $0.30 per additional million requests and $0.02 per additional million CPU milliseconds (as of October 2026).

The trade-offs. Workers is not Node.js; it is a V8-isolate runtime with Node compatibility. Most modern libraries work, but some native modules do not. Next.js runs through an adapter rather than natively, so check feature support before committing a large app. Cloudflare also now publishes a guide to migrate from Pages to Workers static assets, which signals where new development effort is going.

Which one should you choose?

Use this decision process rather than picking on headline price.

1. Identify your framework. Next.js with heavy server features: lean Vercel. Astro, Hugo, Eleventy or a mostly static build: any of the three, and Cloudflare is cheapest at scale.
2. Decide whether the site earns money. If yes, rule out Vercel Hobby immediately.
3. Estimate monthly traffic in GB and requests. Multiply your average page weight by expected page views. Above a few hundred GB per month, Cloudflare's unmetered static bandwidth or Vercel's Flat Rate CDN become worth comparing.
4. Count how often you deploy. Frequent content deploys favor Vercel or Cloudflare over Netlify Free, where each production deploy costs 15 credits.
5. Check compliance needs. If you need a HIPAA BAA, SSO or audit logs, price those add-ons up front; they often outweigh the base plan.
6. Set spend limits and alerts before launch.

Quick recommendations

• Startup building a Next.js SaaS: Vercel Pro. Pair it with a managed database such as Supabase (see Supabase vs Firebase).
• Marketing or content site for a small business: Cloudflare Pages or Netlify, built with a static-first framework (see Next.js vs Remix vs Astro for business sites).
• Agency hosting many client sites with a shared team: Netlify Pro, since members are not charged per seat on credit-based Pro.
• High-traffic static site on a tiny budget: Cloudflare.
• Backend-heavy app with long-running jobs: consider a full cloud instead (see AWS vs Google Cloud vs Azure for startups).

From experience: On client Next.js builds I default to Vercel because it removes framework surprises, then move static marketing pages elsewhere only if traffic justifies it. Most early projects never reach the point where hosting is a meaningful cost; developer time is.

Migration and lock-in

All three are easy to leave if you keep your app framework-standard. Lock-in creeps in through platform-specific features:

• Vercel: Edge Config, Vercel KV/Blob, and Vercel-specific middleware behavior.
• Netlify: Netlify Forms, Identity, Blobs and redirect rules in netlify.toml or _redirects.
• Cloudflare: KV, D1, R2, Durable Objects and Workers bindings.

None of these are bad choices, but write them down in your architecture notes so a future migration is a known cost, not a surprise. If you are choosing your whole stack at once, our guide to choosing a tech stack for a startup walks through the wider decision.

Pre-launch hosting checklist

• [ ] Plan matches use: no commercial sites on Vercel Hobby
• [ ] Spend limit or hard cap configured, with alerts going to a monitored inbox
• [ ] Custom domain connected, HTTPS enforced, www redirect set
• [ ] Environment variables split by preview and production
• [ ] Preview deployments protected if they expose unreleased features or client data
• [ ] Build time checked against plan limits (Cloudflare Pages times out at 20 minutes)
• [ ] Image optimization usage estimated if you rely on it
• [ ] Platform-specific features listed in your architecture notes
• [ ] Rollback tested once before launch day
• [ ] Monitoring or uptime checks in place outside the host itself

Next steps

• Write down your framework, expected monthly traffic and deploy frequency, then run them through the decision process above.
• Open each provider's pricing calculator with those numbers rather than guessing from free-tier limits.
• Deploy the same branch to two platforms for a week and compare build times and real-user performance.
• Turn on spend limits before you share the production URL.
• If you want a second opinion on your architecture before you commit, a fractional CTO review can save months of rework.

Sources

• Vercel pricing: https://vercel.com/pricing
• Vercel Hobby plan (non-commercial use): https://vercel.com/docs/plans/hobby
• Vercel limits: https://vercel.com/docs/limits
• Netlify pricing and credits FAQ: https://www.netlify.com/pricing/
• Cloudflare Pages limits: https://developers.cloudflare.com/pages/platform/limits/
• Cloudflare Workers pricing: https://developers.cloudflare.com/workers/platform/pricing/
• Cloudflare Workers static assets billing: https://developers.cloudflare.com/workers/static-assets/billing-and-limitations/
• Cloudflare Workers Next.js guide: https://developers.cloudflare.com/workers/framework-guides/web-apps/nextjs/

Keep reading