Built-in Interpreters
Seven parsers for Statuspage.io, Synology DSM, Seerr, pfSense, UniFi, plain text, and ntfy JSON. Raw payloads go in. Clean notifications come out.
Server Failover
Define a primary ntfy server with ordered fallbacks. If the primary is down, the next one picks up. Send-once or send-all — your call.
Email Routing
Receive emails via Cloudflare Email Routing and convert them into push notifications. No inbox required.
Interactive CLI
Add servers, create contexts, configure interpreters, and deploy — all through a terminal UI. No TOML. No hand-editing.
Smart Splitting
Messages over 4,000 bytes are automatically split into numbered parts that fit within ntfy's message limits. Nothing gets truncated.
Edge Security
Origin IP shielding, per-context token auth, sender filtering, HTTPS enforcement. Your ntfy server stays off the public internet.
By the Numbers
7
Built-in interpreters
2
Delivery modes
0
Manual config editing
∞
Server fallbacks per context
From the Relay Room
Release notes, integration guides, and the occasional deep dive.
What's New in v2.0.0: Interpreters, Email Routing, and a CLI
Version 2.0.0 is a complete rewrite — built-in interpreters for Synology, pfSense, Seerr, Statuspage, and UniFi, email-to-notification support via Cloudflare Email Routing, message splitting, and an interactive CLI.
Read moreRouting Webhooks by Subdomain: One Worker, Many Services
How ntfy-reverse-proxy routes webhooks from multiple services to the right ntfy topic using subdomain-based matching on a single Cloudflare Worker.
Read moreWhy We Built a Reverse Proxy for ntfy
If you run self-hosted infrastructure with an ntfy server, you need a reliable way to forward webhooks. This Cloudflare Worker handles routing, delivery, and filtering at the edge.
Read more