Hook0 vs Hookdeck: Sending or Receiving Webhooks, EU or US

Hook0 and Hookdeck mostly do different jobs. Hook0 sends webhooks from your product to your customers’ endpoints, is hosted in France, and publishes its server under the SSPL-1.0 licence. Hookdeck’s main product, Event Gateway, receives webhooks from providers such as Stripe and GitHub and routes them to your services, and Hookdeck says it is hosted in the US only. Hookdeck also has a sending product, Outpost, which is Apache 2.0 licensed and offers a managed EU region from its $499 Growth plan. So the real question behind “Hook0 vs Hookdeck” is which direction you need. If you send webhooks, compare Hook0 with Outpost. If you receive them, Hook0 is not a candidate at all.

We build Webhooker, an EU-hosted gateway for receiving webhooks, so read this as a vendor’s page. We have no sending product, which means no stake in the Hook0 against Outpost part. Every Hook0 and Hookdeck fact below links to that vendor’s own pricing page, documentation, legal pages or licence file, checked 21 September 2026. Prices and regions change, so confirm them before you sign.

Do Hook0 and Hookdeck do the same job?

Only partly.

Hook0’s homepage describes it as “Open-Source Webhooks-as-a-service that makes it easy for developers to send webhooks”. Your application makes one API call per event, and Hook0 delivers that event to every customer endpoint subscribed to it, signing it, retrying it and logging each attempt. Your customers get a subscriber portal that you can brand with your own subdomain and logo. Nothing on the homepage covers receiving webhooks from third parties.

Hookdeck sells two products. Event Gateway sits in front of your own services. Stripe, GitHub or Shopify post to a Hookdeck URL, and Hookdeck verifies, queues and delivers each request to your destinations. Outpost goes the other way. Hookdeck’s docs call it “outbound webhooks infrastructure”, and besides plain webhooks it can deliver your platform’s events to AWS SQS, Kinesis and S3, GCP Pub/Sub, Azure Service Bus, RabbitMQ and Kafka.

To sort this out, ask who owns the endpoint you are managing. If it belongs to your customer, you are sending, and the comparison is Hook0 against Outpost. If it belongs to you and the sender is a provider you do not control, you are receiving, and the comparison is Event Gateway against other receiving gateways. Our guide to what a webhook gateway does covers the receiving side.

Where is your webhook data stored?

For an EU company this is often the deciding point, and the two vendors are far apart on it.

Hook0 states that its “webhook data plane runs on Clever Cloud in France, inside the EU, on the free tier and every paid plan”, with optional dedicated workers on Scaleway, also in France. There is one exception, and Hook0 says so itself: the CDN and DDoS layer in front is Cloudflare, a US company. Its sub-processor page lists each vendor with a country and a transfer mechanism. Hosting, workers, one email provider and support chat are in France. Cloudflare, Stripe, Postmark, Sentry and Google Workspace are in the US under standard contractual clauses.

Hookdeck’s own comparison article says “Event Gateway is currently hosted in the US only”. Outpost is another story. Its pricing page lists data residency as US on the Starter plan and US, EU and Asia on Growth and Enterprise. Growth starts at $499 a month plus usage. You can also run Outpost yourself in an EU data centre, because the code is open source.

If payloads carry names, emails or order details, a US-hosted gateway means a transfer you have to document. Our article on whether webhooks count as personal data explains which fields bring GDPR into scope, and EU-hosted webhook infrastructure lists the residency questions to ask any vendor.

Which one is open source, and can you self-host it?

Hook0 and Outpost both publish their source, under different licences.

Hook0’s server is on GitHub under SSPL-1.0, and its client SDKs are MIT. Hook0’s homepage calls SSPL “a source-available copyleft license”. You can read, modify and self-host the code freely, but if you resell Hook0 as a managed service you have to open-source your own infrastructure stack. A team that runs Hook0 for its own product never hits that clause. The Open Source Initiative does not count SSPL as an open source licence, so check whether your company’s policy accepts it. Self-hosting uses Docker Compose or Kubernetes, and Hook0 says the self-hosted version has the same features as the cloud one. The pricing page also sells a managed on-premise instance at €1,000 setup plus €500 a month, or €6,000 a year with no setup fee.

Outpost is on GitHub under Apache 2.0, a permissive licence with no restriction on hosting it for others. Hookdeck says the same codebase runs the managed and self-hosted versions.

Hookdeck’s pricing page lists no self-hosted option for Event Gateway. If you need a receiving gateway on your own servers, neither vendor covers that, and build vs buy webhook infrastructure goes through what owning one costs.

How do retries compare?

Both retry long enough to cover an endpoint that stays down for days.

Hook0’s retry documentation gives the exact schedule. Retries start at 3 seconds and 10 seconds, then 3 minutes, 30 minutes, 1 hour, 3 hours and 5 hours, and hold at 10 hours from the eighth retry on. With the defaults a failing delivery is retried up to 24 times over roughly 8 days. When attempts run out, the last one stays marked as failed and you can replay the event through the API.

Hookdeck Event Gateway makes up to 50 automatic retries on a linear or exponential schedule that you configure, and manual and bulk retries are unlimited. Outpost’s docs describe automatic retries with exponential backoff or a custom schedule, plus manual retries through the portal or API.

Hookdeck gives you more control over the schedule, while Hook0 documents its schedule down to the second, which helps when you write your own API docs. Both deliver at least once, so your consumers, or your customers’ consumers, need idempotency keys either way. Our article on retries, backoff and circuit breakers explains the reasoning behind these schedules.

What does each one cost?

The three products bill on three different units, so compare the unit before the price.

Hook0 bills per event you send to it, with a daily quota. Its pricing page says “one event can trigger multiple webhook subscriptions which can in turn be retried multiple times. Subscriptions and retries are free.” The free Developer plan allows 100 events a day with 7-day retention and blocks extra events with an HTTP 429. Startup is €59 a month excluding VAT for up to 30,000 events a day with 14-day retention, then €0.003 per extra event. Pro is €190 a month for up to 100,000 events a day with 30-day retention, then €0.0001 per extra event. Paid plans are never blocked at the quota.

Hookdeck Event Gateway bills per delivery. Its pricing page defines an event as a message “that’s delivered to a destination”, and the price of an event includes all its retries. One inbound request routed to three destinations counts as three events. The Developer plan is free for up to 10,000 events with 3-day retention and one user. Team starts at $39 a month on pay-as-you-go usage with 7-day retention and unlimited users. Growth starts at $499 a month with 30-day retention, uptime and latency SLAs, and SSO. A static IP is a $100 add-on.

Hookdeck Outpost is $10 per million events on the managed Starter plan, with the first 50,000 events free, retries not charged and 7-day retention. Growth starts at $499 a month plus $10 per million events and adds a 99.99% uptime SLA, 30-day retention, SSO and the EU and Asia regions. Self-hosting is free.

Here is how that works out for a sender. A product that emits about 900,000 events a month fits Hook0’s Startup plan at €59, hosted in France. The same volume on Outpost Starter costs under $10, hosted in the US. To get Hookdeck’s managed EU region you pay $499 a month plus usage. So managed sending in the EU is much cheaper on Hook0, and Outpost wins when US hosting is acceptable or you host it yourself. We compare billing units in webhook pricing models.

Which one gives you a DPA and a sub-processor list?

Both publish a DPA and a sub-processor list, but the lists differ in how much they tell you. Our buyer’s checklist for a GDPR-compliant webhook relay covers what to look for in each document.

Hook0 publishes a data processing agreement with FGRibreau SARL, a French company, as the processor. Its sub-processor page, covered above, gives a country and a transfer mechanism for every vendor. The security page points to Clever Cloud’s SOC 2 and ISO 27001 certifications, which belong to the hosting provider and not to Hook0 itself.

Hookdeck publishes a DPA with Hookdeck Technologies Inc. as the processor. It relies on standard contractual clauses for transfers to the US. The sub-processor list names Google Cloud, Cloudflare and Vercel for hosting, three database vendors, and Railway for Outpost only. It gives a purpose for each but no locations. Hookdeck’s pricing pages list SOC 2 compliance on every Event Gateway and managed Outpost plan, which Hook0 does not claim for itself.

How do Hook0 and Hookdeck compare? (checked 21 September 2026)

Every cell comes from the vendor pages linked above. Treat the table as a snapshot.

Table: Hook0, Hookdeck Event Gateway and Hookdeck Outpost compared on direction, hosting, licence, retries, billing, plans and compliance documents.

When is Hook0 the better choice?

Pick Hook0 when you send webhooks to customers and want the managed service in the EU without an enterprise budget. France-hosted delivery starts on the free tier, and the first paid plan is €59. It also suits teams that want to self-host the full feature set, and teams whose DPO wants a country next to every sub-processor. Check first that SSPL passes your licence policy.

When is Hookdeck the better choice?

Pick Hookdeck Event Gateway when your job is receiving webhooks and US hosting is acceptable. Its receiving feature set is the broader one here: up to 50 automatic retries, filters, JavaScript transformations and SSO on Growth. Pick Outpost when you send webhooks and want a permissive Apache 2.0 licence, delivery to queues and streams as well as HTTP endpoints, or very low usage pricing. Hookdeck is also the only one of the two vendors that covers both directions.

What if you need to receive webhooks in the EU?

Then neither product fits as a managed service. Hook0 does not receive webhooks, and Event Gateway receives them only in the US. Outpost’s EU region does not help, because Outpost sends.

This is the case Webhooker is built for. It is our product, so weigh this section accordingly. Webhooker only receives. Each source gets its own ingest URL, such as https://app.webhooker.eu/in/<token>. Signatures are checked before a request is accepted, with Stripe, GitHub and Shopify presets, generic HMAC, Basic Auth or an API key. Ingest, storage, delivery workers and backups all run in the EU, on Hetzner servers in Germany, with no region to select. Failed deliveries retry six times over about five hours, a per-destination circuit breaker isolates an endpoint that is down, and exhausted events land in a dead-letter queue with single and bulk replay.

One inbound event is one billable event however many destinations receive it. Pricing is Free (10,000 events a month, 3 sources, 14-day retention), Pro at €29 a month (100,000 events, 30-day retention, DPA) and Team at €99 (1,000,000 events, 90-day retention, ordered delivery and a static outbound IP). Usage up to 120% of the quota is free, and there is no overage billing.

Next to Hookdeck it has clear limits: six automatic retries against up to 50, fewer named verification presets, no SSO and no sending product. Svix Ingest and Convoy also receive webhooks and offer EU regions, and the Hookdeck alternatives guide compares all of them. For a direct comparison, see Webhooker vs Hookdeck. To try it on your own traffic, create a free account and add the ingest URL as a second endpoint at one provider.

Frequently asked questions