WebhookLens vs ngrok

ngrok is great for throwaway dev tunnels. When the webhook matters in production, you want a persistent URL, a dashboard, replay, and alerting. That's WebhookLens.

Try WebhookLens free See the comparison

TL;DR

Pick WebhookLens if…

  • Your webhook URL needs to live past your laptop session.
  • You want a persistent history, replay, and inspection dashboard.
  • You want transforms and routing, not just a tunnel.
  • You want the CLI tunnel and a cloud proxy — WebhookLens has both.

Pick ngrok if…

  • You only need a tunnel for a local dev session (a few hours).
  • You're exposing arbitrary HTTP services, not just webhooks.
  • You're fine with losing the URL and history when you quit the tunnel.

Feature comparison

Feature WebhookLens ngrok
Persistent webhook URL✓Paid reserved domain
Real-time live stream dashboard✓Inspector (local)
Event history & search✓ (30/60d retention)Session only
Replay✓ (1-click + CLI)Inspector replay
Signature validation13+ providers✕
Payload transforms✓✕
Smart routing (fan-out)✓✕
Alerting✓✕
CLI tunnel for local dev✓ (webhooklens-cli listen)✓
Self-hosted option✓ (ELv2 Docker image)✕
Starting priceFree / €12/moFree / $8/mo

Using the CLI

If the ngrok muscle memory is ngrok http 3000, WebhookLens is the same vibe — but the webhook URL keeps working after you close the terminal:

webhooklens-cli login --server https://app.webhooklens.cloud
webhooklens-cli listen --port 3000

Anything hitting https://proxy.webhooklens.cloud/wh/<your-slug>/<endpoint> lands in your local app and your dashboard — live. When you close the terminal, webhooks keep arriving; history, replay, transforms all keep working.

Migration

  1. Sign up free — Developer tier, 500 events/mo.
  2. Install the CLI: go install github.com/webhooklens/webhooklens/cmd/cli@latest
  3. Login + listen: webhooklens-cli login then webhooklens-cli listen --port 3000
  4. Replace the ngrok URL in Stripe/GitHub/Shopify with the proxy URL shown in the dashboard.

Start free   Back to home