Dora NodaA team called FanVerse posted a support thread in April describing a bill they didn't understand: over $10 in charges for fewer than 100 deployments, on a project that had shipped hundreds of free builds before without costing a cent. A Vercel staffer's answer took one line to diagnose: the project was building on "Turbo," and Turbo "would use resources a lot more quickly than the Standard option." Nobody on the team had chosen Turbo. It had simply become the default.
That default flip happened on February 3, 2026, when Vercel made Turbo build machines — 30 vCPUs, 60GB of memory — the default for every new Pro project and every Hobby-to-Pro upgrade. It's a genuinely faster machine: Vercel's own numbers put it at up to 30% faster for builds under 2 minutes, up to 50% faster for 2–10 minute builds, and up to 70% faster for anything longer. It's also, as of that same date, a metered one. Standard build machines are only billed when you turn on paid concurrency or pick Elastic — left alone, a Standard build is bundled into the flat Pro seat fee, the same "it just builds, don't think about it" experience Heroku-era PaaS billing trained a generation of developers to expect. Turbo carries no such exemption. Every CPU-minute is billed from the first build, whether or not you asked for the faster machine.
Here's what that line item actually costs a monorepo team a month, what changed since the $0.126/minute figure that made the rounds in February, and where a self-hosted build layer with no per-minute meter actually pays for itself — and where it doesn't.
How the meter works
Vercel's build pricing collapses to one formula, documented on the pricing page: build duration, rounded up to the nearest minute, times the machine's vCPU count, times $0.0035. A 2-minute-34-second build on an 8-vCPU Enhanced machine rounds to 3 minutes, times 8 vCPUs, times $0.0035 — $0.084 for that one build.
Run that formula across all three tiers:
| Machine | vCPUs | Memory | Price / minute | Billed by default? |
|---|---|---|---|---|
| Standard | 4 | — | $0.014 | No — only with concurrency or Elastic |
| Enhanced | 8 | 16GB | $0.028 | Yes |
| Turbo | 30 | 60GB | $0.105 | Yes — and now the default |
The Turbo price wasn't always $0.105. Vercel cut it 16% on April 27, 2026, from $0.126 to $0.105 per minute — which means the number in most February and March writeups (including the one that likely put this exact figure in your head) is already stale. The old $0.126/minute worked out to $0.0042 per vCPU-minute, a real premium over Standard and Enhanced's $0.0035. The cut didn't just make Turbo cheaper — it erased that premium entirely. Post-cut, all three tiers bill the identical $0.0035 per vCPU-minute; the only thing separating them now is raw CPU count, and how much that parallelism actually shortens your wall-clock build time.
So the honest framing isn't "Turbo got a price cut." It's "Turbo's per-CPU rate now matches every other tier's, and since Turbo has 7.5x the CPUs of Standard, a Turbo build costs 7.5x more per minute of build time it uses — partially offset by finishing in a fraction of the minutes."
What that costs a real monorepo team
Take Northwind, a team of five shipping a Turborepo-managed monorepo — a marketing site, a dashboard, and an API — on Vercel Pro. Between preview deployments on every pushed commit and production deploys on every merge, a team this size typically triggers somewhere around 450 builds a month. Their largest app falls in Vercel's "over 10 minutes" bucket: roughly 12 minutes on a Standard machine, cut to about 4 minutes on Turbo.
| Scenario | Cost per build | Builds / month | Build-machine cost |
|---|---|---|---|
| Standard, sequential (no concurrency) | $0 (bundled) | 450 | $0 |
| Turbo, pre-cut rate (Feb–Apr 2026) | 4 min × 30 vCPU × $0.0042 = $0.504 | 450 | $226.80 |
| Turbo, current rate (post Apr 27, 2026) | 4 min × 30 vCPU × $0.0035 = $0.42 | 450 | $189.00 |
Three things worth sitting with. First, the April price cut is real money — the same 450 builds cost $37.80 less a month than they did in March, just because Vercel adjusted a rate, with zero change to the team's code or CI configuration. Second, $189 a month is on top of the $100/month five-seat Pro fee, not instead of it — it's a pure add-on that didn't exist as a line item before the default flipped. Third, and the part the "just switch to Standard" advice glosses over: Standard isn't free in wall-clock time. That same 450 builds at 12 minutes each is 5,400 minutes — 90 hours — of CI queue time a month, against 1,800 minutes (30 hours) on Turbo. The $189 is buying back roughly 60 engineer-facing hours of waiting. That's a real trade, not a tax with no counterpart — which is exactly why the next question is what it costs to get that same speed without a meter attached.
Checking which machine your builds are actually on
None of this requires guesswork about your own account — Vercel's dashboard shows it directly under Project Settings → Build & Deployment → Build Machine, and every invoice line item for builds is labeled "Build CPU Minutes" so it's separable from bandwidth or function costs. If a project was created or upgraded to Pro on or after February 3, 2026 and nobody has touched that setting, it's on Turbo by default, billing from the first build. Dropping it to Standard costs nothing extra as long as on-demand concurrency stays off — the trade is exactly the wall-clock difference in the table above, not a hidden second fee.
The self-hosted side: one box, no meter
A self-hosted build layer — a buildpack or Dockerfile pipeline running on hardware you own — doesn't bill per CPU-minute at all. It bills for the box, flat, regardless of how many times you build in a given month. Sized against Vercel's own tiers, a Hetzner CCX23 (4 dedicated vCPU, 16GB RAM) — roughly Standard-class — runs €85.99/month post-Hetzner's own June 15, 2026 price adjustment, about $93 at current exchange rates. Step up to a CCX33 (8 dedicated vCPU, 32GB RAM, Enhanced-class) and it's €138.49/month, about $150.
Two caveats worth putting on the table rather than waving off, since a self-hosting pitch is only as good as its weakest number. First, Hetzner isn't frozen in time either — that June adjustment raised CCX/CPX pricing 113–175% over what these same boxes cost a year ago; the $93 and $150 figures already have that hike priced in, not a pre-hike number that flatters the comparison. Second, "self-hosted" isn't automatically meter-free if you route it through someone else's control plane: GitHub added a $0.002-per-minute platform charge to self-hosted Actions runners in private repos starting March 2026, which covers job orchestration regardless of whose hardware the job actually runs on. At 450 builds and roughly 4 minutes each, that adds about $3.60/month — trivial next to $189, but it means "self-hosted on GitHub Actions runners" and "your own build layer with no external control plane" aren't the identical claim, and the number that actually gets you to zero incremental meter is the latter.
Where the crossover actually sits
Compare a dedicated CCX33 build box ($150/month flat) against Turbo's current $0.42-per-build rate, and the breakeven is about 357 builds a month — roughly 17 a workday across a 21-day month. Below that volume, paying Vercel's meter costs less than provisioning a box you'd otherwise have no use for. Above it, the flat box wins, and the gap only widens as build volume grows, because Hetzner's price doesn't move with usage and Vercel's does.
The Northwind-style team above, at 450 builds a month, is already past that line: $189 metered versus $150 on a dedicated box, before counting that the box also has no upper bound on how many builds it can absorb in a busier month. And that $150 figure is the pessimistic case — a box provisioned solely for CI. The sharper version of the same math: if the build layer runs on the same always-on machine that's already serving the app in production — which is how a platform like Bex.co is designed to work, deploying straight from a git push onto infrastructure you already operate — there's no dedicated box to break even on at all. The build queue shares idle capacity on hardware that's a sunk cost either way, and the marginal price of the 451st build that month is zero.
The pattern to watch
This is the third time in as many months this list has found a hosted PaaS unbundling a cost that used to be folded into the flat plan fee: bandwidth, then AI-agent invocations, now build minutes. Standard machines still ship free-by-default today, but so did Turbo's predecessor tier before parallel builds became worth metering separately. The build-minute meter didn't replace anything — it's a new line item on top of the seat fee, activated by a default nobody explicitly opted into. Whatever gets bundled into "just works" pricing this quarter is worth checking again next quarter, because the direction of travel on every metered PaaS so far has been the same: fewer things stay flat, not more.
Bex.co is the open-source, AI-native Render alternative — push a git repo, get a running HTTPS service on machines you own, with no per-minute meter on the build step. Star the repo on GitHub or deploy your first app today.
