Softwr

APIs · head to head

Convoy vs Enfuce

Convoy logo

Convoy

APIs

Open source webhooks gateway you self-host, handling both sending and receiving

From
Free
Rated
-
Full reviewWebsite
Enfuce logo

Enfuce

APIs

European issuer processor holding its own payment institution licence

From
On request
Rated
-
Full reviewWebsite

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.; Enfuce coverage is European, so a programme that also needs US or Asian issuing requires a separate processor and a separate integration.
  • They diverge on capability: Convoy covers Inbound and outbound, Enfuce covers Licensed issuing.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Convoy and Enfuce actually diverge.

Attributes where Convoy and Enfuce differ
AttributeConvoyEnfuce
Starting priceFreeOn request
Pricing modelPer month, flat rate regardless of volumequote
Free tierYesNo
PlatformsLinux, Docker, Kubernetes, CloudWeb, REST API

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 Enfuce

  • Licensed issuing
  • Card processing
  • Tokenisation
  • Spend controls
  • Multi-currency programmes
  • Carbon and data services

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 Enfuce
  • A high-volume platform for which per-message webhook pricing costs more than the flat premium licencenot Enfuce
  • A team that also receives webhooks from many providers and wants ingestion, verification and deduplication in the same gatewaynot Enfuce
  • An engineering group that wants webhook delivery driven directly from an existing Kafka or SQS topicnot Enfuce

Enfuce

  • A European fintech launching cards without spending two quarters finding a sponsor banknot Convoy
  • A corporate issuing fuel or expense cards across several EU countries on one programmenot Convoy
  • A bank migrating an existing European card portfolio off a legacy processornot Convoy
  • A programme that must report cardholder transaction carbon data to meet sustainability commitmentsnot 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.

Enfuce

  • Coverage is European, so a programme that also needs US or Asian issuing requires a separate processor and a separate integration.
  • Where Enfuce acts as the licensed issuer it takes on regulatory risk and prices accordingly, so the convenience of skipping a sponsor bank is not free.
  • European interchange caps limit programme revenue far below US levels, so business cases imported from a US card model do not survive the move.
  • It is a smaller supplier than Marqeta or i2c, which means less negotiating room on scheme fees and a thinner partner ecosystem around it.
  • Pricing is entirely quoted with monthly minimums, so low-volume programmes carry a fixed cost that does not scale down with a slow launch.

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

Enfuce

On request
  • Enfuce issuing and processing$undefined/year
    • Per-active-card and per-transaction fees with monthly minimums
    • Higher pricing where Enfuce acts as licensed issuer rather than processor only
    • Interchange arrangements depend on who holds the issuing licence

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.
Convoy review

Choose Enfuce if

  • You need licensed issuing.
  • You work on Web, REST API.
  • You also want card processing.
Enfuce review

Questions people ask

Is Convoy or Enfuce better?
Neither clearly leads. Convoy starts at Free and Enfuce at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Convoy or Enfuce?
Convoy has a free tier; the other does not. Paid plans start at Free for Convoy and On request for Enfuce.
Does Convoy or Enfuce run on more platforms?
Convoy runs on Linux, Docker, Kubernetes, Cloud. Enfuce runs on Web, REST API.
Can I use Convoy for free?
Yes. Convoy has a free tier, so you can try it without paying. Enfuce 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 Enfuce is typically brought in for.
What can Convoy do that Enfuce cannot?
Convoy covers Inbound and outbound, Broker-driven ingestion, Payload transformation, Portal links. Enfuce covers Licensed issuing, Card processing, Tokenisation, Spend controls.

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.

Enfuce: Do I need my own licence to use Enfuce?

Not necessarily. Enfuce holds Finnish payment institution authorisation and can act as issuer, or process under your own licence if you have one.

Convoy: What does premium cost?

A flat 999 US dollars a month, self-hosted, regardless of message volume.

Enfuce: Which regions does it cover?

Europe. It is not a route to issuing cards in the United States or Asia.

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.

Enfuce: How does interchange work?

Who holds the issuing licence determines who receives interchange, so the licensing choice and the revenue model are the same decision.

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.

Share

Related pages

More on Convoy

More on Enfuce

Keep looking

Other head to heads