Do AI agents pick Inngest?
How often agents choose Inngest when a developer needs background jobs & queues — measured across Claude, GPT, Gemini.
95% CI 1%–5%
When developers ask an AI agent for queues, Inngest is picked 2% of the time — ranking #3 of 5 measured across Claude, GPT, Gemini.
1.2M package downloads / week
0 docs in FineWeb · 270 URLs in Common Crawl
4.8M installs / month ▲ 13% MoM
Get the full report
The per-model and per-surface breakdown for Inngest — where it wins, where it loses, and to whom — plus an alert when the Pick Rate moves.
About Inngest
A platform that combines durable execution, event-driven queues, and background jobs without managing infrastructure.
Inngest lets developers write background jobs, scheduled tasks, step functions, and event-driven workflows directly in their existing codebase, with no additional infrastructure to provision or maintain. Functions are triggered by events via HTTP, run with automatic retries, and come with built-in observability through a management UI. It targets teams building on serverless platforms like Next.js, Vercel, Cloudflare Workers, Deno Deploy, and AWS Lambda who need reliable async execution.
Where to start
Install the SDK, define functions using the Inngest client, and serve them through a framework adapter (Next.js, Remix, Redwood, and others are supported). From there, send events to trigger functions and monitor runs through the Inngest dashboard.
The rest of the Background Jobs & Queues ranking
| 1 | BullMQ | 17% |
| 2 | Temporal | 5% |
| 4 | Trigger.dev | 0% |
| 5 | Graphile Worker | 0% |