04 — INSTALL

Get Cloud iNIT

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.

step 1 of 3 — pick a release window
01 release window 7:30 AM

Morning batch. Windows and macOS, sandbox or offline.

Choose this window →
02 release window 9:00 AM

Mid-morning batch. Windows and macOS, sandbox or offline.

Choose this window →
03 release window 10:30 AM

Late-morning batch. Windows and macOS, sandbox or offline.

Choose this window →
04 release window 7:30 PM

Evening batch. Windows and macOS, sandbox or offline.

Choose this window →
system requirements
ComponentMinimumRecommended
OSWindows 10 / macOS 12Windows 11 / macOS 14+
RAM4 GB8 GB+
Storage1.2 GB free3 GB free (offline build)
NetworkRequired for online sandboxNot required for offline build
choosing a build

Online sandbox or 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.

1

Pick a platform

Windows 10/11 or macOS 12+. The installer detects your OS automatically above, but both are available from either card.

2

Choose sandbox or offline

Sandbox needs nothing else to start. Offline asks for cloud credentials on first launch — these stay local and are never sent to us.

3

Watch the first boot

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.

4

Tear down when you're done

Sandboxes auto-expire at the end of their release window. Offline builds tear down on command, rotating any credentials the identity stage generated.

release notes

Recent changelog

v3.0.0

Nine-stage sequence, AI-managed drift correction

  • Reconciler now auto-corrects drift between the secrets and data stages where policy allows
  • ap-south-1 added for compute, storage, and networking stages
  • Boot log export to JSON for CI pipelines
v2.4.0

Offline build credential isolation

  • Offline builds now store cloud credentials in an OS-native secret store instead of a local config file
  • Reduced cold-boot time for the identity stage by roughly a third
v2.3.0

macOS support, sandbox review window

  • Native macOS build, previously Windows-only
  • Sandbox activation review shortened from 24h to the current short window
before you install

Install FAQ

Do I need admin rights to install the offline build?
On Windows, yes — the installer registers a local service that runs the boot engine. On macOS, a standard user account is enough; no root privileges are required.
Can I switch from the sandbox to an offline build later without starting over?
Yes. Boot logs and stage configuration export from a sandbox session and import into an offline build, so you don't have to re-walk the sequence from stage 1 — only the credentials at the identity stage need to be re-issued against your own accounts.
What if the installer fails partway through?
Re-running the installer resumes from the last completed step rather than starting over. If a step keeps failing, the installer log (written next to the installer) will show which prerequisite — usually available disk space or a blocked network port — is missing.
How do I uninstall cleanly?
Uninstalling tears down any active sandboxes first, rotates or revokes credentials the identity stage issued, then removes the local install. Running the uninstaller directly — rather than deleting the app folder by hand — is what triggers that teardown.

Not sure which build?

Online sandboxes are free and reviewed within your batch window. Offline builds skip the queue entirely.