free_tool
What's your cache hit ratio worth?
Every cache hit is a request your origin never serves and an egress byte you pay edge rates for instead of origin rates. Put in your traffic, response size, hit ratio and pricing, and see the dollars the cache saves, the origin load it sheds, and what five more points of hit ratio would add.
Monthly savings
$1,510/mo
$18.1K / year · 91% off the no-CDN bill
7.4M requests / mo kept off the origin.
- Cost without CDN
- $1,654.93/mo
- Cost with CDN
- $144.60/mo
- Egress delivered
- 610 GB
- Origin refill (misses)
- 49 GB
Hit ratio lower than it should be? I'll audit your cache keys, headers and TTLs and find the requests that shouldn't be touching the origin.
Lift your hit ratio: book a callA transparent model of the two costs a cache moves: egress (edge rate vs origin rate, plus origin refill on misses) and origin serving per request. It doesn't price the CDN's own request fees or compute-at-edge; add those from your provider's bill for an exact figure.
how_it_works
The hit ratio is the whole game
A miss costs twice: the origin burns compute to generate the response, then pays origin egress to ship it. A hit costs neither: the edge answers at a cheaper per-GB rate and your origin never wakes up. So the hit ratio is the lever, and small moves compound across millions of requests.
That's why the tool highlights what five more points would save: going from 92% to 97% doesn't feel like much until you see it cuts origin requests by more than half. Cache headers, sane TTLs, and a cache key that doesn't fragment on junk query params are usually the cheapest infrastructure win you have.
faq
Questions & answers
- How does the CDN and Cache Savings Calculator work out savings?
- It prices two scenarios: serving everything from origin versus serving cache hits from the edge. It splits cost into egress per gigabyte and origin request fees, charges origin egress only on cache misses, and the difference between the two scenarios is your savings.
- Why does a small jump in hit ratio save so much?
- Because misses are what hit your origin, raising the hit ratio cuts origin requests faster than it feels. Moving from 92% to 97% can cut origin requests by more than half, which is why the tool also shows the gain from five more points of hit ratio.
- Does it include every line on my CDN bill?
- No. It models egress and origin request costs but leaves out CDN per-request fees and compute-at-edge charges, since those vary by provider. Add those from your own bill for a complete picture.
- Are my traffic and pricing numbers sent anywhere?
- No. The math runs in your browser and nothing is sent to a server. Your inputs are only placed in the URL if you share a link.
- What inputs does it need?
- Monthly requests, average response size, cache hit ratio, and your origin egress, CDN egress and per-thousand origin request prices. It starts from a realistic baseline so you can adjust from there.
Leaving cache savings on the table?
I'll audit your cache keys, headers and TTLs and find the requests that shouldn't be hitting the origin at all. Book a call, or leave your email.
Prefer proof first? See how this plays out in real case studies →