APIs · head to head
Enfuce vs Envoy

Enfuce
APIs
European issuer processor holding its own payment institution licence
- From
- On request
- Free plan
- No

Envoy
Developer Tools
A high-performance L7 proxy written in C++ that is configured by an API rather than a config file, and is usually deployed under a control plane.
- From
- Free
- Free plan
- Yes
The short version
- Envoy is free; Enfuce prices on request.
- Only Enfuce lists licensed issuing; only Envoy lists xDS dynamic configuration.
- Where Enfuce falls short: coverage is European, so a programme that also needs US or Asian issuing requires a separate processor and a separate integration.
- Prices and features on this page were last checked on 20 November 2026.
How do Enfuce and Envoy differ?
Enfuce and Envoy differ on starting price (On request against Free), pricing model (Quote against Open-source) and free tier (No against Yes). Only the attributes on which Enfuce and Envoy actually diverge.
Which features does each one have?
They share no listed features; 6 appear only for Enfuce and 8 only for Envoy. 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 Enfuce
- Licensed issuing
- Card processing
- Tokenisation
- Spend controls
- Multi-currency programmes
- Carbon and data services
Only in Envoy
- xDS dynamic configuration
- Protocol breadth
- Filter chain architecture
- Observability by default
- Outlier detection
- Traffic shaping
- mTLS termination and origination
- Hot restart
What is each one used for?
Enfuce is most often brought in for A bank migrating an existing European card portfolio off a legacy processor. The jobs each tool is most often brought in to do.
Enfuce
- A European fintech launching cards without spending two quarters finding a sponsor banknot Envoy
- A corporate issuing fuel or expense cards across several EU countries on one programmenot Envoy
- A bank migrating an existing European card portfolio off a legacy processornot Envoy
- A programme that must report cardholder transaction carbon data to meet sustainability commitmentsnot Envoy
Envoy
- Acting as the data plane under a service mesh or Gateway API implementation, which is how the overwhelming majority of deployments use itnot Enfuce
- An edge or API gateway that needs per-route retry budgets, circuit breaking and outlier detection rather than round-robin proxyingnot Enfuce
- Migrating traffic between service versions or between a monolith and its replacement, using weighted splits and shadow trafficnot Enfuce
- Standardising observability across a polyglot estate, so that latency, error rates and tracing look the same regardless of the language a service is written innot Enfuce
Where do Enfuce and Envoy fall short?
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
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
Envoy
- The configuration surface is very large and hand-written bootstrap YAML runs to hundreds of lines for routing that Nginx expresses in twenty, which is why nearly every production deployment sits under a control plane and inherits that control plane's constraints as well
- xDS is the real API and it is not stable in the comfortable sense; the v2 API set was removed outright, resource types continue to be deprecated, and your control plane and Envoy binaries have to be upgraded roughly in step or the proxies stop accepting configuration
- Extending it properly means writing a C++ filter and building and maintaining your own Envoy binary; the alternatives are Lua, which adds per-request overhead, and proxy-wasm, whose ABI has remained effectively experimental for years with a real performance cost
- At sidecar density the per-proxy memory and CPU footprint is a measurable share of cluster capacity, since thousands of workloads each carry a full proxy, and this is precisely the cost that has pushed mesh projects towards node-level or ambient architectures
- There is no single vendor selling support for Envoy itself; you get the community plus control-plane vendors such as Solo.io and Tetrate, so an Envoy-level production bug is your own engineers in a C++ codebase unless a support contract happens to cover it
- Diagnosing why a request got a particular response involves reading config dumps, the stats endpoint and the RESPONSE_FLAGS codes in access logs rather than a readable error, which is a specific skill you must hire or spend months growing
How much do Enfuce and Envoy cost?
Enfuce is priced on request; Envoy is free to use. Plan by plan below, from each vendor's own pricing page.
Enfuce
On request- Enfuce issuing and processingOn request
- 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
Envoy
FreeNo published plan breakdown. See the Envoy review.
Which should you pick?
Choose Enfuce if
- You need licensed issuing.
- You work on Web, API.
- You also want card processing.
Choose Envoy if
- You need xds dynamic configuration.
- You want to start without paying.
- You also want protocol breadth.
Questions people ask
- Is Enfuce or Envoy better?
- Neither clearly leads. Enfuce starts at On request and Envoy at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Enfuce or Envoy?
- Envoy has a free tier; the other does not. Paid plans start at On request for Enfuce and Free for Envoy.
- Does Enfuce or Envoy run on more platforms?
- Enfuce runs on Web, API. Envoy runs on Web.
- Can I use Envoy for free?
- Yes. Envoy has a free tier, so you can try it without paying. Enfuce starts at On request.
- What is Enfuce best used for?
- Enfuce is most often used for a european fintech launching cards without spending two quarters finding a sponsor bank, a corporate issuing fuel or expense cards across several eu countries on one programme, a bank migrating an existing european card portfolio off a legacy processor, a programme that must report cardholder transaction carbon data to meet sustainability commitments. Of those, a european fintech launching cards without spending two quarters finding a sponsor bank and a corporate issuing fuel or expense cards across several eu countries on one programme are not what Envoy is typically brought in for.
- What can Enfuce do that Envoy cannot?
- Enfuce covers Licensed issuing, Card processing, Tokenisation, Spend controls. Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default.
Answered from the vendors’ own pages
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.
Envoy: Should I run Envoy on its own, or under a control plane?
Almost always under one. Directly authoring xDS or static bootstrap configuration is viable for a handful of routes and becomes unmanageable beyond that. Envoy Gateway, Istio, Contour, Gloo and Consul all exist to generate that configuration for you.
Enfuce: Which regions does it cover?
Europe. It is not a route to issuing cards in the United States or Asia.
Envoy: How does it compare with Nginx or HAProxy?
Envoy is dynamically configured over an API and instrumented far more heavily; Nginx and HAProxy are faster to configure and lighter for straightforward reverse proxying. If you never need to change routing without a reload, Envoy is more machinery than the problem requires.
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.
Envoy: What does it cost?
Nothing to licence; it is Apache 2.0 and there is no paid edition. The cost is engineering time and, for most organisations, a commercial control plane or cloud service that packages it.
Envoy: Can I write extensions without C++?
You can write Lua filters or proxy-wasm modules in Rust, Go, C++ or AssemblyScript. Both carry per-request overhead compared with a native filter, and the Wasm path has been slower to stabilise than the project originally projected.
Envoy: Is it a CNCF project?
Yes, it is a graduated CNCF project licensed under Apache 2.0, which means the trademark and governance sit with the foundation rather than with Lyft or any vendor.
Related pages
Other head to heads
- Enfuce vs Marqeta
- Enfuce vs Paymentology
- Enfuce vs Highnote
- Enfuce vs i2c
- Enfuce vs Weavr
- Enfuce vs Lithic
- Enfuce vs Thredd
- Enfuce vs Episode Six
- Enfuce vs Tribe Payments
- Enfuce vs Tink
- Enfuce vs Enable Banking
- Enfuce vs Salt Edge
- Enfuce vs Akana
- Enfuce vs Astra
- Enfuce vs Asyncapi
- Enfuce vs Boomi API Management
- Enfuce vs Fintech Farm
- Enfuce vs Formance
- Enfuce vs Istio
- Enfuce vs Ona (formerly Gitpod)
- Enfuce vs Spacelift
- Enfuce vs Jenkins
- Enfuce vs Hookdeck
- Enfuce vs Atlantis
- Enfuce vs Restate
- Enfuce vs Turborepo
- Enfuce vs Helix
- Enfuce vs Git
- Enfuce vs Okteto
- Enfuce vs StackBlitz
- Enfuce vs CodeSandbox
- Enfuce vs Cody
- Enfuce vs Depot
- Enfuce vs Neovim
- Enfuce vs Azure DevOps
- Enfuce vs Bitbucket
- Envoy vs Marqeta
- Envoy vs Paymentology
- Envoy vs Highnote
- Envoy vs i2c
- Envoy vs Weavr
- Envoy vs Lithic
- Envoy vs Thredd
- Envoy vs Episode Six
- Envoy vs Tribe Payments
- Envoy vs Tink
- Envoy vs Enable Banking
- Envoy vs Salt Edge
- Envoy vs Akana
- Envoy vs Astra
- Envoy vs Asyncapi
- Envoy vs Boomi API Management
- Envoy vs Fintech Farm
- Envoy vs Formance
- Envoy vs Istio
- Envoy vs Ona (formerly Gitpod)
- Envoy vs Spacelift
- Envoy vs Jenkins
- Envoy vs Hookdeck
- Envoy vs Atlantis
- Envoy vs Restate
- Envoy vs Turborepo
- Envoy vs Helix
- Envoy vs Git
- Envoy vs Okteto
- Envoy vs StackBlitz
- Envoy vs CodeSandbox
- Envoy vs Cody
- Envoy vs Depot
- Envoy vs Neovim
- Envoy vs Azure DevOps
- Envoy vs Bitbucket
