App bundles, dashboard assets, customer downloads and API responses, served from the edge closest to each user.
From $5/TB down to $2.50/TB, so 100 TB of traffic is about $415 a month · 14-day testing period on real traffic · $25 monthly minimum waived · Engineer reply within 3 business hours
Three delivery cases from our knowledge base, with the full write-ups one click away.
2 GB installers served from nearby edge nodes worldwide, with resumable downloads and origin load staying flat during peak download windows.
A 15 GB patch requested at the same time in Tokyo, Los Angeles, Frankfurt and São Paulo, with cache hit above 97% in the first hour.
Short TTLs for manifests, long TTLs for segments, and steady segment delivery across every bitrate tier in the ABR ladder.
{
"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"
}
}
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.
BlazingCDN delivers SaaS app bundles, dashboard assets, customer downloads and cacheable API responses from one Anycast network. Pricing steps down from $5 to $2.50 per TB, so 100 TB of app traffic costs $415 a month. A REST API, purge, signed links and Prometheus metrics are included, and an engineer replies within 3 business hours.
BlazingCDN bills 100 TB of SaaS app traffic at $415 a month on progressive tiers (as of October 2026). The first 5 TB bill at $5 per TB, which equals the $25 monthly minimum. The next 20 TB bill at $4.50 per TB, and the last 75 TB at $4.00 per TB.
The same rate applies whether users load the dashboard from the US, Europe or Asia. BlazingCDN charges no request fees, so chatty single-page apps with thousands of small JS chunks do not create a second meter. No setup fee and no long-term contract apply. For example, a platform that grows from 100 TB to 200 TB a month moves to $765 in total, because traffic above 100 TB bills at $3.50 per TB. Enterprise terms start from 100 TB a month, and a quote never raises the published price.
BlazingCDN caches SaaS assets with classic pull caching: the first request in a region fetches the file from the origin, and later requests are served from the edge. The network holds a 96%+ average cache hit ratio, so the origin answers each file roughly once per TTL per region.
App bundles work well with hashed filenames. A file such as app.3f9c1.js never changes, so a long TTL is safe, and a new release simply ships new names. Shared files such as index.html or config JSON get short TTLs, or a purge through the REST API when a release goes out. Cacheable API responses, such as feature flags or public catalog data, follow the same rules. Responses are compressed with gzip, Brotli or zstd and served over HTTP/2 and TLS 1.3. For example, a release job can purge the old entry file and warm up the new bundle before users arrive.
BlazingCDN is a good fit for the static and cacheable part of a SaaS platform, not for the dynamic backend. The network does not offer edge compute, WebSockets or HTTP/3, so login flows, real-time collaboration and per-user API calls should stay on the origin or another provider.
The split is usually clean. App bundles, fonts, avatars, documentation, product video and customer export files are static and heavy, and they drive most of the terabytes. Personalized JSON and live sockets are light but cannot be cached. BlazingCDN carries the first group at one rate in every region, from $5 per TB down to $2.50 per TB (as of October 2026). For example, a SaaS company might move 80 TB of downloads and assets to BlazingCDN and keep 2 TB of dynamic API traffic where it is. Files up to 50 GB per file are supported, with unlimited requests.
Yes, BlazingCDN exposes purge and cache warm-up through a REST API that is included on every account. A CI job can call the API after a deploy, purge changed paths and warm up the new bundle before traffic arrives.
The same API manages zones, cache rules, certificates and metrics. For monitoring, BlazingCDN offers a Prometheus endpoint that feeds Grafana or Alertmanager, plus real-time statistics in the panel. An official MCP server lets AI agents read metrics and run cache purges. Raw logs are available for $50 per month (as of October 2026) for teams that ship logs into their own stack. For example, a release pipeline can purge /index.html and the old manifest in one call, then request the new files from the edge. The panel stays available for rare manual changes. Onboarding with an engineer takes about one hour, and a 14-day testing period runs on real production traffic.
BlazingCDN restricts downloads with signed links: an HMAC signature with an expiry time, optionally bound to one client IP or limited to a set number of IPs per URL. A customer export link can, for example, expire after 24 hours and work only from the address that requested it.
Request filters add a second layer. Zones can check the referrer, the user agent and cookies, and apply geo allow and block lists. Transport rules enforce HTTPS and refuse insecure requests. Each zone can use the customer’s own hostname and SSL certificate, and CORS is set per zone, so a dashboard on app.example.com can fetch assets from cdn.example.com cleanly. Files up to 50 GB are supported, which covers large data exports and backups. Signed links, request filters and purge are included in the per-TB price rather than sold as a separate security plan.