A mid-size SaaS company running Cloudflare Pro at $20/month can quietly spend $600+ once Argo Smart Routing, Load Balancing, Workers, and a few certificates stack up. That gap between the plan sticker price and the real invoice is where cloudflare add-on services pricing catches teams off guard. As of Q2 2026, Cloudflare lists over a dozen billable add-ons, most usage-based, and some with metering models that changed within the last twelve months. This article gives you the full line-item cost breakdown, a workload-profile decision matrix you will not find in the docs, and the thresholds where each add-on stops making financial sense.
Cloudflare's base plans — Free, Pro ($20/mo), Business ($200/mo), Enterprise (custom) — gate access to certain add-ons, but most carry their own separate charges. Here is what each costs as of May 2026.
Argo bills at $5/month base plus $0.10 per GB of data transferred through its optimized paths. For a site serving 500 GB/month through Argo, that is roughly $55/month. Argo Tiered Caching, previously bundled, is now free for all paid plans as of late 2025 — a meaningful change, since it was formerly the main reason some teams enabled Argo. If tiered caching was your only motivation, re-evaluate whether you still need the $0.10/GB metered routing.
Workers operate on the Workers Paid plan at $5/month, which includes 10 million requests. Beyond that, pricing is $0.30 per additional million requests (as of 2026). CPU time is metered at $0.02 per million milliseconds. Workers KV adds $5/month for 10 million reads, $0.50 per additional million reads, and $0.50 per million writes. Durable Objects follow a separate model: $0.15 per million requests plus $0.20 per GB-month of storage. Teams running heavy edge compute workloads regularly see Workers bills exceed $100/month before they instrument proper cost tracking.
Load Balancing starts at $5/month for 2 origins and 5 DNS-level health checks, adding $5/month per additional origin. Geo-steering and session affinity require Business or Enterprise plans. Steering via least-connections or random is included. Fifteen health checks per origin pool is the ceiling on Pro. At $5 per origin, a deployment with 8 origins across two pools costs $35/month — modest, but it compounds alongside other add-ons.
ACM is $10/month per zone. It enables custom hostnames on dedicated certificates, cipher suite control, and certificate lifecycle management beyond what Universal SSL provides. For multi-tenant SaaS platforms issuing certificates per customer subdomain, Cloudflare for SaaS (SSL for SaaS) is a separate product with per-hostname pricing — $0.10 per active custom hostname per month (first 100 free on Enterprise).
Legacy rate limiting charges $0.05 per 10,000 good requests matched against rules. It remains available but is functionally superseded by Advanced Rate Limiting, which is included in the WAF on Business and Enterprise plans at no additional per-request cost. If you are still on Pro and using legacy rate limiting with high request volumes, the per-request charges can become material — 50 million good matches per month equals $250.
Cache Reserve uses R2 storage pricing underneath: $0.015 per GB stored per month, plus standard R2 Class A/B operation costs. There is no separate Cache Reserve fee beyond the storage. The value proposition is origin offload — if your origin egress costs exceed $0.015/GB, Cache Reserve pays for itself. At 1 TB of cached content, expect approximately $15/month in storage plus negligible operation charges.
Cloudflare Images costs $5/month for 100,000 stored images and $1 per 100,000 delivered. Stream costs $5 per 1,000 minutes stored and $1 per 1,000 minutes delivered. R2 storage is $0.015/GB/month with zero egress fees — the zero-egress model is R2's differentiator, but Class A operations ($4.50 per million) add up in write-heavy workloads.
Three shifts matter this year. First, Argo Tiered Caching decoupled from the paid Argo add-on in late 2025 and is now free on all paid plans. This removed a common reason to enable Argo, so audit whether you still need metered smart routing. Second, Workers pricing consolidated under the "Workers Paid" plan, retiring the older per-plan bundled request limits. Third, Cloudflare quietly increased the free tier for Pages and Workers to be more generous with build minutes and request counts, making the paid threshold higher for smaller projects. None of these changes apply retroactively to Enterprise contracts negotiated before Q4 2025 — check your specific MSA.
Not every add-on delivers ROI for every architecture. This matrix maps workload types to the add-ons worth evaluating.
| Workload Profile | High-Value Add-Ons | Low-Value / Skip | Typical Monthly Add-On Spend |
|---|---|---|---|
| Media/Video Delivery (50+ TB/mo) | Cache Reserve, Load Balancing, R2 | Argo (cost explodes at volume), Workers (unless doing edge transforms) | $200–$800+ |
| Multi-Tenant SaaS | ACM / SSL for SaaS, Workers, Access | Argo (marginal latency gain vs. cost), Cache Reserve (low static asset volume) | $50–$400 |
| E-Commerce (high origin dependence) | Argo Smart Routing, Load Balancing, Advanced Rate Limiting | Stream, Images (unless UGC-heavy) | $60–$300 |
| API-First / Headless | Workers, Workers KV/Durable Objects, Rate Limiting | Images, Stream, Cache Reserve (API responses are small) | $30–$200 |
| Internal Tools / Zero Trust | Access, Gateway, WARP | Argo, Load Balancing (internal traffic is low-volume) | $7/user (Gateway) + Access seats |
The key takeaway: Argo Smart Routing delivers measurable latency reduction on origin-heavy, cacheable workloads under ~10 TB/month. Past that threshold, the $0.10/GB charge compounds quickly and you should model whether origin optimization or a dedicated delivery network yields better cost-per-millisecond-saved.
Usage-based billing is defensible when consumption is predictable. It breaks down for media delivery and software distribution, where traffic is spiky and volumes are large. A 100 TB/month workload running through Argo alone generates $10,000/month in routing fees — before any plan or other add-on costs. At that scale, teams typically move delivery to a volume-priced CDN and keep Cloudflare for DNS, WAF, and Zero Trust.
For organizations in exactly that position, BlazingCDN's volume-based pricing offers a clear alternative for the delivery layer. At 100 TB/month, BlazingCDN charges $350/month flat with overages at $0.0035/GB — a fraction of what metered Cloudflare add-ons cost at that volume. At 1 PB+, the rate drops to $0.0025/GB. The platform delivers uptime and fault tolerance comparable to Amazon CloudFront, with flexible scaling under demand spikes, making it a fit for enterprises that need predictable delivery costs without sacrificing reliability.
A Business plan ($200/month) with Argo, Load Balancing (4 origins), ACM, and Workers typically lands between $280 and $450/month total, depending on traffic volume. The base plan price is often less than half the real invoice once usage-based meters are running.
At volumes under 10 TB/month, Argo's latency improvements frequently justify the $0.10/GB cost — expect 20–35% reduction in TTFB for uncached requests. Above 10 TB, model the per-GB cost against origin infrastructure improvements or a volume-priced delivery provider. The math usually favors the latter.
Cache Reserve uses R2 storage pricing ($0.015/GB/month) with no additional markup. You pay R2 operation costs on top. They appear as separate line items on your invoice, but Cache Reserve does not carry its own subscription fee.
The minimum is $5/month on a Pro plan for 2 origins with DNS-level steering. Each additional origin is $5/month. Geo-steering requires Business ($200/month base). If you only need failover between two origins, the $5 entry is reasonable. For anything more complex, compare against your cloud provider's native load balancer costs.
Set up billing alerts in the Cloudflare dashboard under Account > Billing > Subscriptions. Use Workers usage analytics to track request counts weekly. For Argo, monitor the "Argo" analytics tab to see exactly how many GB are routed monthly. There is no hard cap or budget-limit feature as of May 2026 — if usage spikes, you pay.
Pull your last three Cloudflare invoices and break out what you are actually paying per add-on. Map each line item against the decision matrix above. If any single add-on exceeds your base plan cost, that is a signal to benchmark alternatives for that specific function. Instrument your origin hit rate — if it is above 40%, Cache Reserve or a delivery-layer change will move the needle faster than Argo. Post your findings in your team's infrastructure channel. The conversation about where to optimize rarely starts until someone puts real numbers in front of people.