Uptime Kuma: An Honest Review (Pros, Cons, and When a Managed Service Makes Sense)
If you're evaluating Uptime Kuma to monitor a few sites — yours or your clients' — this review comes from people who self-host software every day and use it for work too. It's not a review against Uptime Kuma: it's an excellent project, it's free, and we'll say so plainly. The point of this article is something else: what "free" really means when the software has to monitor something on someone else's behalf.
What Uptime Kuma is
Uptime Kuma is a self-hosted uptime monitoring tool, open source under the MIT license. You install it on your own server (a cheap VPS is enough: the project's documentation lists modest requirements, 1-2 vCPUs and 1-2 GB of RAM, about 20 GB of disk) and from there it checks the availability of the sites or services you point it at.
It has no limit on the number of monitors, which makes it immediately attractive compared with the free plan of any paid service, which caps the number of sites.
What it does well, no discounts
It covers more protocols than a website needs. HTTP/S, of course, but also TCP, ping, DNS, keyword on a page, Docker containers, databases. If you monitor infrastructure as well as websites — an internal server, a backend service, a database — Kuma covers cases that a tool built only for websites doesn't.
Aggressive check intervals. Down to 20 seconds between checks, for anyone who needs to know fast.
Almost endless notification channels. Over 95 integrations — email, Telegram, Slack, Discord, custom webhooks, and much more. Whatever your workflow, Kuma probably already knows how to notify it.
A polished interface, in over 20 languages, with 2FA and status pages included in the free package. For an open source tool, the polish of the interface is above the category average.
If you're a sysadmin monitoring your own infrastructure, and running that infrastructure is already part of your daily job, Kuma is probably the right choice. That's not a courtesy concession: it's the correct advice, and we'd give it anyway.
The two costs the word "free" doesn't tell you about
The first is your time. "Self-hosted" means the server is yours in every sense: you install it, update it, back it up, secure it. And — this is the ironic part of self-hosted monitoring — someone has to monitor the monitor: if the server hosting Kuma goes down, who tells you that for that whole period you're blind to everything else? Add the cost of the VPS (€5-10 a month for a decent instance) plus the monthly hours of maintenance, multiply by your hourly rate, and "free" has found its price — often higher than it looks at first sight.
The second is structural, and can't be fixed with more care. A Kuma instance watches your sites from a single point on the network: the server it runs on. A local network problem on that server — not on the monitored site — looks identical to a site that's really down. This isn't a hidden criticism: it's the project's own official documentation that devotes an entry to how to diagnose the "downs that aren't down." For someone monitoring their own infrastructure, an occasional false alarm is a nuisance. For an agency that forwards those alarms to a client, a false alarm is a blow to credibility that no free tool gives back to you.
Uptime Kuma vs UptimeRobot: the wrong question
People who search for "uptime kuma vs uptimerobot" are usually comparing two tools on the same level — both designed to be used directly by whoever is monitoring their own sites. The practical difference is simple: UptimeRobot is a managed service with a generous free plan (no server to install, but fewer protocols and less customisation than Kuma); Kuma is self-hosted and unlimited in monitors, at the cost of your management time. If the criterion is "which software," the answer depends on how much you want to administer yourself. If the criterion is "how do I use it to resell a service to my clients," neither was designed for that — and that's a different problem from which tool to install.
When Kuma is the right choice
- You monitor your own infrastructure and can administer it without trouble
- You need checks beyond HTTP: TCP, ping, DNS, containers, databases
- The management hours are already part of your job, not an extra cost
- You want total control, data on your own server, no external dependencies
When it's worth looking elsewhere
- Monitoring is (or you want it to become) a service you sell to your clients, not a tool you use for yourself
- A false alarm sent to a client costs you more than the monthly fee of a managed tool
- You want status pages with your own branding, on your own domain, without manually configuring proxies and certificates for each one
- You prefer a predictable fee to the unpredictable maintenance hours of one more server
A managed alternative, if the use case is "reselling monitoring"
If you manage sites on behalf of clients and you're evaluating Kuma for that specific use case, it's worth looking at the head-to-head comparison we wrote between Statuo and Uptime Kuma: the same honesty as this article, with a table of verified data and the maths of what self-hosting really costs once you factor in your own time. Statuo was built for exactly the case Kuma doesn't cover: multi-location confirmation to avoid false alarms, white-label status pages ready to resell, a flat fee instead of a server to keep running. The trial lasts 14 days, no credit card required — enough to run it alongside Kuma and see the difference on your real sites, not in a theoretical case.