head to head · open source
Inngest vs Slickflow
Inngest has 6,020 GitHub stars, 389 forks, 234 open issues and last shipped yesterday. Slickflow has 923 stars, 265 forks, 11 open issues and last shipped 4 months ago. Inngest leads on adoption by 552% (6,020 vs 923 stars). Inngest is written in Go under a custom or non-standard licence; Slickflow is written in C# under MIT. Inngest has attracted 6% as many forks as stars, Slickflow 29%. 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 | Slickflow | |
|---|---|---|
| GitHub stars | ★ 6.0K | ★ 923 |
| License | Custom / other | MIT |
| Written in | Go | C# |
| Last push | 2026-11-04 | 2026-06-24 |
| Forks | ⑂ 389 | ⑂ 265 |
| 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 Slickflow if
- You want the Slickflow feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches C#
- You evaluated both and Slickflow 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 Slickflow
Slickflow Current Version: NET8 1. 🤖 AI Powered Workflow Automation SlickFlow: Intelligent Workflow Automation with Large Language Models Slickflow integrates cutting edge Large Language Model (LLM) nodes directly into BPMN workflows, enabling advanced conversational reasoning, RAG (Retrieval Augmented Generation), image understanding and other AI capabilities as first class workflow steps . This transforms traditional workflow systems into dynamic, AI driven orchestration platforms. 1.1 Native LLM Node Integration Add LLM / RAG / Agent nodes into your process diagrams as easily as traditional service tasks…
read the full Slickflow 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 Slickflow more popular?
Inngest has 6,020 GitHub stars and Slickflow has 923. Inngest has the larger community by that measure.
Are Inngest and Slickflow free?
Both are open source. Inngest has no licence declared in this registry, and Slickflow is licensed under MIT. Both are free to self-host.
What is the difference between Inngest and Slickflow?
Inngest is written in Go and Slickflow 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 Slickflow?
Choose Inngest if you want the larger community (6,020 stars) or its Custom / other licence terms. Choose Slickflow if its feature set, stack or MIT licence fits better. Both are self-hostable.