Cloudflare vs Wasabi
Both appear in 2 sections: object storage, egress. Wasabi is cheaper on 2 of 2 comparable measures.
Cloudflare R2 and Wasabi both remove egress fees, which is the expensive part of object storage, and then differ on everything else. Wasabi stores bytes far more cheaply at $0.00699/GB-month against R2's $0.015, roughly half. Neither charges for egress. The difference is in the conditions attached. Wasabi requires a 1 TB minimum billing amount and enforces a 90-day minimum retention per object, so small deployments pay for capacity they do not use and churning data is billed after deletion. R2 has no minimum of either kind: you pay for what is stored, per byte, per month, and deleting an object stops the charge immediately. R2 also charges for operations, $0.0045 per thousand writes and $0.00036 per thousand reads, where Wasabi charges nothing. The practical split is size and volatility. A stable archive above a terabyte is cheaper on Wasabi, and the gap grows with volume: 10 TB costs about $70 a month against R2's $150. Below a terabyte, or with objects that are frequently replaced, Wasabi's minimums make it more expensive in practice than the headline suggests. R2's other argument is adjacency: it sits inside Cloudflare next to Workers and the CDN, so serving from it involves no egress and no additional hop, which Wasabi cannot match.
Object storage
All object storage →Egress
All egress →Neither provider runs an affiliate programme; Pikkly earns nothing from this page.