Two delivery engines under one account: Anycast CDN for static files, large downloads and HLS streaming, Video CDN for VoD. Everything below is taken from the product documentation.
An official MCP server ships with the platform. Point Claude, Cursor or any MCP client at it and your agent operates the CDN from plain instructions, with no wrapper code to maintain.
npx -y @blazingcdn/mcp
Your origin stores one file. The CDN generates, caches and delivers every variant from a query string on your own domain.
Source file, 1376 x 768
resizefit, width 800
resizefit, width 480
https://cdn.example.com/images/photo.jpg?preset=resizefill&width=1200&height=1000
BlazingCDN includes the full feature set on every account: Anycast routing with failover, purge and cache warm-up, signed URLs, origin shield, image processing, Cloud Storage with three geographic copies, real-time statistics, Prometheus metrics and a REST API. Raw logs cost $50 per month. HTTP/3, WebSockets, edge compute and transcoding are not offered.
BlazingCDN Cloud Storage keeps at least three geographic copies of every file, and popular files get more copies. Background checksum validation runs continuously, so silent corruption is found and repaired from a healthy copy. When a drive fails, the platform heals itself by rebuilding the lost copies on other hardware. Cold copies of files nobody requests are retired automatically, which keeps extra copies where the demand is.
Import runs over three parallel streams, and a file is live within five minutes of import. For example, a 50 GB installer pulled from an S3 bucket is copied, checked and ready to serve without a separate origin server. Storage costs $0.015 per GB per month (as of October 2026), so 200 GB of originals costs $3 a month. Delivery out of the bucket is billed on the normal per-TB tiers. Cloud Storage works as the origin for both the Anycast CDN and the Video CDN.
Yes: BlazingCDN exposes purge and cache warm-up through a REST API and an official MCP server with 52 tools. Purge works by path, single or bulk, or as a total purge in one action. Warm-up pre-loads files into cache before a release, so the first users do not hit your origin. An agent in Claude or Cursor can run the same actions from plain instructions. Read tools are always on, writes are off by default, and destructive operations such as deleting a pull zone are not implemented.
Cache rules are granular. The default TTL is two days, and TTL can go up to 365 days. Errors cache for 60 seconds by default, and each HTTP status code can get its own TTL. Slice caching handles multi-gigabyte files. For example, a game studio can purge one 15 GB patch path, then warm the replacement build before posting the update notice. API keys carry scoped permissions, so a release script never needs full account rights.
BlazingCDN image processing is included at no extra charge and runs at the edge on imgproxy. Your origin stores one master file. A query string on your own domain asks for the size, and the edge generates, caches and delivers that variant. Four modes are available: resizefit keeps the whole image, resizefill fills an exact box and crops, resize picks fit or fill per request, and crop cuts around an anchor you choose. Nine gravity anchors control the crop, and setting one dimension keeps the aspect ratio.
For example, a 1376 x 768 source can be served at width 800 and width 480 without storing either file. Variants are cached like any other object, so a repeat request costs only the delivered bytes on the normal per-TB tiers. No separate processing meter exists. BlazingCDN resizes and crops; AI editing such as background removal or generative fill is not offered.
At 100 TB a month BlazingCDN costs $415 (as of October 2026), and almost every feature is inside that number. Purge, origin shield, signed URLs, image processing, Let’s Encrypt certificates, real-time statistics, Prometheus metrics and the REST API carry no separate fee. Requests are not billed, and pull cache volume is never billed.
Only three items sit outside the traffic rate. Raw logs in JSON for Graylog or ELK cost $50 per month. Cloud Storage costs $0.015 per GB per month. Video CDN permanent cache includes the first 500 GB, then costs $0.02 per GB per month. For example, a team moving 100 TB with raw logs switched on pays $415 plus $50. The traffic rate is the same in the US, Europe and Asia. Billing can be per TB or on a 95th percentile plan. There is no setup fee and no long-term contract, and cards, PayPal and bank transfer are accepted.
No: BlazingCDN does not offer HTTP/3, WebSockets, edge compute or video transcoding as of October 2026. Delivery runs over HTTP and HTTPS with HTTP/2, IPv6 and TLS 1.3. RTMP and RTSP ingest are not supported either. The Video CDN repackages video into HLS .ts or .m4s, MPEG-DASH, Smooth Streaming and HDS manifests on the fly, but repackaging never re-encodes. Files must already be encoded at the bitrates you want to serve.
Other limits are documented too. Chunk durations are fixed at 2, 4, 5, 10 or 30 seconds. Each CDN resource has one origin. Proxy mode has no HLS, DASH or clipping. Stacking another proxy CDN in front is not supported. The Video CDN is not meant for files under 10 MB, while the Anycast CDN serves files up to 50 GB. For example, a live channel needs its own media server producing HLS, which BlazingCDN then pulls as the origin.