head to head · open source
Archon vs workflow-core
Archon has 23,495 GitHub stars, 3,474 forks, 321 open issues and last shipped yesterday. workflow-core has 5,926 stars, 1,262 forks, 133 open issues and last shipped 2 days ago. Archon leads on adoption by 296% (23,495 vs 5,926 stars). Archon is written in TypeScript under MIT; workflow-core is written in C# under MIT. Archon has attracted 15% as many forks as stars, workflow-core 21%. Archon was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (workflow-engine), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 8884 open source comparisons
Side by side
| Archon | workflow-core | |
|---|---|---|
| GitHub stars | ★ 23K | ★ 5.9K |
| License | MIT | MIT |
| Written in | TypeScript | C# |
| Last push | 2026-09-17 | 2026-09-16 |
| Forks | ⑂ 3.5K | ⑂ 1.3K |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick Archon if
- You weight community size — 23K stars and counting
- You want the MIT license terms
- Your stack matches TypeScript
- You value the larger contributor base for long-term maintenance
pick workflow-core if
- You want the workflow-core feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches C#
- You evaluated both and workflow-core fits your workflow better
About Archon
Archon is an open source workflow engine for AI coding agents, written in TypeScript and released under the MIT license. It lives in the AI coding ecosystem, alongside tools such as Claude Code, and is distributed through the Bun runtime and the GitHub CLI. The project describes itself as a harness builder: it lets a developer encode a development process as a YAML workflow and then run that workflow reliably across projects. Workflows are stored in a .archon/workflows/ directory and committed to the repository, so the same definition can be invoked from the CLI, a web UI, Slack, Telegram, or GitHub.…
read the full Archon overview →
About workflow-core
Workflow Core is a lightweight, embeddable workflow engine targeting .NET Standard, written in C and released under the MIT license. It lives in the .NET ecosystem, distributed as NuGet packages, and is built around the idea of long running processes that contain multiple tasks and must track their state between steps. Rather than running as a separate server, it is a library that is hosted inside an application, and it exposes a fluent C API for defining workflows. Workflows are expressed as a starting step followed by chained steps, and the same class can declare inputs and outputs that move data from one step …
read the full workflow-core overview →
More in Infrastructure & Operations
Related comparisons
More Orchestration & Scheduling projects
Compare either of these against the rest of the Orchestration & Scheduling field.
Frequently asked questions
Is Archon or workflow-core more popular?
Archon has 23,495 GitHub stars and workflow-core has 5,926. Archon has the larger community by that measure.
Are Archon and workflow-core free?
Both are open source. Archon is licensed under MIT and workflow-core under MIT. Neither carries a licence fee.
What is the difference between Archon and workflow-core?
Archon is written in TypeScript and workflow-core in C#. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, Archon or workflow-core?
Choose Archon if you want the larger community (23,495 stars) or its MIT licence terms. Choose workflow-core if its feature set, stack or MIT licence fits better. Both are self-hostable.