Beam vs CreateOSSandbox Benchmark Comparison

Beam
Faster in 0 of 2
vs
CreateOS
Faster in 2 of 2

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

BenchmarkBeamCreateOSResultRatio
Burst TTI
Time to interactive · Run October 30, 2026
548ms
100% success
136ms
100% success
CreateOS faster
4.04x
DAX
Total workload time · Run October 30, 2026
96.13s
100% success
53.21s
100% success
CreateOS faster
1.81x

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 →

CreateOS

100% success
Median
136ms
P95
176ms
P99
178ms
CreateOS Burst TTI results →

CreateOS had a 4.04x lower median time to interactive (136ms vs 548ms for Beam).

Median time to interactive over time

30 runs from July 3, 2026 to October 30, 2026.

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

CreateOS

100% success
Median
53.21s
P95
53.21s
P99
53.21s
CreateOS DAX results →

CreateOS had a 1.81x lower median total workload time (53.21s vs 96.13s for Beam).

Median total workload time over time

9 runs from September 16, 2026 to October 30, 2026.

BeamCreateOS
View the full DAX leaderboard →

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.024per run
96.13s median at $0.9086/hr

$0.0000375/core-s (1 core = 2 vCPU, so 4 cores) + $0.0000064/GiB-s.

Source pricing page

CreateOS

Per-second wall clock
$0.0098per run
53.21s median at $0.6624/hr

$0.0504/vCPU-hr + $0.0162/GiB-hr — parity with E2B. No egress fees.

Source pricing page
Compare sandbox costs across all providers →

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.

CreateOS was faster in both shared sandbox benchmarks. In Burst TTI (October 30, 2026), CreateOS had a median time to interactive of 136ms versus 548ms for Beam, 4.04x faster. In DAX (October 30, 2026), CreateOS had a median total workload time of 53.21s versus 96.13s for Beam, 1.81x faster.

PartnersGoogle Cloud Run