Runtimes & workflows
Durabull vs Cloudflare Queues
Cloudflare Queues is the message queue for Workers. Messages are not BullMQ jobs. The pricing page’s own formula is ((N × 3) − 1,000,000) / 1,000,000 × $0.40, plus the $5/mo Workers Paid minimum.
Choose Cloudflare Queues when your application runs on Workers and you want messages to stay on Cloudflare.
Choose Durabull when your runtime is Node.js workers on Redis + BullMQ and you need to operate those queues.
Capabilities
The details that change the decision
| Feature | Durabull | Cloudflare Queues |
|---|---|---|
| 1M messages (3 ops) | Free to start + your infrastructure | $5.80 ($5 plan + $0.80 ops) |
| 10M messages | Free to start + your infrastructure | $16.60 |
| 100M messages | Free to start + your infrastructure | $124.60 |
Setup
How Cloudflare Queues connects
Workers produce and consume messages through queue bindings; HTTP pull consumers are also supported. Cloudflare hosts the queue.
Application changes. Yes to leave BullMQ.
- Queue discovery
- N/A.
- Environments
- Cloudflare accounts and queues.
- Alerts
- Cloudflare notifications and metrics. Not BullMQ rules.
- AI & MCP
- Cloudflare publishes official MCP servers (for example Workers Bindings and Workers Observability), but we found no dedicated Queues operations server. None reads BullMQ.
Economics
Understand what you are paying for
- Cloudflare Queues pricing
- As of 2026-10-20: Workers Paid ($5/mo minimum) includes 1M queue operations per month, then $0.40 per million. Each write, read, and delete counts per 64 KB; typically 3 operations per message, and each retry adds a read. Workers Free includes 10,000 operations per day.
- Cloudflare Queues license
- Proprietary Cloudflare managed service.
- Durabull
- Hosted dashboard is free to start. Redis, worker compute, and infrastructure operations remain your costs. Check the pricing page for current terms. Apache License 2.0 (OSI-approved open source). Self-host on your own infrastructure.
| Volume | Runtime / product charges | Durabull hosted fee | Unit |
|---|---|---|---|
| 1M messages | $5.80 | Free to start + your infrastructure | 3 ops/message |
| 10M messages | $16.60 | Free to start + your infrastructure | 3 ops/message |
| 100M messages | $124.60 | Free to start + your infrastructure | 3 ops/message |
Cloudflare example using pricing as of 2026-10-20: three operations per message, payload no larger than 64 KB, full 1M monthly operation allowance, plus $5 Workers Paid. Excludes retries and additional Worker compute; an existing paid subscription changes the incremental cost. Durabull’s free-to-start hosted dashboard excludes Redis, workers, and operations.
Questions about Cloudflare Queues and Durabull
Why three operations per message?
Cloudflare documents write, read, and delete as separate billable operations, each per 64 KB, and says most messages take three operations to deliver. Its pricing page uses messages × 3 in the worked formula.
Evidence
Sources & methodology
Durabull details: product documentation, pricing, and MCP reference. Found a change? Send a correction.
Continue your research
- Durabull vsUpstash QStashServerless HTTP push queue. Pay-as-you-go $1 per 100K messages. Not Redis, not BullMQ.
- Durabull vsAmazon SQS + Step FunctionsManaged AWS queue plus optional orchestrator. Low per-request prices, but every API call bills, including empty receives. Not BullMQ.
- Durabull vsInngestReplaces BullMQ. Cloud bills executions (run + each step). Official MCP inspects Inngest runs, not Redis queues.
Connect Redis. Queues appear.
Inspect your Redis-backed BullMQ queues in one place. Hosted Durabull is free to start.