Skip to content
inetGeek

Cloudflare Queues vs Hatchet

SEPT 2026 audit

A comparison of Cloudflare Queues and Hatchet built from values read directly from each provider's own documentation, with the source recorded against every figure.

Updated 16 criteria comparedSources last checked

The short answer

Choose 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.

Editorial · Palash Bagchi · approved

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

Consider something else if…

  • 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.
  • 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.

4 sourced criteria separate them — see where, with sources, below.

Visit Cloudflare Queues documentationVisit Hatchet documentation

No affiliate links, sponsored placements or paid rankings appear on this site. Ordering follows the sourced data and the stated criteria.

01.

At a glance.

CriterionCloudflare QueuesHatchet
Pricing
Free tierYesYes
Pricing modelBilled 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.
Queues
Included per month1,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.

Only criteria both providers publish appear here; a tinted cell marks a real difference. Criteria only one of them documents are listed below, and an absence there means we found no source — not that the feature is missing. How we source this.

The small bar above a value is inetGeek's own lean toward that side — computed from the same facts shown, never a number the provider published. See the picker below "The short answer" to weigh only the criteria you care about.

02.

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.
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.
Sources (2) →
  • Pricing — Cloudflare Queues docs ↗

    “An operation is counted for each 64 KB of data that is written, read, or deleted. [...] Standard operations 10,000 operations/day included 1,000,000 operations/month included + $0.40/million operations [...] In most cases, it takes 3 operations to deliver a message: 1 write, 1 read, and 1 delete.”

    Read 2026-09-07 · official docs

  • 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

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.
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.
Sources (2) →
  • Pricing — Cloudflare Queues docs ↗

    “1,000,000 operations/month included + $0.40/million operations [...] An operation is counted for each 64 KB of data that is written, read, or deleted. [...] In most cases, it takes 3 operations to deliver a message [...] 10,000 operations/day included”

    Read 2026-09-06 · official docs

  • Pricing — Hatchet ↗

    “Developer Free + usage $10 per 1M task runs First 100,000 runs included”

    Read 2026-09-06 · official pricing

Message retention

Cloudflare Queues

4 days by default on Workers Paid, configurable up to 14 days. Workers Free is fixed at 24 hours.

Hatchet

3 days on the Team plan, stated alongside a 500 requests-per-second throughput ceiling.

Sources (2) →

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.

Hatchet

500 requests per second of throughput on Team; higher tiers are not published as a number.

Sources (2) →
  • Limits — Cloudflare Queues docs ↗

    “Concurrent consumer invocations | 250 push-based only [...] Per-queue message throughput | 5,000 messages per second [...] Per-queue backlog size | 25GB”

    Read 2026-09-06 · official docs

  • Pricing — Hatchet ↗

    “3-day retention 500 RPS throughput See all features”

    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.

Confirm by email; unsubscribe from any issue. Your address goes to Kit and nowhere else — what we do with it.

03.

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.

Entry paid planHatchet: $500/month for Team, which adds users, tenants, retention and throughput on top of usage. Scale is $1,000/month.
RegionsHatchet: 3 live AWS regions (Oregon, N. Virginia, Ireland) plus Sydney in private beta; control plane in aws-us-west-2.
Maximum message sizeCloudflare 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 delayCloudflare Queues: 24 hours, set with delaySeconds when sending or retrying.
Dead letter queueCloudflare Queues: Supported
SOC 2Hatchet: SOC 2 Type II compliant; reports available through the Hatchet Trust Center.
HIPAAHatchet: HIPAA compliant per the security docs; the Scale plan ($1,000/mo) lists audit logs and HIPAA.
GDPR / data residencyHatchet: GDPR compliant per the security docs; EU data plane available in aws-eu-west-1 (Ireland).
Encryption at restHatchet: Data stored in Hatchet Cloud is encrypted at rest; API and worker traffic encrypted with TLS in transit.
Role-based access controlHatchet: Hierarchical tenant roles OWNER, ADMIN, MEMBER, VIEWER plus organization roles; payload visibility can be restricted per member.
Dedicated infrastructureHatchet: Bring-your-own-cloud and self-host support on the Enterprise plan (contact sales).
04.

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.

Provider pages

Cloudflare QueuesMessage queue on Cloudflare Workers, billed per 64 KB operation with no egress or throughput charges.HatchetDurable task queue billed per task run, with a free tier, published throughput limits and a self-hosted option.

Related comparisons

Amazon SQS vs Cloudflare QueuesAmazon SQS vs HatchetAzure Queue Storage vs HatchetCloudflare Queues vs Azure Queue StorageCloudflare Queues vs Google Cloud Pub/SubCloudflare Queues vs InngestCloudflare Queues vs Upstash QStashCloudflare Queues vs Temporal

Every page here is sourced and dated.