Buddy vs VercelSandbox Benchmark Comparison

Buddy
Faster in 1 of 2
vs
Vercel
Faster in 1 of 2

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

BenchmarkBuddyVercelResultRatio
Burst TTI
Time to interactive · Run October 30, 2026
905ms
100% success
423ms
100% success
Vercel faster
2.14x
DAX
Total workload time · Run October 30, 2026
59.09s
100% success
83.37s
100% success
Buddy faster
1.41x

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 →

Vercel

100% success
Median
423ms
P95
562ms
P99
585ms
Vercel Burst TTI results →

Vercel had a 2.14x lower median time to interactive (423ms vs 905ms for Buddy).

Median time to interactive over time

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

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

Vercel

100% success
Median
83.37s
P95
83.37s
P99
83.37s
Vercel DAX results →

Buddy had a 1.41x lower median total workload time (59.09s vs 83.37s for Vercel).

Median total workload time over time

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

BuddyVercel
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 and Vercel were each faster in 1 of 2 shared sandbox benchmarks. In Burst TTI (October 30, 2026), Vercel had a median time to interactive of 423ms versus 905ms for Buddy, 2.14x faster. In DAX (October 30, 2026), Buddy had a median total workload time of 59.09s versus 83.37s for Vercel, 1.41x faster.

PartnersGoogle Cloud Run