Understanding the Egress Fee Mechanism in ML Workflows

Egress fees are not merely a line item on a monthly bill; they are a fundamental architectural constraint for machine learning engineers. In a typical ML pipeline, data moves through several stages: ingestion from a data lake, preprocessing, distributed training across a GPU cluster, and finally, the export of model weights for inference or long-term storage. Each time this data crosses the boundary of a cloud provider's network, a meter starts running. For hyperscalers, this is a high-margin revenue stream designed to discourage users from moving their workloads to competing platforms.

Egress Impact on Multi-GPU Training Pipelines

The technical challenge arises from the sheer volume of data involved in modern AI. Training a Large Language Model (LLM) or a high-resolution computer vision model requires massive datasets that must be streamed to the GPUs. If your data resides in an AWS S3 bucket but your optimized GPU compute is located on a specialized provider, the egress costs from S3 can quickly exceed the cost of the compute itself. This creates a phenomenon known as 'data gravity,' where the cost of moving data is so high that it dictates where the compute must happen, regardless of whether that compute is the most efficient or cost-effective option available.

Egress fees are often non-linear and tiered. They vary based on the destination (internet vs. another region vs. another zone) and the total volume of data transferred per month. This complexity makes it nearly impossible for CTOs to accurately predict the final cost of a training run until the bill arrives, leading to the common 'cloud bill shock' experienced by many growing AI teams.

The Hyperscaler Tax: AWS, GCP, and Azure Egress Structures

The 'Big Three' hyperscalers, including Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure, have built their empires on integrated ecosystems. Their egress fee structures are a key component of this integration. While they often offer significant credits to startups, once those credits expire, the egress fees become a significant burden. These providers typically charge for any data that leaves their specific network backbone to the public internet. While they have introduced waivers for users moving off their platforms under pressure from the EU Data Act, those waivers are conditional. The AWS announcement of 5 March 2024, updated 30 September 2025 and read on 3 August 2026, asks you to apply through AWS Support, gives eligible customers 90 days to complete the move, states that you do not have to close your account, and warns that repeat applications from the same account draw extra scrutiny. None of that covers the daily multi-cloud operations that most AI teams require.

Provider-by-Provider Egress Comparison

In a technical comparison, hyperscalers differentiate between 'inter-region' and 'internet' egress. Inter-region egress occurs when moving data between two data centers owned by the same provider (e.g., from US-East-1 to US-West-2). While cheaper than internet egress, it still adds up during distributed training across multiple regions. Internet egress is the most expensive tier and is triggered whenever you move model checkpoints to a local server or a different GPU cloud provider. For an ML engineer, this means that every `torch.save()` operation that targets an external storage volume is a billable event.

The published rates sit close together and every one of them is tiered by monthly volume. Read on 3 August 2026, AWS lists internet data transfer out of EU (Frankfurt) at $0.09 per GB for the first 10 TB per month beyond a 100 GB free allowance, then $0.085 per GB for the next 40 TB, $0.070 per GB for the next 100 TB and $0.050 per GB above 150 TB. Microsoft Azure lists internet egress from Europe at $0.087 per GB after a free first 100 GB, then $0.083, $0.070 and $0.050 per GB as monthly volume rises. Google Cloud Premium Tier to European destinations lists $0.12 per GiB for the first 1,024 GiB, $0.11 per GiB up to 10,240 GiB and $0.085 per GiB above that, with inbound transfer free. Lyceum charges nothing for ingress or egress on its S3-compatible storage.

The complexity of these tiers often requires dedicated DevOps resources just to monitor and optimize data transfer. Teams frequently resort to complex workarounds, such as setting up private direct connects or using specialized data transfer services, which add their own layers of management overhead and cost. This 'hyperscaler tax' is a primary reason why many AI teams are seeking sovereign, specialized alternatives that offer more transparent and predictable pricing models.

Specialized GPU Clouds and the Shift to Zero Egress

As the demand for high-end GPUs like the H100 and B200 has surged, a new category of specialized GPU cloud providers has emerged. Unlike hyperscalers, these providers focus almost exclusively on compute-intensive workloads. Many of these specialized players have recognized that egress fees are a major pain point for AI researchers and have moved toward a 'zero egress' or 'low egress' model. This shift is not just a marketing tactic; it is a response to the technical reality that AI data is highly mobile and should not be held hostage by infrastructure providers.

Specialized clouds often leverage partnerships with network providers like Cloudflare (through the Bandwidth Alliance) to reduce or eliminate the costs of data transfer. For an ML team, this means they can maintain their primary data lake on one platform while bursting their training workloads to a specialized GPU cluster without worrying about the financial penalty of moving data back and forth. This flexibility is crucial for performing hyperparameter tuning or architectural searches where multiple versions of a model might be exported for evaluation.

Sovereign providers ensure data remains within specific jurisdictions, a critical requirement for scaleups dealing with sensitive or regulated data. Eliminating egress fees allows engineers to focus on model performance rather than bandwidth budgeting, aligning infrastructure incentives with efficient development.

Data Gravity and the Strategic Risk of Vendor Lock-in

Vendor lock-in is often discussed in terms of proprietary APIs or software frameworks, but in the AI era, the most potent form of lock-in is financial. Data gravity, fueled by egress fees, creates a situation where a company's most valuable asset, its data, becomes too expensive to move. This has profound strategic implications for AI startups. If your entire training pipeline is tied to a single provider's storage and compute because of egress costs, you lose the ability to negotiate on price or to take advantage of superior hardware availability elsewhere.

Migration Costs and Data Gravity Lock-In

When a more efficient GPU architecture becomes available on a different platform, data gravity can prevent migration. If your training data is locked behind a six-figure egress wall at your current provider, the cost of switching might outweigh the performance gains of the new hardware. This effectively stifles innovation and forces teams to settle for sub-optimal infrastructure. Furthermore, relying on a single provider for both storage and compute creates a single point of failure. A multi-cloud strategy, which is the gold standard for enterprise resilience, is financially non-viable when egress fees are high.

By choosing a provider with zero egress fees, AI teams can implement a 'best-of-breed' infrastructure strategy. They can store their massive raw datasets in cost-effective cold storage, preprocess them on CPU-optimized instances, and then stream the processed data to high-performance GPU clusters like those managed by Lyceum. This modular approach not only reduces costs but also gives the engineering team the freedom to pivot their infrastructure as the AI landscape evolves. It transforms the cloud from a walled garden into a utility that can be utilized on demand.

Add GPU compute costs to your egress fee comparison. Try the GPU Pricing Calculator →

Calculating the Total Cost of Compute (TCC)

To truly compare GPU cloud providers, ML engineers must look beyond the hourly rate of an A100 or H100. The relevant metric is the Total Cost of Compute (TCC). TCC is a holistic calculation that includes the GPU hourly rate, storage costs, management overhead, and, crucially, egress fees. A provider might offer a lower hourly rate for a GPU but make up for it with aggressive egress charges and high storage premiums. Whether the 'cheaper' GPU is actually cheaper depends on how much data the job moves. At the AWS rates above, exporting 50 TB of checkpoints and processed datasets in a month adds about $4,400 before a single GPU hour is counted, which is enough to reverse a small advantage in the hourly rate.

Total Cost of Compute (TCC) Formula

The formula for TCC can be simplified as: TCC = (GPU Rate × Training Time) + (Data Ingestion + Egress) + (Storage) + (DevOps Hours). In this equation, egress is often the most volatile variable. While training time can be estimated based on model size and hardware throughput, egress depends on how many times you need to move data out of the environment. If you are performing frequent checkpointing to an external S3 bucket for safety, your egress costs will scale linearly with the duration of your training run.

Workload-aware pricing and precise predictions address the TCC problem. Predicting memory footprint and utilization before a job runs helps teams select cost-effective hardware. Zero egress fees provide cost predictability often unavailable on hyperscaler platforms. For a scaleup operating on tight margins post-credits, this predictability is the difference between a successful product launch and a depleted runway. It allows for more aggressive experimentation and faster iteration cycles, which are the primary drivers of success in the AI market.

EU Sovereignty and Data Transfer Compliance

For European AI companies, egress fees are not just a financial issue; they are often intertwined with data sovereignty and compliance. Under the GDPR and the evolving EU Data Act, the movement of data across borders, and even between different cloud providers, is subject to strict oversight. Hyperscalers, which are primarily US-based, often move data through international backbones, which can complicate a company's compliance posture. When data leaves a provider's network (triggering an egress fee), it may also be crossing jurisdictional boundaries, necessitating complex Data Transfer Impact Assessments (DTIAs).

EU Data Act and Fair Egress Pricing

The EU Data Act specifically targets unfair contractual terms and high switching costs, including egress fees. The goal is to make it easier for customers to switch between data processing services. However, the technical implementation of these regulations is still catching up with the reality of AI infrastructure. Sovereign providers headquartered in the EU keep processing inside European data centres. That narrows the legal framework and reduces the risk associated with international data transfers, though the controller still owns the compliance assessment. We also keep a practical guide to choosing a GPU cloud without egress fees.

Furthermore, the EU Data Act provides safeguards against unlawful third-country governmental access to and transfer of non-personal data held in the EU. When your data is stored and processed on a European cloud with zero egress fees, you have full control over its lifecycle. You are not penalized for moving your data to a local on-premise server for specialized auditing or for sharing it with a European partner. This level of control is essential for industries like healthcare, finance, and defense, where data integrity and residency are non-negotiable. In this context, zero egress is not just a cost saving; it is a feature of a secure and compliant data strategy.

Technical Strategies to Minimize Egress Impact

While choosing a zero-egress provider is the most effective way to eliminate these costs, engineers can also employ several technical strategies to minimize data transfer volume. One common approach is the use of efficient data formats. Moving away from raw CSV or JSON files to binary formats like Parquet or TFRecord can significantly reduce the size of the data being transferred. Compression algorithms like Zstandard (zstd) offer a high compression ratio with low CPU overhead, making them ideal for streaming datasets to GPU instances.

Data-Local Preprocessing and Compression

Another strategy is to implement 'data-local' preprocessing. Instead of moving raw data to the GPU cluster, perform as much filtering, augmentation, and normalization as possible within the same network zone where the data is stored. This ensures that only the 'final' training-ready data is sent over the wire. For teams using PyTorch, the WebDataset library is an excellent tool for this. It allows for efficient streaming of large datasets stored as POSIX tar files, which can be read sequentially from any web server or cloud storage, minimizing the need for large-scale data migrations.

import webdataset as wds
 # Example of streaming a dataset to minimize local storage and egress
 dataset = wds.WebDataset("https://<storage-endpoint-from-your-lyceum-dashboard>/data/train-{000..099}.tar") \
 .decode("rgb") \
 .to_tuple("jpg", "json")
 # This approach allows for processing data as it arrives,
 # reducing the need for massive one-time transfers.

Optimizing checkpointing frequency is critical. While frequent checkpoints are necessary for fault tolerance in long-running jobs, each checkpoint represents a potential egress event if stored externally. Using a tiered storage approach, where checkpoints are first saved to fast, local NVMe storage and only periodically synced to external persistent storage, can drastically reduce the total volume of data leaving the network. Auto-detection of memory bottlenecks and workload-aware scheduling helps engineers balance safety and transfer efficiency.

Strategic Infrastructure for AI Scale

AI infrastructure should be transparent and accessible. The GPU cloud market, often characterized by low utilization and opaque egress fees, creates barriers to innovation. Providing CLI, API and dashboard access environments that are high-performance and cost-optimized helps address these challenges. Because Lyceum's S3-compatible storage carries no ingress or egress charge, AI teams can treat the cloud as an extension of their local development environment.

The platform's auto hardware selection engine is a key differentiator. It doesn't just provide a list of GPUs; it analyzes the specific requirements of a workload, considering factors like memory footprint and time constraints, and selects the optimal hardware configuration. This ensures that teams are not overprovisioning resources, which is a major source of waste in AI development. When this optimization is combined with zero egress fees and zero hidden costs, the result is a significantly lower Total Cost of Compute compared to traditional hyperscalers.

For ML engineers, the experience is streamlined through a CLI tool and VS Code extension, allowing them to launch jobs on EU-sovereign infrastructure without leaving their IDE. This level of integration, combined with GDPR-compliant processing in European data centres in Spain, Paris and the Nordics, makes Lyceum a strong partner for European scaleups. As the AI industry moves toward more complex, data-intensive models, the need for a sovereign, egress-free cloud will only grow. Modern infrastructure provides the tools AI teams need to scale without hidden costs.

Sources

[1] AWS News Blog, Free data transfer out to internet when moving out of AWS, 5 March 2024, updated 30 September 2025, read 3 August 2026; [2] Google Cloud, VPC network pricing, Premium Tier internet data transfer out to Europe, read 3 August 2026; [3] European Commission, Data Act, in force 11 January 2024 and applicable from 12 September 2025, read 3 August 2026; [4] Cloudflare, Bandwidth Alliance, read 3 August 2026; [5] Amazon Web Services, AWS Data Transfer price list, EU (Frankfurt), published 20 July 2026, read 3 August 2026; [6] Microsoft Azure, Bandwidth pricing, internet egress from Europe, read 3 August 2026