APIs · head to head
Convoy vs Lithic

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

Lithic
APIs
API-first card issuing platform with direct Visa, Mastercard and Amex network connections
- From
- On request
- Rated
- -
The short version
- Only Convoy has a free tier, so it costs nothing to try first.
- 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.; Lithic pricing is entirely undisclosed, so a company cannot compare total cost against Marqeta, Galileo or Highnote without a sales conversation.
- They diverge on capability: Convoy covers Inbound and outbound, Lithic covers Direct network connections.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which Convoy and Lithic actually diverge.
Identical on both: user rating (Not yet rated), category (APIs).
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 Lithic
- Direct network connections
- Processor Client mode
- Lithic Program Management
- Card lifecycle APIs
- Sandbox environment
- Real-time authorization controls
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 Lithic
- A high-volume platform for which per-message webhook pricing costs more than the flat premium licencenot Lithic
- A team that also receives webhooks from many providers and wants ingestion, verification and deduplication in the same gatewaynot Lithic
- An engineering group that wants webhook delivery driven directly from an existing Kafka or SQS topicnot Lithic
Lithic
- A fintech wanting direct Visa or Mastercard network access rather than routing through a third-party processornot Convoy
- A company that already holds its own issuing licence and wants API access without full programme managementnot Convoy
- A neobank or expense platform wanting Lithic to manage bank and network relationships end to endnot Convoy
- A product team prototyping a card programme in sandbox before committing to a launchnot 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.
Lithic
- Pricing is entirely undisclosed, so a company cannot compare total cost against Marqeta, Galileo or Highnote without a sales conversation.
- Choosing Processor Client mode still leaves the company responsible for holding its own issuing licence and managing the regulatory relationship, which is a substantial undertaking many teams underestimate.
- As with any card infrastructure provider, an outage or network issue at Lithic becomes a direct outage for every card programme built on it, and a customer has limited visibility into root cause during an incident.
- Building a card programme on API infrastructure requires real engineering investment; it is not a plug-and-play product for a non-technical team.
- Switching card infrastructure providers after launch is a major undertaking involving card reissuance and programme migration, so the initial choice carries lasting lock-in.
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
Lithic
On request- Lithic$undefined/year
- Volume and interchange-based pricing, not published
- Separate Processor Client and Program Management pricing tracks
- Custom quote required via sales
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 Lithic if
- You need direct network connections.
- You work on Web, API.
- You also want processor client mode.
Questions people ask
- Is Convoy or Lithic better?
- Neither clearly leads. Convoy starts at Free and Lithic at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Convoy or Lithic?
- Convoy has a free tier; the other does not. Paid plans start at Free for Convoy and On request for Lithic.
- Does Convoy or Lithic run on more platforms?
- Convoy runs on Linux, Docker, Kubernetes, Cloud. Lithic runs on Web, API.
- Can I use Convoy for free?
- Yes. Convoy has a free tier, so you can try it without paying. Lithic starts at On request.
- 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 Lithic is typically brought in for.
- What can Convoy do that Lithic cannot?
- Convoy covers Inbound and outbound, Broker-driven ingestion, Payload transformation, Portal links. Lithic covers Direct network connections, Processor Client mode, Lithic Program Management, Card lifecycle APIs.
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.
Lithic: Does Lithic publish pricing?
No, pricing is volume-based and requires a sales conversation.
Convoy: What does premium cost?
A flat 999 US dollars a month, self-hosted, regardless of message volume.
Lithic: What is the difference between Processor Client and Program Management?
Processor Client suits companies with their own issuing licence and bank relationships; Program Management is for companies wanting Lithic to coordinate those relationships on their behalf.
Convoy: 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.
Lithic: Which networks does it connect to?
Visa, Mastercard and American Express directly.
Convoy: 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 Thredd
- Convoy vs Tribe Payments
- Convoy vs Unit
- Convoy vs Highnote
- Convoy vs Vodeno
- Convoy vs Swan
- Convoy vs Treasury Prime
- Convoy vs Marqeta
- Convoy vs Synctera
- Convoy vs Weavr
- Convoy vs Increase
- Convoy vs i2c
- Convoy vs Brite Payments
- Convoy vs Bruno
- Convoy vs Bud Financial
- Convoy vs Episode Six
- Lithic vs Kong
- Lithic vs Svix
- Lithic vs Tyk
- Lithic vs Janus Gateway
- Lithic vs Appwrite
- Lithic vs Gravitee
- Lithic vs Spring Cloud Gateway
- Lithic vs Formance
- Lithic vs AWS API Gateway
- Lithic vs Hasura
- Lithic vs PocketBase
- Lithic vs Sensedia
- Lithic vs Sila
- Lithic vs Swagger
- Lithic vs TIBCO Mashery
- Lithic vs Zeplo
- Lithic vs Kong Gateway
- Lithic vs Thredd
- Lithic vs Tribe Payments
- Lithic vs Unit
- Lithic vs Highnote
- Lithic vs Vodeno
- Lithic vs Swan
- Lithic vs Treasury Prime
- Lithic vs Marqeta
- Lithic vs Synctera
- Lithic vs Weavr
- Lithic vs Increase
- Lithic vs i2c
- Lithic vs Brite Payments
- Lithic vs Bruno
- Lithic vs Bud Financial
- Lithic vs Episode Six
