Uptime Kuma is a self-hosted monitoring tool with status pages. This guide covers what a self-hosted install really needs (persistent data, WebSockets behind the proxy, notifications and where the monitor should live) and compares it honestly with one-click Uptime Kuma hosted in Germany.
Uptime Kuma is an open-source monitoring tool (louislam/uptime-kuma on GitHub). It checks HTTP(S) endpoints, keywords on pages, TCP ports, ping, DNS, Docker containers and more, sends alerts through many notification channels and can publish status pages for your customers.
For EU users the point is control: the monitor stores your endpoints, alert contacts and response history on your instance instead of on a US SaaS. That makes the hosting location part of your data-protection documentation, not a footnote. This is not legal advice.
Grounded in the project README and wiki as read on 6 November 2026 (README, Wiki).
/app/data. The official image louislam/uptime-kuma listens on port 3001; everything (monitors, history, settings) lives in the data directory. Lose the volume and you lose the monitor.Do not run the monitor on the same server it watches. If that VPS or its network goes down, Uptime Kuma goes down with it and nobody gets the alert. Put it on a separate machine, ideally at a different provider or location.
Our hands-on walkthrough (Compose, HTTPS proxy and first monitors) is in Self-host Uptime Kuma on a VPS. For the data-protection angle and SaaS alternatives see GDPR-compliant uptime monitoring.
Bringing it up takes minutes if you already run Docker and a proxy. The ongoing part is what counts: image updates (back up /app/data before major versions), certificate renewal, keeping the host itself patched, and noticing when the monitor is the thing that is down.
Full disclosure: this is what we sell. As listed in the shop on 6 November 2026:
Shop description, verbatim: “Self-hosted uptime monitoring and a public status page on your own isolated instance. Runs as a persistent container. Hosted in Germany (EU); memory and CPU are capped by the container runtime.” Region chip: Germany Available.
This app runs in the EU region (Germany) of the overnight.host network. Our VPS, game server, voice and web plans run in the US (Dallas, TX and Charlotte, NC), with more regions planned.
One-click apps sit under a hostname on apps.overnight.host with a real wildcard certificate (see the automation / apps overview). You get the app and a URL, not a root shell, and the monitor runs outside your own infrastructure, which is exactly where it should be.
| Self-host | One-click (overnight.host) | |
|---|---|---|
| Server | Your VPS; small instances run in 512 MiB–1 GiB | Isolated persistent container in Germany; RAM/CPU capped by the runtime |
| Setup | Docker + volume + HTTPS proxy with WebSockets + admin account | Automatic after payment; access by e-mail |
| TLS + hostname | Your domain, reverse proxy, certificates | Included under apps.overnight.host |
| Independence | Only if the VPS is not the thing you monitor | Runs outside your own infrastructure by design |
| Updates + backups | You: pin image, back up /app/data first | Platform managed; no published update schedule on the order page |
| Root shell | Yes | No: app, URL and certificate |
Yes, the order page for one-click-uptime-kuma showed Germany Available at €4 / mo when checked on 6 November 2026. US VPS locations are a separate catalogue.
Yes, status pages are a core Uptime Kuma feature and are part of the one-click product description.
No. You get the app, a hostname and a certificate. For root and custom compose, self-host on a VPS.
Your own Uptime Kuma instance with status page, hosted in Germany, for EUR 4 a month. Prices are final totals; no VAT is shown (§19 UStG).
Order Uptime Kuma → Ask a question first