head to head · open source
Inngest vs workflow-core
Inngest has 6,012 GitHub stars, 386 forks, 234 open issues and last shipped yesterday. workflow-core has 5,939 stars, 1,261 forks, 133 open issues and last shipped 4 days ago. Inngest leads on adoption by 1% (6,012 vs 5,939 stars). Inngest is written in Go under a custom or non-standard licence; workflow-core is written in C# under MIT. Inngest has attracted 6% as many forks as stars, workflow-core 21%. Inngest 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
| Inngest | workflow-core | |
|---|---|---|
| GitHub stars | ★ 6.0K | ★ 5.9K |
| License | Custom / other | MIT |
| Written in | Go | C# |
| Last push | 2026-11-02 | 2026-10-30 |
| Forks | ⑂ 386 | ⑂ 1.3K |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick Inngest if
- You weight community size — 6.0K stars and counting
- You want the Custom / other license terms
- Your stack matches Go
- 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 Inngest
Inngest's durable functions replace queues, state management, and scheduling to enable any developer to write reliable step functions faster without touching infrastructure. 1. Write durable functions using any of our language SDKs 2. Run the Inngest Dev Server for a complete local development experience, with production parity. 3. Deploy your functions to your own infrastructure 4. Sync your application's functions with the Inngest Platform or a self hosted Inngest server. 5. Inngest invokes your functions securely via HTTPS whenever triggering events are received. An example durable function Inngest Functions…
read the full Inngest 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 Inngest or workflow-core more popular?
Inngest has 6,012 GitHub stars and workflow-core has 5,939. Inngest has the larger community by that measure.
Are Inngest and workflow-core free?
Both are open source. Inngest has no licence declared in this registry, and workflow-core is licensed under MIT. Both are free to self-host.
What is the difference between Inngest and workflow-core?
Inngest is written in Go 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, Inngest or workflow-core?
Choose Inngest if you want the larger community (6,012 stars) or its Custom / other licence terms. Choose workflow-core if its feature set, stack or MIT licence fits better. Both are self-hostable.