Why CDN Vendors Hide Their Prices (And What to Do About It)
Enterprise pricing isn't opaque by accident. Here's the logic behind it — and how to use it to your advantage.
You’ve spent hours comparing solutions. One site finally looks right. You want to know what it costs. And instead of a number, you get a button: “Contact Sales.”
If that’s felt like a wall, you’re not alone. But having been on both sides of that conversation — as a buyer evaluating CDN options and as a practitioner who’s helped clients negotiate enterprise contracts — I can tell you the button isn’t evasion. It reflects something real about how these products are built and sold. Understanding the logic makes the process a lot less frustrating.
The product genuinely doesn’t have a fixed price
Think about the difference between buying a car off a lot and commissioning a building. A car has a price. A building has a scope, a site, a specification, and then a quote.
Enterprise CDN is much closer to the building. The cost of a terabyte of CDN traffic can range from $2 to $2,500 depending on the region, the volume commitment, the features enabled, and the contract term. That’s not a figure of speech — it’s the actual spread in the market. Publishing a number would either mislead or exclude most of the people reading it.
The variables that actually determine what you’ll pay:
Data transfer volume is the primary driver. Traffic is priced in tiers, and the difference between 10TB/month and 100TB/month isn’t just a 10× cost increase — the per-GB rate changes substantially at each threshold.
Geography changes the economics completely. CDN traffic in North America is cheaper to deliver than traffic to Southeast Asia, sub-Saharan Africa, or South America, where peering costs are higher and infrastructure density is lower. If you’re serving a global audience, the geographic mix of your traffic matters as much as the total volume.
Features are additive. A base CDN contract gets you caching and delivery. DDoS protection, WAF, bot management, image optimisation, and EdgeWorkers are layered on top. Each one changes the number. A platform that needs all of them is buying something fundamentally different from one that needs none of them.
Commitment term has a major effect on rate. A month-to-month arrangement is priced differently from a one-year contract, which is priced differently from three years. The vendor is pricing risk as much as usage.
An online calculator could theoretically handle some of this, but in practice the configurations are complex enough that a poorly-designed one would mislead more than it would help.
The sales call is a technical qualification process
When a vendor asks you to talk to sales before showing you a price, they’re not trying to trap you in a room with someone whose job is to wear you down. They’re trying to understand whether their platform is actually the right fit for your problem — because if it isn’t, the contract becomes painful for both sides.
I’ve sat in enough of these conversations to say: the ones that go well are the ones where the buyer comes in with clarity about their actual requirements. Traffic volume, peak load patterns, geographic distribution, technical stack, compliance requirements, timeline. The sales engineer on the other side is doing a technical scoping exercise. The more precisely you can describe your situation, the faster you get to a real number.
The ones that go badly are usually the result of misaligned expectations about what the product is. Someone buys an enterprise CDN expecting it to work like a DIY cloud service, or underestimates the implementation complexity, or overestimates their internal capacity to operate it. A decent pre-sales conversation surfaces those issues before you’re 90 days into a contract.
The price is a starting point
In enterprise B2B, the quote you receive first is rarely the final number. This is normal and expected — it’s not a sign that you’re being taken advantage of.
Vendors have pricing levers that don’t appear on any published list. Volume commitments unlock lower per-GB rates. Longer contract terms get meaningfully better pricing than shorter ones. Competitive situations — where you have a legitimate alternative offer — give you negotiating room. Even the timing of the conversation matters: end-of-quarter and end-of-year are the most accommodating times to push on price.
The assumption going into any enterprise CDN negotiation should be that the first number is a ceiling, not a floor.
How to approach it
Go into the first call prepared to describe your environment with specifics: current traffic volume, monthly request count, peak concurrency, geographic distribution of your users, and the specific capabilities you need. If you have an existing contract with another vendor, the expiry date and current rates are useful to know — even if you don’t volunteer them immediately.
Run the same process with two or three vendors in parallel. Not to play them against each other in bad faith, but because the exercise of scoping with multiple vendors gives you a much clearer picture of where the market actually sits. You’ll also quickly discover that different vendors have meaningfully different technical architectures, and the capability gaps matter as much as the price.
And ask the right questions: What’s the penalty structure for going over committed volume? What are the SLA terms and the credit mechanism when they’re breached? What does the onboarding and implementation support look like, and is it included? The price line in the contract is one data point; the total cost of operating the relationship is a different number.
The “Contact Sales” button is the beginning of a technical and commercial dialogue, not an obstacle. Approach it that way and it usually goes better than you’d expect.