Pre-warmed volumes so jobs start ready
Standby disks
How standby disks let a BYOC runner start from a prepared filesystem instead of provisioning storage per job.
A standby disk holds a prepared runner filesystem — installed dependencies, populated toolchain directories, warm page cache — so a job attaches to storage that is already in the state it needs.
This is the mechanism behind snapshot runners. Instead of restoring a cache into an empty disk, the disk already contains the result.
| Approach | Install step | Storage cost |
|---|---|---|
| Cold disk + no cache | Full install every job | None |
| Cold disk + cache restore | Restore, then partial install | Cache storage |
| Standby disk | Skipped entirely | Per GB-month, retained |
Your next build could be twice as fast, at half the price
Start free. Migrating away is the same one line, and we publish that diff too.