Wasabi · Rate Limits
Wasabi Rate Limits
Wasabi does not publish hard numerical rate limits for API requests. Instead, Wasabi enforces a free API request policy based on qualitative usage standards. Accounts with validated commercial use cases are generally compliant. Non-validated applications causing inefficient server loads may face restrictions. Egress-to-storage ratio enforcement acts as an implicit throughput constraint.
Wasabi Rate Limits is the machine-readable rate-limit profile for Wasabi on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 5 rate-limit definitions.
The profile also includes 2 backoff/retry policies defined.
Tagged areas include Cloud Storage, Object Storage, S3 Compatible, REST API, and Hot Storage.
5 Limits
Cloud StorageObject StorageS3 CompatibleREST APIHot StorageBucketsObjectsMedia StorageBackupEnterprise Storage
Limits
API Request Rate
Egress-to-Storage Ratio
1
Example: storing 100 TB allows up to 100 TB of monthly egress downloads at no charge. Exceeding this ratio triggers policy enforcement.
Minimum Object Size (Billing)
4
Minimum Storage Duration (Billing)
90
Minimum Monthly Storage (Billing)
Policies
Free API Request Policy
Wasabi provides free API requests for standard commercial workloads. The policy is enforced based on usage patterns rather than hard thresholds. Applications generating disproportionate server load relative to storage activity may be restricted.
Free Egress Policy
Wasabi provides free egress up to the 1:1 egress-to-storage ratio. Ingress (data upload) is always free and unrestricted. Egress exceeding the active storage volume is considered out of policy.