Pushover vs. Ntfy: Which Protocol Actually Keeps Your Self-Hosted Watchdogs From Silencing Your Phone?
The entire discussion centers on achieving reliable, real-time phone notifications stemming from self-hosted computing environments, spanning everything from Home Assistant automations to external Virtual Private Server uptime monitoring.
The divide is sharp: some users insist on premium, paid services like Pushover because of perceived rock-solid reliability, while others aggressively defend open, self-hosted protocols such as ntfy.sh. superglue backs ntfy regardless of controversy, while mhzawadi champions Pushover's cost-effective, paid structure. A major technical point came from KexPilot, who revealed Android notifications flow through centralized providers like Google, bypassing the need for direct port forwarding.
The consensus points toward a clear functional divide. Established open protocols (ntfy, Uptime Kuma) are touted as the community's preferred, robust, non-subscription solution. However, the technical breakthrough explaining how these alerts work—via centralized OS services rather than direct network tunnels—is the definitive insight moving the conversation forward.
Key Points
Pushover is cited as the most reliable option despite requiring payment.
mhzawadi pushed this view, noting its excellent pay-as-you-go model, even pointing to Dan's decade-long positive experience.
ntfy remains a reliable, community-supported open alternative.
superglue scored ntfy highly, asserting its reliability works for the user implementation, countering any current debate.
Android notifications utilize a centralized provider, not direct application connections.
KexPilot provided the technical 'how-to' breakthrough, explaining why alerts work externally without physical port forwarding.
A combination of Uptime Kuma and ntfy provides a robust monitoring loop.
stratself suggested linking Uptime Kuma for service monitoring with ntfy, or alternatively, using a simple cron/cURL script for failure triggers.
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.