head to head · open source
workflow-core vs viewflow
workflow-core has 5,939 GitHub stars, 1,260 forks, 133 open issues and last shipped 2 days ago. viewflow has 2,873 stars, 415 forks, 19 open issues and last shipped 7 days ago. workflow-core leads on adoption by 107% (5,939 vs 2,873 stars). workflow-core is written in C# under MIT; viewflow is written in Python under AGPL-3.0. workflow-core has attracted 21% as many forks as stars, viewflow 14%. workflow-core was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 2 topic tags (workflow, 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
| workflow-core | viewflow | |
|---|---|---|
| GitHub stars | ★ 5.9K | ★ 2.9K |
| License | MIT | AGPL-3.0 |
| Written in | C# | Python |
| Last push | 2026-11-03 | 2026-10-29 |
| Forks | ⑂ 1.3K | ⑂ 415 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick workflow-core if
- You weight community size — 5.9K stars and counting
- You want the MIT license terms
- Your stack matches C#
- You value the larger contributor base for long-term maintenance
pick viewflow if
- You want the viewflow feature set and don't need the biggest community
- You prefer the AGPL-3.0 license terms
- Your stack matches Python
- You evaluated both and viewflow fits your workflow better
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 →
About viewflow
Viewflow The low code for developers with yesterday's deadline [![build]][build] [![coverage]][coverage] [![pypi version]][pypi] [![py versions]][pypi] Viewflow is a low code library for building business applications with Django. It gives you ready made components for user management, workflows, and reporting. You write less code but keep full control. You can customize everything and connect it to your existing systems. Build full featured business applications in a few lines of code. Viewflow ships as one package with everything included. Each part works on its own, but they all work well together. GPT…
read the full viewflow 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 workflow-core or viewflow more popular?
workflow-core has 5,939 GitHub stars and viewflow has 2,873. workflow-core has the larger community by that measure.
Are workflow-core and viewflow free?
Both are open source. workflow-core is licensed under MIT and viewflow under AGPL-3.0. Neither carries a licence fee.
What is the difference between workflow-core and viewflow?
workflow-core is written in C# and viewflow in Python. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, workflow-core or viewflow?
Choose workflow-core if you want the larger community (5,939 stars) or its MIT licence terms. Choose viewflow if its feature set, stack or AGPL-3.0 licence fits better. Both are self-hostable.