Pain Point

Zero-Egress Economics

The architectural and financial constraint where outbound data transfer fees dominate total cost of ownership for high-bandwidth, multi-cloud, and edge AI workloads, and the emerging class of S3-compatible providers that eliminate these fees entirely.

5 connections 3 resources

Summary

What it is

The architectural and financial constraint where outbound data transfer fees dominate total cost of ownership for high-bandwidth, multi-cloud, and edge AI workloads, and the emerging class of S3-compatible providers that eliminate these fees entirely.

Where it fits

A FinOps-critical pain point that dictates multi-cloud architecture decisions. Zero-egress providers like Cloudflare R2, Backblaze B2, and Wasabi have weaponized free egress to capture market share from hyperscalers, fundamentally altering how organizations design hybrid-cloud, edge AI, and cross-region data pipelines.

Misconceptions / Traps
  • Egress is not a minor line item — for data-intensive AI workloads, outbound transfer fees can exceed raw storage costs by 5-10x.
  • Zero-egress does not mean zero cost — API request fees and storage costs still apply and must be modeled.
  • Not all zero-egress providers offer equivalent durability, feature parity, or sustained throughput compared with AWS S3.
Key Connections
  • is_a Egress Cost — the specific economic facet of egress as an architectural constraint
  • constrained_by Cloudflare R2 — R2 eliminates egress fees for all outbound transfer
  • constrained_by Backblaze B2 — B2 offers free egress with CDN integration partners

Definition

What it is

The architectural and financial constraint where outbound data transfer fees dominate total cost of ownership for high-bandwidth, multi-cloud, and edge AI workloads. Zero-egress providers (Cloudflare R2, Backblaze B2, Wasabi) eliminate these fees entirely, fundamentally altering multi-cloud routing architectures.

Connections 5

Outbound 5

Resources 3