DueRelay

What it is

DueRelay is the webhook layer most teams build twice and never quite get right. Event ingest, durable queueing, signed delivery, retries with backoff, dead-letter handling, replay — the parts that look simple in a tutorial and turn into a maintenance graveyard at scale.

The product is built for two audiences with overlapping needs: SaaS teams shipping webhooks to their customers, and agentic systems that need durable, observable, policy-controlled event delivery between components. Same infrastructure, different surface emphasis.

What's built

• Multi-tenant event ingest, queueing, signed delivery, exponential-backoff retries, dead-letter queue with replay
• HMAC signing, idempotency keys, loop detection (rejects events that originated from DueRelay itself)
• Plan model: starter, core, scale, enterprise — with quota dimensions for events, endpoints, events-per-second, and retention window
• Stripe billing wired end-to-end — free tier, paid tier metering, overage at €12 per 25K-event block
• Agent Control Plane: SDK surfaces, policy enforcement, OTEL trace bundles, atomic event bundles, approval workflows
• Simulation sandbox for testing webhook handlers against synthetic event streams
• River — real-time multi-strand pipeline visualization (Three.js + SSE) showing event flow across endpoints in motion
• Get Started flow with latching achievement pills and an Overview that handles live health
• Operational blog at duerelay.com/blog

Architecture posture

Self-hosted on OVH. No platform lock-in, no managed-cloud dependency that locks the company into a renewal cycle. The stack is deliberately conservative — Go backend, Postgres for state, OTEL for observability, standard tooling end-to-end.

Multi-tenancy is a Class 1 invariant from the foundation. Tenant isolation, per-tenant rate limiting, and signing-key separation are non-negotiable architectural commitments, not features added later. The cost is some up-front design weight; the benefit is that growth doesn't compound into a tenancy migration crisis.

Idempotency is enforced on every external write. Stripe charges, webhook deliveries, third-party callbacks — all of them retry, and the system has to be safe under retry without operator intervention.

Who it's for

• SaaS teams that ship webhooks to their customers and want to stop maintaining the delivery infrastructure themselves
• Agentic systems and AI pipelines that need durable, observable, policy-controlled event delivery between components
• Engineering teams whose webhook layer is currently held together with cron jobs, ad-hoc retries, and manual intervention when deliveries fail
• Founders building event-driven platforms who want a well-engineered upstream rather than a vendor lock-in

Status

Live and operational. Billing is wired. Plans are priced. The product is running in production, the dashboards work, the events flow. What's missing is distribution — DueRelay is pre-revenue by choice, focused on getting the surface right before going wide.

The current focus is bringing on early users and design partners — particularly teams with real webhook volume that want to influence the next layer of features in exchange for early-adopter pricing and direct line to the builder.