On this page · 12 sections
- What changed for 2027, and what to do before 1 December
- Vercel Pro: a platform fee, a credit and paid seats
- Netlify Pro: credits and unlimited members
- Cloudflare Workers and Pages: a $5 account minimum
- The Workers Logs billing change on 1 December 2026
- Head-to-head comparison
- Worked monthly bill: a Next.js SaaS at two traffic levels
- Decision table: choose X if
- US and UK notes: tax, currency and data transfers
- Migration and cost-control checklist
- How eCorpIT can help
- References
Summary. The three hosts bill on different units, so team size and traffic shape decide the cheapest, not the headline price. Vercel Pro is a $20 monthly platform fee that includes one deploying seat and $20 of usage credit; each extra deploying seat is $20 a month and viewer seats are free. Netlify Pro is $20 a month with unlimited members and 3,000 credits, and extra credits cost $10 per 1,500 through auto recharge. Cloudflare Workers Paid has a $5 monthly account minimum with 10 million requests and 30 million CPU milliseconds included and no egress charge. From 1 December 2026, Workers Logs moves from $0.60 per million events to Cloudflare Observability pricing: 50 GB of ingestion and 10 GB-month of storage included, then $0.25 per GB and $0.10 per GB-month. In our worked example, a Next.js SaaS with four developers and 2.5 million requests a month costs about $100 on Vercel, $30 on Netlify and $5 on Cloudflare; at eight developers and 25 million requests it is about $308, $230 and $8.40. Seats drive Vercel's bill and bandwidth drives Netlify's; Cloudflare's figure assumes your app runs on vinext (beta) or OpenNext. Vercel says it will add sales tax for California and Colorado addresses from 1 January 2027.
About this article. For founders, engineering leads and finance owners in the US and UK choosing where to host a Next.js or similar web app. We checked every price, allowance and date against Vercel, Netlify and Cloudflare's own pricing pages, documentation and changelogs, and against UK government and US state tax agency pages, on 12 November 2026. All figures are list prices in US dollars before tax; vendors change them often, and no vendor paid for inclusion. This is not financial or tax advice. Researched with AI assistance and reviewed by our editorial team.
What changed for 2027, and what to do before 1 December
Older comparisons are out of date because each host has changed its billing model. Vercel replaced fixed Pro allowances with a $20 monthly usage credit and free viewer seats on 9 September 2025, and on 8 September 2026 made Flat Rate CDN generally available, switched on by default for new Pro teams. Netlify moved new accounts to credit-based plans on 4 September 2025. On 14 April 2026 it dropped the $20 seat charge on credit-based Pro and doubled the bandwidth and compute rates in credits. Cloudflare keeps its $5 Workers Paid minimum but moves Workers Logs to byte-based pricing on 1 December 2026.
Three actions this month:
- Cloudflare users: measure the size of your Workers log events before 1 December. Billing switches from event count to gigabytes ingested, so verbose logs can cost more than before while small ones cost less.
- Vercel users: count deploying seats, then check your Flat Rate CDN tier against sustained traffic. Existing teams stay on on-demand CDN billing unless they opt in, and tier changes take effect at the next billing cycle.
- Netlify users on legacy plans: price your real usage in credits before switching, because Netlify says the move to a credit-based plan cannot be reversed.
For function-level compute on two of these platforms, see our earlier Cloudflare Workers vs Vercel Functions cost analysis; this piece adds Netlify, seats, credits, CDN tiers, the logs change and tax.
Vercel Pro: a platform fee, a credit and paid seats
The $20 monthly platform fee includes one deploying seat and $20 of usage credit. Extra Owner or Member seats, which can deploy, cost $20 a month each. Viewer seats are free and unlimited; viewers can see deployments and comment on previews but cannot configure or deploy. Hobby is free but limited to personal, non-commercial use, so a revenue-earning SaaS belongs on Pro.
The credit covers managed infrastructure from the first unit and expires at month end; usage then bills on demand. New teams get a default $200 on-demand budget with alerts, and can opt to pause production deployments when it is reached.
Unit rates are regional. In Washington D.C. (iad1), Vercel charges $2.00 per million CDN requests, $0.15 per GB of Fast Data Transfer, $0.128 per hour of Fluid Active CPU and $0.0106 per GB-hour of provisioned memory. In London (lhr1) the same lines are $2.40, $0.15, $0.177 and $0.0146. Function invocations cost $0.60 per million, Fast Origin Transfer is $0.06 per GB in both regions, and Deployment Storage and Functions Storage are $0.10 per GB-month each.
Builds cost from $0.0035 per CPU minute, which is one build minute multiplied by the machine's vCPUs. New Pro teams use Elastic build machines by default, with 4 to 30 vCPUs, so a 4-minute build on the smallest is 16 CPU minutes, or $0.056. Paid teams can pin the 2-vCPU Basic machine instead.
Flat Rate CDN replaces per-unit billing for CDN requests and Fast Data Transfer (plus Blob and Sandbox data transfer) with a capacity tier. Pro includes the lowest tier, 1 million requests and 1 TB a month. Paid tiers are $20 for 10 million requests and 50 TB, $100 for 50 million and 50 TB, and $300 for 150 million and 50 TB. Spike protection is on by default, so traffic above the tier is still served and not billed, and Vercel moves you to the right tier at the start of the next cycle if sustained usage exceeds it. Bulk file distribution and media-heavy delivery fall outside its fair-use terms. Vercel does not say whether the usage credit can pay a tier fee; we assume it cannot.
Paid add-ons that often appear on SaaS bills: SAML single sign-on at $300 a month, a HIPAA BAA at $350 a month, password protection at $20 per project a month, and Observability Plus at $1.20 per million events. Runtime logs are kept for one day on Pro, or 30 days with Observability Plus.
Netlify Pro: credits and unlimited members
Netlify's credit-based plans are Free (300 credits a month, hard limit), Personal ($9 a month, 1,000 credits, one member) and Pro ($20 a month, 3,000 credits, unlimited members). The credit meters are:
- Production deploy: 15 credits each. Deploy Previews, branch deploys, failed deploys and rollbacks are free.
- Bandwidth: 20 credits per GB, covering web assets, images, downloads and function responses.
- Web requests: 2 credits per 10,000, including page views, API calls, redirects and Edge Functions.
- Compute: 10 credits per GB-hour for functions, preview servers, Agent Runners and Netlify Database.
- AI inference: 180 credits per US dollar of model usage through Agent Runners or the AI Gateway.
- Form submissions: free on all credit plans.
On Pro, auto recharge adds 1,500 credits for $10 when the balance runs out, about $0.0067 a credit, and recharged credits do not expire. Auto recharge is off by default. When credits run out with recharge off, Netlify pauses every project on the team and visitors see an unavailable-site page until the next cycle. That is a hard spend ceiling and an outage risk at once.
Netlify also sells Pro tiers of 5,000, 10,000, 15,000 and 20,000 monthly credits, with one-month rollover from 5,000 up, but its docs and pricing page send you to the dashboard for those prices, so we did not use them below. Pro includes three concurrent builds, then $40 a month each. On Pro, observability history and function logs run to seven days, with 30 days of web analytics and real user monitoring.
For Next.js, Netlify uses its open-source OpenNext adapter, which supports the App Router, ISR, Server Actions, streaming, middleware and skew protection for Next.js 13.5 onward.
Cloudflare Workers and Pages: a $5 account minimum
Cloudflare prices Workers per account, not per seat. Workers Paid costs a minimum of $5 a month and includes 10 million requests (then $0.30 per million) and 30 million CPU milliseconds (then $0.02 per million). There is no charge for duration and none for egress or bandwidth, and requests to static assets are free and unlimited. One catch: with Workers Caching turned on, cache hits are billed at the per-request rate even though they use no CPU. Pages Functions are billed as Workers.
Cloudflare's Next.js guide recommends vinext, a Vite plugin that reimplements the Next.js API surface, as the default way to run Next.js on Workers, and labels it beta. It supports the App Router, Server Actions, ISR and middleware, while image optimisation is only partly supported. OpenNext stays documented for existing apps that cannot yet migrate, and Pages for static exports. Run npx vinext check before you assume your app will port unchanged.
Workers Builds include 6,000 build minutes a month on paid plans, then $0.005 per minute, with six concurrent builds on 4 vCPUs. The Free plan allows 100,000 requests a day and 10 ms of CPU per invocation, which suits prototypes rather than production SaaS. Since July 2026, eligible pay-as-you-go accounts get a default $10 budget alert, which emails you but does not cap spend.
The $5 minimum covers Workers, Pages Functions, KV, Hyperdrive and Durable Objects allowances. It excludes R2 storage, Images, usage above each allowance and the engineering time to keep a non-Vercel Next.js runtime current.
The Workers Logs billing change on 1 December 2026
Until 1 December, Workers Paid includes 20 million log events a month, then $0.60 per million, with seven-day retention; Workers Free allows 200,000 events a day with three days of retention. Then Workers Logs moves to Cloudflare Observability pricing, a page Cloudflare last updated on 11 November 2026.
Under Observability pricing, Workers Logs shares its ingestion and storage allowances with Workers Traces, Cloudflare Traces, Containers logs, R2 Data Access Logs, AI Gateway logs and Issues. The Paid allowance is 50 GB of ingestion and 10 GB-month of storage per billing cycle, then $0.25 per GB ingested and $0.10 per GB-month stored. Data is kept seven days by default, so storage is roughly ingestion multiplied by 7/30. Cloudflare measures the uncompressed size of each event, including the attributes it adds. Free accounts get 0.5 GB of ingestion a day, then ingestion stops until 00:00 UTC. Free, Pro and Business accounts switch automatically on 1 December; Enterprise accounts switch at contract renewal.
The change rewards small logs and penalises large ones. Our example: 100 million requests a month, two log events per request:
| Log size per request | Old pricing (events) | New pricing (bytes) |
|---|---|---|
| 2 KB (about 1 KB per event) | (200M - 20M) × $0.60 per M = $108.00 | Ingest (200 - 50) GB × $0.25 = $37.50; store (46.7 - 10) GB-month × $0.10 = $3.67; total $41.17 |
| 6 KB (about 3 KB per event) | $108.00 | Ingest (600 - 50) GB × $0.25 = $137.50; store (140 - 10) GB-month × $0.10 = $13.00; total $150.50 |
Ignoring allowances, the models break even at about 2.2 KB per event: $0.60 per million events divided by about $0.273 per GB (ingestion plus seven days of storage). Above that, the December bill rises. The levers Cloudflare documents are a head_sampling_rate below 1 and turning off invocation logs you do not read; keeping each event small does the rest.
Head-to-head comparison
The table summarises the list prices above, checked on 12 November 2026 against each vendor's pricing pages and docs.
| Item | Vercel Pro | Netlify Pro | Cloudflare Workers Paid |
|---|---|---|---|
| Base price | $20/month platform fee | $20/month | $5/month account minimum |
| Included usage | $20 credit; Flat Rate CDN base tier (1M requests, 1 TB) | 3,000 credits | 10M requests, 30M CPU ms |
| Seats | 1 deploying seat; extra $20/month each; viewers free | Unlimited members | No per-seat charge in Workers pricing |
| Bandwidth | $0.15/GB on demand, or a Flat Rate tier | 20 credits/GB (about $0.13 at recharge rate) | No egress charge |
| Requests | $2.00/M (iad1), $2.40/M (lhr1) on demand | 2 credits per 10,000 | $0.30/M above 10M; static assets free |
| Compute | $0.128/h Active CPU + $0.0106/GB-h memory (iad1) | 10 credits/GB-hour | $0.02 per M CPU ms above 30M |
| Builds | From $0.0035 per CPU minute | 15 credits per production deploy | 6,000 min included, then $0.005/min |
| Logs | 1 day; 30 days with Observability Plus at $1.20/M events | 7-day function logs | Observability pricing from 1 Dec 2026 |
| Spend control | $200 default budget, optional pause of production | Auto recharge off means a hard stop | Per-Worker CPU limits; $10 default budget alert |
| Next.js path | Native, no adapter | OpenNext adapter | vinext (beta) or OpenNext |
Worked monthly bill: a Next.js SaaS at two traffic levels
These are our modelling assumptions for a B2B Next.js SaaS, not measurements. Our 40 ms of CPU per request is deliberately high: Cloudflare says server-side rendering workloads typically use 10 to 20 ms.
| Assumption | Level 1: launch | Level 2: growth |
|---|---|---|
| Deploying developers (plus free viewers) | 4 | 8 |
| HTTP requests per month | 2.5 million | 25 million |
| Data transfer | 120 GB | 1.2 TB |
| Server-rendered and API invocations | 500,000 | 5 million |
| Active CPU per invocation | 40 ms | 40 ms |
| Wall-clock time and memory per invocation | 200 ms at 1 GB | 200 ms at 1 GB |
| Production deploys / preview builds | 60 / 200 | 120 / 480 |
| Build time (Vercel on a 4-vCPU Elastic machine) | 4 min | 5 min |
| Vercel origin transfer / deployment and functions storage | 15 GB / 15 GB-month | 150 GB / 40 GB-month |
| Log volume per invocation (Cloudflare) | 2 KB | 2 KB |
Vercel, Level 1 (US, iad1, Flat Rate CDN on, the default for new teams). At 2.5 million requests the team outgrows the included tier and settles on the $20 tier, which covers the CDN lines. Remaining usage: invocations 0.5 × $0.60 = $0.30. Active CPU 500,000 × 0.04 s = 5.56 hours × $0.128 = $0.71. Memory 500,000 × 0.2 s × 1 GB = 27.8 GB-hours × $0.0106 = $0.29. Origin transfer 15 × $0.06 = $0.90. Builds 260 × 4 min × 4 vCPU = 4,160 CPU minutes × $0.0035 = $14.56. Storage 15 × $0.10 = $1.50. That is $18.26, inside the $20 credit. Add the $20 platform fee, three extra seats at $60 and the $20 tier: $100.00 a month. On demand, CDN requests (2.5 × $2.00 = $5.00) and Fast Data Transfer (120 × $0.15 = $18.00) would take usage to $41.26 and the bill to about $101. In London it is also $100.00, as usage still fits the credit.
Vercel, Level 2 (US, $100 Flat Rate tier). On demand, CDN requests would be $50 and data transfer $180; the $100 tier (50 million requests, 50 TB) replaces both. Remaining usage: invocations $3.00, Active CPU 55.6 hours × $0.128 = $7.11, memory 277.8 GB-hours × $0.0106 = $2.94, origin transfer $9.00, builds 600 × 5 min × 4 vCPU = 12,000 CPU minutes × $0.0035 = $42.00, storage $4.00: $68.06 with lines rounded, or $48.06 after the credit. Add the $20 platform fee, seven extra seats at $140 and the $100 tier: $308.06 a month, against $438.06 fully on demand. In London the Flat Rate bill is $311.89. Pinning the 2-vCPU Basic build machine would halve the $42 build line if build times hold. Fluid compute's in-instance concurrency can lower the memory line.
Netlify, Level 1. Deploys 60 × 15 = 900 credits. Bandwidth 120 × 20 = 2,400. Requests 2.5M ÷ 10,000 × 2 = 500. Compute 27.8 GB-hours × 10 = 278. Total 4,078 credits, 1,078 over the 3,000 included, so one $10 recharge: $30 a month, with 422 recharged credits left that do not expire.
Netlify, Level 2. Deploys 1,800, bandwidth 24,000, requests 5,000, compute 2,778: 33,578 credits, 30,578 over. That needs 21 recharges of 1,500 credits: $230 a month. Bandwidth alone is about 71% of the credits; a higher Pro tier may cost less once you see its dashboard price.
Cloudflare, Level 1. 500,000 Worker requests and 20 million CPU ms sit inside the allowances, builds use 1,040 of 6,000 minutes and logs are about 1 GB: $5 a month.
Cloudflare, Level 2. Requests 5 million (inside 10 million). CPU 5M × 40 ms = 200M ms; (200M - 30M) × $0.02 per million = $3.40. Builds use 3,000 minutes and logs 10 GB (about 2.3 GB-month stored), both inside allowances: $8.40 a month. If all 25 million requests hit the Worker rather than free static assets, add (25M - 10M) × $0.30 per million = $4.50.
| Monthly bill (USD, before tax) | Vercel Pro (US) | Vercel Pro (UK, lhr1) | Netlify Pro | Cloudflare Workers Paid |
|---|---|---|---|---|
| Level 1: 4 devs, 2.5M requests | $100.00 | $100.00 | $30.00 | $5.00 |
| Level 2: 8 devs, 25M requests | $308.06 | $311.89 | $230.00 | $8.40 |
| Biggest cost driver | Seats | Seats | Bandwidth | CPU time |
Every figure excludes database, authentication, email, image optimisation and ISR writes. For identity costs, see our companion Auth0 vs Clerk vs Amazon Cognito pricing comparison.
Decision table: choose X if
| Choose | If this describes you |
|---|---|
| Vercel Pro | You want native Next.js support with no adapter layer, and you have few deploying developers or can make most collaborators free viewers |
| Vercel Pro with a paid Flat Rate tier | Your traffic is application traffic, not media downloads, and your on-demand CDN lines would cost more than the tier |
| Netlify Pro | Many people need to deploy, bandwidth is modest, and you prefer a hard credit ceiling to automatic overage |
| Cloudflare Workers Paid | Traffic or bandwidth is high, cost per request matters most, and you can test your app on vinext or OpenNext before each Next.js upgrade |
| Cloudflare Pages | Your site is a static export with no server rendering |
| An Enterprise contract | You need SCIM, a contractual uptime SLA or, on Netlify, payment other than by card |
US and UK notes: tax, currency and data transfers
Currency. All three list prices in US dollars, so UK teams should budget an exchange-rate margin.
UK VAT. Vercel began collecting VAT from international customers on invoices issued from 1 April 2026. VAT-registered UK businesses should enter their GB-prefixed VAT number as a United Kingdom VAT number in billing settings, and may then need to account for VAT themselves under the reverse charge. Check Netlify and Cloudflare invoices for the same treatment.
US sales tax. Vercel already collects sales tax where it is registered and says customers with California or Colorado billing addresses will see sales tax from 1 January 2027, while noting that final state regulations are not yet published. The state changes are California's Senate Bill 122 (Stats. 2026, Ch. 23), which brings digital products, including remotely accessed ones, into sales and use tax from that date, and Colorado's House Bill 26-1223, which makes most computer software taxable from the same date whether it is delivered on disc, by download or by remote access. Both laws apply to sellers generally, so other vendors' invoices may change too; ask your tax adviser.
UK data transfers. All three companies are US-based. Since 12 October 2023, the Data Protection (Adequacy) (United States of America) Regulations 2023 let UK organisations send personal data to US organisations certified under the UK Extension to the EU-US Data Privacy Framework without extra safeguards. Vercel's pricing page lists the EU-U.S. DPF; confirm each vendor's UK Extension listing before relying on it.
Migration and cost-control checklist
- Export 90 days of usage and model it in each vendor's units, including build CPU minutes.
- On Vercel, move collaborators who never deploy to free viewer seats and check deployment retention, which now defaults to 30 days on Pro; our note on Vercel Deployment Storage billing explains the two storage meters.
- On Netlify, decide deliberately whether auto recharge is on. Off means a paused site when credits run out.
- On Cloudflare, set per-Worker CPU limits and log sampling before 1 December, and run
npx vinext checkon a branch.
- Patch before you move. Our note on the Next.js 16.4.5 security release explains how exposure differs between Vercel, Netlify and self-hosted deployments.
- Re-run the model after one full billing cycle on the new platform and compare it with the invoice, not the estimate.
How eCorpIT can help
eCorpIT is a Gurugram-based technology organisation, founded in 2021, assessed at CMMI Level 5 and MSME certified, with senior-led engineering teams working across AWS, Microsoft and Google platforms. Our cloud computing services team can model your hosting bill from real usage exports and set up spend controls, log sampling and CPU limits before traffic moves. Talk to us at /contact-us/.
Last updated: 12 November 2026.