jBPM

jBPM is an open-source Java toolkit for embedding business-process automation inside application services. It is best suited to Java teams that need BPMN workflows, human tasks, rules and decisions in one codebase. Choose it when an embedded, self-hosted engine fits your architecture; look elsewhere if you want a ready-made workflow server.

Overview

jBPM runs as Java libraries inside your service rather than as a separate server. That design keeps process execution close to application code and avoids managing a runtime process repository, but your team must operate the surrounding service and its infrastructure. BPMN 2.0 models are compiled at build time, so production does not require a separate process deployment step.

The project is pure Java, runs on any JVM and is published through Maven Central. It is released under the Apache License 2.0. Apache KIE is currently incubating at the Apache Software Foundation and has not received full ASF endorsement, a status worth weighing for organisations with strict platform-governance requirements.

Key features

A visual workflow builder and IDE-based modelers provide graphical drag-and-drop BPMN creation. The engine includes event triggers, automatic retries and execution observability, giving teams building blocks for event-driven services and operational monitoring.

Human tasks have pluggable lifecycles, assignment strategies and deadlines. This suits approval and case-style processes where work moves between people under explicit timing rules, while the configurable model leaves implementation and user-interface decisions to the service team.

Rule tasks can call DRL rules or DMN decisions evaluated by Drools in the same service. Keeping process flow and decision logic together can reduce integration boundaries for Java applications that already use those rule formats.

Long-running workflows retain durable state and support timers, signals, message correlation, service-level agreement tracking and migration of running instances to a new process version. These features fit processes that span days or longer, but they make persistence, upgrades and operational ownership important design work.

Persistence is pluggable across PostgreSQL and other JDBC databases, MongoDB, Infinispan, RocksDB and the filesystem. The choice supports varied deployment environments, though selecting, securing and operating the store remains your responsibility.

For Apache KIE 10, the documented service approach is Kogito on Quarkus or Spring Boot. Getting started calls for an IDE, JDK 21 (with JDK 17 also listed) and Maven 3.9 or later.

Pricing

Apache KIE (jBPM): free. This is open-source Java workflow software under the Apache License 2.0, with no seat, usage or trial terms stated. It is the clear fit for teams able to fund their own development, hosting and support; the trade-off is that operating the embedded service is part of the job rather than a paid vendor service.

Platforms

jBPM is offered for API, extension, Linux, macOS, Windows, web and self-hosted use. Its JVM-based implementation broadens where the engine can run, while the self-hosted deployment model means infrastructure, persistence and upgrades stay with the adopting team.

Who it's for

Java developers building business automation into services are the natural audience, especially teams combining BPMN 2.0 flows with human work, Drools rules and DMN decisions. It also fits organisations needing durable, long-running processes and control over persistence choices.

It is a weaker match for buyers seeking a standalone workflow server, vendor-managed hosting or a visual tool that operates without Java engineering and service ownership.

Pros and cons

Pros

• Open-source Apache 2.0 licensing: teams can adopt the engine without a software subscription.
• Embedded Java architecture: process execution can live inside an existing service instead of requiring a separate server.
• Broad workflow depth: durable state, timers, correlation, SLA tracking and instance migration address long-running operations.
• Integrated decisions and human work: DRL, DMN, configurable human-task lifecycles and assignment strategies cover mixed automation.
• Pluggable persistence: multiple database and storage options accommodate different self-hosted architectures.

Cons

• Operational ownership: self-hosting an embedded library leaves runtime, storage and service reliability to your team.
• Java-centric setup: an IDE, JDK and Maven are prerequisites, limiting suitability for non-Java delivery teams.
• Incubation status: Apache KIE has not yet been fully endorsed by the ASF, which may matter to risk-sensitive adopters.
• No separate process repository: build-time compilation is efficient, but teams wanting runtime model deployment must use a different approach.

Alternatives

Consider Kestra if you want an Apache 2.0 workflow platform with free availability across API, desktop, web and self-hosted environments.

Workflow Engine is a freemium option whose free perpetual plan allows 10 schemas and four execution threads for personal use.

Choose Argo Workflows for an open-source workflow engine designed for Kubernetes.

Bonita offers a free plan capped at 150 process instances per month, with no time limit and no credit card requirement.

Camunda provides a free self-managed development plan for local development and testing.

Apache Airflow is a free Apache-licensed choice for teams wanting its workflow platform across API, Linux, macOS, self-hosted and web environments.

Bizagi Modeler suits users who need a web and Windows modeler; its free plan supports one user with unlimited processes and models stored locally.

Hatchet is a freemium API, Linux, self-hosted and web option with 1 million runs and 1 million events per month free on its pay-as-you-go plan.

Browse Workflow Orchestration Software and Business Process Management Software for wider category choices.

Verdict

jBPM is a strong choice for Java teams that want BPMN workflows, human tasks and Drools-powered decisions embedded in a self-hosted service, with unusually capable support for long-running process state. Choose another product if you need managed hosting, runtime process administration or a project with a fully established Apache status.