Install
Choose how to install
One server, Kubernetes, or a site with no internet access. Every path runs the same images and starts in setup mode.
| If you have… | Use | Guide |
|---|---|---|
| A Linux server or VM | The installer from the bundle | Linux |
| Windows Server | A Linux VM on Hyper-V (recommended) or WSL2, then the installer | Windows Server |
| A Mac, for evaluation | Podman or Docker Desktop, then the installer | macOS |
| A Kubernetes cluster | The Helm chart | Kubernetes |
| No internet access on site | The air-gapped bundle (everything inside, signed) | Air-gapped |
| A team that prefers Compose | compose.yaml from the bundle | Linux → Compose |
Whichever you choose, 3AM starts in setup mode. You open the console, install the licence and connect your tools. Nothing operates until a valid licence is installed. You never need to edit configuration files, but you can if you prefer to manage 3AM as code (configuration files).
What the installer does
Checks the host: CPUs, memory, free disk, that the port is free, and where the install fingerprint comes from.
Picks the model profile: an NVIDIA or AMD GPU means the GPU profile; otherwise the CPU profile.
Verifies the bundle: every file against
SHA256SUMS, and SHA256SUMS against the 3AM release key.Loads the images and the model weights from the bundle. An install from a bundle never downloads anything.
Starts
3am-model (internal only) and 3am-core (read-only root filesystem, no capabilities, a health check).Runs preflight and prints the console address and the admin token.
Running the installer again upgrades in place: containers are replaced; the data, the admin token and the ingest token are kept.