Softwr

Developer Tools · head to head

Envoy vs Trustly

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

Trustly

APIs

Pay-by-bank payments network, majority-owned by private equity firm Nordic Capital

From
On request
Free plan
No

The short version

  • Envoy is free; Trustly prices on request.
  • Only Envoy lists xDS dynamic configuration; only Trustly lists pay by bank checkout.
  • Where Trustly falls short: the 1.15 to 3.15% merchant fee range is not a single published rate, so a merchant cannot know its actual cost without a sales negotiation.
  • Prices and features on this page were last checked on 20 November 2026.

How do Envoy and Trustly differ?

Envoy and Trustly 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 Trustly actually diverge.

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

Not yet recorded: founded for Envoy.

Which features does each one have?

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

  • Pay by bank checkout
  • Instant refunds
  • Verified payouts
  • Multi-market bank connectivity
  • Merchant dashboard and reconciliation
  • Fraud and risk tooling

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

Trustly

  • An e-commerce merchant wanting a lower-cost alternative or complement to card payment acceptancenot Envoy
  • A gaming or gambling operator needing verified, instant payouts to players' bank accountsnot Envoy
  • A merchant wanting instant refunds processed directly to a customer's bank account rather than card reversal delaysnot Envoy
  • A business in a market with strong open banking adoption wanting pay-by-bank as a checkout optionnot Envoy

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

Trustly

  • It is majority-owned by Nordic Capital, a private equity firm, so its long-term roadmap is ultimately oriented toward an eventual sale or IPO rather than indefinite independent operation
  • Consumer familiarity with paying by bank transfer still lags card payments in most markets, so merchants typically see it used as a secondary option rather than a full card replacement
  • The 1.15 to 3.15% merchant fee range is not a single published rate, so a merchant cannot know its actual cost without a sales negotiation
  • As with all open banking-dependent payment methods, reliability depends on the consistency of the underlying banks' own APIs, which Trustly does not control
  • Its verified payout functionality is heavily used in gaming and gambling, a sector with additional regulatory scrutiny, which is worth factoring in when evaluating vendor risk exposure by association

How much do Envoy and Trustly cost?

Envoy is free to use; Trustly 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.

Trustly

On request
  • TrustlyOn request
    • Typical merchant cost of 1.15% to 3.15% depending on volume and market
    • Exact rate negotiated per merchant, not published as a flat card

Which should you pick?

Choose Envoy if

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

Choose Trustly if

  • You need pay by bank checkout.
  • You work on Web, API.
  • You also want instant refunds.

Questions people ask

Is Envoy or Trustly better?
Neither clearly leads. Envoy starts at Free and Trustly at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Envoy or Trustly?
Envoy has a free tier; the other does not. Paid plans start at Free for Envoy and On request for Trustly.
Does Envoy or Trustly run on more platforms?
Envoy runs on Web. Trustly runs on Web, API.
Can I use Envoy for free?
Yes. Envoy has a free tier, so you can try it without paying. Trustly 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 Trustly is typically brought in for.
What can Envoy do that Trustly cannot?
Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default. Trustly covers Pay by bank checkout, Instant refunds, Verified payouts, Multi-market bank connectivity.

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.

Trustly: Who owns Trustly?

Nordic Capital, a private equity firm, holds a 51.1% majority stake; Alfven & Didrikson and BlackRock hold smaller stakes.

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.

Trustly: Is Trustly going public?

It has discussed an IPO but as of its most recent comments said one remained at least a year away.

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.

Trustly: What does it typically cost a merchant?

Roughly 1.15% to 3.15% of transaction value depending on volume and market, negotiated per merchant.

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