Limits and quotas
Cloud tenants operate within fixed service limits that cannot be changed from the UI.
Limits
| Limit | Value |
|---|---|
| Total storage (database + artifacts) | 60 GB |
| Upload body size | 100 MB |
| Single test result file size | 2,000,000 bytes |
Storage
The 60 GB allocation covers both database content and stored artifacts combined. Once the limit is reached, new uploads may be rejected.
Starting from version 26.4, you can check the current storage usage under Administration → Usage: the Storage usage section shows how much space the database and the artifact storage take and when it was last measured. If your data gets close to the limit, Qameta Software notifies you in advance.
To free up space, configure Cleanup policies and focus on high-volume artifacts from passed tests first. If you need more than 60 GB, see Premium Cloud.
Upload size
The 100 MB limit applies to the full HTTP request body. Uploads that exceed it are blocked before Allure TestOps processes the files.
The 2,000,000 byte limit applies to a single result file. If one file is too large, that result fails to process even if the rest of the upload is valid.
If uploads fail unexpectedly, check request body size and individual result file size before investigating the CI integration.
Statistics rendering lags
The presence of a lag in the delivery of the statistics is an expected behaviour. The application BE caches the data for the requests made towards the database to render widgets data in project dashboards. The cache TTL is 15 minutes by default for all widgets and 30 minutes for the widgets that are showing statistics related to the test results quantities.