Uptime Kuma

Open-source · self-hostable · replaces 2 SaaS tools on os-alt

louislam/uptime-kuma · alive · ★ 86.5k · last commit today · 736 open issues

License: MIT

Good fit for Most use cases — easiest install, broadest notification options, bundled status pages.

Weak at Single-region — checks come from one VPS. For multi-region probes, deploy multiple Uptime Kuma instances and aggregate alerts upstream.

In a terminal? npx -y github:SolvoHQ/os-alt-cli statuspage prints the Statuspage (Atlassian) comparison table including Uptime Kuma. how the CLI works →

Replaces these SaaS

Statuspage (Atlassian) · Public status page / incident communication
`docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:1`. Add monitors (HTTP, TCP, ping, DNS, keyword, JSON-query); enable Status Pages → Add — multiple branded public pages per instance, with subscriber email + 90+ notification channels. Closest single-binary one-stop replacement for Statuspage with bundled checks.
UptimeRobot · External uptime / availability monitoring
`docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:1`. UptimeRobot doesn't have a clean export — recreate monitors manually or use the community Python script that reads the UptimeRobot API and POSTs to Uptime Kuma's API. Native support for 90+ notification channels (Slack, Discord, Telegram, ntfy, Gotify, generic webhook); status pages bundled.

README badges for the SaaS this replaces

Maintainers and forks: drop a badge in your README to link readers from the SaaS-comparison page back to your repo.