Softwr

Automation Integration · head to head

Flowable vs Ozone API

Flowable logo

Flowable

Automation Integration

Apache 2.0 BPMN, CMMN and DMN engine from the team that originally built Activiti

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

  • Flowable is free; Ozone API prices on request.
  • Only Flowable lists BPMN 2.0 engine; only Ozone API lists multi-standard support.
  • Where Flowable falls short: enterprise pricing is not published and is quoted per deployment, leaving buyers without a benchmark against Camunda or IBM alternatives.
  • 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 Flowable and Ozone API differ?

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

Attributes where Flowable and Ozone API differ
AttributeFlowableOzone API
Starting priceFreeOn request
Free tierYesNo
PlatformsLinux, Windows, Self-hosted, WebWeb, API, Linux
CategoryAutomation IntegrationAPIs

Identical on both: pricing model (Quote).

Not yet recorded: founded for Ozone API.

Which features does each one have?

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

  • BPMN 2.0 engine
  • CMMN case management
  • DMN decision tables
  • Spring Boot integration
  • Modelling studio
  • Task and case application
  • REST APIs
  • History and audit

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.

Flowable

  • An insurer automating claims handling where each case follows a different path and BPMN alone cannot express itnot Ozone API
  • A bank embedding process orchestration inside an existing Spring Boot estate rather than buying a separate platformnot Ozone API
  • A team leaving Activiti or jBPM that wants the same API family with active commercial maintenancenot Ozone API
  • A regulated organisation needing complete process history and decision table audit trails for supervisorsnot Ozone API

Ozone API

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

Where do Flowable and Ozone API fall short?

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Flowable

  • The open source engine is genuinely usable but ships without the modelling studio, work application and admin console, so an open source deployment means building your own user interfaces before anyone can use it
  • It expects Java engineering capacity; teams looking for a business-user low-code automation tool will find the modelling and deployment cycle far too technical
  • Enterprise pricing is not published and is quoted per deployment, leaving buyers without a benchmark against Camunda or IBM alternatives
  • The Activiti fork left three engines with related APIs and overlapping documentation in circulation, and search results routinely return advice for the wrong one
  • Flowable AG is a small Swiss company relative to its competitors, so the partner network, training market and pool of engineers with production experience are all limited outside Europe

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 Flowable and Ozone API cost?

Flowable is free to use; Ozone API is priced on request. Plan by plan below, from each vendor's own pricing page.

Flowable

Free
  • Flowable Open SourceFree
    • Apache 2.0 licensed BPMN, CMMN and DMN engines
    • Embeddable Java library or standalone apps
    • No modelling studio or enterprise applications
  • Flowable EnterpriseOn request
    • Modelling studio, work application and admin console
    • Connectors, forms and advanced identity management
    • Support with SLA and version maintenance

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 Flowable if

  • You need bpmn 2.0 engine.
  • You want to start without paying.
  • You work on Linux, Windows, Self-hosted, Web.
  • You also want cmmn case management.

Choose Ozone API if

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

Questions people ask

Is Flowable or Ozone API better?
Neither clearly leads. Flowable 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, Flowable or Ozone API?
Flowable has a free tier; the other does not. Paid plans start at Free for Flowable and On request for Ozone API.
Does Flowable or Ozone API run on more platforms?
Flowable runs on Linux, Windows, Self-hosted, Web. Ozone API runs on Web, API, Linux.
Can I use Flowable for free?
Yes. Flowable has a free tier, so you can try it without paying. Ozone API starts at On request.
What is Flowable best used for?
Flowable is most often used for an insurer automating claims handling where each case follows a different path and bpmn alone cannot express it, a bank embedding process orchestration inside an existing spring boot estate rather than buying a separate platform, a team leaving activiti or jbpm that wants the same api family with active commercial maintenance, a regulated organisation needing complete process history and decision table audit trails for supervisors. Of those, an insurer automating claims handling where each case follows a different path and bpmn alone cannot express it and a bank embedding process orchestration inside an existing spring boot estate rather than buying a separate platform are not what Ozone API is typically brought in for.
What can Flowable do that Ozone API cannot?
Flowable covers BPMN 2.0 engine, CMMN case management, DMN decision tables, Spring Boot integration. Ozone API covers Multi-standard support, Consent management, Developer portal, Regulatory reporting.

Answered from the vendors’ own pages

Flowable: Is Flowable open source?

Yes, the BPMN, CMMN and DMN engines are Apache 2.0. The modelling studio and enterprise applications are commercial.

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.

Flowable: How does it relate to Activiti and jBPM?

The same core developers built jBPM, then Activiti, then forked Activiti in 2016 to create Flowable.

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.

Flowable: What does Flowable Enterprise cost?

Nothing is published. It is quoted per deployment by the vendor.

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.

Flowable: Why choose it over Camunda?

CMMN case management is a first-class engine, which matters when work is exception-driven rather than a fixed sequence.

Share

Related pages

Other head to heads