---
title: Uptime Kuma vs hosted monitoring: what self-hosting actually costs
description: Uptime Kuma is free and genuinely good, and for a lot of people it is the right answer. The honest comparison is not about features — it is about two structural problems that no amount of configuration fixes, and whether either of them applies to you.
canonical: https://watchfor.io/blog/uptime-kuma-vs-hosted-monitoring
---

[All posts](/blog) [Monitoring](/blog/category/monitoring) Sep 11, 2026 · 4 min read · WatchFor Team

# Uptime Kuma vs hosted monitoring: what self-hosting actually costs

Uptime Kuma is free and genuinely good, and for a lot of people it is the right answer. The honest comparison is not about features — it is about two structural problems that no amount of configuration fixes, and whether either of them applies to you.

Uptime Kuma is one of the best open-source projects in this category. It is
free, it is pleasant to use, unlimited monitors, a decent status page, and it
runs anywhere Docker does. For homelabs and side projects it is frequently
the correct answer and no hosted product is going to beat free.

So this is not a feature comparison. It is about two structural problems that
configuration cannot fix, and about what the "free" actually costs once you
add it up. If neither problem applies to you, stop reading and keep Kuma.

## Problem one: it goes down with the thing it watches

The obvious one, and the one everybody nods at and then does anyway. If Kuma
runs on the same server, the same rack, the same provider or the same region
as what it monitors, the outage that takes down your site takes down the
thing that was supposed to tell you about it.

The fix is to host it somewhere else. That is a second server to provision,
patch, back up and remember — and the moment you have done that, "free" has
become "one more thing I operate", which is the real price.

## Problem two: one vantage point cannot tell you where the problem is

This one is quieter and matters more often. Kuma checks from wherever it
runs, which is one place. That means it can tell you a site is unreachable
from there , and it can never tell you whether:

- the site is down, or the path between your VPS and the site is;

- the problem affects everyone or only one region;

- the CDN is serving Europe fine and missing cache in Asia;

- the DNS change has propagated everywhere or only where you are looking.

Those questions need probes in several places at once. It is not a missing
feature — it is the difference between one machine and a network, and it is
why regional failures are the ones that go unnoticed longest.

## What self-hosting actually costs

Free is accurate about the licence and misleading about the total. Honestly
accounted:

- A small VPS somewhere other than your production host. Call it €4–6 a
month, and it has to be somewhere you would not lose in the same incident.

- Upgrades. Kuma ships regularly. A monitoring tool three versions behind
is a monitoring tool with known bugs.

- Backups. A SQLite file nobody backs up, until the disk fills.

- Noticing when it stops. The classic failure: monitoring that died
quietly two weeks ago and nobody noticed, because the thing that would have
told you was the thing that died.

- Your time , which is the largest line and the one nobody puts in the
spreadsheet.

Against roughly €7 a month for a hosted plan, the money is a wash. The
difference is entirely in who does the operating.

## When Kuma is clearly right

- A homelab, a side project, anything where an hour of downtime costs
nothing.

- Policy or compliance requires monitoring data to stay on your own hardware.

- You are monitoring things that never leave your network and cannot be
reached from outside anyway.

- You enjoy running it. This is a real reason and not a lesser one.

## When it stops being right

- You are the person who gets paged, and would rather the pager itself were
not your responsibility.

- You need to know whether a problem is regional, which needs more than one
vantage point.

- Customers are asking whether it was down for them , and "it was fine from
my VPS" is not an answer.

- You need checks Kuma has no plugin for — CDN cache behaviour, network path,
mail authentication, certificate chains across regions.

## Running both

Plenty of teams do, and it is not a compromise so much as two different jobs.
Kuma internally for services that never leave the network, where a single
vantage point is the whole truth anyway. A hosted service for anything
customers touch, where the question is what they experience.

If you go that way, point the hosted one at Kuma's own status page. The
monitor that watches the monitor is the one nobody remembers to set up.

We sell hosted monitoring, so weigh this accordingly. We have tried to make
the case for Kuma properly rather than to caricature it — the two problems
above are the only honest arguments against it, and neither applies to
everyone.

The dated one-to-one is on our [Uptime Kuma alternative
page](/uptime-kuma-alternative); our own free plan is 15 monitors with
commercial use allowed, at [€7 a month](/pricing) beyond that.

[#monitoring](/blog/tag/monitoring)[#uptime](/blog/tag/uptime)

## Start monitoring your services today

WatchFor checks HTTP, DNS, SSL, ping, email and 20+ more — from around the world, with alerts to Slack, Discord, email and beyond.

[Learn more](/docs/monitors)[Start free](/auth/sign-up)

Share this article

---

Canonical page: https://watchfor.io/blog/uptime-kuma-vs-hosted-monitoring · Site guide: https://watchfor.io/llms.txt