Compare

Cloudflare Workers vs Vercel in 2026: Pricing for Real Apps

Cloudflare Workers bills by requests and CPU time, Vercel by seats and usage. Here's how the two price the same app, with every number sourced and dated.

By Engineer Foodie Desk Oct 22, 2026 ✓ Sources checked Oct 22, 2026

7 min read

Prices checked Oct 22, 2026 on Cloudflare’s Workers pricing docs, Cloudflare’s Next.js guide and Vercel’s pricing page. No affiliate links on this page (how we work).

Short version: Cloudflare Workers charges your account $5 a month and then meters requests and CPU time, with bandwidth free. Vercel charges $20 per developer seat on Pro, gives you $20 of usage credit, and meters functions, CPU, memory and (unless you take the Flat Rate CDN) traffic.

So the cheaper one depends on two things: how many people deploy, and how much traffic you push. A solo dev with a busy API leans Workers. A team that wants the Vercel workflow and predictable CDN bills leans Vercel.

We haven’t run the same app on both, so there’s no benchmark here and no made-up monthly bill. We explain each billing model with the vendors’ own numbers. Plan lists live on our Cloudflare price tracker and Vercel price tracker.

TL;DR

Pick Workers if:

You’re one person or a small team, and you don’t want to pay per seat.
Your app moves a lot of bytes. Workers has “no additional charges for data transfer (egress) or throughput (bandwidth).”
Your code is light on CPU per request.

Pick Vercel if:

You don’t want your Next.js app to depend on Cloudflare’s beta route (its recommended adapter, vinext, “is in beta”).
You want a dollar budget that can pause projects automatically.
You’d pay for a fixed CDN bill with “No overages” (Pro’s Flat Rate CDN, price not on the pricing page).

Plans at a glance

Plan	Workers	Vercel
Free	$0, 100K requests/day	Hobby $0, non-commercial
Paid entry	$5/mo per account	Pro $20/mo per developer seat
Included (paid)	10M requests, 30M CPU ms	$20 usage credit
Requests	$0.30 per extra 1M	Functions from $0.60 per 1M
CPU	$0.02 per extra 1M CPU ms	From $0.128 per active CPU hour
Bandwidth	No egress charge	Flat Rate CDN on Pro
Spend cap	Per-request CPU limit	$200 default budget, optional pause

Sources: Workers pricing and Vercel pricing, both verified Oct 22, 2026. Vercel’s rates are listed as “Starting at”, with regional pricing, in USD excluding VAT/GST.

How each one bills

Workers: requests plus CPU milliseconds

On Workers Paid there’s a “minimum charge of $5 USD per month for an account”. On the Standard usage model you get “10 million included per month +$0.30 per additional million” requests, and “30 million CPU milliseconds included per month +$0.02 per additional million CPU milliseconds”. Duration, meaning wall-clock time spent waiting on a database or an API, has “No charge or limit” (Workers pricing, Oct 22, 2026).

Other lines that matter for real bills:

“Requests to static assets are free and unlimited.”
“Cloudflare does not bill for subrequests” (your Worker calling other services).
CPU per invocation maxes out at 5 minutes, with a 30-second default.
Workers Logs: 20 million included per month, then $0.60 per additional million.

Cloudflare’s own worked example uses 15M requests a month at 7 ms of CPU each: the $5 base, plus 5M extra requests at $0.30 per million, plus (105M − 30M) CPU ms at $0.02 per million. See the pricing page for the full calculation. Billing in CPU milliseconds is basically Tetris: every millisecond-shaped block you don’t waste is money you keep.

Vercel: seats plus a usage credit

Vercel Pro is “$20 / month” per developer seat. Viewer seats are “Unlimited” and free, and Pro comes with one billing seat. Each Pro plan includes “$20 of included usage credit”, and “On top of your included credit on Pro, you can pay as you go, uncapped” (Vercel pricing, Oct 22, 2026).

The usage rates on Pro, all “Starting at”:

Function invocations: $0.60 per 1M
Fluid Active CPU: $0.128 per hour
Fluid Provisioned Memory: $0.0106 per GB-hour
Fast Data Transfer and CDN requests: “Included in Flat Rate CDN”

That last line is the big change. Flat Rate CDN lets you “Pay a fixed amount for Vercel CDN each month, regardless of traffic and usage”, with “No overages: Your bill will never increase because of temporary usage spikes.” What it doesn’t do is tell you the fixed amount. The pricing page links to separate docs for that, so check current price there before you budget.

“Starting at” and “regional pricing” on a pricing table is pure Veep: technically true, carefully worded, and you’ll only learn the real number after the vote.

Putting the CPU rates side by side

Converting the published rates to the same unit: Workers’ $0.02 per million CPU ms works out to $0.072 per CPU hour (3.6M ms in an hour), after the 30M ms included. Vercel’s Fluid Active CPU starts at $0.128 per hour. But Vercel also bills provisioned memory and invocations separately, and Workers bills requests. So don’t read that as “Workers is 44% cheaper”. It’s one line of the bill, not the bill.

Free tiers and their limits

Workers Free: “100,000 per day” requests, “No charge for duration”, and “10 milliseconds of CPU time per invocation”. That’s about 3M requests over a 30-day month, but the cap is daily, so a spike day can hit it.

Vercel Hobby: “Our Hobby plan is for personal, non-commercial use.” Included each month: 1M function invocations, 4 hours of Fluid Active CPU, 360 GB-hours of provisioned memory, 100 GB of Fast Data Transfer and 1M CDN requests. And “If you have a free Hobby account, you are limited to the usage caps and cannot purchase additional usage.”

The honest read: Hobby is for side projects that make no money. If your app earns anything, Vercel’s own wording points you to Pro. Workers Free has no such line in the pricing docs we read, but its 10 ms CPU cap per request is tight for heavy server-side rendering.

Next.js and framework support

Cloudflare’s docs: “Cloudflare recommends vinext as the default way to run Next.js applications on Cloudflare Workers.” vinext “is a Vite plugin that reimplements the Next.js API surface”, and you can add it “to an existing Next.js 16 app with a single non-destructive vinext init”. The support table lists App Router, Pages Router, RSC, Server Actions, SSR, static export, ISR and middleware. “next/* imports” are “Mostly supported” and image optimisation is “Partially supported”. And, in Cloudflare’s words, “vinext is in beta” (Cloudflare Next.js guide, Oct 22, 2026).

OpenNext is still listed for people who “maintain an existing OpenNext application that cannot yet migrate to vinext because of a compatibility gap.”

So yes, Next.js runs on Workers, through a reimplementation that’s in beta. If your app leans on image optimisation or unusual next/* imports, test before you move. For Vercel, we only checked the pricing page for this piece. Pro lists “Cold start prevention”, but we’re not making framework claims beyond that.

Teams: seats and spend controls

Seats. Vercel prices Pro by developer seat at $20/month, with free viewer seats. The Workers pricing page prices the account ($5/month minimum) and doesn’t list per-seat charges. If five developers deploy, that’s $100 a month on Vercel before usage, versus the $5 Workers minimum before usage.

Spend controls. Vercel: “Set a limit, get alerts, and we’ll stop usage before you go over budget.” “All new teams have a default on-demand usage budget of $200 (which can be customized)”. You get email, web and SMS alerts, and at 100% “you can optionally configure Vercel to automatically pause all projects with a hard limit.”

Cloudflare’s pricing page offers a different kind of guard: “To prevent accidental runaway bills or denial-of-wallet attacks, configure the maximum amount of CPU time that can be used per invocation.” That’s a cap per request, not a dollar cap. The page doesn’t state a dollar spend cap for Workers. When a bot storm hits at 3 AM, who you gonna call? On Vercel, the budget pause. On Workers, the CPU limit you set beforehand, plus the fact that bandwidth isn’t billed.

Here’s what I’d do

Solo, or a tiny team, building an API or a mostly static site? I’d start on Workers Paid at $5. Bandwidth isn’t billed and static assets are free, so the classic “my post went viral and my host sent an invoice” story mostly goes away. Set the per-invocation CPU limit on day one.

A team shipping a big Next.js app that leans on image optimisation? I’d stay on Vercel Pro until vinext leaves beta, set the spend budget to a number you can live with, and ask Vercel for the Flat Rate CDN price before you scale.

Comparing more hosts? Our Netlify price tracker, Railway price tracker and Render price tracker list their plans with dates.

For the database layer, see Supabase vs Firebase free tier.

FAQ

Is Cloudflare cheaper than Vercel? Often for solo devs and bandwidth-heavy apps ($5/account and no egress charge vs $20/seat), but it depends on seats, CPU and traffic, so price your own usage.

Can I run Next.js on Workers? Yes, Cloudflare recommends vinext (in beta) as the default way, with OpenNext still listed for existing apps.

Workers vs Pages? We didn’t check Pages for this piece; Cloudflare’s Next.js guide now points to Workers with vinext.

Workers vs Railway? We didn’t price Railway for this piece; check current price on Railway’s pricing page or our Railway price tracker.

Sources

Cloudflare Workers pricing (Free, Paid, CPU, requests, egress, static assets, subrequests, logs, CPU limits, worked example): https://developers.cloudflare.com/workers/platform/pricing/ (verified 2026-10-22)
Cloudflare Next.js on Workers guide (vinext, OpenNext): https://developers.cloudflare.com/workers/framework-guides/web-apps/nextjs/ (verified 2026-10-22)
Vercel pricing (Hobby, Pro seats, usage rates, Flat Rate CDN, spend management FAQ): https://vercel.com/pricing (verified 2026-10-22)