Managing Builds

When you build your application code, Vercel runs compute to install dependencies, run your build script, and sends the build output to our Compute and CDN.

By default, we enable our fastest build settings for Pro customers' new projects: Turbo build machines and On-Demand Concurrent Builds.

• If you're on a Hobby plan and looking for faster builds, we recommend upgrading to Pro.
• If you're on an Enterprise plan, build machines are managed as a part of your contract.

Visit Build Diagnostics in the Observability section in the Vercel dashboard sidebar to find your build durations. You can also use this table to quickly identify which solution fits your needs:

For Pro and Enterprise customers, we offer three higher-tier build machines with more compute resources than Standard. Elastic build machines auto-scale based on your recent build durations. Turbo build machines are enabled by default for new Pro projects.

You can set the build machine type in the Build and Deployment section of your settings for your team or for individual projects.

When your team uses Elastic, Enhanced, or Turbo machines, usage contributes to your build usage charges. Elastic build machines are billed by CPU minute, starting at $0.0035 per CPU minute.

Enterprise customers who have Enhanced build machines enabled via contract will always use them by default. You can view if you have this enabled in the Build Machines section of the Build and Deployment tab in your Team Settings. To update your build machine preferences, you need to contact your account manager.

On-demand concurrent builds allow your builds to skip the queue and run immediately. By default, projects have on-demand concurrent builds enabled with full concurrency. Learn more about concurrency modes.

You are charged for on-demand concurrent builds based on the number of concurrent builds required to allow the builds to proceed as explained in usage and limits.

When you enable on-demand build concurrency at the level of a project, any queued builds in that project will automatically be allowed to proceed. You can choose to run all builds immediately or limit to one active build per branch.

You can configure this on the project's Build and Deployment Settings page:

curl --request PATCH \
  --url https://api.vercel.com/v9/projects/YOUR_PROJECT_ID?teamId=YOUR_TEAM_ID \
  --header "Authorization: Bearer $VERCEL_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{
    "resourceConfig": {
      "elasticConcurrencyEnabled": true,
      "buildQueue": {
        "configuration": "SKIP_NAMESPACE_QUEUE"
      }
    }
  }'

import { Vercel } from '@vercel/sdk';
 
const vercel = new Vercel({
  bearerToken: '<YOUR_BEARER_TOKEN_HERE>',
});
 
async function run() {
  const result = await vercel.projects.updateProject({
    idOrName: 'YOUR_PROJECT_ID',
    teamId: 'YOUR_TEAM_ID',
    requestBody: {
      resourceConfig: {
        elasticConcurrencyEnabled: true,
        buildQueue: {
          configuration: 'SKIP_NAMESPACE_QUEUE',
        },
      },
    },
  });
 
  console.log(result);
}
 
run();

For individual deployments, you can force build execution using the Start Building Now button. Regardless of the reason why this build was queued, it will proceed.

1. Select your project from the dashboard.

2. in the sidebar, open Deployments.

3. Find the queued deployment that you would like to build from the list. You can use the Status filter to help find it. You have 2 options:

   • Select the three dots to the right of the deployment and select Start Building Now.
   • Click on the deployment list item to go to the deployment's detail page and click Start Building Now.

4. Confirm that you would like to build this deployment in the Start Building Now dialog.

Some other considerations to take into account when optimizing your builds include:

• Understand and manage the build cache. By default, Vercel caches the dependencies of your project, based on your framework, to speed up the build process
• You may choose to Ignore the Build Step on redeployments if you know that the build step is not necessary under certain conditions
• Use the most recent version of your runtime, particularly Node.js, to take advantage of the latest performance improvements. To learn more, see Node.js

If a build has to wait for queued preview deployments to finish, it can delay the production release process. When Vercel queues builds, we'll processes them in chronological order (FIFO Order).

To ensure that changes to the production environment are prioritized over preview deployments in the queue, you can enable Prioritize Production Builds:

1. From your Vercel dashboard, select the project you wish to enable it for
2. Open Settings in the sidebar, and go to the Build and Deployment section of your Project Settings
3. Under Prioritize Production Builds, toggle the switch to Enabled

The on-demand build usage is based on the amount of time it took for a deployment to build when using a concurrent build. In Billing, Elastic build machines are billed by CPU minute. Enhanced and Turbo machines are billed by build minute.

Build machine usage is priced by machine type. Standard build machines are billed only when on-demand concurrency is enabled. Elastic build machines start at $0.0035 per CPU minute.

Elastic build machines start at $0.0035 per CPU minute. Enterprise contract pricing and discounts can vary.

On-demand concurrent builds for Standard, Enhanced, and Turbo build machines are priced in MIUs per minute of build time used and the rate depends on the number of contracted concurrent builds and the machine type.