Summary
Vercel added per-deployment control over Turbo build machines, letting developers switch on faster build infrastructure only when a given deployment needs it while keeping standard, cheaper builds as the default.
What changed
Turbo build machines can now be enabled per deployment, giving developers on-demand access to faster build infrastructure instead of an all-or-nothing project setting.
Why it matters
Build speed and build cost pull in opposite directions; per-deployment Turbo control lets teams pay for fast builds selectively (e.g., release branches or CI-critical paths) rather than committing every build to premium machines.
Evidence excerpt
Turbo build machines can now be enabled per deployment — developers gain per-deployment control to activate faster build infrastructure when needed while minimizing costs for standard deployments.