Developer Tools · head to head
Envoy vs SoapUI

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

SoapUI
Testing
Open source API testing tool for REST, SOAP and GraphQL, from SmartBear
- From
- Free
- Free plan
- Yes
The short version
- Both are free.
- Only Envoy lists xDS dynamic configuration; only SoapUI lists REST, SOAP, GraphQL and JMS API testing.
- Where SoapUI falls short: open source edition has no data-driven testing or native SDLC integrations.
- Prices and features on this page were last checked on 20 November 2026.
How do Envoy and SoapUI differ?
Envoy and SoapUI differ on platforms and category (Developer Tools against Testing). Only the attributes on which Envoy and SoapUI actually diverge.
Identical on both: starting price (Free), pricing model (Open-source), free tier (Yes).
Which features does each one have?
They share no listed features; 8 appear only for Envoy and 8 only for SoapUI. 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 SoapUI
- REST, SOAP, GraphQL and JMS API testing
- Groovy and JavaScript scripting
- Functional test suites with assertions
- Open source edition under the EUPL
- ReadyAPI edition with security and performance testing
- Service virtualisation in ReadyAPI
- Data-driven testing in ReadyAPI
- CI integrations with Jenkins, TeamCity and Azure DevOps in ReadyAPI
What is each one used for?
SoapUI is most often brought in for functional testing of SOAP web services. 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 SoapUI
- An edge or API gateway that needs per-route retry budgets, circuit breaking and outlier detection rather than round-robin proxyingnot SoapUI
- Migrating traffic between service versions or between a monolith and its replacement, using weighted splits and shadow trafficnot SoapUI
- 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 SoapUI
SoapUI
- Functional testing of SOAP web servicesnot Envoy
- REST and GraphQL API regression checksnot Envoy
- Scripted API tests in Groovynot Envoy
- Evaluating ReadyAPI before a team purchasenot Envoy
Where do Envoy and SoapUI fall short?
SoapUI's most cited limit: open source edition has no data-driven testing or native SDLC integrations. 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
SoapUI
- Open source edition has no data-driven testing or native SDLC integrations
- Test refactoring and result comparison are manual in the open source edition
- Security, performance and virtualisation testing require the paid ReadyAPI edition
- ReadyAPI prices are not listed on the vendor pages, so cost needs a quote or cart visit
How much do Envoy and SoapUI cost?
Envoy is free to use; SoapUI is free to use. Plan by plan below, from each vendor's own pricing page.
Envoy
FreeNo published plan breakdown. See the Envoy review.
SoapUI
FreeNo published plan breakdown. See the SoapUI review.
Which should you pick?
Choose Envoy if
- You need xds dynamic configuration.
- You want to start without paying.
- You also want protocol breadth.
Choose SoapUI if
- You need rest, soap, graphql and jms api testing.
- You want to start without paying.
- You work on Windows, macOS, Linux.
- You also want groovy and javascript scripting.
Questions people ask
- Is Envoy or SoapUI better?
- Neither clearly leads. Envoy starts at Free and SoapUI at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Envoy or SoapUI?
- Envoy starts at Free and SoapUI at Free.
- Does Envoy or SoapUI run on more platforms?
- Envoy runs on Web. SoapUI runs on Windows, macOS, Linux.
- Can I use Envoy for free?
- Both have a free tier, so you can try either at no cost before committing.
- 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 SoapUI is typically brought in for.
- What can Envoy do that SoapUI cannot?
- Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default. SoapUI covers REST, SOAP, GraphQL and JMS API testing, Groovy and JavaScript scripting, Functional test suites with assertions, Open source edition under the EUPL.
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.
SoapUI: Is SoapUI free?
The open source edition is free and licensed under the European Union Public License. The commercial ReadyAPI edition is paid, and the vendor offers a 14-day free trial.
SourceEnvoy: 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.
SoapUI: What protocols does it support?
The open source edition supports REST, SOAP, GraphQL and JMS. ReadyAPI adds XML-RPC, MQTT and other protocols.
SourceEnvoy: 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.
SoapUI: Who makes SoapUI?
SmartBear Software develops it. The project was first released on SourceForge in 2005 and SmartBear acquired its developer Eviware in 2011.
SourceEnvoy: 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.
SoapUI: Which operating systems does it run on?
It is written in Java and Groovy, so it runs across operating systems that support Java. It also has plugins for the IntelliJ IDEA, Eclipse and NetBeans IDEs.
SourceEnvoy: 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 Insomnia
- Envoy vs Testsigma
- Envoy vs Playwright
- Envoy vs CircleCI
- Envoy vs BrowserStack
- Envoy vs mabl
- Envoy vs TestRail
- Envoy vs Qase
- Envoy vs Zephyr Scale
- Envoy vs Ranorex
- Envoy vs JUnit
- Envoy vs Cucumber
- Envoy vs Jest
- Envoy vs TestNG
- Envoy vs Tricentis Tosca
- Envoy vs Eppo
- Envoy vs k6
- Envoy vs CloudBees Smart Tests
- SoapUI vs Istio
- SoapUI vs Ona (formerly Gitpod)
- SoapUI vs Spacelift
- SoapUI vs Jenkins
- SoapUI vs Hookdeck
- SoapUI vs Atlantis
- SoapUI vs Restate
- SoapUI vs Turborepo
- SoapUI vs Helix
- SoapUI vs Git
- SoapUI vs Okteto
- SoapUI vs StackBlitz
- SoapUI vs CodeSandbox
- SoapUI vs Cody
- SoapUI vs Depot
- SoapUI vs Neovim
- SoapUI vs Azure DevOps
- SoapUI vs Bitbucket
- SoapUI vs Insomnia
- SoapUI vs Testsigma
- SoapUI vs Playwright
- SoapUI vs CircleCI
- SoapUI vs BrowserStack
- SoapUI vs mabl
- SoapUI vs TestRail
- SoapUI vs Qase
- SoapUI vs Zephyr Scale
- SoapUI vs Ranorex
- SoapUI vs JUnit
- SoapUI vs Cucumber
- SoapUI vs Jest
- SoapUI vs TestNG
- SoapUI vs Tricentis Tosca
- SoapUI vs Eppo
- SoapUI vs k6
- SoapUI vs CloudBees Smart Tests
