# No build queues: On-demand concurrent builds now on by default

By Steven Van · 2025-09-09

Pro and Enterprise teams get up to 500 concurrent builds instead of 3, with an opt-in bulk toggle for teams on older pricing.

[Vercel](<https://creatorstoolbox.com/tools/vercel>) has switched on [on-demand concurrent builds](<https://vercel.com/docs/builds/managing-builds#on-demand-concurrent-builds>) by default for teams on its new Pro pricing model. Builds across projects now start immediately instead of waiting in a queue, except when multiple builds target the same Git branch.

Teams not yet on the new Pro pricing model can still turn the setting on using the new bulk enable feature, which applies it across projects at once. The feature is available on Pro and Enterprise plans, and only accounts with the owner role can access it.

- Hobby: 1 concurrent deployment; builds beyond that run sequentially.

- Pro: up to **500** concurrent deployments with on-demand concurrency on (3 if it's off), billed by the build minutes used.

- Enterprise: custom concurrency limits tailored to the organisation's needs.

![Vercel](<https://www.google.com/s2/favicons?domain=vercel.com&sz=128>)

Vercel

The platform for frontend developers — deploy, preview, and scale web apps and AI agents with zero config.

[View Vercel →](<https://creatorstoolbox.com/tools/vercel>)

[Original source](<https://vercel.com/docs/builds/managing-builds#on-demand-concurrent-builds>)

[Read No build queues: On-demand concurrent builds now on by default on Creators Toolbox](<https://creatorstoolbox.com/blog/vercel-no-build-queues-on-demand-concurrent-builds-now-on-by-default>)

---
Canonical source: https://creatorstoolbox.com/blog/vercel-no-build-queues-on-demand-concurrent-builds-now-on-by-default
