Buddy vs IsorunSandbox Benchmark Comparison

Buddy
Faster in 0 of 2
vs
Isorun
Faster in 2 of 2

Isorun was faster in both shared sandbox benchmarks.

Shared benchmarks
2
Last run
October 30, 2026
Want the full run details?Sign up free →

Scorecard

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.

BenchmarkBuddyIsorunResultRatio
Burst TTI
Time to interactive · Run October 30, 2026
905ms
100% success
49ms
100% success
Isorun faster
18.5x
DAX
Total workload time · Run October 30, 2026
59.09s
100% success
36.13s
100% success
Isorun faster
1.64x

Burst TTI

Run October 30, 2026

Time from sandbox creation to the first successful command, with 100 sandboxes launched at the same time.

Time to interactive

Buddy

100% success
Median
905ms
P95
1.08s
P99
1.11s
Buddy Burst TTI results →

Isorun

100% success
Median
49ms
P95
57ms
P99
63ms
Isorun Burst TTI results →

Isorun had a 18.5x lower median time to interactive (49ms vs 905ms for Buddy).

Median time to interactive over time

6 runs from October 2, 2026 to October 30, 2026.

BuddyIsorun
View the full Burst TTI leaderboard →

DAX

Run 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

Buddy

100% success
Median
59.09s
P95
59.09s
P99
59.09s
Buddy DAX results →

Isorun

100% success
Median
36.13s
P95
36.13s
P99
36.13s
Isorun DAX results →

Isorun had a 1.64x lower median total workload time (36.13s vs 59.09s for Buddy).

Median total workload time over time

4 runs from October 16, 2026 to October 30, 2026.

BuddyIsorun
View the full DAX leaderboard →

Methodology

  • One workload, every provider. The same script, payload, and model hit every provider, addressed the way its own API expects. Nobody gets a tuned or special path.
  • Repeated on a schedule. Every suite runs many iterations per provider, automated on a recurring schedule, so results reflect steady state rather than one lucky request.
  • Raw results published. Every run is committed as JSON to the public benchmarks repo, next to the code that produced it. Nothing is cherry-picked or held back.
  • How this comparison is built. Each benchmark compares the two providers' medians; results within 5% count as roughly even. A comparison is published only when both providers completed at least 50% of runs in 2 or more shared benchmarks run in the last 30 days.

Frequently asked questions

Have another question? Email us.

Isorun was faster in both shared sandbox benchmarks. In Burst TTI (October 30, 2026), Isorun had a median time to interactive of 49ms versus 905ms for Buddy, 18.5x faster. In DAX (October 30, 2026), Isorun had a median total workload time of 36.13s versus 59.09s for Buddy, 1.64x faster.

PartnersGoogle Cloud Run