What You Need Before You Start
Learning to self host uptime kuma is one of the more rewarding fifteen-minute server projects: Uptime Kuma is a polished, self-hosted monitoring tool that watches your websites and services and pings you on Telegram, Discord, email or dozens of other channels when something goes down. Before you start you need a Linux VPS with Docker, a domain or subdomain pointed at it for HTTPS, and about 1 GB of free RAM — KVM 1 is plenty (checked 14 Oct 2026).
Hostinger’s Docker VPS template skips the manual Docker installation: choose it at setup and you land on a ready container host. On a plain Ubuntu 24.04 VPS, install Docker first, then continue below. Either way, make sure ports 80 and 443 are reachable and you have SSH access with a non-root sudo user.
Uptime Kuma is free and open source under the MIT license, so there are no feature gates or user limits to worry about. The project is actively maintained on GitHub with frequent releases, which is worth checking before you deploy — you want the current stable tag, not a stale tutorial’s version pin. Because it is a single stateful container, it also makes an excellent first Docker project if you are still learning container basics.
Install Uptime Kuma with Docker
The official install is a single command: docker run -d –restart=always -p 3001:3001 -v uptime-kuma:/app/data –name uptime-kuma louislam/uptime-kuma:2. That pulls the official image, maps port 3001, and stores all data in a named Docker volume so upgrades never lose your monitors. Open http://your-server-ip:3001 and create the admin account — do this promptly, because until the account exists the setup screen is public.
Prefer compose? Create a directory, fetch the official compose file, and run docker compose up -d — same result, easier version control. Either method leaves Kuma listening on 3001, which brings us to the step everyone skips and should not: putting it behind HTTPS. Our VPS guide covers the plan basics if you are still choosing.
Put It Behind HTTPS and Lock It Down
Never leave the Kuma dashboard on raw HTTP over the open internet — it is the control panel for your infrastructure alerts. Install Nginx or Caddy as a reverse proxy, point your subdomain at the VPS, and get a free Let’s Encrypt certificate. Then firewall port 3001 so it only answers via the proxy, enable Kuma’s built-in 2FA, and use a strong admin password.
Renewal reality applies here too: the VPS renews roughly 3.3 to 4.3 times the intro price (Gizmodo 2026), so budget the renewal from the start — your monitoring must not lapse because a renewal surprised you. Live VPS figures are on the deal cards (checked 14 Oct 2026).
Self Host Uptime Kuma Monitors: What to Watch First
Once your self host uptime kuma install is live, add monitors in this order: your main website (HTTP keyword check, not just ping), SSL certificate expiry, the VPS itself via ping, and any critical TCP services like databases or game servers. Set check intervals sensibly -- 60 seconds for most things; 20-second intervals are available but generate noise and load.
Create a public status page for your visitors while keeping the admin dashboard private. Kuma supports multiple status pages mapped to domains, which turns your monitoring into a trust signal instead of just an ops tool.
As your monitor list grows, organise monitors into tags by service type -- websites, APIs, infrastructure -- so alert routing stays sane. Kuma's maintenance windows let you silence alerts during planned deploys, which prevents alert fatigue, the number-one killer of monitoring setups. For Docker-hosted services on the same VPS, use Kuma's Docker container monitoring to watch container health directly rather than just pinging ports. And keep one external check that monitors Kuma itself from outside -- a monitor that cannot report its own death is only half a solution.
When NOT to Self-Host Your Monitoring
Self-hosting your monitor on the same infrastructure it watches is the classic trap: when the VPS goes down, your alerting goes down with it. For anything business-critical, either host Kuma on separate infrastructure from your sites or pay for a managed service with independent probes.
Also skip self-hosting if you will not maintain it -- an unpatched Kuma instance is a liability, and Hostinger VPS plans are unmanaged, so updates are yours. Managed services like Better Uptime or Oh Dear exist precisely for teams that want monitoring without another server to babysit.
Who This Guide Is For
This is for developers, homelab enthusiasts and small teams who already run a VPS and want free, private uptime monitoring with great notifications. If you can run a Docker command, you can run Uptime Kuma -- it is genuinely one of the friendlier self-hosted apps.
It is not for enterprises needing compliance reports or global probe networks -- those are managed-service features. Start self-hosted, upgrade when the business justifies it. Pair it with our other VPS guides to build a proper little ops stack.
Maintenance: Updates and Backups
Keep Kuma healthy with two habits: update the image regularly (docker pull then recreate the container -- the named volume preserves everything), and back up the uptime-kuma Docker volume off-site. A monitoring tool you cannot restore is decoration.
Test one restore. The whole point of monitoring is surviving bad days, and untested backups are how bad days get worse (checked 14 Oct 2026).
If you would rather not manage the VPS at all, managed cloud hosting removes the sysadmin burden.
| Approach | Docker run | Docker Compose | Managed uptime service |
|---|---|---|---|
| Setup time | ~5 minutes | ~10 minutes | ~2 minutes |
| HTTPS | You configure proxy | You configure proxy | Included |
| Maintenance | You update image | You update compose | None |
| Cost | VPS fee | VPS fee | Monthly subscription |
| Control | Full | Full | Limited to their features |
| Best for | Quick single setup | Version-controlled setups | Zero-ops teams |
VPS KVM 2
24-month plan, paid upfront
Renews at $14.99/mo
- 2 vCPU + 8 GB RAM
- 100 GB NVMe storage
- 8 TB bandwidth
- Full root access
- n8n one-click template available
FAQ
A Linux VPS with Docker and about 1 GB of free RAM -- Hostinger KVM 1 is enough. You also want a domain or subdomain for HTTPS. The Docker VPS template removes the manual Docker installation step entirely. Pick KVM 2 if you plan to run other monitoring-adjacent containers, like a reverse proxy or log collector, on the same box.
Run: docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:2 -- then open port 3001 and create the admin account immediately. The named volume keeps your data safe across updates.
Yes -- put Nginx or Caddy in front of it as a reverse proxy with a Let's Encrypt certificate, firewall port 3001 to localhost/proxy only, enable Kuma's 2FA, and use a strong password. Never leave the dashboard on open HTTP.
Telegram, Discord, Slack, Pushover, Gotify, email via SMTP and dozens more -- over 90 notification services are supported. Configure at least two channels so a single provider outage cannot silence your alerts. SMS gateways and webhooks are also available for teams with pagers or custom incident workflows.
When you want zero server maintenance, need SLA-backed reliability, or must monitor from multiple global locations without running the probes yourself. Self-hosting wins on cost and privacy; managed wins on convenience. Cost-wise, self-hosting wins for single users while managed services win back their fee the first time they catch an outage you would have missed.