Samuel Arendt

Vercel now bills Standard builds per minute on new Pro and Enterprise teams

On November 17, 2026, Vercel announced that new Pro and Enterprise teams no longer get a Standard build slot included in the plan. From that date, Standard builds on those teams move to the same usage-based billing as the other build machines. On Pro, the price is $0.014 per build minute, drawn from the monthly credit while it lasts. On Enterprise, the contract rate applies.

The announcement also closes an obvious workaround: for teams covered by the change, switching from the Elastic machine to Standard does not make builds free again. Standard builds stay billable.

What a build minute costs now

The Standard machine has 4 vCPUs and 8 GB of memory. Vercel's pricing table bills builds per CPU minute, starting at $0.0035, and the $0.014 per minute for Standard matches those four vCPUs. Billable duration adds the build and post-build steps and is rounded up to the next whole minute, so a 2 minute 10 second build counts as 3 minutes.

Pro includes $20 of credit per month, which applies to every infrastructure resource from the first unit used. By my math, if nothing else consumed that credit, it would cover about 1,400 minutes of Standard builds. In practice, functions, data transfer and requests draw from the same balance, and anything beyond it is billed on demand.

New teams use Elastic machines by default. With Elastic, Vercel picks between 4 and 30 vCPUs based on each project's history, and a heavy build can move up to a larger machine, with a proportional cost per minute.

Who feels the change

The announcement refers to new teams and mentions no change or date for existing ones. If you already run a Pro team, the published text gives you nothing to change right now.

The change weighs more on whoever creates teams often. An agency that opens one Pro team per client, or a company that splits products across teams, now pays for builds from the first deploy on each new team. Projects with many previews per day feel it sooner, because every push to a branch triggers a billed build.

This fits the same decision I discussed in Fixed CDN pricing still depends on the usage tier: a Vercel invoice is increasingly a sum of per-team usage lines, and the budget for a new client has to account for them before the contract is signed.

What to check before opening the next team

Three checks help estimate the bill for a new team:

  1. Measure the billable duration of current builds. The dashboard shows the CPU minutes of each deployment, and vercel inspect (CLI 59.23.1 or later) lists the duration and the vCPUs used. Build Diagnostics shows which step takes longest.
  2. Cut previews nobody reviews. On the same day, Vercel shipped an Ignored Build Step preset that only builds previews for branches with an open pull request. On GitHub and GitLab projects, skipped previews are canceled before they consume CPU minutes.
  3. Set spend alerts on the new team before the first deploy, so usage beyond the credit shows up early.

What the announcement leaves open

The text does not say whether existing teams will move to the same model, or when. It also does not define what counts as a new team: it is unclear whether a Hobby team upgraded to Pro after November 17 falls under the rule. The Hobby plan is not mentioned. If your budget depends on that answer, ask Vercel support and keep the reply in writing.

If your company is weighing something similar, reach me on LinkedIn or WhatsApp.

References

Yellow construction crane with its jib extended horizontally against a clear sky

Photo by Alexander Abero on Unsplash

#Operations, #Radar, #Strategy