# Hatchet vs Inngest

Canonical: https://inetgeek.com/compare/hatchet-vs-inngest/

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

## At a glance

| Criterion | Hatchet | Inngest |
| --- | --- | --- |
| 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. | $99/month for Pro, described as a starting price with usage above the included allowance billed on top. |
| 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. | Per execution, where a step counts the same as a run, plus separate meters for events ingested, span data, scores and realtime connections. The pricing page ships a calculator because the execution count is not the run count. |
| 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. | 50,000 executions a month on the free Hobby plan and 1,000,000 on Pro, pay-as-you-go to 20M. An execution is one function run or one step, so a run with two steps counts as three. |
| Message retention | 3 days on the Team plan, stated alongside a 500 requests-per-second throughput ceiling. | Queue depth rather than a time window: 100,000 queued items on the free plan and 1,000,000 or more on Pro. Trace retention is 7 days on Pro and 90 on Enterprise. |
| Concurrency | 500 requests per second of throughput on Team; higher tiers are not published as a number. | 5 concurrent steps on the free plan, 100 or more on Pro, custom on Enterprise. |

## 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))
- Inngest: $99/month for Pro, described as a starting price with usage above the included allowance billed on top. ([source](https://www.inngest.com/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))
- Inngest: Per execution, where a step counts the same as a run, plus separate meters for events ingested, span data, scores and realtime connections. The pricing page ships a calculator because the execution count is not the run count. ([source](https://www.inngest.com/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))
- Inngest: 50,000 executions a month on the free Hobby plan and 1,000,000 on Pro, pay-as-you-go to 20M. An execution is one function run or one step, so a run with two steps counts as three. ([source](https://www.inngest.com/pricing))

### Message retention

- Hatchet: 3 days on the Team plan, stated alongside a 500 requests-per-second throughput ceiling. ([source](https://hatchet.run/pricing))
- Inngest: Queue depth rather than a time window: 100,000 queued items on the free plan and 1,000,000 or more on Pro. Trace retention is 7 days on Pro and 90 on Enterprise. ([source](https://www.inngest.com/pricing))

### Concurrency

- Hatchet: 500 requests per second of throughput on Team; higher tiers are not published as a number. ([source](https://hatchet.run/pricing))
- Inngest: 5 concurrent steps on the free plan, 100 or more on Pro, custom on Enterprise. ([source](https://www.inngest.com/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 Inngest if Multi-step workflows that need durable execution and retries between steps, rather than a bare queue you write a consumer for.

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: Inngest — Every step is a billable execution, so a three-step workflow costs three times what the run count implies, and the free plan allows five concurrent steps.

## Questions this comparison answers

**Entry paid plan: Hatchet or Inngest?**

Hatchet: $500/month for Team, which adds users, tenants, retention and throughput on top of usage. Scale is $1,000/month.
Inngest: $99/month for Pro, described as a starting price with usage above the included allowance billed on top.

**Should I choose Hatchet or Inngest?**

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 Inngest if Multi-step workflows that need durable execution and retries between steps, rather than a bare queue you write a consumer for.