Skip to main content

Notification Gateway

Your server IP is in every webhook field.

Every endpoint, every email forward, every service config — all pointing at your server. Reverse Proxy for ntfy sits in front so your URL, topics, and tokens stay hidden, and your servers fail over automatically.

Built-in Interpreters

Twelve parsers for Statuspage.io, Synology DSM, Seerr, pfSense, UniFi, Transmission VPN, pfSense Actions, Discord Stonker Bot, Outpost, Mailmask, 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. Webhook senders never see your ntfy server's address.

A closer look

One context for each sender

Give every webhook or mailbox its own context with its own address, topic, and token or sender filter, so each source is kept apart and easy to turn off.

✔ What would you like to do? › Manage Contexts✔ Manage Contexts › Add? Context type: › - Use arrow-keys. Return to submit.❯   HTTP    Email

From the Blog

Launches, milestones, and what's new in Reverse Proxy for ntfy.

What's New in v2.0.0: Interpreters, Email Routing, and a CLI

Version 2.0.0 adds built-in interpreters for Synology, pfSense, Seerr, Statuspage, and UniFi, email-to-notification routing, and an interactive CLI.

Routing 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.

Why We Built a Reverse Proxy for ntfy

Routing webhooks from self-hosted services to ntfy servers with subdomain-based matching, delivery failover, and request filtering on Cloudflare Workers.