Convoy Review (2026): Pricing, Features & Honest Verdict

Reviewed by MakerStack · Published · 7 min read

TLDR

Convoy is an open-source, cloud-native webhooks gateway that ingests, signs, retries, fans out and debugs events so you don’t build that plumbing yourself. Best for: engineering teams shipping webhooks-heavy APIs. Price: Free self-hosted (OSS); Premium self-hosted $999/mo; Cloud free trial then paid. Rating: 7.5/10

What is Convoy?

Convoy is a dedicated webhooks gateway that sits at the edge of your network and does the one job most engineering teams underestimate: reliably delivering events to other people’s servers, and reliably receiving them from providers. If you’ve ever shipped an API, you know the pain. Sending a webhook is a single HTTP POST. Sending webhooks well means retries with exponential backoff, payload signing, per-endpoint rate limiting, static egress IPs, circuit breaking when a customer’s endpoint goes down, a searchable event log for debugging, and a dashboard your customers can actually use. Convoy packages all of that as infrastructure you either self-host or run as a managed cloud service, so you stop rebuilding the same fragile delivery loop in every service you own.

The company behind it is Frain Technologies, founded in February 2021 by Subomi Oluwalana (CEO) and Emmanuel Aina (COO). Oluwalana was a backend developer at Nigerian fintech Tangerine Life, and the pair originally set out to sell APIs to startups. That business didn’t land, but while talking to would-be customers they noticed that nearly everyone building an API hit the same wall with webhooks. They pivoted to solve that, joined Y Combinator’s Winter 2022 batch, and raised roughly $473K in pre-seed funding led by Rally Cap Ventures with participation from Future Africa, Musha Ventures and a long list of African tech angels. Convoy has been open source from day one, with a public roadmap.

Technically, Convoy is written in Go — the same language behind Kubernetes and Prometheus — and is built to scale horizontally. The API server, workers, scheduler and socket server are separate components you can scale independently, and it uses PostgreSQL as its backing store with a control-plane/data-plane split for high availability. It functions, in effect, as a purpose-built message queue for webhooks. The GitHub project (github.com/frain-dev/convoy) sits around 2,800 stars with 200+ tagged releases, so it’s genuinely maintained rather than a weekend proof-of-concept that stalled two years ago.

What Are Convoy’s Key Features?

Incoming and outgoing webhooks in one gateway

Most webhook tools do one direction. Convoy does both. On the outbound side it streams events from your microservices out to your users’ endpoints; on the inbound side it receives webhooks from providers like Stripe or GitHub and routes them to the right internal service. Running both directions through one gateway means a single place to see every event crossing your network boundary, one signing scheme, and one retry policy — instead of two half-baked systems bolted onto different services.

Reliable delivery: retries, rate limiting and circuit breaking

This is the core value. Convoy retries failed deliveries using either constant-interval or exponential backoff with jitter, so a customer’s flapping endpoint doesn’t hammer them or silently drop events. Per-endpoint rate limiting throttles noisy consumers, and endpoint circuit breaking automatically pauses delivery to endpoints that keep failing, then resumes when they recover. You also get email and Slack failure notifications, so a broken consumer surfaces as an alert rather than a support ticket three days later.

Security: payload signing, rolling secrets and static IPs

Every payload can be signed so consumers can verify it genuinely came from you. Convoy supports rolling secrets — rotating signing keys without breaking existing integrations — which also helps guard against attacks like SSRF. Static egress IPs mean your customers can allowlist a fixed set of addresses in their firewalls, a request enterprise consumers make constantly. On the inbound side you get bearer-token authentication and verification, so you’re not writing signature-checking boilerplate for every provider you integrate.

Event fan-out and routing

Convoy can fan out a single event to many endpoints and route based on event type or payload structure. That’s what turns it from a simple relay into a genuine gateway: one internal event can trigger deliveries to dozens of subscribed consumers, each with its own filters, retry rules and rate limits, without your application code knowing or caring how many subscribers exist.

Debugging tools and embeddable customer dashboards

Every event is persisted and searchable, so when a customer says “I never got that webhook,” you can look up the exact delivery, see the response code and body, and replay it. There’s a webhook playground for testing integrations before you go live. And Convoy offers embeddable iframe dashboards (portal links) so your own customers can manage their endpoints, inspect deliveries and retry events themselves — offloading a whole category of support work that otherwise lands on your engineers.

How Much Does Convoy Cost?

Convoy’s pricing splits cleanly between self-hosted and managed cloud, and it’s flat-rate rather than usage-metered. The Community edition is open source and free forever: self-hosted gateway, incoming and outgoing webhooks, automatic retries, message-broker support and community support, with no event cap. That’s a real free tier, not a trial — the tradeoff is you run and maintain the infrastructure.

The Premium self-hosted tier is $999/month and adds the features teams actually reach for at scale: portal links (embeddable customer dashboards), webhook transformation with JavaScript, Google OAuth, a webhook catalogue, OpenTelemetry export, role-based access control, advanced retention, endpoint circuit breaking, white-labelling and priority support. Enterprise is custom-priced and layers on SAML SSO, a support SLA, on-prem deployment help, SOC 2 and compliance support, and solutions engineering. Convoy Cloud, the fully managed SaaS, offers a 14-day free trial (1 project, 1 user, 100 events/day, no card required) before paid plans that reportedly start around $99/month.

For comparison, the closest hosted competitor is Hookdeck, which is usage-based and gets expensive as event volume climbs, while Svix (also YC-backed) starts free and scales into the low hundreds per month before enterprise. The honest read: if you have engineers who can run infrastructure, Convoy’s free OSS edition is dramatically cheaper than any hosted rival. The $999/mo Premium jump is steep for a small team and only makes sense once portal links, RBAC and white-labelling are business-critical.

PlanPricePlan FeaturesBest For
Community (OSS)$0Self-hosted, unlimited events, in/out webhooks, retries, community supportTeams that can self-host
Cloud Trial$0 / 14 days1 project, 1 user, 100 events/day, no cardEvaluating the managed service
Premium (self-hosted)$999/moPortal links, JS transforms, RBAC, OpenTelemetry, white-labelling, priority supportScaling teams needing enterprise features
EnterpriseCustomSAML SSO, SLA support, on-prem help, SOC 2 & complianceEnterprises with compliance needs

Who Is Convoy Best For?

Convoy is squarely a developer-tool for engineering teams whose product exposes webhooks to customers, or who consume a lot of provider webhooks internally. Think a fintech routing payment events, a SaaS platform notifying thousands of customer endpoints, or a growing API company that has outgrown a homegrown “POST and pray” delivery loop. If webhooks are a first-class part of your product surface, Convoy replaces a project you’d otherwise spend an engineering quarter building and then maintaining forever.

Use Convoy if you’re shipping a webhooks-heavy API and want retries, signing, fan-out and a debuggable event log without building them; if you have the DevOps capacity to self-host the free OSS edition (Go binary, PostgreSQL, a message broker); or if enterprise customers are demanding static IPs, RBAC and SOC 2 and you’d rather buy that than build it.

Skip Convoy if you send a handful of webhooks a week — a background job with a simple retry queue is enough and a whole gateway is overkill. Skip it if you have no appetite for self-hosting and the cloud tier’s pricing doesn’t fit your budget, since the value proposition weakens once you’re paying hosted rates. And skip it if your team has zero Go or infrastructure experience and can’t take on operating another stateful service.

Best Convoy Alternatives

Convoy isn’t the only player in the webhooks-infrastructure space. Here are the three most credible alternatives and how they compare.

Svix

Svix is the most direct competitor — also YC-backed, also focused on outbound webhooks-as-a-service. It’s arguably more polished as a pure managed product with excellent SDKs and docs, and it has an open-source server too. Svix leans cloud-first with a free tier and paid plans scaling into the hundreds per month; Convoy leans self-host-first with a genuinely capable free OSS edition. If you want a hosted service and hate ops, Svix; if you want to own the infrastructure, Convoy.

Hookdeck

Hookdeck is a managed gateway strong on the inbound side — receiving, queuing and debugging webhooks from providers — with a slick dashboard and event replay. Its pricing is usage-based and can climb sharply at high event volumes, whereas Convoy’s flat self-hosted model is more predictable at scale. Hookdeck is the easier on-ramp; Convoy is the better long-term cost story if you can host it.

Hooky / QStash (Upstash)

Upstash’s QStash is a serverless message/webhook queue that’s dead simple and cheap for lightweight delivery with retries, priced per message with a free tier. It lacks Convoy’s customer-facing dashboards, fan-out routing and enterprise controls, but for a small team that just needs reliable delivery without running anything, it’s a lighter, cheaper starting point than a full gateway.

Final Verdict: Is Convoy Worth It?

Convoy solves a real, thankless problem well. Webhook delivery is deceptively hard, and every team that builds it in-house rediscovers the same edge cases — retries, signing, dead endpoints, debugging “I never got it” tickets — the expensive way. Convoy hands you that infrastructure as a Go service you can self-host for free, with the retry logic, security controls and debugging tooling already battle-tested across 200+ releases. For an engineering team that treats webhooks as a first-class product feature, that’s genuinely valuable.

The caveats are honest ones. The free edition is only free if you can operate it, and the leap to Premium at $999/month is a hard sell for a small startup that only needs one or two paid features. The Elastic License v2.0 (not a pure open-source license like MIT) means there are restrictions on offering Convoy as a competing hosted service. And as a younger, pre-seed-funded company with a modest team, Convoy carries more platform risk than an incumbent — though being open source and self-hostable meaningfully hedges that; worst case, you keep running the code.

Our recommendation: if you ship webhooks-heavy APIs and have engineers comfortable with Go and PostgreSQL, start with the free self-hosted Community edition today — it’s one of the best value-for-effort tools in the developer-infra category. If you can’t self-host, trial Convoy Cloud but price-compare hard against Svix and Hookdeck before committing. Just don’t reach for a gateway if you’re only sending a trickle of events; that’s a job for a background queue, not Convoy.

Convoy Pros & Cons

What We Like

  • Genuinely free, unlimited self-hosted open-source edition
  • Handles both incoming and outgoing webhooks in one gateway
  • Strong reliability: retries, rate limiting, circuit breaking, static IPs
  • Embeddable customer dashboards offload webhook support work
  • Written in Go and horizontally scalable with a public roadmap

What Could Be Better

  • Big price jump to $999/mo Premium for small teams
  • Free edition requires DevOps capacity to self-host and maintain
  • Elastic License v2.0 restricts hosting Convoy as a competing service
  • Younger pre-seed company carries more platform risk than incumbents

Convoy FAQ

What is Convoy?

Convoy is an open-source, cloud-native webhooks gateway from Frain Technologies (getconvoy.io). It ingests, signs, retries, fans out and debugs both incoming and outgoing webhooks, giving engineering teams reliable event-delivery infrastructure without building it themselves.

How much does Convoy cost?

The self-hosted Community edition is free and open source with unlimited events. Premium self-hosted is $999/month, Enterprise is custom-priced, and Convoy Cloud offers a 14-day free trial before paid plans reportedly starting around $99/month.

Is Convoy worth it?

Yes, if you ship webhooks-heavy APIs and can self-host. The free OSS edition delivers battle-tested retry, signing and debugging infrastructure at no cost. The $999/mo Premium tier is only worth it once features like portal links and RBAC are business-critical.

What are the best Convoy alternatives?

The strongest alternatives are Svix (YC-backed, cloud-first webhooks service), Hookdeck (managed gateway strong on inbound webhooks, usage-based pricing), and Upstash QStash (a simple, cheap serverless webhook queue for lighter needs).

Does Convoy offer a free plan?

Yes. The self-hosted Community edition is open source and free forever with unlimited events. Convoy Cloud also has a 14-day free trial (1 project, 1 user, 100 events/day, no credit card required).

Who is Convoy best for?

Convoy is best for engineering teams whose product exposes webhooks to customers or who consume many provider webhooks internally — fintechs, SaaS platforms and API companies that have outgrown a homegrown delivery loop and can operate the self-hosted service.

Disclosure: MakerStack is funded by featured placement fees, sponsor slots and a small number of affiliate links. Nobody paid for this review. Where any of those does apply to a review, we say so on the page. The scoring criteria are the same in every case. See our editorial policy.