A Managed Webhook Service You Can Take With You
Hook0 delivers your events, signs them, retries them when the receiver is down, and logs every attempt. It runs on an EU data plane from the free tier up. And the day a managed webhook service stops being the right answer, the same codebase self-hosts, open-source under SSPL-1.0.
100 events/day free. No credit card. EU data plane on every plan.
What a webhook service owes you
The parts teams discover after they have already shipped their own delivery loop. Here is where Hook0 stands on each one.
Signed payloads, every attempt
Every delivery carries an HMAC-SHA256 signature, so the receiver can tell your events from anything else that found the endpoint. The verification steps are documented rather than left as an exercise.
Retries that survive a bad afternoon
Two-phase, configurable retries. A subscriber that is down for an hour does not cost you the events that happened during that hour, and you do not write the backoff schedule yourself.
Proof of what actually happened
Per-attempt delivery logs. When a customer says they never received the event, the answer is a lookup rather than an argument.
Replay, once the bug is fixed
Deliveries can be replayed from the logs. The receiver's outage or its parsing bug stops being a data-loss incident and becomes a replay.
Something your customers can use alone
A drop-in subscriber portal where your users register their own endpoints and read their own delivery history, instead of opening a support ticket for every 500.
A data plane you can point to
Payloads, database and backups run on Clever Cloud SAS infrastructure in France, inside the EEA, on every plan including the free tier. The CDN in front is Cloudflare, Inc. (USA), disclosed in the public sub-processor list with its transfer mechanism. See EU webhook infrastructure.
An exit that is not a rewrite
The whole product is open-source under SSPL-1.0, with no open-core holdback, so the cloud runs the code you can run. Leaving means hosting the same software rather than rebuilding against a new API.
What a managed webhook service costs
Where each provider's public pricing starts once you want a supported, managed service rather than a trial.
| Provider | How you run it | Where the pricing starts |
|---|---|---|
| Hook0 | Managed cloud, self-hosted or managed on-premise, all on one codebase. | €0 (free tier, 100 events/day); paid plans from €59/month |
| Hookdeck | Managed platform, US, EU and Asia regions. | Free tier available; the SLA-backed Growth plan is $499/month |
| Svix | Managed cloud, or self-hosting under MIT. | Managed Pro starts at $490/month |
| Convoy | Self-hosted Community, or the managed Premium plan. | Community is free (Elastic License v2); managed Premium is $999/month |
Sources: each provider's public pricing pages, last checked on 2026-07-16. Providers move their prices, so check theirs too. Spotted something out of date? Tell us and we will fix it.
Managed today, yours tomorrow
A webhook service is a dependency in your delivery path. It is worth knowing, before you sign, what happens the day you want it out.
Self-host the same thing
Docker Compose or Kubernetes, PostgreSQL underneath, open-source under SSPL-1.0. Your payloads stay inside your own network. See self-hosted webhooks.
Or keep it managed, in your environment
We deploy a dedicated instance in your infrastructure and keep it maintained: €1,000 setup + €500/month (excl. VAT), or €0 setup + €6,000/year (excl. VAT).
The API does not change
Cloud, self-hosted and on-premise run the same webhook API. Moving between them changes your deployment while your integration code stays as it is.
Webhook service questions
What is a webhook service?
A webhook service takes an event from your backend and delivers it to the HTTP endpoints your customers registered. It owns the four parts that are tedious to own yourself, signing each payload so the receiver can trust it, retrying when the receiver is down, keeping a log of every attempt, and giving your customers somewhere to manage their own endpoints. You make one API call; the service handles the rest of the delivery.
What is the difference between a webhook service and a webhook platform?
In practice the two words describe the same product, and vendors use them interchangeably. "Service" tends to describe the managed side (someone else runs the delivery for you), while "platform" tends to describe the surface you build on: API, portal, event types, logs. Hook0 is both, which is why the same features show up on this page and on the webhook platform page.
How much does a webhook service cost?
Hook0 is free up to 100 events/day, with paid plans from €59/month. Among the other managed providers, as last checked in July 2026, Hookdeck's SLA-backed Growth plan is $499/month, Svix's managed Pro starts at $490/month, and Convoy's managed Premium is $999/month. Self-hosting shifts the cost from a subscription to your own infrastructure and maintenance time.
Where does Hook0 host webhook data?
The webhook data plane, meaning payloads, database and backups, runs on Clever Cloud SAS infrastructure in France, inside the European Economic Area, on every plan including the free tier. The CDN and DDoS layer in front of the website and API is Cloudflare, Inc. (USA), disclosed in our public sub-processor list and framed by the 2021 Standard Contractual Clauses, a documented Transfer Impact Assessment and, where applicable, the EU-US Data Privacy Framework.
Can I move off the managed service later?
Yes, and it is the reason the codebase is open-source under SSPL-1.0 with no open-core holdback. You can self-host the same software with Docker Compose or Kubernetes, or have us run a dedicated instance inside your own environment. The API stays the same in all three cases, so your integration code does not change.
Do I still need a webhook service if I already send HTTP requests?
Sending the first request is the easy part. The sprints go into everything after it, from a retry schedule that does not hammer a struggling receiver to signatures your customers can verify, per-attempt logs for the support conversation, replay after an outage, and a portal so subscribers manage their own endpoints. If you have already built all of that and enjoy maintaining it, you do not need a webhook service.
You have better things to build
Stop building webhook infrastructure. Start shipping features. Get started in minutes.