A. We are introducing storage and transfer limits to the GitLab SaaS offerings.
|GitLab SaaS Tier||Free||Premium||Ultimate|
|Storage (in GB per top-level group)||5 GB||50 GB||250 GB|
|Transfer (in GB per top-level group per month)||10 GB||100 GB||500 GB|
Note: A 10GB project storage limit for git repository and git LFS is currently active for all projects. Once the namespace storage limit is applicable, the project storage limits will be removed.
A. These limits are applicable to users of the GitLab SaaS offerings. These changes do not apply to self-managed users (both free and paid tier) and community programs - including GitLab for Open Source, Education and Startups users.
Customers who are still on the Bronze subscription are not impacted by this change immediately, and the new limits on Premium / Ultimate will be applicable when they upgrade.
A. Yes, GitLab Trial will receive entitlements from GitLab Ultimate.
A. For existing paid tier users:
For existing paid tier users on a multi-year contract:
A. No, application of storage and transfer limits will be independent of each other. Storage usage visibility, and storage limits will be first, transfer usage visibility and transfer limits will follow.
A. Currently storage includes pipeline job artifacts, repositories, package and container registries, snippets, Git LFS, wiki storage, dependency proxy. Future product features that allow you to store data will also be incorporated into the storage usage count, when available.
A. You can view the storage usage on the Group Settings page for Usage Quota in the
Storage tab. The summaries are divided into all storage types listed in the answer to the "What constitutes Storage usage?" question. Each type provides details on how to proceed with detailed analysis and cleanup procedures.
A. Below you will find steps for managing the different storage types:
A: You can use the GitLab API to programmatically view and delete storage data types. There are programming language libraries available that can help with easy-to-use interfaces, for example listing and deleting job artifacts using the Python library for GitLab. A script based on the Python library has been developed by the GitLab Developer Evangelism team in this project. This MIT-licensed script is not officially supported by GitLab and comes without warranty.
A. We plan to apply a cost factor to forks, similar to what is done today for compute credits, as long as the fork relationship is maintained.
A. Transfer is measured as the amount of data egress leaving GitLab.com, except for:
The primary use cases affected by transfer limits are end users working with code repositories, and public distribution of containers and packages. Future product features that allow transfer of data will also be incorporated into the transfer usage count, when available.
A. Viewing transfer usage is not yet available. Until the usage report is available on the Group Settings Usage
Quota Page, transfer limits will not be programmatically applied. If your usage is significantly high, the GitLab team will reach out to you to help manage your usage.
A. Additional storage or transfer units can be purchased from the GitLab Customer Portal at $60/year that includes both 10GB of storage and 20GB/month transfer. For example:
For more information on managing and reducing your storage usage, please contact GitLab support or your GitLab sales representative.