Sandbox Provider Leaderboard
Sandbox Benchmarks
A leaderboard of common benchmarks for each of our sandbox providers.
Performance Over Time
Composite Score
Detailed Metrics
Provider | Score | Median | P95 | P99 | Success |
|---|---|---|---|---|---|
| Declaw | 97.9 | 0.19s | 0.23s | 0.23s | 100% |
| Daytona | 95.7 | 0.34s | 0.56s | 0.60s | 100% |
| Tensorlake | 91.7 | 0.57s | 1.22s | 1.22s | 100% |
| Archil | 92.7 | 0.69s | 0.79s | 0.81s | 100% |
| E2B | 92.4 | 0.69s | 0.82s | 0.93s | 100% |
| Vercel | 90.0 | 0.77s | 1.25s | 1.50s | 100% |
| Upstash | 83.6 | 1.01s | 2.56s | 2.64s | 100% |
| Blaxel | 81.8 | 1.63s | 2.09s | 2.13s | 100% |
| Cloudflare | 77.7 | 1.97s | 2.51s | 2.80s | 100% |
| Namespace | 44.0 | 2.21s | 14.35s | 14.61s | 94% |
| Runloop | 32.7 | 4.79s | 9.42s | 13.56s | 100% |
| CodeSandbox | 11.3 | 8.11s | 15.66s | 18.89s | 100% |
Want to see a provider added?
Methodology
What We Measure
Every benchmark measures Time to Interactive (TTI) — the elapsed time from calling compute.sandbox.create() to the first successful runCommand() inside the sandbox.
Each provider is tested with 100 iterations per run. Benchmarks run automatically via GitHub Actions on a recurring schedule. All results are committed to the public benchmarks repo.
Sequential Test: Sandboxes are launched one at a time, waiting for each to become interactive before starting the next.
Staggered Test: Sandboxes are launched with 200ms delays between each.
Burst Test: All sandboxes are launched concurrently in a single burst.
How We Score
The Composite Score is a weighted blend of timing metrics multiplied by the success rate. Each metric is scored against a fixed 10-second ceiling: 100 × (1 − value / 10,000ms), so a 200ms median scores 98 and anything ≥10s scores 0.
The weighted timing score is then multiplied by the success rate (0–1), so providers that fail frequently are penalized proportionally.
- • Median: 60% — primary signal for typical experience
- • P95: 25% — tail latency / consistency
- • P99: 15% — extreme tail latency
Sandbox Benchmarks FAQs
Have another question? Email us.