Gravixlayer vs SFCompute

Sandbox Benchmark Comparison · Updated November 13, 2026

GravixlayerPre-release
Faster in
1of 2 benchmarks
vs

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

Head to head

  • Time to interactive · lower is better
    Gravixlayer faster1.55x
    Gravixlayer
    400ms
    SFCompute
    621ms
  • Total workload time · lower is better
    SFCompute faster1.48x
    Gravixlayer
    59.08s
    SFCompute
    39.91s

Gravixlayer

100% success · November 13, 2026
Median
400ms
p95
429ms
p99
430ms

SFCompute

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

Median time to interactive over time

5 runs · October 9, 2026 to November 13, 2026
GravixlayerSFCompute

Gravixlayer

100% success · November 13, 2026
Median
59.08s

SFCompute

100% success · November 20, 2026
Median
39.91s
Work at Gravixlayer 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.

Gravixlayer and SFCompute were each faster in 1 of 2 shared sandbox benchmarks. In Burst TTI (November 13, 2026), Gravixlayer had a median time to interactive of 400ms versus 621ms for SFCompute, 1.55x faster. In DAX (November 13, 2026), SFCompute had a median total workload time of 39.91s versus 59.08s for Gravixlayer, 1.48x 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: Gravixlayer 100%, SFCompute 100%; DAX: Gravixlayer 100%, SFCompute 100%.

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