Trusted by teams at
Hookdeck is a webhook gateway: it receives and routes incoming webhooks. If you need to send webhooks to your users -- with retries, signatures, and subscriber management -- Hookdeck doesn't do that. These alternatives do.
Trusted by teams at
Pick the wrong category and you'll end up building the missing half yourself.
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.
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.
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 | Webhook gateway / proxy | Full webhook platform | Webhook platform (open-core) | Webhook platform | Event bus (AWS ecosystem) |
| Sending Webhooks | No | 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 | No | Free (Docker / K8s) | Enterprise plan only | Yes (self-managed) | No (AWS only) |
| Open Source | No (closed-source) | Yes (SSPL-1.0, full source) | Partial (open-core, enterprise closed) | Yes (MPL-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 | US-based | 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) |
Hookdeck does one thing well: receiving and routing webhooks. But there are clear cases where it falls short.
Hookdeck doesn't send webhooks. Period. If your product needs to notify customers via webhooks with retries, HMAC signatures, and delivery logs, you need a webhook platform: Hook0, Svix, or Convoy.
Hookdeck is cloud-only. There is no self-hosting option. If compliance or data sovereignty rules require you to run on your own infrastructure, Hook0 and Convoy are both self-hostable at no cost.
Hookdeck is US-based. Hook0 Cloud is hosted in Europe with GDPR compliance built in. If you're an EU company handling sensitive data, the choice is straightforward.
Hookdeck is closed-source. You can't see how your webhook data is processed. Hook0's entire codebase is open under SSPL-1.0, so you can read and audit every line.
No. Hookdeck is closed-source and cloud-only. You cannot inspect the code, audit it, or self-host it. If open-source matters to you, alternatives like Hook0 (SSPL-1.0) or Convoy (MPL-2.0) are fully open-source.
No. Hookdeck does not offer a self-hosted option. It is cloud-only. If you need to run your webhook infrastructure on your own servers for compliance, data sovereignty, or cost reasons, Hook0 and Convoy both support self-hosting.
A webhook proxy (like Hookdeck) 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.
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.
Stop building webhook infrastructure. Start shipping features. Get started in minutes.