Uptime Kuma: Free Self-Hosted Monitoring for Your Homelab

You run a homelab with a dozen self-hosted services — Jellyfin, a NAS, a game server, maybe a Pi-hole. The moment one goes down, you want to know before someone tells you. Uptime Kuma is a free, open-source, self-hosted monitoring tool that pings your services every few seconds and sends you a Discord, email, or phone notification the second something fails. It takes about five minutes to deploy with Docker, and it gives you a clean status-page UI you can share with family or roommates. This guide walks you through the Docker setup, notification config, and the smartest way to host it so it keeps working even when your main server goes offline. This guide breaks down uptime kuma guide in practical terms.

What Uptime Kuma Monitors: Beyond Basic HTTP Checks

Uptime Kuma isn’t just a website uptime checker — it monitors nearly any network service your homelab runs. The default check is HTTP(s), which works for web apps like Jellyfin, Nextcloud, or your router’s admin page. But you can also monitor TCP ports (e.g., SSH on port 22, a Minecraft server on 25565), DNS resolution (verify a domain resolves correctly), ICMP ping (check if a device is alive on the LAN), and even a full keyword search on a page response (confirm “Login” appears on your app’s homepage).

Each monitor can run on a different interval, and you can group them into a single status page. This means you could have a “Family Services” status page showing Plex, the NAS web UI, and your home assistant dashboard — all visible to household members without giving them server access.

Uptime Kuma Docker Setup: Install in Under 5 Minutes

The quickest way to deploy Uptime Kuma is with Docker Compose. If you already have Docker running on your homelab server — whether it’s a dedicated Docker host, a TrueNAS SCALE app, or an Unraid container — this takes about 60 seconds of copy-paste. If you’re still choosing a platform, our Best Docker Server Build 2026 guide covers hardware that handles containers like this effortlessly.

version: '3.8'
services:
  uptime-kuma:
    image: louislam/uptime-kuma:latest
    container_name: uptime-kuma
    ports:
      - "3001:3001"
    volumes:
      - ./data:/app/data
    restart: unless-stopped

Notification Integrations: Get Alerts Where You Actually See Them

A monitoring tool that only shows status on its own web UI is useless if you’re not looking at it. Uptime Kuma supports 90+ notification services out of the box. The three most useful for homelab users are Discord, email (via SMTP), and ntfy (a lightweight push notification service).

Setting Up Discord Alerts

In Uptime Kuma, go to Settings > Notifications > “Add Notification”. Choose “Discord”, paste your webhook URL (create one in your Discord server settings under Integrations), and give it a name like “Down Alerts”. Save it, then assign it to any monitor by editing the monitor and selecting this notification profile under “Notification”.

Using ntfy for Phone Push Notifications

ntfy is a free, open-source push notification service that works with a simple topic name. In Uptime Kuma’s notification setup, pick “ntfy”, enter your topic (e.g., homelab-alerts), and optionally set a server URL if you self-host ntfy. Install the ntfy app on your phone, subscribe to that topic, and you’ll get push notifications the instant a service goes down — no email setup needed.

Email Alerts via SMTP

For email, you’ll need an SMTP server. Gmail works if you use an app password, or you can run your own mail server in the homelab. Enter the SMTP host, port, username, and password in the notification settings. Email is slower than push notifications but serves as a reliable fallback.

Setting Up a Public Status Page for Shared Services

One of Uptime Kuma’s best features for homelab users is the built-in public status page. It shows the current status of selected monitors in a clean, read-only dashboard. You can share this with family members, roommates, or friends who use your services — they can check whether Plex is down or if it’s their own internet acting up.

Where to Host Uptime Kuma: The “Don’t Monitor Itself” Rule

This is the most important deployment decision you’ll make. If you run Uptime Kuma on the same server that hosts Jellyfin, your NAS, or your game server, then when that server crashes, Uptime Kuma goes down with it — and you won’t get an alert. You’ll only notice the outage when you can’t reach anything.

If you’re on a tight budget and can’t get a second device, consider running Uptime Kuma on a cloud VM or a free-tier Oracle Cloud instance. It only needs 2GB of RAM and a tiny amount of storage — the free tier is more than enough. This way, if your entire homelab goes dark, you still get an alert from outside your network.

Uptime Kuma vs HealthChecks: Which Self-Hosted Monitor Is Right?

If you need to know when a backup script fails to run or a cron job misses its schedule, HealthChecks is the better fit — it expects a “ping” from the job at regular intervals, and alerts if the ping doesn’t arrive. For monitoring services that are always running (websites, game servers, NAS web UIs), Uptime Kuma’s active polling is simpler and more intuitive. Many homelab users run both: Uptime Kuma for live services, HealthChecks for scheduled tasks.

Bottom Line: Should You Deploy Uptime Kuma?

If you run more than three self-hosted services and you want to know about downtime before someone complains, Uptime Kuma is the easiest, cheapest way to get that visibility. It’s free, deploys in five minutes, and works with any notification service you already use. The one non-negotiable rule is to host it on a separate device from the services it monitors — a $50 Raspberry Pi is perfect. Pair it with a Jellyfin install on TrueNAS SCALE or an Unraid server, and you’ll catch failures the moment they happen, not hours later. Remember, RAID is not a backup — always keep separate copies of your important data.