Start by picking a release window. You'll choose the sandbox or offline build next, then your platform — each combination has its own page with the exact release and its requirements.
Morning batch. Windows and macOS, sandbox or offline.
Choose this window → 02 release window 9:00 AMMid-morning batch. Windows and macOS, sandbox or offline.
Choose this window → 03 release window 10:30 AMLate-morning batch. Windows and macOS, sandbox or offline.
Choose this window → 04 release window 7:30 PMEvening batch. Windows and macOS, sandbox or offline.
Choose this window →| Component | Minimum | Recommended |
|---|---|---|
| OS | Windows 10 / macOS 12 | Windows 11 / macOS 14+ |
| RAM | 4 GB | 8 GB+ |
| Storage | 1.2 GB free | 3 GB free (offline build) |
| Network | Required for online sandbox | Not required for offline build |
Both builds run the identical nine-stage boot sequence — the difference is whose cloud accounts they run against and how much you can push through them.
The online sandbox runs against shared accounts we manage across AWS, Azure, and GCP. It's rate-limited and goes through a short automated review before it activates, because it's sharing capacity with everyone else on the same release window. That trade-off is what makes it free — it's built for coursework, demos, and trying out a stage you haven't used before without touching your own billing.
The offline build installs locally and runs the same sequence against your own cloud credentials. There's no shared capacity, so no queue and no rate limit — the boot log reflects your actual account limits, not ours. It's the version to use once you're past learning the sequence and are building something you intend to keep.
Windows 10/11 or macOS 12+. The installer detects your OS automatically above, but both are available from either card.
Sandbox needs nothing else to start. Offline asks for cloud credentials on first launch — these stay local and are never sent to us.
The terminal view streams all nine stages live. A clean first boot ends with stage 9 (traffic) reporting healthy — anything short of that means a stage needs attention before you continue.
Sandboxes auto-expire at the end of their release window. Offline builds tear down on command, rotating any credentials the identity stage generated.