Built by developers,
for developers.
RelayHQ was born from frustration. Building production systems that rely on webhooks means dealing with dropped events, failed retries, opaque delivery errors, and brittle infrastructure. We decided to build the webhook layer we always wanted — reliable, observable, and simple.
Our mission
Make webhook infrastructure invisible — so engineering teams can focus on the product logic that actually matters to their users.
What RelayHQ does
RelayHQ sits between your webhook providers (Stripe, GitHub, Shopify, or any HTTP source) and your backend services. It receives every webhook with a consistent < 50ms acknowledgement, stores it durably, and fans it out to all your destination services simultaneously.
When a destination fails, RelayHQ retries automatically with exponential backoff — up to 5 attempts. If all retries are exhausted, you get an alert and the request stays in your log, ready to replay with one click.
Routing rules let you filter which destinations receive which events — no code changes, no redeployments. Just configure the rule in the dashboard and it takes effect immediately.
What we believe in
Reliability first
Webhooks are mission-critical. We design every part of RelayHQ with the assumption that every event matters — there's no acceptable loss rate.
Developer experience
We build for engineers who want to move fast. Setup should take minutes, not days. The dashboard should answer your questions before you ask them.
Radical transparency
No black boxes. Every delivery attempt, retry, and failure is visible to you. We believe observability is a feature, not a debugging afterthought.
Pragmatic simplicity
We only build what solves real problems. RelayHQ does webhooks exceptionally well and doesn't try to be everything to everyone.
Timeline
RelayHQ founded
Started with a simple problem: webhook delivery in production is harder than it looks. Built the first version to solve it properly.
Multi-destination fanout
Added support for forwarding a single webhook to multiple destinations simultaneously — the feature most requested by early users.
Routing rules
Launched conditional forwarding based on webhook payload and headers, enabling teams to route events to different services without code.
Production launch
Deployed to global infrastructure on Fly.io with Neon Postgres and Upstash Redis. Public access with a generous free tier.
How it's built
RelayHQ is built on a production-grade stack chosen for reliability and low operational overhead:
Get in touch
Have a question, a feature request, or want to discuss an enterprise plan? We'd love to hear from you.