Comparison · Updated November 2026
ngrok vs Hookdeck
ngrok and Hookdeck both get a webhook from the internet to a server on your laptop, and they are built for different jobs. ngrok is a tunnel: a local port gets a public address and traffic passes straight through. Hookdeck is an event gateway: it receives the webhook on its own URL, stores it, and delivers it to your server or, through its CLI, to localhost.
What each one is for
ngrok
ngrok gives a local port a public URL. The free plan comes with one assigned ngrok-free.app domain that stays the same when you restart the agent, HTTP endpoints, and TCP once a card is verified. The sender talks to your app through the tunnel, so it gets your app's own response, and the agent has to be running when the request arrives. Requests show in the local inspector at localhost:4040 and in the dashboard's Traffic Inspector, where they can be replayed.
Hookdeck
Hookdeck's Event Gateway sits between the sender and your server. It accepts each request on a Source URL, logs it as an event, and delivers it to a destination with retries: up to 50 automatic ones per event, and manual ones as often as you like. For local work, hookdeck listen forwards events to a port on your machine, and Hookdeck Inspect gives you a test URL with no account. Hookdeck describes the two together as a free alternative to ngrok for webhooks.
Features and pricing
| Feature | ngrok | Hookdeck |
|---|---|---|
| What it is | A tunnel from a public URL to a local port | An event gateway that receives, stores and delivers webhooks |
| Forward webhooks to localhost | ngrok http 3000 | hookdeck listen 3000 |
| Who answers the sender | Your local app, through the tunnel | Hookdeck accepts the request; your app gets it as a delivery |
| A webhook sent while nothing is listening | The agent must be running to receive it | Stored; retry or replay it once a listener is connected |
| Request history | Traffic Inspector: 24 hours on Free, 72 hours on paid plans | Event log: 3 days on Developer, 7 on Team, 30 on Growth |
| Replay | From the inspector | Retry any event by hand; failed events retry automatically, up to 50 times |
| Free plan | 1 GB of data and 20,000 HTTP requests a month, up to 3 endpoints, 1 user | 10,000 events a month, 3-day retention, 1 user |
| Paid plans | Hobbyist $10/mo; Pay-as-you-go $20/mo plus usage | Team from $39/mo; Growth from $499/mo; events metered past 10,000 |
| Rate limits | 4,000 HTTP requests a minute on Free, 20,000 on paid plans | 5 events a second per destination included; more is queued, not dropped |
| Protocols | HTTP, TCP, and TLS on Pay-as-you-go | HTTP requests |
| Team members | 3 included on Pay-as-you-go, then $5 per user | Unlimited on Team and up |
| MCP server | Yes | Yes: local, through the CLI, read-only to begin with |
ngrok as listed on ngrok.com/pricing and in its docs, Hookdeck as listed on hookdeck.com/pricing and in its docs, in November 2026; "not documented" means we did not find it there. Check their pricing before you buy.
When to pick which
Pick ngrok when
- The sender has to get your local app's own response
- You expose more than webhooks: a website, an API or a TCP service
- You want one address that stays the same on a free plan
- You need your own domain or sign-in rules in front of the endpoint
Pick Hookdeck when
- Webhooks should be kept while your machine is off, for you to retry once it is back
- You want retries, queueing and rate limits between the sender and your server
- The setup you test with should carry on into production
- Several people need the event log: users are unlimited from the Team plan
Where webhooks.cc fits
webhooks.cc is built for the part both tools treat as a side job: testing. An endpoint captures every webhook and keeps it (7 days on Free, 31 on Pro), whether or not anything runs on your machine. whk tunnel forwards each one to localhost, and whk tunnel --live makes the sender wait for your local app's answer, the way a tunnel does.
The SDKs for TypeScript, Python and Go wait for a webhook and assert on it in CI, and whk share puts a local site at a public link. It is not a production gateway like Hookdeck, and it has no TCP tunnels like ngrok.
webhooks.cc vs ngrok · webhooks.cc vs Hookdeck · Live tunnels · Share localhost
Try it yourself
Frequently asked questions
ngrok vs Hookdeck: which should I use for webhook forwarding?
Use ngrok when the sender needs your app's response at once, or when you expose more than webhooks. Use Hookdeck when webhooks should be stored and retried, in development and in production; what arrives while its CLI is not listening is kept, and you retry it yourself. ngrok passes each request straight to your local port; Hookdeck accepts it on its own URL and delivers it as an event.
Is Hookdeck a replacement for ngrok?
For receiving webhooks on localhost, Hookdeck says so itself: its docs describe the Hookdeck CLI with Hookdeck Inspect as a free alternative to ngrok for webhooks. It is not a general tunnel, so for showing a local website to someone, or for TCP, ngrok is the tool.
Which has the larger free plan for webhooks?
ngrok's free plan allows 20,000 HTTP requests and 1 GB of data a month on up to 3 endpoints, and keeps traffic in its inspector for 24 hours. Hookdeck's Developer plan allows 10,000 events a month and keeps them for 3 days. Both are for one user. Figures from each pricing page in November 2026.
What happens to a webhook sent while my laptop is closed?
With ngrok the agent has to be running for the request to reach anything. Hookdeck still stores the request when no CLI listener is attached; once you start a listener you retry or replay it by hand. A webhooks.cc endpoint captures it either way, and you replay it to localhost when you are back.
See also: ngrok vs Webhook.site · Hookdeck vs Webhook.site · ngrok vs LocalTunnel · ngrok vs Cloudflare Tunnel · All comparisons
Start testing webhooks in under a minute
Sign up with one click. No credit card, no setup wizard, no trial limits on core features.