---
title: "workflow-core vs agent-framework"
type: "comparison"
canonical_url: "https://www.graphcanon.com/compare/danielgerlag-workflow-core-vs-microsoft-agent-framework"
tools: ["danielgerlag-workflow-core", "microsoft-agent-framework"]
---

# workflow-core vs agent-framework

*GraphCanon updated Sep 20, 2026*

## Verdict

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; pick agent-framework if the agent-framework provides tools for developers to build and deploy AI agents and multi-agent workflows in Python and .NET environments.

[workflow-core](https://github.com/danielgerlag/workflow-core) reports 5.9k GitHub stars, 1.3k forks, and 133 open issues, last pushed Sep 14, 2026. [agent-framework](https://aka.ms/agent-framework) has 14k stars, 2.3k forks, and 605 open issues, last pushed Sep 18, 2026. Figures are from public GitHub metadata via [workflow-core's repository](https://github.com/danielgerlag/workflow-core) and [agent-framework's repository](https://github.com/microsoft/agent-framework).

| | [workflow-core](/tools/danielgerlag-workflow-core.md) | [agent-framework](/tools/microsoft-agent-framework.md) |
| --- | --- | --- |
| Tagline | Lightweight workflow engine for .NET Standard | Framework for building and deploying AI agents and multi-agent workflows |
| Stars | 5,924 | 13,573 |
| Forks | 1,263 | 2,335 |
| Open issues | 133 | 605 |
| Language | C# | Python |
| 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. | The agent-framework provides tools for developers to build and deploy AI agents and multi-agent workflows in Python and .NET environments. |
| Persona | - | - |
| Runtime | - | - |
| License | MIT | MIT |
| Categories | Developer Tools | AI Agents, Developer Tools |

## Trust and health

_Sourced signals - not a safety guarantee. No winner column._

| | [workflow-core](/tools/danielgerlag-workflow-core.md) | [agent-framework](/tools/microsoft-agent-framework.md) |
| --- | --- | --- |
| Open issues (now) | 133 | 605 |
| Stars delta | +13 (30d) | +855 (30d) |
| Open issues delta | -85 (30d) | -80 (30d) |
| Owner type | User | Organization |
| Full report | [trust report](/tools/danielgerlag-workflow-core/trust.md) | [trust report](/tools/microsoft-agent-framework/trust.md) |

## 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.

## Decision facts: agent-framework

- **Requirements:** Python version 3.6 or newer is required for Python installations.; The .NET Core SDK must be installed for utilizing the .NET packages.
- **Adopt for:** The agent-framework provides tools for developers to build and deploy AI agents and multi-agent workflows in Python and .NET environments.

## Choose when

### Choose workflow-core if…

- workflow-core is primarily C#; agent-framework is Python.
- Tags unique to workflow-core: hacktoberfest, saga, saga-transactions, workflow.
- When you are developing applications in the .NET ecosystem and require a simple yet powerful way to manage business processes with state tracking

### Choose agent-framework if…

- agent-framework is primarily Python; workflow-core is C#.
- Requirements: Python version 3.6 or newer is required for Python installations.; The .NET Core SDK must be installed for utilizing the .NET packages..
- Tags unique to agent-framework: agent-framework, agentic-ai, agents, multi-agent.
- Also covers AI Agents.
- Choose agent-framework if your project requires support for both Python and .NET, allowing you to develop across different ecosystems.

## 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

## When NOT to use agent-framework

- Avoid using the agent-framework if your team does not have proficiency in either Python or.NET, as this may cause difficulties in leveraging its features effectively.
- Do not opt for agent-framework if you only need lightweight support for AI agents without a comprehensive orchestration and deployment framework.

## Common questions

### What is the difference between workflow-core and agent-framework?

workflow-core: Lightweight workflow engine for .NET Standard. agent-framework: Framework for building and deploying AI agents and multi-agent workflows. See the comparison table for live GitHub stats and shared categories.

### When should I choose workflow-core over agent-framework?

Choose workflow-core over agent-framework when workflow-core is primarily C#; agent-framework is Python; Tags unique to workflow-core: hacktoberfest, saga, saga-transactions, workflow; 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 choose agent-framework over workflow-core?

Choose agent-framework over workflow-core when agent-framework is primarily Python; workflow-core is C#; Requirements: Python version 3.6 or newer is required for Python installations.; The .NET Core SDK must be installed for utilizing the .NET packages.; Tags unique to agent-framework: agent-framework, agentic-ai, agents, multi-agent; Also covers AI Agents; Choose agent-framework if your project requires support for both Python and .NET, allowing you to develop across different ecosystems.

### 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

### When should I avoid agent-framework?

Avoid using the agent-framework if your team does not have proficiency in either Python or.NET, as this may cause difficulties in leveraging its features effectively. Do not opt for agent-framework if you only need lightweight support for AI agents without a comprehensive orchestration and deployment framework.

### Is workflow-core or agent-framework more popular on GitHub?

agent-framework has more GitHub stars (13,573 vs 5,924). Stars measure visibility, not whether either tool fits your constraints.

### Are workflow-core and agent-framework open source?

Yes - both are open-source projects on GitHub (workflow-core: MIT, agent-framework: MIT).

### Where can I find alternatives to workflow-core or agent-framework?

GraphCanon lists graph-backed alternatives at [workflow-core alternatives](/tools/danielgerlag-workflow-core/alternatives) and [agent-framework alternatives](/tools/microsoft-agent-framework/alternatives) ([workflow-core markdown twin](/tools/danielgerlag-workflow-core/alternatives.md), [agent-framework markdown twin](/tools/microsoft-agent-framework/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/danielgerlag-workflow-core-vs-microsoft-agent-framework.md) mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers.

### Which is better maintained, workflow-core or agent-framework?

workflow-core: Very active. agent-framework: 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 workflow-core and agent-framework?

GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: [workflow-core trust report](/tools/danielgerlag-workflow-core/trust); [agent-framework trust report](/tools/microsoft-agent-framework/trust).

---

**Machine-readable endpoints**

- JSON: [`/api/graphcanon/graph?tool=danielgerlag-workflow-core`](/api/graphcanon/graph?tool=danielgerlag-workflow-core)
- 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/_
