Hookdeck Alternatives Hookdeck Is Two Products. You Might Want One Platform
Hookdeck's Event Gateway receives and routes incoming webhooks, and sending runs through a second product, Outpost. If you want a single platform to send webhooks to your users, with retries, signatures, and subscriber management, running the same code in the cloud and self-hosted, these alternatives do that.
Gateway vs Platform: What's the Difference?
Pick the wrong category and you'll end up building the missing half yourself.
Webhook Gateway (Hookdeck Event Gateway)
A gateway sits between a third-party webhook sender and your application. It receives incoming webhooks, buffers them, retries failed deliveries, and routes events to the right endpoint. It's basically a reverse proxy for webhooks. You are the consumer.
Webhook Platform (Hook0, Svix, Convoy)
A platform lets you send webhooks to your users. You publish events, the platform delivers them with retries, HMAC signatures, and a subscriber management portal. You are the producer. This is what you need to add webhooks to your product.
Hookdeck vs the Alternatives
Five options, one table. What matters most is whether you need to send webhooks, receive them, or both.
| Criteria | Hookdeck | Hook0 | Svix | Convoy | AWS EventBridge |
|---|---|---|---|---|---|
| Type | Event Gateway (inbound) + Outpost (outbound) | Full webhook platform | Webhook platform (open-core) | Webhook platform | Event bus (AWS ecosystem) |
| Sending Webhooks | Yes (Outpost, separate product) | Yes (core feature) | Yes | Yes | Yes (via API Destinations) |
| Receiving Webhooks | Yes (core feature) | No (by design) | No | Yes (incoming + outgoing) | Yes (event ingestion) |
| Self-Hosting | Outpost only (Apache-2.0) | Free (Docker / K8s) | Enterprise plan only | Yes (self-managed) | No (AWS only) |
| Open Source | Partial (Outpost Apache-2.0, Gateway closed) | Yes (SSPL-1.0, full source) | Partial (open-core, enterprise closed) | Source-available (Elastic License 2.0) | No (AWS proprietary) |
| Free Tier | Yes (100k events/mo) | Yes, no credit card | Yes | Community edition only | Pay-per-use (AWS billing) |
| Data Hosting | Canada-based, EU region available | Europe (GDPR) or self-host | US-based | Self-host only | Multi-region (AWS) |
| Funding | $3.5M VC-funded | 100% Bootstrapped | $17M VC-funded | VC-funded | Amazon (public company) |
When Hookdeck Isn't Enough
Hookdeck does one thing well: receiving and routing webhooks. But there are clear cases where it falls short.
You Need to Send Webhooks
Hookdeck's Event Gateway doesn't send webhooks. That job belongs to Outpost, a separate product with its own plans. If you want one platform that publishes events and delivers them with retries, HMAC signatures, and delivery logs, look at Hook0, Svix, or Convoy.
You Want to Self-Host
Hookdeck opens only its Outpost component, published under Apache-2.0 and self-hostable. The Event Gateway stays closed-source and cloud-only. Hook0 and Convoy both self-host the whole product at no licence cost, and with Hook0 the self-hosted code is the code that runs the managed cloud.
You Need European Data Hosting
Hookdeck is Canada-based, with an EU region available on managed Outpost. Hook0 Cloud is hosted in Europe with GDPR compliance built in. If you're an EU company handling sensitive data, the choice is straightforward.
You Want to Audit the Source Code
Outpost is Apache-2.0, so Hookdeck's delivery code is readable, but the Event Gateway that ingests your webhooks stays closed. Hook0's entire codebase is open-source under SSPL-1.0, and the managed cloud runs that same code, so you can read and audit every line.
Common Questions
Is Hookdeck open-source?
Partly. Outpost, Hookdeck's delivery component, is Apache-2.0 and self-hostable, and the repository is active. The Event Gateway that ingests webhooks stays closed-source and cloud-only. Hook0 is fully open-source under SSPL-1.0, with the whole platform self-hostable. Convoy runs on the Elastic License 2.0, which the OSI does not approve and which forbids offering Convoy as a managed service.
Can I self-host Hookdeck?
Partly. Outpost is Apache-2.0 and runs on your own infrastructure; the Event Gateway has no self-hosted option. Note that on Hookdeck Outpost managed, SSO, RBAC and SCIM are not in the $10/M Starter tier: they start on the Growth tier, at $499/month minimum on top of the per-event cost. If you need your whole webhook infrastructure on your own servers, Hook0 and Convoy both self-host end to end, and Hook0 runs the same code in its managed cloud with no feature gated behind an enterprise tier.
What's the difference between a webhook proxy and a webhook platform?
A webhook proxy (like Hookdeck's Event Gateway) sits between a webhook sender and your application. It receives, routes, and retries incoming webhooks. A webhook platform (like Hook0 or Svix) lets you send webhooks to your users. It handles delivery, retries, signatures, and subscriber management for you. If you want to add webhooks to your product, you need a platform, not a proxy.
What's the best Hookdeck alternative for sending webhooks?
Hook0, if you need to send webhooks. You publish events, Hook0 delivers them to your subscribers with retries, HMAC signatures, and a management dashboard. The code is open-source (SSPL-1.0), you can self-host it, the company is bootstrapped, and the cloud runs in Europe.
Which Hookdeck alternative is EU-hosted and open-source?
Hook0. Hookdeck opens only Outpost, its delivery component, under Apache-2.0; the Event Gateway stays closed-source and cloud-only. Hook0 runs its data plane on Clever Cloud in France (inside the EU), is open-source under SSPL-1.0, and self-hosts on Docker or Kubernetes, so you can read the code or keep webhook data inside your own network. The CDN in front of Hook0 Cloud is Cloudflare (US), disclosed in the public sub-processor list.
You have better things to build
Stop building webhook infrastructure. Start shipping features. Get started in minutes.