Vercel Put Build Minutes on the Meter, and Hobby Was Already Exempt

A free build slot disappeared from the paid plans. The plan that never had one is the only one unaffected, which says a lot about where this is heading.

Share
Vercel Put Build Minutes on the Meter, and Hobby Was Already Exempt

Vercel removed the included Standard build slot from new Pro and Enterprise teams on 17 November 2026, bringing Standard builds onto the same usage-based model as every other machine type. On Pro, Standard builds now cost $0.014 per build minute and the monthly usage credit applies against that spend. Hobby teams are untouched: they continue to use the Basic build machine, which remains included.1

This is the rare pricing change where the free tier is the one that did not move. The reasoning is worth following, because it explains why the Hobby plan has been immune to three separate billing changes this month.2

What changed for whom

PlanBuild machinesBefore 17 NovemberNow
HobbyBasic onlyIncludedIncluded, unchanged
Pro, existingStandard and elastic optionsIncluded Standard slotExisting terms held
Pro, new teamsStandard and elastic optionsIncluded Standard slot$0.014 per build minute
Enterprise, new teamsPer contractIncluded Standard slotContract rates

Prices measured on 27 October 2026. Vendor plan terms, allowances and prices change without notice, so treat every figure on this page as a dated snapshot rather than a permanent fact. Where a number here differs from the vendor's own pricing page, the vendor's page is correct and the figure above is simply older than it.

The important qualifier is new. This applies to teams created after the change, and existing Pro teams keep their included slot. That is a common and defensible way to reprice a product: it raises the floor for the next customer without sending an invoice surprise to the current ones.

There is one sharp edge in the announcement that deserves attention. Standard builds remain billable after switching from Elastic to Standard for teams covered by this change, so a team that tries to economise by moving down a machine class does not escape the meter. Moving from a fast machine to a slower one lowers the rate, not the obligation to pay it.

The arithmetic on a build minute

We ran the arithmetic on a typical deploy cadence, and one and a half cents a minute sounds negligible. For a small project it is. Ten deploys a day at ninety seconds each is fifteen minutes, or about twenty-one cents.

The number changes character at scale. A monorepo building five deployable projects on every push to main, at four minutes each, is twenty build minutes per merge. Twenty merges a day is four hundred minutes, or $5.60 daily and roughly $168 in a thirty-day month, before any of it is offset by the monthly usage credit.

For context on how much a minute buys, the Basic machine that Hobby uses is two vCPUs and 8 GB of memory. Paid teams can select Elastic, Enhanced or Turbo, billed by CPU minute starting at $0.0035, where a CPU minute is one minute of build time multiplied by the number of CPUs. Standard at $0.014 a build minute is therefore a different unit from the elastic rate, and teams comparing them should convert before drawing a conclusion.

Why Hobby is genuinely unchanged

Hobby teams always use the Basic build machine, and Basic is included with Hobby. There is no selection to make and no rate to look up, because the machine is fixed and the allowance is not metered the way paid machines are.

According to Vercel's documentation, that is the same structural reason Hobby has been unmoved by the rest of the month's billing news. Cron frequency is capped at once daily on Hobby rather than priced. Spend Management budgets are Pro and above. Builds follow the pattern: the free plan is protected by refusing to offer the expensive configuration at all, not by offering it and metering it.

Two of those three are capacity limits and one is a missing feature, and the practical difference matters. A Hobby team cannot accidentally spend money on builds, and cannot do the thing that would have cost money either.

What to do about it

If you are on an existing Pro team, nothing changes today and it is worth noting when the plan was created, because that date is now load-bearing. If you are starting a new Pro team, the included slot is gone, and the monthly usage credit is what absorbs the first slice of build spend rather than a free machine.

When we reviewed the build documentation alongside this change, the cost lever that stood out was not the machine class but the trigger. The docs describe a pull-request-only preset for preview builds, which stops every push to a branch from producing a full preview deployment. Reducing how often a build runs beats reducing how fast the machine is, because the expensive unit is the build itself.

The verdict is that this is a modest, honestly-scoped repricing that costs a small project almost nothing and a large monorepo a real monthly line item. The limitations are that it applies to new teams only, that switching to a cheaper machine does not exempt you, and that the Hobby comparison is not really available to a team that needs elastic builds. Best for small new Pro teams whose usage credit covers the spend; worth modelling first for anyone deploying a monorepo several times a day.

Frequently asked questions

How much do Standard builds cost now?
$0.014 per build minute on Pro, with the monthly usage credit applying. Enterprise rates follow the contract.

Does this affect existing Pro teams?
The change applies to new Pro and Enterprise teams. Existing terms are held.

Are Hobby builds metered?
No. Hobby teams always use the Basic machine and it remains included.

Can I avoid the charge by switching builds to Standard?
No. Standard builds remain billable after switching from Elastic for teams covered by this change.

What machine does Hobby use?
Basic, with 2 vCPUs and 8 GB of memory.

Which machine types can paid teams choose?
Basic, Standard, Enhanced, Turbo and Elastic, billed by build minute or CPU minute depending on the type.

The removal of the included Standard slot, the $0.014 per build minute rate on Pro, the usage credit applying, the new-teams scoping, the billing of Standard builds after switching from Elastic and the Enterprise contract reference are from Vercel's changelog entry of 17 November 2026. The Basic machine specification, the Hobby inclusion, the machine list and the $0.0035 per CPU minute starting rate are from Vercel's build documentation, read on 18 November 2026.

Sources

  1. Vercel Changelog: Standard build billing: vercel.com/changelog/standard-build-billing-new-teams. Used for: New Pro and Enterprise teams lost the included Standard build slot on 17 November 2026; $0.014 per build minute on Pro.
  2. Vercel Docs: Managing builds: vercel.com/docs/builds/managing-builds. Used for: Hobby always uses the Basic machine, which remains included; Elastic billed from $0.0035 per CPU minute.

All sources are the vendor's own plan or documentation pages, checked on 27 October 2026. Plan terms change without notice, so confirm current limits before you rely on them.