Beam vs SFCompute

Sandbox Benchmark Comparison · Updated November 20, 2026

SFCompute was faster in 1 of 2 shared sandbox benchmarks, and 1 was roughly even.

Head to head

  • Time to interactive · lower is better
    Roughly even
    Beam
    649ms
    SFCompute
    621ms
  • Total workload time · lower is better
    SFCompute faster2.81x
    Beam
    112.09s
    SFCompute
    39.91s

Burst TTI

November 20, 2026

Beam

100% success
Median
649ms
p95
867ms
p99
877ms

SFCompute

100% success
Median
621ms
p95
765ms
p99
766ms

Median time to interactive over time

15 runs · September 4, 2026 to November 20, 2026
BeamSFCompute

DAX

November 20, 2026

Beam

100% success
Median
112.09s

SFCompute

100% success
Median
39.91s

Median total workload time over time

6 runs · September 16, 2026 to November 20, 2026
BeamSFCompute

Cost per DAX run

Beam

Per-second wall clock
$0.028per run
112.09s median at $0.9086/hr

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

Source pricing page

SFCompute

Per GiB-hour (parkable)
$0.0081per run
39.91s median at $0.7315/hr

Rollout sandboxes at $0.04572/GiB-hr while active (16 GiB); parked/idle drops to ~$0.000139/GiB-hr. Interactive cpu-8 node is $0.4824/hr with a 15-min minimum.

Source pricing page
Compare sandbox costs across all providers
Work at Beam or SFCompute? See where you stand every day, with full run logs, not just on benchmark Friday.Get stealth benchmarks

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 when both providers have at least one successful run in the same benchmark from the last 30 days. A benchmark only gets a verdict when both providers completed at least 50% of its runs. If a provider’s latest run of a benchmark failed, its most recent successful run from that window is used instead.
Read the full methodology

Frequently asked questions

Have another question? Email us.

SFCompute was faster in 1 of 2 shared sandbox benchmarks, and 1 was roughly even. In Burst TTI (November 20, 2026), Beam had a median time to interactive of 649ms and SFCompute 621ms, which counts as roughly even. In DAX (November 20, 2026), SFCompute had a median total workload time of 39.91s versus 112.09s for Beam, 2.81x faster.

Both providers have results in 2 sandbox benchmarks: Burst TTI and DAX. All of them have a speed verdict.

Success rates in the latest runs: Burst TTI: Beam 100%, SFCompute 100%; DAX: Beam 100%, SFCompute 100%.

Burst TTI and DAX results are from November 20, 2026.