Migrating from Hookdeck
This move is honest work, and this page says where: unlike a move from Svix, your consumers' verification code changes. What you get for that is a secret per destination instead of one per project — which is usually the reason people start this migration.
In short
- Hookdeck signs with its own scheme from a project-level secret; HookGet signs Standard Webhooks with a secret per endpoint. Consumers change their verification once — plan an overlap window for it.
- Destinations, filters and event routing recreate cleanly. Pricing moves from metered overage to an allowance: $199 on Pro includes 2 million deliveries.
- JavaScript transformations do not transfer. Six declarative operations cover reshaping; real logic moves into your publisher before the migration, not during it.
- If you self-host Outpost under Apache-2.0, or deliver to Kafka or RabbitMQ, staying is the honest recommendation — we say so below.
How to read this page. Every claim about another product below was read off that company's own public pages on 20 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, including the rows where we lose. If we have something wrong, tell us and it is fixed the same day.
First: which Hookdeck are you leaving?
- Event Gateway — receiving webhooks. Our inbound side verifies fifteen
providers before anything enters your pipeline (the list),
then applies the same retries, timeline and replay as any other event. One real loss:
hookdeck listenis a true local tunnel, and we deliberately do not run one — our local story is a forwarding file, which is simpler and less capable. If the tunnel is the feature you use daily, weigh that honestly. - Outpost — sending webhooks. The rest of this page.
What transfers cleanly
| Thing | How it moves |
|---|---|
| Destination URLs | Recreated through POST /v1/endpoints |
| Event routing and filters | Event types per endpoint, plus payload filters on the delivery body |
| Queue destinations | SQS and Pub/Sub map directly; Service Bus, S3-compatible buckets and a polling endpoint are also here. Kafka, RabbitMQ and EventBridge are not — see below |
| A fixed source address | Included on every plan here; a $100 add-on there |
| The consumer portal | Embeddable and white-label on every plan: POST /v1/portal-links with embed: true |
The part that is genuinely harder than leaving Svix
The Hookdeck signature is computed from the project's secret; a per-destination secret means configuring a custom signature or another destination auth method. HookGet is the reverse: Standard Webhooks per endpoint is the default, with rotation that overlaps two signatures so a switch costs no deliveries. The price of that default is paid once, during migration: every consumer replaces its verification with the Standard Webhooks function and its per-endpoint secret. Run both systems while consumers switch — the order of operations below is built around exactly this.
POST /hooks HTTP/1.1webhook-id: msg_01J8ZQ3F9VBAQ4E1S0TZY6P8YV
Stable across every retry — use it as your idempotency keywebhook-timestamp: 1755264000
Outside a 5-minute window, refuse it — that is the replay guardwebhook-signature: v1,ZeHt1v… v1a,mK4p…
HMAC and ed25519 side by side during a scheme change, space separated{"type":"order.created","timestamp":"…","data":{…}}
Signed content is id.timestamp.body — the exact bytes, never a re-serialisationWhat needs a decision
- Transformations. Hookdeck runs unlimited JavaScript transformations on every tier. We run none, deliberately: six declarative operations (pick, omit, rename, set, unwrap, wrap) reshape a payload, and logic beyond that belongs in your publisher. If your transformations contain real code, move it into the publisher before the migration and verify the output while Hookdeck still delivers.
- Non-HTTP destinations we do not have. Outpost delivers to Kafka, RabbitMQ and EventBridge; we deliver to SQS, SNS, Pub/Sub, Service Bus, buckets and pollers. A consumer wired to Kafka or RabbitMQ has no equivalent here today. That may decide the whole question, and it should.
- Compliance and SLA. Hookdeck publishes a SOC 2 report on request on every plan and a 99.999% SLA from Growth. We publish neither. If either is in your customer contracts, that is a reason to stay, stated plainly.
- Self-hosting. Outpost is Apache-2.0 and free to self-host forever. We are a managed service with no self-hosted edition. If owning the engine is why you chose Outpost, nothing on this page beats that.
The money, both directions
Managed Outpost at low volume is genuinely cheap — $10 per million with the first 50,000 free and no base fee — and if price alone is moving you, check that math first; below roughly a million deliveries a month it likely wins. The comparison changes with scale and with what sits around the delivery: Event Gateway overage starts at $3.00 per 100,000 ($30 per million at the lowest band), the tier with the SLA and 30-day retention is $499, and the static IP is $100 on top. Here, $199 on Pro includes 2 million deliveries, 30-day retention, the portal and the fixed address. The vs page has the full cost table at four volumes.
A safe order of operations
- Open a HookGet account and prove one delivery end to end on the test project.
- Move transformation logic into your publisher while Hookdeck still delivers; compare outputs.
- Recreate destinations for one small tenant and give its consumer the Standard Webhooks verification function and its new secret.
- Publish to both systems for that tenant; the consumer verifies whichever arrives, and you compare the two delivery logs.
- Stop publishing to Hookdeck for that tenant. Watch the timeline for a day.
- Repeat per tenant, largest last, and only then remove the old integration.
Start delivering webhooks today
Step one is an account and one test delivery. Test traffic is never metered.
Create a free account See pricing
10,000 deliveries a month free, no credit card. The free tier blocks rather than bills, so trying the product cannot produce an invoice — which is not true of every free tier in this category.
Verified 20 August 2026 against: Hookdeck pricing · Outpost pricing · Hookdeck authentication docs. Re-checked at least every 120 days.