Cloudflare Queues alternatives
Every queues and background jobs provider this site tracks, ordered by iScore — the same peers Cloudflare Queues's own score is measured against. The line under each name is where its sourced facts differ from Cloudflare Queues's; where a full comparison exists, the row links to it.
- Amazon SQSvs Cloudflare QueuesPricing model: Per request, not per message: every API action counts, and a 1 MiB payload is billed as 1…
- Trigger.devvs Cloudflare QueuesPricing model: A monthly plan fee that is also a credit balance — the fee buys compute rather than sitti…
- Google Cloud Pub/Subvs Cloudflare QueuesPricing model: Three meters: throughput at $40 per TiB counting both publish and subscribe, storage at $…
- Upstash QStashvs Cloudflare QueuesPricing model: Per message rather than per operation, metered against a daily ceiling on the free plan a…
- HatchetPricing model: Usage-based with no plan fees: 1M task runs and 1M events free every month, then $30 per…
- ZeploPricing model: Per HTTP request rather than per message or per execution, with unlimited jobs on every t…
- Inngestvs Cloudflare QueuesPricing model: Per execution, where a step counts the same as a run, plus separate meters for events ing…
- Temporalvs Cloudflare QueuesFree tier: No vs Yes · Kind of free offer: Free credit vs Free tier
- Azure Queue Storagevs Cloudflare QueuesFree tier: No vs Yes · Kind of free offer: Free credit vs Free tier
Where Cloudflare Queues stands against these 9
Cloudflare Queues's own sourced figures, placed among the alternatives above that document the same thing in the same unit. A rank here is one criterion, not a verdict; the iScore above weighs all of them.
- Free tier
- Yes. 7 of the 9 alternatives that document it have one: Amazon SQS, Google Cloud Pub/Sub, Hatchet, Inngest, Upstash QStash, Trigger.dev and 1 more.
- Uptime SLA
- 99.9% monthly uptime, in a dedicated Queues SLA that applies to use of Queues only and names no plan tier…Joint 2nd highest of the 4 that document it. Highest: Google Cloud Pub/Sub — 99.95% or better for Pub/Sub.
- Maximum message size
- 128 KB per message, with roughly 100 bytes of that taken by internal metadata8th highest of the 9 that document it. Highest: Inngest — 4 MiB per step-returned payload; 32 MiB total function run state; 10 MiB hard cap per event batch.
- Message retention
- 4 days by default on Workers Paid, configurable up to 14 daysJoint 3rd highest of the 5 that document it. Highest: Azure Queue Storage — 7 days by default, set per message with messagettl; since version 2017-07-29 it can be any positive number…
- Maximum delay
- 24 hours, set with delaySeconds when sending or retrying4th highest of the 5 that document it. Highest: Temporal — Timers (durable sleeps) may run up to 100 years in Temporal Cloud.
- Concurrency
- 250 concurrent consumer invocations, push-based only, with per-queue throughput capped at 5,000 messages a…Highest of the 3 that document it. Next: Trigger.dev — 20 concurrent runs on the free plan, 50 on Hobby, and more on Pro at $10 a month per additional 50.
A rank whose 80% interval overlaps its neighbour's is an ordering, not a finding; the intervals are on each provider's page and in /scores.json.
