Isorun was faster in both shared sandbox benchmarks.
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.
Time from sandbox creation to the first successful command, with 100 sandboxes launched at the same time.
Time to interactive
Isorun had a 15.4x lower median time to interactive (49ms vs 751ms for Modal).
46 runs from June 17, 2026 to 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
Isorun had a 2.92x lower median total workload time (36.13s vs 105.55s for Modal).
13 runs from August 7, 2026 to October 30, 2026.
Each provider's DAX median total workload time (run October 30, 2026) multiplied by its published rate at the 8 vCPU / 16 GiB benchmark spec. Workload time excludes sandbox create and destroy, and subscription floors and included credits are not modeled.
$0.025/vCPU-hr + $0.015/GiB-hr. Published profile for 8 vCPU + 16 GiB is exactly $0.44/hr.
Source pricing pageSandbox rate $0.00003942/core-s (4 cores = 8 vCPU) + $0.00000667/GiB-s. Regional multipliers (1.25–2.5x) not included.
Source pricing pageHave another question? Email us.
Isorun was faster in both shared sandbox benchmarks. In Burst TTI (October 30, 2026), Isorun had a median time to interactive of 49ms versus 751ms for Modal, 15.4x faster. In DAX (October 30, 2026), Isorun had a median total workload time of 36.13s versus 105.55s for Modal, 2.92x faster.