Beam vs BuddySandbox Benchmark Comparison

Beam
Faster in 1 of 2
vs
Buddy
Faster in 1 of 2

Beam and Buddy were each faster in 1 of 2 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.

BenchmarkBeamBuddyResultRatio
Burst TTI
Time to interactive · Run October 30, 2026
548ms
100% success
905ms
100% success
Beam faster
1.65x
DAX
Total workload time · Run October 30, 2026
96.13s
100% success
59.09s
100% success
Buddy faster
1.63x

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

Beam

100% success
Median
548ms
P95
732ms
P99
739ms
Beam Burst TTI results →

Buddy

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

Beam had a 1.65x lower median time to interactive (548ms vs 905ms for Buddy).

Median time to interactive over time

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

BeamBuddy
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

Beam

100% success
Median
96.13s
P95
96.13s
P99
96.13s
Beam DAX results →

Buddy

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

Buddy had a 1.63x lower median total workload time (59.09s vs 96.13s for Beam).

Median total workload time over time

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

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

Beam and Buddy were each faster in 1 of 2 shared sandbox benchmarks. In Burst TTI (October 30, 2026), Beam had a median time to interactive of 548ms versus 905ms for Buddy, 1.65x faster. In DAX (October 30, 2026), Buddy had a median total workload time of 59.09s versus 96.13s for Beam, 1.63x faster.

PartnersGoogle Cloud Run