jBPMvs
Temporal


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

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
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.
The honest half
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.
Cross-shopped
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.


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


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


Apache Airflow: If the requirement is scheduled data pipeline orchestration rather than business process management
Pricing
Taken from the vendor's own pricing page. Prices move, so check before you buy.
jBPM
Free
Capabilities
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
Each answer names the page it came from, so you can check it rather than take our word for it.
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.
IBM, through Business Automation Manager Open Editions, following the transition away from Red Hat Process Automation Manager as a growth product.
The cloud-native successor that compiles processes ahead of time for Quarkus and Spring Boot, architecturally different from the classic jBPM runtime.
No. It is Apache 2.0 licensed with no fee. Costs are support contracts and the engineering effort to run it.
Keep looking
Durable execution platform for fault-tolerant workflows.
Apache 2.0 BPMN, CMMN and DMN engine from the team that originally built Activiti
Apache 2.0 BPMN engine under Hyland, from which Flowable and Camunda were forked
BPMN process orchestration engine, now source-available rather than open source
Open source ELT built on the Singer tap and target ecosystem, configured as code
Open-source developer platform for building scripts, workflows, and internal apps
Postgres-backed distributed task queue and workflow engine for Python, TypeScript and Go
Open source unified API and OAuth infrastructure for product integrations, licensed under Elastic License 2.0
Commercial Conductor, now the maintainer of the workflow engine Netflix archived
Open source ELT built on the Singer tap and target ecosystem, configured as code
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.
What people switch to, and what they give up
Every tier, and where the cost actually lands
Put it head to head with anything we hold
Its rating, and an embed for your own site
Industrial DataOps middleware that models and contextualises OT data before it reaches IT systems
Per site per yearManaged Apache Flink and Debezium with credit-based pricing and a free tier
Per credit by task hourEmbedded integration platform that SaaS vendors ship inside their own product
Per month by API call volumeApache 2.0 BPMN engine under Hyland, from which Flowable and Camunda were forked
Open source, no licence feeTransactional message queuing for systems where a lost message is a lost payment
Per virtual processor core per monthPostgres-backed distributed task queue and workflow engine for Python, TypeScript and Go
Per month by task run count