Start Building

Webhook infrastructure

Relay webhooks.
Reliably. At scale.

Durelay accepts, verifies, and delivers webhook traffic in milliseconds — then keeps retrying until it lands. One relay layer for every tenant, every destination, every queue.

Start Building View the docs

202 Accept quickly. Deliver durably.

Durelay technical proof points

≤50msp95 accept time
Paralleldestination fan-out
Per-tenantdata isolation
HMACsigned in and out

Why Durelay

Every team rebuilds webhook fan-out. You shouldn’t have to.

Accepting webhooks reliably, fanning them out to every destination a customer configures, retrying the ones that fail, and keeping an inspectable log of what happened — it’s the same plumbing every platform team ends up building from scratch. Durelay is that layer, built once, done right.

How it works

One relay layer. Three durable paths.

Accept once. Choose how each tenant’s traffic moves from there.

01 / Relay Endpoints

One inbound URL. Every outbound destination.

Point a webhook source at a single Durelay URL and fan it out to every destination that needs it — in parallel, with automatic retries on a backoff schedule, and a live delivery log you can inspect and replay from. Your source gets a fast 202 Accepted the moment the request is verified; Durelay handles delivery from there.

↳ Per-destination signing is optional and configurable independently for each destination on the same Relay Endpoint.

deliverieslive
api.customer-a.comdelivered204
hooks.customer-b.ioretrying503
events.internaldelivered200

02 / Queue Endpoints

Turn inbound webhooks into a durable queue.

Every Queue Endpoint gets its own dedicated, isolated queue, so inbound traffic lands somewhere durable instead of straight into your application. Configurable token time-to-live, strict per-tenant isolation, and headroom for payloads up to 100MB when your default limit isn’t enough.

queue / tenant_08isolated
evt_4fe2 · 42 KBevt_4fe1 · 18 KBevt_4fe0 · 64 KB
depth003token ttl12h

03 / Direct Connect

Let your app talk to the queue directly.

When you need the shortest possible path, Direct Connect mints short-lived, narrowly scoped credentials so your application reads and writes a Queue Endpoint’s queue directly — no payload ever passes through Durelay’s relay layer.

scoped credential
dc_live_••••••••••8k2p
queueq_tenant_08
scoperead:write
expires in00:47:32

Security & isolation

Built to isolate. Built to verify.

Standard SaaS-grade security practices, enforced at the request, destination, and tenant boundaries.

01

Signed requests, both directions

Inbound requests are HMAC-verified before anything happens; outbound deliveries can be signed per destination so receivers can verify Durelay as the source.

02

Isolation by default

Every tenant’s configuration, data, and traffic is kept separate at the platform level, not bolted on.

03

Scoped, short-lived credentials

Direct Connect access is narrowly scoped per queue and expires on a schedule you control, not a standing secret.

Editions

Start small. Keep the same delivery model.

Feature limits scale with your traffic. Pricing is being finalized.

Durelay Starter, Growth, and Enterprise feature comparison
Compare editions
StarterPricing pendingStart Building
Growth RecommendedPricing pendingStart Building
EnterpriseTalk to usContact Us
Max Relay Endpoints325Unlimited
Max Queue Endpoints110Unlimited
Max destinations per Relay Endpoint310Unlimited
Requests / minute per endpoint60600Negotiated
Requests / month per account100,0002,000,000Negotiated
Max queue token TTL1 hour12 hours24 hours
Log retention7 days30 days90+ days
Large payload add-on (up to 100MB)—Add-onIncluded
Outbound destination signing—IncludedIncluded
Idempotency keys—IncludedIncluded

Developer experience

A few lines, not a few sprints.

Send a signed request to one Relay Endpoint. Durelay acknowledges it, creates a delivery, and handles the fan-out from there.

Read the docs
Illustrative API example
$ curl -X POST \\
  https://api.durelay.com/v1/relay/rel_01HQ7K \\
  -H "X-Durelay-Signature: sha256=…" \\
  -d '{"event":"invoice.paid"}'

HTTP/1.1 202 Accepted
{"deliveryId":"dlv_01J8N4…","status":"accepted"}

FAQ

The details engineers ask first.

What’s the difference between a Relay Endpoint and a Queue Endpoint?

A Relay Endpoint fans a single inbound request out to multiple outbound HTTP destinations. A Queue Endpoint writes the inbound request straight into a dedicated, durable queue instead of calling anything directly.

How fast is delivery?

Requests are accepted and verified in well under 50ms at the 95th percentile. Fan-out to your destinations happens in parallel afterward, so five destinations resolve about as fast as one.

What happens if a destination is down?

Durelay retries automatically on a backoff schedule and keeps a live, inspectable log with manual retry available for anything that still fails.

Is my data isolated from other tenants?

Yes. Isolation is enforced at the platform level for every tenant, by default.

Can I skip the relay and connect directly to my queue?

Yes — Direct Connect issues short-lived, scoped credentials so your application can read and write a Queue Endpoint’s queue directly over the wire.

The relay layer is ready

Stop rebuilding webhook plumbing.

Start Building