Softwr

Automation Integration · head to head

jBPM vs Ozone API

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
Ozone API logo

Ozone API

APIs

Standards-compliant open banking API layer for banks and regulators

From
On request
Free plan
No

The short version

  • jBPM is free; Ozone API prices on request.
  • Only jBPM lists BPMN 2.0 execution; only Ozone API lists multi-standard support.
  • Where Ozone API falls short: value is driven by regulatory obligation, so an institution not under a mandate struggles to build a business case for the spend.
  • Prices and features on this page were last checked on 20 November 2026.

How do jBPM and Ozone API differ?

jBPM and Ozone API differ on starting price (Free against On request), pricing model and free tier (Yes against No). Only the attributes on which jBPM and Ozone API actually diverge.

Attributes where jBPM and Ozone API differ
AttributejBPMOzone API
Starting priceFreeOn request
Pricing modelOpen source, no licence feeQuote
Free tierYesNo
PlatformsLinux, Windows, Self-hostedWeb, API, Linux
CategoryAutomation IntegrationAPIs

Which features does each one have?

They share no listed features; 8 appear only for jBPM and 6 only for Ozone API. 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 Ozone API

  • Multi-standard support
  • Consent management
  • Developer portal
  • Regulatory reporting
  • Premium API monetisation
  • Deployment flexibility

What is each one used for?

Ozone API is most often brought in for A regulator or standards body building national open finance infrastructure. 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 Ozone API
  • A team that wants BPMN processes and Drools business rules executing in one runtime without integrating two productsnot Ozone API
  • A government or banking system with long-running processes needing durable timers and full audit history at no licence costnot Ozone API
  • A Quarkus estate adopting Kogito to run compiled processes with container-appropriate startup timesnot Ozone API

Ozone API

  • A building society facing an open banking compliance deadline with no API team of its ownnot jBPM
  • A bank operating in several jurisdictions that must satisfy different open banking standards at oncenot jBPM
  • A regulator or standards body building national open finance infrastructurenot jBPM
  • A bank wanting to sell premium APIs beyond the regulatory minimum without building entitlement plumbingnot jBPM

Where do jBPM and Ozone API fall short?

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

Ozone API

  • It provides the API layer, not the core connectivity, so the bulk of the project is still integrating your own core banking systems and that cost is not in the licence
  • Value is driven by regulatory obligation, so an institution not under a mandate struggles to build a business case for the spend
  • It is a small UK vendor selling to large regulated institutions, which raises procurement and vendor viability questions during bank due diligence
  • Premium API monetisation is a genuine capability but few banks have found real demand, so revenue projections used to justify the purchase often do not materialise
  • Standards evolve continuously and each revision means a change programme in your own systems, even where Ozone absorbs the specification work at the API edge

How much do jBPM and Ozone API cost?

jBPM is free to use; Ozone API is priced on request. 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

Ozone API

On request
  • Ozone APIOn request
    • Annual licence or managed service subscription, quoted
    • Scaling by institution size, standards in scope and API call volume
    • Implementation and core integration charged separately

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 Ozone API if

  • You need multi-standard support.
  • You work on Web, API, Linux.
  • You also want consent management.

Questions people ask

Is jBPM or Ozone API better?
Neither clearly leads. jBPM starts at Free and Ozone API at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, jBPM or Ozone API?
jBPM has a free tier; the other does not. Paid plans start at Free for jBPM and On request for Ozone API.
Does jBPM or Ozone API run on more platforms?
jBPM runs on Linux, Windows, Self-hosted. Ozone API runs on Web, API, Linux.
Can I use jBPM for free?
Yes. jBPM has a free tier, so you can try it without paying. Ozone API starts at On request.
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 Ozone API is typically brought in for.
What can jBPM do that Ozone API cannot?
jBPM covers BPMN 2.0 execution, Drools integration, Human task service, Kogito compilation. Ozone API covers Multi-standard support, Consent management, Developer portal, Regulatory reporting.

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.

Ozone API: Is this a competitor to Plaid or TrueLayer?

No, the opposite side. Ozone is bought by the bank exposing data; Plaid and TrueLayer consume it on behalf of third parties.

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.

Ozone API: Does it connect to my core banking system?

It provides the standards-compliant API surface and adapters, but connecting your core is an integration project you scope separately.

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.

Ozone API: Which standards does it support?

UK Open Banking, Berlin Group, FDX, Consumer Data Right and Gulf regional standards, among others, from one platform.

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.

Share

Related pages

Other head to heads