Uptime Kuma is a great open-source, self-hosted monitor. Its one structural limit: it checks from wherever you run it. uptime.bet is a hosted service that checks from several nodes and only alerts when two or more of them agree.
| Uptime Kuma | uptime.bet | |
|---|---|---|
| Hosting | Self-hosted (Docker, Node.js) | Hosted service, nothing to install |
| Source | Open source (MIT) | Closed source |
| Check locations | Where your instance runs | Several nodes (Frankfurt, Singapore, USA) |
| Alert confirmation | Single instance (retries) | Alerts when ≥2 nodes confirm (multi-node monitors) |
| Check types | HTTP, TCP, Ping, DNS, keyword, Docker, DBs and more | HTTP, TCP, Ping, DNS, TLS expiry |
| Notifications | 90+ integrations | Email and webhooks |
| Status pages | Yes | Yes, plus embeddable badges |
| Internal / LAN targets | Yes | No (public targets only) |
| Extras | — | DynDNS, WireGuard VPN, Ping/MTR from all nodes |
| Cost | Free, you pay for hosting | Free during the test phase |
Based on Uptime Kuma’s public documentation as of 2026. Corrections welcome.
If Kuma runs in your homelab, it goes down together with your homelab, your power or your uplink — exactly when you would want an alert. And a single vantage point cannot tell “the site is down” from “my route to it is broken”.
uptime.bet runs outside your network. Nodes in Frankfurt, Singapore and the USA check independently, so a regional routing issue shows up as such instead of waking you up for nothing.
If you want fully self-hosted, open-source software, data that never leaves your box, dozens of notification integrations, or you mainly monitor services inside your LAN — use Uptime Kuma. It is mature and has a large community. uptime.bet cannot monitor private addresses and is not open source.
Many people run both: Kuma for internal services, an external multi-node monitor for what the public sees.
uptime.bet is a young service in a public test phase. It is free to use, without warranty, and billing is not enabled. Notification channels are email and webhooks. Plans shown on the homepage are an indicative preview.
Not yet automatically. Adding a monitor takes a URL and a few clicks.
No. uptime.bet is a hosted service. If self-hosting is a must, Uptime Kuma is a good choice.
The free plan checks each monitor from one node of your choice every 5 minutes. Multi-node checks are part of the higher plans, which are currently a preview.
Yes, anything reachable from the internet (e.g. via a public hostname or DynDNS). Private IPs cannot be checked from outside.
Create a free account, add a URL and get alerts by email or webhook. No credit card.
uptime.bet is in a public test phase: free to use, no warranty, billing not enabled yet.