Tigris vs Wasabi Hot Cloud Storage

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.

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.

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

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