Q. How can I view and manage my compute minutes usage?
A. A Group Owner can view compute minutes usage on the Usage page in your Group settings page.
Q. How can I view and manage my compute minutes usage on public projects?
A. The compute minutes limit is applicable for public projects on GitLab.com as well.
Q. How can I reduce the amount of compute minutes consumed?
A. There are a few methods to consider to reduce the number of compute minutes consumed:
Watch this deep dive video on how you can manage your compute minutes usage.
Q. What happens if I hit the compute minutes allotted limit and forget to purchase additional compute minutes?
A. You will not be able to run new jobs and running jobs may be terminated until you purchase additional compute minutes, or until the next month when you receive your monthly allotted compute minutes.
Q. Do compute minutes purchased during a trial roll into the paid subscription?
A. Purchased compute minutes will remain on a namespace after the trial completes and will be accessible until they run out.
Q. Will I be notified before I hit my limit on compute minutes?
A. You will receive notification banners in-app when your group has less than 30%, 5% or exceeded your total allotted compute minutes.
Percentage Remaining | Users Notified | Notification Type | Frequency |
30% | Owners | Banner | Permanent |
5% | Owners | Banner | Permanent |
0% | Owners | Banner | Permanent |
Q. Can I proactively monitor my compute minutes usage?
A. Yes, you can use the REST API on GitLab.com to monitor your compute minutes usage and integrate this into your standard monitoring tools. Here are a few examples for check plugins and Prometheus integrations:
Q. Are compute minutes used on users/customers' own runners accounted into the quota?
A. No. The compute minutes limit is for jobs using GitLab shared runners. Users/Customers can bring their own runners. compute minutes used on their own runners are not accounted into the limit.
Q. How much does it cost to buy additional compute minutes?
A. compute minutes per top-level group (or personal namespace) are $10 per 1,000 minutes and it is valid for one year from the date of purchase. compute minutes purchased do not auto-renew. Purchased minutes are only valid for 12 months from the date of purchase or until all minutes are consumed, whichever comes first.
Q. Will I have different compute minute pricing for Windows and Linux?
A. No. The pricing is the same regardless of the operating systems.
Q. How do I purchase additional compute minutes?
A. See Purchase additional compute minutes.
To upgrade to a paid GitLab.com Tier, purchase online or contact GitLab Sales
To address your questions and feedback, we have created a space in the GitLab Community Forum, which is actively monitored by GitLab Team members and Product Managers involved with this change.
When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
Cookie Policy
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, enabling you to securely log into the site, filling in forms, or using the customer checkout. GitLab processes any personal data collected through these cookies on the basis of our legitimate interest.
These cookies enable helpful but non-essential website functions that improve your website experience. By recognizing you when you return to our website, they may, for example, allow us to personalize our content for you or remember your preferences. If you do not allow these cookies then some or all of these services may not function properly. GitLab processes any personal data collected through these cookies on the basis of your consent
These cookies allow us and our third-party service providers to recognize and count the number of visitors on our websites and to see how visitors move around our websites when they are using it. This helps us improve our products and ensures that users can easily find what they need on our websites. These cookies usually generate aggregate statistics that are not associated with an individual. To the extent any personal data is collected through these cookies, GitLab processes that data on the basis of your consent.
These cookies enable different advertising related functions. They may allow us to record information about your visit to our websites, such as pages visited, links followed, and videos viewed so we can make our websites and the advertising displayed on it more relevant to your interests. They may be set through our website by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant advertisements on other websites. GitLab processes any personal data collected through these cookies on the basis of your consent.