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

Last updated: | By Rafal Fila

Related Tools

Activepieces

No-code workflow automation with self-hosting and AI-powered features

Workflow Automation

Automatisch

Open-source Zapier alternative

Workflow Automation

Bardeen

AI-powered browser automation via Chrome extension

Workflow Automation

Calendly

Scheduling automation platform for booking meetings without email back-and-forth, with CRM integrations and routing forms for lead qualification.

Workflow Automation

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.

Dive Deeper

case-study

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.

comparison

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, $20/month Hobby). This 2026 comparison covers license, programming model, pricing, observability, and self-host options.

comparison

Inngest vs Temporal 2026: Durable Functions vs Durable Workflows

Inngest (2021, San Francisco) is a developer-first durable functions platform with TypeScript and Python SDKs, 50,000 step runs/month free, and Hobby pricing from $20/month. Temporal (2019) is the heavyweight durable workflow engine with seven-language SDK coverage, Cassandra-backed scale, and Cloud pricing from roughly $200/month at low volume or $2.5-4.5K/month self-host. This 2026 comparison covers programming model, pricing, scale ceiling, and operational footprint.