Cloudflare R2 vs Wasabi Hot Cloud Storage

Cloudflare R2

Free egress and a monthly free tier of 10 GB-month plus 1 million writes, though enabling R2 needs a checkout with a payment method on the account. No versioning, tagging, ACLs or bucket policies on the S3 API; retention comes as bucket lock rules.

Wasabi Hot Cloud Storage

IAM policies, STS sessions of up to 12 hours, Object Lock and audit logging give an agent tight, revocable access at $7.99 a TB-month with no egress or request fees. No request limits are published with numbers for the S3 API, there is no OpenAPI file, and billing assumes 1 TB and 90 days of storage as minimums.

Cloudflare R2

1. Set region to auto and the endpoint to https://<account-id>.r2.cloudflarestorage.com. us-east-1 also works, other region names fail
2. Ask the operator for temporary credentials scoped to your bucket and prefix rather than a long-lived token
3. For public reads put a custom domain or an r2.dev subdomain on the bucket; presigned URLs only sign the S3 hostname
4. On 429 TooManyRequests check for concurrent writes to one key; R2 allows one write a second per key
5. Send If-None-Match with * on PutObject so a retried upload can't overwrite someone else's object

Wasabi Hot Cloud Storage

1. Use the bucket's own regional endpoint, such as s3.eu-central-2.wasabisys.com. The docs say a wrong endpoint allows GET but not PUT or DELETE
2. Ask for a sub-user key with a policy limited to one bucket, or an STS session. A root key has full access, billing included
3. Avoid short-lived objects. Each object deleted before 90 days is billed for the remaining days, and objects under 4 KB bill as 4 KB
4. Keep monthly downloads at or below the stored volume, the limit of the free egress policy
5. Call https:// endpoints explicitly. The S3 API also accepts plain HTTP
6. For the MCP beta, type https://mcp.wasabisys.dev/s3 from the page text. The links in the docs table point at a different host