HookGet vs Hookdeck
An event gateway with the strongest local-development story in the category, plus Outpost, their Apache-2.0 self-hostable engine.
In short
- Choose Hookdeck if: You want a local tunnel, non-HTTP destinations through Outpost, transformations, or you would genuinely rather self-host.
- Choose HookGet if: You want per-endpoint secrets and rotation as the default rather than as configuration, and you do not want to run the infrastructure.
- Both sign with, or are compatible with, Standard Webhooks — so consumers usually do not change.
- Every line about Hookdeck below was read off their own pages on 16 August 2026, and links to the page it came from.
How to read this page. Every claim about another product below was read off that company's own public pages on 16 August 2026, and each one links to the page it came from — check it yourself, that is what the links are for. Pricing and features move without anyone telling us, so our build fails if this page goes more than 120 days without a re-check. Everything stated about HookGet is something you can verify in the product today. If we have something wrong, tell us and it is fixed the same day.
Where Hookdeck is stronger
- A local tunnel CLI —
hookdeck listenforwards real events to localhost, and they position it as a free replacement for ngrok. source - Unlimited transformations on every tier, including the free one, plus filtering on inbound traffic. source
- Outpost is Apache-2.0, and they state it is the same binary either way: "No private forks or proprietary versions." source
- Outpost delivers to AWS SQS, RabbitMQ and Kafka, not only to HTTPS endpoints. source
- A SOC 2 Type 2 report is available on request on every tier, including the free one. source
- Managed Outpost is priced at $10 per million events, and self-hosting it costs nothing. source
- They run an MCP server too, through the same CLI — an assistant can operate their gateway as it can ours. source
Trade-offs to weigh
- The Hookdeck signature is computed from the project's secret. A per-destination secret means configuring a custom signature or another destination auth method instead. source
- Retention is 3 days on the free tier, 7 on Team ($39/month) and 30 on Growth ($499/month). source
- Inbound URLs live on their domain (
hkdk.events) — although that is true of every hosted gateway, ours included. source
Where HookGet is different
| Capability | HookGet |
|---|---|
| Signature scheme | Standard Webhooks, the open specification |
| Retry schedule | 8 attempts over ~21 hours, settable per endpoint |
| Secret rotation | Per endpoint, with an overlap window so nothing drops |
| Dead letters | Kept, inspectable, replayable — with the original event id |
| Recovery | One call resumes a disabled destination and replays what died |
| Gap repair | Re-queues events that were published but never attempted |
| Auto-disable | 50 consecutive failures, or immediately on 410 Gone |
| Operational events | Disable and recovery are published as events you can subscribe to |
| Inbound sources | 15 providers verified before anything enters the pipeline |
| Rate limiting | Token bucket per endpoint, plus per project and per source |
| Egress safety | Two independent layers against reaching private networks |
| Agent interface | An MCP server over the same API, 18 tools |
| Hosting | EU, Frankfurt, with no region premium |
| Teams | Four roles, expanded per request, with an audit log |
What HookGet does not have
If any of these is a requirement, Hookdeck or another option in the comparison is the better answer, and we would rather you found that out here.
| Capability | Status |
|---|---|
| Embeddable customer portal | Not yet. Your team gets a dashboard; your customers do not get their own page |
| Transformations | Not available. Events are delivered as published |
| Local tunnel CLI | Not available |
| Non-HTTP destinations | Not available. Delivery is HTTPS |
| mTLS / OAuth2 to destinations | Not available |
| Compliance reports | No SOC 2, HIPAA or PCI attestation today |
| Self-hosting | Not available today |
Moving between them
Consumers that verify Standard Webhooks signatures do not change. What needs planning is the destination list, the secrets and any feature above that we do not have. The migration guide covers the patterns, including running both in parallel before you commit.
Questions
Is HookGet a drop-in replacement for Hookdeck?
For delivery and signatures, largely yes — both sign with or are compatible with Standard Webhooks, so consumers usually need no change. Anything you use that we list as not built is not a drop-in, and the honest answer is to check that list before you plan a move.
When should I stay with Hookdeck?
You want a local tunnel, non-HTTP destinations through Outpost, transformations, or you would genuinely rather self-host.
How do the retry policies differ?
HookGet defaults to eight attempts over about 21 hours and lets you set the schedule per endpoint, which matters when one destination needs a tighter or looser rhythm than the rest. Check the current schedule in their documentation — it is the kind of detail that changes.
Verified 16 August 2026 against: Hookdeck's site. Re-checked at least every 120 days.