Softwr

Automation Integration · head to head

jBPM vs Refact

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
Refact logo

Refact

Developer Tools

Autonomous AI coding agent for development tasks

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.; Refact requires configuration for optimal performance
  • They diverge on capability: jBPM covers BPMN 2.0 execution, Refact covers Autonomous agent workflows.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which jBPM and Refact actually diverge.

Attributes where jBPM and Refact differ
AttributejBPMRefact
Pricing modelOpen source, no licence feeFreemium with paid tiers
PlatformsLinux, Windows, Docker, KubernetesVS Code, Web
CategoryAutomation IntegrationDeveloper Tools
FoundedUnknown2023

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated).

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 Refact

  • Autonomous agent workflows
  • IDE chat
  • Real-time code completions
  • GitHub integration
  • Database integration
  • On-premise deployment
  • Multi-LLM support
  • 25+ language support

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

Refact

  • Autonomous code generation for development tasksnot jBPM
  • End-to-end bug fixes and refactoringnot jBPM
  • Multi-language software development accelerationnot jBPM
  • Enterprise development with data privacy requirementsnot 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.

Refact

  • Requires configuration for optimal performance
  • On-premise deployment adds operational complexity
  • Free tier limited by daily agent request quota
  • Coin system adds complexity to cost calculation

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

Refact

Free
  • FreeFree
    • Limited daily agent usage
    • Unlimited completions
    • 2,000 coins for agent and chat
  • Pro$10/month
    • 40 daily agent requests
    • 64k context window
    • 10,000 coins monthly
  • Enterprise$undefined/custom
    • On-premise deployment
    • Custom coin allocation
    • Fine-tuning support

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 Refact if

  • You need autonomous agent workflows.
  • You want to start without paying.
  • You work on VS Code, Web.
  • You also want ide chat.
Refact review

Questions people ask

Is jBPM or Refact better?
Neither clearly leads. jBPM starts at Free and Refact at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, jBPM or Refact?
jBPM starts at Free and Refact at Free.
Does jBPM or Refact run on more platforms?
jBPM runs on Linux, Windows, Docker, Kubernetes. Refact runs on VS Code, Web.
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 Refact is typically brought in for.
What can jBPM do that Refact cannot?
jBPM covers BPMN 2.0 execution, Drools integration, Human task service, Kogito compilation. Refact covers Autonomous agent workflows, IDE chat, Real-time code completions, GitHub integration.

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.

Refact: How many programming languages does Refact support?

Refact supports 25+ programming languages including Python, JavaScript, Go, Rust, Java, C++, and many others.

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.

Refact: Can I deploy Refact on-premises?

Yes. Refact offers on-premise deployment options for organizations requiring complete data control and privacy.

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.

Refact: What LLMs does Refact support?

Refact works with multiple LLMs including Claude, GPT-4, and open-source models, giving you flexibility in model selection.

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.

Share

Related pages

More on jBPM

More on Refact

Keep looking

Other head to heads