Cloudflare R2 vs Tigris

Cloudflare R2

Free egress and a free tier of 10 GB-month plus 1 million writes a month. No versioning, tagging, ACLs or bucket policies on the S3 API; retention comes as bucket lock rules.

Tigris

No egress fees, and one endpoint (t3.storage.dev) with region auto for every location. 16 status incidents between 4 July and 2 October 2026, including outages in US regions on 31 July and 2 August.

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

Tigris

1. Point the AWS SDK at https://t3.storage.dev with region auto; the stdio MCP README still shows the older fly.storage.tigris.dev endpoint
2. Ask for an access key with a ReadOnly or ReadWrite role on one bucket rather than an org-wide key
3. Keep presigned URLs short; Tigris accepts up to 90 days
4. Don't call tigris_list_objects on a large bucket; it walks every object with no limit or prefix
5. Use @tigrisdata/iam 2.6.0 or later before writing policies with conditions