SFCompute vs Vercel

Sandbox Benchmark Comparison · Updated November 20, 2026

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

Head to head

  • Time to interactive · lower is better
    Vercel faster2.02x
    SFCompute
    621ms
    Vercel
    307ms
  • Total workload time · lower is better
    SFCompute faster2.55x
    SFCompute
    39.91s
    Vercel
    101.83s

Burst TTI

November 20, 2026

SFCompute

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

Vercel

100% success
Median
307ms
p95
459ms
p99
593ms

Median time to interactive over time

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

DAX

November 20, 2026

SFCompute

100% success
Median
39.91s

Vercel

100% success
Median
101.83s

Median total workload time over time

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

Cost per DAX run

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

Vercel

Active CPU + provisioned memory
$0.039per run
101.83s median at $1.3632/hr

$0.128/active-CPU-hr per vCPU + $0.0212/GB-hr provisioned memory (wall clock). CPU upper bound at 100% utilization; real bills for I/O-bound runs are lower.

Source pricing page
Compare sandbox costs across all providers
Work at SFCompute or Vercel? 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 and Vercel were each faster in 1 of 2 shared sandbox benchmarks. In Burst TTI (November 20, 2026), Vercel had a median time to interactive of 307ms versus 621ms for SFCompute, 2.02x faster. In DAX (November 20, 2026), SFCompute had a median total workload time of 39.91s versus 101.83s for Vercel, 2.55x 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: SFCompute 100%, Vercel 100%; DAX: SFCompute 100%, Vercel 100%.

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