Vercel changes default build billing for new Pro and Enterprise teams

- Reading
- 4 min
New Pro and Enterprise teams at Vercel lose the free Standard build slot and start paying per minute, under the same model already used for Performance machines.
Vercel has changed how it bills for the default build on new teams under the Pro and Enterprise plans. According to the company's official changelog, teams created from now on no longer get a free Standard build slot: this machine type now falls under the same usage-based billing model that already applied to Performance machines.
In practice, this takes away from the Pro plan a benefit that had been part of its value proposition since the beginning: running the production build without worrying about the clock. Now, every minute counts.
What changes on the bill
Under the Pro plan, builds on Standard machines now cost $0.014 per build minute. The monthly usage credit already included in the plan applies to this consumption, so teams with low deploy traffic are unlikely to notice a difference. Enterprise contracts follow whatever terms have already been negotiated.
Before this change, the Standard machine was, for practical purposes, the "free" build included in Pro: you only paid per minute if you chose the Performance machine, which is faster and more expensive. Now both machine types follow the same logic: you pay for what you use, and the plan's credit determines whether that comes out of your pocket or not.
Who is affected for now
The changelog is specific: the change applies to new Pro and Enterprise teams. This suggests existing accounts remain under the previous model, at least for now, but Vercel doesn't detail a transition timeline or confirm whether this will be extended later. Anyone thinking about creating a new team on Vercel for a Next.js project starting today goes straight into the new rules.
It's worth checking the build machine type configured in Team Settings or the project settings: that's where you can see whether the team is running on Standard or Performance, and track consumption in the account's usage tab.
Elastic, Standard, and the fine print
The changelog includes a caveat that's easy to miss: teams affected by the change keep getting billed for builds on Standard machines even after switching the build concurrency model from Elastic to Standard. In other words, switching the concurrency model (which controls how many builds run in parallel) isn't a way to escape per-minute billing: what determines the cost is the machine type used for the build, not the concurrency policy chosen.
This distinction matters because teams with multiple preview branches, frequent PRs, and large monorepos tend to run builds in parallel quite often, regardless of whether they're on Elastic or Standard concurrency.
What this means for anyone maintaining a Next.js app
For teams deploying Next.js on Vercel, builds happen all the time: every push to a feature branch, every PR preview, every production deploy triggers a build job. In projects with active CI, this easily adds up to dozens of builds a day. With usage-based billing applying from the very first minute for new teams, this volume of builds now shows up on the invoice in a way that used to stay hidden behind the included slot.
In short: the real impact depends on the team's profile. For a personal project or a small team with few deploys per week, the Pro plan's monthly credit will likely cover consumption without generating a noticeable extra cost. For a team with a heavy CI pipeline, a monorepo with multiple Next.js apps, and a culture of preview deploys on every PR, however, the cost of builds stops being invisible.
How to reduce the impact in practice
A few approaches help contain build minute consumption, without giving up the preview deploy workflow that makes Next.js shine on Vercel:
- Review build caching: make sure
node_modulesand the Next.js cache (.next/cache) are being reused between builds, instead of reinstalling dependencies from scratch on every push. - In monorepos, use remote caching from tools like Turborepo to avoid rebuilding packages that haven't changed.
- Review
postinstallscripts and unnecessary build steps that inflate each job's runtime without adding value. - Periodically monitor the team's Usage tab, instead of only checking the invoice at the end of the month.
- Evaluate whether every branch really needs to trigger an automatic preview deploy, or whether some workflows can be restricted to manual deploys.
None of these measures are exclusive to Vercel: they're practices worth adopting regardless of build billing, because faster builds also mean faster feedback in the team's day-to-day work. But with Standard builds becoming a direct cost item for new teams, optimizing this step stops being just a productivity matter and starts showing up on the infrastructure cost spreadsheet.
Anyone evaluating where to host a new Next.js project now has one more factor to weigh: the cost of builds is no longer a detail buried in the fine print of the Performance plan, it now applies, right from the first line of the changelog, to any team that just got started on Vercel.
Translated from the Brazilian Portuguese original · Read the original
Vercel puts Priority Projects into public beta for teams running Next.js in production
The paid add-on identifies real bots, labels suspicious traffic, and blocks unapproved scripts using CSP, without adding any client-side JavaScript.





