Uptime Kuma
Self-hosted uptime monitoring with a polished UI, 20+ monitor types, public status pages, and 90+ notification integrations. Replaces UptimeRobot or Better Stack with no subscription fees
Quick Start
docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:2 Overview
Uptime Kuma is a self-hosted uptime monitoring tool that replaces services like UptimeRobot or Better Stack with a single Docker container you run yourself. Set up monitors for HTTP endpoints, TCP ports, DNS records, Docker containers, SSL certificate expiry, and more. When something goes down, it fires a notification to whichever channel you have configured — Slack, Discord, Telegram, PagerDuty, email, or one of 90+ other integrations.
The interface stands out for a self-hosted tool. It is clean, responsive, and clearly designed with care. Adding a monitor takes seconds, the dashboard gives an at-a-glance view of everything, and the status page feature generates a public-facing page that updates automatically — useful if you want a status page for a SaaS product without paying Better Stack’s subscription rates.
Monitor types go beyond a basic HTTP ping: heartbeat monitors for cron jobs, Kubernetes ingress checks, game server monitoring, and Docker container health are all included. Check intervals can be set as low as 20 seconds.
The practical limits are worth knowing. Uptime Kuma is a single-process Node.js application. It is not designed to run in a high-availability multi-node configuration. It stores data in SQLite by default, so backing up the data directory is your responsibility. And because it is largely maintained by a solo developer, feature velocity and bug fix timing reflect that.
For personal projects, small teams, and indie products that want uptime monitoring without a monthly bill, it covers everything necessary.
Uptime Kuma: Pros & Cons
| Pros (The Wins) | Cons (The Friction) |
|---|---|
| No limits, no fees: Unlimited monitors, no check interval floor, self-hosted. | Single-process: Not designed for HA or multi-node deployments. |
| 90+ notifications: Slack, Discord, Telegram, PagerDuty, webhooks, and more. | No escalation routing: Sends alerts but no on-call scheduling or rotations. |
| Status pages: Public and private pages with custom domain support. | SQLite by default: Backup setup is manual; data lives in one file. |
| 87.4k stars: One of the most popular self-hosted tools available. | Solo developer: Feature pace and bug fixes depend on one person. |
Use Cases
Specific ways to use Uptime Kuma for your workflow.
Deployment Strategy
Recommended ways to host Uptime Kuma in your own environment.