Comparison
camunda vs flowable-engine
Verdict
Pick camunda if camunda's strength in BPMN and its Java base offer robust process orchestration options, ideal for those needing deep workflow management with a focus on interoperable microservice architectures; pick flowable-engine if flowable-engine is a Java-based BPM platform which focuses on being compact and efficient for developers, system admins, and business users.
Markdown twin · camunda alternatives · flowable-engine alternatives
GraphCanon updated Sep 20, 2026
15views this month
Trust & integrity
| Signal | camunda | flowable-engine |
|---|---|---|
| Maintenance | Very active (0d since push) As of Sep 15, 2026 · github_public_v1 | Very active (2d since push) As of Sep 14, 2026 · github_public_v1 |
| Provenance | Not a fork · Organization account As of Sep 15, 2026 · github_public_v1 | Not a fork · Organization account As of Sep 14, 2026 · github_public_v1 |
| OSV dependency advisories | No lockfile (source not queried) As of Jul 15, 2026 · osv@v1 | No lockfile (source not queried) As of Jul 15, 2026 · osv@v1 |
| deps.dev advisories | Not queried deps.dev@v1 | Not queried deps.dev@v1 |
| OpenSSF Scorecard | Not queried openssf-scorecard@v1 | Not queried openssf-scorecard@v1 |
Tagline
- camunda
- Process Orchestration Framework
- flowable-engine
- A compact and highly efficient workflow and Business Process Management (BPM) platform
Stars
- camunda
- 4.3k
- flowable-engine
- 9.5k
Forks
- camunda
- 819
- flowable-engine
- 2.9k
Open issues
- camunda
- 2.8k
- flowable-engine
- 411
Language
- camunda
- Java
- flowable-engine
- Java
Adopt for
- camunda
- Camunda's strength in BPMN and its Java base offer robust process orchestration options, ideal for those needing deep workflow management with a focus on interoperable microservice architectures.
- flowable-engine
- Flowable-engine is a Java-based BPM platform which focuses on being compact and efficient for developers, system admins, and business users.
Persona
- camunda
- -
- flowable-engine
- -
Runtime
- camunda
- -
- flowable-engine
- -
License
- camunda
- -
- flowable-engine
- Apache-2.0
Last pushed
- camunda
- Sep 15, 2026
- flowable-engine
- Sep 12, 2026
Categories
- camunda
- Developer Tools
- flowable-engine
- Developer Tools
Trust and health
Days since push
- camunda
- 0d
- flowable-engine
- 2d
Open issues (now)
- camunda
- 2.8k
- flowable-engine
- 411
Stars delta
- camunda
- +41 (30d)
- flowable-engine
- +84 (30d)
Open issues delta
- camunda
- -73 (30d)
- flowable-engine
- +10 (30d)
Full report
- camunda
- Trust report
- flowable-engine
- Trust report
Choose camunda if…
- Tags unique to camunda: grpc, microservices, orchestration-framework.
- - For projects requiring integration of standardized BPMN processes within a microservices architecture
- More recently updated (last pushed Sep 15, 2026).
When NOT to use camunda
- - Avoid if the project requires non-BPMN process models or languages that are not natively supported within Camunda's framework
- - Not suitable for teams looking to minimize technology stack, as its ecosystem includes several components like Zeebe, Operate, Tasklist which might increase complexity
Choose flowable-engine if…
- When your project requires extensive integration with existing Java applications without adding significant overhead.
- More GitHub stars (9.5k vs 4.3k) - visibility, not fit.
When NOT to use flowable-engine
- If you need a BPM solution that heavily relies on graphical process design tools, as Flowable-engine may not cater to non-technical users as intuitively as some competitors.
- In scenarios needing extensive support for custom programming languages outside of Java, as this could limit its applicability and efficacy.
Explore
Sources
Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.
- GitHub stars (camunda/camunda) · observed Sep 20, 2026
- GitHub forks (camunda/camunda) · observed Sep 20, 2026
- Last push (camunda/camunda) · observed Sep 15, 2026
- License file (unknown) · observed Sep 20, 2026
- Decision facts (enrichment) · observed Jul 16, 2026
- Trust scan (lockfile / OSV) · observed Jul 15, 2026
- GitHub stars (flowable/flowable-engine) · observed Sep 20, 2026
- GitHub forks (flowable/flowable-engine) · observed Sep 20, 2026
- Last push (flowable/flowable-engine) · observed Sep 12, 2026
- License file (Apache-2.0) · observed Sep 20, 2026
- Decision facts (enrichment) · observed Jul 16, 2026
- Trust scan (lockfile / OSV) · observed Jul 15, 2026
GitHub stars on cards: camunda 4.3k · flowable-engine 9.5k (synced Sep 20, 2026).
Common questions
- What is the difference between camunda and flowable-engine?
- camunda: Process Orchestration Framework. flowable-engine: A compact and highly efficient workflow and Business Process Management (BPM) platform. See the comparison table for live GitHub stats and shared categories.
- When should I choose camunda over flowable-engine?
- Choose camunda over flowable-engine when Tags unique to camunda: grpc, microservices, orchestration-framework; - For projects requiring integration of standardized BPMN processes within a microservices architecture; More recently updated (last pushed Sep 15, 2026).
- When should I choose flowable-engine over camunda?
- Choose flowable-engine over camunda when When your project requires extensive integration with existing Java applications without adding significant overhead; More GitHub stars (9.5k vs 4.3k) - visibility, not fit.
- When should I avoid camunda?
- - Avoid if the project requires non-BPMN process models or languages that are not natively supported within Camunda's framework - Not suitable for teams looking to minimize technology stack, as its ecosystem includes several components like Zeebe, Operate, Tasklist which might increase complexity
- When should I avoid flowable-engine?
- If you need a BPM solution that heavily relies on graphical process design tools, as Flowable-engine may not cater to non-technical users as intuitively as some competitors. In scenarios needing extensive support for custom programming languages outside of Java, as this could limit its applicability and efficacy.
- Is camunda or flowable-engine more popular on GitHub?
- flowable-engine has more GitHub stars (9,535 vs 4,279). Stars measure visibility, not whether either tool fits your constraints.
- Are camunda and flowable-engine open source?
- Yes - both are open-source projects on GitHub.
- Where can I find alternatives to camunda or flowable-engine?
- GraphCanon lists graph-backed alternatives at camunda alternatives and flowable-engine alternatives (camunda markdown twin, flowable-engine markdown twin), ranked by typed relationship edges rather than popularity votes.
- Is there a machine-readable version of this comparison?
- Yes. The markdown twin at this comparison mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers.
- Which is better maintained, camunda or flowable-engine?
- camunda: Very active. flowable-engine: Very active. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance.
- Where are the full trust reports for camunda and flowable-engine?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: camunda trust report; flowable-engine trust report.