Hatchet vs Inngest
SEPT 2026 auditA 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
Choose Hatchet if…
Task workloads that want a countable unit and no plan fee: 1M task runs and 1M events free each month with a card on file, then $30 per million runs, with 10,000 concurrent worker slots before any contract.
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: You want a published uptime percentage or long run history: SLAs come only on the quoted Custom plan, and history is kept 7 days with a card on file (1 day without) unless you move to Custom.
- 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.
Neither quite fits? Every other option, ranked by iScore: Hatchet alternatives · Inngest alternatives
15 sourced criteria separate them — see where, with sources, below.
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 |
| Kind of free offer | Free tier | Free tier |
| What the free plan includes | Two levels on the free Pay-as-you-go plan. No card: 2,000 task runs and 2,000 events a day. Card on file: 1M task runs and 1M events a month included, then $30 and $5 per million. | 50,000 executions and 500,000 events ingested a month with 5 concurrent steps, no credit card required. |
| Credit card to start | No | No |
| Entry paid plan | No plan fee: Pay-as-you-go is $0 a month and bills only usage past the free million runs and events ($30 per million runs). Custom, for 100M+ runs a month or enterprise features, is priced by conversation. | $99/month for Pro, described as a starting price with usage above the included allowance billed on top. |
| Pricing model | Usage-based with no plan fees: 1M task runs and 1M events free every month, then $30 per million runs and $5 per million events, with volume pricing at 100M+ runs a month on Custom. Users past 50 are $10 each. | 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. |
| Infrastructure | ||
| Regions | 3 live AWS regions (Oregon, N. Virginia, Ireland) plus Sydney in private beta; control plane in aws-us-west-2. | All customer data hosted on AWS databases located in the United States; no other region offered on the security page. |
| Queues | ||
| Included per month | 1M task runs and 1M events a month on Pay-as-you-go with a card on file, then $30 per million runs and $5 per million events. Without a card: 2,000 task runs and 2,000 events a day. | 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. |
| Maximum message size | 4 MB default maximum payload size for a task's input or output between worker and Hatchet engine. | 4 MiB per step-returned payload; 32 MiB total function run state; 10 MiB hard cap per event batch. |
| Message retention | Run history, logs and traces stay queryable for 1 day on Pay-as-you-go without a card, 7 days with a card on file, and 90+ days on Custom. This is dashboard and API history, not how long an undelivered task waits in the queue, so no magnitude is recorded. | 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 | 2,000 worker slots (tasks running at once, totalled across all workers) on Pay-as-you-go without a card, 10,000 with a card on file; Custom gets dedicated capacity. No requests-per-second ceiling is published. | 5 concurrent steps on the free plan, 100 or more on Pro, custom on Enterprise. |
| Dead letter queue | Not supported — No built-in DLQ; failed task instances persist in the dashboard for manual analysis and retry. | Not supported — No dead-letter queue; failed runs stay in the dashboard and are re-run in bulk with Replay. |
| Compliance | ||
| SOC 2 | SOC 2 Type II compliant; reports available through the Hatchet Trust Center. | SOC 2 Type II compliant; report available on request via the trust center. |
| HIPAA | HIPAA compliant per the security docs; the Scale plan ($1,000/mo) lists audit logs and HIPAA. | HIPAA BAAs offered as an add-on for healthcare compliance (Enterprise column of the pricing table). |
| GDPR / data residency | GDPR compliant per the security docs; EU data plane available in aws-eu-west-1 (Ireland). | Data residency only: Inngest Cloud runs in two eastern-US footprints, AWS us-east-2 (Ohio) and Inngest bare metal in Ashburn, Virginia. |
| Encryption at rest | Data stored in Hatchet Cloud is encrypted at rest; API and worker traffic encrypted with TLS in transit. | All data in Inngest databases is encrypted at rest and in transit; optional encryption middleware lets you bring your own key. |
| Customer-managed keys | Documented SDK middleware pattern encrypts task inputs and outputs before they reach the Hatchet server; the encryption key stays in the worker environment. | Bring-your-own-key via SDK encryption middleware that encrypts payloads client-side before they reach Inngest; not a server-side KMS option. |
| Role-based access control | Hierarchical tenant roles OWNER, ADMIN, MEMBER, VIEWER plus organization roles; payload visibility can be restricted per member. | SAML, RBAC and audit trails listed as Enterprise plan features. |
| Dedicated infrastructure | Dedicated capacity, multi-region, and self-hosted or bring-your-own-cloud (BYOC) deployment on the Custom plan (talk to an engineer). | Enterprise runs on dedicated function execution infrastructure with isolated queue and constraint shards; Dedicated Infrastructure is an enterprise add-on. The add-on's contents and price are not described on the page. |
Where they differ.
What the free plan includes
- Hatchet
- Two levels on the free Pay-as-you-go plan. No card: 2,000 task runs and 2,000 events a day. Card on file: 1M task runs and 1M events a month included, then $30 and $5 per million.
- Inngest
- 50,000 executions and 500,000 events ingested a month with 5 concurrent steps, no credit card required.
Sources (2) →Sources ↓
- Hatchet Pricing ↗
“Pay-as-you-go No card Pay-as-you-go Card on file Custom [...] 2,000/day 1M/mo included then $30/M [...] 2,000/day 1M/mo included then $5/M”
Read 2026-09-27 · official pricing · Report a correction
- Pricing — Inngest ↗
“Hobby [...] $0/mo No credit card required [...] 50k executions [...] 5 concurrent steps [...] 500k events ingested”
Read 2026-09-13 · official pricing · Report a correction
Entry paid plan
- Hatchet
- No plan fee: Pay-as-you-go is $0 a month and bills only usage past the free million runs and events ($30 per million runs). Custom, for 100M+ runs a month or enterprise features, is priced by conversation.
- Inngest
- $99/month for Pro, described as a starting price with usage above the included allowance billed on top.
Sources (2) →Sources ↓
- Hatchet Pricing ↗
“Pay-as-you-go $0 to start [...] No surprise bills. No plan fees. You pay $30 per million runs, only after your free million, with volume pricing at 100M+ runs a month.”
Read 2026-09-27 · official pricing · Report a correction
- Pricing — Inngest ↗
“Pro [...] Starting at $99/mo [...] 1M executions included Pay as you go up to 20M”
Read 2026-09-06 · official pricing · Report a correction
Pricing model
- Hatchet
- Usage-based with no plan fees: 1M task runs and 1M events free every month, then $30 per million runs and $5 per million events, with volume pricing at 100M+ runs a month on Custom. Users past 50 are $10 each.
- 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 ↓
- Hatchet Pricing ↗
“1M runs and 1M events free, every month Then $30 per million runs, $5 per million events [...] No surprise bills. No plan fees. You pay $30 per million runs, only after your free million, with volume pricing at 100M+ runs a month. [...] Users 50 included, then $10/user”
Read 2026-09-27 · official pricing · Report a correction
- 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 · Report a correction
Regions
- Hatchet
- 3 live AWS regions (Oregon, N. Virginia, Ireland) plus Sydney in private beta; control plane in aws-us-west-2.
- Inngest
- All customer data hosted on AWS databases located in the United States; no other region offered on the security page.
Sources (2) →Sources ↓
- Region Availability - Hatchet Documentation ↗
“aws-us-west-2 Oregon (US) Live aws-us-east-1 N. Virginia (US) Live aws-eu-west-1 Ireland Live aws-ap-southeast-2 Sydney Private Beta”
Read 2026-09-13 · official docs · Report a correction
- Security | Inngest ↗
“All of our data is hosted on Amazon Web Services (AWS) databases. These databases are all located in the United States.”
Read 2026-09-13 · official site · Report a correction
Included per month
- Hatchet
- 1M task runs and 1M events a month on Pay-as-you-go with a card on file, then $30 per million runs and $5 per million events. Without a card: 2,000 task runs and 2,000 events a day.
- 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 ↓
- Hatchet Pricing ↗
“1M runs and 1M events free, every month Then $30 per million runs, $5 per million events [...] 2,000/day 1M/mo included then $30/M [...] 2,000/day 1M/mo included then $5/M”
Read 2026-09-27 · official pricing · Report a correction
- 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 · Report a correction
Maximum message size
4 MB default maximum payload size for a task's input or output between worker and Hatchet engine.
4 MiB per step-returned payload; 32 MiB total function run state; 10 MiB hard cap per event batch.
Sources (2) →Sources ↓
- Troubleshooting Workers - Hatchet Documentation ↗
“The payload is too large for the worker to accept or the Hatchet engine to send. The default maximum payload size is 4MB.”
Read 2026-09-13 · official docs · Report a correction
- Inngest usage limits - Inngest Documentation ↗
“Step-returned payload size 4MiB Applies to data returned by a step. Function run state size 32MiB Includes event data, step data, function return data, and internal metadata.”
Read 2026-09-13 · official docs · Report a correction
Message retention
- Hatchet
- Run history, logs and traces stay queryable for 1 day on Pay-as-you-go without a card, 7 days with a card on file, and 90+ days on Custom. This is dashboard and API history, not how long an undelivered task waits in the queue, so no magnitude is recorded.
- 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 ↓
- Hatchet Pricing ↗
“Retention How long run history, logs, and traces stay queryable in the dashboard and API. 1 day 7 days 90+ days”
Read 2026-09-27 · official pricing · Report a correction
- 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 · Report a correction
Concurrency
- Hatchet
- 2,000 worker slots (tasks running at once, totalled across all workers) on Pay-as-you-go without a card, 10,000 with a card on file; Custom gets dedicated capacity. No requests-per-second ceiling is published.
- Inngest
- 5 concurrent steps on the free plan, 100 or more on Pro, custom on Enterprise.
Sources (2) →Sources ↓
- Hatchet Pricing ↗
“Worker slots Each slot runs one task at a time. A worker with 100 slots can run 100 tasks concurrently. The limit is the total across all workers. 2,000 10,000 Dedicated capacity”
Read 2026-09-27 · official pricing · Report a correction
- Pricing — Inngest ↗
“5 concurrent steps [...] 100+ concurrent steps [...] Custom concurrent steps”
Read 2026-09-06 · official pricing · Report a correction
SOC 2
- Hatchet
- SOC 2 Type II compliant; reports available through the Hatchet Trust Center.
- Inngest
- SOC 2 Type II compliant; report available on request via the trust center.
Sources (2) →Sources ↓
- Security - Hatchet Documentation ↗
“Hatchet is SOC 2 Type II, HIPAA, and GDPR compliant. Company-level security practices, compliance reports, and security documentation are available at the Hatchet Trust Center .”
Read 2026-09-13 · official docs · Report a correction
- Security | Inngest ↗
“Inngest is SOC 2 Type II compliant. [...] Read our announcement , request a copy of the report or contact us for additional questions.”
Read 2026-09-13 · official site · Report a correction
HIPAA
- Hatchet
- HIPAA compliant per the security docs; the Scale plan ($1,000/mo) lists audit logs and HIPAA.
- Inngest
- HIPAA BAAs offered as an add-on for healthcare compliance (Enterprise column of the pricing table).
Sources (2) →Sources ↓
- Security - Hatchet Documentation ↗
“Hatchet is SOC 2 Type II, HIPAA, and GDPR compliant.”
Read 2026-09-13 · official docs · Report a correction
- Pricing | Inngest ↗
“Dedicated slack channel Direct P0 support from our team HIPAA BAAs for healthcare compliance Add-on”
Read 2026-09-13 · official pricing · Report a correction
GDPR / data residency
- Hatchet
- GDPR compliant per the security docs; EU data plane available in aws-eu-west-1 (Ireland).
- Inngest
- Data residency only: Inngest Cloud runs in two eastern-US footprints, AWS us-east-2 (Ohio) and Inngest bare metal in Ashburn, Virginia.
Sources (2) →Sources ↓
- Security - Hatchet Documentation ↗
“Hatchet is SOC 2 Type II, HIPAA, and GDPR compliant.”
Read 2026-09-13 · official docs · Report a correction
- Inngest Cloud Architecture | Scheduling & Execution - Inngest Docs ↗
“Inngest Cloud runs across two nearby infrastructure footprints in the eastern United States: [...] AWS us-east-2 (Ohio) hosts customer-facing APIs, control plane services, and supporting data services. [...] Inngest-operated bare metal in Ashburn, Virginia hosts the primary run scheduling and function execution data plane”
Read 2026-09-13 · official docs · Report a correction
Encryption at rest
- Hatchet
- Data stored in Hatchet Cloud is encrypted at rest; API and worker traffic encrypted with TLS in transit.
- Inngest
- All data in Inngest databases is encrypted at rest and in transit; optional encryption middleware lets you bring your own key.
Sources (2) →Sources ↓
- Security - Hatchet Documentation ↗
“Encryption at rest : data stored in Hatchet Cloud is encrypted at rest.”
Read 2026-09-13 · official docs · Report a correction
- Security - Inngest Documentation ↗
“End to end encryption All data in Inngest databases is encrypted at rest and encrypted in transit, including between Inngest's servers and your servers.”
Read 2026-09-13 · official docs · Report a correction
Customer-managed keys
- Hatchet
- Documented SDK middleware pattern encrypts task inputs and outputs before they reach the Hatchet server; the encryption key stays in the worker environment.
- Inngest
- Bring-your-own-key via SDK encryption middleware that encrypts payloads client-side before they reach Inngest; not a server-side KMS option.
Sources (2) →Sources ↓
- Middleware - Hatchet Documentation ↗
“Encrypt sensitive input fields before they reach the Hatchet server, and decrypt the output on the way back. This ensures plaintext data never leaves your worker process. [...] The encryption key never leaves the worker environment.”
Read 2026-09-13 · official docs · Report a correction
- Security - Inngest Documentation ↗
“For an added layer of encryption and control of your data, install encryption middleware and bring your own encryption key.”
Read 2026-09-13 · official docs · Report a correction
Role-based access control
- Hatchet
- Hierarchical tenant roles OWNER, ADMIN, MEMBER, VIEWER plus organization roles; payload visibility can be restricted per member.
- Inngest
- SAML, RBAC and audit trails listed as Enterprise plan features.
Sources (2) →Sources ↓
- User Roles - Hatchet Documentation ↗
“Every user in a tenant has a role that controls what they can do in the dashboard and REST API. Roles are hierarchical: each role can do everything the roles below it can.”
Read 2026-09-13 · official docs · Report a correction
- Pricing | Inngest ↗
“Advanced tracing, metrics, alerts + 90 day trace retention Dedicated Slack channel SAML, RBAC, audit trails”
Read 2026-09-13 · official pricing · Report a correction
Dedicated infrastructure
- Hatchet
- Dedicated capacity, multi-region, and self-hosted or bring-your-own-cloud (BYOC) deployment on the Custom plan (talk to an engineer).
- Inngest
- Enterprise runs on dedicated function execution infrastructure with isolated queue and constraint shards; Dedicated Infrastructure is an enterprise add-on. The add-on's contents and price are not described on the page.
Sources (2) →Sources ↓
- Hatchet Pricing ↗
“For 100M+ runs a month, dedicated capacity, or enterprise features. [...] Dedicated capacity and multi-region [...] Self-hosted and BYOC support”
Read 2026-09-27 · official pricing · Report a correction
- Inngest Cloud Architecture | Scheduling & Execution - Inngest Docs ↗
“Enterprise customers run on dedicated function execution infrastructure: [...] Dedicated Infrastructure is an enterprise-only add-on available on request.”
Read 2026-09-13 · official docs · Report a correction
When these numbers change, hear about it. Sources are re-checked monthly; a repricing goes out as a short note.
Documented by only one.
These criteria are published by one provider and not the other. An absence here means we have not found a source, not that the feature is missing — except where we say we read the other provider's own page on a given date and it does not state it. Those rows lean, and the provider can correct them with a link.
Questions this comparison answers.
Entry paid plan: Hatchet or Inngest?
Hatchet: No plan fee: Pay-as-you-go is $0 a month and bills only usage past the free million runs and events ($30 per million runs). Custom, for 100M+ runs a month or enterprise features, is priced by conversation.
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 and no plan fee: 1M task runs and 1M events free each month with a card on file, then $30 per million runs, with 10,000 concurrent worker slots before any contract.
Pick Inngest if Multi-step workflows that need durable execution and retries between steps, rather than a bare queue you write a consumer for.
Comments are hosted by EchoThread, which sets cookies and offers social sign-in. Like the analytics on this site, it does not load until you accept — see the privacy page.