Trigger.dev review

Trigger.dev is an open-source TypeScript platform for building and deploying background workflows and long-running AI agents. It handles the execution machinery—queues, retries, scaling and checkpointing—so developers can coordinate work that may pause, run for a long time or need to recover after an error. The product can be self-hosted, according to the published product information.

The feature set includes scheduled tasks, webhooks and multi-stage workflows, plus agent features such as tool calling, streamed responses and human approval steps. Realtime updates can send task status and responses to a frontend. For operations, Trigger.dev lists run logs, tracing, filters, alerts and dashboards. Retry behavior can be configured for tasks, errors and requests.

The practical fit is TypeScript teams that want durable workflow infrastructure without assembling every queue and recovery mechanism themselves. It is not presented here as a general-purpose visual automation tool: the product is built around developers writing workflows in TypeScript.

Trigger.dev’s strongest case is durable work in a TypeScript application: tasks can use retries, queues and checkpoints, while workflows coordinate schedules, webhooks and multiple stages. That is useful for work that should not disappear when a request ends, including AI-agent runs that need tool calls, streaming or a human approval step. Logs, tracing, filters, alerts and dashboards give teams places to inspect runs when something stalls or fails.

The pricing structure may also suit workflows composed of many steps. A commenter in a Reddit discussion says Trigger.dev charges per job invocation rather than per step, and argues that this avoids shaping code around step costs. That is a user’s comparison, not a guarantee that every workload will be cheaper; the listed invocation and compute charges still matter.

There is a free plan for trying the product or running a small workload: the pricing page lists $5 in monthly compute credits, 20 concurrent runs, unlimited tasks, five team members and 10 schedules. Hobby is listed at $10 per month, with $10 in monthly credits, 50 concurrent runs, 100 schedules and seven-day log retention. Self-hosting is also an option for teams that want more control over deployment.

The free plan is bounded: it allows 20 concurrent runs, five team members and 10 schedules, and includes $5 in monthly compute credits. Hobby raises those caps to 50 concurrent runs and 100 schedules, but keeps the five-member limit and provides only seven-day log retention. Teams needing more headroom move to Pro, listed at $50 per month, with 200+ concurrent runs, 25+ team members, 1,000+ schedules and 30-day log retention. Enterprise pricing is custom and not published.

The monthly plan price is only part of the cost picture. The pricing page lists compute at $0.0000169–$0.0006800 per second, depending on machine, and run invocation at $0.000025 per run. Pro overages include $10 per additional 50 concurrent runs and $20 per seat above 25; extra schedules, dashboards, Realtime connections and preview branches also have separate charges. The page lists monthly prices only, with no annual price or discount published. Model run volume and compute use before scaling; the headline plan price alone does not tell you the full bill.

Trigger.dev has a free plan, then charges $10/month for Hobby and $50/month for Pro, according to the pricing information checked on November 6, 2026. Free includes $5 in monthly compute credits, 20 concurrent runs and 10 schedules. Hobby raises that to 50 concurrent runs and 100 schedules, with $10 in credits and 7-day log retention. Pro includes $50 in credits, 200+ concurrent runs, 1,000+ schedules and 30-day retention. That’s a $40 monthly jump from Hobby, before overages. Enterprise pricing is not published.

The listed prices are monthly; annual billing and discounts are not published. Credits don’t make usage unlimited: compute is billed at $0.0000169–$0.0006800 per second, depending on machine, and run invocations cost $0.25 per 10,000. Pro overages can add up too: extra concurrency costs $10 per 50 runs, and seats beyond 25 cost $20 each. Check expected usage before treating Pro as a predictable $50 plan.

Trigger.dev is built for TypeScript workflows, so teams moving from another system should expect to review and adapt task definitions, retries, schedules and integrations—not just copy run history. The published product information doesn’t quantify migration time or document a migration path from specific competitors. Trigger.dev offers self-hosting, which gives teams another deployment option, but that alone doesn’t establish that workflows or stored data are portable.

The published sources don’t specify data-export formats or cover what happens to run history when you leave. Confirm export and retention requirements before moving production workloads; the listed log-retention limits are 7 days on Hobby and 30 days on Pro. We also don’t have sourced Reddit posts about why users leave Trigger.dev, so we can’t responsibly present a Reddit consensus. The practical trade-off is clearer: it suits teams already building in TypeScript, while Python-first teams or anyone needing predictable all-in pricing may have reason to look elsewhere. Budget for metered compute and invocation costs as well as the plan fee.