Microsandbox vs SFCompute

Sandbox Benchmark Comparison · Updated November 13, 2026

SFCompute was faster in both shared sandbox benchmarks.

Head to head

  • Time to interactive · lower is better
    SFCompute faster8.02x
    Microsandbox
    4.99s
    SFCompute
    621ms
  • Total workload time · lower is better
    SFCompute faster1.40x
    Microsandbox
    56.07s
    SFCompute
    39.91s

Microsandbox

100% success · November 13, 2026
Median
4.99s
p95
5.99s
p99
6.24s

SFCompute

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

Median time to interactive over time

12 runs · September 4, 2026 to November 13, 2026
MicrosandboxSFCompute

Microsandbox

100% success · November 13, 2026
Median
56.07s

SFCompute

100% success · November 20, 2026
Median
39.91s

Cost per DAX run

Microsandbox

Per-second wall clock
$0.010per run
56.07s median at $0.6592/hr

$0.05/vCPU-hr + $0.0162/GiB-hr + disk $0.0001/GiB-hr. Plans include monthly compute pools.

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 Microsandbox 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 both shared sandbox benchmarks. In Burst TTI (November 13, 2026), SFCompute had a median time to interactive of 621ms versus 4.99s for Microsandbox, 8.02x faster. In DAX (November 13, 2026), SFCompute had a median total workload time of 39.91s versus 56.07s for Microsandbox, 1.40x 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: Microsandbox 100%, SFCompute 100%; DAX: Microsandbox 100%, SFCompute 100%.

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