Wasabi

Wasabi positions itself as hot storage — always-accessible, no retrieval fees, no storage class complexity. For agents, the appeal is simplicity: one storage tier, S3-compatible API, predictable pricing. The 90-day minimum storage duration is the critical constraint agents must account for — objects deleted before 90 days still incur the full 90-day charge. This makes Wasabi unsuitable for temporary file staging or short-lived cache patterns. For persistent storage of artifacts, logs, or datasets that agents reference over weeks or months, the pricing advantage over S3 Standard is meaningful. No serverless compute integration, no event notifications, no data processing pipeline — Wasabi is pure storage.

IAM-style access keys with access key ID and secret key, compatible with S3 SDKs. Wasabi supports IAM policies for user/group permission management — more granular than B2's key scoping but simpler than AWS IAM. Bucket policies control resource-level access. No STS equivalent for temporary credentials — agents must use long-lived keys. MFA delete is supported for bucket protection. The account model supports sub-accounts for organizational isolation. No workload identity federation or OIDC integration. For agents, the auth surface is functional but basic: create a key, scope it to a bucket, use standard S3 auth headers.

Wasabi's API is S3-compatible via region-specific endpoints (s3.wasabisys.com for us-east-1, s3.us-west-1.wasabisys.com, etc.). Standard S3 SDKs work with endpoint override. ListObjectsV2, GetObject, PutObject, DeleteObject, and multipart upload all function as expected. Object versioning and lifecycle policies are supported. Gaps from full S3 compatibility: no Select (SQL query over objects), no batch operations, no storage class transitions (single tier), no S3 Object Lambda. For straightforward CRUD — which is what most agent storage workloads need — the compatibility is adequate. Response format follows S3 XML conventions.

Error responses follow S3 XML format with standard error codes. The most agent-relevant operational constraint is the 90-day minimum storage policy — delete requests succeed immediately but billing continues for the remainder of the 90-day period. This is not an error condition; it's a business rule that agents must encode in their storage selection logic. Rate limits exist but are not publicly documented with specific thresholds. Wasabi's SLA guarantees 99.9% availability. Immutability features (object lock, compliance mode) are available for regulatory workloads. Multi-region replication is supported across Wasabi's growing region list but requires explicit configuration.

Documentation covers the essentials — account setup, S3 compatibility, IAM configuration, and region endpoints — but lacks the depth of S3, GCS, or even B2's docs. Integration guides for common tools (rclone, Cyberduck, Veeam) are available but agent-specific guidance is absent. The knowledge base format mixes support articles with technical documentation, making discovery uneven. No official SDK — agents use standard S3 SDKs with endpoint override, which works but means Wasabi-specific features (like the compliance dashboard) aren't programmatically accessible. Console UI is functional for basic management. Community and ecosystem are smaller than competitors.