Developer Tools · head to head
Cortex vs SoapUI

Cortex
Developer Tools
Internal developer portal that scores service ownership and maturity rather than just cataloguing services
- From
- On request
- Free plan
- No

SoapUI
Testing
Open source API testing tool for REST, SOAP and GraphQL, from SmartBear
- From
- Free
- Free plan
- Yes
The short version
- SoapUI is free; Cortex prices on request.
- Only Cortex lists query language; 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 Cortex and SoapUI differ?
Cortex and SoapUI 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 Cortex and SoapUI actually diverge.
Which features does each one have?
They share no listed features; 8 appear only for Cortex 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 Cortex
- Service catalogue
- Scorecards
- Initiatives
- Self-service templates
- Query language
- Eng intelligence
- Integrations layer
- On-call and ownership mapping
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.
Cortex
- A platform team that needs to prove to leadership how far a Kubernetes or framework migration has actually progressed across hundreds of servicesnot SoapUI
- An organisation where ownership of production services is genuinely unknown after reorganisations or acquisitionsnot SoapUI
- Enforcing production readiness standards on new services at creation time rather than at incident reviewnot SoapUI
- Replacing a self-hosted Backstage that is consuming a full-time engineer or two just to stay upgradednot SoapUI
SoapUI
- Functional testing of SOAP web servicesnot Cortex
- REST and GraphQL API regression checksnot Cortex
- Scripted API tests in Groovynot Cortex
- Evaluating ReadyAPI before a team purchasenot Cortex
Where do Cortex 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.
Cortex
- Pricing is quote only, so a platform team cannot build a business case or compare against the true cost of self-hosted Backstage without entering a sales cycle first
- The catalogue is only as accurate as the metadata you supply, so an organisation with inconsistent repository conventions spends its first quarter cleaning data before any scorecard means anything
- Scorecards create political friction: publishing a per-team grade turns an engineering standard into a performance metric, and teams will game the rules rather than fix the underlying issue
- It is closed source and hosted, so organisations with strict data residency or air-gap requirements have limited options compared with running Backstage themselves
- Value scales with organisation size, so a company with fifty engineers and thirty services will find the catalogue tells them nothing they did not already know while still paying an enterprise contract
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 Cortex and SoapUI cost?
Cortex is priced on request; SoapUI is free to use. Plan by plan below, from each vendor's own pricing page.
Cortex
On request- CortexOn request
- Service catalogue and ownership mapping
- Scorecards and initiatives
- Self-service templates
SoapUI
FreeNo published plan breakdown. See the SoapUI review.
Which should you pick?
Choose Cortex if
- You need service catalogue.
- You work on Web, API.
- You also want scorecards.
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 Cortex or SoapUI better?
- Neither clearly leads. Cortex starts at On request and SoapUI at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Cortex or SoapUI?
- SoapUI has a free tier; the other does not. Paid plans start at On request for Cortex and Free for SoapUI.
- Does Cortex or SoapUI run on more platforms?
- Cortex runs on Web, API. SoapUI runs on Windows, macOS, Linux.
- Can I use SoapUI for free?
- Yes. SoapUI has a free tier, so you can try it without paying. Cortex starts at On request.
- What is Cortex best used for?
- Cortex is most often used for a platform team that needs to prove to leadership how far a kubernetes or framework migration has actually progressed across hundreds of services, an organisation where ownership of production services is genuinely unknown after reorganisations or acquisitions, enforcing production readiness standards on new services at creation time rather than at incident review, replacing a self-hosted backstage that is consuming a full-time engineer or two just to stay upgraded. Of those, a platform team that needs to prove to leadership how far a kubernetes or framework migration has actually progressed across hundreds of services and an organisation where ownership of production services is genuinely unknown after reorganisations or acquisitions are not what SoapUI is typically brought in for.
- What can Cortex do that SoapUI cannot?
- Cortex covers Service catalogue, Scorecards, Initiatives, Self-service templates. 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
Cortex: How is Cortex different from Backstage?
Backstage is an open source framework you build and staff. Cortex is a hosted product with scorecards and initiatives out of the box and no platform team required to keep it running.
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.
SourceCortex: Is pricing published?
No. Cortex requires a sales conversation and prepares a custom proposal.
SoapUI: What protocols does it support?
The open source edition supports REST, SOAP, GraphQL and JMS. ReadyAPI adds XML-RPC, MQTT and other protocols.
SourceCortex: Can it self-host?
It is offered as a hosted product; on-premise arrangements are handled through sales rather than published.
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.
SourceCortex: What is the main adoption risk?
Bad or missing service metadata. The catalogue and every scorecard on top of it inherit whatever quality your repositories already have.
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.
SourceRelated pages
Other head to heads
- Cortex vs Backstage
- Cortex vs OpsLevel
- Cortex vs GitHub
- Cortex vs Spacelift
- Cortex vs Earthly
- Cortex vs Atlantis
- Cortex vs SonarQube
- Cortex vs Envoy
- Cortex vs Depot
- Cortex vs Istio
- Cortex vs Nix
- Cortex vs Buildkite
- Cortex vs Azure DevOps
- Cortex vs Bitbucket
- Cortex vs Daytona
- Cortex vs Helix
- Cortex vs Nx Cloud
- Cortex vs Pants Build
- Cortex vs Insomnia
- Cortex vs Testsigma
- Cortex vs Playwright
- Cortex vs CircleCI
- Cortex vs BrowserStack
- Cortex vs mabl
- Cortex vs TestRail
- Cortex vs Qase
- Cortex vs Zephyr Scale
- Cortex vs Ranorex
- Cortex vs JUnit
- Cortex vs Cucumber
- Cortex vs Jest
- Cortex vs TestNG
- Cortex vs Tricentis Tosca
- Cortex vs Eppo
- Cortex vs k6
- Cortex vs CloudBees Smart Tests
- SoapUI vs Backstage
- SoapUI vs OpsLevel
- SoapUI vs GitHub
- SoapUI vs Spacelift
- SoapUI vs Earthly
- SoapUI vs Atlantis
- SoapUI vs SonarQube
- SoapUI vs Envoy
- SoapUI vs Depot
- SoapUI vs Istio
- SoapUI vs Nix
- SoapUI vs Buildkite
- SoapUI vs Azure DevOps
- SoapUI vs Bitbucket
- SoapUI vs Daytona
- SoapUI vs Helix
- SoapUI vs Nx Cloud
- SoapUI vs Pants Build
- 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
