Vercel Enables Per-Deployment Turbo Build Machine Opt-in
Vercel now allows developers to enable Turbo build machines on a per-deployment basis using Git commit messages, Vercel CLI, or the REST API. This provides temporary resource scaling for specific builds without requiring global project setting modifications.
Verified State Diff
Impact & Verification Analysis
Vercel developers requiring high-performance build resources for specific deployments without permanent project-wide configuration changes.
This feature allows for more cost-effective and flexible resource allocation, enabling developers to opt-in to faster build times only when necessary, such as for complex production builds, while keeping standard builds on default infrastructure.
Full Fact Overview
Vercel has introduced granular control over build infrastructure, allowing users to trigger Turbo build machines for individual deployments. Previously, Turbo build machines were managed via global project settings. Users can now trigger this behavior by adding '#VERCEL_BUILD_MACHINE=TURBO' to a Git commit message, using the '--turbo' flag in Vercel CLI version 59.20.0 or later, or by setting the 'buildMachine' parameter to 'turbo' via the REST API.