.png)
How It Works
Every major cloud provider charges for outbound data transfer, commonly called egress. When your application sends data to end users over the internet, moves files between regions, or exports data to an on-premises system, the provider meters those bytes and bills accordingly. AWS calls this “data transfer out,” Azure calls it “bandwidth,” and GCP uses the same “egress” terminology. Inbound data (ingress) is typically free, but outbound data is not. Costs accumulate per gigabyte transferred, and the rate varies by destination: transferring within the same region is usually cheapest, cross-region transfers cost more, and transfers out to the internet cost the most. At scale, these charges can represent a significant and often overlooked share of a cloud bill.
Why It Matters for Cloud Cost
Egress costs are among the most underestimated line items on a cloud invoice. They tend to grow quietly alongside application traffic without triggering the same scrutiny as compute or storage spend. A data-intensive workload, a poorly architected microservices setup with excessive cross-region calls, or a content delivery configuration that bypasses a CDN can each drive egress charges into the tens or hundreds of thousands of dollars per year. Without visibility into which services and destinations are generating egress, engineering and finance teams have no clear target for reduction. Egress charges also create a structural disadvantage: because providers charge heavily to move data out, switching providers or adopting a multi-cloud architecture becomes more expensive than it appears on paper.
ClearCost, Usage AI’s visibility and showback reporting layer, provides teams with cost reporting across their cloud accounts to support spend analysis and internal accountability.