Inngest
Ranked 8 of 12 workflow engines by recommenders
People recommend Inngest for durable retries and observability without touching business logic. The common caveat is that you give up transactional job creation.
People recommend Inngest for durable retries and observability without touching business logic. The common caveat is that you give up transactional job creation.
10 people gave an opinion
- recommend it
- 8
- criticize it
- 2
- approval share
- 80%
Recommended in 6 of 13 months
- November 2025: recommended
- December 2025: not recommended
- January 2026: not recommended
- February 2026: recommended
- March 2026: recommended
- April 2026: recommended
- May 2026: not recommended
- June 2026: not recommended
- July 2026: recommended
- August 2026: not recommended
- September 2026: recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 8 people recommend itNeeds 10 or more, not met.
- 4 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 6 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Durable retries and observability
“adding durable retries and observability with Inngest, all without touching your business logic”
Comment from 20 Jul 2026 in “Make Your AI Agent Durable in 8 Minutes [video]” “Inngest's Durable Endpoints aim to solve the durable API problem without messy DB txns”
Comment from 11 Mar 2026 in “Ask HN: Do you still run Redis and workers just for background jobs?” Named among workflow tools
“Let me introduce you to a few of my friends: Make, Task, Dagu, Windmill, Rivet, Inngest”
Comment from 23 Feb 2026 in “Google restricting Google AI Pro/Ultra subscribers for using OpenClaw” “Rivet, Inngest, OVH/uTask, OVH/cds”
Comment from 23 Feb 2026 in “Aqua: A CLI message tool for AI agents”
What people warn about
Each mark is one comment
Gives up transactional job creation
“It works, but you give up transactional job creation”
Comment from 11 Mar 2026 in “Ask HN: Do you still run Redis and workers just for background jobs?”
Other workflow engines people recommend
The four most recommended other workflow engines, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| Temporal | 138 | 43 | 76% | 12 | 1 yr13 owners | Approved |
| DBOS | 39 | 9 | 81% | 12 | — | Approved |
| Apache Airflow | 18 | 5 | 78% | 10 | — | Approved |
| Restate | 16 | 3 | 84% | 10 | — | Approved |
| InngestThis page | 8 | 2 | 80% | 6 | — | — |
What people said
11 of the 13 comments that mention it, newest first. Each links to the original comment.
“it was so much simpler operationally”
“adding durable retries and observability with Inngest, all without touching your business logic”
“Even Inngest assumes you can write code”
“I use Inngest to manage all the pipelines so things keep processing smoothly”
“Inngest's Durable Endpoints aim to solve the durable API problem without messy DB txns”
“It works, but you give up transactional job creation”
“which sends all your private data to Inngest”
“Rivet, Inngest, OVH/uTask, OVH/cds”
“Let me introduce you to a few of my friends: Make, Task, Dagu, Windmill, Rivet, Inngest”
“really like the APIs you guys have created for defining step functions”
“use inngest to bridge Node and Python services”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.