starter.wikiSearch⌘K

Managed durable task workers

Trigger.dev

A TypeScript task platform with managed workers, durable runs, retries, waits, schedules, and run operations.

Visit official site

Editorial verdict

Choose Trigger.dev when managed TypeScript task workers remove more worker and retry infrastructure than the platform-specific model adds.12

Best for

  • Long-running or failure-sensitive TypeScript tasks
  • Teams wanting managed task compute and run operations
  • Scheduled work that must continue as a durable task
12

Not ideal for

  • Simple process-local work or message transport
  • Teams needing another language/workflow model
  • Unmodeled run, compute, capacity, retention, and add-on cost
12
Main trade-off

Worker plumbing decreases while task code, build/deploy, run state, machine, limits, billing, and control plane become platform-specific.12

Product boundary

Whether managed TypeScript workers and durable runs justify Trigger.dev's SDK, deployment, pricing, and control-plane dependency.

Trigger.dev executes durable tasks; queues transport messages and schedulers invoke by time. Self-hosting transfers platform operations and lacks some Cloud behavior.12

For: TypeScript teams operating important background and scheduled jobs

  • The language/runtime does not fit.
  • Managed workers are not desired.
  • Current plan and capacity economics are unacceptable.

Why teams consider Trigger.dev

  • Managed workersCloud executes task code on managed workers.12
  • Durable runsRetries and waits are integrated with run state.12
  • SchedulesScheduled invocation can continue into durable execution.12

Pricing

Plan plus executing-run invocation, per-second machine compute, and optional capacity/features; disputed current concurrency values remain qualitative.3

Managed task execution

Selected Cloud plan and machine

Model plan, runs, executing seconds, machine size, qualitative plan-limited concurrency, schedules, retention, and add-ons.3

Run invocation
$0.000025 per executing run at verification3
Concurrency
Plan-limited; exact Pro value withheld due official-page conflict3
Pricing checked View official pricing

Trigger.dev vs alternatives

Inngest

Choose when
Choose event-driven durable functions and application-hosted execution.
Compared with Trigger.dev
Execution ownership differs from managed task workers.6

Temporal

Choose when
Choose complex long-lived workflow orchestration.
Compared with Trigger.dev
The programming and worker operating model is larger.78

BullMQ

Choose when
Choose application-owned Redis and workers.
Compared with Trigger.dev
The team owns persistence, compute, monitoring, and recovery.910

Resources and sources

Official product, policy, and pricing

  • Trigger.dev documentation
    Open
  • Trigger.dev limits
    Open
  • Trigger.dev pricing
    Open
  • Trigger.dev self-hosting overview
    Open
  • Trigger.dev scheduled tasks
    Open
  1. 1
    Trigger.dev documentation

    Trigger.dev · Accessed Official

  2. 2
    Trigger.dev limits

    Trigger.dev · Accessed Official

  3. 3
    Trigger.dev pricing

    Trigger.dev · Accessed Official

  4. 4
    Trigger.dev self-hosting overview

    Trigger.dev · Accessed Official

  5. 5
    Trigger.dev scheduled tasks

    Trigger.dev · Accessed Official

  6. 6
    Inngest functions

    Inngest · Accessed Official

  7. 7
    Temporal documentation

    Temporal · Accessed Official

  8. 8
    Temporal Cloud pricing

    Temporal · Accessed Official

  9. 9
    BullMQ documentation

    Taskforce.sh · Accessed Official

  10. 10
    BullMQ production guidance

    Taskforce.sh · Accessed Official