starter.wiki

Managed message queue

Cloudflare Queues

A Workers-native managed queue with batching, delay, retries, consumer concurrency, and dead-letter queues.

Visit official site

Editorial verdict

Choose Cloudflare Queues when Workers-native transport removes more integration work than Cloudflare coupling and at-least-once design create.14567

Best for

  • Workers producers and consumers
  • Managed batch, retry, delay, and DLQ handling
  • Teams avoiding a second cloud control plane
14567

Not ideal for

  • Provider-neutral broker requirements
  • Enterprise topics and sessions
  • Applications whose consumers do not fit Workers
14567
Main trade-off

Tight Workers integration trades against Cloudflare coupling, at-least-once consumer design, and product-specific limits.14567

Product boundary

Whether Workers-native managed queue transport is the right delivery and consumer model.

Queues transports messages. Workers executes consumers; durable Background Jobs, CDN, DNS, and generic Cloudflare products remain separate.4

For: Cloudflare Workers applications whose producers or consumers already live in the Cloudflare service graph

  • Consumers do not fit Workers runtime semantics.
  • At-least-once duplicates cannot be handled.
  • Broker topics/sessions or provider-neutral operation are required.

Why teams consider Cloudflare Queues

  • Workers-native graphProducers and consumers integrate directly with Workers bindings.4
  • Managed failure controlsBatching, retry, delay, concurrency, and DLQs are configurable.4
  • No queue clusterThe team does not operate separate broker infrastructure.4

Pricing

Queue operations and message-size chunks are metered separately from Workers consumer compute and other Cloudflare products.6

Evaluation

Free — 10,000 operations per day

Verified 2026-07-25; Free retention and limits differ from Paid.6

Production

Paid — 1 million operations included monthly, then $0.40 per million

Writes, reads, deletes, retries, and 64 KB chunks affect operations; Workers compute is separate.6

Primary meter
Queue operations in 64 KB chunks6
Separate cost
Workers producer/consumer compute and adjacent products6
Pricing checked View official pricing

Cloudflare Queues vs alternatives

Amazon SQS

Choose when
Choose it for an AWS-native pull queue.
Compared with Cloudflare Queues
AWS integration with separate consumers and multi-service operations.13

Upstash QStash

Choose when
Choose it when a signed HTTP endpoint should receive deliveries directly.
Compared with Cloudflare Queues
Lower consumer infrastructure with delivery/retry billing.79

Azure Service Bus

Choose when
Choose it for enterprise topics, subscriptions, or sessions.
Compared with Cloudflare Queues
Richer broker model with more complexity.1012

Resources and sources

Official product, policy, and pricing

  • Cloudflare Queues documentation
    Open
  • Cloudflare Queues delivery guarantees
    Open
  • Cloudflare Queues pricing
    Open
  1. 1
    Amazon SQS developer guide

    Amazon Web Services · Accessed Official

  2. 2
    Amazon SQS at-least-once delivery

    Amazon Web Services · Accessed Official

  3. 3
    Amazon SQS pricing

    Amazon Web Services · Accessed Official

  4. 4
    Cloudflare Queues documentation

    Cloudflare · Accessed Official

  5. 5
    Cloudflare Queues delivery guarantees

    Cloudflare · Accessed Official

  6. 6
    Cloudflare Queues pricing

    Cloudflare · Accessed Official

  7. 7
    Upstash QStash queues

    Upstash · Accessed Official

  8. 8
    Upstash QStash retries

    Upstash · Accessed Official

  9. 9
    Upstash QStash pricing

    Upstash · Accessed Official

  10. 10
    Azure Service Bus overview

    Microsoft · Accessed Official

  11. 11
    Azure Service Bus sessions

    Microsoft · Accessed Official

  12. 12
    Azure Service Bus pricing

    Microsoft · Accessed Official