Cloudflare Queues vs Zeplo
SEPT 2026 auditA comparison of Cloudflare Queues and Zeplo built from values read directly from each provider's own documentation, with the source recorded against every figure.
The short answer
Choose Cloudflare Queues if…
Workers applications that want a queue with no egress or throughput charges and a retention window measured in days rather than hours.
Editorial · Palash Bagchi · approved
Choose Zeplo if…
Turning an HTTP endpoint into a queued, retried job without running a consumer — and keeping a month of logs while doing it, which nothing else here offers on a free plan.
Editorial · Palash Bagchi · approved
Consider something else if…
- Cloudflare Queues: Billing is per 64 KB operation rather than per message, so a large payload or a chatty retry loop costs several times what the message count suggests.
- Zeplo: The free tier's overage is $20 per 100,000 requests, twenty times the Company plan's rate, so staying free past 500 requests is the most expensive way to use it.
6 sourced criteria separate them — see where, with sources, below.
Pick the criteria you care about. The chart counts how many of them lean toward each provider — the same read as scanning the bars below, just totalled for the ones you chose.
Cloudflare Queues 0
Zeplo 0
At a glance.
| Criterion | Cloudflare Queues | Zeplo |
|---|---|---|
| Pricing | ||
| Free tier | Yes | Yes |
| Pricing model | Billed per operation, not per message: one operation per 64 KB written, read or deleted, and a message larger than 64 KB counts as several. Cloudflare states a normal delivery takes three operations — one write, one read, one delete — so a million messages is nearer three million operations. Workers Paid includes 1,000,000 operations a month, then $0.40 per million; the free plan allows 10,000 a day. | Per HTTP request rather than per message or per execution, with unlimited jobs on every tier and team size as a separate axis — three members included on Company, $15 for each beyond. |
| Queues | ||
| Included per month | 1,000,000 operations a month on Workers Paid, then $0.40 per million. An operation is each 64 KB written, read or deleted, so a typical message costs three — Cloudflare's own formula is ((messages × 3) − 1,000,000) / 1,000,000 × $0.40. Workers Free allows 10,000 operations a day. | 500 requests free, then $20 per 100,000. The Company plan includes 1,000,000 requests and charges $10 per million beyond — five times cheaper per request than the free plan's overage rate. |
| Maximum message size | 128 KB per message, with roughly 100 bytes of that taken by internal metadata. Messages above 64 KB are billed as multiple operations. | 256 KB inline request body (unlimited via S3 offload); plan payload caps are 64 KB on Developer and 1 MB on Company. |
| Message retention | 4 days by default on Workers Paid, configurable up to 14 days. Workers Free is fixed at 24 hours. | 30 days of log retention on every plan — free, Company and Enterprise alike. The longest window in this category by a wide margin. |
| Maximum delay | 24 hours, set with delaySeconds when sending or retrying. | 30 days (2,592,000 seconds) maximum delay_seconds per request. |
| Concurrency | 250 concurrent consumer invocations, push-based only, with per-queue throughput capped at 5,000 messages a second and a 25 GB backlog. | API rate limit rather than a concurrency figure: 100 requests/min on Developer (Free) and 2,000 requests/min on Company ($39/mo). |
Where they differ.
Pricing model
- Cloudflare Queues
- Billed per operation, not per message: one operation per 64 KB written, read or deleted, and a message larger than 64 KB counts as several. Cloudflare states a normal delivery takes three operations — one write, one read, one delete — so a million messages is nearer three million operations. Workers Paid includes 1,000,000 operations a month, then $0.40 per million; the free plan allows 10,000 a day.
- Zeplo
- Per HTTP request rather than per message or per execution, with unlimited jobs on every tier and team size as a separate axis — three members included on Company, $15 for each beyond.
Sources (2) →Sources ↓
- Pricing — Cloudflare Queues docs ↗
“An operation is counted for each 64 KB of data that is written, read, or deleted. [...] Standard operations 10,000 operations/day included 1,000,000 operations/month included + $0.40/million operations [...] In most cases, it takes 3 operations to deliver a message: 1 write, 1 read, and 1 delete.”
Read 2026-09-07 · official docs
- Pricing — Zeplo ↗
“Jobs Unlimited Unlimited Unlimited Included team members 1 3 Custom Addition team members $15 $15 $15 Log retention 30 days 30 days 30 days”
Read 2026-09-06 · official pricing
Included per month
- Cloudflare Queues
- 1,000,000 operations a month on Workers Paid, then $0.40 per million. An operation is each 64 KB written, read or deleted, so a typical message costs three — Cloudflare's own formula is ((messages × 3) − 1,000,000) / 1,000,000 × $0.40. Workers Free allows 10,000 operations a day.
- Zeplo
- 500 requests free, then $20 per 100,000. The Company plan includes 1,000,000 requests and charges $10 per million beyond — five times cheaper per request than the free plan's overage rate.
Sources (2) →Sources ↓
- Pricing — Cloudflare Queues docs ↗
“1,000,000 operations/month included + $0.40/million operations [...] An operation is counted for each 64 KB of data that is written, read, or deleted. [...] In most cases, it takes 3 operations to deliver a message [...] 10,000 operations/day included”
Read 2026-09-06 · official docs
- Pricing — Zeplo ↗
“Free 500 requests included $20 / 100k requests [...] $39 /month 1M requests included $10 / million requests”
Read 2026-09-06 · official pricing
Maximum message size
128 KB per message, with roughly 100 bytes of that taken by internal metadata. Messages above 64 KB are billed as multiple operations.
256 KB inline request body (unlimited via S3 offload); plan payload caps are 64 KB on Developer and 1 MB on Company.
Sources (2) →Sources ↓
- Limits — Cloudflare Queues docs ↗
“Message size | 128 KB [...] Messages can include up to ~100 bytes of internal metadata that counts towards total message limits.”
Read 2026-09-06 · official docs
- Limits - Zeplo docs ↗
“Maximum request body size 256KB inline, unlimited via S3 offload [...] Max payload 64KB 1MB”
Read 2026-09-13 · official docs
Message retention
4 days by default on Workers Paid, configurable up to 14 days. Workers Free is fixed at 24 hours.
30 days of log retention on every plan — free, Company and Enterprise alike. The longest window in this category by a wide margin.
Sources (2) →Sources ↓
- Pricing — Cloudflare Queues docs ↗
“Message retention | 24 hours (non-configurable) | 4 days default, configurable up to 14 days”
Read 2026-09-06 · official docs
- Pricing — Zeplo ↗
“Log retention 30 days 30 days 30 days”
Read 2026-09-06 · official pricing
Maximum delay
24 hours, set with delaySeconds when sending or retrying.
30 days (2,592,000 seconds) maximum delay_seconds per request.
Sources (2) →Sources ↓
- Limits — Cloudflare Queues docs ↗
“delaySeconds (when sending or retrying) | 24 hours”
Read 2026-09-06 · official docs
- Limits - Zeplo docs ↗
“Maximum delay_seconds 2,592,000 (30 days)”
Read 2026-09-13 · official docs
Concurrency
- Cloudflare Queues
- 250 concurrent consumer invocations, push-based only, with per-queue throughput capped at 5,000 messages a second and a 25 GB backlog.
- Zeplo
- API rate limit rather than a concurrency figure: 100 requests/min on Developer (Free) and 2,000 requests/min on Company ($39/mo).
Sources (2) →Sources ↓
- Limits — Cloudflare Queues docs ↗
“Concurrent consumer invocations | 250 push-based only [...] Per-queue message throughput | 5,000 messages per second [...] Per-queue backlog size | 25GB”
Read 2026-09-06 · official docs
- Limits - Zeplo docs ↗
“Plan API rate limit Developer (Free) 100 requests/min Company ($39/mo) 2,000 requests/min”
Read 2026-09-13 · official docs
When these numbers change, hear about it. Sources are re-checked monthly; a repricing goes out as a short note.
Documented by only one.
These criteria are published by one provider and not the other. An absence here means we have not found a source, not that the feature is missing.
Questions this comparison answers.
Should I choose Cloudflare Queues or Zeplo?
Pick Cloudflare Queues if Workers applications that want a queue with no egress or throughput charges and a retention window measured in days rather than hours.
Pick Zeplo if Turning an HTTP endpoint into a queued, retried job without running a consumer — and keeping a month of logs while doing it, which nothing else here offers on a free plan.