Managing Builds

When you build your application code, Vercel runs compute to install dependencies, run your build script, and upload the build output to our CDN. There are several ways in which you can manage your build compute.

• If you need faster build machines or more memory, you can purchase Enhanced or Turbo build machines.
• If you are deploying frequently and seeing build queues, you can enable On-Demand Concurrent Builds where you pay for build compute so your builds always start immediately.

Visit Build Diagnostics in the Observability tab of the Vercel Dashboard 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 two higher-tier build machines with more vCPUs, memory and disk space than Standard.

You can set the build machine type in the Build and Deployment section of your Project Settings.

When your team uses Enhanced or Turbo machines, it'll contribute to the "On-Demand Concurrent Build Minutes" item of your bill.

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.

By default, only one concurrent build is executed at a time. Other builds will be queued and handled in chronological order (FIFO Order). On-demand concurrent builds allow all builds to be executed in parallel, with no queues.

When enabled, 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 enable it 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,
      "buildMachineType": "enhanced",
    }
  }'

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,
        buildMachineType: 'enhanced',
      },
    },
  });
 
  // Handle the result
  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. From the top navigation, select the Deployments tab.

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. Select the Settings tab, 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, usage of Enhanced and Turbo machines contributes to "On-Demand Concurrent Build Minutes".

On-demand concurrent builds are priced in $ per minute of build time and is based on the type of build machines used.

On-demand concurrent builds 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.