# Trigger.dev

Canonical: https://inetgeek.com/queues/trigger-dev/

Background jobs platform billed as monthly credits against compute, with plan tiers set by concurrent runs.

## Who it suits

Teams that want background jobs written as normal code with the bill expressed as compute credits rather than a per-message meter.

Consider something else if Concurrency is the axis that forces an upgrade — 20 simultaneous runs on free, 50 on Hobby, then $10 a month per additional 50.

## What the documentation says

### Pricing

- Free tier: Yes ([source](https://trigger.dev/pricing), read 2026-09-06)
- Entry paid plan: $10/month for Hobby, which includes $10 of credits; Pro is $50/month including $50 of credits. ([source](https://trigger.dev/pricing), read 2026-09-06)
- Pricing model: A monthly plan fee that is also a credit balance — the fee buys compute rather than sitting on top of it — with concurrency, preview branches, dashboards and schedules each priced as separate add-ons beyond the plan's allowance. ([source](https://trigger.dev/pricing), read 2026-09-06)

### Queues

- Included per month: Credits rather than a message or execution count: $5 a month free, $10 included on Hobby and $50 on Pro, spent against compute. ([source](https://trigger.dev/pricing), read 2026-09-06)
- Message retention: Log retention of 1 day on the free plan, 7 days on Hobby and 30 days on Pro, with the query period matching. ([source](https://trigger.dev/pricing), read 2026-09-06)
- Concurrency: 20 concurrent runs on the free plan, 50 on Hobby, and more on Pro at $10 a month per additional 50. ([source](https://trigger.dev/pricing), read 2026-09-06)

## Compared with

- [Trigger.dev vs Cloudflare Queues](https://inetgeek.com/compare/cloudflare-queues-vs-trigger-dev/)
- [Trigger.dev vs Upstash QStash](https://inetgeek.com/compare/qstash-vs-trigger-dev/)
- [Trigger.dev vs Inngest](https://inetgeek.com/compare/inngest-vs-trigger-dev/)