Hookman

Hookman is built around a narrow problem in branch-based development: webhook providers such as Stripe and Paddle expect a fixed callback URL, but preview deployments change with every branch. Instead of editing provider settings each time, Hookman gives you one permanent endpoint and handles the routing behind it.

The service sits between webhook providers and your deployments. You create a project, get a stable URL like hookman.dev/w/acme/payments, and define which branch or deployment should receive events. A CLI command such as hookman switch –branch main changes the target immediately, and routing rules can send the same event to multiple deployments. Routing runs on Cloudflare’s edge with latency under 2ms.

It is aimed at developers and small teams who test payment flows, subscription events, or other webhooks across feature branches and preview environments. Anyone who has repeatedly updated a Stripe dashboard while reviewing a pull request will recognize the use case.

A sensible workflow is to create one Hookman project per provider or event group, point the provider at the stable endpoint once, and use the CLI or dashboard to switch targets during testing. The free tier covers 1,000 webhooks per month, which is enough to evaluate the service before committing.

Hookman is a focused utility rather than a full webhook platform, and that focus is what makes it worth considering for branch-heavy development workflows.