# Webhooker vs Svix vs Hookdeck (2026)

> Svix, Hookdeck and Webhooker compared on direction, hosting region, retention, billing unit and DPA, with a source for every fact.

Source: https://webhooker.eu/blog/webhooker-vs-svix-vs-hookdeck
Last updated: 2026-09-15

If you are comparing Svix vs Hookdeck, or looking at alternatives to either, Webhooker shows up in the same searches, and all three can now receive webhooks. They still differ on the things that decide a purchase: which direction each product was built around, where your payloads are stored, how long they are kept, what you are billed for, and which plan includes a DPA. Once you know which way your traffic flows and where it has to live, the right pick is usually clear.

We build Webhooker, so we have a side in this. To make the comparison checkable, every fact about Svix and Hookdeck below links to the vendor’s own pricing page or documentation, checked on 13 September 2026. Prices and regions change, so check them again before you sign anything.

## Do Svix, Hookdeck and Webhooker solve the same problem?

The word “webhook” hides two opposite jobs, and both of them are the reverse of [calling an API yourself](https://webhooker.eu/blog/webhook-vs-api). Outbound means your product sends events to your customers’ endpoints. You are the publisher, so you care about fan-out to many subscribers, subscriber management, per-tenant signing, and giving customers a way to see their own delivery logs. Inbound means your product receives events from Stripe, GitHub, or a payment provider. Now you care about verifying signatures, absorbing traffic spikes, retrying failures without duplicating side effects, and never dropping a payload on the floor.

A typical inbound failure goes like this. A team wires up a receiving endpoint for Stripe, it works in testing, then a Friday-night deploy takes the downstream service offline for ten minutes. Stripe keeps retrying on its own schedule, some events land and some don’t, and on Monday nobody can say which invoices were processed. Outbound tooling does nothing for that problem; it needs a receiver that stores events and retries delivery itself.

Svix started on the outbound side, as webhooks-as-a-service for teams that send events, and added [Svix Ingest](https://www.svix.com/ingest/) for receiving. Hookdeck’s Event Gateway is built for receiving, and a separate product, Outpost, handles sending. Webhooker only receives. Before comparing pricing, it helps to understand [what a webhook gateway does](https://webhooker.eu/blog/what-is-a-webhook-gateway).

## How do you choose between them?

Pick the criteria that match your traffic, then score each tool against them. These eight cover most of the decision:

- **Direction.** Are you sending webhooks to customers (outbound) or receiving them from third parties (inbound)? This is the biggest fork, and it tells you which of each vendor’s products you are evaluating.
- **Hosting and residency.** Where does the data live? Webhook payloads routinely carry personal data, so for EU teams under GDPR, [where the pipeline is hosted](https://webhooker.eu/#eu) can decide the purchase on its own.
- **Verification.** Does it [verify inbound signatures](https://webhooker.eu/blog/webhook-security-signature-verification) so you can trust that an event really came from Stripe or GitHub, and can it sign outbound requests so your downstream services can trust it?
- **Reliability.** [Retries with backoff](https://webhooker.eu/blog/webhook-retries-exponential-backoff), a circuit breaker that stops hammering a dead endpoint, a [dead-letter queue](https://webhooker.eu/blog/webhook-dead-letter-queue-replay) for events that exhaust their retries, and a replay button for when you’ve fixed the bug.
- **Transformations.** Can you reshape, enrich, or filter payloads before they reach your services, so you aren’t rewriting adapters in application code?
- **Outbound addresses.** If any destination sits behind a corporate firewall, delivery only works from [a stable set of IPs you can hand to their security team](https://webhooker.eu/blog/static-outbound-ip-webhooks). Shared serverless egress ranges change without warning.
- **Pricing model.** What is the billing unit, and are retries and fan-out counted? Each model breaks at a different point, which we cover in [the four webhook pricing models side by side](https://webhooker.eu/blog/webhook-pricing-models).
- **Compliance.** Is a data processing agreement available, and on which plans? For regulated buyers, the answer can end an evaluation before pricing comes up.

Score all three tools against the criteria that apply to you and skip the rest.

## What is Svix good at?

Svix’s core product is Dispatch, outbound webhooks-as-a-service. If you run a SaaS platform that sends events to thousands of customer endpoints, it gives you subscriber management, retries, delivery dashboards and signing that would otherwise take a team months to build and years to harden. The server behind it is [open source under the MIT license](https://github.com/svix/svix-webhooks).

[Svix Ingest](https://docs.svix.com/ingest/receiving-with-ingest) is the receiving side. It verifies signatures for a list of named providers, Stripe among them, stores and retries webhooks that fail to deliver, lets you replay messages, and can transform payloads inside Svix.

Svix is not US-only. Its [pricing page](https://www.svix.com/pricing/) lists isolated US and EU regions on every plan, including Free, with custom regions on Enterprise. The free tier covers 50,000 messages a month with 30-day payload retention, and Professional starts at $490 a month with 90-day retention. Only attempted messages count towards usage, retries are free, and every 64 KiB of payload counts as one message. The EEA data processing agreement is included on Professional and Enterprise, not on Free.

If your core need is letting your users subscribe to your events and trust that they arrive, Svix is a strong fit. If you also receive webhooks and want one vendor for both directions, Ingest makes that possible.

## What is Hookdeck good at?

Hookdeck’s Event Gateway is built for receiving. It verifies signatures with [built-in support for a number of third-party providers](https://hookdeck.com/docs/authentication) plus generic methods, makes [up to 50 automatic retries](https://hookdeck.com/docs/retries) with unlimited manual and bulk retries, runs [JavaScript transformations](https://hookdeck.com/docs/transformations), and [filters events](https://hookdeck.com/docs/filters) on headers, body, query and path. Debugging is the area it has invested in most, and its dashboard reflects that.

Hosting is the constraint for EU teams. Hookdeck’s own comparison article states that [“Event Gateway is currently hosted in the US only”](https://hookdeck.com/webhooks/platforms/hookdeck-event-gateway-vs-svix-ingest-webhook-receiving-comparison). Pricing is per delivered event with retries included: according to [the pricing page](https://hookdeck.com/pricing), the Developer plan is free for up to 10,000 events with 3-day retention, Team starts at $39 a month with 7-day retention, and Growth starts at $499 a month with 30 days. A [data processing addendum](https://hookdeck.com/dpa) is published. For sending, [Outpost](https://hookdeck.com/outpost/pricing) is Apache 2.0 licensed, and its managed EU region starts on the Growth plan.

On the inbound side, Hookdeck is a credible, well-established option with production use behind it. If your data has to stay in the EU, Event Gateway’s US-only hosting is what sends you looking at Hookdeck alternatives.

## Where does Webhooker fit?

Webhooker is an [EU-hosted inbound webhook gateway](https://webhooker.eu/) with a deliberately narrow focus: receive, verify, and route third-party events, with ingest, storage, delivery workers and backups all in the EU. There is no region to pick. Each source gets its own ingest URL. Ingest returns 200 OK in milliseconds, and delivery to your services happens out of band, so a slow or failing downstream never blocks intake or makes the sender think the event failed. Keeping intake and delivery apart is the main job of any gateway, and it is easy to get wrong in a self-built receiver.

Reliability is built on at-least-once delivery from a durable queue, with retries, a circuit breaker, a dead-letter queue, and single or bulk replay for when something downstream was broken and you want to reprocess the backlog once it’s fixed. Each source verifies signatures with a Stripe, GitHub or Shopify preset, or a generic HMAC-SHA256/SHA1 scheme with hex or base64 digests for any other provider. Outbound requests are signed so your services can trust the source, transformations reshape payloads per destination, and a live tail shows events landing in real time while you wire up a new source.

Both paid plans include a DPA, so the cheapest plan with one costs €29 a month. According to [pricing](https://webhooker.eu/pricing), the plans are Free (€0, 10k events a month, 3 sources, 14-day retention), Pro (€29, 100k events, 50 sources, 30-day retention), and Team (€99, 1M events, 200 sources, 90-day retention). One event is one inbound webhook, so fanning it out to several destinations is not billed, and usage up to 120% of the quota is free.

Webhooker has two clear limitations. Webhooker does not do outbound webhooks-as-a-service, so if sending events to your own customers is the job, Svix Dispatch or Hookdeck Outpost will serve you better. And the free tier keeps events for 14 days, where Svix’s free tier keeps payloads for 30.

## How do Svix, Hookdeck and Webhooker compare? (checked 13 September 2026)

Every Svix and Hookdeck cell comes from the pages linked above. Treat the table as a snapshot and confirm current details on each vendor’s site before committing.

| Criterion | Svix | Hookdeck | Webhooker |
| --- | --- | --- | --- |
| Built around | Sending (Dispatch), receiving via Ingest | Receiving (Event Gateway), sending via Outpost | Receiving only |
| Hosting regions | US and EU on every plan, custom on Enterprise | Event Gateway: US only | EU only |
| Inbound verification | Named providers such as Stripe | Built-in providers plus generic methods | Stripe, GitHub, Shopify presets plus generic HMAC-SHA256/SHA1 |
| Retries and replay | Automatic retries, replay | Up to 50 automatic, unlimited manual and bulk | Backoff, circuit breaker, DLQ, single and bulk replay |
| Transformations | Yes | JavaScript, plus filters | Yes, per destination |
| Free tier | 50,000 messages a month, 30-day retention | Up to 10,000 events, 3-day retention | 10,000 events a month, 14-day retention |
| Entry paid plan | Professional from $490/mo, 90-day retention | Team from $39/mo, 7-day retention | Pro €29/mo, 30-day retention |
| Billing unit | Attempted message, retries free, 64 KiB = 1 message | Delivered event, retries included | Inbound event, fan-out not billed |
| DPA | EEA DPA on Professional and Enterprise | Published DPA | On every paid plan |

## Which one should you pick?

**Choose Svix if** your main job is sending webhooks to your own users, or you want one vendor for both directions with an EU region available on every plan. Budget for Professional if you need the EEA DPA.

**Choose Hookdeck if** you need an inbound gateway with a mature debugging dashboard, JavaScript transformations and filters, and US hosting is acceptable for your compliance posture. If it is not, we go through [what to compare in an EU-hosted Hookdeck alternative](https://webhooker.eu/blog/hookdeck-alternatives-eu), and [Webhooker vs Hookdeck](https://webhooker.eu/blog/webhooker-vs-hookdeck) compares the two receiving gateways one to one.

**Choose Webhooker if** you only receive webhooks from third parties, you want every leg of the pipeline inside the EU rather than a region to select, and you want a DPA and per-event pricing without fan-out charges from €29 a month. To test the billing model before paying, [create a free source](https://app.webhooker.eu/register), point a Stripe test-mode webhook at its ingest URL, add two destinations, and check that the history shows one event with two deliveries.

None of these is the best webhook gateway in the abstract. The best one for you is built for your direction of traffic and hosted where your compliance team is comfortable.

## Frequently asked questions

### Can one tool both receive and send webhooks?

Yes, with Svix, whose Dispatch product sends and whose Ingest product receives, both on the same plans. Hookdeck splits the jobs into two products, Event Gateway for receiving and Outpost for sending. Webhooker only receives: it can forward and re-sign requests to your own downstream services, but it has no subscriber management for sending webhooks to your customers.

### Which of Svix, Hookdeck and Webhooker is hosted in the EU?

For receiving webhooks, Svix and Webhooker can keep data in the EU; Hookdeck’s Event Gateway cannot. Svix offers an isolated EU region on every plan, including Free. Hookdeck states that its Event Gateway is hosted in the US only; its managed EU region applies to Outpost, the sending product, from the $499 Growth plan. Webhooker runs ingest, storage, delivery workers and backups only in the EU. Whichever you pick, ask where backups, logs and sub-processors sit as well as the primary region.

### Which of them can receive Stripe and GitHub webhooks?

Any of the three can receive them: Svix through Ingest, Hookdeck through Event Gateway, and Webhooker with built-in Stripe, GitHub and Shopify verification. The per-provider detail is in [verifying Stripe signatures](https://webhooker.eu/blog/verify-stripe-webhook-signatures) and [verifying GitHub signatures](https://webhooker.eu/blog/verify-github-webhook-signature), and either way you will need [the endpoint’s signing secret](https://webhooker.eu/blog/stripe-webhook-signing-secret) first. If EU-only hosting and a DPA on the cheapest paid plan matter, Webhooker fits. If you want the most mature debugging dashboard and US hosting is fine, Hookdeck is worth a close look. If you also send webhooks, Svix covers both directions.