APIs · head to head
Dwolla vs Envoy

Dwolla
APIs
Account to account payment API for ACH, RTP and FedNow with pay by bank and instant payment routing
- From
- On request
- Free plan
- No

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
The short version
- Dwolla is a long-running US bank payments API.
- Envoy is free; Dwolla prices on request.
- Only Dwolla lists ACH transfers; only Envoy lists xDS dynamic configuration.
- Prices and features on this page were last checked on 20 November 2026.
How do Dwolla and Envoy differ?
Dwolla and Envoy differ on starting price (On request against Free), pricing model (Quote against Open-source) and free tier (No against Yes). Only the attributes on which Dwolla and Envoy actually diverge.
Identical on both: platforms (Web).
Not yet recorded: founded for Envoy.
Which features does each one have?
They share no listed features; 8 appear only for Dwolla and 8 only for Envoy. 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 Dwolla
- ACH transfers
- Instant payments
- Rail orchestration
- Bank account verification
- Dwolla Balance
- Webhooks and reconciliation
- Pay by bank
- White label flows
Only in Envoy
- xDS dynamic configuration
- Protocol breadth
- Filter chain architecture
- Observability by default
- Outlier detection
- Traffic shaping
- mTLS termination and origination
- Hot restart
What is each one used for?
The jobs each tool is most often brought in to do.
Dwolla
- An insurance or lending platform disbursing funds to customer bank accounts where card payout fees would destroy the marginnot Envoy
- A B2B marketplace collecting large invoice payments by bank transfer rather than paying interchange on cardsnot Envoy
- A payroll or gig platform that needs to pay workers instantly and wants the rail chosen automatically by receiving bank capabilitynot Envoy
- A property management system collecting rent by ACH with verified bank accounts and reliable return handlingnot Envoy
Envoy
- Acting as the data plane under a service mesh or Gateway API implementation, which is how the overwhelming majority of deployments use itnot Dwolla
- An edge or API gateway that needs per-route retry budgets, circuit breaking and outlier detection rather than round-robin proxyingnot Dwolla
- Migrating traffic between service versions or between a monolith and its replacement, using weighted splits and shadow trafficnot Dwolla
- 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 Dwolla
Where do Dwolla and Envoy fall short?
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Dwolla
- Nothing is published: there are no per-transaction rates, no platform fee and no minimum on the pricing page, so every buyer negotiates blind and small platforms have no way to sanity check what they are quoted
- It is payments only, with no deposit accounts, card issuing or general ledger, so companies embedding financial products need at least one further vendor and the reconciliation between them
- Instant payment reach depends on the receiving institution supporting RTP or FedNow, so a meaningful share of payouts still fall back to ACH timing regardless of what the API can do
- ACH returns and administrative returns remain your operational problem, and platforms new to bank rails routinely underestimate the customer support load that failed debits generate
- Access to instant rails runs through Dwolla banking partner, which reintroduces a bank dependency into a product that otherwise avoids sponsor bank programme risk
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
How much do Dwolla and Envoy cost?
Dwolla is priced on request; Envoy is free to use. Plan by plan below, from each vendor's own pricing page.
Dwolla
On request- Dwolla Payment APIOn request
- Custom pricing built around transaction volume, rails used and integration needs
- No published per-transaction rates or platform fees
- Volume based plans for platforms and enterprises
Envoy
FreeNo published plan breakdown. See the Envoy review.
Which should you pick?
Choose Envoy if
- You need xds dynamic configuration.
- You want to start without paying.
- You also want protocol breadth.
Questions people ask
- Is Dwolla or Envoy better?
- Neither clearly leads. Dwolla starts at On request and Envoy at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Dwolla or Envoy?
- Envoy has a free tier; the other does not. Paid plans start at On request for Dwolla and Free for Envoy.
- Does Dwolla or Envoy 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. Dwolla starts at On request.
- What is Dwolla best used for?
- Dwolla is most often used for an insurance or lending platform disbursing funds to customer bank accounts where card payout fees would destroy the margin, a b2b marketplace collecting large invoice payments by bank transfer rather than paying interchange on cards, a payroll or gig platform that needs to pay workers instantly and wants the rail chosen automatically by receiving bank capability, a property management system collecting rent by ach with verified bank accounts and reliable return handling. Of those, an insurance or lending platform disbursing funds to customer bank accounts where card payout fees would destroy the margin and a b2b marketplace collecting large invoice payments by bank transfer rather than paying interchange on cards are not what Envoy is typically brought in for.
- What can Dwolla do that Envoy cannot?
- Dwolla covers ACH transfers, Instant payments, Rail orchestration, Bank account verification. Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default.
Answered from the vendors’ own pages
Dwolla: What does Dwolla cost?
It does not publish anything. Pricing is custom and built around volume, rails and integration. Establish the monthly platform fee and any minimum before negotiating per-transaction rates.
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.
Dwolla: Does it support instant payments?
Yes, through both the RTP network and the FedNow Service, with automatic selection based on the receiving bank. Where neither is supported, payments fall back to ACH.
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.
Dwolla: Is Dwolla a bank?
No. It is a payments platform that works through banking partners. It does not offer deposit accounts or card issuing.
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.
Dwolla: How does bank account verification work?
Either instantly through open banking connections or by micro-deposit verification, which takes a day or two but works where instant linking fails.
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
- Dwolla vs Moov
- Dwolla vs Increase
- Dwolla vs Sila
- Dwolla vs Astra
- Dwolla vs Method Financial
- Dwolla vs Trustly
- Dwolla vs Volt
- Dwolla vs TrueLayer
- Dwolla vs Yapily
- Dwolla vs Tink
- Dwolla vs Token.io
- Dwolla vs Zimpler
- Dwolla vs Boomi API Management
- Dwolla vs Fintech Farm
- Dwolla vs Formance
- Dwolla vs GraphQL Playground
- Dwolla vs IBM API Connect
- Dwolla vs Janus Gateway
- Dwolla vs Istio
- Dwolla vs Ona (formerly Gitpod)
- Dwolla vs Spacelift
- Dwolla vs Jenkins
- Dwolla vs Hookdeck
- Dwolla vs Atlantis
- Dwolla vs Restate
- Dwolla vs Turborepo
- Dwolla vs Helix
- Dwolla vs Git
- Dwolla vs Okteto
- Dwolla vs StackBlitz
- Dwolla vs CodeSandbox
- Dwolla vs Cody
- Dwolla vs Depot
- Dwolla vs Neovim
- Dwolla vs Azure DevOps
- Dwolla vs Bitbucket
- Envoy vs Moov
- Envoy vs Increase
- Envoy vs Sila
- Envoy vs Astra
- Envoy vs Method Financial
- Envoy vs Trustly
- Envoy vs Volt
- Envoy vs TrueLayer
- Envoy vs Yapily
- Envoy vs Tink
- Envoy vs Token.io
- Envoy vs Zimpler
- Envoy vs Boomi API Management
- Envoy vs Fintech Farm
- Envoy vs Formance
- Envoy vs GraphQL Playground
- Envoy vs IBM API Connect
- Envoy vs Janus Gateway
- 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
