egress fees

Webcast

Stop Paying Egress Tax for Your Own Data

The Hidden Cost Reshaping Cloud Architecture

Picture of DataStorage Editorial Team

DataStorage Editorial Team

Watch the Full Webcast

DataStorage.com x Backblaze: How Cloud Storage Economics Are Shifting in the AI Era

Hear the full discussion on egress fees, data mobility, and why storage design is being rewritten.

Table of Contents

The Egress Problem Isn’t Just a Bill — It’s an Architectural Constraint

If you run a data-intensive business — AI, SaaS, media, analytics — you’ve likely felt it: egress fees quietly dictate how teams build, store, and ship data.

In our recent conversation with Backblaze VP of Sales Nilay Patel, he put it bluntly:

“Amazon charges these incredibly high fees to get your data out… they’re just crazy, egregious fees.”

The hyperscaler model hasn’t merely made storage expensive — it has made using your own data expensive. Which leads to a bigger issue: companies architect around avoiding egress, not around what their workloads actually need. Cold tiers, fractured pipelines, delayed migrations, single-cloud lock-in — most of these patterns stem directly from a fear of the “egress tax.”

How Egress Fees Distort Technical Decision-Making

Patel gave a concrete example that captures the absurdity:

“They charge you about $90 per terabyte to access your data once.”

Run that math on any sizable workflow — video delivery, AI training sets, nightly ETL jobs — and the consequences are obvious:

  • Teams reduce data access to avoid unpredictable bills.
  • Companies avoid multi-cloud architectures even when compute or CDN alternatives are better.
  • Media teams downsample, AI teams store less, SaaS teams limit customer exports — simply to avoid costs.

One of the stories Patel shared shows how extreme this gets:

“A media company needed to re-index assets after changing their media management system… it took so long and cost so much to pull the footage from Glacier that they said, ‘We are never doing that again.’”

That’s not an engineering decision. That’s a penalty.

Why Cold Storage Is Failing Modern Workloads

Cold storage emerged for archival-era problems. Today’s reality is different:

  • AI teams need fast, repeated access to large training sets.
  • Media teams need to retrieve raw footage instantly.
  • SaaS platforms need immediate access to logs, snapshots, or customer data.
  • Even internal analytics jobs increasingly rely on live object storage data, not warehoused extracts.

Patel captured how quickly this has shifted:

“There’s all this data that maybe was thought to not be valuable anymore. But now suddenly it is — and you need access to it.”

AI and multimodal training pipelines flipped the script: archived data became active data overnight. And cold tiers, with their retrieval delays and egress penalties, are architecturally incompatible with that shift.

The Economics Behind Always-Hot Storage

The podcast dives deep into the economics of why hyperscalers price egress so aggressively. Patel doesn’t hedge:

“On the egress side, they are just charging you a tax. It’s not because they have some innovative way to make it cheaper… They want to lock you into using only their services.”

That economic model creates three distortions:

  1. Data becomes trapped. Teams hesitate to migrate, even when another cloud is cheaper, faster, or closer to GPUs.
  2. Architectures become monolithic. Workflows that should be modular — storage → compute → CDN — get forced into one provider.
  3. Innovation slows. Patel shared real customer impact:

    “One company had to shut off their free tier and delay engineering hires because AWS storage and egress became too expensive.”

Egress fees don’t just distort cloud bills — they distort roadmaps, product strategy, and growth.

Why Data Mobility Is Becoming a Requirement

A major theme of the episode: modern infrastructure is moving toward choice, not consolidation.

AI startups are using GPU clouds like CoreWeave, Lambda, Voltage Park. Media companies are pushing video through CDNs like Cloudflare, Fastly, Akamai. SaaS platforms are running analytics in Snowflake, BigQuery, Databricks.

Your storage can no longer assume a single downstream compute or delivery path. Patel captured the reality:

“One quarter of all our outbound traffic now goes to neo clouds. These companies didn’t exist a few years ago.”

Infrastructure is fragmenting — fast. And egress-heavy storage is fundamentally incompatible with that trend.

What Modern Teams Need in Storage Infrastructure

To support data mobility and high-throughput workloads, storage needs to be:

  • Always-hot — no tiering, no cold delays.
  • Predictably priced — flat, transparent, not usage-punitive.
  • Egress-friendly — architected for movement, not lock-in.
  • High-throughput — especially for AI teams feeding GPUs.
  • S3-compatible — to slot into existing tools and pipelines.

The next decade belongs to cloud architectures that are flexible, modular, and multi-cloud by default — not locked into a single provider’s economics.

Go Deeper: Watch the Full Conversation

In the webcast, we explore:

  • Why cold storage fails AI and media workloads
  • How egress fees became a cloud “dark pattern”
  • Why data mobility is now a competitive advantage
  • The rise of neo GPU clouds and multi-cloud workflows
  • Real examples of teams rethinking storage economics

Share this article

🔍 Browse by categories

🔥 Trending Articles

Newsletter

Stay Ahead in Cloud
& Data Infrastructure

Get early access to new tools, insights, and research shaping the next wave of cloud and storage innovation.