Key takeaways

  • Know when a site or server stops answering: one self-hosted tool watches web, ping, DNS and Docker targets.
  • Get told where you already are: alerts can go out through more than 90 notification services, including Telegram, Discord and Slack.
  • Checks can run at 20-second intervals, so an outage is spotted quickly.
  • Show customers the truth: it supports multiple status pages, which can be mapped to specific domains.
  • The catches: you run it yourself, some platforms are unsupported, and the maintainer has little time to test pull requests.

What it is

Uptime Kuma describes itself as an easy-to-use self-hosted monitoring tool. It is open source under the MIT licence, and the code is on GitHub at louislam/uptime-kuma.

The problem it solves

Anyone who runs a website, an API or a home server needs to hear about an outage before their users do. Hosted monitoring services do that job, but not everyone wants to hand it to a third party.

The author says he wanted a self-hosted tool like Uptime Robot and found it hard to find a suitable one. Uptime Kuma is his answer.

What you get

  • One place for many checks: HTTP(s), TCP, keyword, JSON query, websocket, ping, DNS, push, Steam game server and Docker container monitors.
  • Alerts where you work: more than 90 notification services are listed, including Telegram, Discord and Slack.
  • Quick detection: checks can run at 20-second intervals.
  • A public face: multiple status pages, which can be mapped to specific domains.
  • A way to look first: the project offers a temporary live demo whose data is deleted after 10 minutes.

The catches

  • You are the operator: it is self-hosted, so running, securing and updating it is your job.
  • Exposure: after a Docker install the README says it runs on all network interfaces, though it documents a way to limit exposure to localhost only.
  • Platform limits: network file systems such as NFS are not supported, and the non-Docker route is not supported on FreeBSD, OpenBSD, NetBSD, Replit or Heroku.
  • Maturity and support: the maintainer says there are a lot of pull requests and he does not have time to test them all, and he does not answer questions sent by email.

What we did not test

We did not install Uptime Kuma, try the live demo, set up an alert or check how quickly it detects an outage. Every claim here comes from a literal quote in the project's README or the GitHub API, and the feature descriptions are the project's own.

Verdict

Editors' view: this suits people who run their own sites or servers and want alerts without paying a hosted service. If you cannot spare time to maintain another server, a hosted monitor may be the safer choice. If you try it, start with the project's demo, and keep any install off the public internet until you have chosen how it is exposed.

Repository
louislam/uptime-kuma
JavaScript · MIT
View on GitHub ↗

Sources

Need help adopting this, or have a software project in mind?

Tell us what you are building. The initial consultation is free. Email [email protected] or follow @zolnaltd.

Start a conversation →