Sandbox Benchmark Comparison · Updated November 20, 2026
Daytona and SFCompute were each faster in 1 of 2 shared sandbox benchmarks.
$0.000014/vCPU-s + $0.0000045/GiB-s — identical rates to E2B. Creating/stopping transitions bill as running.
Source pricing pageRollout 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 pageHave another question? Email us.
Daytona and SFCompute were each faster in 1 of 2 shared sandbox benchmarks. In Burst TTI (November 20, 2026), Daytona had a median time to interactive of 483ms versus 621ms for SFCompute, 1.29x faster. In DAX (November 20, 2026), SFCompute had a median total workload time of 39.91s versus 77.85s for Daytona, 1.95x 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: Daytona 100%, SFCompute 100%; DAX: Daytona 100%, SFCompute 100%.
Burst TTI and DAX results are from November 20, 2026.