Sandbox hardware and software context — use this to tell whether a provider is faster because of more CPUs/memory, not a faster disk or network.
Median workload time x published rates at the 8 vCPU / 16 GiB sandbox spec. Excludes sandbox create/destroy time. This provider bills CPU on active usage, so the wall-clock figure shown is an upper bound.
$0.128/active-CPU-hr per vCPU + $0.0212/GB-hr provisioned memory (wall clock). CPU upper bound at 100% utilization; real bills for I/O-bound runs are lower. Source · Compare all providers
Total disk usage (du -sx) captured after each phase — a proxy for disk I/O and storage cost. Some providers report 0 here if their sandbox filesystem doesn't support usable disk-usage reporting.
Each iteration runs the full clone + install + typecheck cycle from a fresh sandbox.
| # | Phases | Total | Prepare | Bun DL | Bun Unpack | Clone | Install | Typecheck | Error |
|---|---|---|---|---|---|---|---|---|---|
| 1 | 7/7 | 121.54s | 19.42s | 0.36s | 0.90s | 3.17s | 19.02s | 68.13s | — |