Self-host Uptime Kuma with Levelrail

Verified

A self-hosted uptime monitor with a clean dashboard for HTTP, TCP, DNS, and ping checks.

  • AuthorlouislamVerified by Levelrail
  • LicenceMIT
  • Memory256 MiB
  • Archarm64
  • Services1

How to self-host Uptime Kuma

  1. Pull the images

    One image is pulled on your server.

    Show images
    • louislam/uptime-kuma:1.23.13
  2. Create the app

    One service starts in a single Compose app, with 1 named volume mount for your data, on port 3001.

  3. Fill in the secrets

    You do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

Uptime Kuma requirements

Memory
About 256 MiB
Architectures
amd64 image published, arm64 tested
Ports
3001
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
MIT, permissive license
  • Verified. Verified on arm64 with image tag 1.23.13. Our CI ran this exact image version and it answered on its health path. Evidence

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Uptime Kuma. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the Uptime Kuma docs page.

Deploy Uptime Kuma your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Uptime Kuma from the CLI

levelrail-cli templates deploy uptime-kuma --name my-uptime-kuma

Deploy Uptime Kuma with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/uptime-kuma/deploy

Uptime Kuma configuration

Uptime Kuma services

ServiceImagePortsVolumes
kuma louislam/uptime-kuma:1.23.13 3001 data -> /app/data

Uptime Kuma environment variables

The catalog lists no environment variables for this template.

Ports and volumes

Ports
3001
Volumes
1 named mount: data -> /app/data

Uptime Kuma FAQ

How much memory does Uptime Kuma need?

The catalog lists about 256 MiB of memory for Uptime Kuma.

Does Uptime Kuma run on arm64?

For Uptime Kuma, arm64 is tested; amd64 is image published.

What licence is Uptime Kuma under?

Uptime Kuma is licensed under MIT, which is permissive, with few conditions on reuse.

Does Uptime Kuma need configuration before it starts?

No. The template fills in its own defaults.

Which ports does Uptime Kuma use?

Uptime Kuma listens on port 3001 inside the stack.

Where does Uptime Kuma keep its data?

In a named volume: data mounted at /app/data.

Can I deploy Uptime Kuma on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id uptime-kuma for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image louislam/uptime-kuma:1.23.13 is what you deploy there.

levelrail-cli templates deploy uptime-kuma --name my-uptime-kuma