APIs · head to head
Convoy vs Lago

Convoy
APIs
Open source webhooks gateway you self-host, handling both sending and receiving
- From
- Free
- Rated
- -

Lago
Accounting
Open-source billing infrastructure for usage-based models
- From
- Free
- Rated
- -
The short version
- Each has a real cost: Convoy the default deployment is self-hosted, so you operate Convoy plus Postgres and Redis and carry the on-call burden for the system that delivers your customers' events.; Lago free tier limited to 10,000 entities per month with 5M event cap
- They diverge on capability: Convoy covers Inbound and outbound, Lago covers Real-time usage metering.
- Prices and features above were last checked on 31 August 2026.
Where they differ
Only the attributes on which Convoy and Lago actually diverge.
Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated).
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in Convoy
- Inbound and outbound
- Broker-driven ingestion
- Payload transformation
- Portal links
- Circuit breaking
- Retry policies
- OpenTelemetry export
- Role-based access control
Only in Lago
- Real-time usage metering
- Multiple pricing models
- Automated invoicing
- Prepaid credits
- Entitlements
- Multi-currency support
- Payment orchestration
- Revenue analytics
What people use each for
The jobs each tool is most often brought in to do.
Convoy
- A fintech that cannot route customer webhook traffic through a third-party SaaS for compliance reasonsnot Lago
- A high-volume platform for which per-message webhook pricing costs more than the flat premium licencenot Lago
- A team that also receives webhooks from many providers and wants ingestion, verification and deduplication in the same gatewaynot Lago
- An engineering group that wants webhook delivery driven directly from an existing Kafka or SQS topicnot Lago
Lago
- Building usage-based billing for high-volume APIs and infrastructurenot Convoy
- Implementing metered billing for AI and tokenized servicesnot Convoy
- Creating subscription and hybrid pricing modelsnot Convoy
- Managing multi-currency billing for global companiesnot Convoy
- Maintaining billing infrastructure without vendor lock-innot Convoy
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Convoy
- The default deployment is self-hosted, so you operate Convoy plus Postgres and Redis and carry the on-call burden for the system that delivers your customers' events.
- Frain Technologies is a small startup, and putting customer-facing delivery infrastructure on it means accepting real vendor continuity risk on a component that is hard to swap out quickly.
- The premium tier at a flat 999 US dollars a month is poor value below substantial volume, while the community edition omits the portal, transformations and RBAC that most production deployments end up wanting.
- The hosted cloud trial is capped at one project and 100 events a day, which is too small to properly evaluate the service before committing.
- Documentation and the third-party ecosystem are thinner than the established webhook services, so unusual configurations often mean reading the Go source.
Lago
- Free tier limited to 10,000 entities per month with 5M event cap
- No specific pricing published for Pro annual plan or Scale plan
- Self-hosted and on-premise deployments require engineering resources
- Community support only on free tier
- Scale plan requires annual contracts and sales engagement
Pricing, plan by plan
Convoy
Free- CommunityFree
- Self-hosted open source gateway
- Inbound and outbound webhooks
- Automatic retries and message broker support
- Premium$999/month
- Flat rate irrespective of message volume
- Portal links and payload transformation
- RBAC, circuit breaking and white labelling
- Enterprise$undefined/year
- SAML SSO
- Dedicated support with SLA
- On-premises deployment assistance
- Cloud$undefined/month
- Hosted by Convoy
- 14 day trial limited to one project and 100 events a day
- Usage-based tiers above the trial
Lago
Free- Build (Free)Free
- 10,000 managed entities per month
- 5M usage events per month
- 1K events per second rate limit
- Pro$399/month
- 10,000 entities included (graduated pricing to 100K)
- 25M usage events included (to 500M with graduated rates)
- 10K events per second (upgradeable to 100K)
- Scale$null/custom
- Custom entity and event volumes
- 50K events per second (upgradeable to 100K)
- RBAC and SSO (SAML)
Which should you pick?
Choose Convoy if
- You need inbound and outbound.
- You want to start without paying.
- You work on Linux, Docker, Kubernetes, Cloud.
- You also want broker-driven ingestion.
Choose Lago if
- You need real-time usage metering.
- You want to start without paying.
- You work on Web, Cloud, Self-hosted, On-premise, VPC.
- You also want multiple pricing models.
Questions people ask
- Is Convoy or Lago better?
- Neither clearly leads. Convoy starts at Free and Lago at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Convoy or Lago?
- Convoy starts at Free and Lago at Free.
- Does Convoy or Lago run on more platforms?
- Convoy runs on Linux, Docker, Kubernetes, Cloud. Lago runs on Web, Cloud, Self-hosted, On-premise, VPC.
- Can I use Convoy for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is Convoy best used for?
- Convoy is most often used for a fintech that cannot route customer webhook traffic through a third-party saas for compliance reasons, a high-volume platform for which per-message webhook pricing costs more than the flat premium licence, a team that also receives webhooks from many providers and wants ingestion, verification and deduplication in the same gateway, an engineering group that wants webhook delivery driven directly from an existing kafka or sqs topic. Of those, a fintech that cannot route customer webhook traffic through a third-party saas for compliance reasons and a high-volume platform for which per-message webhook pricing costs more than the flat premium licence are not what Lago is typically brought in for.
- What can Convoy do that Lago cannot?
- Convoy covers Inbound and outbound, Broker-driven ingestion, Payload transformation, Portal links. Lago covers Real-time usage metering, Multiple pricing models, Automated invoicing, Prepaid credits.
Answered from the vendors’ own pages
Convoy: Is Convoy really open source?
Yes, the community edition is open source and self-hostable, covering both inbound and outbound webhooks with retries.
Lago: Can I use Lago open-source for free?
Yes, Lago is open-source under the AGPLv3 license and can be self-hosted. The cloud-based Build plan is also free with limits of 10,000 entities and 5M events per month.
SourceConvoy: What does premium cost?
A flat 999 US dollars a month, self-hosted, regardless of message volume.
Lago: What payment providers does Lago integrate with?
Lago integrates with Stripe and Adyen for payment processing. It is not a payment processor itself but orchestrates payments through these providers.
SourceConvoy: Does it receive webhooks as well as send them?
Yes, inbound ingestion with verification and deduplication is a first-class feature, unlike most webhook services.
Lago: Does Lago support multiple currencies?
Yes, Lago supports multi-currency billing with automatic currency conversion for global businesses.
SourceConvoy: Do I have to self-host?
No, there is a hosted cloud, but the trial is capped at 100 events a day and self-hosting is the primary model.
Related pages
Other head to heads
- Convoy vs Kong
- Convoy vs Svix
- Convoy vs Tyk
- Convoy vs Janus Gateway
- Convoy vs Appwrite
- Convoy vs Gravitee
- Convoy vs Spring Cloud Gateway
- Convoy vs Formance
- Convoy vs AWS API Gateway
- Convoy vs Hasura
- Convoy vs PocketBase
- Convoy vs Sensedia
- Convoy vs Sila
- Convoy vs Swagger
- Convoy vs TIBCO Mashery
- Convoy vs Zeplo
- Convoy vs Kong Gateway
- Convoy vs Orb
- Convoy vs Metronome
- Convoy vs Stigg
- Convoy vs Dodo Payments
- Convoy vs Creem
- Convoy vs Invoicera
- Convoy vs Polar
- Convoy vs Maxio
- Convoy vs Zuora
- Convoy vs Paddle
- Convoy vs Invoicely
- Convoy vs QuickBooks
- Convoy vs Mercury
- Convoy vs Mesh Payments
- Convoy vs Money Forward Cloud
- Convoy vs Moneybird
- Convoy vs MYOB
- Convoy vs Netvisor
- Lago vs Kong
- Lago vs Svix
- Lago vs Tyk
- Lago vs Janus Gateway
- Lago vs Appwrite
- Lago vs Gravitee
- Lago vs Spring Cloud Gateway
- Lago vs Formance
- Lago vs AWS API Gateway
- Lago vs Hasura
- Lago vs PocketBase
- Lago vs Sensedia
- Lago vs Sila
- Lago vs Swagger
- Lago vs TIBCO Mashery
- Lago vs Zeplo
- Lago vs Kong Gateway
- Lago vs Orb
- Lago vs Metronome
- Lago vs Stigg
- Lago vs Dodo Payments
- Lago vs Creem
- Lago vs Invoicera
- Lago vs Polar
- Lago vs Maxio
- Lago vs Zuora
- Lago vs Paddle
- Lago vs Invoicely
- Lago vs QuickBooks
- Lago vs Mercury
- Lago vs Mesh Payments
- Lago vs Money Forward Cloud
- Lago vs Moneybird
- Lago vs MYOB
- Lago vs Netvisor
