head to head · open source
Inngest vs obelisk
Inngest has 6,017 GitHub stars, 387 forks, 234 open issues and last shipped yesterday. obelisk has 766 stars, 19 forks, 2 open issues and last shipped 2 days ago. Inngest leads on adoption by 686% (6,017 vs 766 stars). Inngest is written in Go under a custom or non-standard licence; obelisk is written in Rust under AGPL-3.0. Inngest has attracted 6% as many forks as stars, obelisk 2%. 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 | obelisk | |
|---|---|---|
| GitHub stars | ★ 6.0K | ★ 766 |
| License | Custom / other | AGPL-3.0 |
| Written in | Go | Rust |
| Last push | 2026-11-04 | 2026-11-03 |
| Forks | ⑂ 387 | ⑂ 19 |
| 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 obelisk if
- You want the obelisk feature set and don't need the biggest community
- You prefer the AGPL-3.0 license terms
- Your stack matches Rust
- You evaluated both and obelisk 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 obelisk
Obelisk A deterministic workflow engine built on the WASM Component Model. [!WARNING] Pre release : Expect changes in CLI, gRPC, WIT, and database schema. Obelisk in Action The Stargazers app features: A webhook listening to GitHub star events. Activities for interacting with Turso DB, OpenAI, and GitHub. A workflow orchestrating the activities. Obelisk fly.io deployment tool features: A complete workflow for deploying Obelisk apps on fly.io Cleanup / compensating actions on failure What's Included Obelisk Runtime : A single binary executing deterministic workflows, activities, and webhook endpoints, persisting…
read the full obelisk 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 obelisk more popular?
Inngest has 6,017 GitHub stars and obelisk has 766. Inngest has the larger community by that measure.
Are Inngest and obelisk free?
Both are open source. Inngest has no licence declared in this registry, and obelisk is licensed under AGPL-3.0. Both are free to self-host.
What is the difference between Inngest and obelisk?
Inngest is written in Go and obelisk in Rust. 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 obelisk?
Choose Inngest if you want the larger community (6,017 stars) or its Custom / other licence terms. Choose obelisk if its feature set, stack or AGPL-3.0 licence fits better. Both are self-hostable.