Beam vs VercelSandbox Benchmark Comparison
Vercel was faster in both shared sandbox benchmarks.
- Shared benchmarks
- 2
- Last run
- October 30, 2026
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.
Burst TTI
Run October 30, 2026Time from sandbox creation to the first successful command, with 100 sandboxes launched at the same time.
Time to interactive
Vercel had a 1.29x lower median time to interactive (423ms vs 548ms for Beam).
Median time to interactive over time
30 runs from July 3, 2026 to October 30, 2026.
DAX
Run October 30, 2026A real developer workload: install system packages, download Bun, clone the opencode repo, then run bun install and bun typecheck.
Total workload time
Vercel had a 1.15x lower median total workload time (83.37s vs 96.13s for Beam).
Median total workload time over time
9 runs from September 16, 2026 to October 30, 2026.
Cost per DAX run
Each provider's DAX median total workload time (run October 30, 2026) multiplied by its published rate at the 8 vCPU / 16 GiB benchmark spec. Workload time excludes sandbox create and destroy, and subscription floors and included credits are not modeled.
Beam
Per-second wall clock$0.0000375/core-s (1 core = 2 vCPU, so 4 cores) + $0.0000064/GiB-s.
Source pricing pageVercel
Active CPU + provisioned memory$0.128/active-CPU-hr per vCPU + $0.0212/GB-hr provisioned memory (wall clock). CPU upper bound at 100% utilization; real bills for I/O-bound runs are lower.
Source pricing pageMethodology
- 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.
Vercel was faster in both shared sandbox benchmarks. In Burst TTI (October 30, 2026), Vercel had a median time to interactive of 423ms versus 548ms for Beam, 1.29x faster. In DAX (October 30, 2026), Vercel had a median total workload time of 83.37s versus 96.13s for Beam, 1.15x faster.