Self-host Uptime Kuma on a VPS
A self-hosted uptime monitor with a clean dashboard for HTTP, TCP, DNS, and ping checks.
levelrail-cli templates deploy uptime-kuma --name my-uptime-kumaSpecification
- Status
- Verified on arm64 with image tag 1.23.13
- Category
- Monitoring
- Services
- kuma
- Ports
- 3001
- Volumes
- 1
- Memory
- about 256 MiB
- arm64
- tested
- amd64
- image published
- Settings to fill in
- none
- License
- Permissive license, MIT
About Uptime Kuma
A self-hosted uptime monitor with a clean dashboard for HTTP, TCP, DNS, and ping checks.
What it deploys
Uptime Kuma runs as one service in a single Compose app, listening on port 3001, with 1 named volume mount.
| Service | Image | Tag | Ports | Volumes |
|---|---|---|---|---|
| kuma | louislam/uptime-kuma | 1.23.13 | 3001 | data -> /app/data |
Before you install
- CPU architecture. arm64 listed. Every image lists linux/arm64 in its registry manifest. That is a manifest fact, not proof the app runs on Arm.
- Verified. Verified on arm64 with image tag 1.23.13. Verified means our CI ran this exact image version and it answered on its health path. Evidence
Settings and environment
The catalog lists no environment variables for this template.
Install Uptime Kuma on a VPS
-
Install Levelrail on a fresh VPS
Run this as root on a Linux server (amd64 or arm64) with ports 80 and 443 reachable. The installer prints a setup link.
curl -fsSL https://levelrail.com/install.sh | sudo sh -
Sign in
Open the setup link, choose a password, then log the CLI in. The CLI install command is
curl -fsSL https://levelrail.com/install-cli.sh | shif the machine does not have it. See Getting started.levelrail-cli login --device -
Read the template
Shows the entry, including its full compose.yaml.
levelrail-cli templates get uptime-kuma -
Deploy it
This deploys the template compose file as an app. The app name defaults to the template id; --name sets another.
levelrail-cli templates deploy uptime-kuma --name my-uptime-kuma
Without a domain the app gets an sslip.io address. You can also deploy it from the dashboard: Apps, New app, Browse templates, then Uptime Kuma.
Docs and upstream
More in Monitoring
- Uptime Kuma (MariaDB)Uptime Kuma with a MariaDB sidecar provisioned, for the setups that opt out of its default SQLite file.
- UnPollerPolls a UniFi controller and exposes network, client and device statistics as Prometheus metrics. The install form carries up.conf as an editable file and asks for a read-only controller login.
- VectorHigh performance observability data pipeline for logs and metrics. The install form carries vector.yaml as an editable file, so it starts with an HTTP source and a console sink.
- VictoriaLogsA log database with a built in web UI and low memory use, with a data volume. Send logs to port 9428 from this project. The API has no login, so restrict access before exposing it.
- VictoriaMetricsA fast, resource-frugal time-series database that speaks the Prometheus query and remote-write APIs. Has no authentication, so point Prometheus-style senders at victoriametrics:8428 from other services in this project, or attach a domain only behind Basic Auth. Not published on the host.
- TelegrafPlugin driven agent that collects metrics and exposes them for Prometheus. The install form carries telegraf.conf as an editable file, so it starts with CPU, memory and disk inputs already wired.