Blog
RSSNotes from the delivery path
Engineering deep dives, webhook debugging guides, and what we're learning building private webhook infrastructure.
- Engineering
How We Cut Our Cold-Path Latency From 2600ms to 650ms
How HookDeploy cut cold-path latency from a 2600ms regression down to 650ms: parallelizing sequential Supabase calls, adding a missing cache layer, moving R2 writes off the response path, and consolidating three config lookups into one cached RPC.
- Reliability
The Outage Ends. The Cleanup Doesn't.
Why HookDeploy exists: a firsthand account of cleaning up after Azure and AWS outages, hunting down which webhooks made it and which silently didn't, and why capturing and replaying webhooks beats manual reconciliation every time.
- Private Delivery
Why Our CLI and Desktop Agent Are Source Available
Why HookDeploy's CLI and desktop agent are source available under BSL 1.1, not fully open source: full code transparency for the software that runs on your infrastructure, an intact git history, and a pre-launch resilience audit that caught real bugs before customers could.
- Infrastructure
Multi-Region from Day One: What It Actually Costs
How HookDeploy built real data residency from day one: four fully separate regional databases (US, EU, APAC, AU), Cloudflare's global edge for fast ingestion, and a CI pipeline that keeps identical code running everywhere so customer data never leaves its region.
- Private Delivery
Why We Killed WireGuard and Tailscale for Our Own mTLS Agent
Why HookDeploy replaced WireGuard and Tailscale with a first-party mTLS agent: unlimited free development agents, no per-seat networking costs passed to customers, and built-in GDPR compliance via EU-restricted exit nodes.
- Security
What Security Means to Us
What security means at HookDeploy: break-glass access, weekly-rotating encryption keys, fail-closed architecture, and hardware-key-only staff access.
- Infrastructure
Why We Chose Cloudflare as Our Cloud Provider
How HookDeploy's edge-first architecture led us to Cloudflare: Workers for zero-latency ingestion, R2 for egress-free payload storage, and Cloudflare Tunnels with VPC connectivity to route webhooks privately to our first-party mTLS agent on customer infrastructure.