Inngest

Docs › Introduction › Get started

Overview

Run your first durable workflow, Sandbox, online eval, or live update.

Start with the area you need first: durable functions coordinate work, sandboxes run code in isolation, agent evals connect outcomes to runs, and realtime sends progress to your users.

Start the Dev Server

Every quick start runs locally against the Inngest Dev Server. It records your events and runs, and shows each run's trace at http://localhost:8288.

Start the Dev Server with one of the commands below:

Bash installer
curl -sSfL https://cli.inngest.com/install.sh | sh
inngest dev -u http://localhost:3000/api/inngest
Brew
brew install inngest/tap/inngest
inngest dev -u http://localhost:3000/api/inngest
NPX
npx --ignore-scripts=false inngest-cli@latest dev

# -u supplies the app URL when discovery does not find it.
npx --ignore-scripts=false inngest-cli@latest dev -u http://localhost:3000/api/inngest
Docker
docker run -p 8288:8288 -p 8289:8289 inngest/inngest \
  inngest dev -u http://host.docker.internal:3000/api/inngest

Pick a quick start

Build a durable workflow

Send an event, run a saved step, and inspect the run locally. Choose TypeScript, Go, or Python.

inngest.com
Run code in a Sandbox

Create an isolated microVM, run a command, and inspect its output in the run trace. Sandbox beta access is required.

inngest.com
Measure an outcome

Score a response, compare variants, and connect later feedback to the run that served it. Scoring uses TypeScript SDK v4 beta APIs.

inngest.com
Show live progress

Publish updates from a durable function to a signed-in user's browser.

inngest.com

Choose a language for your first workflow

The Durable Execution quick start has separate guides for TypeScript, Go, and Python. Each sends the same event and shows the resulting run.

Read What is Inngest? first if you want to see how these capabilities fit together before writing code.

Updated Nov 10, 2026

Powered byZunoy