HookWatcher vs ngrok for webhooks
By the HookWatcher team · Updated
The short version
ngrok is a general-purpose ingress and tunnelling platform; webhooks are one use. HookWatcher is built around webhooks: a permanent capture URL with server-side history, replay against your current code, and tests. Use ngrok for production ingress, custom domains, TCP or traffic policies. Use HookWatcher when the provider should keep sending to one URL while you debug, whether or not your laptop is online.
Side by side
| HookWatcher | ngrok | |
|---|---|---|
| Public URL for localhost | hwcli tunnel: a public HTTPS URL for a local app; the caller gets your app's response; no WebSocket upgrades or customer-owned domains | Yes, the core product. Free includes one dev domain; bring-your-own domains on Pay-as-you-go |
| Requests while your machine is offline | Stored: capture endpoints keep every request; hwcli listen delivers them later | Not stored: agent endpoints exist only while the agent runs; cloud endpoints can answer with a custom offline response |
| Request history | Capture endpoints: Per plan (retention days and requests per endpoint), see pricing. Tunnel traffic: only on your computer | Traffic Inspector: 24 hours on Free, 72 hours on Hobbyist and Pay-as-you-go (up to 90 days with a Pay-as-you-go add-on) |
| Replay | Replay, Modify & Replay, and Replay Lab (duplicates, delays, sequences; concurrent and burst on paid plans) | Replay and replay with modifications in the local agent's inspector and the Traffic Inspector |
| Signature verification | Stripe and GitHub signatures verified against the captured bytes, plus test signatures for replays (paid plans) | verify-webhook traffic policy action for dozens of providers (500 verifications a month on Free) |
| Paid plans | Free, Developer, Pro, Team and Enterprise; limits and prices on pricing | Hobbyist $10 a month ($8 billed yearly); Pay-as-you-go $20 base; Enterprise from $10,000 a year |
| Free plan limits | See pricing | 1 GB transfer and 20,000 HTTP requests a month; a warning page in front of browser (HTML) traffic, not API clients |
| Regression tests and CI | hwcli test run replays saved real webhooks and checks responses; JUnit output | Not stated |
Where ngrok does more
- A general ingress platform: TCP, wildcard and custom domains, traffic policies, a Kubernetes operator and SDKs for Go, JavaScript, Python and Rust.
- Webhook verification for many more providers at the edge.
- Traffic shaping and security policies in front of production services.
Where HookWatcher does more
- A permanent capture URL with stored history, so nothing is lost while you're offline.
- Replay Lab, Debug Sessions and regression tests for webhook handlers.
- Forwarding to several destinations with per-destination retries.
Compare with a real webhook
Switching from ngrok
| With ngrok | With HookWatcher |
|---|---|
ngrok http 8080 | hwcli tunnel http 8080, when the caller needs your app's live response |
| Update the provider's webhook URL every time the tunnel URL changes | Point the provider at a HookWatcher endpoint once, then hwcli listen <endpoint> --to http://localhost:8080/webhooks whenever you work |
| Replay in the inspector at localhost:4040 | hwcli replay <request-id>, any time within your plan's retention |
Frequently asked questions
Should I use ngrok or HookWatcher for webhooks?
For webhooks during development, a capture URL is usually the better fit: the provider sends to one stable URL, nothing is lost when your laptop sleeps, and you can replay any delivery later. Use a tunnel (ngrok or hwcli tunnel) when the caller needs your app's real response, such as OAuth callbacks or URL verification challenges.
Does HookWatcher replace ngrok?
For webhook and local-development tunnels, often. Not for production ingress, TCP, WebSockets or your own domains, which ngrok supports and HookWatcher's tunnels don't.
Sources
- ngrok
- ngrok pricing
- ngrok free plan limits
- ngrok traffic inspection
- ngrok agent inspection interface
- ngrok verify-webhook action
- ngrok endpoints (agent and cloud endpoints)
HookWatcher facts: features, pricing, documentation. Something out of date? Tell us.