Queues ETL pipeline: about $16.60 a month on Workers Paid

A month that looks like the numbers below comes to roughly $16.60, base fee included. The meter that runs out first is Queues operations, at 3000% of its included usage. Prices are the public list as of 2026-09-15; the real invoice is the only truth.

Adjust the numbers → ← Usage Guard

Usage assumed for the month

• Workers requests: 3M
• Workers CPU time (ms): 20M
• D1 rows written: 20M
• Queues operations: 30M

What this setup looks like

An ingest Worker receives webhooks and puts each event on a queue; a consumer batches them into D1. Ten million events a month sounds like ten million operations. It is thirty million, because Queues bills the write, the read and the acknowledgement as separate operations. That factor of three is the part most first budgets miss.

Why Queues operations runs out first

Workers Paid includes 1M Queues operations a month. At 30M this pipeline is at 3000% of that, and the overage is the biggest line even though the Worker and D1 behind it sit inside their allowances. Every retry adds another read and another ack, so a consumer that keeps failing on one bad message multiplies the count without moving any data.

What to watch in GraphQL Analytics

queueMessageOperationsAdaptiveGroups by queue and day, split by action. Reads should stay close to writes; if reads run well ahead, messages are being retried. Send poison messages to a dead-letter queue after a couple of attempts. Batch size does not change the operation count, but it does cut the D1 writes behind it.

Prices and included usage copied from Cloudflare's public pricing pages on 2026-09-15. Approximate: some meters round up to the next unit, Workers AI and bandwidth are not included, and the real invoice is the only truth.

Other typical bills

• Static site with a Worker
• D1-heavy API
• Durable Objects alarm loop
• KV session cache
• R2 media site

Also exploring

Paying for Workers and wary of a surprise invoice? See Usage Guard — per-metric spike alerts and an optional stop switch.

Routing support@ through Cloudflare and reading it in Gmail? See Routed Inbox — a small shared inbox on Email Routing, no seat pricing.

Managing Cloudflare for many clients? See Zone Audit — config drift and baseline checks across accounts.