Inngest is the reliability layer for modern applications. It combines durable execution, events, and queues into a zero-infra platform with built-in observability.

Works with:

Read the documentation and get started in minutes.

On any serverless platform (Next.js, Deno Deploy, RedwoodJS, AWS Lambda, and anything else) and with no extra infrastructure:

• ⚡ Write background jobs
• 🕐 Create scheduled and cron jobs
• ♻️ Build serverless queues
• 🪜 Write complex step functions
• 🚘 Build serverless event-driven systems
• 🪝 Reliably respond to webhooks, with retries and payloads stored for history

👋 Have a question or feature request? Join our Discord!

Getting started · Features · Version support · Contributing · Documentation

Getting started

Install Inngest:

npm install inngest

Or get it from JSR:

deno add jsr:@inngest/sdk

Writing functions

Write serverless functions and background jobs right in your own code:

import { Inngest } from "inngest";

const inngest = new Inngest({ id: "my-app" });

// This function will be invoked by Inngest via HTTP any time
// the "app/user.signup" event is sent to to Inngest
export default inngest.createFunction(
  { id: "user-onboarding-communication" },
  { event: "app/user.signup" },
  async ({ event, step }) => {
    await step.run("Send welcome email", async () => {
      await sendEmail({
        email: event.data.email,
        template: "welcome",
      });
    });
  }
);

• Functions are triggered by events which can be sent via this SDK, webhooks, integrations, or with a simple HTTP request.
• When a matching event is received, Inngest invokes the function automatically, with built-in retries.

Serving your functions

Inngest invokes functions via HTTP, so you need to serve them using an adapter for the framework of your choice. See all frameworks here in our docs. Here is an example using the Next.js serve handler:

// /pages/api/inngest.ts
import { Inngest } from "inngest";
// See the "inngest/next" adapter imported here:
import { serve } from "inngest/next";
import myFunction from "../userOnboardingCOmmunication"; // see above function

// You can create this in a single file and import where it's needed
const inngest = new Inngest({ id: "my-app" });

// Securely serve your Inngest functions for remote invocation:
export default serve(inngest, [myFunction]);

Sending events to trigger functions

// Send events
import { Inngest } from "inngest";
const inngest = new Inngest({ id: "my-app" });

// This will run the function above automatically, in the background
inngest.send("app/user.signup", {
  data: { email: "text@example.com", user_id: "12345" },
});

• Events can trigger one or more functions automatically, enabling you to fan-out work.
• Inngest stores a history of all events for observability, testing, and replay.

Features

• Fully serverless: Run background jobs, scheduled functions, and build event-driven systems without any servers, state, or setup
• Works with your framework: Works with Next.js, Redwood, Express, Cloudflare Pages, Nuxt, Fresh (Deno), and Remix
• Deploy anywhere: Keep deploying to your existing platform: Vercel, Netlify, Cloudflare, Deno, Digital Ocean, etc.
• Use your existing code: Write functions within your current project and repo
• Fully typed: Event schemas, versioning, and governance out of the box
• Observable: A full UI for managing and inspecting your functions

Version support

The library works across browsers, Bun, Deno, Node, and Cloudflare Workers.

We support the LTS versions of these runtimes and the last 3 minor versions of TypeScript; once a runtime version drops out of LTS, any major, minor, or patch update to the inngest library may drop support for it, which will be mentioned in the patch notes.

Contributing

Check out CONTRIBUTING.md to get started.