Sail vs SFCompute

Sandbox Benchmark Comparison · Updated November 20, 2026

SFCompute was faster in both shared sandbox benchmarks.

Head to head

  • Time to interactive · lower is better
    SFCompute faster14.4x
    Sail
    8.94s
    SFCompute
    621ms
  • Total workload time · lower is better
    SFCompute faster1.85x
    Sail
    73.66s
    SFCompute
    39.91s

Sail

100% success · November 13, 2026
Median
8.94s
p95
9.22s
p99
9.26s

SFCompute

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

Median time to interactive over time

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

DAX

November 20, 2026

Sail

100% success
Median
73.66s

SFCompute

100% success
Median
39.91s

Median total workload time over time

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

Cost per DAX run

Sail

Observed usage
$0.0054per run
73.66s median at $0.2620/hr

$0.015/used vCPU-hr + $0.008/used GiB-hr + $0.0007/GiB-hr NVMe — bills observed usage, not reservations (upper bound shown at full utilization). Plus $0.012 per L Sailbox creation. No charge while sleeping.

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 Sail 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 8.94s for Sail, 14.4x faster. In DAX (November 20, 2026), SFCompute had a median total workload time of 39.91s versus 73.66s for Sail, 1.85x 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: Sail 100%, SFCompute 100%; DAX: Sail 100%, SFCompute 100%.

Burst TTI results are from November 13, 2026; DAX results are from November 20, 2026.