Hatchet vs Inngest
A comparison of Hatchet and Inngest built from values read directly from each provider's own documentation, with the source recorded against every figure.
The short answer
- 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.
5 sourced criteria separate them:
- Entry paid plan
- 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.
- 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.
- 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.
- 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.
- 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.
- Message retention
- Hatchet: 3 days on the Team plan, stated alongside a 500 requests-per-second throughput ceiling.
- 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.
- Concurrency
- Hatchet: 500 requests per second of throughput on Team; higher tiers are not published as a number.
- Inngest: 5 concurrent steps on the free plan, 100 or more on Pro, custom on Enterprise.
Pick the criteria you care about. The chart counts how many of them lean toward each provider — the same read as scanning the bars below, just totalled for the ones you chose.
Hatchet 0
Inngest 0
At a glance.
| Criterion | Hatchet | Inngest |
|---|---|---|
| Pricing | ||
| 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. |
| Queues | ||
| 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.
- Inngest
- $99/month for Pro, described as a starting price with usage above the included allowance billed on top.
Sources (2) →Sources ↓
- Pricing — Hatchet ↗
“Team $500 /mo + usage Everything in Developer, plus: 10 users & 5 tenants 3-day retention 500 RPS throughput [...] Scale $1,000 /mo + usage”
Read 2026-09-06 · official pricing
- Pricing — Inngest ↗
“Pro [...] Starting at $99/mo [...] 1M executions included Pay as you go up to 20M”
Read 2026-09-06 · official 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.
- 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.
Sources (2) →Sources ↓
- Pricing — Hatchet ↗
“Developer Free + usage $10 per 1M task runs [...] Team $500 /mo + usage [...] SSO Audit logging Bring your own cloud Self-host support Custom SLAs”
Read 2026-09-06 · official pricing
- Pricing — Inngest ↗
“TOTAL EXECUTIONS PER MONTH (30,000 runs × 2 steps per run) + 30,000 runs = 90,000 executions [...] 500 MB span data ingested [...] 10K scores [...] 500k events ingested [...] 50 realtime connections”
Read 2026-09-06 · official 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.
- 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.
Sources (2) →Sources ↓
- Pricing — Hatchet ↗
“Developer Free + usage $10 per 1M task runs First 100,000 runs included”
Read 2026-09-06 · official pricing
- Pricing — Inngest ↗
“50k executions [...] 1M executions included Pay as you go up to 20M [...] (30,000 runs × 2 steps per run) + 30,000 runs = 90,000 executions [...] A single durable function run or step execution”
Read 2026-09-06 · official pricing
Message retention
- Hatchet
- 3 days on the Team plan, stated alongside a 500 requests-per-second throughput ceiling.
- 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.
Sources (2) →Sources ↓
- Pricing — Hatchet ↗
“10 users & 5 tenants 3-day retention 500 RPS throughput”
Read 2026-09-06 · official pricing
- Pricing — Inngest ↗
“100k queue depth [...] 1M+ queue depth [...] Granular tracing, metrics, alerts + 7 day trace retention [...] Advanced tracing, metrics, alerts + 90 day trace retention”
Read 2026-09-06 · official pricing
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.
Sources (2) →Sources ↓
- Pricing — Hatchet ↗
“3-day retention 500 RPS throughput See all features”
Read 2026-09-06 · official pricing
- Pricing — Inngest ↗
“5 concurrent steps [...] 100+ concurrent steps [...] Custom concurrent steps”
Read 2026-09-06 · official pricing
When these numbers change, hear about it. Sources are re-checked monthly; a repricing goes out as a short note.
Which should you choose?
Choose 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.
Editorial · Palash Bagchi · approved
Choose Inngest if…
Multi-step workflows that need durable execution and retries between steps, rather than a bare queue you write a consumer for.
Editorial · Palash Bagchi · approved
Consider something else if…
- 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.
- 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.