# Cloudflare Queues

> Fine when producer and consumer are both Workers. Inside AWS, SQS wins.

- Verdict: Skip (Proposed: research-backed, not yet confirmed by Nic)
- Vendor: Cloudflare
- Layer: [APIs, queues and events](https://cloudlesslabs.com/stack/layers/api-events.md)
- Last reviewed: 18 October 2026, by Nicolas Dao (Cloudless Labs, Sydney)
- Web page: https://cloudlesslabs.com/stack/cloudflare-queues/. The whole stack in one file: https://cloudlesslabs.com/stack/brief.md

No FIFO, no IAM, no Lambda back-pressure, and ten times SQS's cost at volume. I don't need it.

## Use it when

- Both ends run on Workers, or you need delays longer than 15 minutes.

## Don't use it when

- Anything inside AWS. SQS has FIFO, IAM and batched Lambda consumers.

## Pricing

$0.40 per million operations (each write, read and delete; about 3 per message), billed per message so batching saves nothing. 50M messages ≈ $60 vs about $6 on SQS batched.

## Gotchas, with fixes

- **Gotcha:** Without a dead-letter queue, failed messages are deleted.
  **Fix:** Always configure a DLQ.

## Provisioning

Official Pulumi package · Official Terraform provider

## Use instead

SQS: FIFO, IAM and batched Lambda consumers, inside AWS where the work is.

## Alternatives

- [Amazon SQS](https://cloudlesslabs.com/stack/aws-sqs/index.md): Everything on AWS.

## Sources

- [Queues pricing](https://developers.cloudflare.com/queues/platform/pricing/)

## Related

- [APIs, queues and events](https://cloudlesslabs.com/stack/layers/api-events.md): every tool in this layer, with its verdict
- [The whole stack in one file](https://cloudlesslabs.com/stack/brief.md): every use case and tool, for questions that span many
- [Map of every Markdown file on cloudlesslabs.com, with what each one answers](https://ask.cloudlesslabs.com)