Push notifications finally solved my home lab alerting problem that email never could

Published Sep 23, 2026, 10:01 AM EDT His love of PCs and their components was born out of trying to squeeze every ounce of performance out of the family computer. Tinkering with his own build at age 10 turned into building PCs for friends and family, fostering a passion that would ultimately take shape as a career path. Besides being the first call for tech support for those close to him, Ty is a computer science student, with his focus being cloud computing and networking. He also competed in semi-pro Counter-Strike for 8 years, making him intimately familiar with everything to do with peripherals. Generating alerts from my home lab and its related services was always done via Proxmox for me. It was the simplest, included in the OS, and covered what I thought I needed. It generated a notification event, rendered it into an email, and handed it to Postfix, which delivered it in well under a second, but that's exactly the problem. Email isn't the most optimal way to get a notification in front of me—it's accessible through any device, but I have to be looking for it, and the push notification on my phone can be buried beneath other Gmail notifications. Ntfy solved this for me by enabling me to send push notifications to my phone directly, and when tied to other services, it doesn't die with the host like my Proxmox notifications did. The mail server has virtually no delay Email notifications get jumbled Postfix on a Proxmox host will hand off a message in under a second, and the receiving mail server will have it moments later. That part is fine, rock solid, but everything downstream is where the outages get missed. That message sits in my inbox until my mobile client fetches it, which it does so pretty consistently, but it's not always instantaneous. The real problem is that it can get buried easily. If I get another email or two on top of the notification from Proxmox, it becomes even more unlikely that it'd hit my radar. One of the bigger issues is that email downplays the severity on the surface. Proxmox's notification system does carry it: every event has a level of info, notice, warning, error or unknown, and you can route on it, but that's all hidden behind the email itself. On my end, all I see is a Gmail notification with no indication of if it's something to actually worry about. Proxmox already knows how to talk to a push server Ntfy is perfect here Since the notification system was reworked, Proxmox VE separates targets from matchers, and one of the supported target types is a plain webhook, which is a configurable URL with method, headers, and body. The official documentation mentions ntfy by name, which tells you how well the two fit together. ntfy is a pub-sub notification server with an HTTP interface: you POST to a topic, and anything subscribed to that topic gets a push. Self-hosted, it's a single Go binary, a deb package, and one YAML file, and it fits in an LXC with 512MB of RAM. It solves the problem of what email structurally can't solve, which is separate channels with separate urgency levels. Backup failures a Focus Mode on my phone that I've allowed through at maximum priority, and things like available package updates or other non-urgent notifications are left for when I feel like checking them. A dead host can't speak If it's dead, you'll need something else to speak to it If my Proxmox box shuts down because of a hardware failure or power outage, it has no way of communicating that. It only emits notifications for backup, replications, updates, and other non-shutdown related events. And since the ntfy instance is running on the host itself, if the host shuts down, the container obviously does too. There are smaller caveats that come along with this too: I'm running this to communicate with my phone primarily, which is running iOS. To get an iOS device to communicate with a self-hosted ntfy server, you have to configure upstream forwarding so that a poll request travels via ntfy.sh to APNs, then the phone fetches the real message from your server. It's a small thing, and doesn't exist on Android, but it's the difference between getting the notification instantly and getting it hours later. Running ntfy and Uptime Kuma off-site is the true setup Yet another reason to rent a VPS Checking for a heartbeat is the bare minimum, and to do so, you need an off-site machine. A cheap VPS is useful for so many things, but this is just another to add to the list. A push monitor in Uptime Kuma does this in about two minutes of setup, and whether it lives on that VPS or an SBC at a relative's house, the result is the same. Uptime Kuma keeps track of if something is up or not, and then running ntfy concurrently on the same device allows you to send downtime notifications. Nothing happens on my home lab without me knowing about it now I still have email alerts configured in Proxmox because they're a great fallback for the case where something on the system goes wrong, but the host is fine. They also act as a good archive for when I want to know what happened three weeks ago. Email is no longer the thing I'm relying on to tell me something is wrong right now, ntfy and Uptime Kuma do that for me, and my inbox is now just the paper trail.