Developer Tools · head to head
Envoy vs Highnote

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

Highnote
APIs
Card issuing, acquiring and ledger on one platform for embedded payments
- From
- On request
- Free plan
- No
The short version
- Envoy is free; Highnote prices on request.
- Only Envoy lists xDS dynamic configuration; only Highnote lists card issuing.
- Prices and features on this page were last checked on 20 November 2026.
How do Envoy and Highnote differ?
Envoy and Highnote 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 Highnote actually diverge.
Which features does each one have?
They share no listed features; 8 appear only for Envoy and 8 only for Highnote. 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 Highnote
- Card issuing
- Merchant acquiring
- Unified ledger
- Spend controls
- GraphQL API
- Programme management
- Dispute handling
- Real time authorisation webhooks
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 Highnote
- An edge or API gateway that needs per-route retry budgets, circuit breaking and outlier detection rather than round-robin proxyingnot Highnote
- Migrating traffic between service versions or between a monolith and its replacement, using weighted splits and shadow trafficnot Highnote
- 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 Highnote
Highnote
- A marketplace that both pays out to sellers and issues them spend cards, wanting one settlement ledgernot Envoy
- A vertical software company embedding card acceptance and card issuing for the same customer basenot Envoy
- A fintech launching a commercial charge card programme with custom authorisation logicnot Envoy
- A platform replacing separate issuing and acquiring vendors to remove cross system reconciliationnot Envoy
Where do Envoy and Highnote 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
Highnote
- Card issuing requires a sponsor bank, and that bank sets programme approval, compliance obligations and often minimum volumes, so a small programme can be rejected regardless of technical fit
- Pricing is entirely quoted, including platform fees, per active card charges and monthly minimums that do not appear on the website, so the true cost per card is only visible late in a sales process
- Interchange sharing is the real revenue model for most customers, and the split is negotiated, capped for regulated debit under the Durbin amendment and sensitive to your spend mix, so revenue projections built on headline interchange rates overstate income
- Running issuing and acquiring with one provider concentrates risk: an outage or a compliance action affects both money in and money out at the same time
- Highnote is a younger company than the established issuer processors, so long term programme continuity, network certifications in new geographies and international coverage are thinner than the incumbent alternatives
How much do Envoy and Highnote cost?
Envoy is free to use; Highnote is priced on request. Plan by plan below, from each vendor's own pricing page.
Envoy
FreeNo published plan breakdown. See the Envoy review.
Highnote
On request- Highnote platformOn request
- Quoted per programme with no public rate card
- Requires a sponsor bank relationship for card issuing
- Interchange sharing terms negotiated per programme
Which should you pick?
Choose Envoy if
- You need xds dynamic configuration.
- You want to start without paying.
- You also want protocol breadth.
Choose Highnote if
- You need card issuing.
- You work on Web, API.
- You also want merchant acquiring.
Questions people ask
- Is Envoy or Highnote better?
- Neither clearly leads. Envoy starts at Free and Highnote at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Envoy or Highnote?
- Envoy has a free tier; the other does not. Paid plans start at Free for Envoy and On request for Highnote.
- Does Envoy or Highnote run on more platforms?
- Envoy runs on Web. Highnote runs on Web, API.
- Can I use Envoy for free?
- Yes. Envoy has a free tier, so you can try it without paying. Highnote 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 Highnote is typically brought in for.
- What can Envoy do that Highnote cannot?
- Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default. Highnote covers Card issuing, Merchant acquiring, Unified ledger, Spend controls.
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.
Highnote: Do I need a sponsor bank?
Yes for card issuing in the United States. Highnote is a processor and programme platform, not a bank, and the sponsor bank sets approval and compliance terms.
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.
Highnote: How do customers make money on a card programme?
Mostly interchange sharing. Negotiate the split explicitly and model it against your actual spend mix, since regulated debit interchange is capped.
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.
Highnote: Can Highnote handle both accepting and issuing payments?
Yes since its 2025 acquiring launch, on the same ledger, which is its main structural differentiator.
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.
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 Marqeta
- Envoy vs Lithic
- Envoy vs Enfuce
- Envoy vs Paymentology
- Envoy vs Episode Six
- Envoy vs Toqio
- Envoy vs i2c
- Envoy vs Thredd
- Envoy vs Unit
- Envoy vs Synctera
- Envoy vs Weavr
- Envoy vs Tribe Payments
- Envoy vs Strapi
- Envoy vs Thunder Client
- Envoy vs Akoya
- Envoy vs Convoy
- Envoy vs Enable Banking
- Envoy vs Fintecture
- Highnote vs Istio
- Highnote vs Ona (formerly Gitpod)
- Highnote vs Spacelift
- Highnote vs Jenkins
- Highnote vs Hookdeck
- Highnote vs Atlantis
- Highnote vs Restate
- Highnote vs Turborepo
- Highnote vs Helix
- Highnote vs Git
- Highnote vs Okteto
- Highnote vs StackBlitz
- Highnote vs CodeSandbox
- Highnote vs Cody
- Highnote vs Depot
- Highnote vs Neovim
- Highnote vs Azure DevOps
- Highnote vs Bitbucket
- Highnote vs Marqeta
- Highnote vs Lithic
- Highnote vs Enfuce
- Highnote vs Paymentology
- Highnote vs Episode Six
- Highnote vs Toqio
- Highnote vs i2c
- Highnote vs Thredd
- Highnote vs Unit
- Highnote vs Synctera
- Highnote vs Weavr
- Highnote vs Tribe Payments
- Highnote vs Strapi
- Highnote vs Thunder Client
- Highnote vs Akoya
- Highnote vs Convoy
- Highnote vs Enable Banking
- Highnote vs Fintecture
