> ## Documentation Index
> Fetch the complete documentation index at: https://docs.leamout.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Installation

> Initialize a staged Leamout self-hosted runtime with the operator CLI.

The production CLI and runtime are released as versioned Linux `amd64` artifacts. The runtime archive follows the naming convention:

```text theme={null}
leamout_runtime_<VERSION>_linux_amd64.tar.gz
```

The installer stages the runtime matching the exact CLI version. After the CLI and release bundle are present, initialize the deployment:

```bash theme={null}
sudo leamout init
```

`init` creates a durable deployment UUID, generates deployment-owned secrets, writes production configuration, and installs/verifies the staged runtime bundle.

A new initialization writes state under `/var/lib/leamout` and configuration under `/etc/leamout`. Re-running `init` preserves an existing valid deployment identity and secrets while re-verifying/installing the matching runtime bundle.

Then validate the local installation:

```bash theme={null}
sudo leamout doctor
```

and start it:

```bash theme={null}
sudo leamout up
```

<Warning>
  The target design describes hosted activation and a public bootstrap endpoint, but the current `leamout init` implementation does not accept an activation token. Do not rely on `--activation-token` until that workflow ships.
</Warning>