Migrate from Hookdeck
Use HookSense for inspection, Hookdeck for delivery.
Hookdeck is a great event gateway — for outbound delivery. If you've been using it just to debug inbound webhooks, the $39 + metered overage isn't justified. HookSense is purpose-built for inspection.
Step 1 · Identify what to migrate
- 1In Hookdeck, list your inbound sources (the ones receiving webhooks, not the ones sending).
- 2Decide which ones are purely for debugging vs. which need queueing/SLA delivery.
- 3Debug-only sources move to HookSense. Production delivery stays on Hookdeck (or migrate to Svix).
Step 2 · Map features
| In Hookdeck | In HookSense |
|---|---|
| Source (e.g., `stripe`) | Endpoint (`/w/stripe-prod`) |
| 10k events/mo + $0.33/100k overage | Sense flat $49 = 50k req/day, ~1.5M/mo, no overage |
| Connection (1 source → N destinations) | Not 1:N delivery — HookSense replays manually to any URL |
| Issue tracker (failed deliveries) | Auto-retry (Sense) + AI diagnose v2 — same intent, narrower scope |
| SSO/SAML (Growth $499) | SSO available on Enterprise ($199 — contact sales) |
Step 3 · Things to know
- If you use Hookdeck for 1-source → N-destinations fan-out, HookSense is NOT a replacement. Pair the two: Hookdeck delivers, HookSense inspects.
- Hookdeck's 'replay all failed events from last week' is a built-in feature. HookSense replays individually or via the new transformation API.
- Compliance/audit log: Sense doesn't include audit log; if you need it, plan for Enterprise.
Zero-downtime migration
Try HookSense Sense for 14 days (full refund window). Migrate one source at a time. Keep Hookdeck running for production delivery; HookSense for the debug loop.
Start with a free endpoint