Inngest

““ Day AI is a complex network of LLMs, data processing, and 3rd party services. Every component in the system needs to wake up at the right times, run for long periods of time, and react intelligently to behavior in other components. Inngest is like the nervous system for all of that, it makes things reliable by default so we can focus on building. ””

““ Our pipelines have many interdependent components chained together. Lots can go wrong in that workflow—including unpredictable behavior from the models themselves. Inngest gives us fine-grained control over errors, and how they propagate, so we can just focus on what the agents should do, not what to do when they fail. ””

““ Inngest completely transformed how we handle AI orchestration at Cohere. Its intuitive developer experience, built-in multi-tenant concurrency, and flow control allowed us to scale without the complexity of other tools or the need to build custom solutions. What would have taken us a month. ””

“I really liked the Inngest dashboard. I'm often looking for specific customers and PR numbers. I appreciate how easy it is to query for those as well as for specific function names.”

“Compared to what I was doing before, which was essentially tagging everything with trace IDs and doing hardcore grepping , it was much easier to see all the steps and sub-steps triggered by an event”

“Inngest's event and step architecture are essential to cubic. Our Agents trigger numerous nested and parallel steps; The ability to string them together with good traceability and observability is a game-changer!”

“In all honesty, we don't need to use the dashboard much because Inngest just works. So that's great. But we know it's there if an error happens and then we can investigate it, understand why it failed, and recover the information.”

“The good thing about Inngest is that we explicitly say in our codebase: “send an event to Inngest” and then we can check in the dashboard what Inngest reacts to. It's easy to debug and follow the flows of changes in our application this way.”

“Configuration with Inngest is really easy. When we read our code base, we can immediately understand what it is and what it does.”

“We are now sure that as soon as the previous sync has ended, the next ones for this specific space will run immediately and won't be affected by any other user or customer on the platform.”

“We had to hack Google Cloud Tasks to achieve the same capabilities that Inngest offers out of the box, but eventually hit a roadblock achieving pure concurrency. Inngest's Developer Experience is simply incomparable. We are going to gradually migrate most features to use Inngest.”

“LLMs APIs are pretty different than other traditional APIs, which are usually pretty fast and reliable; they are slow and pretty brittle. Inngest makes solving both of those things straightforward!”

“At Ocoya, we were struggling with the complexities of managing our social media and e-commerce workflows. Thanks to Inngest, we were able to simplify our development process, speed up our time to market, and deliver a better customer experience. Inngest has become an essential tool in our tech stack, enabling us to focus on delivering a world-class product to our users.”

“By leveraging Inngest, we've seen a 50% reduction in debugging time. The ability to test complex workflows locally has been a game-changer, giving us confidence that our AI-driven processes will run smoothly in production.”

“As soon as companies release their data, we want to have it in Fey. With our old tool it would take up to a day for them to show up, which was a result of mostly complicated configuration. And with Inngest now it's like almost instant , maximum 30 minutes.”

“The technology we were using before was a lot harder and wasn't as efficient. It was difficult to work with events, it required Python (when Fey's tech stack is JavaScript), and deploying was more annoying since it didn't integrate to Vercel. Inngest made it much easier and as a result, we now get much faster data updates in our application.”

“As soon as companies release their data, we want to have it in Fey. With our old tool it would take up to a day for them to show up. And with Inngest it's almost instant.”

“It means that we can effortlessly have these things running in the background, doing work at the time horizons and level of sophistication that a person would. They can sit there and do stuff without us worrying about the mechanics. That kind of behavior is typically very hard to orchestrate, but for us it was a no-brainer to use Inngest and be done with it.”

“Every system eventually has incidents. Issues with webhook processing? Just replay it, and the rest of the system works like magic. What's satisfying about Inngest's replay feature is how ridiculously good it is. Because workflows trigger other workflows through events, you can see exactly where in the chain something broke. You just go to that spot, click replay, and the whole system resumes. That never gets old for me.”

“For this part of the system, "wait for events" makes our work much easier because we can start a process with many steps, pause it, and then continue when something happens in another part of the system. We can have one process start work, then wait for a completely different process on another computer to finish its task before continuing — it's like magic!”

“Inngest choreographs these services, acting as the orchestration hub that coordinates everything. We use a vendor API for meeting bots that sends a bot to a meeting at a specific time. Inngest handles everything else — processing incoming calendar events, figuring out what to do with the bots, tracking their current state, and more. It's like the nervous system for our entire operation, using our database state and communicating with third-party systems. Everything is ultimately triggered by webhooks from various sources.”

“For anyone who is building multi-step AI agents (such as AutoGPT type systems), I highly recommend building it on top of Inngest's job queue orchestration framework, the traceability it provides out of the box is super useful, plus you get timeouts & retries for free.”

“I wanted to find a solution that would let us just write the code, not manage the infrastructure around queues, concurrency, retries, error handling, prioritization... I don't think that developers should be even configuring and managing queues themselves in 2024.”

“The DX and visibility with Inngest is really incredible. We are able to develop functions locally easier and faster that with our previous queue. Also, Inngest's tools give us the visibility to debug issues much quicker than before.”

“Replays and error handling are so critical. Being able to replay functions is incredibly useful because outcomes can be unpredictable. Whether it's an outage or data inconsistency somewhere that affects function runs, having the ability to retry that work ensures we process everything end-to-end without missing a thing.”