Softwr
jBPM logo

jBPM

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

As of 31 August 2026, jBPM is free to use. The BPMN process engine that has been part of the JBoss and Red Hat stack since 2004, donated with Drools and OptaPlanner to the Apache Software Foundation as the KIE project. Softwr lists it under Automation Integration. jBPM is made by Apache Software Foundation, available on Linux, Windows, Docker, Kubernetes.

Overview

What jBPM does

jBPM is a Java business process management engine implementing BPMN 2.0, with a process runtime, a persistent execution store, human task management, timers and a designer. It has always been tightly coupled to Drools, the rules engine from the same stable, so processes and business rules share a runtime and a knowledge base. Kogito, the cloud-native successor, compiles processes ahead of time for Quarkus and Spring Boot so they start fast enough for containers and serverless. The important fact is the ownership change. Red Hat donated Drools, jBPM, OptaPlanner and Kogito to the Apache Software Foundation, where they are now developed as Apache KIE, currently in incubation, with releases such as KIE 10.1.0 in July 2025. The last Red Hat-sponsored jBPM release under the old numbering, 7.74.1, dates from 2023. Commercial support has moved too: the enterprise path is now IBM Business Automation Manager Open Editions rather than Red Hat Process Automation Manager as a growth product. Buyers are Java organisations, often in banking, insurance and government, that already run jBPM and are deciding between staying on the 7.x line, moving to Apache KIE and Kogito, or leaving. The trade-off is transition cost. The engine is free and standards-based, but Kogito is architecturally different from the classic jBPM runtime, and an incubating Apache project with a shifting commercial owner is a harder thing to justify to an architecture board than it was five years ago.

What people use it 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

The honest half

Where it falls short

Concrete and checkable, so you can decide whether any of them matter to you. This is the half of a review a vendor will not write about 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.

Cross-shopped

What people choose instead of jBPM

Each pairing was judged by two reviewers asking whether a buyer would genuinely weigh the two against each other. The ones that failed were deleted rather than published.

  • jBPM logo
    jBPM
    vs
    Temporal logo
    Temporal

    Temporal: If you want durable execution defined in code with active commercial backing rather than BPMN modelling

  • jBPM logo
    jBPM
    vs
    Nintex logo
    Nintex

    Nintex: If business users rather than Java developers should own the processes

  • jBPM logo
    jBPM
    vs
    Apache Airflow logo
    Apache Airflow

    Apache Airflow: If the requirement is scheduled data pipeline orchestration rather than business process management

Pricing

What jBPM costs

Taken from the vendor's own pricing page. Prices move, so check before you buy.

jBPM

Free

  • Apache 2.0 licence with no usage restrictions
  • Full BPMN engine, human tasks and Drools integration
  • Community support via Apache KIE mailing lists
  • Commercial support available separately from IBM

Capabilities

Features

  • BPMN 2.0 execution

    Standards-based process runtime with persistence and recovery

  • Drools integration

    Business rules and processes sharing one knowledge base and runtime

  • Human task service

    WS-HumanTask based assignment, groups and task lifecycle

  • Kogito compilation

    Ahead-of-time compiled processes for Quarkus and Spring Boot

  • Process designer

    Graphical BPMN modelling in the workbench tooling

  • Timers and signals

    Long-running processes with durable timers and event correlation

  • REST and Java APIs

    Engine control from Java or over HTTP

  • Case management

    Ad hoc case handling built on the process runtime

Answered, with sources

Questions people ask

Each answer names the page it came from, so you can check it rather than take our word for it.

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.

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.

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.

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

Keep looking

Where to go from jBPM

Best Automation Integration software for

Compare jBPM with

Other Automation Integration software

  • Durable execution platform for fault-tolerant workflows.

    Free, then $100/mo12 researched notes
  • The work automation platform

    Free plan10 researched notes
  • Apache 2.0 BPMN, CMMN and DMN engine from the team that originally built Activiti

    Free plan12 researched notes
  • Apache 2.0 BPMN engine under Hyland, from which Flowable and Camunda were forked

    Open source12 researched notes
  • BPMN process orchestration engine, now source-available rather than open source

    Pricing on request12 researched notes
  • Open source ELT built on the Singer tap and target ecosystem, configured as code

    Open source12 researched notes
  • The open-source ELT platform

    Free plan13 researched notes
  • Open-source developer platform for building scripts, workflows, and internal apps

    Free, then $120/mo10 researched notes
  • Postgres-backed distributed task queue and workflow engine for Python, TypeScript and Go

    Free, then $500/mo12 researched notes
  • The fair-code workflow automation tool

    Free, then €20/mo12 researched notes
  • The open-source customer data platform

    Free plan11 researched notes
  • Open source unified API and OAuth infrastructure for product integrations, licensed under Elastic License 2.0

    Free, then $50/mo13 researched notes
  • Commercial Conductor, now the maintainer of the workflow engine Netflix archived

    Free plan12 researched notes
  • Sync your business logic with data

    Free plan10 researched notes
  • Specialist AI Agents for Every Task

    10 researched notes
  • Automation inside Salesforce

    Free, then $25/user/month13 researched notes
  • The #1 integration platform for enterprise

    From $2,000/mo10 researched notes
  • Open source ELT built on the Singer tap and target ecosystem, configured as code

    Open source12 researched notes

Softwr does not host reviews and shows no star rating for jBPM, because a rating we did not collect is not ours to publish. What is here is the pricing and platform detail from the vendor’s own pages, limitations we could state concretely, and alternatives a reviewer confirmed people weigh against it. Tell us if any of it is wrong.

More on jBPM

Best Automation Integration software alternatives

Industrial DataOps middleware that models and contextualises OT data before it reaches IT systems

Per site per year

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

quote

Managed Apache Flink and Debezium with credit-based pricing and a free tier

Per credit by task hour

Embedded integration platform that SaaS vendors ship inside their own product

Per month by API call volume

Apache 2.0 BPMN engine under Hyland, from which Flowable and Camunda were forked

Open source, no licence fee

Transactional message queuing for systems where a lost message is a lost payment

Per virtual processor core per month

Postgres-backed distributed task queue and workflow engine for Python, TypeScript and Go

Per month by task run count

BPMN process orchestration engine, now source-available rather than open source

quote

Compare jBPM with alternatives