Trigger.dev vs Inngest 2026: OSS Durable Runners Compared
Trigger.dev (2022, London) is a fully Apache 2.0 durable runner with task-based authoring, machine-size selection, and first-class self-host. Inngest (2021, San Francisco) is a developer-first event-driven step platform with an open-source dev server and a managed cloud (50K step runs/month free, Pro from $99/month). This 2026 comparison covers license, programming model, pricing, observability, and self-host options.
The Bottom Line: Trigger.dev wins on Apache 2.0 license and first-class self-host; Inngest wins on event-driven step semantics and zero-ops managed cloud. Choose by license requirement and programming-model preference.
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)
| Tier | Trigger.dev | Inngest |
|---|---|---|
| Free | Hobby tier with limited runs and machine hours | 50,000 step runs/month, 3 concurrent runs |
| Entry | Pro from $20/month, additional run and machine fees | Hobby $20/month, 200K steps |
| Mid | Pro tiers scale by run volume and machine size | Pro $50-$500/month tiers |
| Scale | Enterprise self-host (Apache 2.0) | Enterprise quote, self-host option on plan |
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.
Tools Mentioned
Trigger.dev
Open-source background jobs and durable workflows platform for TypeScript developers.
Workflow AutomationInngest
Durable workflow and background job platform for TypeScript and Python services.
Workflow AutomationHatchet
Open-source distributed task queue and workflow engine for Python, TypeScript, and Go services.
Workflow AutomationTemporal Workflows
Build applications that never lose state, even when everything else fails.
Workflow AutomationRelated Guides
Keystroke vs n8n in 2026: Agent-Built TypeScript vs the Visual Canvas
Keystroke, launched in July 2026 by Y Combinator W24 company Sprint Labs, is a code-first automation platform where AI coding agents write workflows as TypeScript in the user's repository. n8n, founded in 2019, is the most widely deployed source-available visual workflow platform, with 200,000+ users and a $2.5 billion valuation. This comparison covers the agent-authored versus canvas building models, durable execution, licensing (Elastic License 2.0 vs the Sustainable Use License), verified July 2026 pricing including Keystroke's usage metering, and the maturity gap between a days-old platform and an established ecosystem.
QuantumBPM vs Camunda 2026: Single-Binary Challenger vs the BPMN Incumbent
QuantumBPM (launched 2026, Coroid s.r.o., Slovakia) packages a BPMN 2.0 runtime and DMN 1.5 decision engine into one Go binary backed by Temporal and PostgreSQL. Camunda (Berlin, founded 2013) is the category incumbent: Camunda 7 (Apache 2.0, in maintenance) and the Zeebe-based Camunda 8 platform. This comparison covers product structure, architecture, DMN TCK conformance with recording dates, deployment, pricing, and vendor maturity, verified July 2026.
Migrating 23 Make Scenarios to Self-Hosted n8n: a 3-Week Breakdown
Anonymized retrospective of a DTC ecommerce brand migrating 23 Make scenarios to a self-hosted n8n instance over three weeks. Tooling cost dropped from $348/month on Make Teams to roughly $12/month on a Hetzner VPS, but credential and webhook recreation consumed about 40% of total project time.
Related Rankings
Best Durable Workflow Engines for Production in 2026
A ranked list of the best durable workflow engines for production deployments in 2026. Durable workflow engines persist execution state to a database so that long-running workflows survive process restarts, deployments, and infrastructure failures. The ranking covers Temporal, Prefect, Apache Airflow, Camunda, Windmill, and n8n. Tools were evaluated on production reliability, developer experience, scalability, open-source health, and documentation quality. The shortlist intentionally mixes code-first engines (Temporal, Prefect, Airflow) with hybrid visual platforms (Camunda, Windmill, n8n) to reflect how production teams actually choose workflow engines in 2026.
Best No-Code Automation Platforms in 2026
A ranked list of no-code automation platforms in 2026. The ranking covers visual workflow builders that allow non-engineering teams to connect SaaS apps, route data, and add conditional logic without writing code. Entries cover proprietary cloud platforms (Zapier, Make, Pipedream, IFTTT) and open-source visual builders (n8n, Activepieces). Scoring reflects integration breadth, pricing accessibility, visual editor ease, reliability and error handling, and self-hosting availability.
Common Questions
What should teams do now that Relay.app is shutting down?
Relay.app announced on 16 July 2026 that it is shutting down. Free accounts and all their data are permanently deleted after 15 August 2026 at 23:59 PT, and paid accounts after 14 September 2026 at 23:59 PT, with paying customers keeping full access at no charge until that date. Export the workspace archive well before the deadline, because generation can take up to 24 hours and the emailed download link expires after 48; for the human-in-the-loop workflows Relay.app was usually bought for, Zapier and n8n are the only platforms evaluated here where a reviewer can edit an AI draft mid-run without custom development.
How much does Keystroke cost in 2026?
Keystroke offers three tiers as of July 2026: Hobby (free forever, with $1/month of included usage credit), Pro ($20/month, including $20/month of usage credit), and Organization (custom pricing with SSO, RBAC, and audit logs). Usage is metered on every tier: $0.01 per agent or workflow run, $0.005 per empty poll, $0.007 per web search, roughly $0.067 per hour of sandbox compute, and a 1.1x markup on AI model calls unless you bring your own API keys.
What is Keystroke?
Keystroke is a code-first workflow automation and AI agent platform, launched July 13, 2026 by Y Combinator-backed Sprint Labs, that positions itself as an n8n alternative built for AI coding agents. Workflows are written as typed TypeScript in the user's own repository, usually by agents such as Claude Code, Cursor, or Codex, and deployed to Keystroke's managed cloud or self-hosted under the source-available Elastic License 2.0.
Is Keystroke worth it in 2026?
Keystroke earns a provisional 6.5/10 in its July 2026 open alpha: the agent-native TypeScript model is genuinely differentiated and the free Hobby tier makes it safe to trial, but the platform is pre-1.0 (npm at v0.1.98, public repository published July 13, 2026), has no third-party production track record, and its Elastic License 2.0 restricts offering it as a hosted service. Worth trialing for teams that build through coding agents; too young for production-critical workflows.