Your own delivery nodes: isolated hardware, your regions, your rules. Built and operated by our engineers, or handed to your team with root access.
Reply within 3 business hours. No sales sequence.
Private is an arrangement of hardware, not a marketing word. Four things change, and all four are checkable.
Your objects sit on hardware that holds nothing else. No shared cache, and no eviction caused by somebody else’s spike at three in the morning.
The nodes carry your traffic and nothing else. Capacity you paid for is capacity you get, including on the day of a launch.
Delivery runs under your domain with your TLS certificate. Nothing in the request path advertises the provider behind it.
Headers, auth, tokenisation and routing behave the way your application needs them to, not the way a shared platform permits.
Live events and VOD libraries where a buffering incident becomes a public one. Private nodes hold the peak and keep the p95 predictable on the night that matters.
Software updates, model artefacts and large payloads delivered under your own domain, with caching behaviour you set rather than request.
Internal and customer-facing applications where the caching layer has to sit inside a named jurisdiction and stay auditable.
The point of a private network is that you choose the map instead of inheriting one.
Nodes go where your audience actually is, not where the average customer of a shared platform would want them.
Each node is provisioned with transit that suits its local market, rather than one global template applied everywhere.
Capacity is sized for the geography you actually serve, so the bill follows your map rather than a global footprint.
The honest counter-case: if your traffic is spread thin across many regions, the shared tiers usually stay cheaper. We will tell you that on the call rather than after the build.
A private network does not mean a private toolchain. Everything you already use keeps working against your own nodes.
Zones, cache rules and certificates are managed where you already manage them.
Automation you have already written keeps working against your private zones.
Invalidation behaves identically, per file or across a whole zone.
Raw logs are available on the same terms as on the public tiers.
The two get confused often. The difference is who the audience is.
Dedicated hardware carrying your own delivery. The audience is your users, the traffic is yours, and the goal is control and performance.
Our platform resold under your brand. The audience is your customers, the traffic is theirs, and the goal is a product you can sell. See White Label CDN.
A private network is dedicated hardware, so it is priced as a fixed monthly figure per node plus delivery on your agreed tier. That figure follows the node count, the locations and the term, and it is quoted in writing before anything is ordered. It is not a metered rate.
For reference, 100 TB a month on the public tiers costs $415. Where a private build overtakes that depends on your regions and how much of your volume is cacheable. The full ladder sits on Custom Enterprise CDN Infrastructure, next to Individual CDN Servers and Hybrid CDN Solutions.
Tell us the regions and the workload. You get a reply within 3 business hours, with either an outline of the build or an honest answer that the shared tiers fit you better.
He reads every request sent from this page and replies within 3 business hours, including the reply that says the shared tiers fit you better. No sales sequence in between.