Softwr

Developer Tools · head to head

Envoy vs Featurespace ARIC Risk Hub

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
Featurespace ARIC Risk Hub logo

Featurespace ARIC Risk Hub

Cybersecurity

Adaptive behavioural analytics for payment fraud and financial crime

From
On request
Free plan
No
Visit Featurespace ARIC Risk HubFull review

The short version

  • Envoy is free; Featurespace ARIC Risk Hub prices on request.
  • Only Envoy lists xDS dynamic configuration; only Featurespace ARIC Risk Hub lists adaptive behavioural analytics.
  • Where Featurespace ARIC Risk Hub falls short: pricing is not published and is volume-linked, which makes the cost of a growth year hard to forecast during a three year business case.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which Envoy and Featurespace ARIC Risk Hub actually diverge.

Attributes where Envoy and Featurespace ARIC Risk Hub differ
AttributeEnvoyFeaturespace ARIC Risk Hub
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 Featurespace ARIC Risk Hub

  • Adaptive behavioural analytics
  • Real time scoring
  • Automated model updates
  • APP scam detection
  • AML transaction monitoring
  • Rules alongside models

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 Featurespace ARIC Risk Hub
  • An edge or API gateway that needs per-route retry budgets, circuit breaking and outlier detection rather than round-robin proxyingnot Featurespace ARIC Risk Hub
  • Migrating traffic between service versions or between a monolith and its replacement, using weighted splits and shadow trafficnot Featurespace ARIC Risk Hub
  • 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 Featurespace ARIC Risk Hub

Featurespace ARIC Risk Hub

  • A UK bank exposed to mandatory reimbursement for authorised push payment scams and needing to intervene before the payment leavesnot Envoy
  • An acquirer scoring merchant transactions in real time to reduce chargeback exposure without raising decline ratesnot Envoy
  • A card issuer replacing a rules-only fraud engine whose false positive rate is driving genuine customer declinesnot Envoy
  • A payments processor that needs one behavioural engine serving both fraud and AML rather than two separate stacksnot 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

Featurespace ARIC Risk Hub

  • Visa now owns the vendor, so an institution buying scheme-neutral infrastructure, or one competing with Visa value added services, has a governance question that did not exist before December 2024
  • Pricing is not published and is volume-linked, which makes the cost of a growth year hard to forecast during a three year business case
  • Adaptive models are harder to explain to a regulator than deterministic rules, and model risk teams often demand parallel rule coverage that erodes the operational saving
  • Behavioural profiling needs history, so newly onboarded customers and low frequency accounts are scored with thin data and the detection lift is smallest exactly where fraud concentrates
  • Deployment into an existing payment path is an engineering project with latency budgets to hit, and banks with legacy core systems often find the integration, not the analytics, is the schedule risk

Pricing, plan by plan

Envoy

Free

No published plan breakdown. See the Envoy review.

Featurespace ARIC Risk Hub

On request
  • ARIC Risk HubOn request
    • Priced by transaction volume or protected accounts
    • Cloud or on premises deployment
    • Model tuning services quoted separately

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 Featurespace ARIC Risk Hub if

  • You need adaptive behavioural analytics.
  • You work on Web, Linux.
  • You also want real time scoring.
Featurespace ARIC Risk Hub review

Questions people ask

Is Envoy or Featurespace ARIC Risk Hub better?
Neither clearly leads. Envoy starts at Free and Featurespace ARIC Risk Hub at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Envoy or Featurespace ARIC Risk Hub?
Envoy has a free tier; the other does not. Paid plans start at Free for Envoy and On request for Featurespace ARIC Risk Hub.
Does Envoy or Featurespace ARIC Risk Hub run on more platforms?
Envoy runs on Web. Featurespace ARIC Risk Hub runs on Web, Linux.
Can I use Envoy for free?
Yes. Envoy has a free tier, so you can try it without paying. Featurespace ARIC Risk Hub 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 Featurespace ARIC Risk Hub is typically brought in for.
What can Envoy do that Featurespace ARIC Risk Hub cannot?
Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default. Featurespace ARIC Risk Hub covers Adaptive behavioural analytics, Real time scoring, Automated model updates, APP scam detection.

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.

Featurespace ARIC Risk Hub: Is Featurespace still sold as its own product?

Yes. ARIC Risk Hub continues to be sold under the Featurespace name, described as a Visa solution, and is available to non-Visa institutions.

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.

Featurespace ARIC Risk Hub: Does using it require being a Visa customer?

No. The platform is sold to banks, acquirers and processors regardless of scheme relationships, though the ownership is a reasonable governance consideration.

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.

Featurespace ARIC Risk Hub: Can it run on premises?

Yes. On premises deployment is supported, which matters for institutions with data residency constraints.

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 Featurespace ARIC Risk Hub

Keep looking

Other head to heads