Uptime Kuma

Combine multi-protocol health checks, notifications, and status pages in one dashboard

It monitors HTTP(S), TCP, keywords, JSON queries, WebSocket, Ping, DNS records, Push, Steam servers, and Docker containers, with intervals down to 20 seconds. More than 90 notification services and multiple status pages are supported.

Sources: [2]

Start with a short Docker Compose flow and pick up new monitor types and security fixes in 2.5.4

The README provides a compose.yaml download followed by docker compose up -d. Release 2.5.4 adds SFTP monitoring with password/private-key authentication and new notification providers, plus a jsonata CVE update and a DoS weakness fix.

Sources: [2][3]

For homelabs and smaller services that want monitoring data and status pages under their own control

It suits homelabs, indie services, and small teams that want checks, notifications, and status pages on their own server without adopting a larger observability stack.

Treat port exposure, persistent data, and upgrades as operator responsibilities

The README Docker examples expose port 3001 on all interfaces unless you bind it differently. Prefer localhost binding or a reverse proxy/TLS setup for internet-facing use. NFS is explicitly unsupported for data storage. Because releases such as 2.5.4 carry security fixes, self-hosting also requires an update cadence.

Sources: [2][3]