Trigger.dev

Trigger.dev is an open-source TypeScript platform for long-running background jobs, durable AI agents, and production workflows. It combines task execution, queues, retries, scheduling, deployment, logs, traces, replay, and cancellation. Tasks run in containers and can include system packages or binaries such as FFmpeg. Durable waits preserve execution without charging compute while idle, and realtime features can stream agent responses and tool calls to an application.

Capabilities and workflow fit

The concrete feature set is: 1. Durable TypeScript tasks without a fixed execution timeout. 2. Queues, concurrency, schedules, waits, and retries. 3. Logs, traces, replay, cancellation, and bulk operations. 4. Container builds with packages and system binaries. 5. Realtime streaming and human-in-the-loop pauses. 6. Project-aware MCP server for coding agents. Test these capabilities as a complete workflow, not an isolated checklist. Use representative inputs and define the expected asset, note, answer, finding, action, or completed task before starting. Record completion rate, correction time, latency, intervention frequency, and cost per accepted result. Include difficult cases such as missing context, ambiguous input, revoked access, upstream failure, and a changed interface or schema.

For systems that read company data or take actions, verify least-privilege access, credential handling, encryption, retention, deletion, audit logs, subprocessors, regional processing, and whether customer material is used for training. Keep a qualified person responsible for clinical, security, financial, or physical-world decisions. A successful demonstration is not evidence that the tool will recover safely from every production failure.

Pricing and purchasing checks

Official cloud pricing lists Free at $0 with $5 monthly compute, Hobby at $10 with $10 compute, Pro at $50 with $50 compute, and custom Enterprise. Managed use also includes invocation and machine-time charges. Model actual run duration, retries, concurrency, and volume before choosing a plan. Pricing can change after publication. Ask for currency, taxes, billing interval, renewal terms, included usage, overages, support, cancellation, data export, and deletion commitments in writing. Run a bounded pilot with a spending cap. Usage-priced products can accumulate retries and agent-loop charges, while open-source or self-hosted products still require compute, monitoring, upgrades, and operational ownership.

Pros, limitations, and alternatives

The strongest advantages are consolidates workflow infrastructure in one platform; durable waits avoid charges during idle periods; containers support flexible dependencies; pricing publishes credits and machine rates. Important limitations are typescript-first design is not no-code; compute and invocation charges need monitoring; external side effects still need idempotency; self-hosting transfers operations to the team. Give each limitation an owner and a test. Permission risk needs scoped accounts and audit review; reliability risk needs repeatable failure cases; uncertain pricing needs a dated quote tied to measured usage.

Relevant comparison points include Inngest and Temporal, plus n8n and LangGraph. These are adjacent options or workflow alternatives, not promises of feature parity. Compare candidates using the same inputs, acceptance criteria, security requirements, and total-cost assumptions rather than category labels alone.

Practical use cases and verdict

The clearest uses are 1. Run an approval-gated support agent durably. 2. Process media with FFmpeg, queues, retries, and replay. 3. Schedule ETL and inspect every run. 4. Coordinate parallel model calls with concurrency limits. Start with the narrowest use case that has a known baseline for time, errors, and cost. Preserve a manual fallback and test exports before making the product a system of record or required production dependency.

Trigger.dev belongs on a shortlist when its verified capabilities remove concrete steps from one of these workflows. Adoption should follow only after current commercial terms, permissions, output quality, failure recovery, and portability have been tested with the buyer’s own users and data.