Softwr

Developer Tools · head to head

Envoy vs ThetaRay

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
ThetaRay logo

ThetaRay

Cybersecurity

Unsupervised AI transaction monitoring for cross-border and correspondent banking

From
On request
Free plan
No
Visit ThetaRayFull review

The short version

  • Envoy is free; ThetaRay prices on request.
  • Only Envoy lists xDS dynamic configuration; only ThetaRay lists cross-border focus.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which Envoy and ThetaRay actually diverge.

Attributes where Envoy and ThetaRay differ
AttributeEnvoyThetaRay
Starting priceFreeOn request
Pricing modelOpen-sourceQuote
Free tierYesNo
CategoryDeveloper ToolsCybersecurity

Identical on both: platforms (Web).

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 ThetaRay

  • Unsupervised detection
  • Cross-border focus
  • Sanctions screening
  • Alert triage
  • Customer risk scoring
  • Cloud native

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

ThetaRay

  • A correspondent bank that cannot see the ultimate originator and needs behavioural signals rather than counterparty listsnot Envoy
  • A cross-border payments fintech whose rules engine produces more alerts than its compliance team can clearnot Envoy
  • A bank under a regulatory consent order needing demonstrable improvement in detection within a fixed periodnot Envoy
  • A payment institution entering a high-risk corridor where existing thresholds were calibrated on domestic trafficnot 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

ThetaRay

  • Unsupervised models are harder to justify to an examiner than explicit rules, and some regulators still expect documented threshold logic, which can force you to run both systems
  • The alert reduction claim depends heavily on your data, so a parallel run is essential and adds months and cost before you can decommission the incumbent
  • Coverage is strongest in cross-border and correspondent flows; institutions whose risk is domestic retail fraud will find the fit weaker than a general-purpose monitoring platform
  • It is a smaller vendor than the incumbents, so integration connectors into legacy core banking systems are often bespoke work rather than a supported adapter
  • Model retraining and tuning are vendor-led, which means changing detection behaviour is a support conversation rather than something your own analysts can do that afternoon

Pricing, plan by plan

Envoy

Free

No published plan breakdown. See the Envoy review.

ThetaRay

On request
  • ThetaRay SonarOn request
    • Priced by monitored transaction volume and number of monitored entities
    • SaaS on Azure with regional data residency options
    • Parallel run and model tuning included in onboarding

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

  • You need unsupervised detection.
  • You also want cross-border focus.
ThetaRay review

Questions people ask

Is Envoy or ThetaRay better?
Neither clearly leads. Envoy starts at Free and ThetaRay at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Envoy or ThetaRay?
Envoy has a free tier; the other does not. Paid plans start at Free for Envoy and On request for ThetaRay.
Does Envoy or ThetaRay run on more platforms?
Both run on Web, so platform support will not decide this one for you.
Can I use Envoy for free?
Yes. Envoy has a free tier, so you can try it without paying. ThetaRay 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 ThetaRay is typically brought in for.
What can Envoy do that ThetaRay cannot?
Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default. ThetaRay covers Unsupervised detection, Cross-border focus, Sanctions screening, Alert triage.

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.

ThetaRay: Does it replace a rules engine entirely?

Rarely on day one. Most institutions run it alongside existing rules during a parallel period, and some keep specific regulator-mandated rules permanently.

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.

ThetaRay: Where is the data processed?

SaaS runs on Microsoft Azure with regional deployment options, which is the mechanism for meeting data residency conditions in regulated markets.

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.

ThetaRay: Is sanctions screening included?

Screening is available on the same platform but licensed as part of the commercial package rather than bundled by default. Confirm it is in your quote.

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 ThetaRay

Keep looking

Other head to heads