How Wasabi Pricing Works and What Fees Wasabi Says It Doesn't Charge

Wasabi prices storage as a flat rate per terabyte per month, and the company states that it does not charge for egress, API requests, or data retrieval. That combination is the core of its pitch: you pay for what you store, and moving or accessing that data doesn't add a separate line item. This model is aimed at workloads where data is read frequently or moved between systems — AI training data, backups, archives — because those are the activities that generate the "hidden" fees on other clouds. The trade-off to weigh is that flat per-TB pricing rewards predictable, large-footprint storage and is less suited to tiny datasets or workloads where you need frequent small-file churn with heavy metadata operations, since you're paying for capacity rather than activity.

The billing model in one sentence

Wasabi charges a flat rate per TB of stored data per month. There is no separate meter for how much you download, how many API calls you make, or how often you retrieve a file.

The company frames this against hyperscaler pricing by arguing that "nearly half of hyperscaler storage cost is fees, not storage," and that egress, API requests, and retrieval charges "compound fast at AI scale." Wasabi's answer is one rate with no surprises.

What Wasabi says it does not charge for

The page states data is "hot by default with no rehydration or retrieval fees," and that there are "no fees for egress, access, or recovery" in the context of its cyber resilience offering. For AI workloads it states "zero egress to any data platform, neocloud, hyperscaler, or on-prem GPU clusters."

Why "hot by default" matters for cost

On tiered storage systems, data that sits in a cold or archive tier is cheap to store but expensive or slow to access — you pay retrieval fees and wait for rehydration. Wasabi's model removes that tiering decision: data stays accessible, and access doesn't trigger a charge.

That changes the cost math for two common patterns:

• Backups and archives you actually restore. If you test restores or pull data for legal discovery, audit, or ransomware recovery, retrieval fees on a tiered system can dominate the bill. Wasabi states immutability for regulatory holds, legal discovery, and audit-ready retention with no retrieval fees.
• AI and analytics pipelines that read repeatedly. Training datasets, checkpoints, and inference logs get read many times. Under per-request or per-GB egress pricing, that read pattern is the expensive part. Wasabi states it works with any GPU cloud or compute provider with no fees when data moves.

Estimating your cost

The page includes a savings calculator that takes three inputs and returns a monthly and annual figure:

• Storage amount (the example starts at 1 TB)
• Percent downloaded per month (the example uses 20%)
• The output is shown as a monthly and yearly dollar amount

To use it for your own estimate, you need your total stored volume in TB and a realistic read percentage — the share of your stored data you download or retrieve in a typical month. If you're comparing against another provider, run the same two numbers through both pricing models; the gap usually comes from the read percentage, not the storage rate.

What the pricing page does not specify

The source material describes the pricing structure (flat per-TB, no egress/API/retrieval fees) and mentions a free trial, but it does not list the actual dollar rate per TB, minimum storage commitments, minimum retention periods, or support-plan costs. Those are the details that determine your real bill, so confirm them on Wasabi's pricing page or with sales before committing.

Two practical checks before you decide:

1. Minimum duration and minimum storage. Many flat-rate object storage providers require a minimum retention period (e.g., 90 days) or a minimum billable volume. If your data is short-lived or your footprint is small, this can raise your effective cost above the headline rate.
2. What counts as a "request." Wasabi states no API request fees, but confirm whether any operations (like certain lifecycle transitions or bulk deletes) fall outside that.

When this pricing model fits

Wasabi's flat per-TB model with no egress or retrieval fees tends to fit best when:

• Your stored volume is large and grows predictably (backups, archives, AI datasets).
• You read or move data often enough that per-GB egress or per-request charges would be significant.
• You want to avoid tiering decisions and rehydration delays.

It fits less well when your dataset is small, when you store data for only a few days, or when your workload is dominated by massive numbers of tiny objects rather than capacity — in those cases, compare the effective per-TB cost including any minimums against usage-based alternatives.