TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Show HN: Outpost – OSS infra for outbound webhooks and event destinations

65 点作者 alexbouchard2 天前
Hey HN, we&#x27;re launching Outpost, an open-source, self-hostable component designed to handle outbound event delivery for SaaS&#x2F;API platforms.<p>If you&#x27;re building a platform, you eventually need to send events to your users (think payment success, resource updates, workflow changes). Implementing this reliably—handling retries, monitoring, scaling, providing a decent dev experience for consumers, and managing tenants—becomes a significant, recurring engineering task that distracts from core product development. We built Outpost to offload that complexity.<p>Outpost delivers events via traditional webhooks and also directly to event destinations like message queues and buses. While webhooks are ubiquitous, they have limitations at scale regarding cost, reliability patterns, and security posture. We observed platforms like Stripe, Shopify, and Twilio offering direct bus&#x2F;queue integrations for these reasons—it&#x27;s often cheaper and more resilient. It offers a better DX for consumers who prefer programmatic consumption. Outpost provides this flexibility out of the box as a core feature.<p>Key features:<p>- Multiple Delivery Methods: Webhooks + native Event Destinations (SQS, Kinesis, GCP Pub&#x2F;Sub, RabbitMQ, Hookdeck, etc.).<p>- Guaranteed Delivery: At-least-once guarantee with configurable automatic retries.<p>- Observability: Built-in event log &amp; OpenTelemetry support.<p>- Management: API for destination (endpoint) management; optional User Portal for end-user self-service (debugging, destination management).<p>- Multi-tenancy, topics, webhook security best practices (signatures, timestamps), etc.<p>Given you most likely already have a system in place, Outpost is backward compatible with your existing payload format, HTTP headers, and signatures.<p>It&#x27;s written in Go and licensed under Apache 2.0. It&#x27;s still early days, and we&#x27;d love your feedback – especially on the architecture, desired event destinations, or any rough edges you find.<p>GitHub: <a href="https:&#x2F;&#x2F;github.com&#x2F;hookdeck&#x2F;outpost">https:&#x2F;&#x2F;github.com&#x2F;hookdeck&#x2F;outpost</a> Docs: <a href="https:&#x2F;&#x2F;outpost.hookdeck.com&#x2F;docs" rel="nofollow">https:&#x2F;&#x2F;outpost.hookdeck.com&#x2F;docs</a><p>Thanks for checking it out!

4 条评论

ksajadi2 天前
Looks great! how is this different from your commercial offering (Hookdeck)?
评论 #43905972 未加载
simplesagar2 天前
Congrats on the launch! This is really exciting and seems like an obvious progression on how companies can expose their event streams. Interfaces like kafka are so ubiquitous compared to webhooks. This seems to build on that with infrastructure to take care of all the failure points and tough devex. Anyone who&#x27;s worked with webhooks knows how common failures are!
评论 #43908610 未加载
jonbo3722 天前
Really excited to try Outpost — especially appreciate that it’s open source. Looking forward to testing it in a real-world setup and sharing feedback!
评论 #43908600 未加载
farbour2 天前
Well done guys!