RELEASE WINDOW · 7:30 AM

Sandbox or offline build?

Both run the identical nine-stage boot sequence. The difference is whose cloud accounts they run against, and how hard you can push them.

step 2 of 3 — pick a build
SHARED CAPACITY · REVIEWED

Online sandbox

Runs the full nine-stage sequence against shared accounts we manage across AWS, Azure, and GCP. Rate-limited, and it goes through a short automated review before activating, because capacity is shared with everyone else on the same release window. That trade-off is what keeps it free.

  • Activates after a short automated review within this release window
  • Rate-limited, since capacity is shared
  • Needs no cloud credentials of your own
  • Auto-expires at the end of the release window
Choose online sandbox →
YOUR ACCOUNTS · NO QUEUE

Offline build

Installs locally and runs the same nine-stage sequence against your own cloud credentials. No shared capacity, so no queue and no rate limit — the boot log reflects your actual account limits rather than ours.

  • Unlocks immediately — no review queue
  • No rate limits; your account limits apply instead
  • Asks for cloud credentials on first launch; these stay local and are never sent to us
  • Credentials are held in an OS-native secret store (since v2.4.0)
Choose offline build →

← Back to release windows