[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f6sk1vskh8muj":3},{"code":4,"message":5,"data":6,"timestamp":68},10000,"success",{"full_name":7,"position":8,"description":9,"language":10,"stars":11,"forks":12,"stars_gained":13,"age_days":14,"hn_threads":15,"one_liner":40,"summary_md":41,"topic":42,"github_topics":45,"license":58,"homepage":59,"updated_at":60,"history":61},"louislam\u002Fuptime-kuma",5,"A fancy self-hosted monitoring tool","JavaScript",92880,8605,58,1940,[16,21,27,31,36],{"id":17,"title":18,"points":19,"comments":8,"posted_at":20},28809501,"A fancy open-source self-hosted monitoring tool",59,"2021-10-09",{"id":22,"title":23,"points":24,"comments":25,"posted_at":26},37159980,"Uptime Kuma: An easy-to-use self-hosted monitoring tool",2,0,"2023-08-17",{"id":28,"title":29,"points":24,"comments":25,"posted_at":30},28047254,"Uptime Kuma: A fancy self-hosted monitoring tool","2021-08-03",{"id":32,"title":33,"points":34,"comments":25,"posted_at":35},39408788,"Uptime Kuma is an easy-to-use self-hosted monitoring tool",1,"2024-02-17",{"id":37,"title":38,"points":34,"comments":25,"posted_at":39},39101866,"Uptime-Kuma: A fancy self-hosted monitoring tool","2024-01-23","A self-hosted uptime monitor for people who want to watch their own services without paying for a hosted uptime service.","If you run a handful of servers or sites and want alerts when something stops responding, Uptime Kuma gives you a dashboard and notification routing you can host yourself. The author's stated motivation was finding a self-hosted alternative to hosted uptime services, since the closest option they found was no longer maintained.\n\n## The problem\n\nBefore Uptime Kuma, checking whether a service is up often means either paying a hosted monitoring service or cobbling together cron jobs and a notification script. You want to define checks for HTTP endpoints, TCP ports, DNS records and more, then be told quickly when one fails. With Uptime Kuma, that check configuration, status display and alert routing live in one self-hosted web app, so the setup step changes from scripting each check to adding it in the UI and picking a notification channel. The result is a dashboard with per-check history, ping charts and optional public status pages.\n\n## What's different\n\nIts main draw is breadth of check types paired with a reactive web UI. The README lists HTTP(S), HTTP keyword and JSON query, TCP, Websocket, Ping, DNS record, Push, Steam game server and Docker container checks, with 20-second intervals. Notifications cover Telegram, Discord, Gotify, Slack, Pushover, SMTP email and a long list of other services, and you can publish multiple status pages mapped to specific domains. Certificate info, proxy support and 2FA round out the operational bits.\n\nThe trade-off is scope. A 2021 Hacker News commenter noted it is not aimed at heavyweight platforms like Nagios, NMS or Zabbix and accepted that it would not scale like them. That framing still matters: this is a single monitoring app with a friendly UI, not a distributed observability stack. The same thread also raises the self-hosting question: if your monitoring host goes down, you lose visibility, so an external check on the monitor itself is worth planning ([thread](https:\u002F\u002Fnews.ycombinator.com\u002Fitem?id=28809501)).\n\n## Who should try it\n\nGood fit: an individual or small team running a few sites, home-lab services or internal tools who wants a visual dashboard, several notification channels and public status pages without operating a large monitoring system. The live [demo](https:\u002F\u002Fdemo.kuma.pet\u002Fstart-demo) lets you poke at the UI before installing. Poor fit: someone who needs large-scale, multi-node monitoring comparable to Nagios or Zabbix, or who cannot host the monitor somewhere that stays reachable when the services it watches fail.\n\n## Requirements and limitations\n\nThe documented install paths are Docker Compose, a single `docker run` command, or a non-Docker install requiring Node.js 20.4+, Git and pm2 for background running. The non-Docker path supports major Linux distributions and Windows 10\u002FServer 2012 R2 or higher, but explicitly not FreeBSD\u002FOpenBSD\u002FNetBSD or Replit\u002FHeroku. NFS-backed storage is not supported, so data must live on a local directory or volume; that matters for anyone planning to put the database on a NAS share. The Docker command exposes port 3001 on all interfaces by default, and the README shows how to bind it to localhost only.\n\nOngoing care means updates and backups: the README defers upgrades to a separate wiki guide, so check that before deploying a version you intend to keep. If you need reverse-proxy or other advanced setups, the install wiki is the place to start rather than assuming the default command covers it.\n\n## HotRepo's take\n\nHotRepo recorded 92,862 stars on 2026-10-24 (+49) and 92,870 on 2026-10-25 (+58), with those two days on the daily trending board. That is far too little comparable history to judge whether interest is rising or fading; it only confirms a large existing following and a recent appearance. The practical question is whether a single self-hosted instance fits your failure domain: verify how you will monitor the monitor before committing.",{"slug":43,"name":44},"devops","DevOps & Self-hosting",[46,47,48,49,50,51,52,53,54,55,56,57],"docker","monitor","monitoring","responsive","self-hosted","selfhosted","single-page-app","socket-io","uptime","uptime-monitoring","webapp","websocket","MIT","https:\u002F\u002Fuptime.kuma.pet","2026-10-25T02:51:57Z",[62,66],{"date":63,"stars":64,"stars_gained":65},"2026-10-24",92862,49,{"date":67,"stars":11,"stars_gained":13},"2026-10-25",1792918769]