Gravixlayer was faster in 1 of 2 shared sandbox benchmarks, and 1 was roughly even.
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 8.91x lower median time to interactive (102ms vs 905ms for Buddy).
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
The medians are within 5% of each other (59.09s vs 58.66s), so this counts as roughly even.
4 runs from October 16, 2026 to October 30, 2026.
Have another question? Email us.
Gravixlayer was faster in 1 of 2 shared sandbox benchmarks, and 1 was roughly even. In Burst TTI (October 30, 2026), Gravixlayer had a median time to interactive of 102ms versus 905ms for Buddy, 8.91x faster. In DAX (October 30, 2026), Buddy had a median total workload time of 59.09s and Gravixlayer 58.66s, which counts as roughly even.