Updated 25 October 2026 · By the Upcertain team
What Uptime Kuma offers
According to its README, Uptime Kuma monitors HTTP(S), TCP, HTTP keyword and JSON queries, WebSocket, ping, DNS records, push (heartbeat), Steam game servers and Docker containers. It checks as often as every 20 seconds and sends notifications through more than 90 services. It serves multiple status pages, which can be mapped to your own domains. You install it with Docker or Node.js on a server you run.
What self-hosting involves
- A server outside what it monitors. A monitor on the same machine or network as your app goes down with it, and cannot tell you so.
- Watching the watcher. If the monitoring server stops, alerts stop with it. Someone has to monitor the monitor.
- Updates and backups. Upgrades, database backups and security patches are yours.
- HTTPS and domains for status pages. A reverse proxy and certificates for every status page domain.
Side by side
| Upcertain | Uptime Kuma | |
|---|---|---|
| Hosting | Hosted by Upcertain | Self-hosted (Docker or Node.js) |
| Licence and cost | Early access, plans without billing | MIT licence; you pay for the server |
| Monitor types | HTTP, keyword, ping, port, SSL, heartbeat | HTTP, TCP, keyword, JSON query, WebSocket, ping, DNS, push, game servers, Docker containers |
| Fastest check | 30 s | 20 s |
| Notifications | Email, Slack, Discord, Teams, Google Chat, signed webhooks | 90+ services |
| Status pages | Custom domain with automatic HTTPS, password or private, subscribers, per-service downtime | Multiple pages, mapped to your domains |
| Team members and roles | Owner, admin, editor, viewer, notify-only | Not in the README's feature list |
| REST API and MCP | Yes | Not in the README's feature list |
Uptime Kuma's details come from its README on GitHub, read on 25 October 2026.
When Uptime Kuma is the better choice
- You need a monitor type Upcertain does not have, such as DNS records, Docker containers or game servers.
- You must monitor services on a private network that nothing outside can reach.
- You already run servers and like owning every part of your stack.
- You need a notification service Upcertain does not support directly.
When hosted is the better choice
- You do not want monitoring to depend on a server you also have to keep alive.
- Several people need their own logins with roles: owner, admin, editor, viewer or notify-only.
- You want status pages on your domain without running a proxy, with subscribers and password protection.
- You want AI agents to read your monitors over MCP or scripts to use a REST API.
Using both
You can keep Uptime Kuma inside your network for private services and use a hosted monitor for public endpoints and the status page. A heartbeat monitor in Upcertain can even watch the self-hosted monitor: have the Uptime Kuma server call the heartbeat URL every minute, and you hear if it stops.
Questions
Can I import my Uptime Kuma monitors?
Sources
- Uptime Kuma README on GitHub (read 25 October 2026)