CyberNord Relay - Recover the exact event behind the incident.
by•
CyberNord Relay helps teams monitor, diagnose, and safely replay failed webhooks and event deliveries. Capture every attempt, compare payloads and responses, detect recurring failures, prevent duplicate processing, and preserve an auditable recovery timeline. Built for payment, SaaS, commerce, and distributed systems where a missed event can become lost revenue or an operational incident.
Replies
Hi Product Hunt 👋
I’m Nikita, solo founder and lead engineer behind CyberNord Relay.
Relay helps engineering teams recover failed webhooks without manually reconstructing what happened across logs, retries, alerts, and incident tools.
When a webhook fails, the hard question isn’t “did it fail?” It’s: what changed, what is safe to replay, and how do we leave a clear recovery record?
With Relay, teams can:
capture and inspect webhook deliveries and every delivery attempt;
validate signatures for Stripe, GitHub, Shopify, and generic HMAC sources;
diagnose failures using payload, response, timing, status, and provider context;
replay original, edited, batch, or shadow events in a controlled workflow;
configure delivery and latency alerts, incident grouping, and recovery timelines;
export traffic and audit history, and apply retention policies.
Relay is built for payment flows, SaaS integrations, e-commerce, and any event-driven workflow where a lost event can become lost revenue or a customer incident.
It is early-stage and focused: Relay does not claim to replace your full observability or incident-management stack. Its job is to make failed-event recovery understandable, controlled, and auditable.
I’d love feedback on:
Which webhook failures consume the most engineering time for you?
What evidence do you need before approving a replay?
Which provider integration should Relay support next?
Product Hunt launch offer: 50% off any Relay subscription until December 31, 2026 — code PRODUCTHUNT50.
Thank you for supporting a solo founder building from Ukraine. 🚀