Why Per-Deployment Build Machines Matter
Every deployment is not created equal. A hotfix on a Friday afternoon, a monorepo build that suddenly balloons past the default memory ceiling, or a one-off migration script — these scenarios don't justify permanently upgrading your project's build machine tier. Yet until now, that was the only lever available.
Vercel's new per-deployment Turbo build machine option flips that model: you get the extra CPU and memory only for the deployment that needs it, then everything reverts to your project defaults. No config drift, no surprise billing on every subsequent push.
This is a small changelog entry with outsized operational impact — especially for teams running cost-sensitive CI pipelines.

Three Ways to Enable Turbo Build Machines
Vercel exposes the same capability through three interfaces. Pick whichever fits your workflow.
1. Git Commit Message (Zero Tooling)
Prepend the environment variable to your commit message before pushing:
# Enable Turbo build machine for this single deployment
git commit -m "#VERCEL_BUILD_MACHINE=TURBO
fix: resolve race condition in auth middleware"
git push origin main
The directive is parsed by Vercel's build orchestrator and applies only to the deployment triggered by that commit. Subsequent commits without the flag fall back to your project's default machine.
2. Vercel CLI (Requires v59.20.0+)
# Deploy with Turbo build machine for this invocation only
vc deploy --turbo
# Combine with other flags as usual
vc deploy --prod --turbo
Note the CLI version requirement — older CLIs will silently ignore the flag, so verify with vc --version first.
3. REST API (Programmatic Control)
When creating a deployment via the API, set buildMachine to turbo in the request body:
{
"name": "my-project",
"target": "production",
"buildMachine": "turbo"
}
This is the path to take if you're orchestrating deployments from a custom CI system or an internal platform layer.

Trade-offs and Caveats
| Aspect | Default Machine | Turbo Machine |
|---|---|---|
| Cost | Baseline | Higher per-minute rate |
| Build speed | Standard | Up to ~3x faster on CPU-bound builds |
| Config persistence | Project-level | Per-deployment only |
| Best for | Routine pushes | Heavy monorepos, hotfixes, migrations |
Important limitations to keep in mind:
- Not a silver bullet. If your build is I/O-bound (e.g., waiting on a slow npm registry or a remote cache miss), a faster CPU won't help much. Profile first.
- CLI version gating. Teams on older Vercel CLI versions will not see the
--turboflag work. Pin your CLI version in CI to avoid silent failures. - Billing visibility. Because Turbo is opt-in per deployment, cost spikes can hide inside normal deployment volume. Set up spend alerts if you're enabling it frequently.
- No retroactive application. You cannot flip an already-completed deployment to Turbo — it must be set at deployment creation time.
For teams running agent workloads or complex web stacks, the broader question of which build infrastructure to standardize on is worth revisiting. If you're evaluating the surrounding stack decisions, the reference architecture guide on agent and web stacks is a useful companion read.

When to Reach for Turbo
Treat per-deployment Turbo build machines as a surgical tool, not a default. The sweet spot is:
- Monorepo builds that occasionally exceed default memory
- Emergency hotfixes where minutes matter
- One-off migration or codegen deployments
For everything else, keep your project defaults and let the machine tier stay boring. The real win here isn't raw speed — it's optionality without config debt.
Next Steps
- Audit your last 30 deployments: which ones hit build timeouts or OOM errors? Those are your Turbo candidates.
- Wire the
#VERCEL_BUILD_MACHINE=TURBOdirective into a CI rule that auto-applies it when a build exceeds a threshold. - If you're also optimizing browser-side inference in your app, see how LiteRT.js changes the WebGPU/WebNN calculus.
Source: Vercel changelog — Turbo build machines per deployment