reddit · SideProject · 10-05 06:50 60 分 ← 返回列表

I built HookArmor: An open-source webhook buffer & DLQ because Stripe's 5-minute replay window kept breaking our deploys

Hey r/SideProject , I wanted to share a tool I built called **HookArmor** ([GitHub]( https://github.com/pkdoddamani/hookarmor ) | [npm]( https://www.npmjs.com/package/hookarmor) ). It is a lightweight, self-hosted webhook dead-letter queue (DLQ) and reliability buffer built with Node.js and SQLite. ### The Problem That Triggered This If you accept billing or sync webhooks from providers like Stripe, Shopify, or GitHub, you’ve probably run into this headache: Webhook providers enfo

五维评分

付费意愿

需求真实度

个人可落地

竞争空间

新鲜度

AI 分析

痛点：Stripe/Shopify/GitHub 等 webhook 有 2-5 秒超时限制，部署或故障时易丢失；超过 Stripe 5 分钟重放窗口又会被签名校验拒绝，企业级 relay 贵且自建 Kafka/RabbitMQ 太重。

目标用户：使用 Stripe、Shopify、GitHub 等 webhook 的独立开发者、小型 SaaS 团队和后端工程师。

证据：I didn't want to pay $50+/month for enterprise webhook relays, nor did I want to manage a complex Kafka/RabbitMQ/Redis cluster just to reliably buffer incoming webhooks. / Stripe includes a timestamp in the Stripe-Signature header ... their official SDK enforces a strict 5-minute tolerance window. Any replay after 5 minutes throws a signature verification exception

变现：开源核心 + 托管云服务：按 webhook 量或月订阅收费；高级功能包括多租户、审计日志、告警、自动重放、团队协作和 SLA。

MVP：2 周内做托管版 HookArmor：一键接入 Stripe，持久化接收 webhook，异步转发到用户应用，失败入队，提供简单 dashboard 手动/自动重放，并处理 Stripe 签名时间戳问题。

竞品：Hookdeck、Svix、Convoy、Stripe 官方 webhook 重放、AWS SQS/SNS + Lambda、RabbitMQ/Kafka/Redis 自建方案

摘要：作者因 Stripe 5 分钟重放窗口和 2-5 秒 webhook 超时问题，开发了开源自托管工具 HookArmor，用 Node.js + SQLite 做轻量 DLQ 和可靠性缓冲。帖子明确提到不想支付 $50+/月的企业级 relay，也不愿维护 Kafka/RabbitMQ/Redis，说明 webhook 可靠性有真实痛点，但当前是开源自发布，缺少他人付费验证，且竞品较多。适合做低门槛托管版或开源商业化。