Open-source webhook tools compared (2026)
Use this page to shortlist a webhook server you can run yourself. It covers the five projects whose source you can download and self-host, and separates the ones under an open-source licence from the source-available ones, because that decides what you may do with them.
Licence first
Section titled “Licence first”| Project | Licence | Kind |
|---|---|---|
| Railhook | MIT | Open source, approved by the OSI |
| Svix | MIT | Open source, approved by the OSI |
| Hookdeck Outpost | Apache-2.0 | Open source, approved by the OSI |
| Convoy | Elastic License 2.0 | Source-available |
| Hook0 | SSPL | Source-available |
An OSI-approved licence lets you run, change and redistribute the software, including inside a product you sell. The Elastic License 2.0 and the SSPL let you read and run the source but restrict offering it as a service. If you plan to embed a webhook server in something you host for others, read those two licences with a lawyer first.
What each one does
Section titled “What each one does”| Railhook | Svix | Outpost | Convoy | Hook0 | |
|---|---|---|---|---|---|
| Sends webhooks to your customers | Yes | Yes | Yes | Yes | Yes |
| Receives webhooks from providers | Yes | As a separate product (Ingest) | No | Yes | — |
| Held back from the self-hosted build | Nothing | App Portal, transformations | — | Portal links, JavaScript transformations, OpenTelemetry, RBAC | — |
| Delivers to queues and event buses | No | — | Yes | — | — |
| Customer-facing portal | Yes | Hosted only | Yes | Paid editions | — |
| OpenTelemetry | No | Yes | Yes | Paid editions | — |
A dash means the pages we checked did not settle the point. It is not a claim that the feature is missing.
In one line each
Section titled “In one line each”- Railhook — both directions in one MIT product, every feature self-hosted with no licence key, a localhost tunnel in the CLI, an embeddable customer portal. HTTP delivery only, no OpenTelemetry. Railhook vs the others.
- Svix — a mature sending platform, with 9 SDKs, a Terraform provider and SOC 2 and HIPAA on the hosted service; the open-source server leaves out the App Portal and transformations. Railhook vs Svix.
- Hookdeck Outpost — sending only, and the one to pick when your customers’ receivers are SQS, Kafka, EventBridge, Pub/Sub or RabbitMQ. Hookdeck’s receiving gateway is a separate, closed-source SaaS. Railhook vs Hookdeck.
- Convoy — both directions, under a source-available licence, with portal links, JavaScript transformations, OpenTelemetry and RBAC in paid editions. Railhook vs Convoy.
- Hook0 — sending, with an EU-hosted cloud, under the SSPL. Railhook vs Hook0.
How to choose
Section titled “How to choose”- You need both directions under an open-source licence: Railhook. Svix offers receiving as a separate product (Ingest), and Convoy covers both directions under a source-available licence.
- Your customers’ receivers are queues: Outpost.
- Your customers must manage their own endpoints, and hosting with a vendor is fine: Svix.
- Your hosted data must stay in the EU and a hosted service is required: Hook0, or self-host any of the others in your own region.
Next steps
Section titled “Next steps”How Railhook comparesRailhook's strengths and every gap, in detail.
Install with DockerRun Railhook on your own server.
Migrate to RailhookMove from another platform with both live.