Vercel Now Budgets Every Project, and Still Only for Paying Teams

Two providers shipped spending caps within three days of each other. Both of them aimed the feature at the accounts already paying.

Share
Vercel Now Budgets Every Project, and Still Only for Paying Teams

Vercel added project and product budgets to Spend Management on 16 November 2026. A project budget can halt deployments for that one project at the limit while every other project keeps shipping, and a product budget tracks a line item like Fast Data Transfer across the whole team. Notifications fire at 50%, 75% and 100% of each budget. Spend Management is included at no additional cost for Pro teams and Enterprise teams on Flexible Commitment plans.1

Read the last sentence twice, because it is the whole story for anyone on the free plan. The feature is maturing quickly and the eligibility has not moved an inch.2

What the new budgets do

Budget scopeBehaviour
TeamTracks total team spend, can pause production deployments
ProjectTracks one project, can pause that project's production deployments alone
ProductTracks one product across the team, no automatic pausing
Notifications50%, 75% and 100% of each budget
EligibilityPro teams and Enterprise on Flexible Commitment
CostNo additional charge, bundled with the plan

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 project scope is the meaningful addition. Halting one project while the rest of the team keeps shipping is the difference between a control you can leave switched on and one that turns an overrun into a company-wide outage.

Product budgets deliberately cannot pause anything. They report across the team, which suits a line item like data transfer that no single project owns and where pausing would be arbitrary. That asymmetry is a considered design choice rather than an omission.

Everything is scriptable. There is a CLI for listing budgets, setting a project budget with a pause flag, and setting a product budget, so an environment can be provisioned together with the guardrail that protects it.

The three-day pattern

This landed three days after Cloudflare shipped Spend Management in beta. Cloudflare's version is pay-as-you-go only, capping Workers and Durable Objects, and it leaves free accounts with alerts and no brake. Vercel's is Pro and above, which means a Hobby team has no spending control at all.

ProviderFree plan can cap spend?What happens at the limit
VercelNo, Pro and aboveProduction deployments can pause
CloudflareNo, pay-as-you-go onlyCost-incurring invocations are rejected

According to both changelogs, these are two competitors three days apart, both shipping the single most useful billing feature a free tier could offer, and both confining it to accounts that already pay. That is a converged position across the market, not an oversight at one company, and it tells you something about how the free tier is now being valued.

Our advice is to stop expecting the cap to arrive on the free plan. Hobby's protection is that Vercel refuses the dangerous configuration at deploy time, which is a blunter instrument that works precisely because the expensive shape cannot exist. That is the model to rely on, and it is the reason the paid cap matters less than it appears.

Why the free tier is excluded

The logic is consistent if unsentimental. A budget is a control on metered spend, and a plan with no metered spend has nothing to budget. Vercel's Hobby tier is designed so that most usage stops rather than bills, and its failure mode is a deployment that quietly fails to ship, and no invoice follows.

The gap appears the moment a Hobby team upgrades. The first days on a paid plan are exactly when nobody has configured a budget, and it is exactly when the failure mode changes from a blocked deploy to an open meter. Spending caps are worth most at the moment of transition, and that is the moment no product currently covers by default.

We checked both providers' documentation side by side, and the caveat to note before relying on this is the scoping of the pause. Only team and project budgets can pause production deployments. A product budget that reaches 100% tells you the data transfer bill is enormous and then watches it continue, so a team that sets only a product budget has configured an alert and no brake.

What counts toward a project budget

A project budget tracks spend attributable to that project, which is a narrower set of line items than the team total. Infrastructure that is metered per deployment or per request lands on the project. Anything shared across the team, such as a pooled product line, does not, which is why product budgets exist as a separate scope instead of being folded into the project view.

That split is worth understanding before a team sets both and assumes they add up to the team budget. They do not, and a project budget that sits reassuringly below its limit can still coexist with a product line quietly overrunning.

The pause applies to production deployments only. Preview deployments are not mentioned, and a paused project does not stop serving traffic that is already live. It stops the next production deployment from shipping, which is a graceful way to halt a bad situation and a poor way to stop a runaway runtime bill, since the running code continues to run.

Where this sits for a free team

Nothing in this release changes a Hobby team's options. There is a free project budget feature in the sense that the dashboard now has a page to visit, and it is a page a Hobby team cannot use.

When we compared the two offerings, the detail that mattered was not the pause behaviour but the eligibility line on both pages, which is identical in substance and phrased politely enough that it looks like a limitation rather than a decision. The verdict is that this is a well-built control for a paying team and a non-event for a free one, and the trade-off is intentional. Best for Pro teams running several projects with one shared bill; not ideal for anyone evaluating on Hobby and expecting to grow into a guardrail.

Frequently asked questions

Can a Hobby team set budgets in Spend Management?
No. It is included for Pro teams and Enterprise teams on Flexible Commitment plans.

Can a project budget pause only that project?
Yes. It can pause that project's production deployments without pausing others.

Can a product budget pause anything?
No. Only team and project budgets support automatic pausing.

When are notifications sent?
At 50%, 75% and 100% of each budget.

Does Spend Management cost extra?
No, it is included at no additional cost for eligible plans.

Can budgets be managed with the CLI?
Yes, with commands to list budgets and set project or product budgets, including a pause flag.

The project and product budget scopes, the pause behaviour, the notification thresholds, CLI support and the Pro and Flexible Commitment eligibility are all from Vercel's changelog entry of 16 November 2026, and the Spend Management documentation, read on 17 November 2026. The Cloudflare comparison uses Cloudflare's announcement of 13 November 2026.

Sources

  1. Vercel Changelog: Project and product budgets: vercel.com/changelog/set-budgets-for-projects-and-products-in-spend-management. Used for: Project and product budgets added 16 November 2026; only team and project budgets pause production deployments.
  2. Vercel Docs: Spend Management: vercel.com/docs/spend-management. Used for: Eligibility is Pro and Enterprise Flexible Commitment; notifications at 50/75/100 percent.

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.