A practical decision rule: use Amazon S3 when backup durability, lifecycle depth, and ecosystem coverage dominate; use Cloudflare R2 when an S3-compatible edge-oriented design fits; use Azure Blob when the rest of the estate is already Azure; consider Infrai when the main cost is integrating several backend capabilities and a plain, discoverable REST surface matters. For a fintech tenant-document system, keep every object private, make restore a separate workflow, and treat a large-file transfer as a throughput problem rather than a pricing headline.
The backup invariant is simple: a tenant snapshot is immutable to the restore workflow, a retry cannot create a second logical snapshot, and the restore target is selected explicitly. The storage provider is only one part of that contract. A cheap GB-month does not compensate for an unsafe overwrite or a restore path that cannot explain what happened.
Keep it boring.
What fails first in a tenant backup runbook?
The dangerous signal is not always an outage.…