Commercial transition
Previous stateTeams selected the build-machine type through team or project settings for subsequent deployments.
→New statePro and Enterprise teams can select Turbo for one deployment through the CLI, a Git integration commit marker or the deployment API without changing the project default.
Who is affected
Vercel Pro and Enterprise teams that need Turbo build capacity for selected deployments rather than every deployment in a project.
Action required
Use the supported per-deployment selector only for builds that need Turbo capacity and account for the plan's build-machine usage model.
Evidence boundary
The source proves per-deployment selection of Turbo build machines. It does not change the published Turbo unit price, make Turbo available to Hobby, or change a project's default setting.
Timeline
- Per-deployment Turbo selection introduced
Vercel added supported ways to request a Turbo build machine for a single deployment.
Official sources
- Turbo build machines can now be enabled per deploymentVercel · 2026-09-17 · Official Vercel build-machine feature and entitlement authority