Uptime Kuma, a self-hosted uptime monitor, runs checks every 20 seconds from one container
The MIT-licensed JavaScript project monitors HTTP(s), TCP, ping, DNS, WebSocket and Docker targets, serves status pages and sends alerts to 90+ notification services.
What the project is
louislam/uptime-kuma describes itself as an easy-to-use self-hosted monitoring tool. The README’s motivation section says the author was looking for a self-hosted tool like “Uptime Robot”, found the closest option, statping, to be unstable and no longer maintained, and set out to build one with a better UI.
The repository is written in JavaScript, licensed under MIT and was created on 2021-07-03, so it is not new. It is back on GitHub trending: as a snapshot at the time of writing it had 94177 stars, 432 of them gained in the last day, and 8800 forks, with the last push on 2026-11-14.
What it monitors
The feature list covers these check types:
- HTTP(s), HTTP(s) Keyword and HTTP(s) Json Query
- TCP, Ping and DNS Record
- Websocket
- Push monitors
- Steam Game Server
- Docker Containers
Checks can run at 20-second intervals. Alerts go out via Telegram, Discord, Gotify, Slack, Pushover, Email (SMTP) and, per the README, 90+ notification services in total. The tool can serve multiple status pages and map status pages to specific domains. It also shows a ping chart and certificate info, supports proxies and offers 2FA. The interface is multi-language, with translations handled through Weblate.
On the technical side, the topics list a single-page app built on socket-io and WebSocket. The motivation section says the project tried WebSocket with an SPA instead of a REST API, and used Vue 3, vite.js and Bootstrap 5.
Running it
The quickest route is Docker Compose: download the project’s compose.yaml and run docker compose up -d. A single container also works:
docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:2
Either way, the README notes that Uptime Kuma then listens on all network interfaces on port 3001. To limit exposure to localhost only, it suggests publishing the port as -p 127.0.0.1:3001:3001. For a monitoring dashboard, that default deserves attention before the container goes on a host with a public address.
Two further cautions in the README: file systems like NFS are not supported for the data directory, so map it to a local directory or volume; and the top Google result for the name, uptimekuma.co, is not the official website.
Without Docker, the requirements are Node.js 20.4 or newer, Git and pm2 for running in the background. Supported platforms include major Linux distros such as Debian, Ubuntu, Fedora and ArchLinux, and Windows 10 (x64) or Windows Server 2012 R2 (x64) or higher. FreeBSD, OpenBSD, NetBSD, Replit and Heroku are listed as unsupported. Setup is npm run setup, then node server/server.js to try it or pm2 start server/server.js --name uptime-kuma to keep it running.
Trying before installing
A public demo server is available from the README. It is a temporary instance: all data is deleted after 10 minutes. For questions, the project points to GitHub Issues and the r/UptimeKuma subreddit rather than email.
Source: louislam/uptime-kuma on GitHub