<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/turbo-build-machines-can-now-be-enabled-per-deployment-dc0kdirvg" -->

---
title: Turbo build machines can now be enabled per deployment
description: Vercel now lets developers enable Turbo build machines for individual deployments instead of only at the project level, giving temporary access to more build...
canonical: https://daily.dev/posts/turbo-build-machines-can-now-be-enabled-per-deployment-dc0kdirvg
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Turbo build machines can now be enabled per deployment | daily.dev
og:description: Vercel now lets developers enable Turbo build machines for individual deployments instead of only at the project level, giving temporary access to more build...
og:url: https://daily.dev/posts/turbo-build-machines-can-now-be-enabled-per-deployment-dc0kdirvg
og:image: https://api.daily.dev/og/posts/Dc0kdIrVg.png
og:image:alt: Turbo build machines can now be enabled per deployment
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Turbo build machines can now be enabled per deployment

**[Vercel](https://daily.dev/sources/vercel)** · 1 min read · 1 upvotes · 0 comments

## Summary

Vercel now lets developers enable Turbo build machines for individual deployments instead of only at the project level, giving temporary access to more build resources without changing global settings. This can be triggered by including a specific tag in a Git commit message, using the Vercel CLI (version 59.20.0 or later) with a new flag, or setting a buildMachine parameter via the REST API when creating a deployment.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://vercel.com/changelog/turbo-build-machines-can-now-be-enabled-per-deployment>

## Questions this post answers

### How do I enable a Turbo build machine for just one Vercel deployment instead of the whole project?

You can enable it per deployment in three ways: include #VERCEL_BUILD_MACHINE=TURBO in your Git commit message before pushing to GitHub, run vc deploy --turbo using Vercel CLI 59.20.0 or later, or set buildMachine to turbo when creating a deployment through the Vercel REST API. This avoids changing global project settings for a temporary resource boost.

_Track platform changes like this build machine option as you tune deployment costs, with daily.dev._

### Which version of the Vercel CLI supports the --turbo flag for deployments?

Vercel CLI version 59.20.0 or later supports the --turbo flag, used as vc deploy --turbo to enable a Turbo build machine for that specific deployment without altering project-wide build machine settings.

_daily.dev helps developers keep pinned CLI versions current when tooling flags like this ship._

## Similar posts on daily.dev

- [Elastic build machines are available in Beta](https://daily.dev/posts/elastic-build-machines-are-available-in-beta-2w3g0xldk) · Vercel · 1 upvotes · 0 comments
- [Vercel CI is now in beta](https://daily.dev/posts/vercel-ci-is-now-in-beta-oapcgqqal) · Vercel · 1 upvotes · 0 comments
- [Elastic build machines now use Turborepo cache hits to prevent downgrades](https://daily.dev/posts/elastic-build-machines-now-use-turborepo-cache-hits-to-prevent-downgrades-hqj8inghu) · Vercel · 0 upvotes · 0 comments
- [Elastic Build Machines is now GA](https://daily.dev/posts/elastic-build-machines-is-now-ga-5qksahv5p) · Vercel · 0 upvotes · 0 comments

---

Tags: [#cicd](https://daily.dev/tags/cicd), [#vercel](https://daily.dev/tags/vercel)

[View this post on daily.dev](https://daily.dev/posts/turbo-build-machines-can-now-be-enabled-per-deployment-dc0kdirvg)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Turbo build machines can now be enabled per deployment","url":"https://daily.dev/posts/turbo-build-machines-can-now-be-enabled-per-deployment-dc0kdirvg","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/turbo-build-machines-can-now-be-enabled-per-deployment-dc0kdirvg"},"datePublished":"2026-09-17T20:36:20.516Z","dateModified":"2026-09-17T21:26:47.197Z","description":"Vercel now lets developers enable Turbo build machines for individual deployments instead of only at the project level, giving temporary access to more build...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/91f4aaadeec52e5702332ac23be43f66?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/91f4aaadeec52e5702332ac23be43f66?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Vercel","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Vercel","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/04cca7235cf84db092f24b7ba427b3e1","url":"https://daily.dev/sources/vercel"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/turbo-build-machines-can-now-be-enabled-per-deployment-dc0kdirvg","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"cicd,vercel","timeRequired":"PT1M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Vercel","item":"https://daily.dev/sources/vercel"},{"@type":"ListItem","position":3,"name":"Turbo build machines can now be enabled per deployment"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/turbo-build-machines-can-now-be-enabled-per-deployment-dc0kdirvg#faq","mainEntity":[{"@type":"Question","name":"How do I enable a Turbo build machine for just one Vercel deployment instead of the whole project?","acceptedAnswer":{"@type":"Answer","text":"You can enable it per deployment in three ways: include #VERCEL_BUILD_MACHINE=TURBO in your Git commit message before pushing to GitHub, run vc deploy --turbo using Vercel CLI 59.20.0 or later, or set buildMachine to turbo when creating a deployment through the Vercel REST API. This avoids changing global project settings for a temporary resource boost. Track platform changes like this build machine option as you tune deployment costs, with daily.dev."}},{"@type":"Question","name":"Which version of the Vercel CLI supports the --turbo flag for deployments?","acceptedAnswer":{"@type":"Answer","text":"Vercel CLI version 59.20.0 or later supports the --turbo flag, used as vc deploy --turbo to enable a Turbo build machine for that specific deployment without altering project-wide build machine settings. daily.dev helps developers keep pinned CLI versions current when tooling flags like this ship."}}]}
```

