Argus deployment

Install Argus on your server.

Deploy a new control plane or connect another machine to an existing Argus instance. The public bootstrap verifies the native installer before it runs; credentials and configuration stay in your terminal.

Ubuntu / Debian amd64 root / sudo native installer

Install

Run one command on the server

SHA-256 checked before execution
Loading install command…
01 Downloads the native installer 02 Verifies the published checksum 03 Starts guided setup in your terminal

What happens next

A guided server-side setup

Nothing is configured in this browser. The installer asks only for what the selected setup needs.

  1. 1
    Choose a mode

    Create a control plane here or connect a managed server.

  2. 2
    Authenticate packages

    Enter a GitHub classic PAT with read:packages.

  3. 3
    Configure the host

    For a control plane, provide the main domain and optional content-domain override.

  4. 4
    Verify deployment

    Argus starts its services and runs installation health checks.

Before you install

Server requirements

The installer intentionally refuses unsupported hosts or conflicting container stacks instead of changing them automatically.

Operating systemUbuntu or Debian
Architectureamd64
Privilegesroot or sudo
IngressTCP 80 + 443 available
DNSMain + content domainargus.example.com
content.argus.example.com
Private registryGitHub classic PATread:packages access to Argus GHCR images

On your server

What Argus installs

/opt/argus/Compose files and runtime environment
/etc/argus/Host configuration and registry credentials
/var/lib/argus/Persistent host state and backups
/var/log/argus/Installer and lifecycle logs
/usr/local/bin/argus-agent, argus-helper, argusctl

Application services run with Docker Compose. The Agent and privileged Helper run as native systemd services.

Installer security

Designed to be inspectable

✓
Verified bootstrap

The published installer checksum is validated before execution.

✓
Terminal-only secrets

Your registry token is entered silently and is never collected by this page.

✓
Root-only registry storage

Validated GHCR credentials are stored in /etc/argus/registry.env with mode 0600.

✓
Rerunnable

Existing generated IDs, secrets, data and the installed immutable revision are preserved.

Installation modes

One installer, two jobs

01

New control plane

Install the Argus application stack plus the local Agent and Helper on this server.

  • Main and content domains
  • Initial operator credentials
  • Docker Compose control plane
02

Managed server

Connect another machine to an existing Argus project using a short-lived setup code.

  • Single-use enrollment code
  • Native Agent + Helper
  • No local control plane

After installation

Verify the host

Use the native CLI for local service, connection and broader installation checks.

argusctl status
argusctl health
argusctl connection
sudo argusctl smoke