HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
louislam
uptime-kuma
JavaScript2021–2026
louislam / uptime-kuma

uptime-kuma

A fancy self-hosted monitoring tool

36Distinct people
45Mentions
1Explicit recommenders
93.6KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A fancy self-hosted monitoring tool

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I installed Uptime Kuma (https://github.com/louislam/uptime-kuma) on my dokku paas to monitor my dokku apps. It works great. It is great for pure HTTP services, but it can be…

xrd used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 1:02:30 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year45 dated mentions

Observed mentions: 2021-08-03 09:37:01 UTC to 2026-10-08 23:27:36 UTC.

0510152021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 9 mentions; 1 submissions, 8 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 13 mentions; 2 submissions, 11 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 11 mentions; 0 submissions, 11 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC321
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC707
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC918
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC13211
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC11011
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC202

What Hacker News says

9 sources
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/
In Show HN: I was frustrated with pricing of PagerDuty et al., so made one myself
Currently I have a hybrid setup, where stuff that needs more compute or storage (which are cheaper if you buy hardware) runs locally in my homelab, whereas the things that need better uptime or more bandwidth are available in rented VPSes. I've actually played around with what is hosted where, depending on what I need: for example, uptime monitoring currently runs locally, checking whether I can reach the remote sites from my residential connection. LOCALLY (in my homelab) - Startpage, with Heimdall: https://heimdall.site/ - Backups, with BackupPPC: https://backuppc.github.io/backuppc/ - Twitch stream and YouTube video backups, with PeerTube: https://joinpeertube.org/ - File sharing for larger files, with Nextcloud: https://nextcloud.com/ - Chat solution, with Mattermost: https://mattermost.com/ - Project management, with OpenProject: htt
Read the rest
ps://www.openproject.org/ - CI runners, with Drone CI: https://www.drone.io/ - Minecraft servers, with docker-minecraft-server: https://github.com/itzg/docker-minecraft-server - Static code analysis, with SonarQube: https://docs.sonarqube.org/latest/ - Uptime monitoring, with Uptime Kuma: https://github.com/louislam/uptime-kuma PUBLICLY (in rented VPSes) - Code repositories, with Gitea: https://gitea.io/en-us/ - CI, with Drone CI: https://www.drone.io/ - Package/container management, with Nexus: https://www.sonatype.com/products/nexus-repository - File sharing, with Nextcloud: https://nextcloud.com/ - Link shortener, with Yourls: https://yourls.org/ - Mail server, with docker-mailserver: https://github.com/docker-mailserver/docker-mailserver - Analytics, with Matomo: https://matomo.org/ - Container management, with Portainer: https://www.portainer.io/ - Server monitoring, with Zabbix: https://www.zabbix.com/ - Blog, with Grav: https://getgrav.org/ My homepage and some other projects as well. I manage most of these as Docker containers (with Swarm, though K3s is great too), so thankfully handling data backups and resource limits is pretty easy. Currently, I use Apache as the reverse proxy in front of all of these (lots of modules for a variety of features, as well as Let's Encrypt integration with mod_md). So far it seems to work decently, isn't too expensive, helps me avoid e-waste (homelab nodes run 200 GE CPUs with 35 W TDP), although updates are always a pain. The blog has more information about some of these pieces of software, in case anyone is interested: https://blog.kronis.dev/ For example, previously I ran GitLab, but Gitea + Drone + Nexus proved to be a better solution for my needs and workloads.
In Ask HN: What's on your home server?
> I don't mind if the protocol if FUBAR. It works for me and it works for an awful lot of people. And it encrypts the web. To me, it feels like most stuff becomes much more troublesome once you peel back the curtain and drop down to the internals. For most folks (myself included), using a web server that handles most of this for you will be enough. There's Traefik, there's Caddy and plenty of other options. Even Apache has support for ACME with mod_md, about which I wrote on my blog last year: https://blog.kronis.dev/tutorials/how-and-why-to-use-apache-... It's not perfect (you still need a restart/reload for the new cert to be actually used), but the configuration side of things is simple enough and most of the issues are known: https://httpd.apache.org/docs/2.4/mod/mod_md.html > Before that, it was manually re-creating a cert, faffing w
Read the rest
ith chains (converting formats and dealing with bad documentation) and update the production servers manually. It was a royal PITFA. This has always been a pain to me, for example, the OpenSSL CLI is a bit like tar in how unintuitive it is, vs something like the Docker CLI which walks you through a tree of commands with all of their parameters that you might be interested in. Curiously, I've had most success with using graphical software for manually working with certificates, like Keystore Explorer: https://blog.kronis.dev/tutorials/lets-run-our-own-ca The linked article is a bit barebones (I didn't feel like Googling for the OpenSSL equivalents for the actions to demonstrate the difference in UX), but I want to express the importance and usefulness of your software (CLI, TUI, GUI, API, whatever) telling you what options are available to you, which makes a world of difference. In my eyes, there's no reason why a junior dev or someone who hasn't worked with OpenSSL (or an equivalent piece of software) in the past should have their first time doing so be miserable. Then again, needing to think about bunches of different formats and what technology accepts what is probably always going to be at least moderately painful or annoying: https://serverfault.com/a/9717 > Don't forget to set a calendar reminder for the next year's renewal. Thankfully, this is pretty easy to deal with! Even if you use ACME, you'll still want this in place, in case automatic cert renewal fails, or if the cert just isn't swapped over to by the web server. For example, for the self-hosting crowd, something like Uptime Kuma allows you to have all sorts of reminders, including certificate expiry: https://github.com/louislam/uptime-kuma (note: Uptime Kuma does not batch those notifications, I got about 30 messages in Slack at the same time because a bunch of sites had the same wildcard certificate that was going to expire) Basically, it's nice to see that as a end user of software you can have a decent experience, for the most part. Definitely a bit better in some regards than what you might have been dealing with 10 years ago or so. Not that all of the problems or nitpicks are solved, or will be for the foreseeable future. Personal worries: what if Let's Encrypt becomes a non-viable option for whatever reason? There aren't that many ACME compatible providers out there.
In I still have an old-school cert on my HTTPS site

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.