How it works
Your application keeps running in AWS, Azure or Google Cloud. Efficient Cloud Egress instances in our data centres sit between it and your users: they fetch from your origin over the direct connection to the provider, cache what can be cached, and deliver to the internet from our network. You pay the provider’s much lower private-transfer rate for the origin traffic, and we charge for delivery in credits.
Built for dynamic and long-tail content
CDNs are excellent at static files that many users request. They help much less with API responses, personalised pages or large catalogues where each object is requested rarely, which is exactly the traffic that drives most cloud transfer bills. Efficient Cloud Egress is designed for it:
- Persistent connections to your origin and caching where the content allows it.
- Request collapsing: cacheable objects are locked so only one request per object reaches your backend.
- Serving stale content while it updates in the background, so users never wait for a slow origin.
- Dynamic pages passed straight through when they cannot be cached.
Two layers with Cloudflare
Many customers with dynamic applications use both: Cloudflare in front for security and for static assets such as JavaScript, CSS and images, and Efficient Cloud Egress behind it for the dynamic traffic that would otherwise be billed by the cloud provider. As a Cloudflare partner we design and run both layers together.
Included
- Edge caching with unlimited purge.
- HTTP/2 and your own TLS certificates.
- Static and dynamic content.
- Active/active instances in more than one region for resilience.
- Easy failback to serving directly from the cloud.
- Logs available to download.
- Management from the web console, Ansible, Terraform or the API.
- 24x7 support.
Pricing
Efficient Cloud Egress is priced in credits, with no commitment to a provider plan. All prices exclude VAT.
| Usage | Credits |
|---|---|
| Data transfer | 1 credit per GB |
| Efficient Cloud Egress instance | 0.5 credits per hour (about 365 per month) |
| Credits bought | Price per credit (USD) |
|---|---|
| 512 | $0.050 |
| 1,024 or more | $0.045 |
| 10,240 or more | $0.040 |
| 51,200 or more | $0.037 |
| 102,400 or more | $0.035 |
| 512,000 or more | $0.033 |
| 1,048,576 or more | $0.031 |
For example, 5 TB a month with one instance uses 5,120 + 365 = 5,485 credits; at $0.045 per credit that is about $247 a month. How much you save depends on your provider, region and volume, so send us a recent bill and we calculate it on your real traffic.