Skip to content

DAX Benchmark: CreateOS

CreateOS

Phases Completed

0/7 phases
○ Prepare○ Cache Clear○ Bun Download○ Bun Unpack○ Clone○ Install○ Typecheck
Latest Error
sandbox create failed after 2213ms: createos-sandbox request failed (429): sandbox per-day quota reached (50 / 50). Try again in 24h or contact an operator.

Estimated Cost

Median workload time x published rates at the 8 vCPU / 16 GiB sandbox spec. Excludes sandbox create/destroy time.

Cost / Workload
—
Rate @ 8 vCPU / 16 GiB
$0.6624/hr
Billing Model
Per-second wall clock
1,000 Workloads / Month
—

$0.0504/vCPU-hr + $0.0162/GiB-hr — parity with E2B. No egress fees. Source · Compare all providers

Total Duration

Failed
This phase never completed in the latest run, so there's no duration to show.

Prepare

Failed
This phase never completed in the latest run, so there's no duration to show.

Bun Download

Failed
This phase never completed in the latest run, so there's no duration to show.

Bun Unpack

Failed
This phase never completed in the latest run, so there's no duration to show.

Clone

Failed
This phase never completed in the latest run, so there's no duration to show.

Install

Failed
This phase never completed in the latest run, so there's no duration to show.

Typecheck

Failed
This phase never completed in the latest run, so there's no duration to show.

Raw Iterations

Each iteration runs the full clone + install + typecheck cycle from a fresh sandbox.

#PhasesTotalPrepareBun DLBun UnpackCloneInstallTypecheckError
10/70.00s——————sandbox create failed after 2213ms: createos-sandbox request failed (429): sandbox per-day quota reached (50 / 50). Try again in 24h or contact an operator.

Methodology

What We Measure

Each run executes a cold clone + install + typecheck cycle of the opencode repository inside a fresh sandbox: install system packages and Node.js, download and unpack Bun, shallow-clone opencode at a pinned commit, run bun install, then bun typecheck.

Each provider runs 1 iteration per scheduled benchmark run. Benchmarks run via GitHub Actions and results are committed to the public benchmarks repo.

How We Score

The Composite Score is the median number of the 7 benchmark phases (prepare, cache clear, bun download, bun unpack, clone, install, typecheck) a provider completed before failing, if any — shown as a fraction like 7/7.

The other metrics (Total, Prepare, Clone, Install, Typecheck) are real-world phase durations in seconds — providers are ranked by median duration (lower is better) when one of those is selected. The benchmark requires curl, root/sudo, and a package manager (apt, dnf, or apk) inside the sandbox — providers without those capabilities fail early, which shows up as a low phase count.