What problem it solves

Users need a way to monitor the availability of services and receive timely notifications when something fails. A suitable self-hosted monitoring solution must support multiple service types, flexible deployment options, and clear status reporting.

Key features

• Broad monitoring coverage — Monitor HTTP and HTTPS endpoints, TCP services, keyword and JSON queries, WebSockets, ping targets, DNS records, push endpoints, Steam game servers, and Docker containers.

  Source: README

• Multi-channel notifications — Send alerts through established messaging and email services, including Telegram, Discord, Gotify, Slack, Pushover, and SMTP.

  Source: README

• Status pages and monitoring details — Publish multiple status pages, associate them with specific domains, and review ping charts and certificate information alongside uptime monitoring.

  Source: README

• Flexible deployment and access — Run the monitoring service with Docker Compose, a Docker command, or a non-Docker Node.js and PM2 setup. Proxy support and two-factor authentication are also available.

  Source: README, compose.yaml

Quick start

Copied verbatim from the project's README.

docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:2

Who it may suit

This project may suit system administrators, developers, and self-hosting enthusiasts who need to monitor services through a deployment they control.

Topics to discuss

• Which additional monitor types would be most useful for the community?

• Which notification integrations should receive priority next?

• What deployment or configuration challenges need clearer documentation?

Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.

Read the original README https://github.com/louislam/uptime-kuma#readme

ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.