Sandbox benchFull results

E2B vs Daytona

We timed E2B and Daytona through one SDK, alongside 7 other sandbox providers, on two tracks: the same 4 vCPU, 8 GB machine for every provider, and each provider's default machine. Every result is a median with its p95 and 95% interval. When the two medians sit inside each other's intervals, we call it a tie.

Sandbox bench runs on Sandbox SDK, which the same team (opencoredev) builds. We may work with some of these providers. No provider paid for these results or decided how they were tested.

Same machine: 4 vCPU, 8 GB

E2B is ahead on 9 of the 23 tests both finished, Daytona on 13, and 1 is tied within their 95% intervals.

  • Median cold start E2B 0.79 s vs Daytona 1.3 s (E2B ahead).
  • Median agent tool replay E2B 15 s vs Daytona 12 s (Daytona ahead).

Default machines

E2B is ahead on 10 of the 23 tests both finished, Daytona on 11, and 2 are tied within their 95% intervals.

  • Median cold start E2B 0.50 s vs Daytona 1.5 s (E2B ahead).
  • Median agent tool replay E2B 16 s vs Daytona 15 s (Daytona ahead).

E2B vs Daytona on the same 4 vCPU, 8 GB machine

Every provider asked for Boat's machine, 4 vCPU and 8 GB, or its nearest size. Runs from 2026-10-22 to 2026-10-23, 9 providers. E2B is ahead on 9 of the 23 tests both finished, Daytona on 13, and 1 is tied within their 95% intervals. Ranks are out of every provider on this track; see them all on the full results.

E2B

Measured inside
4 vCPU, 7.8 GB
Cost per 1,000 tasks
$1.56 (metered)
Success rate
100.00% (1,073 of 1,073)
Pause and resume
pause 1.29 s, resume 0.51 s (median of 100)
  • Asked for: 4 vCPU, 8 GB, template r1h7gud12rf1f6iu29r0.
  • Ran in: The Dalles, US.
  • Cost: $0.0016 per task, their own usage records at published rates (metered over 10 tasks, medium confidence).
  • Failures counted against E2B: none.

Daytona

Measured inside
4 vCPU, 8 GB
Cost per 1,000 tasks
$1.36 (billed)
Success rate
100.00% (976 of 976)
Pause and resume
Daytona's container sandboxes have no pause: stop and start restarts the sandbox and ends every running process.
  • Asked for: 4 vCPU, 8 GB, template daytona-large.
  • Cost: $0.0014 per task, from its bill (billed over 10 tasks, low confidence).
  • Failures counted against Daytona: none.

E2B's cost is metered and Daytona's is billed, so the two aren't directly comparable. A task is: create a sandbox, run the 100-call tool replay, delete it. Cost per task comes from a separate cost run, billed per sandbox.

Start-up

TestE2BDaytonaAhead
Cold start (lower is better)0.79 s 4th of 9p95 2.2 s95%: 0.71 s to 0.82 s1.3 s 8th of 9p95 2.1 s95%: 1.1 s to 1.3 sE2B

Agent work

TestE2BDaytonaAhead
Agent tool replay (lower is better)15 s 3rd of 9p95 17 s95%: 15 s to 16 s12 s 1st of 9p95 30 s95%: 12 s to 13 sDaytona
npm install (lower is better)1.8 s 9th of 9p95 2.9 s95%: 1.7 s to 1.9 s0.75 s 1st of 9p95 0.91 s95%: 0.73 s to 0.77 sDaytona
pip install (lower is better)4.9 s 7th of 9p95 8.2 s95%: 4.2 s to 5.0 s4.2 s 5th of 9p95 5.5 s95%: 4.0 s to 4.3 sDaytona
git clone (lower is better)1.2 s 6th of 9p95 2.1 s95%: 1.1 s to 1.3 s0.43 s 1st of 9p95 1.0 s95%: 0.42 s to 0.45 sDaytona
Dev server ready (lower is better)2.2 s 3rd of 9p95 3.4 s95%: 2.1 s to 2.3 s2.6 s 5th of 9p95 6.6 s95%: 2.5 s to 2.6 sE2B
Preview URL first byte (lower is better)0.27 s 3rd of 9p95 0.49 s95%: 0.27 s to 0.28 s0.25 s 2nd of 9p95 0.44 s95%: 0.25 s to 0.27 sDaytona
Edit, rebuild, reload (lower is better)0.33 s 3rd of 9p95 0.56 s95%: 0.32 s to 0.34 s0.31 s 2nd of 9p95 0.76 s95%: 0.30 s to 0.34 sDaytona

Everyday calls

TestE2BDaytonaAhead
Run a command (lower is better)0.13 s 1st of 9p95 0.19 s95%: 0.13 s to 0.14 s0.13 s 2nd of 9p95 0.30 s95%: 0.13 s to 0.14 sTied
Write + read 1 KB (lower is better)0.23 s 4th of 9p95 0.38 s95%: 0.23 s to 0.24 s0.18 s 2nd of 9p95 0.52 s95%: 0.17 s to 0.18 sDaytona
Write + read 10 MB (lower is better)1.3 s 3rd of 9p95 2.3 s95%: 1.3 s to 1.4 s1.0 s 2nd of 9p95 2.7 s95%: 1.0 s to 1.1 sDaytona
Reconnect (lower is better)0.46 s 3rd of 9p95 1.8 s95%: 0.45 s to 0.46 s0.30 s 1st of 9p95 0.71 s95%: 0.28 s to 0.32 sDaytona
Destroy (lower is better)0.11 s 1st of 9p95 0.15 s95%: 0.11 s to 0.12 s0.85 s 8th of 9p95 2.5 s95%: 0.80 s to 0.90 sE2B

Pause and snapshots

TestE2BDaytonaAhead
Pause + resume (lower is better)1.8 s 5th of 6p95 3.5 s95%: 1.6 s to 2.0 sDaytona's container sandboxes have no pause: stop and start restarts the sandbox and ends every running process.n/a
Take snapshot (lower is better)1.8 s 3rd of 8p95 2.2 s95%: 1.1 s to 2.0 s7.4 s 8th of 8p95 49 s95%: 6.8 s to 12 sE2B
Start from snapshot (lower is better)1.1 s 3rd of 8p95 3.2 s95%: 0.82 s to 1.6 s2.4 s 7th of 8p95 4.6 s95%: 2.3 s to 3.0 sE2B

Bursts

TestE2BDaytonaAhead
10 at once, all ready (lower is better)In one of its three bursts of 10, two creates failed on E2B's side (E2B reported a timeout), so only 2 of 3 bursts finished and the size is not published; coming in the next update2.9 s 7th of 8p95 9.9 s95%: 2.3 s to 9.9 sn/a
25 at once, all ready (lower is better)1.1 s 2nd of 9p95 1.3 s95%: 0.94 s to 1.3 s5.3 s 7th of 9p95 5.6 s95%: 2.3 s to 5.6 sE2B

Machine speed

TestE2BDaytonaAhead
CPU, one core (higher is better)10.3M/s 7th of 9p95 15.3M/s95%: 9.8M/s to 10.6M/s9.2M/s 9th of 9p95 10.1M/s95%: 9.1M/s to 9.3M/sE2B
CPU, all cores (higher is better)26.5M/s 8th of 9p95 37.8M/s95%: 24.8M/s to 27M/s25.9M/s 9th of 9p95 28.5M/s95%: 25.3M/s to 26.3M/sE2B
Memory bandwidth (higher is better)12.3 GB/s 9th of 9p95 14.0 GB/s95%: 11.7 GB/s to 12.7 GB/s29.9 GB/s 5th of 9p95 33.2 GB/s95%: 29.3 GB/s to 30.9 GB/sDaytona
Disk write (higher is better)867 MB/s 4th of 9p95 1.0 GB/s95%: 750 MB/s to 902 MB/s1.4 GB/s 3rd of 9p95 2.9 GB/s95%: 1.2 GB/s to 1.9 GB/sDaytona
Disk read (higher is better)6.2 GB/s 8th of 9p95 7.5 GB/s95%: 5.9 GB/s to 6.4 GB/s17.3 GB/s 4th of 9p95 18.9 GB/s95%: 16.7 GB/s to 17.7 GB/sDaytona
4K random write (higher is better)6.9K IOPS 5th of 9p95 8.9K IOPS95%: 6.6K IOPS to 7.1K IOPS20.9K IOPS 2nd of 9p95 30K IOPS95%: 19.6K IOPS to 22.1K IOPSDaytona
4K random read (higher is better)453K IOPS 5th of 9p95 601.5K IOPS95%: 436.3K IOPS to 476.2K IOPS343K IOPS 7th of 9p95 403.6K IOPS95%: 337.3K IOPS to 364.1K IOPSE2B

E2B vs Daytona on each one's default machine

Each provider's default sandbox, so machine sizes differ. Runs from 2026-10-22 to 2026-10-23, 9 providers. E2B is ahead on 10 of the 23 tests both finished, Daytona on 11, and 2 are tied within their 95% intervals. Ranks are out of every provider on this track; see them all on the full results.

E2B

Measured inside
2 vCPU, 473 MB
Cost per 1,000 tasks
$0.49 (metered)
Success rate
100.00% (1,076 of 1,076)
Pause and resume
pause 0.26 s, resume 0.45 s (median of 100)
  • Asked for: 2 vCPU, 512 MB, template base.
  • Machine: E2B's default base template is 2 vCPU and 512 MB. E2B's pricing page says its default sandbox has 4 GB, so E2B ran smaller here than that.
  • Ran in: The Dalles, US.
  • Cost: $0.00049 per task, their own usage records at published rates (metered over 10 tasks, medium confidence).
  • Failures counted against E2B: none.

Daytona

Measured inside
1 vCPU, 1 GB
Cost per 1,000 tasks
$0.64 (billed)
Success rate
100.00% (973 of 973)
Pause and resume
Daytona's container sandboxes have no pause: stop and start restarts the sandbox and ends every running process.
  • Asked for: 1 vCPU, 1 GB.
  • Cost: $0.00064 per task, from its bill (billed over 10 tasks, low confidence).
  • Failures counted against Daytona: none.

E2B's cost is metered and Daytona's is billed, so the two aren't directly comparable. A task is: create a sandbox, run the 100-call tool replay, delete it. Cost per task comes from a separate cost run, billed per sandbox.

Start-up

TestE2BDaytonaAhead
Cold start (lower is better)0.50 s 1st of 9p95 2.0 s95%: 0.48 s to 0.51 s1.5 s 8th of 9p95 2.8 s95%: 1.4 s to 1.6 sE2B

Agent work

TestE2BDaytonaAhead
Agent tool replay (lower is better)16 s 3rd of 9p95 18 s95%: 16 s to 17 s15 s 2nd of 9p95 34 s95%: 13 s to 18 sDaytona
npm install (lower is better)2.1 s 9th of 9p95 2.8 s95%: 2.0 s to 2.3 s1.2 s 4th of 9p95 1.4 s95%: 1.2 s to 1.3 sDaytona
pip install (lower is better)5.0 s 8th of 9p95 6.0 s95%: 4.8 s to 5.1 s4.6 s 7th of 9p95 6.2 s95%: 4.3 s to 4.7 sDaytona
git clone (lower is better)1.2 s 5th of 9p95 2.6 s95%: 1.1 s to 1.2 s0.62 s 2nd of 9p95 0.97 s95%: 0.47 s to 0.87 sDaytona
Dev server ready (lower is better)2.3 s 4th of 9p95 3.3 s95%: 2.2 s to 2.6 s2.8 s 5th of 9p95 6.8 s95%: 2.6 s to 3.6 sE2B
Preview URL first byte (lower is better)0.27 s 2nd of 9p95 0.53 s95%: 0.26 s to 0.28 s0.28 s 3rd of 9p95 0.46 s95%: 0.26 s to 0.31 sE2B
Edit, rebuild, reload (lower is better)0.34 s 2nd of 9p95 0.59 s95%: 0.33 s to 0.36 s0.34 s 3rd of 9p95 0.96 s95%: 0.33 s to 0.45 sTied

Everyday calls

TestE2BDaytonaAhead
Run a command (lower is better)0.14 s 1st of 9p95 0.15 s95%: 0.14 s to 0.14 s0.14 s 2nd of 9p95 0.31 s95%: 0.13 s to 0.17 sTied
Write + read 1 KB (lower is better)0.24 s 5th of 9p95 0.26 s95%: 0.23 s to 0.24 s0.18 s 2nd of 9p95 0.53 s95%: 0.17 s to 0.18 sDaytona
Write + read 10 MB (lower is better)1.3 s 3rd of 9p95 2.4 s95%: 1.3 s to 1.4 s1.2 s 2nd of 9p95 2.5 s95%: 1.2 s to 1.3 sDaytona
Reconnect (lower is better)0.46 s 3rd of 9p95 0.68 s95%: 0.46 s to 0.46 s0.31 s 1st of 9p95 0.77 s95%: 0.29 s to 0.34 sDaytona
Destroy (lower is better)0.11 s 1st of 9p95 0.12 s95%: 0.11 s to 0.11 s0.96 s 8th of 9p95 3.2 s95%: 0.90 s to 1.1 sE2B

Pause and snapshots

TestE2BDaytonaAhead
Pause + resume (lower is better)0.74 s 3rd of 6p95 3.6 s95%: 0.72 s to 0.84 sDaytona's container sandboxes have no pause: stop and start restarts the sandbox and ends every running process.n/a
Take snapshot (lower is better)0.34 s 1st of 8p95 0.67 s95%: 0.32 s to 0.39 s10 s 8th of 8p95 336 s95%: 7.5 s to 15 sE2B
Start from snapshot (lower is better)0.75 s 3rd of 8p95 1.2 s95%: 0.55 s to 0.92 s2.6 s 7th of 8p95 6.8 s95%: 2.3 s to 3.2 sE2B

Bursts

TestE2BDaytonaAhead
10 at once, all ready (lower is better)1.1 s 4th of 9p95 1.1 s95%: 0.62 s to 1.1 s2.0 s 6th of 9p95 2.8 s95%: 1.7 s to 2.8 sE2B
25 at once, all ready (lower is better)0.87 s 2nd of 8p95 1.2 s95%: 0.83 s to 1.2 sIn one of its three bursts of 25, one create timed out on Daytona's side (24 of 25 ready), so only 2 of 3 bursts finished and the size is not published; coming in the next updaten/a

Machine speed

TestE2BDaytonaAhead
CPU, one core (higher is better)10M/s 7th of 9p95 15.3M/s95%: 9.7M/s to 10.6M/s9.1M/s 9th of 9p95 13.7M/s95%: 8.9M/s to 9.3M/sE2B
CPU, all cores (higher is better)14.1M/s 7th of 9p95 20.2M/s95%: 13.9M/s to 14.9M/s6.9M/s 9th of 9p95 10.3M/s95%: 6.8M/s to 7M/sE2B
Memory bandwidth (higher is better)12.3 GB/s 9th of 9p95 14.2 GB/s95%: 12.1 GB/s to 12.7 GB/s31.0 GB/s 5th of 9p95 57.0 GB/s95%: 30.3 GB/s to 31.9 GB/sDaytona
Disk write (higher is better)949 MB/s 4th of 9p95 1.1 GB/s95%: 885 MB/s to 996 MB/s1.2 GB/s 3rd of 9p95 2.9 GB/s95%: 1.1 GB/s to 1.3 GB/sDaytona
Disk read (higher is better)6.2 GB/s 8th of 9p95 7.6 GB/s95%: 6.1 GB/s to 6.5 GB/s16.2 GB/s 4th of 9p95 28.8 GB/s95%: 15.9 GB/s to 16.6 GB/sDaytona
4K random write (higher is better)7.2K IOPS 5th of 9p95 8.8K IOPS95%: 6.8K IOPS to 7.5K IOPS20.2K IOPS 2nd of 9p95 29.6K IOPS95%: 18.6K IOPS to 20.9K IOPSDaytona
4K random read (higher is better)467K IOPS 5th of 9p95 643K IOPS95%: 451.7K IOPS to 479.1K IOPS342.4K IOPS 7th of 9p95 774.7K IOPS95%: 323.9K IOPS to 348.6K IOPSE2B

How to read these numbers

  • Daytona was re-collected on Oct 22 after its account quota was raised from 10 vCPU / 10 GiB; earlier Daytona numbers were limited by that quota.
  • Daytona's billed cost can still change for up to 48 hours.
  • Every call starts from one server in Florida, US. Providers hosted farther away pay that round trip on every call; Boat (France) and boxd (Germany) pay a transatlantic one.
  • There are two tracks. Same machine: 4 vCPU, 8 GB: Every provider asked for Boat's machine, 4 vCPU and 8 GB, or its nearest size. A provider marked “machine differs” measured something else inside. Default machines: Each provider's default sandbox, so machine sizes differ.
  • Cost per task has a kind. Billed comes from the provider's bill, metered from its usage records at published rates, and estimate from our measured time at list price. Kinds are not directly comparable. Prices cover compute only at list rates: disk, transfer, subscriptions and credits are excluded.
  • Pause and resume times come from the previous SDK run, because the newest runs skipped them. A burst size is published only when all three bursts finished.
  • Failures caused by our own code are set aside, not counted. Every provider-side failure is kept.
  • Ranks compare medians. Medians inside each other's 95% intervals count as tied, so a close rank can be noise.

More results