I've been deploying production Next.js and Astro sites for clients since 2020. Every year, the pricing conversation gets more complicated — not because the platforms are more expensive (though some are), but because the billing models keep shifting in ways that make apples-to-apples comparisons genuinely hard.

Last month I sat down with invoices from three platforms across nine client projects and did the math. Not the "calculator on their pricing page" math. The real math. The "why is this bill $340 when I estimated $80" math.

This article is everything I learned. If you're choosing between Vercel, Netlify, and Cloudflare Pages for a production deployment in 2026, this should save you a few painful surprises.

Vercel Pricing in 2026: Real Costs vs Netlify & Cloudflare Pages

Table of Contents

Why Platform Pricing Is Harder Than It Looks

Every platform wants you to look at their free tier and think "this is basically free." And for a personal blog or side project, it genuinely is. The problem starts when you have actual traffic, actual dynamic routes, and actual business requirements.

Here's what makes the comparison tricky:

  • Billing units differ. Vercel charges for function invocations and execution time. Netlify charges for "serverless function executions" with a different definition. Cloudflare charges for Workers requests. These aren't the same thing.
  • Bandwidth definitions vary. Some platforms count edge cache hits. Others don't. Some charge for image optimization bandwidth separately.
  • Overages are where the money is. The base plan might be $20/month, but a traffic spike can quietly 5x your bill.

I've seen teams pick Vercel because "it works great with Next.js" without realizing their ISR-heavy architecture would generate 2M function invocations per month. That's not a hypothetical — that was one of our Next.js development clients last year.

Vercel Pricing Breakdown 2026

Vercel updated their pricing structure in late 2025, and the current model (as of Q1 2026) looks like this:

Plan Tiers

Plan Monthly Cost Team Members Bandwidth Serverless Function Executions Edge Function Invocations Build Minutes
Hobby $0 1 100 GB 100K 500K 6,000/mo
Pro $20/member Up to 10 1 TB 1M 1M included 24,000/mo
Enterprise Custom Unlimited Custom Custom Custom Custom

What Actually Costs Money

The $20/member/month Pro plan is where most production sites land. But here's where it gets interesting:

  • Additional bandwidth: $40 per 100 GB after the 1 TB included
  • Additional serverless function executions: $6 per 1M after the first 1M
  • Additional edge function invocations: $2 per 1M
  • Edge Middleware: Runs on every request by default. If you're using middleware for auth checks or redirects, every single page view triggers it.
  • Image Optimization: 5,000 source images included on Pro; $5 per additional 1,000 source images
  • Web Analytics: Included, but Advanced Analytics starts at $10/project/month
  • DDoS Protection & WAF: Only on Enterprise

The Serverless Function Gotcha

This is the one that catches people. In a Next.js App Router project, every page.tsx that uses server components, every API route, every Server Action — these all count as serverless function invocations. A single page load can trigger multiple function invocations if you have parallel data fetching.

I audited a client project last quarter and found that a single product page was generating 4 function invocations per visit: one for the layout, one for the product data, one for recommendations, and one for inventory status. At 200K page views per month, that's 800K function invocations from one page alone.

// Each of these generates a separate function invocation on Vercel
// app/products/[slug]/page.tsx
export default async function ProductPage({ params }) {
  const product = await getProduct(params.slug); // invocation 1
  const recommendations = await getRecommendations(params.slug); // invocation 2
  const inventory = await getInventory(params.slug); // invocation 3
  
  return <ProductView product={product} recommendations={recommendations} inventory={inventory} />;
}

You can batch these, but the default patterns in most tutorials don't.

Vercel's 2025-2026 Pricing Changes

Vercel made a notable shift in late 2025 by introducing "Fluid Compute" as their default execution model, replacing the older per-invocation serverless approach with a more container-like model that keeps functions warm longer. This actually reduces costs for apps with consistent traffic, but bursty traffic patterns still get hit hard.

They also introduced spend caps on Pro plans — you can now set a maximum monthly spend, which is genuinely useful. Before this, runaway bills were a real concern.

Vercel Pricing in 2026: Real Costs vs Netlify & Cloudflare Pages - architecture

Netlify Pricing Breakdown 2026

Netlify restructured their pricing in early 2025 and has kept it relatively stable into 2026.

Plan Tiers

Plan Monthly Cost Team Members Bandwidth Serverless Functions Edge Functions Build Minutes
Starter $0 1 100 GB 125K invocations Unlimited 300/mo
Pro $19/member Up to 10 1 TB 2M invocations Unlimited 25,000/mo
Enterprise Custom Unlimited Custom Custom Custom Custom

What Actually Costs Money

  • Additional bandwidth: $55 per 100 GB (yes, more expensive than Vercel)
  • Additional serverless function invocations: $7.50 per 1M
  • Large media storage: $2.50 per 100 GB
  • Forms: 100 submissions/month on Starter; additional at $19/site/month for 1,000 submissions
  • Identity (Auth): 1,000 active users free; $99/site/month for 10,000
  • Analytics: $9/site/month

Netlify's Strengths and Weaknesses

Netlify's edge functions being unlimited on all paid plans is genuinely good. If your architecture leans heavily on edge logic — geolocation-based routing, A/B testing at the edge, auth token verification — Netlify won't charge you extra for it.

The weakness? Netlify's serverless functions run on AWS Lambda under the hood, and cold starts are noticeably worse than Vercel's in my testing (averaging 300-500ms vs Vercel's 100-200ms for comparable Node.js functions in early 2026).

Also, Netlify's Next.js support, while improved significantly with their runtime v5, still lags behind Vercel's native support. Features like Partial Prerendering and Server Actions work, but I've hit edge cases that required workarounds. If you're doing headless CMS development with a Next.js frontend, this matters.

Cloudflare Pages Pricing Breakdown 2026

Cloudflare Pages is the odd one out here, and in many ways, the most interesting option.

Plan Tiers

Plan Monthly Cost Team Members Bandwidth Workers Requests KV Operations Build Minutes
Free $0 Unlimited Unlimited 100K/day 100K reads/day 500/mo
Pro $20/month (flat) Unlimited Unlimited 10M/month 1B reads/month 5,000/mo
Business $200/month Unlimited Unlimited 50M/month 5B reads/month 20,000/mo

The Bandwidth Advantage

Read that table again. Unlimited bandwidth on all plans, including free. This is Cloudflare's killer advantage. If you're running a media-heavy site or serving lots of images and video, the bandwidth savings alone can be hundreds of dollars per month.

What Actually Costs Money

  • Additional Workers requests: $0.30 per 1M after plan limits
  • Durable Objects: $0.15 per 1M requests + storage fees
  • R2 Storage (if used for assets): $0.015 per GB/month, $4.50 per 1M Class A operations
  • Workers AI: Pay-per-use, varies by model
  • Images: $5/month for 100K variants; $1 per additional 100K

The Catch With Cloudflare Pages

Here's where I have to be honest: Cloudflare Pages runs on the Workers runtime, not Node.js. This means:

  • No native fs module
  • No native Node.js APIs (though compatibility has improved massively with the nodejs_compat flag)
  • Some npm packages simply won't work
  • Next.js support via @cloudflare/next-on-pages or the newer opennext adapter works, but it's not first-party

For Astro development, Cloudflare Pages is actually excellent. Astro's adapter for Cloudflare is well-maintained and the SSR story is solid. For Next.js, it's workable but you'll hit rough edges.

Side-by-Side Cost Comparison

Let me put real numbers to three common scenarios. All prices are monthly, based on 2026 pricing.

Metric Vercel Pro Netlify Pro Cloudflare Pro
Base cost (3 team members) $60 $57 $20
2 TB bandwidth $60 + $40 = $100 $57 + $55 = $112 $20
5M function invocations $60 + $24 = $84 $57 + $22.50 = $79.50 $20
2 TB bandwidth + 5M invocations $124 $134.50 $20
Image optimization (20K images) +$75 +$0 (use external) +$5
Analytics Included (basic) +$9/site Free (basic via CF dashboard)

That Cloudflare column is not a typo. For bandwidth-heavy, moderate-traffic sites, Cloudflare Pages is dramatically cheaper.

Real-World Scenario: Marketing Site with 500K Monthly Visitors

A typical marketing site for a mid-size company: 30 pages, CMS-driven content, contact forms, maybe a blog with 200 posts. Static generation with some ISR for the blog.

Assumptions:

  • 500K page views/month
  • 800 GB bandwidth (images, fonts, etc.)
  • 600K serverless function invocations (ISR, form handling, API routes)
  • 3 team members
  • 1,000 form submissions/month
Vercel Pro Netlify Pro Cloudflare Pro
Base plan $60 $57 $20
Bandwidth overage $0 $0 $0
Function overage $0 $0 $0
Forms External service $19 External service
Total $60 $76 $20

At this scale, all three are pretty affordable. The differences start to matter when you scale up.

Real-World Scenario: SaaS Dashboard with Heavy API Routes

A dashboard app with authenticated users, real-time data, lots of API calls. Think: analytics dashboard, project management tool, or admin panel.

Assumptions:

  • 50K active users
  • 8M page views/month
  • 2.5 TB bandwidth
  • 15M function invocations
  • 5 team members
  • WebSocket connections (where supported)
Vercel Pro Netlify Pro Cloudflare Business
Base plan $100 $95 $200
Bandwidth overage $600 $825 $0
Function overage $84 $97.50 $0
Total $784 $1,017.50 $200

Now the differences are stark. Cloudflare's flat-rate model with unlimited bandwidth absolutely shines for high-traffic dynamic apps. But remember — you're trading cost savings for a more constrained runtime environment.

Vercel would likely push you toward Enterprise at this scale, which typically starts around $1,500/month but includes DDoS protection, SLA guarantees, and priority support.

Real-World Scenario: E-commerce Storefront

A headless commerce site using Shopify or similar as the backend, with a Next.js or Astro frontend.

Assumptions:

  • 200K monthly visitors
  • 1.5M page views (browsing behavior)
  • 1.8 TB bandwidth (product images)
  • 8M function invocations (product pages, cart, checkout, search)
  • 15,000 source images for optimization
  • 4 team members
Vercel Pro Netlify Pro Cloudflare Pro
Base plan $80 $76 $20
Bandwidth overage $320 $440 $0
Function overage $42 $45 $0
Image optimization $50 External ($20-50) $5
Total $492 $581-611 $25

E-commerce is where the bandwidth costs really bite on Vercel and Netlify. Even with aggressive caching, product images eat bandwidth fast.

If you're building a headless storefront and cost is a factor, Cloudflare Pages deserves serious consideration — assuming your framework of choice has solid Cloudflare support. Check our pricing page if you want help evaluating the right platform for your specific project.

Hidden Costs Nobody Talks About

Preview Deployments

All three platforms create preview deployments for PRs. On Vercel Pro, you get unlimited preview deployments, but they consume build minutes and function invocations. A busy team pushing 20 PRs/day with automated testing can burn through build minutes fast.

Middleware and Edge Execution

Vercel's middleware runs on every request that matches its matcher pattern. If your middleware checks auth on every route, that's an edge function invocation per request. On a site with 1M monthly requests, that's 1M edge function invocations just for middleware. At $2 per 1M, it's cheap — but it adds up when combined with other edge usage.

Cron Jobs

Vercel charges cron job invocations against your serverless function quota. If you have a cron that runs every minute, that's 43,200 invocations/month from a single cron. Netlify's scheduled functions work similarly. Cloudflare's Cron Triggers are included in your Workers request quota.

Build Minutes in Monorepos

If you're running a monorepo with Turborepo, every deployment rebuilds more than you'd think. Vercel's Remote Caching helps, but you'll still use more build minutes than a single-project repo. I've seen monorepos consume 3-5x the build minutes of equivalent standalone projects.

Developer Experience Cost

This isn't on any invoice, but it's real. Vercel's DX for Next.js is unmatched. Things just work. The deploy preview comments, the speed insights, the integration with the Next.js error overlay — it saves developer hours. If you're paying developers $150/hour and Vercel saves each dev 2 hours/month in debugging deployment issues, that's worth $300/month per developer. Factor that in.

Which Platform Should You Actually Pick

After deploying dozens of production sites across all three platforms, here's my honest take:

Pick Vercel if:

  • You're building with Next.js and want zero friction
  • DX matters more than saving $50/month
  • You need the latest Next.js features on day one
  • Your traffic is moderate and predictable

Pick Netlify if:

  • You need built-in forms, identity, or other add-ons
  • Your team prefers a more visual/UI-driven deployment workflow
  • You're using a framework other than Next.js (Hugo, Eleventy, etc.)
  • Edge functions are a core part of your architecture

Pick Cloudflare Pages if:

  • Bandwidth costs would be significant on other platforms
  • You're building with Astro, SvelteKit, or another CF-friendly framework
  • You want the most aggressive cost optimization
  • You're comfortable working within Workers runtime constraints
  • You need global performance (CF's edge network is massive)

For most of our client work at Social Animal, we default to Vercel for Next.js projects and Cloudflare Pages for Astro projects. The rare Netlify deployment happens when a client has existing Netlify infrastructure or needs their specific add-on features.

If you're unsure which direction to go, reach out to us — platform selection is one of the first things we nail down in any engagement.

FAQ

How much does Vercel actually cost for a production site in 2026? For a typical production site with moderate traffic (under 500K monthly visitors), expect to pay $60-120/month on the Pro plan depending on team size. High-traffic sites with heavy dynamic rendering can easily hit $500-1,000/month due to bandwidth and function invocation overages. Vercel's spend caps (introduced in late 2025) help prevent bill shock, but you'll need to set them proactively.

Is Cloudflare Pages really free for production use? The free tier is genuinely usable for small production sites — unlimited bandwidth is real. However, you're limited to 100K Workers requests per day, 500 build minutes per month, and one build at a time. For any serious production site with a team, the $20/month Pro plan is the practical minimum. It's still dramatically cheaper than alternatives.

Can I use Next.js on Cloudflare Pages? Yes, but with caveats. The @cloudflare/next-on-pages package and the newer OpenNext adapter both work, but you'll encounter limitations. Some Next.js features like native next/image optimization need workarounds, and the Workers runtime doesn't support all Node.js APIs. App Router works, but I'd recommend thorough testing of your specific patterns before committing. For full Next.js compatibility, Vercel remains the path of least resistance.

Why is my Vercel bill higher than expected? The most common culprits are: middleware running on every request (check your matcher patterns), ISR/SSR pages generating more function invocations than anticipated (each parallel data fetch can be a separate invocation), preview deployments consuming resources, and image optimization charges for sites with lots of unique images. Enable Vercel's usage dashboard and check it weekly until you understand your consumption patterns.

Is Netlify cheaper than Vercel in 2026? At the base plan level, they're nearly identical ($19 vs $20 per member). Where they diverge is overages: Netlify charges $55 per 100 GB of additional bandwidth vs Vercel's $40. Netlify's serverless function overage is also slightly more expensive. However, Netlify includes unlimited edge functions on paid plans, which can offset costs if your architecture is edge-heavy. For most standard web projects, Vercel ends up slightly cheaper.

Do any of these platforms offer spend caps or billing alerts? Vercel introduced spend caps on Pro plans in 2025 — you can set a hard limit, and your site will continue serving cached content when you hit it. Netlify offers spend notifications but not hard caps on Pro. Cloudflare's model is largely flat-rate, making overages less of a concern, but they do offer billing alerts for Workers usage. Always set up alerts regardless of platform.

What's the best platform for a headless CMS site? It depends on the framework. For Next.js with a headless CMS (Sanity, Contentful, Storyblok), Vercel offers the smoothest experience with features like on-demand ISR and draft mode. For Astro-based headless CMS sites, Cloudflare Pages gives you incredible performance at a fraction of the cost. The CMS choice itself rarely dictates the platform — it's the frontend framework that matters most.

Should I use Vercel Enterprise or explore alternatives? If your Vercel Pro bill consistently exceeds $800/month, it's worth having the Enterprise conversation — not because it's cheaper per se, but because you get SLA guarantees, DDoS protection, and a dedicated support engineer. Alternatively, at that spend level, migrating dynamic workloads to Cloudflare Workers while keeping your static assets on any CDN can cut costs by 60-70%. We've done this migration for several clients and it's not as painful as it sounds.