Roadmap

Various updates and refreshes to the Inngest docs to improve core guides and provide additional context like how the Inngest SDK + executor work when invoking functions.

Provide better insights regarding workloads for customers

Use Drata to help facilitate SOC 2 compliance process.

Revisiting the core DX of the dev server to improve onboarding, fix issues, and add new functionality around each view: Apps, Functions List, Stream, and the Payload/Function Run view.

We should have a public API, allowing us to do things like: cancelling jobs by run ID; looking up all jobs from an event ID; fetching a single job's status.

Steps should be able to override retry policies and set their own concurrency keys

Tools like superjson are common in the JS ecosystem, allowing users to maintain objects such as dates across network boundaries. The SDK can support these patterns by allowing a "transformer" to serialize/deserialize data passing to/from Inngest.

Allow passing in regions, eg: `eu`, within HTTP headers when sending events, ensuring that all data is parsed, stored, and executed within the specified region.

Arguments input to and output from a serve handler are sometimes needed by a user, for instance to set `callbackWaitsForEmptyEventLoop` in a Lambda environment or change outgoing registration URLs.

Users should be able to try/catch steps that permanently fail, alongside having the function's onFailure error handler run. This lets you write regular idiomatic error handling code.

We should add a library and SDK utilities for mocking SDK steps for each function.

Build an SDK that allows defining Inngest functions using Python.

Build an SDK that allows defining Inngest functions using Python.

Allow full text searching of function output or event data (not including user data, as that's encrypted). This allows you to find eg. an event containing a specific ID.

Implement a durable API layer using SQL within the open-source server to allow E2E self-hosting.

Add the ability for SDK-defined functions to declare multiple triggers, either multiple events, crons, or both.

Add a tool which allows for continual linear subscriptions to an event stream, eg: `step.subscribe("event/name", { if: "xyz == 123", timeout: "10m" }, (acc, async, ctx) => {})`. This lets us listen for all events of a type within a function.

Store function failures and allow full text search (eg. for filtering, which lets us replay specific errors). Categorize errors, eg. for function timeouts, and show smart tips to resolve.

Expose low, normal, and high priorities for functions. Potentially allow replays to have their own priorities (note that if a function has high priority and a replay has high priority, this will be a noop).

Improve account authentication for Inngest including support for multi-factor authentication and SAML SSO. Project will lay groundwork for future auth improvements that may include magic links, WebAuthn, etc.

Allow configuration of step timeouts on a per-step basis, cancelling work if the timeout is reached before steps finish.

Users should be able to reply a single function run or a group of function runs based on a time + status filter query. Both should be achievable via the Inngest dashboard.

Inngest users may have multiple accounts for personal work, their company and/or clients. Users desire to have a single shared login across multiple Inngest, isolated accounts each with separate billing.