Engineering notes from building Dispatch — webhook infrastructure, Go internals, honest comparisons, and the occasional war story.
Subscribe via RSS6 min read
Our events list said a webhook was delivered. The detail page for the same event said it had never been attempted. Both numbers were correct — only one of them came through row-level security.
6 min read
Both receive, verify, filter, transform, and deliver webhooks — then they part ways. Hookdeck terminates events in your services and queues; Dispatch terminates them in front of your team. An honest comparison.
8 min read
We let tenants render Go templates on our API servers for live preview. Bounding the language failed seven times. Inverting to an allowlist changed the failure mode — and that was the point.
5 min read
dispatch listen tunnels verified, filtered webhook events straight to localhost — with one-key replay, mid-session config changes, and every delivery logged. The whole workflow, in about a minute.