Automation Integration · head to head
Flowable vs Orkes

Flowable
Automation Integration
Apache 2.0 BPMN, CMMN and DMN engine from the team that originally built Activiti
- From
- Free
- Rated
- -

Orkes
Automation Integration
Commercial Conductor, now the maintainer of the workflow engine Netflix archived
- From
- Free
- Rated
- -
The short version
- Each has a real cost: Flowable the open source engine is genuinely usable but ships without the modelling studio, work application and admin console, so an open source deployment means building your own user interfaces before anyone can use it.; Orkes netflix archived the Conductor repository in December 2023 and Orkes took over maintenance, so the large-company backing that justified many original adoptions no longer exists.
- They diverge on capability: Flowable covers BPMN 2.0 engine, Orkes covers JSON workflow definitions.
- Prices and features above were last checked on 31 August 2026.
Where they differ
Only the attributes on which Flowable and Orkes actually diverge.
Identical on both: starting price (Free), pricing model (quote), 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 Flowable
- BPMN 2.0 engine
- CMMN case management
- DMN decision tables
- Spring Boot integration
- Modelling studio
- Task and case application
- REST APIs
- History and audit
Only in Orkes
- JSON workflow definitions
- Polyglot workers
- Visual workflow builder
- AI and LLM tasks
- Human tasks
- Event handlers
- RBAC and secrets
- Hosted or self-hosted
What people use each for
The jobs each tool is most often brought in to do.
Flowable
- An insurer automating claims handling where each case follows a different path and BPMN alone cannot express itnot Orkes
- A bank embedding process orchestration inside an existing Spring Boot estate rather than buying a separate platformnot Orkes
- A team leaving Activiti or jBPM that wants the same API family with active commercial maintenancenot Orkes
- A regulated organisation needing complete process history and decision table audit trails for supervisorsnot Orkes
Orkes
- A microservices estate that needs orchestration across services written in different languages without a shared SDKnot Flowable
- A team already running Conductor OSS that wants a supported distribution now that Netflix has stopped maintaining itnot Flowable
- An AI platform composing agent steps, model calls and vector lookups as versioned workflow definitionsnot Flowable
- A business process needing human approval steps interleaved with automated service callsnot Flowable
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Flowable
- The open source engine is genuinely usable but ships without the modelling studio, work application and admin console, so an open source deployment means building your own user interfaces before anyone can use it.
- It expects Java engineering capacity; teams looking for a business-user low-code automation tool will find the modelling and deployment cycle far too technical.
- Enterprise pricing is not published and is quoted per deployment, leaving buyers without a benchmark against Camunda or IBM alternatives.
- The Activiti fork left three engines with related APIs and overlapping documentation in circulation, and search results routinely return advice for the wrong one.
- Flowable AG is a small Swiss company relative to its competitors, so the partner network, training market and pool of engineers with production experience are all limited outside Europe.
Orkes
- Netflix archived the Conductor repository in December 2023 and Orkes took over maintenance, so the large-company backing that justified many original adoptions no longer exists.
- Enterprise pricing is entirely unpublished, and the only free option is explicitly a prototyping sandbox whose limits can change at any time, so there is no supported low-cost entry point.
- Self-hosting Conductor OSS in production means operating the engine plus its persistence and indexing dependencies, typically Postgres or Cassandra with Elasticsearch, which is a substantial platform commitment.
- JSON workflow definitions are language agnostic but verbose and awkward to test, and teams accustomed to defining workflows in code find them a step backwards in developer experience.
- Orkes is a small company whose commercial future is tied to a single open source project it also maintains, which concentrates both vendor and project risk in the same place.
Pricing, plan by plan
Flowable
Free- Flowable Open SourceFree
- Apache 2.0 licensed BPMN, CMMN and DMN engines
- Embeddable Java library or standalone apps
- No modelling studio or enterprise applications
- Flowable Enterprise$undefined/year
- Modelling studio, work application and admin console
- Connectors, forms and advanced identity management
- Support with SLA and version maintenance
Orkes
Free- Developer EditionFree
- All Conductor OSS features plus enterprise capabilities
- Sandbox for prototyping only
- Rate limits and resources may change without notice
- Enterprise$undefined/year
- Availability SLA up to 99.99%
- Orkes-hosted or customer-hosted deployment
- Dedicated technical account manager
Which should you pick?
Choose Flowable if
- You need bpmn 2.0 engine.
- You want to start without paying.
- You work on Linux, Windows, Docker, Kubernetes, Cloud.
- You also want cmmn case management.
Choose Orkes if
- You need json workflow definitions.
- You want to start without paying.
- You work on Linux, Docker, Kubernetes, Cloud.
- You also want polyglot workers.
Questions people ask
- Is Flowable or Orkes better?
- Neither clearly leads. Flowable starts at Free and Orkes at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Flowable or Orkes?
- Flowable starts at Free and Orkes at Free.
- Does Flowable or Orkes run on more platforms?
- Flowable runs on Linux, Windows, Docker, Kubernetes, Cloud. Orkes runs on Linux, Docker, Kubernetes, Cloud.
- Can I use Flowable for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is Flowable best used for?
- Flowable is most often used for an insurer automating claims handling where each case follows a different path and bpmn alone cannot express it, a bank embedding process orchestration inside an existing spring boot estate rather than buying a separate platform, a team leaving activiti or jbpm that wants the same api family with active commercial maintenance, a regulated organisation needing complete process history and decision table audit trails for supervisors. Of those, an insurer automating claims handling where each case follows a different path and bpmn alone cannot express it and a bank embedding process orchestration inside an existing spring boot estate rather than buying a separate platform are not what Orkes is typically brought in for.
- What can Flowable do that Orkes cannot?
- Flowable covers BPMN 2.0 engine, CMMN case management, DMN decision tables, Spring Boot integration. Orkes covers JSON workflow definitions, Polyglot workers, Visual workflow builder, AI and LLM tasks.
Answered from the vendors’ own pages
Flowable: Is Flowable open source?
Yes, the BPMN, CMMN and DMN engines are Apache 2.0. The modelling studio and enterprise applications are commercial.
Orkes: Does Netflix still maintain Conductor?
No. Netflix archived its repository in December 2023. The open source project continues at conductor-oss under Apache 2.0, maintained by Orkes.
Flowable: How does it relate to Activiti and jBPM?
The same core developers built jBPM, then Activiti, then forked Activiti in 2016 to create Flowable.
Orkes: Is there a free production tier?
No. The Developer Edition is a sandbox that the vendor states is unsuitable for production. Self-hosting Conductor OSS is the free production route.
Flowable: What does Flowable Enterprise cost?
Nothing is published. It is quoted per deployment by the vendor.
Orkes: What does Enterprise cost?
Nothing is published; it is quoted by deployment and support requirements.
Flowable: Why choose it over Camunda?
CMMN case management is a first-class engine, which matters when work is exception-driven rather than a fixed sequence.
Orkes: How does it compare with Temporal?
Conductor uses declarative JSON workflow definitions and external workers; Temporal defines workflows in code. Temporal has the larger community.
Related pages
Other head to heads
- Flowable vs Temporal
- Flowable vs Nintex
- Flowable vs jBPM
- Flowable vs Activiti
- Flowable vs Camunda
- Flowable vs Kogito
- Flowable vs Airbyte
- Flowable vs Nango
- Flowable vs Windmill
- Flowable vs Hatchet
- Flowable vs Meltano
- Flowable vs RudderStack
- Flowable vs HighLevel
- Flowable vs Grouparoo
- Flowable vs Hevo Data
- Flowable vs HighByte Intelligence Hub
- Flowable vs IBM MQ
- Flowable vs n8n
- Flowable vs Autonoly
- Flowable vs Cyclr
- Flowable vs Hightouch
- Flowable vs Jitterbit
- Flowable vs Pipedream
- Flowable vs Tray.io
- Orkes vs Temporal
- Orkes vs Nintex
- Orkes vs jBPM
- Orkes vs Activiti
- Orkes vs Camunda
- Orkes vs Kogito
- Orkes vs Airbyte
- Orkes vs Nango
- Orkes vs Windmill
- Orkes vs Hatchet
- Orkes vs Meltano
- Orkes vs RudderStack
- Orkes vs HighLevel
- Orkes vs Grouparoo
- Orkes vs Hevo Data
- Orkes vs HighByte Intelligence Hub
- Orkes vs IBM MQ
- Orkes vs n8n
- Orkes vs Autonoly
- Orkes vs Cyclr
- Orkes vs Hightouch
- Orkes vs Jitterbit
- Orkes vs Pipedream
- Orkes vs Tray.io
