Website · Documentation · Pricing

Cost calculator

Your traffic

Choose a workload. We’ll estimate traffic and requests for you.

Estimated monthly costs

USD per month, before tax. Load balancing and unpriced extras are excluded.

What’s included?

Estimates cover cacheable content. Origin and optional services are added only when you enter their rates. Plans differ in features and coverage; check their terms before buying.

Advanced settings
Split traffic between regions

Percentages must total 100%. The same split applies to bytes and requests. CloudFront charges by serving edge location; this is an approximation. Shared free allowances are allocated proportionally.

Origin and optional services

Paid tiers start with this workload; estimates do not include other account traffic. Enter your own effective rates after origin allowances. Reads use request misses; egress uses byte fill. Functions assume one invocation per viewer request. Zero leaves an extra out of the estimate; it does not mean your origin is free.

Compare a quote you received

This is your quote, not a published provider price. Use an effective rate for the selected traffic mix; tiers, included usage and commitments need to be reflected in your inputs. Sharing a scenario includes your quote details.

Presets are starting assumptions, not measured traffic. Video assumes one rendition and segment GETs; playlists, retries and extra audio tracks add requests. Fill is a byte ratio, not a request cache-hit rate. GB = 1 billion bytes; Google bills GiB = 1,073,741,824 bytes; CloudFront estimates use binary GB as a billing assumption.

Overview

CDNSun has operated since 2012, with main offices in Prague. It provides static-content caching, software delivery and live/on-demand streaming.

Select the delivery cities for each service and manage configuration through the dashboard or API. Static pull, hosted content and HTTP Live have different workflows; confirm the service type before integration.

Network

The network page names 30 cities across five continents. The map shows approximate city centers; test latency from the access networks your visitors use.

CDNSun lets customers select locations for each service. Check those selections against the audience and pricing table, and test actual delivery performance rather than assume the globally nearest city is always used.

Published delivery cities

Approximate city centers. Select locations for the actual service; city counts are not a capacity or performance measure. Unmatched names remain listed without pins.

AmsterdamBucharestBudapestFrankfurtKievLondonMadridMilanStockholmWarsawAtlantaChicagoDallasDenverLos AngelesMiamiNew YorkSeattleMexico CitySantiagoSao PauloTorontoBombayHong KongJohannesburgSingaporeSydneyTel AvivTokyo
Cities

Amsterdam, Bucharest, Budapest, Frankfurt, Kiev, London, Madrid, Milan, Stockholm, Warsaw, Atlanta, Chicago, Dallas, Denver, Los Angeles, Miami, New York, Seattle, Mexico City, Santiago, Sao Paulo, Toronto, Bombay, Hong Kong, Johannesburg, Singapore, Sydney, Tel Aviv, Tokyo

Listed without a marker: .

Features

FeatureSupported
Web application firewallNot listed
Bot protectionNot listed
DDoS protection✓ Supported
Rate limitingNot listed
HTTP/3 (QUIC)Not listed
TLS 1.3Not listed
Tiered caching◐ Partial
Origin shield◐ Partial
Instant cache purge✓ Supported
Serve stale while refreshingNot listed
Serve stale on origin errorsNot listed
Image optimizationNot listed
On-demand video✓ Supported
Live video✓ Supported
Digital rights managementNot listed
HLS / DASH packaging✓ Supported
WebSocketsNot listed
Signed URLs✓ Supported
Edge computeNot listed
Edge functionsNot listed
Key-value storageNot listed
Configuration API✓ Supported
Real-time logs◐ Partial
Log export◐ Partial
Terraform providerNot listed

✓ Supported · Partial: limited or separate-product support · ✗ Not supported · Not listed: unconfirmed. Some features need a separate product or plan.

Delivery and access control

  • Static pull and push services support cache expiry, query-string behavior, file/all purging and prefetching. Wildcard purge is not supported; request/path limits apply.
  • Custom certificates and managed Let’s Encrypt certificates support HTTPS. Current HTTP/3 and TLS-version coverage is unconfirmed.
  • Signed URLs can expire or restrict access by IP. HLS protection needs tokens that cover the intended segment paths.
  • The price card includes DDoS protection; a full WAF or managed bot product remains unconfirmed.

Media and observability

  • HTTP Live supports RTMP and HLS/DASH push/pull. RTMP push can create multiple bitrates, with HLS/DASH output.
  • Current reports, minute-level live reports and hourly reports have different freshness. Raw logs are collected hourly into configured storage.
  • Real-time log forwarding is arranged through support, rather than assumed to be enabled automatically.

Origin shielding

There is no packaged shield product. The documented alternative chains a small CDN service ahead of the delivery service. It adds billable traffic and requires purging the shield before the outer CDN.

Pricing

  • Business delivery is $0.03/GB for the listed European, US and Canadian cities, and $0.06/GB for the other listed cities. Business supports 20 websites with no monthly minimum; Custom has negotiated rates and a $200 minimum.
  • Requests, API, SSL, streaming and transcoding carry no separate charge on the published card. Incoming traffic is free.
  • Up to 5 GB storage is free; larger storage and any chained shield traffic add cost. The calculator excludes those unless you supply their rates.
  • A 15-day trial is temporary. Unused prepaid credit expires after a year unless topped up; depleted accounts can be suspended. Choose locations and confirm account terms.

Developer tools

  • Use the REST API for supported services, origins, locations, certificates and cache operations. The knowledge base includes a client and integrations for common CMS/framework stacks.
  • Static content can be pulled from an origin or uploaded to CDN storage. Streaming inputs use the selected media workflow.
  • Create a logs service and logs storage before downloading raw access logs by FTP, FTPS, SFTP or rsync. Default retention is 31 days within available capacity.
  • Confirm forwarding destination, latency and commercial terms with support if continuous logs are required. A current official Terraform provider is unconfirmed.

When it fits

  • Static websites, downloads and media projects whose audience matches the selected published cities.
  • Request-heavy content where a delivery-only rate is useful and storage requirements are modest.
  • Teams comfortable managing origin/cache behavior or RTMP/HLS/DASH inputs through the dashboard and API.

Before you choose

  • Check HTTP/3, TLS versions, WAF and edge-function support if they are requirements for your project.
  • Hourly raw-log files are not a continuous stream; arrange forwarding with support if needed.
  • Add storage above the free allowance and chained-shield traffic to the estimate.
Sources