Uptime Kuma alternative for people who do not want to run a server
Logdash is the hosted version of what Kuma does for most people - HTTP checks, heartbeats, a status page and alerts - with no VPS, no container and no SQLite file to back up.
Uptime Kuma is genuinely good software. The dashboard looks better than most paid products, it covers more monitor types than anything else in its price bracket, the notification provider list is enormous, and it costs nothing but a container. If you already have a box with spare capacity and you enjoy owning your data, running Kuma is the right call and this page is not going to argue you out of it.
The reason people leave is not the software. It is that a monitor running on your own infrastructure shares a fate with your infrastructure. The night the host has a problem is the night Kuma has the same problem, quietly, and you find out from a customer instead of from a notification. Underneath that sits the maintenance nobody plans for: container updates, the database volume, a reverse proxy certificate, and a notification config you set up once in 2024 and have never tested since.
Logdash is the hosted answer to that, not a self-hosted replacement. It is AGPL-3.0 licensed with a public repository, but production self-hosting is not a one-command install today. It runs locally for development and the rest is tracked on GitHub. If self-hosting is the point, stay on Kuma. If the point was a monitor that outlives your server, that is the trade here.
The endpoint the hosted check hits
@app.get("/health")
async def health():
try:
await db.execute("select 1")
except Exception:
# 503 so a live process with a dead database still reads as down
raise HTTPException(status_code=503, detail="db")
return {"ok": True}- Create the monitor Add a monitor and paste the health URL. The first check runs straight away, so you find out the URL is wrong now rather than during an incident.
- Move the heartbeats Kuma push URLs become a POST to https://api.logdash.io/ping/<httpMonitorId>, no auth, no body. Pro expects one every 15 seconds, so anything that pinged less often needs a heartbeat loop, plus a stamp file for scheduled jobs.
- Turn the app off Stop the container and let one check fail. The status page flips to down and the Telegram alert arrives with the status code, this time sent from somewhere that is not the machine you just turned off.
Uptime Kuma status page API and badges
Kuma has both, with caveats. Its badges cover status, uptime, ping and certificate expiry, and the Badge Maker builds the URL for you. Its status page JSON lives under /api/status-page, but the wiki says that API is for Kuma itself and not officially supported. Logdash publishes a versioned public endpoint, a typed client, a shadcn component and a Next.js starter, so a custom status page in your own design is a template away. Badges come per monitor: classic shows uptime over 24h, 7d, 30d or 90d, and status and card come in light or dark.
# The whole status page as JSON, no key
curl https://api.logdash.io/v1/status_pages/your-status-page-id
# One monitor's badge: classic style, 30-day uptime by default.
# your-badge-key is that monitor's id in the JSON above.
curl -o uptime.svg \
https://logdash.io/d/your-status-page-id/badges/your-badge-key.svgLogdash vs Uptime Kuma
| Feature | Logdash | Uptime Kuma |
|---|---|---|
| Where it runs | Hosted, nothing to update | Your server, your updates, your backups |
| Monitor types | HTTP checks and push heartbeats | HTTP, TCP, ping, DNS, keyword, certificate expiry and more |
| Survives your infrastructure failing | Runs outside your stack | Goes down with the host it sits on |
| Notification channels | Telegram and webhook | Dozens of providers built in |
| App logs and custom metrics | Eight SDKs into the same dashboard | Not what Kuma is for |
| Cost at five services | Covered by the free plan | Free, plus whatever the box costs |
| Production self-hosting | Not ready, tracked on GitHub | The entire point, one container |
| Status page API | Versioned public JSON, typed client, component | Internal endpoints, not officially supported |
When Uptime Kuma is the better pick
- You already run a homelab or a VPS with headroom. Kuma costs one container and you keep every byte of the history.
- You need TCP, DNS, ping or certificate expiry checks. Logdash has none of those and is not near having them.
- Monitoring has to stay inside your network, on hosts with no public egress.
- Self-hosting in production is the requirement. Kuma does that today and Logdash does not, which is the honest end of the comparison.
What migrating involves
No importer, and for a dozen URLs that is fine. Copy them across, rewire the push jobs as above, and run both for a week. The history does not come with you, so if you quote an uptime figure to customers, screenshot the Kuma dashboard first.