Website · Documentation · Pricing
Overview
Transparent CDN is now marketed as Transparent Edge. The platform uses Varnish Enterprise and VCL to move request-handling logic closer to users, alongside delivery, security and media options.
Its history distinguishes several milestones: a CDN pilot in 2011, commercialization in 2014, the Transparent CDN name in 2016 and commercial integration in 2021. The current website operator is Transparent Edge Services, S.L., with a registered address in Madrid.
Network
The published inventory names locations across several continents. The map uses country-qualified city centers; duplicate sites in one city share a pin. Texas and the inconsistent Nigeria “Laos” label remain unpinned, as do unmatched names.
The map shows approximate city centers. Check the locations and features included in your contract and test delivery from your audience’s networks.
Approximate city centers, not facilities. Multiple PoPs in one city share a pin. Regional, inconsistent and unmatched names remain unpinned.
Cities
Berlin, Germany, Frankfurt, Germany, Vienna, Austria, Brussels, Belgium, Sofia, Bulgaria, Zagreb, Croatia, Bratislava, Slovakia, Madrid, Spain, Barcelona, Spain, Helsinki, Finland, Paris, France, Marseille, France, Athens, Greece, Amsterdam, Netherlands, London, United Kingdom, Manchester, United Kingdom, Dublin, Ireland, Milan, Italy, Palermo, Italy, Oslo, Norway, Warsaw, Poland, Prague, Czechia, Bucarest, Romania, Stockholm, Sweden, Geneva, Switzerland, Kiev, Ukraine, Budapest, Hungary, Calgary, Canada, Toronto, Canada, Vancouver, Canada, Boston, United States of America, New York, United States of America, Chicago, United States of America, Miami, United States of America, Los Angeles, United States of America, Dallas, United States of America, Phoenix, United States of America, Atlanta, United States of America, Denver, United States of America, Seattle, United States of America, San Jose, United States of America, Houston, United States of America, Mc Allen, United States of America, Mexico City, Mexico, Querétaro, Mexico, Buenos Aires, Argentina, Sao Paulo, Brazil, Santiago de Chile, Chile, Bogota, Colombia, Lima, Peru, Johannesburg, South Africa, Dubai, United Arab Emirates, Hong Kong, Hong Kong S.A.R., Tel Aviv, Israel, Tokyo, Japan, Kuala Lumpur, Malaysia, Singapore, Singapore, Seoul, South Korea, Istanbul, Turkey, Melbourne, Australia, Perth, Australia, Sidney, Australia, Auckland, New Zealand
Listed without a marker: Slough, United Kingdom, Belgrade, Republic of Serbia, Zurich, Switzerland, Montreal, Canada, Ashburn, United States of America, Texas, United States of America, Portland, United States of America, Washington DC, United States of America, Laos, Nigeria, Fujairah, United Arab Emirates.
Features
| Feature | Supported |
|---|---|
| Web application firewall | ✓ Supported |
| Bot protection | ✓ Supported |
| DDoS protection | ✓ Supported |
| Rate limiting | Not listed |
| HTTP/3 (QUIC) | Not listed |
| TLS 1.3 | Not listed |
| Tiered caching | ✓ Supported |
| Origin shield | ◐ Partial |
| Instant cache purge | Not listed |
| 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 | ◐ Partial |
| HLS / DASH packaging | ◐ Partial |
| WebSockets | Not listed |
| Signed URLs | Not listed |
| Edge compute | ◐ Partial |
| Edge functions | ◐ Partial |
| 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.
Cache and edge logic
VCL supports request routing, headers, multiple backends and A/B or canary behavior. Use VCL for cache logic; ask separately about a JavaScript runtime if your project needs one. Optional two-layer caching adds a mid-tier to reduce origin requests. ESI is available but must be enabled per site. Flexible purge is offered; check propagation time before depending on refreshed content.
Logs and security
Hourly batch exports support FTP/SFTP and S3-compatible storage. An enabled real-time streaming service provides delivery logs through authenticated Kafka consumers. WAF, bot management and DDoS protection depend on the chosen security scope.
Media options
Video workflows include live/on-demand delivery, recording, transcoding and on-the-fly HLS/DASH rewrapping. Commercial DRM integration is offered; confirm the license system, workflow and charges. Image optimization is a separate portfolio option.
Pricing
General CDN delivery is advertised at one quoted price per GB, without geographic price differentiation or a per-request delivery charge. Obtain the actual rate and minimum commitment.
Cyberpacks are different bundles: Small/Medium/Large list 10/50/100 TB of transfer and 400 million/2 billion/4 billion requests, with separate WAF, bot and Layer 7 site allowances. Public numeric bundle prices and overage rates are unconfirmed.
Use the calculator with a USD quote. Include allowances, minimums and optional products in the estimate, and check the request-overage charges for security bundles. Confirm image/media processing, storage and support costs separately.
Developer tools
Configure delivery
Use the linked documentation and its API reference for actual service controls. VCL can express routing and request logic; test cache keys, headers, multi-origin behavior and deployment rollback. WordPress and cloud-origin integration guides are available.
Export logs
Batch shipping must be activated and configured. Real-time Kafka consumers require their own certificates, approved source IPs and consumer-group configuration; Filebeat, Logstash and Python examples are documented. Set log retention and monitoring so you can retrieve the records you need after an incident.
Support
Cyberpacks include Standard support with 8/5 incident availability. Enterprise tiers advertise 24/7 incident coverage, with phone support at 8/5. Confirm the plan’s escalation terms. Ask about Terraform automation and HTTP/3 if they are requirements for the deployment.
When it fits
- Web teams needing VCL control over routing and cache behavior.
- Buyers comparing a global transfer rate with negotiated security scope.
- Sites requiring batch or real-time request-log integrations.
- Media workflows able to quote processing and DRM integration separately.
Before you choose
- VCL controls cache logic; check separately if you need a JavaScript runtime.
- Include Cyberpack allowances and security overages when budgeting.
- Ask about required HTTP/3, purge timing and Terraform support.
- Choose support coverage that matches your incident hours and preferred contact channel.
Sources
- www.transparentedge.eu/en/
- www.transparentedge.eu/wp-content/uploads/2025/09/Dosier-de-prensa-2025.pdf
- www.transparentedge.eu/en/terms-of-use/
- www.transparentedge.eu/en/content-delivery-cdn/next-generation-cdn/
- docs.transparentedge.eu/
- docs.transparentedge.eu/guides/streaming-logs
- docs.transparentedge.eu/getting-started/dashboard/log-shipping
- docs.transparentedge.eu/getting-started/faq/architecture/cache-layers
- docs.transparentedge.eu/guides/edge-computing/esi-tags
- docs.transparentedge.eu/guides/web-application-gateway
- www.transparentedge.eu/en/video-streaming/
- www.transparentedge.eu/en/ciberpacks/
- www.naturalearthdata.com/
- aws.amazon.com/s3/pricing/
- cloud.google.com/storage/pricing
