Vercel - Costs - Deployments - Founders
3 min lectura

Vercel's new Standard build billing: when PR-only previews make sense

How new Vercel teams can assess Standard build minutes and test PR-only previews without breaking review workflows.

Vercel's new Standard build billing: when PR-only previews make sense

If you just started a Vercel Pro team and every push produces a preview, two November 17, 2026 changes deserve a look. New Pro and Enterprise teams no longer get an included Standard build slot; Standard builds move to usage billing. At the same time, Vercel added a preset that skips previews for branches without an open pull request. The founder's decision is which builds actually help someone review the product.

What changed in billing

Vercel says the Standard change applies to new Pro and Enterprise teams starting November 17. On Pro, Standard builds cost $0.014 per build minute, and the monthly usage credit applies. Enterprise rates follow the contract. For teams covered by the change, switching from Elastic back to Standard does not make Standard free. The announcement does not say that every existing team has lost a previous allowance. Check your team creation date, plan, and billing page before changing a workflow.

For scale, 100 previews taking three minutes each would consume 300 build minutes, or $4.20 of Standard usage before credits or other adjustments. That is arithmetic using the posted rate, not a measured invoice. Your real build duration, machine selection, and other usage determine your bill. Inspect your own Usage page for a meaningful baseline.

What the PR-only preset does

The new Ignored Build Step preset is called Only build previews for pull requests. On projects connected to GitHub or GitLab, Vercel cancels previews for branch pushes without an open PR before they consume Build CPU Minutes. Production deployments and previews for branches with open PRs still build. You can find it under Deployments → Configuration → Ignored Build Step → Behavior in the project settings.

This is a fit for a team that opens a PR when a feature is ready for review. It can be a poor fit if designers, customers, or copy reviewers depend on preview links before the PR exists. The preset decides whether to build; it does not create a review process. Map who needs each preview and at what stage before enabling it across projects.

Comparison of which previews build under the PR-only preset
Diagram of Vercel's announced behavior.

A useful test this week

  1. In Billing and Usage, confirm whether your team is covered, which build machine each project uses, and the build minutes consumed last week.
  2. Separate production, open-PR previews, and branch previews without a PR. Measure minutes spent on the last category; commit count alone is not an estimate of savings.
  3. Enable the preset on a secondary GitHub or GitLab project. Push to a branch without a PR and check that the preview is canceled. Then open a PR and verify that the preview builds.
  4. Ask design and content reviewers if they need a link before a PR. Keep the previous flow or open PRs earlier if they do.

The goal is to pay for previews that support a real review and stop building links nobody opens. SoyJB reviewed both official announcements and prepared the test, but did not change a live Vercel account or measure actual savings. Pricing and contract terms can differ by team.

Sources

Comentarios

Aún no hay comentarios. Sé el primero.

Deja un comentario