4 MIN READ
The cloud egress bill used to be the line item nobody looked at. In 2026 it has become the line item the finance team has started asking about, the line item the cloud architect has started designing around, and the line item that decides whether the multi-cloud strategy pays back the cost. The egress charge the platform org thought was free turns out to be the largest line item on the bill after the workload lands in production.
What follows is the working version of the field guide. The shorter version is what the architect and the finance team actually have time to read.
What the egress charge actually covers
Data transfer out is the line item the SaaS company watches most closely. The cloud provider charges for the data the workload sends to the internet, and the charge scales with the user base. The product grows, the egress bill grows with it, and most of the company does not see the line item until the bill arrives.
Cross region transfer is the charge the multi region architecture introduces. The cloud provider charges for the data the workload sends to the other region within the same cloud, and the charge accumulates as the global product spreads. Most platforms do not realise this is a separate line item until the second region goes live, and the second region is when the bill starts to look very different.
Cross cloud transfer is the charge the multi cloud architecture introduces. The cloud provider charges for the data the workload sends to the other cloud, and the charge compounds with the egress charge on the receiving side. Every byte that leaves the boundary gets billed twice, and twice turns into a meaningful number once the workload hits production scale.
Where the bill sneaks up
Backup to the other cloud is the line item the architect did not budget for. The platform org backs up the production data to the other cloud for the disaster recovery, and the backup gets sent across the cloud boundary every night. The cross cloud transfer turns into the largest line item on the egress bill, and the line item that never appeared in the original estimate.
Analytics to the data lake is the line item the analytics team does not see on the production bill. The production system sends the event data, the log data, the telemetry to the data lake the analytics team uses, and the data lake sits in the other cloud. The finance team sees the line item on the consolidated bill. The analytics team does not.
Customer data return counts as the line item neither the customer nor the platform org budgeted for. The regulation now requires the data portability request to be honoured, the data the customer uploaded has to be returned, and the egress charge applies to the transfer. The charge the customer did not budget for is the same charge the company has to absorb or pass through.
How to bring it down
Three moves if the cloud architect wants the egress bill under control without giving up the architecture the workload needs.
Cache at the edge. The edge cache (Cloudflare, Fastly, AWS CloudFront) serves the static content from the point of presence close to the user, and the edge reduces the data transfer out of the origin region. The edge can be deployed in a weekend and pays back the cost in a month, which is one of the better ROI arguments in the whole stack.
Compress before transfer. The compression the workload applies before the data leaves the workload reduces the bytes the cloud provider charges for. Gzip, brotli, protocol buffers all provide it. The workload can add the compression layer without changing the architecture, and the savings show up on the next bill.
Co-locate the analytics. The analytics that runs in the same region as the production data avoids the cross region transfer entirely. The data team can run the analytics on the cloud native analytics service the cloud provider offers, instead of running it on the other cloud because the budget was already there. The right home for the analytics is the same region as the data, not the team whose budget already paid for the other cloud.
The cloud architect that pulls all three moves holds the bill. The one that pretends the bill is the cost of doing business ends up being the one that explains the surprise to the CFO at the next quarterly review.
The bottom line
Data transfer out, cross region transfer, cross cloud transfer: those three are the source of the egress bill. Edge cache, compression, co-location: those three are the lever. The architect that pulls all three holds the bill. The one that pretends the bill is the cost of doing business ends up explaining the surprise to the CFO at the next quarterly review.
Sources & Further Reading
All claims in this article are sourced from primary documentation, vendor advisories, and reputable security researchers.
Spotted an error? Email the editor. Corrections are issued with a visible correction note.
Editorial standards. Every article on humanrequired.org is reviewed by a human editor before publication. AI may assist with drafting or research; final editorial control is human. Read the full standards.
