Duerelay

Reliable event and webhook delivery infrastructure

Visit Website
February 9, 2026 Building a small reliability layer for webhook and event delivery

I’ve been working on a backend infrastructure project focused on reliable event and webhook delivery.

The goal is to isolate common reliability concerns - durable event storage, async delivery, retries with backoff, idempotency, safe concurrency, and replay - into a standalone, reusable component rather than reimplementing this logic inside each product.

The system is API-only (no UI), designed to be embedded into existing services that rely on webhooks or internal events. It’s currently pre-revenue and still at an infrastructure stage, with the core delivery and failure-handling logic in place.

I’m sharing it here to get feedback from others building event-driven systems and to explore whether it makes more sense to continue developing it, open it up, or potentially hand it off to someone who needs this kind of component in their stack.

Happy to discuss architecture details or trade notes with anyone who’s dealt with webhook delivery failures, retries, or replay in event-driven systems.

3 Comments

  1. 2

    Congratulations on your launch. It looks impressive! What channels are you exploring to attract early users?

    1. 1

      Thank you!

      Duerelay was built inside a small portfolio of projects to solve a concrete operational problem and it’s currently used by another project we run.

      At this stage the focus isn’t scaling users. We are documenting what it does well, who it’s for, and deciding whether it makes more sense to keep it internal or transfer it to a team that already needs this kind of infrastructure.

      So we could say discovery is happening through direct conversations, founder communities and marketplaces rather than traditional growth channels.

      1. 2

        That makes total sense. It sounds like you're taking the right approach by validating your ideas internally and through direct conversations before scaling up.

        Using founder communities and marketplaces is a smart strategy, and Reddit can also fit in well here. It’s one of the few platforms where you can showcase your workflow, inquire about real pain points, and identify which audiences are genuinely engaged—without prematurely promoting a “product.”

        Once you decide to move beyond internal discovery, I would be happy to help you plan a small, discussion-driven rollout on Reddit. This can help you test your positioning and attract interested users naturally. Feel free to reach out to me anytime when you’re ready! 👍

About

Duerelay exists to address a common reliability gap in event-driven systems, where webhook and event delivery failures are often handled inconsistently or left to each product to reimplement. It provides a focused infras