--- title: "camunda vs workflow-core" type: "comparison" canonical_url: "https://www.graphcanon.com/compare/camunda-camunda-vs-danielgerlag-workflow-core" tools: ["camunda-camunda", "danielgerlag-workflow-core"] --- # camunda vs workflow-core *GraphCanon updated Sep 20, 2026* ## 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. [camunda](https://camunda.com/platform/) reports 4.3k GitHub stars, 819 forks, and 2.8k open issues, last pushed Sep 15, 2026. [workflow-core](https://github.com/danielgerlag/workflow-core) has 5.9k stars, 1.3k forks, and 133 open issues, last pushed Sep 14, 2026. Figures are from public GitHub metadata via [camunda's repository](https://github.com/camunda/camunda) and [workflow-core's repository](https://github.com/danielgerlag/workflow-core). | | [camunda](/tools/camunda-camunda.md) | [workflow-core](/tools/danielgerlag-workflow-core.md) | | --- | --- | --- | | Tagline | Process Orchestration Framework | Lightweight workflow engine for .NET Standard | | Stars | 4,279 | 5,924 | | Forks | 819 | 1,263 | | Open issues | 2,829 | 133 | | Language | Java | C# | | Adopt for | 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 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 | - | - | | Runtime | - | - | | License | - | MIT | | Categories | Developer Tools | Developer Tools | ## Trust and health _Sourced signals - not a safety guarantee. No winner column._ | | [camunda](/tools/camunda-camunda.md) | [workflow-core](/tools/danielgerlag-workflow-core.md) | | --- | --- | --- | | Open issues (now) | 2.8k | 133 | | Stars delta | +41 (30d) | +13 (30d) | | Open issues delta | -73 (30d) | -85 (30d) | | Owner type | Organization | User | | Full report | [trust report](/tools/camunda-camunda/trust.md) | [trust report](/tools/danielgerlag-workflow-core/trust.md) | ## Decision facts: camunda - **Adopt for:** 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. ## Decision facts: workflow-core - **Adopt for:** 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. ## Choose when ### 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 ### 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 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 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 ## 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](/tools/camunda-camunda/alternatives) and [workflow-core alternatives](/tools/danielgerlag-workflow-core/alternatives) ([camunda markdown twin](/tools/camunda-camunda/alternatives.md), [workflow-core markdown twin](/tools/danielgerlag-workflow-core/alternatives.md)), 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](/compare/camunda-camunda-vs-danielgerlag-workflow-core.md) 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](/tools/camunda-camunda/trust); [workflow-core trust report](/tools/danielgerlag-workflow-core/trust). --- **Machine-readable endpoints** - JSON: [`/api/graphcanon/graph?tool=camunda-camunda`](/api/graphcanon/graph?tool=camunda-camunda) - LLM index: [/llms.txt](/llms.txt) - Full corpus: [/llms-full.txt](/llms-full.txt) _GraphCanon - The knowledge graph for AI development. https://www.graphcanon.com/_