CDN for AdTech: Priced per Terabyte, Never per Request
Creative images, HTML5 rich media, JS tag libraries and the video files your VAST documents reference, served from the edge closest to the viewer. Requests, cache volume, HTTPS and custom domains are not billed at all.
$5.00/TB falling to $2.50/TB, one rate in the US, EU and Asia, so 100 TB is about $415 a month · $25 monthly minimum · Engineer reply within 3 business hours
Ad delivery is priced per request almost everywhere. Not here.
An ad server ships millions of small static objects. On a metered CDN the bandwidth is a rounding error and the request count is the invoice. We bill traffic only, so the same volume looks like this at $5.00/TB, the entry rate.
20 KB JS tag library
per million loads. Twenty gigabytes of traffic, and the million requests are not a line item.
100 KB HTML5 banner
per million impressions. One hundred gigabytes of traffic, served from the edge closest to the viewer.
2 MB video ad creative
per million impressions. Two terabytes of traffic, still billed at the same rate in every region.
At volume the rate falls to $2.50/TB and these figures halve. Cache volume is never billed, and the request count does not appear on the invoice at any tier.
Anycast CDN or Video CDN: which your assets need
Anycast CDN
Video CDN
Your ad server decides what to show. We make the file arrive.
We are a delivery layer, not a processing layer. Knowing exactly where our job ends is the fastest way to see whether we belong in your stack.
What we do
- Serve creative images, HTML5 bundles, JS tag libraries and VAST media files from the edge closest to the viewer
- Cache them, and never bill you for the cached volume or for the requests
- Give you purge by path or in full, plus a cache warm-up call before a flight opens
- Enforce signed URLs, referrer lists, geo and IP rules on those assets
- Set the CORS and timing headers publisher pages need to load them
- Hand over CDN statistics, status codes and raw delivery logs on request
What stays in your stack
- The auction and everything in the bid path
- Impression and click beacons, which have to reach your own servers to be counted
- VAST generation, wrapper chains and macro substitution
- Invalid-traffic filtering, viewability and verification
- Consent strings and what your CMP decides they mean
- Attribution and the numbers your measurement vendors report
Nothing we do can change what your ad server decided. It can change how quickly the file it pointed at reaches the viewer.
One creative master, every placement size
A campaign that runs across ten placement sizes usually means ten rendered files per creative, stored and versioned. Image Processing runs at the edge instead: keep one master creative on your origin, ask for the size a placement needs in the query string, and the edge generates the variant once and caches it like any other object. The processing itself is not billed.
Master creative, 1376 x 768
resizefit, width 800
resizefit, width 480
https://cdn.yourdomain.com/creatives/spring-launch.jpg?preset=resizefill&width=300&height=250
What 100 TB of ad delivery costs
$5.00/TB falling to $2.50/TB as volume grows. 100 TB a month is about $415, the same figure whether that traffic is served in the US, the EU or Asia. HTTPS, custom domains, SSL certificates, cache volume and every request are included in that number. The monthly minimum is $25. Above 1,500 TB a month the price is quoted around your traffic. Full tiers on the pricing page.
Delivery controls for ad ops
Cache rules built for creative churn
One signature per campaign, not per creative
Referrer, IP and geo rules
CORS headers you control
Your own hostname, SSL issued automatically
Statistics, status codes and raw logs
EU delivery for creatives and consent assets
When a campaign requires that creatives, tags and consent scripts are served from inside the EU, the delivery can be pinned to European cache servers, shared or dedicated to you. Where the bytes are served from is a configuration choice on the resource, not a plan tier and not a separate contract.
What a consent string means, and what your site is allowed to load once it has been read, stays with your CMP. We control the location of the file and who may fetch it.
- GDPR cache servers, delivery restricted to EU locations
- Private cache servers, hardware reserved for your traffic
- Geo and IP allow or block lists on any resource
- Signed URLs with an expiry validated at the edge
Send us a month of ad-call volume. We will price it.
Tell us the traffic, the average creative weight and the regions you serve. You get the rate, the monthly figure and an engineer who answers within 3 business hours.
How teams move creatives onto BlazingCDN
No part of your ad stack is rewritten. The creative origin stays where it is and the traffic changes hostname.
1. Talk to an engineer
Accounts are opened by our team, not by a signup form. Send the monthly ad-call volume, the average creative weight and the regions, and you get the rate and an account.
2. Move the assets to a CDN hostname
We do not proxy your DNS and we do not sit in front of your ad server. You point a CNAME at the zone, add your own domain, and your ad server starts writing that hostname into creative and script URLs. Everything else in the stack stays exactly where it is.
3. Warm the cache before the flight
Pre-position the creatives booked for the window through the warm-up API, then watch the hit ratio in the panel. Many platforms run us as a second CDN on a share of creative traffic first.
What we are building for AdTech teams
Tag libraries and SDK bundles
Personalization and MarTech scripts
Display and HTML5 rich media
VAST video creatives
Test CDN Speed Across Top Regions
Avg. Download Speed
Latency
Test link
Straight answers
Can you serve our impression and click pixels?
No, and you should not want us to. A beacon only counts if the request reaches your own server, so it is deliberately non-cacheable and it belongs on your infrastructure. What moves to us is the static payload around it: creative images, HTML5 bundles, tag libraries, SDK and CMP scripts, and the video files a VAST document references.
Do you generate or transform VAST tags?
No. We deliver the media files a VAST document references, and the document itself only if it is a static file you host with us. A document generated per request with macro substitution stays in your ad server.
Do we have to change our DNS?
No. We do not proxy traffic at the DNS level and we do not sit in front of your ad server. You get a zone hostname, point your own domain at it with a CNAME, and your ad server writes that hostname into asset URLs. Nothing else in the stack moves.
Do you filter invalid traffic or measure viewability?
No. IVT detection, viewability and verification belong to your measurement vendors. We serve bytes, and raw delivery logs can be switched on so your own numbers can be reconciled against the ad server.
Can we set our own CORS headers?
Yes, for the whole account or per domain. Allow-Origin, Allow-Methods, Allow-Headers, Expose-Headers, Allow-Credentials and Max-Age are all configurable, and Timing-Allow-Origin can be set so a publisher page is able to read real delivery timing for your assets.
Do we need a signed URL for every creative?
No. A URL Part Signature signs a path prefix, so a campaign folder is signed once and every filename under it reuses that signature. Links can also carry a start and end timestamp, an IP or prefix binding, a cap of up to five distinct IPs, and a cookie check.
Our ad server marks creatives as non-cacheable. What then?
Origin cache headers win by default, so a creative sent with no-cache is fetched every time. You can override that per resource with the Ignore Cache-Control setting, and set Active, Inactive and Browser TTL yourself, from the two-day default up to 365 days.
Are ad requests counted, capped or charged?
Requests are not billed, cached or not. The invoice is traffic at the tier rate, from $5.00/TB down to $2.50/TB, plus the $25 monthly minimum. Cache volume is not billed either.
Can we run BlazingCDN alongside our current CDN?
Yes. Most platforms start by moving a share of creative traffic to a separate hostname and shift more once the hit ratio and the logs look right. See BlazingCDN as your second CDN.
What latency should we expect outside the US and EU?
Average edge latency measured on our own test files in June 2026 is 27 ms in Europe, 24 ms in North America and 47 ms in Asia. Your own figures depend on where your users are and on your asset mix. The regional numbers are published on Performance Metrics.
How large can a single creative be?
Up to 50 GB per file, which covers any video creative or rich-media bundle. Large VAST media libraries usually belong on Video CDN, where files are replicated inside the network.
Do you support WebSockets?
No. BlazingCDN delivers HTTP and HTTPS traffic, including video and large files. Long-lived bidirectional connections are not proxied, so real-time signalling stays outside the CDN.
Questions ad tech teams ask about BlazingCDN
BlazingCDN delivers ad creatives, HTML5 rich media, JS tag libraries and VAST media files at $5 per TB falling to $2.50, with one rate in the US, Europe and Asia. Requests and cache volume are never billed, so millions of small ad calls cost only their bytes. Auctions, beacons and VAST generation stay in your stack.
What does BlazingCDN charge for a billion banner impressions?
On BlazingCDN, one billion impressions of a 100 KB HTML5 banner is 100 TB of traffic, which costs $415 a month (as of October 2026). Requests are not billed at any tier, so the billion ad calls are not a line item. Only delivered bytes count. The same 100 TB figure covers 50 million plays of a 2 MB video creative, or five billion loads of a 20 KB tag library.
The rate is the same in the US, Europe and Asia. HTTPS, custom domains, SSL certificates and cache volume are included in that number. The tiers fall from $5 per TB to $2.50 per TB as volume grows, so a 200 TB month costs $765. The monthly minimum is $25. For example, an exchange serving 20 TB of tags and banners in a month pays $92.50, whatever the request count behind those bytes.
How does BlazingCDN fit next to our ad server?
BlazingCDN sits behind one CNAME as the delivery layer, while the ad server keeps the auction and decides what to show. The creative origin stays where it is. You point a CNAME at the zone, add your own domain, and the ad server writes that hostname into creative and script URLs. BlazingCDN does not proxy your DNS or sit in front of the ad server.
BlazingCDN serves creative images, HTML5 bundles, tag libraries and VAST media files, with purge by path or in full and a warm-up call before a flight opens. Your stack keeps the bid path, impression and click beacons, VAST generation and macro substitution, invalid-traffic filtering, viewability, consent decisions and attribution. For example, a beacon must reach your own server to be counted, so pixels stay on your infrastructure. Raw delivery logs at $50 per month (as of October 2026) let your team reconcile bytes served against the ad server.
Can BlazingCDN serve impression pixels or generate VAST tags?
No: BlazingCDN serves neither counting pixels nor generated VAST, because both must reach your own servers on every request. A beacon counts only if the request reaches your server, so it is deliberately non-cacheable. A VAST document generated per request with macro substitution also stays in your ad server. BlazingCDN delivers the media files a VAST document references, and the document itself only when it is a static file.
Other limits apply. WebSockets are not supported, so real-time signalling stays outside the CDN. Edge compute is not offered, and invalid-traffic filtering and viewability belong to your measurement vendors. Files up to 50 GB are supported, which covers any video creative. For example, a 2 MB creative referenced by a VAST wrapper is served from the edge, while the wrapper chain resolves in your stack. Delivery costs $5 per TB falling to $2.50 (as of October 2026).
How do ad tech teams move creatives onto BlazingCDN?
Moving creatives onto BlazingCDN takes three steps, and no part of the ad stack is rewritten. First, talk to an engineer: accounts are opened by the team, not by a signup form, so send monthly ad-call volume, average creative weight and regions. Second, point a CNAME at the zone, add your own domain, and have the ad server write that hostname into asset URLs. Third, warm the creatives booked for the flight through the warm-up API, then watch the hit ratio in the panel.
Many platforms start with BlazingCDN as a second CDN on a share of creative traffic, for example 10%, then shift more once the logs look right. Onboarding takes about one hour. The 14-day testing period runs on real production traffic. A KYC check is completed before production traffic, and an engineer replies within 3 business hours.
Does every ad creative need its own signed URL on BlazingCDN?
No: BlazingCDN signs a path prefix with a URL Part Signature, so one signature covers a whole campaign folder. Every filename under that folder reuses the same signature. Links can carry start and end timestamps, an IP or prefix binding, a cap of up to 5 distinct IPs and a cookie check. Two secrets allow rotation without breaking live campaigns.
Cache headers matter as much as signatures. Origin cache headers win by default, so a creative sent with no-cache is fetched on every request. The Ignore Cache-Control setting overrides that per resource, and Active, Inactive and Browser TTL run from the two-day default up to 365 days. CORS is configurable, including Timing-Allow-Origin, so publisher pages can read real delivery timing. For example, a flight running 30 days can use one folder signature that expires on the last day of the flight.