Reliable infrastructure to work with webhooks and external events — without managing it yourself.
Two products: Event Gateway for Receiving Webhooks: Handle events from external providers before they hit your app — with full observability and control. And Outpost for Sending Webhooks: Deliver events to users' preferred systems reliably and securely — managed or self-hosted.
This is the 2nd launch from Hookdeck. View more
Hookdeck Outpost
Launching today
Send webhooks in minutes for one-tenth the cost. Outpost is open-source infrastructure that delivers to webhooks, SQS, Pub/Sub, RabbitMQ, Kafka, and more. Multi-tenant, at-least-once delivery, customer portal — self-hosted or managed.
Free
Launch Team / Built With
Hookdeck
Hey Product Hunt, and thanks to @fmerian for hunting!
We launched Outpost as an open-source project about a year ago to solve a problem we kept seeing: every platform that needs to send webhooks to their customers ends up building the same infrastructure from scratch: retries, tenant isolation, delivery logs, a portal for end users to manage their endpoints. It's a significant engineering investment for something that isn't anyone's core product.
Outpost was our answer to that: open source, self-hostable, and designed to be the last outbound webhook system you need to build.
Outpost doesn't just do webhooks. It supports Event Destinations, too: your customers can receive events via SQS, Pub/Sub, Kafka, RabbitMQ, and other brokers and queues, not just HTTP requests. This is something we've seen Stripe, Shopify, and Twilio all moving toward, and Outpost gives any platform the same capability out of the box.
We also now offer a managed version (Hookdeck Outpost) for teams that don't want to run the infrastructure themselves. It runs the exact same codebase (no proprietary fork). Pricing starts at $10 per million events, which makes it the most affordable managed option available.
Would love to hear from anyone who's currently maintaining a homegrown webhook delivery system. What are the biggest pain points? And if you've tried Outpost, what could we do better?
@fmerian @_gw iTICKET has been testing and using Outpost for the last few months and we honestly love it. We originally tried to roll our own webhook system using a bunch of db triggers and polling tasks, and while it worked, moving to Outpost has been a total game changer. It is basically set and forget - we can just trust it to work and go and handle the volume.
We had trialed SVIX previously and while there was nothing wrong with it, Outpost is leaps ahead. It is cost effective, cloud hosted, architecturally solid, and actually just a pleasure to use. The API and docs are fantastic too. Everything does what it says on the tin - it has been remarkably stable and consistent from day one.
Given Outpost is a product of the Hookdeck team and everything they have already established, it is no wonder this works so well.
Working with the team has been awesome, especially Alexandre who has spearheaded things with us and everyone has been incredibly responsive. It has been great contributing to the beta version and seeing how quickly the product has grown over recent months. Huge congrats to the team on the v1.0 launch!
@fmerian @_gw Open sourcing the outbound side is a good call. Most webhook infra is built for receiving, and when you need to send them reliably you end up reinventing retry queues and dead letter handling in your own app code. Does Outpost handle idempotency keys on the sending side or is that left to the consumer?
Hookdeck
@fmerian @whetlan Thanks Whetlan! Outpost handles it - the event id functions as the idempotency key (https://hookdeck.com/docs/outpost/destinations/webhook#event-format)
Hookdeck
Hey Product Hunters 👋 I lead DX at Hookdeck and have been working across the Outpost SDKs, docs, and parts of the codebase.
When we conceived Event Destinations and started building Outpost as the first open-source implementation, we thought it would be interesting and hoped it would land. It's done far better than we expected. Since the beta, we've worked hard with the open-source community and customers, and one of the things we hadn't specifically planned for was a managed version, but the demand for it was clear enough that we built it. That's what's launching today alongside the open-source v1.0.
Outpost is a manifestation of Event Destinations. Platforms need to deliver events wherever their customers actually want them, and to offer a really solid webhook option. HTTP isn't going anywhere, but for many use cases, delivering directly to a queue, stream, or broker is a better fit. Outpost covers both, and it's the best outbound event infrastructure available right now. It's simple, and with that comes really solid DX and ease of integration.
Outpost also fills a clear gap on the agentic side. So many companies are building with agents, for agents, or integrating with agents, and event infrastructure is foundational to a lot of what they need. Agents need to be triggered by events, and agents need to emit events when things happen inside their workflows. On task completion, on state changes, and on handoff. That's what enables agent-to-agent communication, event-driven agent initialization, and workflows where one agent's output triggers another agent's run.
Always looking for feedback on the product in general and on DX in particular.
Hookdeck
It's been a thrill to build Outpost. We took our experience receiving 100B webhooks from over 7k different vendors and condensed these learnings into a straightforward API and product. It's the fastest and most scalable way to send webhooks.
Liveblocks
Congrats on the launch!