Trigger.dev pricing, free plan and limits

Open-source TypeScript background job platform that eliminates serverless timeouts. Durable execution, auto-retries, real-time traces. Free tier available.

  • ai orchestration
  • Web
checked

Last updated: 2026-08-19

Trigger.dev is an open-source TypeScript platform for durable background jobs, launched in 2022 to remove the timeout ceilings that make serverless functions unworkable for long AI agent tasks. Its checkpoint-resume design restores a task's exact state after any restart or failure, with automatic retries and idempotent execution handled for you.

About Trigger.dev

Trigger.dev is an open-source, TypeScript-native platform for durable background jobs, founded in 2022 in London. The team has raised $20.3M in funding, including a $16M Series A led by Standard Capital, and releases the core engine under an open-source license carrying roughly 14.6k GitHub stars. Its checkpoint-resume architecture snapshots a running task's full state at each wait point and restores it on recovery, which is what lets jobs keep going past the limits that stop ordinary serverless functions. Tasks are written as plain async TypeScript, with no special DSL or determinism rules, while the platform handles retries, deduplication, and OpenTelemetry tracing automatically. Trigger.dev ships as a fully managed cloud service or a self-hosted Docker and Kubernetes deployment for teams that need to keep jobs on their own infrastructure.

Pricing

Free: $0/month, 20 concurrent runs, 10 schedules, 1-day log retention. Hobby: $10/month, 50 concurrent runs, 100 schedules, 7-day logs. Pro: $50/month, 200+ concurrent runs, 1000+ schedules, 30-day logs, 25+ team members. Enterprise: custom pricing. All paid tiers also bill compute separately at $0.0000169-$0.0006800 per second of execution plus $0.000025 per run invocation.

Key Features

  • Checkpoint-Resume Durable Execution: Snapshots exactly where a task left off and resumes it after any restart, letting jobs run for up to 14 days instead of hitting a serverless function's timeout ceiling.
  • Plain Async TypeScript, No DSL: Tasks are ordinary async functions; Trigger.dev handles state capture, retries, and idempotency without a workflow-specific syntax or determinism constraints to learn.
  • 100+ Native Integrations: Built-in connectors for Slack, Stripe, Linear, GitHub, SendGrid, Notion, OpenAI, Deepgram, Twilio, and Airtable remove the need to hand-write API auth and retry logic.
  • Live OpenTelemetry Traces: Every run streams a real-time execution timeline with logs and error detail to a live dashboard, so failures surface immediately instead of requiring log-polling.
  • Self-Host or Managed Cloud: Run on Trigger.dev's managed SaaS with no Redis or worker processes to operate, or self-host the same engine via Docker and Kubernetes Helm charts.

Pros

  • Removes the serverless timeout ceiling that makes AWS Lambda, Vercel, and Google Cloud Functions unsuitable for long AI agent runs, without asking developers to learn a new orchestration DSL.
  • Lower operational overhead than Temporal or BullMQ-style setups: no Redis instance, no worker pool, and no Kubernetes cluster to keep patched when you use the managed cloud tier.
  • Faster to adopt than Temporal for teams already comfortable with async TypeScript, since there is no separate DSL or replay-determinism model to learn first.
  • Open-source with an active GitHub community, so self-hosting or auditing the engine is possible without vendor lock-in.

Cons

  • TypeScript and JavaScript are the primary languages; Python support exists only through a limited extension, so Python-first teams pay a context-switching cost.
  • Cloud-tier tasks are capped at a 14-day maximum runtime with no published path to longer durations, so workflows that inherently need weeks of execution require a custom enterprise conversation.
  • Local development requires an internet connection to Trigger.dev Cloud; there is no offline or fully air-gapped test mode.
  • Documentation on v3/v4 migration has historically lagged behind the product, though this has been improving.

Frequently Asked Questions

How much do you pay for Trigger.dev?

Free costs $0/month with 20 concurrent runs. Hobby is $10/month with 50 concurrent runs and 7-day log retention. Pro is $50/month with 200+ concurrent runs and 30-day retention. Enterprise pricing is custom, and all paid tiers also bill compute time and run invocations separately.

Does Trigger.dev have a free plan?

Yes, the Free plan costs $0/month and includes 20 concurrent runs, 10 schedules, and 1-day log retention. The same durable-execution engine runs underneath, just with lower concurrency and schedule caps than the paid tiers.

Which tools compete with Trigger.dev in 2026?

Temporal is the enterprise alternative, with more mature replay-based durability but a steeper learning curve and infrastructure to run yourself. Inngest is the closest peer, scheduling jobs through its own dashboard instead of running your code directly the way Trigger.dev does.

Trigger.dev or Temporal: which should you pick?

Temporal guarantees exact replay determinism for mission-critical workflows at companies like Stripe and Netflix, but that requires writing deterministic workflow code and operating your own worker infrastructure. Trigger.dev trades some of that rigor for speed: plain async TypeScript, a managed cloud tier, and a setup that takes minutes instead of the hours Temporal's client SDKs typically require.

How long does it take to get going with Trigger.dev?

Getting Trigger.dev running takes minutes: install the SDK, define a task as a plain async function, and run it locally with the CLI dev server. Temporal's own client libraries ask for a heavier lift by comparison, so deploying to the free tier here to try checkpoint-resume durability needs no credit card and no dedicated worker setup.

Top Alternatives

  • Temporal: Plain async TypeScript on a managed cloud tier is Trigger.dev's approach. Temporal demands more: Stripe- and Netflix-scale replay determinism, but only if you're willing to run your own worker infrastructure for it.
  • Inngest: Trigger.dev runs your own code directly inside its durable engine. Inngest instead schedules jobs through its own dashboard, a different model for the same durability problem.
  • n8n: Writing durable jobs in plain TypeScript code is Trigger.dev's whole pitch. n8n goes visual and low-code instead, no code required to build the workflow.

HokAI guides covering Trigger.dev

More AI Tools on HokAI

Visit Trigger.dev Official Website