Self-hosting a full monitoring stack in one command: servers, logs, APM and status pages

Description and use

Install a complete self‑hosted monitoring stack with a single command, consolidating metrics, logs, status pages, and optional tracing, with automated updates and backups.

Problem

Teams need a self-hosted monitoring stack to keep data in-house or avoid escalating SaaS costs, but typical stacks involve five separate services that are hard to maintain for small teams.

Outcome

A single command installs a fully functional, self‑hosted monitoring stack that replaces five separate services, reduces maintenance effort, and supports offline operation with secure license verification.

Workflow

• 1. Run the one‑command installer with domain, email, and license parameters.
• 2. Installer installs Docker if missing, downloads and verifies the release bundle via Ed25519 signature.
• 3. Generates a Caddyfile for automatic HTTPS and starts Postgres, a worker, and two web replicas for rolling updates.
• 4. Use vigil update to perform safe, rollback‑enabled updates.
• 5. Use vigil backup to dump the database and config every six hours via cron.
• 6. For private networks, add --internal-tls for self‑signed certs and --no-phone-home to keep the instance offline.

Evidence

Vigil's self-hosted edition installs like this on any Ubuntu, Debian, RHEL-family or Alpine host:

Source

It installs Docker if missing, downloads the release bundle and its Ed25519 signature, verifies the signature with openssl before extracting anything, writes a Caddyfile with automatic HTTPS, and starts Postgres, a worker and two web replicas so updates are rolling.

Source

Postgres is the only stateful part. A fleet of 20 servers reporting every 30 seconds with logs enabled lands around 2 GB of database growth a month at the default retention.

Source