# Hatchet vs Trigger.dev

Canonical: https://inetgeek.com/compare/hatchet-vs-trigger-dev/

Every value below is read from Hatchet's and Trigger.dev's own documentation. See https://inetgeek.com/methodology/ for how.

## At a glance

| Criterion | Hatchet | Trigger.dev |
| --- | --- | --- |
| Free tier | Yes | Yes |
| Entry paid plan | $500/month for Team, which adds users, tenants, retention and throughput on top of usage. Scale is $1,000/month. | $10/month for Hobby, which includes $10 of credits; Pro is $50/month including $50 of credits. |
| Pricing model | Usage-first: every plan is "free + usage" or "$N/mo + usage" at $10 per million task runs, with the plan fee buying users, tenants, retention and throughput rather than volume. Self-hosting is offered with support on the enterprise tier. | 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. |
| Included per month | 100,000 task runs included free, then $10 per million. The cleanest per-unit rate in this category — Hatchet counts task runs where Cloudflare counts 64 KB operations and Inngest counts steps. | Credits rather than a message or execution count: $5 a month free, $10 included on Hobby and $50 on Pro, spent against compute. |
| Message retention | 3 days on the Team plan, stated alongside a 500 requests-per-second throughput ceiling. | Log retention of 1 day on the free plan, 7 days on Hobby and 30 days on Pro, with the query period matching. |
| Concurrency | 500 requests per second of throughput on Team; higher tiers are not published as a number. | 20 concurrent runs on the free plan, 50 on Hobby, and more on Pro at $10 a month per additional 50. |

## Where they differ

### Entry paid plan

- Hatchet: $500/month for Team, which adds users, tenants, retention and throughput on top of usage. Scale is $1,000/month. ([source](https://hatchet.run/pricing))
- Trigger.dev: $10/month for Hobby, which includes $10 of credits; Pro is $50/month including $50 of credits. ([source](https://trigger.dev/pricing))

### Pricing model

- Hatchet: Usage-first: every plan is "free + usage" or "$N/mo + usage" at $10 per million task runs, with the plan fee buying users, tenants, retention and throughput rather than volume. Self-hosting is offered with support on the enterprise tier. ([source](https://hatchet.run/pricing))
- Trigger.dev: 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))

### Included per month

- Hatchet: 100,000 task runs included free, then $10 per million. The cleanest per-unit rate in this category — Hatchet counts task runs where Cloudflare counts 64 KB operations and Inngest counts steps. ([source](https://hatchet.run/pricing))
- Trigger.dev: 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))

### Message retention

- Hatchet: 3 days on the Team plan, stated alongside a 500 requests-per-second throughput ceiling. ([source](https://hatchet.run/pricing))
- Trigger.dev: 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))

### Concurrency

- Hatchet: 500 requests per second of throughput on Team; higher tiers are not published as a number. ([source](https://hatchet.run/pricing))
- Trigger.dev: 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))

## Which should you choose?

Pick Hatchet if Task workloads that want a countable unit — 100,000 runs free and $10 per million is the least ambiguous pricing in this category.

Pick Trigger.dev if 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: Hatchet — The jump from free to the first paid tier is $500 a month, which buys retention and throughput rather than volume, so a small production workload pays a lot for features it may not need.

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

## Questions this comparison answers

**Entry paid plan: Hatchet or Trigger.dev?**

Hatchet: $500/month for Team, which adds users, tenants, retention and throughput on top of usage. Scale is $1,000/month.
Trigger.dev: $10/month for Hobby, which includes $10 of credits; Pro is $50/month including $50 of credits.

**Should I choose Hatchet or Trigger.dev?**

Pick Hatchet if Task workloads that want a countable unit — 100,000 runs free and $10 per million is the least ambiguous pricing in this category.
Pick Trigger.dev if Teams that want background jobs written as normal code with the bill expressed as compute credits rather than a per-message meter.