Big news.
Weβre excited to announce our $21m Series A!
Inngest now powers 30B monthly executions, helping product teams build reliable products efficiently, at scale.
As AI moves to production, the need for fast, durable workflows is essential.
Read the announcement postπ
Everybody talks about Context Engineering principles but few show how it works π³οΈ
Letβs build an AI Research Assistant and see how Context Engineering helps make it more reliable and accurate π
Unbreakable workflows meet best-in-class observability. π€πβοΈ
@Inngest, a durable workflow orchestration platform, helps developers build scalable products, like AI workflows, agents, & e-commerce stores, without the complexity of managing infrastructure.
Paul, co-founder of @cubic_dev_ , shared a take thatβll change how you think about AI models
π
β Models know better than you which context they need
β Fewer tools win
β Expect failures: embrace observability and durability from day one
The Inngest DevServer MCP is handy for debugging and testing complex workflows composed of multiple Inngest functions.
Again, with a simple prompt, the AI Assistant will generate the proper event and keep track of the progress and logs of the triggered runs π―
Test your local Inngest Functions without any manual event data crafting β¨
Simply ask βSend a test signup event with email 'alice@example.com' and monitor the function executionβ and follow your AI Assistant results.
Weβre thrilled to release the Inngest DevServer MCP β¨
Youβll no longer need to manually create testing events or manually trigger your Inngest functions via your app.
Test and debug your local Inngest functions directly from Cursor or Claude Code.
Learn howπ
AI agent orchestration has the same reliability challenges as any async workflow. How do you handle retries? Manage state? Debug errors?
Join @Hiteshdotcom and I on Fri Oct 31 @ 12pm ET for a live session on the practical side of building durable agents: x.com/Hiteshdotcom
Ever shipped an AI agent that broke the moment it hit production?
same.
That's why @Hiteshdotcom & @djfarrelly are going live to talk about building durable AI agents & workflows that actually survive production.
We're covering: workflow orchestration, error handling, retries, state management & more.
Join us:
ποΈ Friday, October, 31st, 2025 @ 12PM EST
ποΈ Twitter Space on @Hiteshdotcom
As a gluer of code tools and concepts, I generally like taking things I love and finding other ways of implementing/building them.
@convex_dev is a really good technology so I have been toying with other technologies to get a similar feel
@instant_db w/ @inngest does that!
Explicit >>> magic, and the difference between `ππππ.πππ()` and "πππ π πππππππ " is huge.
We shipped implicit IDs when we created the ππππ.πππ API in 2022. Switched to explicit APIs within months. Here's why:
β No magic compilation. What you write is what you run. With directives, what you write *isn't* what you run.
β Steps = explicit code transactions
β Steps = easy unit test and mock
β Steps = far more powerful API (`ππππ.π ππππ΅πππ΄ππππ`, `ππππ.ππππππ`, etc.)
β Steps = easy change management
β Steps = language agnostic: switch from TS β Go and pick up where you left off
β Explicit functions = insanely powerful flow control
β Explicit functions = fan out
In other words, one compiles your code into routes you never wrote. The other gives you typed functions that do exactly what they say. Here's a deep dive:
Developing apps with Inngest give you time travel superpowers π¦Έ
In just one click or using our API, replay workflows runs to quickly recover from failures β‘
Learn how Windmill and Day AI use it to power their Agents π
On the other hand, Throttling do not drop incoming events, it spread queued runs over time to match a given frequency.
If too many of them are stacked, theyβll get delayed to match the desired frequency.