A big, clean machine for the heavy part
When a build or a test run outgrows a sandbox, your agent leases a host from a pool, runs over SSH and hands it back wiped.
Run the full test suite
Claude Code leased a large host for the part that was too heavy for its sandbox. Access and secrets end when the lease does.
bh-large-04 from linux-large for 2 has maya18,402 files10:02DB_TEST_URL for this lease only10:03go test ./... -p 161,240 passedcoverage.out off the host10:31- Lease
- lease_7f2c
- Host
- bh-large-04
- Pool
- linux-large
- Size
- 16 vCPU · 32 GB
- Requested by
- Claude Code as maya
- Certificate
- ends with the lease
- Secrets
- 1, ends with the lease
- Region
- us-east
- Time left
- 1:26:00
Some jobs are too big for where the agent works. A build host is a clean, large machine your agent leases for the heavy part, runs over SSH, and hands back. Nothing is left on it afterwards.
Shard a suite across all the vCPUs of the lease instead of one shared runner.
Pro leases run up to 4 hours, Team leases up to 12.
The next run gets a clean machine. Pull what you need off before you release it.
The whole suite,
on every core
A test suite that crawls on a laptop or a shared runner gets a machine to itself. The agent shards it across every vCPU of the lease and moves on while it runs.
Everything ends
when the lease does
The SSH certificate and every Vault secret issued for a lease are valid only while it lasts. Release it early or let it run out: access stops at the same moment and the machine is wiped.
How we secure it →Included in
your plan
Lease time draws from your plan’s monthly vCPU-hours, like sandboxes and workspaces.
See pricing →Sandboxes only.
One lease at a time, from 750 vCPU-hours a month.
Several leases at once, from hours pooled across the team.
Hand the slow part
to a big machine
Build hosts come with Pro and up. Lease one when the job needs it.