# Hatchet

Canonical: https://inetgeek.com/queues/hatchet/

Durable task queue billed per task run, with a free tier, published throughput limits and a self-hosted option.

## Who it suits

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.

Consider something else if 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.

## Adoption signals

- Open source: hatchet-dev/hatchet — 7,923 stars, 499 forks (GitHub, checked 2026-09-12)

## iScore

69 / 100 (80% interval 64–75), rank 6 of 10 in queues — interval overlaps the next rank, so this is an ordering, not a finding.

inetGeek's own reading, computed from sourced facts against category peers by disclosed rules. Not a provider claim. Intervals are 80%; a provider with few documented facts is pulled toward the category middle rather than scored on what little is known.
Read this score with care:
- Capacity and limits is thin: 2 of 5 criteria are scored, so it sits near the category middle with a wide interval (46–59). Read the interval, not the point.
- Documented but not scored, because the page states it as text with no comparable number or a yes/limited/no (a one-time, usage-based or other-vendor price, or a per-site choice): minimum_paid_price, concurrency_limit, queue_retention. Read them on the provider page; the score neither rewards nor penalises what it could not compare.

Method: https://inetgeek.com/iscore/. Full output with every criterion's basis: https://inetgeek.com/scores.json. Every queues peer ranked: https://inetgeek.com/queues/hatchet/alternatives/

- Price: 91 (73–100), weight 31%, 3 of 4 criteria scored; scored for peers, not here — undocumented or stated without a number or a yes/limited/no: minimum_paid_price
- Capacity and limits: 52 (46–59), weight 25%, 2 of 5 criteria scored; scored for peers, not here — undocumented or stated without a number or a yes/limited/no: concurrency_limit, max_delay, queue_retention
- Capabilities: 16 (0–45), weight 6%, 1 of 1 criteria scored
- Trust and compliance: 81 (68–94), weight 18%, 8 of 12 criteria scored; scored for peers, not here — undocumented or stated without a number or a yes/limited/no: iso27001, pci_dss, private_networking, support_included
- Evidence: 92 (92–92), weight 10%, 4 of 4 criteria scored
- Adoption: 34 (24–44), weight 10%, 1 of 1 criteria scored

## What the documentation says

### Pricing

- Free tier: Yes ([source](https://hatchet.run/pricing), read 2026-09-27)
- Kind of free offer: Free tier ([source](https://hatchet.run/pricing), read 2026-09-27)
- 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. ([source](https://hatchet.run/pricing), read 2026-09-27)
- Credit card to start: No ([source](https://hatchet.run/pricing), read 2026-09-27)
- 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. ([source](https://hatchet.run/pricing), read 2026-09-27)
- 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. ([source](https://hatchet.run/pricing), read 2026-09-27)

### Infrastructure

- Regions: 3 live AWS regions (Oregon, N. Virginia, Ireland) plus Sydney in private beta; control plane in aws-us-west-2. ([source](https://docs.hatchet.run/v1/region-availability), read 2026-09-13)
- Uptime SLA: Latency guarantees and SLAs on the Custom plan, sold by contract (talk to an engineer). No percentage is published on the pricing page. ([source](https://hatchet.run/pricing), read 2026-09-27)

### 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. ([source](https://hatchet.run/pricing), read 2026-09-27)
- Maximum message size: 4 MB default maximum payload size for a task's input or output between worker and Hatchet engine. ([source](https://docs.hatchet.run/v1/troubleshooting), read 2026-09-13)
- 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. ([source](https://hatchet.run/pricing), read 2026-09-27)
- 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. ([source](https://hatchet.run/pricing), read 2026-09-27)
- Dead letter queue: Not supported — No built-in DLQ; failed task instances persist in the dashboard for manual analysis and retry. ([source](https://docs.hatchet.run/v1/bulk-retries-and-cancellations), read 2026-09-13)

### Compliance

- SOC 2: SOC 2 Type II compliant; reports available through the Hatchet Trust Center. ([source](https://docs.hatchet.run/v1/security), read 2026-09-13)
- HIPAA: HIPAA compliant per the security docs; the Scale plan ($1,000/mo) lists audit logs and HIPAA. ([source](https://docs.hatchet.run/v1/security), read 2026-09-13)
- GDPR / data residency: GDPR compliant per the security docs; EU data plane available in aws-eu-west-1 (Ireland). ([source](https://docs.hatchet.run/v1/security), read 2026-09-13)
- Encryption at rest: Data stored in Hatchet Cloud is encrypted at rest; API and worker traffic encrypted with TLS in transit. ([source](https://docs.hatchet.run/v1/security), read 2026-09-13)
- 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. ([source](https://docs.hatchet.run/v1/middleware), read 2026-09-13)
- Role-based access control: Hierarchical tenant roles OWNER, ADMIN, MEMBER, VIEWER plus organization roles; payload visibility can be restricted per member. ([source](https://docs.hatchet.run/v1/user-roles), read 2026-09-13)
- Dedicated infrastructure: Dedicated capacity, multi-region, and self-hosted or bring-your-own-cloud (BYOC) deployment on the Custom plan (talk to an engineer). ([source](https://hatchet.run/pricing), read 2026-09-27)

## Compared with

- [Hatchet vs Inngest](https://inetgeek.com/compare/hatchet-vs-inngest/)
- [Hatchet vs Temporal](https://inetgeek.com/compare/hatchet-vs-temporal/)
- [Hatchet vs Trigger.dev](https://inetgeek.com/compare/hatchet-vs-trigger-dev/)
- [Hatchet vs Amazon SQS](https://inetgeek.com/compare/amazon-sqs-vs-hatchet/)
- [Hatchet vs Azure Queue Storage](https://inetgeek.com/compare/azure-queue-storage-vs-hatchet/)
- [Hatchet vs Cloudflare Queues](https://inetgeek.com/compare/cloudflare-queues-vs-hatchet/)
- [Hatchet vs Google Cloud Pub/Sub](https://inetgeek.com/compare/google-pubsub-vs-hatchet/)
- [Hatchet vs Upstash QStash](https://inetgeek.com/compare/hatchet-vs-qstash/)
- [Hatchet vs Zeplo](https://inetgeek.com/compare/hatchet-vs-zeplo/)