Automation Integration · head to head
jBPM vs Windmill
jBPM
Automation Integration
Long-running Java BPMN engine, now developed inside Apache KIE with commercial support from IBM
- From
- Free
- Rated
- -
Windmill
Automation Integration
Open-source developer platform for building scripts, workflows, and internal apps
- From
- Free
- Rated
- -
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.; Windmill free self-hosted tier caps SSO users at 10 and workspaces at 3, requiring Enterprise for larger teams.
- They diverge on capability: jBPM covers BPMN 2.0 execution, Windmill covers Script-to-workflow engine.
- Prices and features above were last checked on 31 August 2026.
Where they differ
Only the attributes on which jBPM and Windmill actually diverge.
Identical on both: starting price (Free), 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 Windmill
- Script-to-workflow engine
- Auto-generated UIs
- Self-hosted deployment
- Git sync
- SSO support
- Audit logs
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 Windmill
- A team that wants BPMN processes and Drools business rules executing in one runtime without integrating two productsnot Windmill
- A government or banking system with long-running processes needing durable timers and full audit history at no licence costnot Windmill
- A Quarkus estate adopting Kogito to run compiled processes with container-appropriate startup timesnot Windmill
Windmill
- Turning ad-hoc scripts into scheduled jobs and APIsnot jBPM
- Building internal tools from existing Python/TypeScript codenot jBPM
- Self-hosted automation for engineering teamsnot jBPM
- Orchestrating multi-language workflowsnot 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.
Windmill
- Free self-hosted tier caps SSO users at 10 and workspaces at 3, requiring Enterprise for larger teams.
- Compute unit and seat-based pricing (developer vs. operator seats, worker compute units) adds pricing complexity beyond a flat monthly fee.
- Email triggers are capped at 100/day on the free tier, limiting event-driven use cases without upgrading.
- Smaller ecosystem of pre-built integrations compared to more established automation tools like n8n.
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
Windmill
Free- Free / Open-sourceFree
- Unlimited executions
- Self-hosted deployment
- Max 10 users with SSO
- Enterprise$120/month
- Unlimited executions and workspaces
- Uncapped SSO seats
- 24/7 priority support (3-hour response)
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.
Choose Windmill if
- You need script-to-workflow engine.
- You want to start without paying.
- You work on web, api, linux, windows, mac.
- You also want auto-generated uis.
Questions people ask
- Is jBPM or Windmill better?
- Neither clearly leads. jBPM starts at Free and Windmill at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, jBPM or Windmill?
- jBPM starts at Free and Windmill at Free.
- Does jBPM or Windmill run on more platforms?
- jBPM runs on Linux, Windows, Docker, Kubernetes. Windmill runs on web, api, linux, windows, mac.
- 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 Windmill is typically brought in for.
- What can jBPM do that Windmill cannot?
- jBPM covers BPMN 2.0 execution, Drools integration, Human task service, Kogito compilation. Windmill covers Script-to-workflow engine, Auto-generated UIs, Self-hosted deployment, Git sync.
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.
Windmill: What does Windmill cost?
Windmill's Free and Open-source edition is $0/month for self-hosted use with unlimited executions, while Enterprise starts at $120/month with unlimited workspaces and uncapped SSO seats, priced further by developer/operator seats and compute units.
SourcejBPM: 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.
Windmill: Is there a free plan and what are its limits?
The free self-hosted plan supports unlimited executions but caps SSO at 10 users, workspaces at 3, groups/permissions at 4, and email triggers at 100 per day.
SourcejBPM: 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.
Windmill: How is usage metered on Windmill Enterprise?
Enterprise usage is metered through seats (developer seats at $20/month, operator seats at $10/month) and compute units, e.g. $100/month for 2 standard-worker compute units.
SourcejBPM: 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.
Windmill: What happens to a self-hosted Windmill deployment if the company shuts down?
The pricing page addresses this directly as an FAQ topic, noting that self-hosted applications built on the open-source edition can continue running independently of Windmill the company.
SourceRelated pages
Other head to heads
- jBPM vs Temporal
- jBPM vs Nintex
- jBPM vs Flowable
- jBPM vs Activiti
- jBPM vs Camunda
- jBPM vs Meltano
- jBPM vs Airbyte
- jBPM vs Hatchet
- jBPM vs n8n
- jBPM vs RudderStack
- jBPM vs Nango
- jBPM vs Orkes
- jBPM vs Polytomic
- jBPM vs Relevance AI
- jBPM vs Salesforce Flows
- jBPM vs SnapLogic
- jBPM vs Grouparoo
- jBPM vs Merge
- jBPM vs Flowise
- jBPM vs Automate.io
- jBPM vs Autonoly
- jBPM vs Boomi
- jBPM vs Browser Use
- jBPM vs Browserbase
- Windmill vs Temporal
- Windmill vs Nintex
- Windmill vs Flowable
- Windmill vs Activiti
- Windmill vs Camunda
- Windmill vs Meltano
- Windmill vs Airbyte
- Windmill vs Hatchet
- Windmill vs n8n
- Windmill vs RudderStack
- Windmill vs Nango
- Windmill vs Orkes
- Windmill vs Polytomic
- Windmill vs Relevance AI
- Windmill vs Salesforce Flows
- Windmill vs SnapLogic
- Windmill vs Grouparoo
- Windmill vs Merge
- Windmill vs Flowise
- Windmill vs Automate.io
- Windmill vs Autonoly
- Windmill vs Boomi
- Windmill vs Browser Use
- Windmill vs Browserbase