---
title: Build Machines
description: Choose compute resources for your deployment builds.
order: 4
---

Each deployment build runs on a dedicated build VM. The **build machine tier** controls how much CPU and memory is available during the build step.

Build machine settings apply per project and affect every deployment build for that project.

## Available tiers

| Tier            | vCPUs | Memory | Best for                                     |
| --------------- | ----- | ------ | -------------------------------------------- |
| **Standard**    | 2     | 4 GB   | Lightweight apps, APIs, and most projects    |
| **Enhanced**    | 4     | 8 GB   | Larger applications with heavier build steps |
| **Performance** | 8     | 16 GB  | Demanding builds with long compile times     |

Change your tier under **Settings → Build Machine** in the project dashboard.

## Plan availability

Build machine tiers are gated by your workspace plan:

| Plan      | Available tiers                 |
| --------- | ------------------------------- |
| **Hobby** | Standard                        |
| **Pro**   | Standard, Enhanced              |
| **Team**  | Standard, Enhanced, Performance |

Upgrade your plan from the billing page if you need a tier that isn't available on your current plan.

## When to upgrade

Consider a larger build machine when:

- Builds time out or run out of memory during compilation
- You have large dependency trees (e.g. heavy Node.js or Rust builds)
- Docker multi-stage builds require significant intermediate resources

Build machine tier affects **build time and reliability**, not the resources available to your running application at runtime.

## Next steps

- [Configuration options](/docs/guides/configuration.md): other project settings
- [Deploy your first project](/docs/guides/first-deployment.md): deployment walkthrough