Alternatives to Convoy (2026)

The company behind Convoy essentially wound down. It's now a side project rather than a full-time effort. Here are the webhook sending platforms most teams migrate to, with honest pros, cons, and when each is a good fit.

By Svix Team · Last updated

IMPORTANT

The company behind Convoy essentially wound down. The project is still open source, but is now maintained as a small side project rather than a full-time effort, so it's not advised for production environments.

TL;DR

  • Svix Dispatch: recommended for production and the most direct migration target. Measured 99.99999% uptime, HIPAA + PCI-DSS, FIFO, transformations, throttling, and an MIT-licensed open-source server.
  • Hookdeck Outpost: newer cost-focused option with a narrower feature set.
  • Hook0: small EU bootstrapped option for low-volume teams.
  • Webhook Relay: better suited to dev tooling than customer-facing outbound webhooks.
  • Build it yourself: reasonable if you have custom needs, but consider starting from one of the open-source / self-hosted offerings above (Svix included) and customizing from there.

Convoy was, for several years, a reasonable open-source webhook delivery server. The company behind it essentially wound down, and the project is now a small side project rather than a full-time effort. Combined with measured uptime below 99.0% over the last 12 months and a source-available Elastic License v2.0 rather than a true open-source license, teams running Convoy in production should plan a migration.

Below is an honest look at Convoy's main competitors and alternatives: what each is good at, what each is missing, and which one is the right migration target depending on your situation.

Svix DispatchRecommended

The webhook sending platform used by fast growing startups and the Fortune 500, delivering billions of webhooks with measured 99.99999% historical uptime. Svix Dispatch covers everything Convoy ships and adds FIFO ordering, endpoint throttling, polling endpoints, Standard Webhooks compatibility, a wider destination matrix (Kafka, SQS, RabbitMQ, Pub/Sub, ServiceBus, EventBridge, S3, GCS, Azure Storage, and more), HIPAA and PCI-DSS compliance, SDKs in nine languages plus a CLI, and an MIT-licensed open-source server.

Best for: Production webhook delivery: anything customer-facing, anything in a regulated industry, anything where downtime or missed deliveries are a problem. Also the most direct migration target for teams currently running Convoy who can no longer rely on it.

Not a good fit for: Hobbyist projects with zero budget where you genuinely don't care about uptime, security, or feature gaps.

Read the full Svix Dispatch vs. Svix Dispatch comparison.

Hookdeck Outpost

A newer webhook sending product from Hookdeck. Covers retries, replay, OpenTelemetry streaming, and a small set of destinations, with aggressive pricing for low volume. Has measured 99.9% historical uptime and lacks HIPAA, PCI-DSS, payload transformations, FIFO, and endpoint throttling.

Best for: Cost-sensitive small teams that can tolerate downtime and missing features.

Not a good fit for: Regulated industries, customer-facing webhook delivery at scale, or anything that needs FIFO, throttling, transformations, or a broad destination matrix.

Read the full Svix Dispatch vs. Hookdeck Outpost comparison.

Hook0

A small bootstrapped European startup offering webhook-sending infrastructure with a hosted SaaS in the EU and a source-available SSPL self-hosted server. Covers subscriptions, retries, signatures, and replay, but only delivers HTTPS webhooks.

Best for: Small EU teams with modest webhook volume that need EU-only data residency.

Not a good fit for: Multi-region data residency, queue or object-store destinations, regulated industries, or anything beyond a few thousand events per day.

Read the full Svix Dispatch vs. Hook0 comparison.

Webhook Relay

A long-running webhook tunneling and forwarding product, primarily used for routing inbound webhooks to local environments and small-scale fan-out. Closer to a developer-tooling product than to a customer-facing webhook delivery platform.

Best for: Local development, internal tooling, and routing webhooks between systems where production reliability and compliance are not required.

Not a good fit for: Customer-facing outbound webhook delivery at scale, regulated workloads, or teams that need a wide SDK matrix or a consumer-facing application portal.

Building it yourself

Rolling your own webhook delivery layer on top of a queue and a worker pool. If you have genuinely custom requirements, this can be a reasonable path. Worth noting that several of the providers above (Svix included) offer self-hosted and open-source options (Svix's MIT-licensed open-source server), so before going fully in-house it's often a good idea to start from one of those and customize as needed.

Best for: Teams with very specific, non-standard requirements and the engineering bandwidth to maintain webhook infrastructure long-term.

Not a good fit for: Most teams. Self-hosting an existing open-source server (Svix's MIT-licensed open-source server, for example) usually gets you most of the way there without taking on the long tail of retries, noisy neighbor isolation, observability, replay, transformations, FIFO, throttling, and a customer-facing portal.

See our build vs. buy analysis for the tradeoffs of running webhook delivery in-house.

Conclusion

If you're currently running Convoy and need to migrate, Svix Dispatch is the most direct replacement. It covers every Convoy feature, adds many more, has been battle-tested at much larger scale, and offers an MIT-licensed open-source server you can self-host if you prefer that deployment model. The open-source Svix server is fully compatible with the hosted SaaS, so you can start self-hosted and migrate to SaaS later, or vice versa.

Start sending webhooks today,
no credit card required.

Get started for free