Inngest

With Inngest, functions are triggered by events or schedules and broken into steps (step.run, step.sleep, step.waitForEvent). Each step is retried and memoized independently, so long-running workflows survive failures and deploys without managing queues or workers. Inngest calls your existing HTTP endpoints, which makes it work on serverless platforms such as Vercel, Netlify or AWS Lambda as well as on long-running servers. Flow control features like concurrency limits, throttling, debouncing, rate limiting and prioritization are built in, and a local Dev Server provides a UI for testing.