Inngest
A weekend of work, and real gaps remain.
Durable background functions: steps that survive restarts, retries, sleeps that can last days, and events that fan out to many handlers.
Build a durable job queue. The step log is the whole idea. STACK - Postgres, one worker process A RUN IS A ROW - Written before the first step, with status and payload - Each step appends its input, output and duration; a completed step is never re-run - On restart, the worker replays from the last completed step. That single rule is durable execution SLEEPING - A sleep is a status of waiting and a wake-at timestamp, not a setTimeout - A process restart must not lose it RETRIES - Exponential backoff with a cap, then a dead-letter row keeping the original payload - Idempotency keys on anything that writes to a third party CONCURRENCY - A limit per function, enforced by SELECT FOR UPDATE SKIP LOCKED Include the run schema, the replay logic and the concurrency query.
What you lose
- Durable execution, where a function sleeping for three days resumes exactly where it stopped after a deploy
- Concurrency and throttling controls per function
- A run history showing every step's input and output
If you would rather not build
- A Postgres job table, which is what the prompt builds
The escape hatch
open source · no votes, no paid placement
Temporal
$0Durable execution as a platform, self-hostable but operationally serious.
temporalio/temporalfree · open source
BullMQ
$0A Redis-backed job queue with retries, delays and concurrency.
taskforcesh/bullmqfree · open source
Why this verdict
our own opinion · changed only by a person
58/100
Verdict kinda at 58. Durable execution is a step log and a replay rule; getting it right is a weekend, and the run history is what makes it debuggable.
History
tracked since 10 Aug 2026 · nothing is ever overwritten
Nothing recorded yet. This chart fills in once the page has visitors, votes or prompt copies — it will not draw a flat line to look busy.
Questions about Inngest
answered from the record above
Is Inngest free?
No — the plan we track is $75 a month. Basic from around $75/month billed monthly, priced on runs and concurrency.
Can you replace Inngest by building your own?
ALMOST. A weekend of work, and real gaps remain. Replacement score 58 out of 100, build time a weekend. Read what you lose before you decide.
How much does Inngest cost?
$75 a month on Basic — $900 a year. Recorded 10 Aug 2026.
What do you lose by replacing Inngest?
Durable execution, where a function sleeping for three days resumes exactly where it stopped after a deploy; Concurrency and throttling controls per function; A run history showing every step's input and output. If any of those carry weight for you, keep paying.
Is there an open-source alternative to Inngest?
Yes: Temporal, BullMQ. The prompt on this page is for when you want it your way instead.
Related entries
same category first, most replaced first
Every week, something stops being worth paying for.
New verdicts, prices that moved, entries added. One email a week. Unsubscribe in one click.
free forever · no tracking pixel · every prompt stays free on the site