CloudOverview / Reference

Field guides for choosing storage

Work from the workload to the architecture, then to the bill.

These guides use illustrative workloads and explicit assumptions. They are editorial analysis; we have not benchmarked the providers.

Field guide

Amazon S3 vs Cloudflare R2

Compare regional integration and direct-delivery economics without assuming the products are interchangeable.

Read the guide ↗
Field guide

Backblaze B2 vs Wasabi

Compare stable backups, changing objects and full restores—not just two headline capacity prices.

Read the guide ↗
Field guide

Budgeting for public downloads

A small object library can create a large transfer bill. Plan for the popular release and repeated downloads.

Read the guide ↗
Field guide

Choosing object storage for public images

Separate originals, variants, origin requests and delivery before comparing the bill.

Read the guide ↗
Field guide

Choosing storage for backups you can restore

Budget for the recovery event, object churn and retained versions—not only a quiet month of storage.

Read the guide ↗
Field guide

Evaluating European object storage

A European region is one useful fact. It does not answer every placement, resilience or processing question.

Read the guide ↗
Field guide

Request costs and egress: two different meters

Understand why small objects can be operation-heavy and large downloads can be bandwidth-heavy.

Read the guide ↗
Field guide

S3 compatibility is an operation checklist

Validate the client behavior you need instead of treating API compatibility as a universal yes/no promise.

Read the guide ↗