BerryBox Choose a runner
AMD x64 machines for your existing GitHub Actions jobs.
Use a single BerryBox label as the job's runs-on value. Enable the label in your team's runner settings first.
| Size | Balanced label | RAM | Listed USD / minute |
|---|---|---|---|
| 2 vCPU | berrybox-2vcpu-ubuntu-2404 | 8 GiB | $0.004 |
| 4 vCPU | berrybox-4vcpu-ubuntu-2404 | 16 GiB | $0.008 |
| 8 vCPU | berrybox-8vcpu-ubuntu-2404 | 32 GiB | $0.016 |
| 16 vCPU | berrybox-16vcpu-ubuntu-2404 | 64 GiB | $0.032 |
For memory-heavy jobs, use berrybox-memory-2vcpu-ubuntu-2404, or the equivalent 4, 8 or 16 vCPU label. These provide 8 GiB per vCPU, starting at $0.006/minute for 2 vCPU / 16 GiB, scaling proportionally.
berrybox-ubuntu-latest is an alias for the balanced 2 vCPU Ubuntu 24.04 runner. Custom team aliases resolve to an enabled profile. The dashboard and berrybox pricing show the current rate; the rate recorded for each job determines its charge.
What the label guarantees
The label selects CPU count, memory and Ubuntu 24.04 x64. BerryBox chooses among compatible AMD EC2 instance pools. It does not pin a particular chip generation or instance family. A larger runner consumes more of your team's vCPU concurrency allowance.
Each job receives its own VM and encrypted root disk. The official GitHub Actions runner executes your workflow directly. The VM is terminated and the disk removed afterwards.
Choosing a size
Start with 2 vCPU for lightweight checks. Move to 4 or 8 vCPU when your build or test runner can use parallel CPU. Choose memory optimized when the job runs out of RAM rather than assuming more CPU will fix it.
Compare cost per completed job, not just duration. An 8 vCPU runner costs four times the 2 vCPU rate; it needs enough speedup to justify that difference.