Limits and quotas
Default per-account limits as of 2026-05-27. Limits scale with usage; email support@bangmod.storage if your workload exceeds these — we raise the ceiling on validated workloads.
Storage and objects
| Resource | Default limit |
|---|---|
| Buckets per account | 100 soft cap. Raise on request. |
| Objects per bucket | Unlimited (operationally; subject to fair-use review for >1B keys). |
| Max object size | 5 TB |
| Max single PUT | 5 GB. Use multipart for larger. |
| Min multipart part size | 5 MB (except the last part) |
| Max multipart parts | 10,000 |
| Max object key length | 1024 bytes (UTF-8 encoded) |
| Max user metadata per object | 2 KB (sum of x-amz-meta-* headers) |
| Tags per object | 10 |
| Tags per bucket | 50 |
API rate limits
| Operation class | Sustained req/sec per prefix | Burst |
|---|---|---|
| PUT / POST / DELETE / COPY | 3,500 | 10× for 30 s |
| GET / HEAD | 5,500 | 10× for 30 s |
| LIST | 500 (per bucket, not per prefix) | 3× for 30 s |
Throttled responses return HTTP 503 with x-amz-error-code: SlowDown. Implement exponential backoff as you would against AWS.
Access keys
| Resource | Default limit |
|---|---|
| Active access keys per account | 10 |
| Members per account | 20 (Enterprise raises this on request) |
| Presigned URL max expiry | 604,800 seconds (7 days) |
Bandwidth and egress
We do not throttle aggregate egress for paying accounts. Egress is metered and billed per GB; no hidden caps.
Public buckets (those served via anonymous read) have a separate fair-use review process to prevent open-relay-style egress abuse; see AUP §3.
Free tier
New accounts receive a small monthly allowance to validate the service. Specifics are listed on the pricing page at sign-up.