Install

Each Ordo component installs on the machine that runs it. The install script downloads a prebuilt binary, verifies its SHA-256 checksum, and checks the minisign signature when minisign is installed. Debian and RPM packages are published alongside the archives in the same release.

Install Ordo

Operator workstation

The machine you operate Ordo from gets the ordo operator CLI and ordo-state (module authoring and validation). This is the default install:

Linux / macOS

curl -fsSL https://getordo.dev/install.sh | sh

Windows

irm https://getordo.dev/install.ps1 | iex

Orchestrator host

The control host gets ordo-orchestrator:

Linux / macOS

curl -fsSL https://getordo.dev/install.sh | sh -s -- ordo-orchestrator

Windows

& ([scriptblock]::Create((irm https://getordo.dev/install.ps1))) -Bin ordo-orchestrator

Managed machines

Each machine you want to manage gets ordo-agent:

Linux / macOS

curl -fsSL https://getordo.dev/install.sh | sh -s -- ordo-agent

Windows

& ([scriptblock]::Create((irm https://getordo.dev/install.ps1))) -Bin ordo-agent

Note

Piping to iex cannot forward arguments, so the single-component Windows commands use a script block instead of a pipe. The Linux/macOS one-liner passes the component after -s --.

Create your operator identity

Back on your workstation, generate an operator keypair:

ordo operator init

This prints your public key (hex) and operator ID. The public key is used to bootstrap the orchestrator in the next step; the private key stays in the operator data directory and is never shared. If you lose track of the public key, print it again with:

ordo operator whoami