Comparison
workflow-core vs agent-framework
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.
Markdown twin · workflow-core alternatives · agent-framework alternatives
GraphCanon updated Sep 20, 2026
8views this month
Trust & integrity
| Signal | workflow-core | agent-framework |
|---|---|---|
| Maintenance | Very active (0d since push) As of Sep 15, 2026 · github_public_v1 | Very active (0d since push) As of Sep 18, 2026 · github_public_v1 |
| Provenance | Not a fork · Personal account As of Sep 15, 2026 · github_public_v1 | Not a fork · Organization account As of Sep 18, 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
- workflow-core
- Lightweight workflow engine for .NET Standard
- agent-framework
- Framework for building and deploying AI agents and multi-agent workflows
Stars
- workflow-core
- 5.9k
- agent-framework
- 14k
Forks
- workflow-core
- 1.3k
- agent-framework
- 2.3k
Open issues
- workflow-core
- 133
- agent-framework
- 605
Language
- workflow-core
- C#
- agent-framework
- Python
Adopt for
- 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.
- agent-framework
- The agent-framework provides tools for developers to build and deploy AI agents and multi-agent workflows in Python and .NET environments.
Persona
- workflow-core
- -
- agent-framework
- -
Runtime
- workflow-core
- -
- agent-framework
- -
License
- workflow-core
- MIT
- agent-framework
- MIT
Last pushed
- workflow-core
- Sep 14, 2026
- agent-framework
- Sep 18, 2026
Categories
- workflow-core
- Developer Tools
- agent-framework
- AI Agents, Developer Tools
Trust and health
Open issues (now)
- workflow-core
- 133
- agent-framework
- 605
Stars delta
- workflow-core
- +13 (30d)
- agent-framework
- +855 (30d)
Open issues delta
- workflow-core
- -85 (30d)
- agent-framework
- -80 (30d)
Owner type
- workflow-core
- User
- agent-framework
- Organization
Full report
- workflow-core
- Trust report
- agent-framework
- Trust report
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
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
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 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.
Explore
Sources
Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.
- 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 (microsoft/agent-framework) · observed Sep 20, 2026
- GitHub forks (microsoft/agent-framework) · observed Sep 20, 2026
- Last push (microsoft/agent-framework) · observed Sep 18, 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: workflow-core 5.9k · agent-framework 14k (synced Sep 20, 2026).
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 and agent-framework alternatives (workflow-core markdown twin, agent-framework 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, 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; agent-framework trust report.