Buddy vs E2BSandbox Benchmark Comparison

Buddy
Faster in 2 of 2
vs
E2B
Faster in 0 of 2

Buddy 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.

BenchmarkBuddyE2BResultRatio
Burst TTI
Time to interactive · Run October 30, 2026
905ms
100% success
1.27s
100% success
Buddy faster
1.40x
DAX
Total workload time · Run October 30, 2026
59.09s
100% success
75.86s
100% success
Buddy faster
1.28x

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 →

E2B

100% success
Median
1.27s
P95
1.47s
P99
1.70s
E2B Burst TTI results →

Buddy had a 1.40x lower median time to interactive (905ms vs 1.27s for E2B).

Median time to interactive over time

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

BuddyE2B
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 →

E2B

100% success
Median
75.86s
P95
75.86s
P99
75.86s
E2B DAX results →

Buddy had a 1.28x lower median total workload time (59.09s vs 75.86s for E2B).

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.

Buddy was faster in both shared sandbox benchmarks. In Burst TTI (October 30, 2026), Buddy had a median time to interactive of 905ms versus 1.27s for E2B, 1.40x faster. In DAX (October 30, 2026), Buddy had a median total workload time of 59.09s versus 75.86s for E2B, 1.28x faster.

PartnersGoogle Cloud Run