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.
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?
We've been running Nuntly's webhook delivery on self-hosted Outpost for months. Best decision we made: ripping out our in-house implementation.
Not going back.
We've been using Outpost since the beginning of the year while in beta and it's been great! Y'all are super responsive with feedback or issues, pricing is more than fair and generous free tier, and the UI is really polished too. Really enjoyed working with you guys and we're a happy customer :)
Wow, congrats on the launch, team! This is such a real infrastructure problem, and Outpost feels like a very clean, thoughtful answer to it. Love the open-source plus managed approach too. Excited to see this launch.
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.
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.
About Hookdeck Outpost on Product Hunt
“Open-source outbound webhooks for your platform”
Hookdeck Outpost launched on Product Hunt on April 23rd, 2026 and earned 111 upvotes and 14 comments, placing #15 on the daily leaderboard. 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.
Hookdeck Outpost was featured in API (98.1k followers), Open Source (68.4k followers), Developer Tools (511.7k followers) and GitHub (41.2k followers) on Product Hunt. Together, these topics include over 108.1k products, making this a competitive space to launch in.
Who hunted Hookdeck Outpost?
Hookdeck Outpost was hunted by fmerian. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Hookdeck Outpost stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
fmerian
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?