deniz.in

Markets

Weather

Loading weather

· via Vercel blog

Vercel moves Standard builds to usage-based billing for new Pro and Enterprise teams

Vercel's new Pro and Enterprise teams will no longer get an included Standard build slot; Standard builds now cost $0.014 per minute on Pro, charged against the plan's usage credit.

Vercel moves Standard builds to usage-based billing for new Pro and Enterprise teams

Vercel drops the bundled Standard build slot for new teams

Vercel has moved Standard builds to usage-based billing for newly created Pro and Enterprise teams. According to a changelog post on the Vercel blog, published 17 November 2026, new teams on those plans no longer receive an included Standard build slot, and Standard build minutes are now metered in the same way as the platform's other build machine types.

How the new pricing works

On Pro plans, Standard builds are charged at $0.014 per build minute, Vercel says, and the plan's monthly usage credit can be applied to build usage. At that rate, a team consuming 10,000 Standard build minutes in a month would accrue roughly $140 in build charges before any credit offsets it.

Enterprise teams are handled differently: Vercel states that Enterprise rates follow each customer's contract rather than the published per-minute figure.

The changelog also clarifies one edge case: for teams covered by the change, Standard builds remain billable even after switching from Elastic to Standard builds. Moving a project between machine types does not, in other words, create an unmetered path.

Who is affected

The change is scoped to new Pro and Enterprise teams rather than the entire customer base. The changelog does not spell out terms for teams created before the announcement, and it refers only to teams covered by the change when describing the Elastic-to-Standard billing behavior. Teams unsure of their configuration can check which build machine is in use, since Vercel directs users to team settings and project settings to select a build machine, alongside its documentation on managing builds.

Why it matters

Build minutes are one of the quietly compounding costs of running on a managed deployment platform. By removing the bundled Standard slot, Vercel converts what was a fixed, plan-included resource into a variable line item for new customers, bringing Standard builds in line with the metered model already applied to its other machine types.

For engineering teams, the practical consequences are budgeting and configuration. A team spinning up a new Vercel organisation should now model build-minute consumption explicitly — long builds and frequent preview deployments can push minutes up quickly — and confirm which machine type their projects use, because that choice now feeds directly into the bill. The clarification that switching from Elastic to Standard keeps builds billable also removes any assumption that a cheaper or unmetered option exists simply by flipping machine types.

The change also fits a broader industry pattern: platform vendors increasingly prefer pure usage-based pricing over bundled allowances because it maps revenue to underlying compute cost. That is cleaner for the vendor, but it shifts the forecasting burden onto customers, making usage monitoring and spend alerts part of routine operations rather than an optional extra. Existing Vercel teams are not the immediate audience here, but anyone provisioning new environments — or weighing Vercel against alternatives for a fresh project — should fold the new per-minute Standard build pricing into their cost estimates.

  • #vercel
  • #usage-based-billing
  • #cloud-costs
  • #devops
  • #paas

Related posts