
Darwin Wu11/29/2023
How we built better observability into Inngest

Aaron Harper11/8/2023
Safer error handling, inspired by Go and Rust

Lauren Craigie5/27/2026
If you're building a platform where every customer request will hit the same OpenAI bill, you need the ability to slice and shape concurrency at a per-tenant level.

Tony Holdstock-Brown5/15/2024
Building the expression engine that powers ephemeral event matching.

Lauren Craigie3/25/2026
Queuing and durable execution are two layers of the same problem. In this post we’ll look at solutions dedicated to each, and when each are most appropriate for what you’re building.

Aaron Harper3/18/2026
Worker threads solve real problems, but they come with constraints that Go, Rust, and Python developers would never expect. Here's what we learned moving Inngest Connect's internals off the main thread.

Sterling Chin6/3/2026
Official Inngest plugins and skills for Claude Code, Codex, Cursor, and whatever agent you already use.

Lauren Craigie2/25/2026
Every durable execution system adds some latency between steps. It's the tax we pay for reliability. Here's how to eliminate it.

Lauren Craigie3/24/2026
fal.ai runs hundreds of models at scale. Inngest orchestrates the workflow around them — retries, async coordination, per-user fairness, and observability. Here's how the two work together to build a full media pipeline.

Dan Farrelly3/17/2026
Use Inngest's step primitives to build resilient, observable AI agents without a heavyweight framework.

Lauren Craigie3/17/2026
How Windmill replaced brittle n8n flows with a durable internal ops agent—Pim—powered by Inngest Connect, context-first design, and a focused toolset.

Riadh Daghmoura3/10/2026
We reduced pressure on our sharded Redis cluster by introducing a gRPC proxy that caches immutable run state and routes consistently by run ID.

Dan Farrelly3/3/2026
Agent runtimes don't need yet another framework — they need a durable, event-driven harness that connects tools, memory, and models on production-grade infrastructure.

Bruno Scheufler7/23/2024
Read about how we rolled our new sharded infrastructure out to production without a millisecond of downtime and how it improved Inngest's overall performance.

Dan Farrelly12/10/2024
Learn what Durable Execution is, how it works, and why it's beneficial to your system.

Charly Poly12/10/2024
Combining step.run() and step.ai.infer() is the best toolset to build reliable AI applications on Serverless while saving on compute.

Sterling Chin4/21/2026
Orchestration has been the undefined pillar of Agent Experience. Stripe Projects just made it core infrastructure.

Aaron Harper4/7/2026
A promise that never resolves is a surprisingly clean way to interrupt an async function.
Darwin Wu11/7/2024
Summary of the queue related issues in October 2024

Darwin Wu5/28/2026
As we scale our datacenter footprint, we consolidated Ansible, libvirt, and NetBox inventory sync into a single Go app—using Inngest events instead of scattered coordination logic.

Andy Lawrence1/15/2026
How we shipped Insights AI, what we learned about building agentic features, and why dogfooding your own infrastructure actually works.

Charly Poly2/19/2026
AI Agents introduce multiple points of failure that traditional retry logic cannot handle. Durable execution provides the automatic state persistence, retries, and workflow resumption that make agents production-ready.

Lauren Craigie4/23/2026
Learn how to build a scalable, multi-step lead enrichment and qualification pipeline using Inngest's durable execution and concurrency controls. Handles tens of thousands of leads per day across multiple enrichment providers, LLM scoring, and CRM writes—without queue sprawl or provisioning overhead.

Mitchell Alderson (guest post)4/16/2026
I built a self-improving agent on Inngest, then learned the hard part wasn't retraining prompts, but stopping the system from gaming its own evaluation.

Lauren Craigie4/16/2026
Inngest is an official launch partner for Stripe Projects—a new agent-first protocol for standing up production stacks without hopping between dashboards, digging around docs, or copying keys.

Jakob Evangelista4/12/2026
Support questions need evidence, not guesses. We built a bot that reads the live thread, searches the docs, finds similar historical tickets, and only then drafts a response.

Lauren Craigie3/9/2026
Add step-level durability to your Next.js AI routes so failures don't restart from zero—each step is independently retryable and memoized.

Tony Holdstock-Brown1/22/2024
Building the Inngest queue - Part I

Bruno Scheufler2/23/2026
How we extracted constraint enforcement into a dedicated service to unlock lower latency, greater scalability, and flow control for Durable Endpoints.

Dan Farrelly4/27/2026
CVE-2026-42047

Darwin Wu, Dan Farrelly10/24/2025
Summary of the incident that caused function execution to fail on October 24, 2025

Tony Holdstock-Brown10/24/2025
Comparing explicit APIs vs magic directives for workflows, queues, and durable execution. Or, directives as an antipattern.

Igor Gassmann5/5/2023
What did we learn from building and shipping our new app with the Next.js 13 App Router?

Linell Bonnette5/1/2026
I was looking for a side project to test some real concurrency. A Commander deck analyzer turned out to be the perfect excuse. Here's how I used Inngest's durable functions and Realtime to fan out parallel steps and stream results live to the UI.

Lakshmi Kasinathan3/20/2026
How we improved reliability of our cron scheduler by rebuilding it on top of our own durable queue primitives.

Inngest3/13/2026
I thought I was good at TypeScript. Refactoring the Inngest SDK proved I was okay at best—and that changed how I think about types forever.

Jacob Heric1/30/2026
We care a lot about developer experience. But it's hard to build beautiful experiences for customers, while grinding through 10-12 second page load times. Here's how—and why—our team migrated from Next.js to Tanstack Start.

Dan Farrelly8/16/2024
A full report on the incident that caused function execution to fail on August 16, 2024 UTC.

Dan Farrelly, Bruno Scheufler4/17/2026
A full report on the incident that caused significant delays in function scheduling and execution for all customers.

Lauren Craigie4/28/2026
Outtake chose Inngest to abstract away the complexity of reliability infrastructure, so they can focus on advancing their agents, not worrying about how they break.

Lauren Craigie4/8/2026
Everyone needs retries. Not everyone needs priority queuing—yet. Here’s what 50,000 users taught me about when teams need to solve which problems, and why.