Softwr

Developer Tools · head to head

Envoy vs Feedzai

Envoy logo

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
Visit EnvoyFull review
Feedzai logo

Feedzai

Cybersecurity

Real-time transaction fraud and financial crime detection for banks and payment processors

From
On request
Free plan
No
Visit FeedzaiFull review

The short version

  • Envoy is free; Feedzai prices on request.
  • Only Envoy lists xDS dynamic configuration; only Feedzai lists real-time scoring.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which Envoy and Feedzai actually diverge.

Attributes where Envoy and Feedzai differ
AttributeEnvoyFeedzai
Starting priceFreeOn request
Pricing modelOpen-sourceQuote
Free tierYesNo
PlatformsWebWeb, Linux
CategoryDeveloper ToolsCybersecurity

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 Envoy

  • xDS dynamic configuration
  • Protocol breadth
  • Filter chain architecture
  • Observability by default
  • Outlier detection
  • Traffic shaping
  • mTLS termination and origination
  • Hot restart

Only in Feedzai

  • Real-time scoring
  • Rule and model hybrid
  • Case manager
  • Behavioural biometrics
  • Model explainability
  • Deployment options

What people use each for

The jobs each tool is most often brought in to do.

Envoy

  • Acting as the data plane under a service mesh or Gateway API implementation, which is how the overwhelming majority of deployments use itnot Feedzai
  • An edge or API gateway that needs per-route retry budgets, circuit breaking and outlier detection rather than round-robin proxyingnot Feedzai
  • Migrating traffic between service versions or between a monolith and its replacement, using weighted splits and shadow trafficnot Feedzai
  • 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 Feedzai

Feedzai

  • A bank joining an instant payments scheme where transfers are irrevocable and post-hoc recovery is impossiblenot Envoy
  • A card issuer whose existing rules engine cannot be changed without a release, so fraud waves run for daysnot Envoy
  • An acquirer needing per-merchant risk models rather than one portfolio-wide modelnot Envoy
  • A bank required by its regulator to explain automated declines to customers, which rules out opaque scoringnot Envoy

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

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

Feedzai

  • Pricing is per transaction with an annual minimum, so a bank with seasonal or growing volume commits to a floor it may not use and pays overage above the band
  • It sits in the authorisation path, which makes every upgrade a change-controlled event with rollback plans, and the operational burden falls on the bank rather than the vendor
  • Out of the box models need months of the customer own labelled fraud history before they beat the rules they replace, so the value case starts late
  • AML and fraud are licensed as separate modules, so institutions expecting one platform fee find the transaction monitoring capability is a second line item
  • The buyer profile is large institutions, so smaller banks and fintechs face minimums that make per-transaction economics unattractive below significant scale

Pricing, plan by plan

Envoy

Free

No published plan breakdown. See the Envoy review.

Feedzai

On request
  • Feedzai Financial Crime PlatformOn request
    • Priced by transaction volume with annual minimum commitment
    • Modules for fraud, AML and account opening licensed separately
    • Cloud, private cloud and on-premises deployment

Which should you pick?

Choose Envoy if

  • You need xds dynamic configuration.
  • You want to start without paying.
  • You also want protocol breadth.
Envoy review

Choose Feedzai if

  • You need real-time scoring.
  • You work on Web, Linux.
  • You also want rule and model hybrid.
Feedzai review

Questions people ask

Is Envoy or Feedzai better?
Neither clearly leads. Envoy starts at Free and Feedzai at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Envoy or Feedzai?
Envoy has a free tier; the other does not. Paid plans start at Free for Envoy and On request for Feedzai.
Does Envoy or Feedzai run on more platforms?
Envoy runs on Web. Feedzai runs on Web, Linux.
Can I use Envoy for free?
Yes. Envoy has a free tier, so you can try it without paying. Feedzai starts at On request.
What is Envoy best used for?
Envoy is most often used for acting as the data plane under a service mesh or gateway api implementation, which is how the overwhelming majority of deployments use it, an edge or api gateway that needs per-route retry budgets, circuit breaking and outlier detection rather than round-robin proxying, migrating traffic between service versions or between a monolith and its replacement, using weighted splits and shadow traffic, standardising observability across a polyglot estate, so that latency, error rates and tracing look the same regardless of the language a service is written in. Of those, acting as the data plane under a service mesh or gateway api implementation, which is how the overwhelming majority of deployments use it and an edge or api gateway that needs per-route retry budgets, circuit breaking and outlier detection rather than round-robin proxying are not what Feedzai is typically brought in for.
What can Envoy do that Feedzai cannot?
Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default. Feedzai covers Real-time scoring, Rule and model hybrid, Case manager, Behavioural biometrics.

Answered from the vendors’ own pages

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.

Feedzai: Can Feedzai run on-premises?

Yes. On-premises and private cloud deployments are supported, which is why it appears in markets where transaction data cannot legally leave the country.

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.

Feedzai: Does it cover AML as well as fraud?

It does, but transaction monitoring is a separately licensed module. Assume two line items if you want both.

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.

Feedzai: How fast are decisions?

Designed for the authorisation window, typically tens of milliseconds. This is the constraint that rules out batch scoring architectures.

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.

Share

Related pages

More on Envoy

More on Feedzai

Keep looking

Other head to heads