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.0000115/GB-s on allocated RAM while active (16 GiB). CPU is derived from memory — 16 GB maps to ~6 cores, not 8. Upper bound shown. 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 | 46.92s | 1.19s | 0.30s | 0.49s | 1.39s | 10.45s | 25.40s | — |