Definition
A CDN, or Content Delivery Network, caches and delivers content closer to end users so fewer requests have to travel back to the origin system. It usually improves latency and reduces load on the origin, but it does not make delivery cost disappear. It changes where cost shows up.
Why it matters in pricing decisions
CDNs matter in pricing because they often improve performance while shifting the cost mix into a more complicated combination of egress, request, and cache-behavior economics. A business can lower origin cost and still end up with a pricing problem if CDN request intensity, regional delivery, or cache-miss behavior vary a lot across customers.
The practical issue is whether CDN cost should stay inside a blended rate or become visible through usage pricing, tiering, or a pass-through rule. That depends on how uneven the traffic patterns are.
Where CDN cost changes the model
CDN cost changes the pricing model most when one of three things is true:
- traffic varies a lot by region or customer type
- request-heavy behavior matters as much as transferred GB
- cache misses or origin fetches create a hidden second layer of cost
In those situations, a clean per-GB headline rate can look simpler than the real economics. Teams may need separate thresholds, heavier-account exceptions, or a clearer bandwidth policy rather than pretending all delivered traffic has the same cost.
How to use it with PricingNest tools
Use the Bandwidth Cost Calculator to estimate whether delivered traffic still clears margin once CDN cost is included. If the product also stores content or files, pair it with the Storage Cost Calculator so storage and delivery cost are not accidentally collapsed into one vague number.
When the problem shifts from definition to packaging, move into the CDN Cost Pass-Through guide. That is where the decision becomes whether traffic should be blended, tiered, or exposed more directly.
Common interpretation mistakes
- Assuming a CDN always lowers total cost rather than sometimes relocating it.
- Looking only at GB delivered while ignoring request fees or regional spread.
- Treating cache-hit improvement as permanent even when customer behavior changes.
- Mixing origin and CDN charges together so no one can explain which layer is driving margin pressure.
Example
Suppose a media-heavy SaaS product uses a CDN to serve customer files. Cache hit rate is excellent for the average account, but a subset of customers generates highly variable regional traffic and many cache misses. The average cost per GB still looks acceptable, yet the heavy cohort is much more expensive to serve. In that case, the CDN is helping product performance, but the pricing model may still need bandwidth guardrails or a separate high-usage policy.