Comparison
camunda vs workflow-core
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 workflow-core if workflow-core is a lightweight workflow engine designed for .NET Standard environments, providing support for workflows and saga transactions in C#. It's open-source under the MIT License.
Markdown twin · camunda alternatives · workflow-core alternatives
GraphCanon updated Sep 20, 2026
7views this month
vs
Trust & integrity
| Signal | camunda | workflow-core |
|---|---|---|
| Maintenance | Very active (0d since push) As of Sep 15, 2026 · github_public_v1 | Very active (0d since push) As of Sep 15, 2026 · github_public_v1 |
| Provenance | Not a fork · Organization account As of Sep 15, 2026 · github_public_v1 | Not a fork · Personal account As of Sep 15, 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
- workflow-core
- Lightweight workflow engine for .NET Standard
Stars
- camunda
- 4.3k
- workflow-core
- 5.9k
Forks
- camunda
- 819
- workflow-core
- 1.3k
Open issues
- camunda
- 2.8k
- workflow-core
- 133
Language
- camunda
- Java
- workflow-core
- C#
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.
- workflow-core
- workflow-core is a lightweight workflow engine designed for .NET Standard environments, providing support for workflows and saga transactions in C#. It's open-source under the MIT License.
Persona
- camunda
- -
- workflow-core
- -
Runtime
- camunda
- -
- workflow-core
- -
License
- camunda
- -
- workflow-core
- MIT
Last pushed
- camunda
- Sep 15, 2026
- workflow-core
- Sep 14, 2026
Categories
- camunda
- Developer Tools
- workflow-core
- Developer Tools
Trust and health
Open issues (now)
- camunda
- 2.8k
- workflow-core
- 133
Stars delta
- camunda
- +41 (30d)
- workflow-core
- +13 (30d)
Open issues delta
- camunda
- -73 (30d)
- workflow-core
- -85 (30d)
Owner type
- camunda
- Organization
- workflow-core
- User
Full report
- camunda
- Trust report
- workflow-core
- Trust report
Choose camunda if…
- camunda is primarily Java; workflow-core is C#.
- Tags unique to camunda: bpmn, grpc, java, microservices.
- - For projects requiring integration of standardized BPMN processes within a microservices architecture
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 workflow-core if…
- workflow-core is primarily C#; camunda is Java.
- Tags unique to workflow-core: hacktoberfest, saga, saga-transactions.
- When you are developing applications in the .NET ecosystem and require a simple yet powerful way to manage business processes with state tracking
When NOT to use workflow-core
- If your project requires integration with non-.NET technologies for workflow management
- When complex workflows and extensive customization options are needed that exceed the capabilities of a lightweight library like workflow-core
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 (danielgerlag/workflow-core) · observed Sep 20, 2026
- GitHub forks (danielgerlag/workflow-core) · observed Sep 20, 2026
- Last push (danielgerlag/workflow-core) · observed Sep 14, 2026
- License file (MIT) · 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 · workflow-core 5.9k (synced Sep 20, 2026).
Common questions
- What is the difference between camunda and workflow-core?
- camunda: Process Orchestration Framework. workflow-core: Lightweight workflow engine for .NET Standard. See the comparison table for live GitHub stats and shared categories.
- When should I choose camunda over workflow-core?
- Choose camunda over workflow-core when camunda is primarily Java; workflow-core is C#; Tags unique to camunda: bpmn, grpc, java, microservices; - For projects requiring integration of standardized BPMN processes within a microservices architecture.
- When should I choose workflow-core over camunda?
- Choose workflow-core over camunda when workflow-core is primarily C#; camunda is Java; Tags unique to workflow-core: hacktoberfest, saga, saga-transactions; When you are developing applications in the .NET ecosystem and require a simple yet powerful way to manage business processes with state tracking.
- 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 workflow-core?
- If your project requires integration with non-.NET technologies for workflow management When complex workflows and extensive customization options are needed that exceed the capabilities of a lightweight library like workflow-core
- Is camunda or workflow-core more popular on GitHub?
- workflow-core has more GitHub stars (5,924 vs 4,279). Stars measure visibility, not whether either tool fits your constraints.
- Are camunda and workflow-core open source?
- Yes - both are open-source projects on GitHub.
- Where can I find alternatives to camunda or workflow-core?
- GraphCanon lists graph-backed alternatives at camunda alternatives and workflow-core alternatives (camunda markdown twin, workflow-core 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 workflow-core?
- camunda: Very active. workflow-core: 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 workflow-core?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: camunda trust report; workflow-core trust report.