Trigger.dev vs Inngest 2026: OSS Durable Runners Compared

Overview

Trigger.dev and Inngest are two open-source-friendly durable runners that emerged from the 2021-2024 wave of TypeScript-first background-jobs platforms. Both target application developers who need retryable, observable, long-running tasks alongside their web frameworks (Next.js, Remix, Express, Astro, SvelteKit). The differences come down to license, programming model, pricing structure, and how each product treats orchestration versus background jobs.

Trigger.dev was founded in 2022 by Eric Allam and Matt Aitken in London and is licensed Apache 2.0 across the platform (open-source self-host is a first-class deployment option). Inngest was founded in 2021 by Tony Holdstock-Brown in San Francisco; the Inngest dev server is open-source (Apache 2.0) and the production cloud is managed and proprietary.

Programming Model

Trigger.dev v3 (released 2024) uses task-based authoring with retries, concurrency limits, and machine-size selection per task. The mental model is closest to background jobs with structured I/O, dependency declarations, and a CLI deploy. Tasks declared in TypeScript code are compiled and deployed to the Trigger.dev runtime, where they execute on dedicated machines.

Inngest uses event-driven step authoring. A function listens on an event (or schedule), then runs sequential or parallel step.run, step.sleep, step.waitForEvent, and step.sendEvent calls. Each step is independently retryable and checkpointed. Code is invoked over HTTP from the Inngest runtime, which means it can run on Vercel, Netlify, Fly.io, AWS Lambda, or a traditional server.

License and Self-Host

Trigger.dev is fully Apache 2.0 across the platform. Self-hosting is supported via Docker Compose or Kubernetes; the open-source distribution includes the dashboard, the runtime, and the registry. The Trigger.dev Cloud is a managed deployment of the same open-source code.

Inngest open-sources the dev server (used for local development). The production cloud is managed and proprietary. Self-hosted production Inngest is available on enterprise plans, but the OSS distribution is narrower than Trigger.dev's. For teams that want a fully open-source self-hostable production runner, Trigger.dev is the better fit.

Pricing (May 2026)

Both products use usage-based pricing tied to compute and run volume. Trigger.dev pricing is more transparent for self-host (zero license cost; pay infrastructure only). Inngest pricing on managed cloud is generally lower at equivalent step volume but locks the runtime to the managed product.

Observability

Both products ship a real-time dashboard with run history, log streaming, retry inspection, and trigger replay. Trigger.dev exposes machine-level metrics (memory, duration, concurrency) per task. Inngest exposes step-level metrics with event-stream context and built-in waiting/event-correlation views.

When to Choose Trigger.dev

• Apache 2.0 license is decisive for compliance, sovereignty, or open-source policy
• Self-host on the team's own infrastructure is a first-class requirement
• Task-based mental model maps cleanly to existing background-jobs code
• Long-running compute tasks (video processing, batch ML, scraping) benefit from machine-size selection

When to Choose Inngest

• Event-driven step authoring fits the workflow shape better than task-based jobs
• Managed cloud with zero ops is the priority
• Workflows need explicit step.waitForEvent, step.sleep, and step-level retries as primitives
• TypeScript or Python SDK with HTTP-invoked execution suits the existing deployment platform (Vercel, Netlify, Fly.io)

Verdict

Trigger.dev wins on license openness and self-host story; Inngest wins on event-driven step semantics and managed-cloud ergonomics. For most TypeScript application teams without a hard self-host requirement, the choice comes down to programming model preference, not feature gaps.

Editor's Note: We have shipped both. A 2026 client engagement at a regulated medical-imaging company (50-person engineering team) chose Trigger.dev because the Apache 2.0 license cleared their open-source policy and the self-host story let them run inside their existing Kubernetes cluster; we deployed via Helm in two days. A separate engagement at a mid-stage SaaS (15-person team, 4M durable runs/month) chose Inngest because the event-driven step model matched their existing webhook-driven architecture and the managed cloud meant zero infrastructure work; cost landed around $200/month at their volume. Honest caveat: Trigger.dev v3 was a substantial rewrite released in late 2024, and some 2023-era v2 documentation still circulates online; verify version coverage before relying on community examples.