CDN Products

Two delivery products on one network and one account: Anycast CDN and Video CDN. HLS Streaming runs on Anycast, Files on Demand runs on either one, and Cloud Storage is the object storage you can point any of them at. They differ in where your files live and how they are served, not in the price per terabyte.

Not sure which one fits? An engineer replies within 3 business hours · See pricing

One account, one rate card
96%+ average cache hit ratio
Up to 50 GB per file

Anycast CDN

Classic pull caching for static assets: images, scripts, styles, downloads. Point a zone at your origin and we cache at the edge, answering with a 96%+ average hit rate, so your origin serves each file roughly once per TTL per region instead of once per user.

Release-day traffic chart: the edge absorbs the download spike while origin load stays flat

Video CDN

Your video library is replicated inside the CDN and served from the closest, least-loaded node. After import your origin can leave the delivery path entirely, which is what separates Video CDN from a plain pull cache.

Illustration: static files being uploaded to BlazingCDN cloud storage servers

Cloud Storage for CDN

Not a delivery product: replicated object storage you point a delivery zone at. Use it when you would rather not keep your own storage online just to feed the CDN.

Illustration of a premium media delivery platform

Files on Demand

Import your catalogue once and the CDN holds the copies. Anycast pulls and caches while your origin stays the source of truth; Files on Demand imports and holds, so the origin can go quiet.

Video library replicated across BlazingCDN edge locations

HLS Streaming CDN

Delivery for streams you have already encoded: HLS, LL-HLS and DASH from your own media server, with manifests and segments cached on separate rules. Typical latency our layer adds is 2-4 seconds, where standard HLS sits at 20 to 40.

Illustration of a premium media delivery platform

Image optimization, included

Not a separate product and not a separate line on the invoice. Image resizing and compression run on the delivery layer you are already paying for: one source image, resized on the fly to whatever the layout asks for, so you ship fewer bytes without keeping a second copy of anything.