SOFTWARE · RELEASE DAY DELIVERY
CDN for Software Companies
Installers, patches and game builds, served from the edge on release day instead of from your build server.
From $5/TB down to $2.50/TB, so 100 TB of downloads is about $415 a month · 14-day testing period on real traffic · $25 monthly minimum waived · Engineer reply within 3 business hours
50 GB
Per file, with no size surcharge
Under 3%
Of demand reaches your origin
96%+
Average cache hit ratio
What 100 TB of downloads costs
Progressive tiers work like tax brackets: each rate applies only to the traffic inside its range. Requests, HTTPS, custom domains and origin shield are included, and the rate is the same in Europe, Asia and America.
TIER 01
First 5 TB
$5.00 per TB
- $25 for the whole tier
- This is also the monthly minimum
TIER 02
5 to 25 TB
$4.50 per TB
- $90 for the next 20 TB
- 25 TB in total: about $115
TIER 03
25 to 100 TB
$4.00 per TB
- $300 for the next 75 TB
- 100 TB in total: about $415
100 TB a month works out at $415
Each tier is billed only on the traffic inside it, so the tiers add up rather than replace each other. 25 TB is about $115, 500 TB is about $1,815, and above 500 TB a month we quote it for you.
Four ways software gets shipped
Same network, same rate. What changes is the shape of the release and where the load lands.
SaaS platforms with 24/7 patch delivery
Small, frequent updates that have to reach every tenant at once. They sit at the edge, so a rolling patch does not turn into an origin spike.
Game launchers and versioning
Multi-GB builds and delta patches with a hard release hour. Range requests keep downloads resumable, and concurrent misses collapse into one origin fetch.
DevOps CI/CD and nightly builds
Artifacts published straight from the pipeline through the API, purged network-wide in seconds, with cache warming before a release goes public.
Installer vendors and app catalogues
Full installers, disk images and asset packs up to 50 GB per file, on the same pull cache and the same progressive tiers, with no size surcharge.
Which product carries your builds
Anycast CDN
Classic pull cache for installers, patches and static assets. Point a zone at your origin, we cache at the edge and answer with a 96%+ hit rate. Files up to 50 GB, no size surcharge and no separate plan.
Cloud Storage for CDN
Use our replicated object storage as the origin for any zone, so the build server does not have to stay online just to serve downloads.
Files on Demand
Large-file delivery for catalogues that change often: import once, serve everywhere, and let the CDN hold the copies instead of your origin.
RELEASE DAY
What happens the hour a release goes live
Four things that happen to every software vendor at the same moment. Here is what the edge does in each one.
Ten thousand people pull a cold file
Concurrent misses collapse into one origin fetch. Your build server answers once, the edge fans the file out to everyone else.
The download is 4 GB and the line drops
Full range-request support, so clients resume where they stopped and fetch chunks in parallel instead of starting the installer over.
You want the cache warm before launch
Push a list of URLs through the API and the files are in position before the announcement goes out, not after the first thousand users arrive.
A patch ships the wrong binary
Purge across the whole network in seconds, then re-warm from the same API call, without waiting for a TTL to expire.
Test CDN Speed Across Top Regions
Speed data measured June 2026
Avg. Download Speed
Latency
Test link
*Download speed and latency may vary depending on the quality of your network connection.
Keeping paid builds paid
Licence logic stays in your application. What the CDN can do is make the download link useless to anyone it was not issued for.
Signed links
- HMAC signature with an expiry
- URL bound to one IP
- Limit on IPs per URL
Request filters
- Referrer and user-agent checks
- Cookie checks, standard and extended
- Geo allow and block lists
Transport and indexing
- HTTPS enforced, insecure requests refused
- Secrets managed per resource
- Googlebot bypass for public pages
{
"pull_zone": {
"name": "string",
"source": "origin",
"origin": "string",
"origin_ssl": true,
"origin_url": "string",
"bucket_id": "8f7ac8aa-ed2b-4e16-81e0-0766bdb092b8",
"folder_name": "string",
"cache_gzipped": true,
"domain": "string"
}
}
24/7 DevOps Escalation
BlazingCDN plugs into the stack you already run: a REST API for zones, cache, certificates and metrics, an official MCP server for AI agents, and a Prometheus endpoint for Grafana or Alertmanager.
Purge and warm up cache from your CI, pull traffic data into your own dashboards, and keep the panel for the rare manual change.
Where to go next
Neighbouring scenarios that run on the same network and the same tiers.
Custom Configs