Skip to main content
For the complete documentation index, see llms.txt. Markdown versions are available by appending .md to page URLs.
The supported Linux installer performs discovery, secure configuration, deployment, service startup, and health verification. It is safe to rerun and does not require manual rule selection.

​
Requirements

  • x86-64 or ARM64 Linux with systemd for the central service and supported collectors
  • An identity-pinned administrative transport for each remote Linux endpoint
  • Noninteractive sudo on remote endpoints
  • Existing authenticated cloud or provider CLIs when using hosted discovery

​
Fleet installation from a checkout

Fleet mode discovers available inventory sources, selects one supported central host deterministically, and installs collectors only where administrative access is already authorized. Unsupported or unreachable assets remain visible as explicit coverage gaps.

​
Hosted onboarding

The authenticated Setup page at https://app.devlookout.com/setup creates a short-lived, account-bound setup command. Run that generated command in the terminal where your provider CLIs are already authenticated.
Never paste a setup token into chat, a URL, process arguments, source control, or cloud-init data. Use the owner-only token-file flow generated by the Setup page.

​
Single-host installation

Use local mode when fleet discovery is intentionally unwanted:

​
Verify

The doctor checks Node compatibility, storage and key posture, file permissions, snapshot integrity, journal chains, disk headroom, and abandoned temporary files.

​
Uninstall

Remove application code and services while retaining configuration, identities, keys, and event data:
Permanently remove Lookout-managed configuration and data only when explicitly intended:
Purge operates against the installer’s fixed allowlist and removes service users only when the protected installer manifest proves that Lookout created them.