Why We Built a Reverse Proxy for ntfy
info
This post describes version 1.x. Version 2.0.0 is a full rewrite with built-in interpreters, email support, and an interactive CLI. See What's New in v2.0.0 for the current feature set.
If you run self-hosted infrastructure — a company server or a home lab — and you use ntfy for notifications, you've probably pointed a few webhooks at your ntfy server directly. It works, but it doesn't scale well. Every service needs the server URL and topic hardcoded. There's no filtering, no fallback if the server goes down, and no way to route different services to different topics without giving each one a different endpoint.
We built ntfy-reverse-proxy to sit between your services and your ntfy server, handling routing, delivery, and filtering on Cloudflare Workers.