I'm Michael and I built HookDeploy. HookDeploy is a webhook infrastructure tool that captures webhooks at the edge, allows for inspection, transformation and fanout to multiple destinations including to your own private infrastructure with our first-party (source-available) mTLS agent. Runs as a service on Linux, lives in the tray on Windows and in the menu bar on Mac.
As I'm sure most of you you have felt webhooks kind of suck if things don't go exactly as planned. Dropped webhooks or failures are likely silent. What actually drove me to build this was cleaning up after major cloud outages more than once. Cross referencing what System A knew against what System B actually had and reentering data by hand or trying to simulate events firing again. I have spent weeks of my life cleaning up webhook failures. HookDeploy solves that problem with a button and intelligent grouping of failed requests into incidents. If you've ever seen or had to clean up after a ransomware attack - you understand why I'd prefer to keep my firewall as tight as possible too.
Our agent enables developers and teams to keep ports closed - if there is nothing to scan, there is nothing to attack. Getting to our own mTLS agent was a journey of trying to integrate existing solutions: first WireGuard (too much operational overhead), then Tailscale which was excellent, but it had real drawbacks on the required memory per joined tailnet and the additional cost to a user's Tailscale bill. It took several months to get it right, but it was worth every week of it.
A few things to note at launch: we are launching with security measures in place: data is encrypted at rest with org-scoped keys rotated weekly (BYOK is on the roadmap), segregated databases for US, EU, APAC and AU so customer data stays where customers are not traversing underwater fiber to come to the US. We have 7 private delivery exit regions: San Francisco (us-west), New York (us-east), London (uk-london), Amsterdam (eu-west), Frankfurt (eu-central), Singapore (ap-southeast) and Sydney (au-southeast).
Our platform is built primarily on Cloudflare for speed and security utilizing workers, KV, R2, Queues, Tunnels/VPC, and of course DNS and security.
This has been some time in the making and I am excited to answer your questions and get feedback! Thank you in advance!
I'm Michael and I built HookDeploy. HookDeploy is a webhook infrastructure tool that captures webhooks at the edge, allows for inspection, transformation and fanout to multiple destinations including to your own private infrastructure with our first-party (source-available) mTLS agent. Runs as a service on Linux, lives in the tray on Windows and in the menu bar on Mac.
As I'm sure most of you you have felt webhooks kind of suck if things don't go exactly as planned. Dropped webhooks or failures are likely silent. What actually drove me to build this was cleaning up after major cloud outages more than once. Cross referencing what System A knew against what System B actually had and reentering data by hand or trying to simulate events firing again. I have spent weeks of my life cleaning up webhook failures. HookDeploy solves that problem with a button and intelligent grouping of failed requests into incidents. If you've ever seen or had to clean up after a ransomware attack - you understand why I'd prefer to keep my firewall as tight as possible too.
Our agent enables developers and teams to keep ports closed - if there is nothing to scan, there is nothing to attack. Getting to our own mTLS agent was a journey of trying to integrate existing solutions: first WireGuard (too much operational overhead), then Tailscale which was excellent, but it had real drawbacks on the required memory per joined tailnet and the additional cost to a user's Tailscale bill. It took several months to get it right, but it was worth every week of it.
A few things to note at launch: we are launching with security measures in place: data is encrypted at rest with org-scoped keys rotated weekly (BYOK is on the roadmap), segregated databases for US, EU, APAC and AU so customer data stays where customers are not traversing underwater fiber to come to the US. We have 7 private delivery exit regions: San Francisco (us-west), New York (us-east), London (uk-london), Amsterdam (eu-west), Frankfurt (eu-central), Singapore (ap-southeast) and Sydney (au-southeast).
Our platform is built primarily on Cloudflare for speed and security utilizing workers, KV, R2, Queues, Tunnels/VPC, and of course DNS and security.
This has been some time in the making and I am excited to answer your questions and get feedback! Thank you in advance!