Wasabi

Use it when

• The bill must be predictable from stored volume alone: one flat rate per terabyte-month, with no separate egress or API-operation charges.
• Data is written once and kept: backups, archives, media libraries, compliance retention.
• WORM matters: Object Lock in governance and compliance modes with legal holds, to SEC 17a-4.
• Existing S3 tooling should work unchanged.

Think twice when

• Data is short-lived or rewritten: the 90-day minimum duration bills deleted or overwritten objects through day 90, which punishes staging areas and partition-rewriting pipelines.
• Reads routinely exceed stored volume; the free-egress policy assumes egress stays below it, and sustained overage is capped by policy rather than priced.
• Compute must sit next to the data; there is no colocated query ecosystem, so engines read across the network.
• Tiering is expected; there is deliberately one storage class.

How it runs

Fully managed with eleven-nines annual durability (the mechanism is not published), replication available to another region on the same continent or to another account, and event notifications only through SNS, which requires an AWS account. The single-tier, flat-rate model is the product; Backblaze B2 is the closest competitor, differing mainly on minimum duration.