Softwr

APIs · head to head

Convoy vs Yapily

Convoy logo

Convoy

APIs

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

From
Free
Rated
-
Full reviewWebsite
Yapily logo

Yapily

APIs

Open banking API infrastructure for account data and pay-by-bank payments across Europe

From
Free
Rated
-
Full reviewWebsite

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.; Yapily production pricing itself is not published; only the resulting typical merchant transaction cost is publicly known, so the underlying platform fee still requires a sales conversation.
  • They diverge on capability: Convoy covers Inbound and outbound, Yapily covers Unified open banking API.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Convoy and Yapily actually diverge.

Attributes where Convoy and Yapily differ
AttributeConvoyYapily
Pricing modelPer month, flat rate regardless of volumeFree sandbox, pay-as-you-go production
PlatformsLinux, Docker, Kubernetes, CloudWeb, API

Identical on both: starting price (Free), free tier (Yes), 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 Yapily

  • Unified open banking API
  • Account information access
  • Payment initiation
  • Free sandbox
  • Multi-country bank coverage
  • Webhooks and reconciliation tooling

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

Yapily

  • A merchant wanting a lower-cost payment method alongside card acceptancenot Convoy
  • A lending or budgeting product needing bank account data for affordability checksnot Convoy
  • A business wanting one API instead of separate integrations to each bank's own open banking standardnot Convoy
  • A company prototyping open banking features for free in sandbox before committing budgetnot 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.

Yapily

  • Production pricing itself is not published; only the resulting typical merchant transaction cost is publicly known, so the underlying platform fee still requires a sales conversation.
  • Consumer adoption of pay-by-bank still lags card payments, so merchants offering it as a checkout option typically see it used as a secondary rather than primary payment method.
  • Coverage depends on the banks in each country maintaining reliable open banking APIs, and inconsistent bank-side reliability across markets is a known category-wide weakness, not unique to Yapily but not solved by it either.
  • As infrastructure for both account data and payments, a company only needing one of those two capabilities is still evaluating a broader platform than it may need.
  • Regulatory dependence on PSD2 and UK open banking rules means the underlying legal framework, not just Yapily's product, could shift and affect what is possible on the platform.

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

Yapily

Free
  • SandboxFree
    • Free testing environment
    • UK and European bank connections for development
  • Production$undefined/month
    • Pay-as-you-go pricing, exact rates not published
    • Typical pay-by-bank cost of 0.1 to 0.5% or a flat 5 to 30 pence per transaction

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 Yapily if

  • You need unified open banking api.
  • You want to start without paying.
  • You work on Web, API.
  • You also want account information access.
Yapily review

Questions people ask

Is Convoy or Yapily better?
Neither clearly leads. Convoy starts at Free and Yapily at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Convoy or Yapily?
Convoy starts at Free and Yapily at Free.
Does Convoy or Yapily run on more platforms?
Convoy runs on Linux, Docker, Kubernetes, Cloud. Yapily runs on Web, API.
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 Yapily is typically brought in for.
What can Convoy do that Yapily cannot?
Convoy covers Inbound and outbound, Broker-driven ingestion, Payload transformation, Portal links. Yapily covers Unified open banking API, Account information access, Payment initiation, Free sandbox.

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.

Yapily: Is there a free way to try it?

Yes, sandbox access is free for development and testing.

Convoy: What does premium cost?

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

Yapily: How much cheaper is pay-by-bank than card payments?

Typically 0.1 to 0.5% of transaction value, or a flat 5 to 30 pence, against 1.5 to 3.5% for card scheme fees.

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.

Yapily: Is production pricing published?

No, production access is pay-as-you-go but exact rates require a sales conversation.

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 Yapily

Keep looking

Other head to heads