Switched from BullMQ

“Almost used BullMQ because that's what everyone uses. Tried Inngest for the message queue instead. Zero broker setup, just functions that trigger when they should. Honestly the best infra decision I've made in months.”

RAG document processing

“We introduced background processing using Inngest. Instead of making users wait while processing large documents, heavy tasks run asynchronously in the background. This keeps the application responsive and improves user experience.”

GenAI cohort build

“We took ChaiBookLM to the next level by wiring up Firecrawl for scraping, Cloudinary for storage, and Inngest for seamless background workflows.”

Agent harnesses

“If you are building a harness for non technical folks, you must understand Durable Execution. I would recommend using Inngest. Give users absolute super powers with agent led workflows.”

Retries & observability

“Moved complex background jobs to Inngest. Retry logic and observability are finally usable.”

Modern AI stack

“In my SaaS I'm using Next.js, Vercel, Supabase, Inngest, and Vercel AI SDK. All the agents run on Inngest triggered through webhooks on different events.”

Tool discovered too late

“For me it's Inngest.”

Inngest vs Temporal

“I've constantly felt like I'm losing my mind because there are a lot of Temporal stans and I have often felt it wasn't it DX wise. Going to try out Inngest soon.”

Durability & retries

“I can't even imagine hand-rolling durability and retries. Inngest has been such a time saver. You guys are killing it.”

Founder stack on a budget

“Use Vercel, Supabase, and Cloudflare. I also recommend Inngest for async automation. My rule of thumb is to keep monthly ops costing less than a single dinner out — that way it stays affordable even with zero income as it ramps up.”

Durable agent primitives

“Step-level scoring you can defer until the real signal arrives is a smart primitive for durable agents.”

Async cost tracking

“We use Inngest to process cost tracking events asynchronously. You send the usage data, and we crunch the numbers in the background. Zero impact on your core app's latency.”

LLM observability

“Used Inngest to add observability to my RAG pipeline — tracking latency, errors, and full input/output logs for every LLM call. Still learning it, but it's already made debugging the pipeline so much easier.”

Agent streaming

“Refactored my AI agent to run on Inngest — LLM calls now go through a background job with real-time streaming instead of blocking on HTTP. Cleaner architecture, better UX.”

Execution data

“Production experiments with granular execution data via Inngest — très cool.”

“Just use Inngest.”

Modern SaaS stack

“The best open source and self-hostable stack: Next.js, shadcn, Drizzle, Hono, better-auth, Inngest. That's what I used to build my boilerplate.”

Event-driven AI pipeline

“Integrated Inngest for background jobs. First event: feature.request.created. This single event triggers the entire AI pipeline — decouples the API from AI execution completely. Retry support built in. No lost jobs.”

Async workflows

“If you're building async workflows, check out Inngest. It's a great tool for background jobs, AI workflows, and agentic applications. Event-driven execution without the complexity of managing queues or cron jobs.”

Self-hosting Inngest

“I'm self-hosting Inngest — super easy to set up. I self-host probably 95% of the whole app stack. On the bright side I didn't even know the internet was down recently worldwide — my app just kept working.”

Compared to Trigger.dev

“Recently tried Inngest for background jobs with NestJS and I was impressed! I've found the APIs cleaner than Trigger.dev, and in our case we didn't want to run our jobs in a separate cloud for security issues, and Inngest allows to call HTTP endpoints on your own infra.”

Background jobs on Vercel

“I was skeptical of all the durable execution frameworks popping up the last couple years — but after a few weeks using Inngest, I have to admit — I'm totally sold. It's really easy to deploy frontend apps on Vercel, but there's always been this gap for background jobs. Inngest is now filling that gap for a lot of my use cases.”