Softwr

Automation Integration · head to head

jBPM vs Microsoft Power Automate

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
Microsoft Power Automate logo

Microsoft Power Automate

Automation Integration

Automate tasks across cloud and on-premises apps

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.; Microsoft Power Automate free plan limited to 750 flow runs/month and standard connectors only; premium connectors require paid plans
  • They diverge on capability: jBPM covers BPMN 2.0 execution, Microsoft Power Automate covers Automated flows.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which jBPM and Microsoft Power Automate actually diverge.

Attributes where jBPM and Microsoft Power Automate differ
AttributejBPMMicrosoft Power Automate
Pricing modelOpen source, no licence feeUnknown
PlatformsLinux, Windows, Docker, KubernetesWeb, Cloud, Desktop
FoundedUnknown2016

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 Microsoft Power Automate

  • Automated flows
  • Instant flows
  • Scheduled flows
  • Desktop automation
  • Process mining
  • Business process flows
  • Approval workflows
  • 500+ connectors

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

Microsoft Power Automate

  • Workflow Automationnot jBPM
  • Data Integrationnot jBPM
  • Process Automationnot jBPM
  • App Integrationnot jBPM
  • API Connectivitynot 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.

Microsoft Power Automate

  • Free plan limited to 750 flow runs/month and standard connectors only; premium connectors require paid plans
  • Not suitable for long-running workflows; can fail unexpectedly without warning
  • Limited to simple linear logic; fails with complex workflows involving multiple stakeholders
  • Tasks cannot automate at scale when requiring more than approximately 60 users

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

Microsoft Power Automate

Free
  • FreeFree
    • 750 flow runs/month
    • Standard connectors only
    • Basic cloud flows
  • Premium$15/user/month
    • Cloud flows (DPA)
    • Attended RPA
    • 250 MB Dataverse database
  • Process$150/bot/month
    • Unattended automation
    • Cloud and desktop flows
    • 50 MB Dataverse database
  • Hosted Process$215/bot/month
    • Microsoft-managed virtual machine
    • Unattended automation
    • Same Dataverse entitlements as Process plan

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 Microsoft Power Automate if

  • You need automated flows.
  • You want to start without paying.
  • You work on Web, Cloud, Desktop.
  • You also want instant flows.
Microsoft Power Automate review

Questions people ask

Is jBPM or Microsoft Power Automate better?
Neither clearly leads. jBPM starts at Free and Microsoft Power Automate at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, jBPM or Microsoft Power Automate?
jBPM starts at Free and Microsoft Power Automate at Free.
Does jBPM or Microsoft Power Automate run on more platforms?
jBPM runs on Linux, Windows, Docker, Kubernetes. Microsoft Power Automate runs on Web, Cloud, Desktop.
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 Microsoft Power Automate is typically brought in for.
What can jBPM do that Microsoft Power Automate cannot?
jBPM covers BPMN 2.0 execution, Drools integration, Human task service, Kogito compilation. Microsoft Power Automate covers Automated flows, Instant flows, Scheduled flows, Desktop automation.

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.

Microsoft Power Automate: Is Power Automate included with Microsoft 365?

Yes. If you have an eligible Microsoft 365 subscription, you can use Power Automate at no extra cost for flows relying only on standard connectors (SharePoint, Outlook, Teams). Premium connectors (Salesforce, SAP, Oracle) require paid plans.

Source
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.

Microsoft Power Automate: How many flow runs are allowed on the free plan?

Power Automate's free tier (included with Microsoft 365) is limited to 750 flow runs per month and standard connectors only. Out of 900+ total connectors, the free plan only includes Microsoft ecosystem apps and limited third-party apps.

Source
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.

Microsoft Power Automate: What's the difference between Premium and Process plans?

Premium ($15/user/month) provides attended automation with cloud flows and standard RPA. Process plan ($150/bot/month) enables unattended automation where bots run without human intervention on virtual machines for high-volume, repetitive tasks.

Source
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.

Microsoft Power Automate: Does Power Automate support long-running workflows?

No. Power Automate is not suitable for long-lasting workflows because they can run without warning and fail unexpectedly. The platform is built for linear, branching logic (if-then) rather than complex, multi-step business processes involving multiple stakeholders.

Source
Share

Related pages

More on jBPM

More on Microsoft Power Automate

Keep looking

Other head to heads