What does HackerNews think of uptime-kuma?

In what ways is it better than Uptime Kuma which doesn't require a bunch of SaaS spaghetti to run and has much broader community support.

[1] https://github.com/louislam/uptime-kuma

I run Uptime Kuma[1] in my home to monitor all my homelab and Kubernetes services. It's really awesome. How does OpenStatus compare to it?

[1] https://github.com/louislam/uptime-kuma

It's for people who owns a lot of servers/computers at home and need to monitor its uptime.

For safety reason, it's impossible to expose the system to the public internet, we can only use the "push" strategy to report the up status. This tool is just for this purpose: request an URL at some interval repeatedly.

Recommend to use this with uptime-kuma (https://github.com/louislam/uptime-kuma)

Uptime-Kuma [1] with ntfy [2]. Most of my services expose HTTP so I just have Uptime-Kuma monitor that. But if you have something that is not exposed to the public you can still use a "push" type monitor, and in a cron job on your server(s), send heartbeat to it when everything is working.

[1] https://github.com/louislam/uptime-kuma

[2] https://ntfy.sh/

Frustrated by expensive per-seat pricing and unfriendly contract terms, we looked for PagerDuty alternatives and found a fantastic open-source project called Uptime Kuma: https://github.com/louislam/uptime-kuma

Uptime Kuma is one of the few open-source projects that feels like a commercial product: polished user experience, frequent release cadence, and a rich set of features including monitoring PostgreSQL servers, Docker containers, and so much more. Its list of supported notification services is so long that I don't even recognize half of the options available. Truly impressive.

Side note and shameless plug… We love Uptime Kuma so much that we made it one of the cornerstone applications provided by Fortressa, which we think of as the “App Store for Open Source”: https://fortressa.com/