HookDeploy

Webhook infra with private delivery, no open ports

Android

SaaS

Developer Tools

GitHub

Visit WebsiteSee on Product HuntApp Store ⧉Play Store ⧉Github ⧉Twitter ⧉

Hey Product Hunt! I'm Michael, solo founder of HookDeploy. I spent years as the default IT/ops person at mid-size companies, nobody that size hires someone specifically for webhook infrastructure, you just become the person who fixes it when something breaks and integrating a bunch of systems that were never designed to work together. The thing that actually pushed me to build this was cloud outages: not the outage itself, but the days after, trying to figure out which webhooks made it through and which silently didn't, re-entering data by hand, hoping I didn't double-process something that had actually gone through fine the first time. HookDeploy captures every webhook at the edge before forwarding it, so a bad config or downstream outage means a replay button instead of a week of manual cleanup. And instead of routing delivery through a shared tunnel service, we built our own source-available mTLS agent, so your infrastructure never needs an open port to receive anything. Taps is the feature I am most proud of - developers can tap into live traffic - the raw incoming webhook or post-transformation to a destination so you can debug in peace without interrupting production traffic. The mTLS agent runs a service on Linux, sits in the menu bar on Mac and in the tray on Windows. We are also shipping with iOS and Android apps so you can get notified as soon as something breaks and replay failures from your phone instead of running for the laptop. We also integrate with PagerDuty and Better Stack for incident management (we also have our own incident management), Slack and Discord for comms, and Zapier, Make, and n8n for everything else. Free tier is live, would genuinely love feedback, especially from anyone who's built or maintained their own webhook reconciliation scripts at 2am after an outage. That's exactly who I built this for.