Reduce cloud egress spend and protect your origins with a private, high‑capacity caching layer that sits between your cloud infrastructure and the edge. Cloud Wrapper maximizes origin offload, stabilizes performance during spikes, and integrates with Akamai delivery services and third‑party CDNs.
Customers commonly achieve 90%+ offload; in some cases offload exceeds 99%. One customer reported about a 90% reduction in AWS egress costs after adopting Cloud Wrapper. Read the customer story
Simply increasing edge cache TTLs can help, but it has limits: - Cache churn and long tail: Large catalogs and long‑tail objects are frequently evicted under pressure; long TTLs don’t guarantee retention. - Cache‑miss storms: When popular objects expire simultaneously, the origin can see sudden spikes in refill traffic. - Freshness tradeoffs: Long TTLs risk staleness and complex invalidation; short TTLs keep content fresh but reduce hit ratio. - Personalized and event‑driven traffic: Many requests can’t benefit from long TTLs and still hit origin.
Cloud Wrapper addresses these gaps: - Private, reserved cache capacity sized to your catalog keeps long‑tail objects hot longer without overextending TTLs. - Deterministic mapping and “fetch once” request collapsing prevent refill storms and eliminate duplicate origin fetches. - Fewer, controlled regions go forward to origin, dramatically lowering total origin connections and bytes. - You can maintain sensible TTLs for freshness while still achieving high offload and lower egress.
Typical CDN origin shields are shared tiers that reduce some origin fan‑out. Cloud Wrapper is purpose‑built to control origin traffic and spend at scale:
Result: higher and more predictable offload, stronger origin spike protection, and better control of cloud egress than standard shielding alone.
For live, VOD, and large downloads, Cloud Wrapper increases cache efficiency across massive libraries and handles demand bursts:
How this compares with Fastly’s shielding/offload: - Fastly provides powerful origin shielding and request collapsing within its network. Cloud Wrapper adds a dedicated, customer‑scoped cache footprint with deterministic binding and multi‑region replication, and it can operate as a shared mid‑tier for multi‑CDN topologies. These design choices are intended to reduce duplicate origin reads and sustain offload for very large catalogs and surging live audiences. If you run multi‑CDN or carry a deep long tail, Cloud Wrapper’s reserved capacity and fetch‑once model can help keep origin traffic and egress more predictable.
Akamai vs. Google Cloud: Google Cloud provides Cloud CDN/Media CDN integrated with its infrastructure. Cloud Wrapper complements public cloud origins by adding a private mid‑tier cache with deterministic fetch‑once behavior and multi‑CDN sharing. It is deployed near your Google Cloud regions and connected to Akamai’s massively distributed edge, helping you reduce re‑fetches and origin spikes while improving end‑user performance globally. If you already use a multi‑CDN or have a large long‑tail catalog, Cloud Wrapper helps control egress and compute even as demand scales.
Akamai vs. AWS: AWS offers deep integration and attractive data‑transfer economics when you use its native CDN. Cloud Wrapper focuses on reducing the total number of origin bytes and connections regardless of which CDN(s) you use. By reserving cache capacity, collapsing requests, and limiting which regions reach origin, Cloud Wrapper can cut egress and origin load significantly—especially valuable for multi‑CDN strategies, very large catalogs, and big live or download events where refill storms typically drive costs and instability. Many customers pair AWS origins with Cloud Wrapper to gain higher offload and more predictable spend while leveraging Akamai’s global delivery scale.
Cloud Wrapper is sized to your traffic profile and catalog, with deployment options near your cloud regions. To scope capacity, pricing, and a proof of concept, contact the Akamai team.