Control your notifications without code changes. Route to Slack, Discord, Email & more. Mute noisy alerts, throttle chatty services, and escalate critical issues—all from a web UI. Built-in retries, real-time dashboards & AI agent integration.
Hey Product Hunt! 👋 I built NotifyGate because I was tired of:
- Getting flooded by the same alert 100 times during an outage
- Deploying code just to change where notifications go
- Having zero visibility into what notifications are actually being delivered
NotifyGate sits between your services and notification channels. You send events to one API, then control everything else from the dashboard—routing, throttling, muting, escalation, and more. The best part? You can change any of this instantly without touching your code. During a maintenance window? Toggle a mute rule. New team member needs alerts? Add a routing rule. Noisy service? Throttle it. I'd love your feedback! What notification pain points do you deal with?
Report
@red_lin Really nice product I like the focus on team collaboration. I’m currently working solo, but I’d love to try it as the team grows. If you’re ever open to a conversation around improving product security as you scale, happy to connect
@sujal_meghwal Thanks a lot — really appreciate it! Feel free to try it anytime as you grow, and I’d be happy to hear your security thoughts as I scale. Let’s stay in touch .
Report
@red_lin happy to give my security thoughts do you want create private communication line b/w us or you want to go full public mode
Report
Wow, NotifyGate looks amazing! The idea of throttling chatty services without code is brilliant. How granular can I get with the muting - can I silence specific types of events from a service, or is it all-or-nothing?
@jaydev13 Thanks so much for checking out NotifyGate! 🎉
To answer your question - yes, the muting is very granular! You can silence specific event types, filter by severity level, target specific projects/modules, match on metadata fields, and even use regex patterns on titles. It's designed so you can surgically mute exactly what you need without affecting everything else.
I'd love to get you set up to try it out! If you'd like an invite, just let me know and I'll get that sorted.
And genuinely - any feedback you have would be incredibly valuable. Whether it's:
Features you wish existed
Anything confusing in the UI or docs
Use cases that aren't well supported
Rough edges you run into
I'm all ears. This is the kind of input that shapes where the product goes next, so don't hold back!
Report
Really need this. Will it automatically retry after detecting a delivery failure?
@emmy_sepulvedaYes! NotifyGate uses Oban for job processing, which automatically retries failed deliveries up to 5 times with exponential backoff.
If a notification fails to deliver (e.g., webhook timeout, Slack API error), it will:
Retry automatically with increasing delays
Log the failure details so you can see what went wrong
Mark the event as failed only after all retries are exhausted
The retry behavior is configurable per-queue if you need different retry strategies for different notification types. Would love to hear if you have specific retry requirements we should consider!
NotifyGate
@red_lin Really nice product I like the focus on team collaboration. I’m currently working solo, but I’d love to try it as the team grows. If you’re ever open to a conversation around improving product security as you scale, happy to connect
NotifyGate
@sujal_meghwal Thanks a lot — really appreciate it! Feel free to try it anytime as you grow, and I’d be happy to hear your security thoughts as I scale. Let’s stay in touch .
@red_lin happy to give my security thoughts do you want create private communication line b/w us or you want to go full public mode
Wow, NotifyGate looks amazing! The idea of throttling chatty services without code is brilliant. How granular can I get with the muting - can I silence specific types of events from a service, or is it all-or-nothing?
NotifyGate
@jaydev13 Thanks so much for checking out NotifyGate! 🎉
To answer your question - yes, the muting is very granular! You can silence specific event types, filter by severity level, target specific projects/modules, match on metadata fields, and even use regex patterns on titles. It's designed so you can surgically mute exactly what you need without affecting everything else.
I'd love to get you set up to try it out! If you'd like an invite, just let me know and I'll get that sorted.
And genuinely - any feedback you have would be incredibly valuable. Whether it's:
Features you wish existed
Anything confusing in the UI or docs
Use cases that aren't well supported
Rough edges you run into
I'm all ears. This is the kind of input that shapes where the product goes next, so don't hold back!
Really need this. Will it automatically retry after detecting a delivery failure?
NotifyGate
@emmy_sepulveda Yes! NotifyGate uses Oban for job processing, which automatically retries failed deliveries up to 5 times with exponential backoff.
If a notification fails to deliver (e.g., webhook timeout, Slack API error), it will:
Retry automatically with increasing delays
Log the failure details so you can see what went wrong
Mark the event as failed only after all retries are exhausted
The retry behavior is configurable per-queue if you need different retry strategies for different notification types. Would love to hear if you have specific retry requirements we should consider!