Automation Integration · head to head
Cyclr vs SoapUI

Cyclr
Automation Integration
Embedded integration platform that SaaS vendors ship inside their own product
- From
- $1595/month
- 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; Cyclr starts at $1595/mo.
- Only Cyclr lists white-label integration UI; 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 Cyclr and SoapUI differ?
Cyclr and SoapUI differ on starting price ($1595/month against Free), pricing model and free tier (No against Yes). Only the attributes on which Cyclr and SoapUI actually diverge.
Not yet recorded: founded for SoapUI.
Which features does each one have?
They share no listed features; 8 appear only for Cyclr 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 Cyclr
- White-label integration UI
- Connector library
- Workflow builder
- Custom connectors
- Regional hosting
- MCP server offering
- Usage metering
- Templates
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.
Cyclr
- A mid-market SaaS vendor losing deals because prospects ask for a CRM integration it has not builtnot SoapUI
- A product team that would rather ship an integration marketplace this quarter than hire two engineers to maintain connectorsnot SoapUI
- A European software company that needs its customers' integration data processed inside the EU for procurement reasonsnot SoapUI
- A vendor whose customers each want a slightly different variation of the same integration and cannot be served by one hard-coded connectornot SoapUI
SoapUI
- Functional testing of SOAP web servicesnot Cyclr
- REST and GraphQL API regression checksnot Cyclr
- Scripted API tests in Groovynot Cyclr
- Evaluating ReadyAPI before a team purchasenot Cyclr
Where do Cyclr 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.
Cyclr
- Entry pricing of 1,595 US dollars a month for one connector and 100,000 API calls means small vendors will find building two or three integrations in-house genuinely cheaper, and Cyclr only pays off past a certain integration count
- Connectors and API calls are metered separately, so a successful integration marketplace pushes you up tiers as your customers adopt it, meaning the cost rises with usage rather than with the revenue that usage generates
- Custom connectors to APIs outside the library are your work to build and maintain, so the promise of not building integrations only holds for applications Cyclr already covers
- Debugging is harder when the integration runs in a third-party runtime, because your support team sees a failed workflow rather than an HTTP response and has to escalate to Cyclr for anything non-obvious
- Deep embedding creates real switching cost: your customers' live integrations run on Cyclr, so migrating later means recreating every customer workflow, which in practice means you rarely leave
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 Cyclr and SoapUI cost?
Cyclr starts at $1595/mo; SoapUI is free to use. Plan by plan below, from each vendor's own pricing page.
Cyclr
$1595/month- PAYG$1,595/mo
- 100,000 API calls included
- 1 connector included
- Unlimited integrations and users
- Growth$2,595/mo
- 1,000,000 API calls included
- 10 connectors included
- Everything in PAYG
- Scale$7,195/mo
- 5,000,000 API calls included
- Unlimited connectors
- Everything in Growth
- Private CloudOn request
- Dedicated hosting in US, UK or EU
- Configurable processing and runtime
- Quoted pricing
SoapUI
FreeNo published plan breakdown. See the SoapUI review.
Which should you pick?
Choose Cyclr if
- You need white-label integration ui.
- You work on Web, API.
- You also want connector library.
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 Cyclr or SoapUI better?
- Neither clearly leads. Cyclr starts at $1595/month and SoapUI at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Cyclr or SoapUI?
- SoapUI has a free tier; the other does not. Paid plans start at $1595/month for Cyclr and Free for SoapUI.
- Does Cyclr or SoapUI run on more platforms?
- Cyclr 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. Cyclr starts at $1595/month.
- What is Cyclr best used for?
- Cyclr is most often used for a mid-market saas vendor losing deals because prospects ask for a crm integration it has not built, a product team that would rather ship an integration marketplace this quarter than hire two engineers to maintain connectors, a european software company that needs its customers' integration data processed inside the eu for procurement reasons, a vendor whose customers each want a slightly different variation of the same integration and cannot be served by one hard-coded connector. Of those, a mid-market saas vendor losing deals because prospects ask for a crm integration it has not built and a product team that would rather ship an integration marketplace this quarter than hire two engineers to maintain connectors are not what SoapUI is typically brought in for.
- What can Cyclr do that SoapUI cannot?
- Cyclr covers White-label integration UI, Connector library, Workflow builder, Custom connectors. 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
Cyclr: What does Cyclr actually cost?
Published tiers start at 1,595 US dollars per month for 100,000 API calls and one connector, rising to 7,195 for unlimited connectors and five million calls.
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.
SourceCyclr: Do my customers know they are using Cyclr?
No. The interface is white-labelled to appear as part of your product.
SoapUI: What protocols does it support?
The open source edition supports REST, SOAP, GraphQL and JMS. ReadyAPI adds XML-RPC, MQTT and other protocols.
SourceCyclr: Can I host it in the EU or UK?
Yes, on the private cloud tiers, which matters for European procurement requirements.
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.
SourceCyclr: What if the connector I need does not exist?
You build a custom connector using Cyclr tooling, which is work you own rather than work the platform removes.
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
- Cyclr vs Paragon
- Cyclr vs Nango
- Cyclr vs Tray.io
- Cyclr vs Celigo
- Cyclr vs Workato
- Cyclr vs Boomi
- Cyclr vs Alloy Automation
- Cyclr vs Merge
- Cyclr vs Hatchet
- Cyclr vs MuleSoft
- Cyclr vs Zapier
- Cyclr vs RudderStack
- Cyclr vs Tealium
- Cyclr vs Trigger.dev
- Cyclr vs UiPath
- Cyclr vs Informatica
- Cyclr vs jBPM
- Cyclr vs Jitterbit
- Cyclr vs Insomnia
- Cyclr vs Testsigma
- Cyclr vs Playwright
- Cyclr vs CircleCI
- Cyclr vs BrowserStack
- Cyclr vs mabl
- Cyclr vs TestRail
- Cyclr vs Qase
- Cyclr vs Zephyr Scale
- Cyclr vs Ranorex
- Cyclr vs JUnit
- Cyclr vs Cucumber
- Cyclr vs Jest
- Cyclr vs TestNG
- Cyclr vs Tricentis Tosca
- Cyclr vs Eppo
- Cyclr vs k6
- Cyclr vs CloudBees Smart Tests
- SoapUI vs Paragon
- SoapUI vs Nango
- SoapUI vs Tray.io
- SoapUI vs Celigo
- SoapUI vs Workato
- SoapUI vs Boomi
- SoapUI vs Alloy Automation
- SoapUI vs Merge
- SoapUI vs Hatchet
- SoapUI vs MuleSoft
- SoapUI vs Zapier
- SoapUI vs RudderStack
- SoapUI vs Tealium
- SoapUI vs Trigger.dev
- SoapUI vs UiPath
- SoapUI vs Informatica
- SoapUI vs jBPM
- SoapUI vs Jitterbit
- 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
