Cloud cost intelligence
Most cloud bills hide a networking leak. Model your real egress flows, then see how much each architectural fix recovers.
Teal = share of annual egress spend recoverable with the levers enabled below.
Account-level lever: a negotiated or committed data-transfer-out discount. Applies to internet egress (and the internet portion of NAT flows) across every flow, stacking on top of the per-flow architectural fixes. Inter-region and cross-AZ traffic is left at list price, since those rarely fall under a transfer-out commitment.
| Per-GB rate (USD) | AWS | GCP | Azure |
|---|
Defaults are simplified US/Zone-1 list-price approximations checked in June 2026, with 1 TB treated as 1024 GB. Internet egress is computed across provider volume tiers; the rest are editable flat per-GB assumptions. Inter-region cross-continent pricing is represented with one rate per provider, even though real corridor pricing varies by source and destination. Treat every cell as editable and confirm against the provider's own pricing before quoting a number.
Co-locate moves cross-region endpoints into one region, repricing inter-region traffic at the cross-AZ (or free, same-AZ) rate — the savings are largest on cross-continental flows, which is why each inter-region flow now carries a route selector. Replace NAT with endpoint drops the per-GB NAT-processing surcharge by routing service traffic through a VPC/Private endpoint (or Private Google Access). CDN offload serves a cache-hit share of internet egress from the edge; savings depend on hit ratio and can go negative at low hit rates, which the tool shows honestly. AZ affinity trims avoidable cross-zone chatter from multi-AZ topologies. Committed-use (account-level, above) applies a negotiated discount to internet egress on top of all of the above.
Sources for default rates: provider pricing pages plus independent 2026 breakdowns from AWS, Google Cloud, and Azure. Estimates are illustrative and not a substitute for your actual billing export.