Promigence vs SuperserveSandbox Benchmark Comparison

PromigencePre-release
Faster in 2 of 2
vs
Superserve
Faster in 0 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.

BenchmarkPromigenceSuperserveResultRatio
Burst TTI
Time to interactive · Run October 30, 2026
65ms
100% success
371ms
100% success
Promigence faster
5.69x
DAX
Total workload time · Run October 30, 2026
36.19s
100% success
64.26s
100% success
Promigence faster
1.78x

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

Promigence

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

Superserve

100% success
Median
371ms
P95
655ms
P99
705ms
Superserve Burst TTI results →

Promigence had a 5.69x lower median time to interactive (65ms vs 371ms for Superserve).

Median time to interactive over time

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

PromigenceSuperserve
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

Promigence

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

Superserve

100% success
Median
64.26s
P95
64.26s
P99
64.26s
Superserve DAX results →

Promigence had a 1.78x lower median total workload time (36.19s vs 64.26s for Superserve).

Median total workload time over time

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

PromigenceSuperserve
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 371ms for Superserve, 5.69x faster. In DAX (October 30, 2026), Promigence had a median total workload time of 36.19s versus 64.26s for Superserve, 1.78x faster.

PartnersGoogle Cloud Run