“Inngest is powering our background jobs and workflows with ease! Its powerful automation and seamless integration into our development process allow us to focus on building without worrying about infrastructure.”
Background Jobs & CronMaker says so +1 · source ↗
Inngest
Platform for orchestrating durable, event-driven functions and workflows without managing queue infrastructure yourself.
Works with AI agents:llms.txtCLIBuilt into LovableInngest runs background jobs and multi-step workflows for you. Instead of running a queue, workers and a retry scheduler, you send events and Inngest decides which of your functions should run, when, and how many at once.
Your code stays in your own app. You write functions with the TypeScript, Python or Go SDK and break them into named steps; Inngest calls your app over an HTTP endpoint (usually /api/inngest, with handlers for Next.js, Express, Hono, SvelteKit, Cloudflare Workers, Lambda and many more) or over an outbound WebSocket from a long-running worker. Each finished step's result is saved, so a retry or resume skips work that already succeeded.
For a small team the useful parts are: steps that can sleep or wait for another event for days without holding a server, flow control (concurrency, throttling, debouncing, rate limits, batching) set per function, a local Dev Server for development, and a trace of every run. The hosted service runs in the eastern US; the whole system also ships as one open-source binary you can self-host.
Limits to know: individual steps are capped at two hours and by your host's own request timeout, step results at 4 MiB and total run state at 32 MiB, so large payloads belong in your own storage. Python and Go trail TypeScript on newer features, and self-hosted installs get no direct support from the Inngest team.
Where it fits
How Inngest itself is built
8 tools, from its own code, website and Product Hunt page.
Who uses it
16 makers' products, each linked to the source that shows it, and 11 open-source projects that declare it in their code.
“Great integration with the modern Vercel stack!”
Background Jobs & CronMaker says so +1 · source ↗“Inngest is doing all the magic for us!”
Background Jobs & CronMaker says so · source ↗“We also hosted our own Redis-based queue before managing events infra became a job in itself. Inngest has top tier local dev DX and helps our background jobs scale infinitely.”
Background Jobs & CronMaker says so · source ↗“It helped me to create very complex workflows very fast.”
Background Jobs & CronMaker says so · source ↗“Inngest's queuing system is a fantastic improvement over managing queues ourselves - it frees up time so we can spend talking to more customers instead.”
Background Jobs & CronMaker says so · source ↗“Inngest lets us focus on building the app and not working on infra.”
Background Jobs & CronMaker says so · source ↗“Fantastic for background job handling, with first-class observability built in.”
Background Jobs & CronMaker says so · source ↗“All of our async operations run on Inngest. They have the best DX. Super simple to do debouncing, throttling, fanning out, and more. Easy to test in local, and easy to monitor in production.”
Background Jobs & CronMaker says so · source ↗“Queue bookmark, marketing flow and more.”
Background Jobs & CronMaker says so · source ↗“We power all our async workflows with Inngest. You can test everything locally, and get out-of-the-box production monitoring. It’s hands-down the best DX and lets us spend more time serving customers instead of wrangling queues.”
Background Jobs & CronMaker says so · source ↗Open source: a project that declares Inngest as a dependency in its public code — verifiable, but not necessarily a live product.
What makers say
7 makers on why they use Inngest, in their own words on Product Hunt.
Inngest is powering our background jobs and workflows with ease! Its powerful automation and seamless integration into our development process allow us to focus on building without worrying about infrastructure.
ProductlaneSep 2026 ↗All of our async operations run on Inngest. They have the best DX. Super simple to do debouncing, throttling, fanning out, and more. Easy to test in local, and easy to monitor in production.
NorthSep 2026 ↗We also hosted our own Redis-based queue before managing events infra became a job in itself. Inngest has top tier local dev DX and helps our background jobs scale infinitely.
FirstQuadrantSep 2026 ↗Inngest's queuing system is a fantastic improvement over managing queues ourselves - it frees up time so we can spend talking to more customers instead.
CloudglueSep 2026 ↗Fantastic for background job handling, with first-class observability built in.
QA.techSep 2026 ↗Loved and watch-outs
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises, with how Product Hunt tags its reviews.
- It replaces a self-hosted Redis queue and workers, so teams stop running event infrastructure themselves. PHPH 2
- Workflows can be tested locally, and production runs come with tracing and monitoring built in. PHPH 2inngest.com
- Debouncing, throttling and fan-out are simple, making complex multi-step flows such as AI agents quick to build. PHinngest.com
Reliability and open issues
- minor Delayed observability of events Sep 2026
- major Delays with function execution Sep 2026
- major Degraded Function Execution Sep 2026
Alternatives to Inngest
All alternatives by situation →Questions makers ask about Inngest
Do I have to run my functions on Inngest's servers?
No. Your functions run wherever you deploy your app, such as Vercel, Lambda, containers or your own servers; Inngest only schedules them and calls your endpoint or connected worker. source ↗
Which languages are supported?
There are official open-source SDKs for TypeScript (Node.js, Bun, Deno and edge runtimes), Python 3.10+ and Go. TypeScript receives new features first. source ↗
Can I self-host Inngest?
Yes. The Inngest CLI is a single binary (also a Docker image) that contains every service; by default it uses SQLite and an in-memory Redis, and you can point it at external Postgres and Redis. The Inngest team does not offer direct support for self-hosted instances outside enterprise agreements. source ↗
Where is my data processed, and is it SOC 2 compliant?
Inngest Cloud runs in the eastern United States (AWS us-east-2 plus Inngest-operated hardware in Ashburn, Virginia). The company states it is SOC 2 Type II compliant and supports SAML sign-in and end-to-end encryption of step data via middleware. source ↗
How long can a step or a workflow run?
A single step can run up to two hours, but never longer than your hosting provider's timeout. A whole run, including sleeps and waits, is limited by plan, from 30 days on the free plan up to a year on higher plans. source ↗
Is the free plan suitable for production?
Inngest describes its Hobby plan as meant for testing and validating workflows; Hobby accounts receive infrastructure changes first and may see temporary added latency, while paid plans run on isolated infrastructure. The free plan also keeps traces for only 24 hours. source ↗
My endpoint sits behind Vercel Deployment Protection. Will it work?
Inngest's servers must be able to reach your serve endpoint, so you either disable Deployment Protection for it or, on Vercel Pro, configure a protection bypass. Requests are authenticated with your signing key instead. source ↗
Is Inngest free?
Yes — there is a free tier a small product can run on; paid use starts at $99/mo. source ↗
Is Inngest open source or self-hostable?
Open source, and you can self-host it. source ↗
Can AI coding agents work with Inngest?
It serves an llms.txt docs index; it has an official CLI (inngest-cli); Lovable set it up natively.
Who uses Inngest?
16 makers' products we track, each with a source, and 11 open-source projects declare it in their code. source ↗