Cost visualization
Enter your assumptions
Formula used
Billable edge egress (GB) = max(0, Edge Egress − Free Egress)
Edge bandwidth cost = Billable Egress × Price per GB × Region Multiplier
Billable requests (M) = max(0, Requests − Free Requests)
Request cost = Billable Requests × Price per 1M × Region Multiplier
Subtotal = Bandwidth + Requests + Storage + Origin + Logs + Add-ons
After discount = Subtotal − (Subtotal × Discount%)
Total = After discount + (After discount × Tax%)
How to use this calculator
- Enter usage, region, unit rates, and add-ons.
- Add free tier, discount, and tax if applicable.
- Calculate, review the breakdown, then export CSV or PDF.
Bandwidth is usually the primary cost driver
Most CDN invoices scale with outbound delivery. If you serve 2,500 GB per month at $0.08 per GB, edge bandwidth alone is $200 before regional uplift. A 1.15 regional multiplier increases that line item to $230, which can exceed fixed add-ons.
If your monthly egress doubles, costs rarely double exactly because tiered rates apply, but budgeting with your contracted unit rate keeps forecasts conservative and helps spot savings targets over time too.
Requests matter when traffic is API-heavy
Request pricing becomes visible when objects are small but frequent. At 80 million requests and $0.75 per million, the request line is $60. With the same 1.15 multiplier, it becomes $69. Optimizing cacheability and using longer TTLs can reduce request volume at the edge.
Origin fetch reflects cache effectiveness
Origin fetch is the backhaul you pay to pull content into cache. If origin fetch is 400 GB at $0.02, the cost is $8. Improving hit ratio from 70% to 80% can reduce origin load in practice, while keeping user delivery steady. The calculator also estimates cache-served traffic using your hit ratio.
Storage and logs are steady, predictable lines
Storage is commonly billed per GB-month. With 250 GB at $0.02, storage adds $5. Logs and analytics exports can add meaningful spend at scale; for 50 GB at $0.03, log delivery adds $1.50. These lines help you capture operational features in the same forecast.
When you negotiate, ask for separate rates for regional egress, free-tier bundles, and committed-use discounts. Small changes, like lowering egress by 5% or improving hit ratio by 5 points, can fund add-ons such as security or support without raising budgets.
Discounts and taxes change the final payable total
Contract discounts are usually applied to the subtotal, then taxes are applied after discounts. For example, a 10% discount on a $400 subtotal saves $40, and a 5% tax on the discounted $360 adds $18. Use this structure to compare providers consistently across scenarios.
FAQs
1) What inputs matter most for accuracy?
Bandwidth and request volume usually dominate, but fixed add-ons, regional uplift, and free-tier limits can shift totals significantly for smaller workloads.
2) Why is there a region multiplier?
Many providers apply higher rates in certain geographies. The multiplier approximates that uplift so you can compare scenarios consistently across regions.
3) How should I estimate origin fetch?
Start with current origin egress metrics. If you do not have them, approximate origin fetch as (1 \u2212 hit ratio) \u00d7 edge egress, then refine once you have logs.
4) Does cache hit ratio change the cost directly?
Not directly in this calculator\u2019s total. It is used to estimate cache-served traffic and inform how origin fetch may change when your caching improves.
5) Can I model committed-use discounts?
Yes. Enter your effective discount percentage as negotiated. If your contract has tiered pricing, rerun scenarios with the expected blended unit rates.
6) What should I export and share internally?
Download the CSV or PDF after calculating. Share the breakdown, assumptions, and region selection so stakeholders can validate inputs and approve budgets.