If you run anything on the internet — a site, an API, a webhook endpoint — you should know when it goes down before your users do. Uptime Kuma is the open-source answer: a self-hosted monitoring tool that checks your services on a schedule, publishes status pages, and pings you when something breaks.
What a monitor can check
Uptime Kuma covers more than “is the homepage up”:
- HTTP(S) — URL checks with status code, keyword, and JSON query matching
- TCP and ping — is the port open, does the host respond
- DNS — record resolution checks
- Keyword — does the page still contain (or not contain) a string
- Steam/Docker/database monitors and more for infrastructure checks
Each monitor records response times, so you also get latency history — not just up/down.
Status pages
You can publish public status pages for the services you monitor — the same style of page SaaS companies pay for with hosted status products. Your domain, your data, no third-party account.
Alerts where you actually are
Telegram, Discord, Slack, webhooks, email, and dozens of other notification channels. A common setup: a Telegram DM to yourself or a channel for your team, triggered when a monitor flips to down — and again when it recovers.
Why self-hosting Kuma used to be annoying
The tool is free — the friction was running it: a server somewhere, Docker, updates, HTTPS, and keeping the monitoring box itself monitored. Half the point of monitoring is that it just works, so babysitting it is self-defeating.
The Pod card below runs Uptime Kuma for you with persistent history and its own Address. It’s also the lightest app in the library — half a vCPU and 1 GiB is plenty for personal monitoring, which is why it’s the cheapest Pod we offer.