Projects / Uptime Kuma

Uptime Kuma

Home & Everyday Life

Monitor website and service availability, send incident notifications, and provide status pages.

Use with conditions
Last updatedRelease 2026-09-16
Open source licenseMIT
PlatformsLinux · Windows · Docker · Web
DeploymentContainers / self-hosted

About this project

Uptime Kuma is a self-hosted availability-monitoring application that repeatedly checks websites and services. Monitor types include HTTP(S), TCP, Ping, DNS, and WebSocket, along with keyword and JSON-query checks. Users configure a monitor for each target and inspect its changing status in a dashboard, providing an ongoing record instead of relying only on manually opening a website.

Notifications can use email, Telegram, Discord, Gotify, Slack, and other integrations. Multiple status pages, custom domains, latency charts, and certificate information support different ways of presenting the results. An internal monitoring dashboard and a public status page serve different audiences. Notification delivery still requires configuring the chosen channel; listing an integration does not establish a working connection.

Deployment options include Docker and a direct Node.js installation with its runtime and process-management prerequisites. Application data needs persistent storage, and the repository explicitly excludes NFS: a local directory or volume is required. The service listens on all network interfaces by default, with an option to bind locally, so exposure must be configured deliberately.

Decision guide
01

Why it is worth a look

  • HTTP, TCP, and Ping monitoring and multiple notification channels in one application
  • First-party usage or installation documentation is available
  • A verifiable formal release record is available
02

Before you use it

  • The monitoring instance itself must keep running
  • NFS data directories are unsupported; use a local directory or volume
  • The default published port is open on all network interfaces; check network exposure during deployment
Manual setupHigh
With an AI agentModerate
DeploymentContainers / self-hosted
Additional requirements3 confirmed; others not verified

Download the official Compose file into a new directory; Confirmed requirements: Command line, Docker, An always-on device or service; Some requirements have not been verified. Check the official setup instructions.

03

What it can do

  • HTTP, TCP, and Ping monitoring
  • Multiple notification channels
  • Status pages
  • Certificate information
  • Multifactor authentication

Who it fits

Good for

People running personal websites or home services; Small teams needing simple status pages

Not a fit

Unwilling to maintain a self-hosted service and not considering hosting providers; Only accepting a workflow without checking permissions and data backups

Getting started

  1. Download the official Compose file into a new directory
  2. Configure local persistent data and ports
  3. Start the service and create an administrator account
  4. Add monitors and manually test notifications