head to head · open source
Archon vs workflow-core
Archon has 23,800 GitHub stars, 3,517 forks, 321 open issues and last shipped 3 days ago. workflow-core has 5,939 stars, 1,261 forks, 133 open issues and last shipped 4 days ago. Archon leads on adoption by 301% (23,800 vs 5,939 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 20902 open source comparisons
Side by side
| Archon | workflow-core | |
|---|---|---|
| GitHub stars | ★ 24K | ★ 5.9K |
| License | MIT | MIT |
| Written in | TypeScript | C# |
| Last push | 2026-10-31 | 2026-10-30 |
| Forks | ⑂ 3.5K | ⑂ 1.3K |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick Archon if
- You weight community size — 24K 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 The first open source harness builder for AI coding. Make AI coding deterministic and repeatable. Archon is a workflow engine for AI coding agents. Define your development processes as YAML workflows planning, implementation, validation, code review, PR creation and run them reliably across all your projects. Like what Dockerfiles did for infrastructure and GitHub Actions did for CI/CD Archon does for AI coding workflows. Think n8n, but for software development. Why Archon? When you ask an AI agent to "fix this bug", what happens depends on the model's mood. It might skip planning. It might forget to run…
read the full Archon overview →
About workflow-core
Workflow Core Workflow Core is a light weight embeddable workflow engine targeting .NET Standard. Think: long running processes with multiple tasks that need to track state. It supports pluggable persistence and concurrency providers to allow for multi node clusters. Announcements New related project: Conductor Conductor is a stand alone workflow server as opposed to a library that uses Workflow Core internally. It exposes an API that allows you to store workflow definitions, track running workflows, manage events and define custom steps and scripts for usage in your workflows. Documentation See Tutorial here…
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,800 GitHub stars and workflow-core has 5,939. 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,800 stars) or its MIT licence terms. Choose workflow-core if its feature set, stack or MIT licence fits better. Both are self-hostable.