Gravixlayer was faster in both shared sandbox benchmarks.
Median of each benchmark's primary metric; lower is better. Medians within 5% count as roughly even, and a benchmark gets no speed verdict when either provider completed fewer than 50% of runs.
Time from sandbox creation to the first successful command, with 100 sandboxes launched at the same time.
Time to interactive
Gravixlayer had a 101.3x lower median time to interactive (102ms vs 10.28s for Sandbox0).
4 runs from October 9, 2026 to October 30, 2026.
A real developer workload: install system packages, download Bun, clone the opencode repo, then run bun install and bun typecheck.
Total workload time
Gravixlayer had a 2.13x lower median total workload time (58.66s vs 124.96s for Sandbox0).
5 runs from October 9, 2026 to October 30, 2026.
Have another question? Email us.
Gravixlayer was faster in both shared sandbox benchmarks. In Burst TTI (October 30, 2026), Gravixlayer had a median time to interactive of 102ms versus 10.28s for Sandbox0, 101.3x faster. In DAX (October 30, 2026), Gravixlayer had a median total workload time of 58.66s versus 124.96s for Sandbox0, 2.13x faster.