CreateOS vs SFCompute

Sandbox Benchmark Comparison · Updated November 6, 2026

CreateOS and SFCompute were each faster in 1 of 2 shared sandbox benchmarks.

Head to head

  • Time to interactive · lower is better
    CreateOS faster1.87x
    CreateOS
    332ms80%
    SFCompute
    621ms
  • Total workload time · lower is better
    SFCompute faster1.32x
    CreateOS
    52.68s
    SFCompute
    39.91s

CreateOS

80% success · November 6, 2026
Median
332ms
p95
394ms
p99
417ms

SFCompute

100% success · November 20, 2026
Median
621ms
p95
765ms
p99
766ms

Median time to interactive over time

14 runs · September 4, 2026 to November 20, 2026
CreateOSSFCompute

CreateOS

100% success · November 6, 2026
Median
52.68s

SFCompute

100% success · November 20, 2026
Median
39.91s

Median total workload time over time

5 runs · September 16, 2026 to October 9, 2026
CreateOSSFCompute

Cost per DAX run

CreateOS

Per-second wall clock
$0.0097per run
52.68s median at $0.6624/hr

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

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

CreateOS and SFCompute were each faster in 1 of 2 shared sandbox benchmarks. In Burst TTI (November 6, 2026), CreateOS had a median time to interactive of 332ms versus 621ms for SFCompute, 1.87x faster. In DAX (November 6, 2026), SFCompute had a median total workload time of 39.91s versus 52.68s for CreateOS, 1.32x 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: CreateOS 80%, SFCompute 100%; DAX: CreateOS 100%, SFCompute 100%.

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