San Francisco. Built here, running here.

Build forthe lonngrun.

If your code runs for minutes or days, it won't run straight through. Wrap functions in steps that automatically retry, pause, and fan out. Scale instantly, without thinking about infra.

Start Free
An Inngest run trace: a step.run function with a flaky step retrying across three attempts before completing, alongside each step's duration.
Before: the tangle of infrastructure (queues, pubsub, idempotency, error handling, capacity management) you have to build yourself.
After: a single step.run() call replacing all that infrastructure.

Durable doesn't have to be hard.

Orchestrating lonng-running code is tough. But you don't need to wrangle a bunch of extra infrastructure to do it. The Inngest SDK is the fastest way to make any code durable and observable by default.

Because one request is never the finish line.

However it's written, wherever it runs, Inngest makes lonng running jobs (and short sprints), unbreakable.

Start building.

Pick a quickstart

The lonng run. San Francisco.

Lonng-running humans. Lonng running agents.

We're bringing Build for the Lonng Run to San Francisco through coffee, community, and a few opportunities to get moving.

  • The campaign drink at Corgi Café.

    The Lonng Run.

    Find our campaign drink at Corgi Café and follow the lonng run from your cup to your code.

    Starting October 1.

  • The San Francisco bay, looking toward the Golden Gate Bridge.

    Run with us.

    Join the Inngest community for a run in San Francisco. All paces welcome.

    Date TBD

  • Developers working together at an Inngest community event.

    Keep the lonng run going.

    Join us for another opportunity to connect with San Francisco builders.

    Date and venue TBD

Keep building.

Explore the technical ideas behind lonng-running agents and workflows.