Gravixlayer vs PromigenceSandbox Benchmark Comparison

GravixlayerPre-release
Faster in 0 of 2
vs
PromigencePre-release
Faster in 2 of 2

Promigence was faster in both shared sandbox benchmarks.

Shared benchmarks
2
Last run
October 30, 2026
Want the full run details?Sign up free →

Scorecard

Median of each benchmark's primary metric; lower is better. Medians within 5% count as roughly even, and a benchmark gets no speed verdict when either provider completed fewer than 50% of runs.

BenchmarkGravixlayerPromigenceResultRatio
Burst TTI
Time to interactive · Run October 30, 2026
102ms
100% success
65ms
100% success
Promigence faster
1.56x
DAX
Total workload time · Run October 30, 2026
58.66s
100% success
36.19s
100% success
Promigence faster
1.62x

Burst TTI

Run October 30, 2026

Time from sandbox creation to the first successful command, with 100 sandboxes launched at the same time.

Time to interactive

Gravixlayer

100% success
Median
102ms
P95
107ms
P99
107ms
Gravixlayer Burst TTI results →

Promigence

100% success
Median
65ms
P95
82ms
P99
86ms
Promigence Burst TTI results →

Promigence had a 1.56x lower median time to interactive (65ms vs 102ms for Gravixlayer).

Median time to interactive over time

2 runs from October 23, 2026 to October 30, 2026.

GravixlayerPromigence
View the full Burst TTI leaderboard →

DAX

Run October 30, 2026

A real developer workload: install system packages, download Bun, clone the opencode repo, then run bun install and bun typecheck.

Total workload time

Gravixlayer

100% success
Median
58.66s
P95
58.66s
P99
58.66s
Gravixlayer DAX results →

Promigence

100% success
Median
36.19s
P95
36.19s
P99
36.19s
Promigence DAX results →

Promigence had a 1.62x lower median total workload time (36.19s vs 58.66s for Gravixlayer).

Median total workload time over time

3 runs from October 20, 2026 to October 30, 2026.

GravixlayerPromigence
View the full DAX leaderboard →

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 only when both providers completed at least 50% of runs in 2 or more shared benchmarks run in the last 30 days.

Frequently asked questions

Have another question? Email us.

Promigence was faster in both shared sandbox benchmarks. In Burst TTI (October 30, 2026), Promigence had a median time to interactive of 65ms versus 102ms for Gravixlayer, 1.56x faster. In DAX (October 30, 2026), Promigence had a median total workload time of 36.19s versus 58.66s for Gravixlayer, 1.62x faster.

PartnersGoogle Cloud Run