# Cloudflare Queues vs Hatchet

Canonical: https://inetgeek.com/compare/cloudflare-queues-vs-hatchet/

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

## At a glance

| Criterion | Cloudflare Queues | Hatchet |
| --- | --- | --- |
| Free tier | Yes | Yes |
| Pricing model | Billed per operation, not per message: one operation per 64 KB written, read or deleted, and a message larger than 64 KB counts as several. Cloudflare states a normal delivery takes three operations — one write, one read, one delete — so a million messages is nearer three million operations. Workers Paid includes 1,000,000 operations a month, then $0.40 per million; the free plan allows 10,000 a day. | 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. |
| Included per month | 1,000,000 operations a month on Workers Paid, then $0.40 per million. An operation is each 64 KB written, read or deleted, so a typical message costs three — Cloudflare's own formula is ((messages × 3) − 1,000,000) / 1,000,000 × $0.40. Workers Free allows 10,000 operations a day. | 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. |
| Message retention | 4 days by default on Workers Paid, configurable up to 14 days. Workers Free is fixed at 24 hours. | 3 days on the Team plan, stated alongside a 500 requests-per-second throughput ceiling. |
| Concurrency | 250 concurrent consumer invocations, push-based only, with per-queue throughput capped at 5,000 messages a second and a 25 GB backlog. | 500 requests per second of throughput on Team; higher tiers are not published as a number. |

## Where they differ

### Pricing model

- Cloudflare Queues: Billed per operation, not per message: one operation per 64 KB written, read or deleted, and a message larger than 64 KB counts as several. Cloudflare states a normal delivery takes three operations — one write, one read, one delete — so a million messages is nearer three million operations. Workers Paid includes 1,000,000 operations a month, then $0.40 per million; the free plan allows 10,000 a day. ([source](https://developers.cloudflare.com/queues/platform/pricing/))
- 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))

### Included per month

- Cloudflare Queues: 1,000,000 operations a month on Workers Paid, then $0.40 per million. An operation is each 64 KB written, read or deleted, so a typical message costs three — Cloudflare's own formula is ((messages × 3) − 1,000,000) / 1,000,000 × $0.40. Workers Free allows 10,000 operations a day. ([source](https://developers.cloudflare.com/queues/platform/pricing/))
- 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))

### Message retention

- Cloudflare Queues: 4 days by default on Workers Paid, configurable up to 14 days. Workers Free is fixed at 24 hours. ([source](https://developers.cloudflare.com/queues/platform/pricing/))
- Hatchet: 3 days on the Team plan, stated alongside a 500 requests-per-second throughput ceiling. ([source](https://hatchet.run/pricing))

### Concurrency

- Cloudflare Queues: 250 concurrent consumer invocations, push-based only, with per-queue throughput capped at 5,000 messages a second and a 25 GB backlog. ([source](https://developers.cloudflare.com/queues/platform/limits/))
- Hatchet: 500 requests per second of throughput on Team; higher tiers are not published as a number. ([source](https://hatchet.run/pricing))

## Which should you choose?

Pick Cloudflare Queues if Workers applications that want a queue with no egress or throughput charges and a retention window measured in days rather than hours.

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.

Consider something else: Cloudflare Queues — Billing is per 64 KB operation rather than per message, so a large payload or a chatty retry loop costs several times what the message count suggests.

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.

## Documented by only one

- Entry paid plan: Hatchet: $500/month for Team, which adds users, tenants, retention and throughput on top of usage. Scale is $1,000/month.
- Regions: Hatchet: 3 live AWS regions (Oregon, N. Virginia, Ireland) plus Sydney in private beta; control plane in aws-us-west-2.
- Maximum message size: Cloudflare Queues: 128 KB per message, with roughly 100 bytes of that taken by internal metadata. Messages above 64 KB are billed as multiple operations.
- Maximum delay: Cloudflare Queues: 24 hours, set with delaySeconds when sending or retrying.
- Dead letter queue: Cloudflare Queues: Supported
- SOC 2: Hatchet: SOC 2 Type II compliant; reports available through the Hatchet Trust Center.
- HIPAA: Hatchet: HIPAA compliant per the security docs; the Scale plan ($1,000/mo) lists audit logs and HIPAA.
- GDPR / data residency: Hatchet: GDPR compliant per the security docs; EU data plane available in aws-eu-west-1 (Ireland).
- Encryption at rest: Hatchet: Data stored in Hatchet Cloud is encrypted at rest; API and worker traffic encrypted with TLS in transit.
- Role-based access control: Hatchet: Hierarchical tenant roles OWNER, ADMIN, MEMBER, VIEWER plus organization roles; payload visibility can be restricted per member.
- Dedicated infrastructure: Hatchet: Bring-your-own-cloud and self-host support on the Enterprise plan (contact sales).

## Questions this comparison answers

**Should I choose Cloudflare Queues or Hatchet?**

Pick Cloudflare Queues if Workers applications that want a queue with no egress or throughput charges and a retention window measured in days rather than hours.
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.