Developer Tools · head to head
Envoy vs Unit

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

Unit
APIs
Banking as a service platform for embedding deposit accounts, cards and payments, with a sponsor bank behind it
- From
- On request
- Free plan
- No
The short version
- Envoy is free; Unit prices on request.
- Only Envoy lists xDS dynamic configuration; only Unit lists deposit accounts.
- Prices and features on this page were last checked on 20 November 2026.
How do Envoy and Unit differ?
Envoy and Unit 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 Unit actually diverge.
Which features does each one have?
They share no listed features; 8 appear only for Envoy and 8 only for Unit. 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 Unit
- Deposit accounts
- Card issuing
- Payments
- White label components
- Compliance operations
- Lending
- Programme reporting
- Sandbox
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 Unit
- An edge or API gateway that needs per-route retry budgets, circuit breaking and outlier detection rather than round-robin proxyingnot Unit
- Migrating traffic between service versions or between a monolith and its replacement, using weighted splits and shadow trafficnot Unit
- 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 Unit
Unit
- A vertical SaaS platform for contractors that wants to hold customer funds and issue expense cards without pursuing a charternot Envoy
- A payroll or benefits platform embedding accounts so employees can be paid ahead of schedulenot Envoy
- A marketplace that wants seller balances to sit in real accounts under its own brand rather than as ledger entries at a processornot Envoy
- A company that needs interchange revenue from a card programme to make the unit economics of its core product worknot Envoy
Where do Envoy and Unit 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
Unit
- Your product depends on a sponsor bank you do not contract with directly, and 2024 showed what that means: Thread Bank received an FDIC enforcement action naming its banking as a service programmes and Blue Ridge Bank went under an OCC consent order and offboarded fintech partners
- Programme approval by the bank is a separate gate from signing with Unit, and it can add months and impose product restrictions that were not visible during the commercial conversation
- Compliance obligations are shared but the operational load lands on you, and platforms consistently underestimate the staffing needed for disputes, escalations and the bank ongoing oversight requests
- Pricing is unpublished and blends platform fees, per-account and per-transaction charges and interchange sharing, which makes it hard to model unit economics before you have volume and easy to be surprised by the minimum
- Migrating a live deposit programme to a different provider or bank is extremely disruptive because it involves moving customer accounts and card credentials, so switching costs are far higher than for ordinary software
How much do Envoy and Unit cost?
Envoy is free to use; Unit is priced on request. Plan by plan below, from each vendor's own pricing page.
Envoy
FreeNo published plan breakdown. See the Envoy review.
Unit
On request- Unit Banking as a ServiceOn request
- Platform fee plus per-account and per-transaction charges, quoted
- Interchange sharing arrangements negotiated per programme
- Minimum commitment typical
Which should you pick?
Choose Envoy if
- You need xds dynamic configuration.
- You want to start without paying.
- You also want protocol breadth.
Choose Unit if
- You need deposit accounts.
- You work on Web, iOS, Android.
- You also want card issuing.
Questions people ask
- Is Envoy or Unit better?
- Neither clearly leads. Envoy starts at Free and Unit at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Envoy or Unit?
- Envoy has a free tier; the other does not. Paid plans start at Free for Envoy and On request for Unit.
- Does Envoy or Unit run on more platforms?
- Envoy runs on Web. Unit runs on Web, iOS, Android.
- Can I use Envoy for free?
- Yes. Envoy has a free tier, so you can try it without paying. Unit 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 Unit is typically brought in for.
- What can Envoy do that Unit cannot?
- Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default. Unit covers Deposit accounts, Card issuing, Payments, White label components.
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.
Unit: Who actually holds the money?
A chartered partner bank, not Unit. Deposits sit at the sponsor bank and FDIC insurance flows from that bank, so its condition is your condition.
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.
Unit: What happened with Unit sponsor banks in 2024?
Thread Bank received an FDIC enforcement action that explicitly named its banking as a service and lending as a service programmes, and Blue Ridge Bank was under an OCC consent order from January 2024 and offboarded fintech partners. Blue Ridge exited the order in late 2025.
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.
Unit: What does Unit cost?
Not published. Expect a platform fee, per-account and per-transaction charges, an interchange share and a minimum commitment.
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.
Unit: Do we need our own compliance team?
Yes. Unit supplies tooling and the bank sets the rules, but disputes, escalations and evidence for bank oversight require named people on your side.
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
- 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
- Envoy vs Treasury Prime
- Envoy vs Synctera
- Envoy vs Solaris
- Envoy vs Increase
- Envoy vs Column
- Envoy vs Toqio
- Envoy vs Weavr
- Envoy vs Thredd
- Envoy vs Lithic
- Envoy vs Swan
- Envoy vs Vodeno
- Envoy vs Griffin
- Envoy vs Bud Financial
- Envoy vs Dwolla
- Envoy vs Liveblocks
- Envoy vs Parse Server
- Envoy vs Payload CMS
- Envoy vs PubNub
- Unit vs Istio
- Unit vs Ona (formerly Gitpod)
- Unit vs Spacelift
- Unit vs Jenkins
- Unit vs Hookdeck
- Unit vs Atlantis
- Unit vs Restate
- Unit vs Turborepo
- Unit vs Helix
- Unit vs Git
- Unit vs Okteto
- Unit vs StackBlitz
- Unit vs CodeSandbox
- Unit vs Cody
- Unit vs Depot
- Unit vs Neovim
- Unit vs Azure DevOps
- Unit vs Bitbucket
- Unit vs Treasury Prime
- Unit vs Synctera
- Unit vs Solaris
- Unit vs Increase
- Unit vs Column
- Unit vs Toqio
- Unit vs Weavr
- Unit vs Thredd
- Unit vs Lithic
- Unit vs Swan
- Unit vs Vodeno
- Unit vs Griffin
- Unit vs Bud Financial
- Unit vs Dwolla
- Unit vs Liveblocks
- Unit vs Parse Server
- Unit vs Payload CMS
- Unit vs PubNub
