Website · Documentation · Pricing
Overview
KeyCDN provides pull-zone caching and push-zone storage for websites, images and video delivery. Its dashboard and REST API handle zone setup, cache purging and reporting.
The delivery tariff has regional volume tiers and includes HTTP/HTTPS requests. Image processing, log forwarding and extra zones have separate charges.
Network
- Published PoP cities cover six continents; the map uses the active city table, rather than planned locations.
- KeyCDN describes a non-federated network with 60+ data centers across 40+ countries. Data centers and cities are different measures.
- Origin Shield can reduce repeated fetches from an origin. Test latency from your audience locations before choosing a delivery network.
Approximate city centers, not exact facilities. City counts do not measure network capacity. Published locations can change; some listed places have no marker.
Cities
Atlanta, Chicago, Dallas, Denver, Los Angeles, Miami, Montreal, New York, San Francisco, Seattle, Amsterdam, Athens, Bucharest, Dublin, Frankfurt, Helsinki, Kyiv, Lisbon, London, Madrid, Milan, Oslo, Paris, Stockholm, Vienna, Warsaw, Zurich, Almaty, Bangalore, Dubai, Hong Kong, Istanbul, Moscow, Seoul, Singapore, Tel Aviv, Tokyo, Auckland, Brisbane, Melbourne, Perth, Sydney, Johannesburg, Bogota, Buenos Aires, Lima, Mexico City, Santiago, Sao Paulo, Copenhagen
Features
| Feature | Supported |
|---|---|
| Web application firewall | Not listed |
| Bot protection | ◐ Partial |
| DDoS protection | ✓ Supported |
| Rate limiting | Not listed |
| HTTP/3 (QUIC) | Not listed |
| TLS 1.3 | ✓ Supported |
| Tiered caching | ✓ Supported |
| Origin shield | ✓ Supported |
| Instant cache purge | ✓ Supported |
| Serve stale while refreshing | Not listed |
| Serve stale on origin errors | Not listed |
| Image optimization | ✓ Supported |
| On-demand video | ✓ Supported |
| Live video | ✓ Supported |
| Digital rights management | Not listed |
| HLS / DASH packaging | Not listed |
| WebSockets | Not listed |
| Signed URLs | ✓ Supported |
| Edge compute | Not listed |
| Edge functions | Not listed |
| Key-value storage | Not listed |
| Configuration API | ✓ Supported |
| Real-time logs | ✓ Supported |
| Log export | ✓ Supported |
| Terraform provider | Not listed |
✓ Supported · Partial: limited or separate-product support · ✗ Not supported · Not listed: unconfirmed. Some features need a separate product or plan.
Caching and access
Origin Shield adds an optional cache layer before the origin. Zone settings control cache keys, cookies and headers. Global purges take a few seconds; Push Zones support URL purges. Secure Tokens restrict access to content, while image-processing requests have a separate signing mode.
Images and logs
Image Processing resizes and transforms images through query parameters and has its own operation charge. Raw access logs can be forwarded through syslog for a daily fee. Traffic reports are near real time rather than a zero-delay request feed.
Video delivery
Deliver HLS live streams from an external media origin. Enable Optimize for HLS for live playback; leave it disabled for on-demand media. Encoding and packaging are separate responsibilities.
Security and protocols
TLS 1.3 and DDoS protection are included. The bad-bot setting is a simpler control than a managed bot-security suite. Confirm any required HTTP/3, WebSocket or stale-cache behavior before relying on it.
Pricing
- Delivery starts at $0.04/GB in North America/Europe, $0.08 in Asia/Oceania and $0.10 in Africa/Latin America, with volume tiers.
- HTTP and HTTPS requests are included. The account has a $4 monthly minimum and a $49 minimum credit payment.
- Image processing costs $0.40 per 1,000 operations; log forwarding costs $1/day. Extra zones and push storage are separate.
- The free trial lasts 14 days. Check the current tariff for your exact usage and optional services.
Developer tools
- The REST API manages zones, aliases, referrers, reports and purge requests.
- Purge requests and general API calls have distinct API rate limits; these are separate from viewer delivery.
- Use API clients or existing site integrations for automation.
When it fits
- Websites delivering static files and images with regional usage-based pricing.
- Teams wanting API-controlled zones, a shield cache and token access.
- HLS delivery with an existing media origin and separate encoding workflow.
Before you choose
- Check any required video encoding, edge runtime or advanced security separately.
- Low traffic still needs prepaid credit and the monthly account minimum.
- Add image operations, logs, storage and extra zones where your setup uses them.
Sources
- www.keycdn.com/
- www.keycdn.com/network
- www.keycdn.com/pricing
- www.keycdn.com/api
- www.keycdn.com/features
- www.keycdn.com/about
- www.keycdn.com/support/pull-zone-settings
- www.keycdn.com/support/purge-cdn-cache
- www.keycdn.com/support/cdn-log-forwarding
- www.keycdn.com/support/publishing-an-http-live-stream
- www.keycdn.com/support/secure-token
- www.keycdn.com/support/image-processing
- www.keycdn.com/blog/new-feature-origin-shield
- www.keycdn.com/blog/quic
- www.naturalearthdata.com/
- aws.amazon.com/s3/pricing/
- cloud.google.com/storage/pricing
