Can you self-host Trigger.dev in 2026?
Quick Answer: Yes. Trigger.dev is open-source under the Apache 2.0 license and supports self-hosting via Docker Compose or Kubernetes. Self-hosting gives you full control over your job runs and data, but you take on operating Postgres, Redis, the worker queue, and the dashboard yourself.
Self-Hosting Trigger.dev (as of May 2026)
Trigger.dev is an open-source background-job platform aimed at developers building AI and integration workflows. The project is licensed under Apache 2.0, and the maintainers publish official self-hosting instructions.
Components You Run
A self-hosted Trigger.dev deployment includes:
- Web app and API (Next.js)
- Postgres for jobs, runs, schedules, and account data
- Redis for the queue and transient state
- Worker process(es) that execute job runs
- A reverse proxy (Caddy or nginx) for TLS
For a small team, all of this fits comfortably on a single VPS (4 GB RAM is the practical minimum). For higher load, the workers scale horizontally.
Deployment Options
- Docker Compose for single-host deployments (the official quickstart).
- Kubernetes with the published Helm chart for HA deployments.
- PaaS deployments (Render, Railway, Fly.io) using the published images.
Cloud vs Self-Hosted Trade-offs
| Aspect | Trigger.dev Cloud | Self-Hosted |
|---|---|---|
| Setup time | minutes | a few hours for first deployment |
| Ongoing maintenance | none | Postgres backups, Redis, upgrades, TLS |
| Data residency | US / EU regions | wherever you host |
| Pricing | metered runs + plan fee | infrastructure cost only |
| Updates | automatic | you pull and deploy |
| Support | included with paid plans | community + GitHub |
When to Self-Host
- The team has data-residency or compliance requirements that exclude SaaS.
- The job volume is large enough that Cloud pricing exceeds infrastructure cost.
- The team wants to extend the platform with custom integrations or changes.
When NOT to Self-Host
- For small teams without ops capacity, Trigger.dev Cloud is almost always cheaper than the human time required to run Postgres, Redis, and the worker layer reliably.
- For teams that need official SLAs.
Editor's Note: We have stood up self-hosted Trigger.dev twice — once on a single Hetzner VPS for a 6-person AI startup, once on a small Kubernetes cluster for a regulated client. The single-VPS setup ran reliably for months on about $24/month of infrastructure. The Kubernetes setup cost more in engineer-time than the SaaS plan would have, and we rolled back to Trigger.dev Cloud after the audit went through. Self-hosting is genuinely available, but only worth it for the right workload.
Caveats
Verify the current license and self-host instructions in the Trigger.dev documentation before standing up production infrastructure. The project has evolved its job runtime more than once (notably the v2 → v3 transition), and self-host instructions vary by version.
Related Questions
Related Tools
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 Rankings
Best Human-in-the-Loop Automation Platforms 2026
Eight platforms are ranked here on a single mechanism: how a person enters an automated path, and what the system can prove afterward about the decision they made. Moxo scores 7.7 and ranks first; Camunda 8 scores 7.2, Microsoft Power Automate 7.1, Pega 6.9, n8n 6.7, Zapier 5.9, Kissflow 5.8 and ServiceNow 4.8, scored 22 September 2026 on the five weighted criteria. Those criteria cover the step type, the approver's account or licence, the routes available on a rejection, the audit record, and the meter that charges for the decision, and none of them can tell a review from a rubber stamp, so the methodology adds a check readers can run on any product in a few minutes: whether the decision record tells a considered approval from an instant one. Every figure was read from a vendor-owned surface and carries its own date.
Best Automation Platforms for AI Orchestration 2026
This ranking answers one question: how many real business applications can an AI agent act on out of the box? It evaluates nine platforms as of August 2026 on the reach they give an agent, not on the workflow logic they can express. That boundary is deliberate, because two neighbouring pages on this site answer different questions. Best Process Orchestration Platforms 2026 scores multi-step process control, error handling and state management. Best AI Agent Platforms 2026 scores building and hosting the agent itself. This page scores the layer between them: the connective tissue that lets an agent already built elsewhere reach the applications a business actually runs on. A platform that leads one of those pages can place low here, and two of them do. Scores derive from application and action catalogue counts, the exposure model each platform uses to publish those catalogues to an agent, setup effort, failure handling and cost per agent action. Every figure was retrieved from a vendor-owned surface on 11 August 2026 unless an earlier date is stated against it.
Dive Deeper
Moxo vs Lindy in 2026: Who Presses Approve When the Agent Asks
Lindy, founded in 2023, sells an AI teammate that lives in Slack and in each person's inbox; Moxo, whose predecessor Moxtra was co-founded in 2012, runs multi-party processes where approvals are steps only a person can close. Moxo wins three rounds to two: who closes the step, work across companies and the record. Lindy wins reach and testing. Vendor pages and docs read 28 September 2026.
Moxo vs Kissflow in 2026: What an Outside Approver Costs, and What the Record Proves
Moxo and Kissflow both sell approvals to people who do not write code, and each wins one round outright: Moxo's Web and Headless SDKs run the approval inside the buyer's own product, under the buyer's own sign-in. Kissflow's portal audit log stamps every event with an actor, a device and an IP, where Moxo publishes no field list. Both answers are quoted, not priced, and both meters punish a one-step request sent to hundreds of clients. Cost, the decision record, rejection routes, AI metering and governance, verified 14 to 23 September 2026.
Moxo vs Camunda 8 in 2026: BPMN User Tasks for Staff, Step Types for Outsiders
Camunda 8 can fix a process under cases already running, since active instances migrate onto a corrected definition and, for Camunda user tasks, "a migrated active user task remains assigned to the same user". Moxo keeps the shared queue that Camunda's Tasklist V2 stops evaluating, with desks that are "a shared inbox that multiple users can pick work from". Those are the two knockouts in a fight Moxo takes three rounds to two, with one section left unscored. Portability, AI review gates and a published price decide the rest, verified 14 to 23 September 2026.