Softwr

Automation Integration · head to head

jBPM vs Kogito

jBPM logo

jBPM

Automation Integration

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

From
Free
Rated
-
Full reviewWebsite
Kogito logo

Kogito

Automation Integration

Cloud-native business automation for Quarkus, now an Apache KIE component

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: 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.; Kogito kogito is a developer framework, not a product, so there is no equivalent of Camunda Operate for business users and any process monitoring interface has to be built or bought separately.
  • They diverge on capability: jBPM covers BPMN 2.0 execution, Kogito covers Build-time code generation.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which jBPM and Kogito actually diverge.

Attributes where jBPM and Kogito differ
AttributejBPMKogito
PlatformsLinux, Windows, Docker, KubernetesLinux, Docker, Kubernetes

Identical on both: starting price (Free), pricing model (Open source, no licence fee), free tier (Yes), user rating (Not yet rated), category (Automation Integration).

What each one covers

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 Kogito

  • Build-time code generation
  • Quarkus and Spring Boot support
  • DMN decision services
  • Drools rules engine
  • Serverless workflow
  • Kubernetes operator

What people use each for

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 Kogito
  • A team that wants BPMN processes and Drools business rules executing in one runtime without integrating two productsnot Kogito
  • A government or banking system with long-running processes needing durable timers and full audit history at no licence costnot Kogito
  • A Quarkus estate adopting Kogito to run compiled processes with container-appropriate startup timesnot Kogito

Kogito

  • A Quarkus microservice that must expose a DMN decision model as a REST endpoint with millisecond start-upnot jBPM
  • Serverless deployment of business rules where a traditional BPM server would be far too heavynot jBPM
  • A Red Hat shop that wants the upstream of Red Hat process automation with the option of a supported build laternot jBPM
  • Replacing hand-coded conditional logic with DMN tables that business analysts can review and amendnot jBPM

Where each one falls 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.

Kogito

  • Kogito is a developer framework, not a product, so there is no equivalent of Camunda Operate for business users and any process monitoring interface has to be built or bought separately.
  • Long-running stateful processes need external persistence and messaging that you configure and operate yourself, which removes much of the convenience a BPM server normally provides.
  • It sits inside the Apache KIE incubator, and incubating status means graduation is not guaranteed and the project name and artefact coordinates have already changed once.
  • Red Hat is by far the dominant contributor despite ASF stewardship, so the roadmap follows Red Hat product priorities rather than community demand.
  • Documentation is spread across legacy JBoss sites, the old Kogito site and the new Apache KIE site, and search results routinely land on outdated versions, which costs real time during adoption.

Pricing, plan by plan

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

Kogito

Free
  • KogitoFree
    • Apache 2.0 licence
    • Apache KIE incubating project
    • No usage limits

Which should you pick?

Choose jBPM if

  • You need bpmn 2.0 execution.
  • You want to start without paying.
  • You work on Linux, Windows, Docker, Kubernetes.
  • You also want drools integration.
jBPM review

Choose Kogito if

  • You need build-time code generation.
  • You want to start without paying.
  • You work on Linux, Docker, Kubernetes.
  • You also want quarkus and spring boot support.
Kogito review

Questions people ask

Is jBPM or Kogito better?
Neither clearly leads. jBPM starts at Free and Kogito at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, jBPM or Kogito?
jBPM starts at Free and Kogito at Free.
Does jBPM or Kogito run on more platforms?
jBPM runs on Linux, Windows, Docker, Kubernetes. Kogito runs on Linux, Docker, Kubernetes.
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 Kogito is typically brought in for.
What can jBPM do that Kogito cannot?
jBPM covers BPMN 2.0 execution, Drools integration, Human task service, Kogito compilation. Kogito covers Build-time code generation, Quarkus and Spring Boot support, DMN decision services, Drools rules engine.

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.

Kogito: Is Kogito still maintained?

Yes. It is an Apache KIE incubating project with active commits, with Red Hat as the dominant contributor.

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.

Kogito: How does it differ from jBPM?

Kogito compiles process and rule definitions into application code at build time; jBPM was a runtime engine that loads definitions.

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.

Kogito: Does it need Quarkus?

It is designed for Quarkus and supports Spring Boot; both are Java frameworks rather than a standalone server.

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.

Kogito: Is there commercial support?

Not from Apache. Red Hat sells supported builds of this lineage as part of its subscriptions.

Share

Related pages

More on jBPM

More on Kogito

Keep looking

Other head to heads