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.
Large box (8 vCPU / 16 GB): $0.40/active-CPU-hour — assumes 100% CPU utilization for the whole build. 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 | 51.94s | 3.91s | 0.28s | 0.62s | 2.49s | 9.97s | 25.02s | — |