Svix Dispatch vs. Convoy

When it comes to uptime and reliability, there's a stark difference between the offerings.

Svix Dispatch has been running webhook traffic at scale for years, with an actual measured uptime of 99.99999% and reference customers including Brex, Clerk, Twilio, PagerDuty, Lob, Resend, Replicate, Lithic, Benchling, Drata, incident.io, and many others. Svix offers 99.999% of uptime SLAs, and delivers around 99.99999%.

Convoy advertises a 99.99% SLA on the Pro tier and up to 99.999% on Enterprise. They have traditionally had issues with uptime, and hit less than 99.0% of uptime in the last 12 months. There are also no published case studies and limited production exposure.

NOTE: Convoy no longer has any active employees or anyone working on it full time, so it's unclear whether incidents are still reported on the status page.

This is another area where Svix is very much ahead.

Svix Dispatch has been serving companies of all sizes and in a variety of different verticals and compliance environments, which means that the product has been battle-tested in a variety of environments and has already built the features your customers will ask before such as mTLS, endpoint throttling, and more.

Convoy covers a meaningful portion of the basics: retries, replay, circuit breaking, and more. Though it hasn't been battle-tested in environments where uptime, security, and scale are a requirement, and with a small customer base and no active full-time maintainers, the product is unlikely to close those gaps in the near term.

An example to illustrate the difference in scale: the Svix NPM package is downloaded 4.5 million times a week, while the Convoy one only 1.9 thousand times a week.

Svix Dispatch has been serving customers in finance, health, insurance, and other regulated industries, and has been evaluated and approved by some of the best security teams.. It also offers a wide compliance footprint with SOC 2 Type II, HIPAA, PIPEDA, PCI-DSS, GDPR, and CCPA to help you serve your customers and their compliance requirements.

Convoy has SOC 2 and GDPR coverage, but has a much narrower compliance footprint, lacks production exposure with regulated customers, and hasn't been widely scrutinized by security teams.

Svix Dispatch offers everything your customers needs in order to easily consume webhooks in the manner they want it. Consumer application portal for webhook management and observability, endpoint throttling to avoid accidental denial-of-service, polling endpoints, per-message and bulk retries, JavaScript transformations for modifying payloads and having fine-grained delivery, and more.

Convoy covers a narrower slice: it offers JavaScript transformations, portal links for embedded customer dashboards, and circuit breaking, but lacks FIFO ordering, per-endpoint throttling, polling endpoints, and isn't compatible with the mature Standard Webhooks ecosystem. This means your customers will have a harder time consuming your webhooks if you use Convoy, which leads to lower adoption and less reliable integrations.

Svix ships official SDKs for TypeScript, Python (sync and async), Go, Java, Kotlin (coroutines), Ruby, Rust, PHP, and C#, plus a full CLI. Svix also authored the Standard Webhooks specification together with Twilio, Kong, Mux, Supabase, ngrok, and Lob. The spec is now adopted by OpenAI, Render, Clerk, Resend, and many others. Meaning Svix and its customers is fully compatible with the ecosystem and tools built for those services.

Convoy covers JavaScript, Ruby, and Go, and is not compatible with the Standard Webhooks ecosystem.

Svix Dispatch offers a hosted SaaS, enterprise on-prem, and an open source product. The hosted SaaS and enterprise on-prem offer full feature parity. The open source server is fully compatible with the hosted SaaS, with some advanced features and the built-in UI only included in SaaS. SDKs, including the build-your-own-UI SDKs are available for all deployments.

Convoy is available as both a hosted SaaS and a self-hosted offering under the Elastic License v2.0 (source-available, not open source). Some features such as SSO/SAML are gated as paid features even in the self-hosted version.

Both vendors support fan-out beyond plain webhooks, but Svix's destination matrix is significantly wider. Convoy supports Kafka, SQS, RabbitMQ, and Google Pub/Sub. Svix covers all of those plus Azure ServiceBus, AWS EventBridge, AWS S3, Google Cloud Storage, Azure Storage Blobs, FIFO endpoints, polling endpoints, and custom connectors, along with a library of out-of-the-box connectors for common downstream services. If you anticipate routing webhooks into a mix of queues, object stores, and SaaS destinations, the difference in surface area will matter.

Svix Dispatch and Convoy package things differently across the tiers. The Svix free tier offers higher rate-limits and higher retention compared to the paid Convoy offering. However if you need more advanced functionality, the Svix Professional tier goes at $490, which is higher than Convoy's $99 / month (+ $100 for static IPs).

Choose Svix Dispatch if you're building a product where webhook delivery is part of the customer experience and product maturity is important, you expect to send many events, or downtime or missed deliveries are not tolerable. Svix is also the better choice if you operate in an environment where security and compliance are important, or you require HIPAA or PCI-DSS. It's also the safer default at any scale where vendor maturity and a track record of running real production workloads matter.

Given Convoy no longer has any active full-time maintainers, we don't recommend it for production use. If you're a solo developer or hobbyist comfortable self-hosting under the Elastic License v2.0 and the missing features (FIFO, throttling, polling endpoints, broader destinations, Standard Webhooks compatibility) don't matter, the open-source server can still be a reasonable starting point, but plan to either fork it or migrate off as your needs grow. Or alternatively, just use the open source Svix offering instead.

Given that Convoy no longer has any active full-time maintainers, it's not recommended for any production use. If you care about reliability, uptime, and product maturity, or operate in environments where security and compliance are a must, Svix Dispatch is probably the better fit for you.