Softwr

Automation Integration · head to head

jBPM vs SoapUI

jBPM logo

jBPM

Automation Integration

Long-running Java BPMN engine, now developed inside Apache KIE with commercial support from IBM

From
Free
Free plan
Yes
SoapUI logo

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 jBPM lists BPMN 2.0 execution; only SoapUI lists groovy and JavaScript scripting.
  • 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 jBPM and SoapUI differ?

jBPM and SoapUI differ on pricing model, platforms and category. Only the attributes on which jBPM and SoapUI actually diverge.

Attributes where jBPM and SoapUI differ
AttributejBPMSoapUI
Pricing modelOpen source, no licence feeOpen-source
PlatformsLinux, Windows, Self-hostedWindows, macOS, Linux
CategoryAutomation IntegrationTesting

Identical on both: starting price (Free), free tier (Yes).

Which features does each one have?

They share no listed features; 8 appear only for jBPM 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 jBPM

  • BPMN 2.0 execution
  • Drools integration
  • Human task service
  • Kogito compilation
  • Process designer
  • Timers and signals
  • REST and Java APIs
  • Case management

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.

jBPM

  • A Java organisation already running jBPM 7 that needs to decide between the Apache KIE line, Kogito or migration awaynot SoapUI
  • A team that wants BPMN processes and Drools business rules executing in one runtime without integrating two productsnot SoapUI
  • A government or banking system with long-running processes needing durable timers and full audit history at no licence costnot SoapUI
  • A Quarkus estate adopting Kogito to run compiled processes with container-appropriate startup timesnot SoapUI

SoapUI

  • Functional testing of SOAP web servicesnot jBPM
  • REST and GraphQL API regression checksnot jBPM
  • Scripted API tests in Groovynot jBPM
  • Evaluating ReadyAPI before a team purchasenot jBPM

Where do jBPM 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.

jBPM

  • The project moved to the Apache Software Foundation as Apache KIE and is still in incubation, which is a weaker governance signal than a vendor-owned product and a harder case to make to an architecture board
  • The classic jBPM 7.x line has not had a Red Hat-sponsored release since 2023, so staying on it means running effectively frozen software while the development happens under a different name
  • Kogito is architecturally different from the classic runtime, using ahead-of-time compilation, so moving forward is a migration project rather than a version upgrade
  • Commercial support has shifted to IBM Business Automation Manager Open Editions, which means renegotiating with a different vendor under different terms than Red Hat customers signed
  • The tooling and workbench have long been the weakest part, and organisations routinely build their own process administration interfaces because the shipped ones are dated

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 jBPM and SoapUI cost?

jBPM is free to use; SoapUI is free to use. Plan by plan below, from each vendor's own pricing page.

jBPM

Free
  • jBPMFree
    • Apache 2.0 licence with no usage restrictions
    • Full BPMN engine, human tasks and Drools integration
    • Community support via Apache KIE mailing lists

SoapUI

Free

No published plan breakdown. See the SoapUI review.

Which should you pick?

Choose jBPM if

  • You need bpmn 2.0 execution.
  • You want to start without paying.
  • You work on Linux, Windows, Self-hosted.
  • You also want drools integration.

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 jBPM or SoapUI better?
Neither clearly leads. jBPM 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, jBPM or SoapUI?
jBPM starts at Free and SoapUI at Free.
Does jBPM or SoapUI run on more platforms?
jBPM runs on Linux, Windows, Self-hosted. SoapUI runs on Windows, macOS, Linux.
Can I use jBPM for free?
Both have a free tier, so you can try either at no cost before committing.
What is jBPM best used for?
jBPM is most often used for a java organisation already running jbpm 7 that needs to decide between the apache kie line, kogito or migration away, a team that wants bpmn processes and drools business rules executing in one runtime without integrating two products, a government or banking system with long-running processes needing durable timers and full audit history at no licence cost, a quarkus estate adopting kogito to run compiled processes with container-appropriate startup times. Of those, a java organisation already running jbpm 7 that needs to decide between the apache kie line, kogito or migration away and a team that wants bpmn processes and drools business rules executing in one runtime without integrating two products are not what SoapUI is typically brought in for.
What can jBPM do that SoapUI cannot?
jBPM covers BPMN 2.0 execution, Drools integration, Human task service, Kogito compilation. 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

jBPM: Is jBPM dead?

No. Development continues as part of Apache KIE, with releases through 2025, but the Red Hat-sponsored 7.x line has been static since 2023.

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.

Source
jBPM: Who provides commercial support?

IBM, through Business Automation Manager Open Editions, following the transition away from Red Hat Process Automation Manager as a growth 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.

Source
jBPM: What is Kogito?

The cloud-native successor that compiles processes ahead of time for Quarkus and Spring Boot, architecturally different from the classic jBPM runtime.

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.

Source
jBPM: Does it cost anything?

No. It is Apache 2.0 licensed with no fee. Costs are support contracts and the engineering effort to run it.

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.

Source
Share

Related pages

Other head to heads