How Railhook compares

Railhook compared with Svix, Hookdeck, Convoy and Hook0, on points each vendor states in its own public documentation, with Railhook’s gaps listed too.

As of 2026-09

Competitor details come from the linked public pages as of September 2026. Products change: check their documentation before deciding, and send a pull request if something is out of date.

At a glance

	Railhook	Svix	Hookdeck	Convoy
Open-source licence	MIT	MIT (the Svix server)	Apache-2.0 (Outpost)	Elastic License 2.0
Sends webhooks to your customers	Yes	Yes	Yes (Outpost)	Yes
Receives webhooks from providers	Yes	Yes (Svix Ingest)	Yes (Event Gateway)	Yes
Delivers to queues and cloud services, not only HTTP	No	—	Yes (Outpost)	—
Customer-facing portal	Yes, embeddable and self-hosted	App Portal, in the hosted version only	User portal (Outpost)	Portal Links
OpenTelemetry	No	Yes (server)	Yes (Outpost)	—
Every feature self-hosted without a licence key	Yes	—	—	No

A dash means the vendor’s pages did not settle the point either way, not that the feature is missing.

Compare in depth

• Railhook vs Svix
• Railhook vs Hookdeck
• Railhook vs Convoy
• Railhook vs Hook0
• Open-source webhook tools compared

Railhook

• Both directions. Outgoing events to customer endpoints and incoming provider webhooks share one attempt lifecycle, one dashboard and one set of failed messages.
• Everything self-hosted. Every feature is in the MIT repository, with no licence key. BILLING_ENABLED defaults to false.
• Railhook Cloud runs at railhook.io on a free plan. Paid plans with support and higher limits will come later.
• Standard Webhooks signatures alongside Railhook’s own X-Signature header, with a grace window on secret rotation.
• Per-endpoint ordering, opt-in, with a timeout so one stuck delivery cannot block an endpoint forever.
• Replay creates new deliveries from stored events (Time Machine in the dashboard) instead of re-sending the original.
• A built-in request bin and a localhost tunnel in the CLI.
• A workflow builder for multi-step processing beyond single transformations.
• An embeddable customer portal, self-hosted: your users register endpoints, choose event types, see their deliveries and retry failed ones. Sessions are short-lived and can be pinned to the embedding origin. See Customer portal.

What Railhook does not have

• A young customer portal. Theming is a brand colour, a logo, light or dark, and the language. No custom CSS, no custom portal domain, no view of the event catalog’s schemas.
• HTTP delivery only. No SQS, S3, EventBridge, Pub/Sub or RabbitMQ destinations.
• No SSO (SAML or OIDC) and no SCIM.
• No OpenTelemetry. Prometheus metrics are thorough; there are no traces.
• Three fixed roles and two API key scopes. No custom roles, no per-resource permissions.
• Filtering is project-level. A subscription cannot carry its own filter, and incoming webhooks cannot be filtered.
• No automatic disabling of an endpoint that keeps failing.
• No batching, no built-in static egress IPs (see Static egress IP).
• SDKs for Node.js, Python and PHP only. No Go SDK and no Terraform provider.

Svix

• The Svix server is open source under the MIT licence and can export traces to an OpenTelemetry collector. (svix/svix-webhooks)
• Its App Portal lets your customers add endpoints, debug deliveries, and inspect and replay past webhooks. (App Portal) Svix states the portal is included only in the hosted version, not the open-source one. (Consumer App Portal (OSS))
• Svix Ingest receives webhooks from providers, verifies them and forwards them to destinations. (Receiving with Ingest)

Choose Svix if a polished self-service customer portal is the priority and a hosted service suits you.

Hookdeck

• Outpost is Hookdeck’s open-source, Apache-2.0 product for sending events. It delivers to webhooks, Hookdeck Event Gateway, Amazon EventBridge, AWS SQS, AWS S3, GCP Pub/Sub and RabbitMQ, and includes a user portal and OpenTelemetry traces, metrics and logs. (hookdeck/outpost)
• Event Gateway receives webhooks at a source URL and routes them through connections to destinations, with filters, transformations, deduplication and retries. (Hookdeck docs)

Choose Hookdeck if your customers’ receivers are queues or cloud event buses rather than HTTP services. Railhook cannot deliver there.

Convoy

• Convoy sends webhooks to your users and receives webhooks from providers. It is licensed under the Elastic License 2.0. (frain-dev/convoy)
• Some features of the self-hosted edition are enabled by a licence key, and the free Community edition is limited to one user, one organisation and two projects. (frain-dev/convoy)
• Portal Links generate a customer-facing dashboard of an endpoint’s deliveries, as a one-time link or one you embed. (Portal Links)

Choose Convoy if you want both directions and an embeddable delivery view, and its licence terms fit.

Hook0

• Hook0 is a service for sending webhooks to your customers. It is licensed under the Server Side Public License, and its hosted service runs in the EU, in France by default. (Hook0)

Choose Hook0 if a hosted sending service must keep its data in the EU and its licence terms fit.