Softwr

Developer Tools · head to head

Envoy vs Lithic

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

Lithic

APIs

API-first card issuing platform with direct Visa, Mastercard and Amex network connections

From
On request
Free plan
No

The short version

  • Envoy is free; Lithic prices on request.
  • Only Envoy lists xDS dynamic configuration; only Lithic lists direct network connections.
  • Where Lithic falls short: pricing is entirely undisclosed, so a company cannot compare total cost against Marqeta, Galileo or Highnote without a sales conversation.
  • Prices and features on this page were last checked on 20 November 2026.

How do Envoy and Lithic differ?

Envoy and Lithic differ on starting price (Free against On request), pricing model (Open-source against Quote) and free tier (Yes against No). Only the attributes on which Envoy and Lithic actually diverge.

Attributes where Envoy and Lithic differ
AttributeEnvoyLithic
Starting priceFreeOn request
Pricing modelOpen-sourceQuote
Free tierYesNo
PlatformsWebWeb, API
CategoryDeveloper ToolsAPIs

Which features does each one have?

They share no listed features; 8 appear only for Envoy and 6 only for Lithic. 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 Lithic

  • Direct network connections
  • Processor Client mode
  • Lithic Program Management
  • Card lifecycle APIs
  • Sandbox environment
  • Real-time authorization controls

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

Lithic

  • A fintech wanting direct Visa or Mastercard network access rather than routing through a third-party processornot Envoy
  • A company that already holds its own issuing licence and wants API access without full programme managementnot Envoy
  • A neobank or expense platform wanting Lithic to manage bank and network relationships end to endnot Envoy
  • A product team prototyping a card programme in sandbox before committing to a launchnot Envoy

Where do Envoy and Lithic fall 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

Lithic

  • Pricing is entirely undisclosed, so a company cannot compare total cost against Marqeta, Galileo or Highnote without a sales conversation
  • Choosing Processor Client mode still leaves the company responsible for holding its own issuing licence and managing the regulatory relationship, which is a substantial undertaking many teams underestimate
  • As with any card infrastructure provider, an outage or network issue at Lithic becomes a direct outage for every card programme built on it, and a customer has limited visibility into root cause during an incident
  • Building a card programme on API infrastructure requires real engineering investment; it is not a plug-and-play product for a non-technical team
  • Switching card infrastructure providers after launch is a major undertaking involving card reissuance and programme migration, so the initial choice carries lasting lock-in

How much do Envoy and Lithic cost?

Envoy is free to use; Lithic is priced on request. Plan by plan below, from each vendor's own pricing page.

Envoy

Free

No published plan breakdown. See the Envoy review.

Lithic

On request
  • LithicOn request
    • Volume and interchange-based pricing, not published
    • Separate Processor Client and Program Management pricing tracks
    • Custom quote required via sales

Which should you pick?

Choose Envoy if

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

Choose Lithic if

  • You need direct network connections.
  • You work on Web, API.
  • You also want processor client mode.

Questions people ask

Is Envoy or Lithic better?
Neither clearly leads. Envoy starts at Free and Lithic at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Envoy or Lithic?
Envoy has a free tier; the other does not. Paid plans start at Free for Envoy and On request for Lithic.
Does Envoy or Lithic run on more platforms?
Envoy runs on Web. Lithic runs on Web, API.
Can I use Envoy for free?
Yes. Envoy has a free tier, so you can try it without paying. Lithic 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 Lithic is typically brought in for.
What can Envoy do that Lithic cannot?
Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default. Lithic covers Direct network connections, Processor Client mode, Lithic Program Management, Card lifecycle APIs.

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.

Lithic: Does Lithic publish pricing?

No, pricing is volume-based and requires a sales conversation.

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.

Lithic: What is the difference between Processor Client and Program Management?

Processor Client suits companies with their own issuing licence and bank relationships; Program Management is for companies wanting Lithic to coordinate those relationships on their behalf.

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.

Lithic: Which networks does it connect to?

Visa, Mastercard and American Express directly.

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

Other head to heads