Vercel Shows the CPU-Minute Math Behind the Surprise Bills

Vercel now shows the billable duration and CPU minutes behind every deployment, in the dashboard, the vc inspect CLI command and the REST API (Vercel changelog, Sept. 21, 2026). Billable duration is a build’s combined build and post-build time, rounded up to the next whole minute; CPU minutes multiply that duration by the machine’s vCPU count, so a 9-minute build on a 30-vCPU machine reads as 270 CPU minutes. The CLI figure requires vc 59.23.1 or later.

Why now

The number lands five months into a running dispute in the Vercel Community forum over exactly this math. A Pro account holder posted on Sept. 12, 2026, that support case #01BTdgkqgjXDKcBG had gone three days without a reply on a $1,865.42 charge, 933% over their $200 Spend Management cap. The cause: their project’s build machine had silently defaulted to Turbo, Vercel’s 30-vCPU tier, billed at $0.105 per CPU minute against Standard’s $0.014, a 7.5x multiplier. Builds that finished in 20 to 30 seconds still billed as full minutes across all 30 cores.

That default isn’t new. A separate thread dated April 1, 2026, described an unrelated Pro account hit with a $659.72 Build Minutes charge with no opt-in and no warning. A Vercel community moderator, Pauline P. Narvas, confirmed the root cause at the time: “This appears related to the recent change where Turbo build machines became the default for Pro accounts.” Vercel refunded that charge but didn’t say the default would change, telling the account holder instead to switch machines manually or set spend-management alerts. Both remedies require knowing to look, which is precisely what a build that finishes in under a minute doesn’t prompt anyone to do.

What the new number does, and doesn’t, fix

Surfacing billable duration and CPU minutes in the dashboard and API gives a team the exact inputs to that multiplication before an invoice does it for them. Anyone auditing usage can now see a build’s vCPU count and duration side by side, instead of reverse-engineering a line item after the fact, which is what both community threads above had to do.

It doesn’t touch the setting that produced the surprise in the first place. Turbo and Elastic build machines still default on for Pro accounts without a notification or confirmation step, so a project can accumulate CPU minutes at 7.5x the Standard rate for months before anyone with billing access happens to check. Visibility narrows the gap between “the charge happened” and “someone could have caught it,” but it’s still an opt-out cost sitting behind a default most account holders never chose.

Key Takeaways

• Vercel now shows billable duration (build plus post-build time, rounded up to the minute) and CPU minutes (duration times vCPU count) per deployment, effective Sept. 21, 2026.
• Turbo build machines, Vercel’s 30-vCPU tier, bill at $0.105 per CPU minute versus $0.014 on Standard, a 7.5x multiplier, and have defaulted on for new Pro projects since around April 2026.
• A Sept. 12, 2026 community case put a Pro account $1,865.42 over its $200 spend cap after builds that ran 20 to 30 seconds billed as full CPU minutes across 30 cores.
• The new figures make the math auditable. They don’t change the default machine tier or add a confirmation step before Turbo billing starts.