Service uptime monitoring
HTTP, TCP, ping, DNS, Docker, Steam

// screenshot of uptime.kuma.pet ↗
Uptime Kuma is a self-hosted status monitor — pings HTTP endpoints, TCP ports, DNS records, Docker containers, Steam game servers; alerts on failures via 80+ notification channels. Beautiful UI, status page generator, designed by a single dedicated maintainer (Louis Lam).
Uptime Kuma is a self-hosted status monitor — pings HTTP endpoints, TCP ports, DNS records, Docker containers, Steam game servers; alerts on failures via 80+ notification channels. Beautiful UI, status page generator, designed by a single dedicated maintainer (Louis Lam).
For self-hosters who want their own UptimeRobot / Pingdom without paying per-monitor SaaS fees.
Concrete scenarios where teams pick Uptime Kuma over the SaaS alternative.
HTTP, TCP, ping, DNS, Docker, Steam
share service health publicly
80+ notification channels (Slack, Discord, email, SMS, etc.)
historical uptime percentages
keyword presence in HTTP responses
If your team profile matches one of these, Uptime Kuma is a strong fit out of the box.
monitoring their own services
tracking SaaS dependencies + their own services
providing uptime visibility internally
giving customers monitoring
monitoring side projects
When evaluating self-hosted options for this category, here are the dimensions on which Uptime Kuma consistently lands above the alternatives.
The stack you'll plug Uptime Kuma into — services, protocols, and adjacent apps in the BluixApps catalog.
louislam/uptime-kuma:1 (latest stable major)/app/data/app/data (SQLite + config)Operational guidance from running this in production — what to do before you scale, what to lock down, what surprises people.
/app/data3001:3001 · louislam/uptime-kuma:1