Daytona vs Tenki

Sandbox Benchmark Comparison · Updated October 30, 2026

Daytona and Tenki were each faster in 1 of 2 shared sandbox benchmarks.

Head to head

  • Burst TTITime to interactive · lower is better
    Daytona faster3.15x
    Daytona
    668ms
    Tenki
    2.10s
  • DAXTotal workload time · lower is better
    Tenki faster1.22x
    Daytona
    74.40s
    Tenki
    60.78s

Burst TTI

October 30, 2026

Daytona

100% success
Median
668ms
p95
747ms
p99
860ms
Daytona Burst TTI results

Tenki

100% success
Median
2.10s
p95
2.18s
p99
2.18s
Tenki Burst TTI results

Median time to interactive over time

18 runs · July 24, 2026 to October 30, 2026
DaytonaTenki

Daytona

100% success · October 23, 2026
Median
74.40s
Daytona DAX results

Tenki

100% success · October 30, 2026
Median
60.78s
Tenki DAX results

Median total workload time over time

16 runs · July 31, 2026 to October 23, 2026
DaytonaTenki

Cost per DAX run

Daytona

Per-second wall clock
$0.014per run
74.40s median at $0.6624/hr

$0.000014/vCPU-s + $0.0000045/GiB-s — identical rates to E2B. Creating/stopping transitions bill as running.

Source pricing page

Tenki

Per-second wall clock
$0.011per run
60.78s median at $0.6624/hr

$0.000014/vCPU-s + $0.0000045/GiB-s; usage draws from monthly workspace credits first.

Source pricing page
Compare sandbox costs across all providers →
Work at Daytona or Tenki? See where you stand every day, with full run logs, not just on benchmark Friday.Get stealth benchmarks →

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. If a provider’s latest run of a benchmark failed, its most recent successful run from that window is used instead.

Frequently asked questions

Have another question? Email us.

Daytona and Tenki were each faster in 1 of 2 shared sandbox benchmarks. In Burst TTI (October 30, 2026), Daytona had a median time to interactive of 668ms versus 2.10s for Tenki, 3.15x faster. In DAX (October 23, 2026), Tenki had a median total workload time of 60.78s versus 74.40s for Daytona, 1.22x faster.

PartnersGoogle Cloud Run