Five years after UnifiedPush launched, only about 20 apps support it and Android still has no native mechanism for custom notification servers. Users on HN and privacy forums explicitly wish Android supported specifying self-hosted notification servers. ntfy works well as infrastructure but the ecosystem adoption is stuck because app developers have no incentive to support an alternative protocol when Firebase is free and easy.
builder note
Don't build another push server. Build the adoption layer. A drop-in Android library that detects UnifiedPush distributors and falls back to Firebase transparently would let app developers support both with zero effort. The bottleneck is developer friction, not infrastructure.
landscape (3 existing solutions)
The infrastructure works (ntfy is solid). The protocol exists (UnifiedPush). What's missing is the adoption flywheel. App developers won't support UP without users demanding it, and users can't demand it without apps supporting it. A library that makes UP integration a one-line addition to Android apps could break this chicken-and-egg problem.
ntfy Excellent self-hosted notification server but requires manual setup and each app must explicitly integrate it UnifiedPush Good protocol standard but only ~20 apps support it after 5 years. No mainstream app adoption. NextPush Clever Nextcloud integration for self-hosted push but requires Nextcloud, limiting audience sources (3)
push-notificationsdegoogleandroidprivacyunifiedpush
Self-hosting email in 2026 is still described as pain despite Mailcow and Mail-in-a-Box automating the technical setup. The unsolved problem is deliverability: new IPs start with zero reputation, major providers penalize inactivity, and self-hosters lack the postmaster relationships that professional services maintain. Multiple 2026 articles confirm that email deliverability is no longer a technical problem but a reputation and relationship problem that no self-hosted tool addresses.
builder note
Don't build another mail server. Build the deliverability layer that wraps around existing servers. Think of it as a reputation management sidecar for Mailcow/MiaB that handles IP warming, blocklist monitoring, postmaster request automation, and sender score dashboards. That's the product nobody is making.
landscape (3 existing solutions)
Every self-hosted email solution solves the same problem (setting up Postfix/Dovecot correctly) while ignoring the actual hard problem (IP reputation management). The tool that automates IP warming schedules, monitors blocklists proactively, and provides deliverability dashboards for low-volume senders doesn't exist.
Mail-in-a-Box Automates DNS/SPF/DKIM setup perfectly but does nothing for IP warming, reputation monitoring, or blocklist management Mailcow More configurable than MiaB with Rspamd spam filtering but still no automated reputation management or deliverability monitoring Stalwart Mail Server Modern Rust-based server with excellent protocol support but same deliverability blind spot as all self-hosted options sources (3)
self-hosted-emaildeliverabilityreputationprivacyanti-surveillance