| stage | group | info | type |
|---|---|---|---|
Fulfillment |
Purchase |
To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments |
index, reference |
GitLab SaaS is the GitLab software-as-a-service offering, which is available at GitLab.com. You don't need to install anything to use GitLab SaaS, you only need to sign up. When you sign up, you choose:
The subscription determines which features are available for your private projects. Organizations with public open source projects can actively apply to our GitLab for Open Source Program.
Qualifying open source projects also get 50,000 compute minutes and free access to the Ultimate tier through the GitLab for Open Source program.
A GitLab SaaS subscription applies to a top-level group. Members of every subgroup and project in the group:
- Can use the features of the subscription.
- Consume seats in the subscription.
To subscribe to GitLab SaaS:
- View the GitLab SaaS feature comparison and decide which tier you want.
- Create a user account for yourself by using the sign up page.
- Create a group. Your subscription tier applies to the top-level group, its subgroups, and projects.
- Create additional users and add them to the group. The users in this group, its subgroups, and projects can use the features of your subscription tier, and they consume a seat in your subscription.
- On the left sidebar, select Settings > Billing and choose a tier.
- Fill out the form to complete your purchase.
Prerequisite:
- You must have the Owner role for the group.
To see the status of your GitLab SaaS subscription:
- On the left sidebar, at the top, select Search GitLab ({search}) to find your group.
- Select Settings > Billing.
The following information is displayed:
| Field | Description |
|---|---|
| Seats in subscription | If this is a paid plan, represents the number of seats you've bought for this group. |
| Seats currently in use | Number of seats in use. Select See usage to see a list of the users using these seats. |
| Max seats used | Highest number of seats you've used. |
| Seats owed | Max seats used minus Seats in subscription. |
| Subscription start date | Date your subscription started. If this is for a Free plan, it's the date you transitioned off your group's paid plan. |
| Subscription end date | Date your current subscription ends. Does not apply to Free plans. |
- Introduced in GitLab 13.5.
- Updated in GitLab 13.8 to include public email address.
A GitLab SaaS subscription uses a concurrent (seat) model. You pay for a subscription according to the maximum number of users assigned to the top-level group or its children during the billing period. You can add and remove users during the subscription period without incurring additional charges, as long as the total users at any given time doesn't exceed the subscription count. If the total users exceeds your subscription count, you will incur an overage which must be paid at your next reconciliation.
A top-level group can be changed like any other group.
Every user is included in seat usage, with the following exceptions:
- Users who are pending approval.
- Members with the Guest role on an Ultimate subscription.
- GitLab-created service accounts:
- Ghost User.
- Bots such as:
Seat usage is reviewed quarterly or annually.
If a user navigates to a different top-level group (one they have created themselves, for example) and that group does not have a paid subscription, they would not see any of the paid features.
It is also possible for users to belong to two different top-level groups with different subscriptions. In this case, they would see only the features available to that subscription.
To view a list of seats being used:
- On the left sidebar, at the top, select Search GitLab ({search}) to find your group.
- Select Settings > Usage Quotas.
- On the Seats tab, view usage information.
For each user, a list shows groups and projects where the user is a direct member.
- Group invite indicates the user is a member of a group shared with a group.
- Project invite indicates the user is a member of a group shared with a project.
The data in seat usage listing, Seats in use, and Seats in subscription are updated live. The counts for Max seats used and Seats owed are updated once per day.
To view your subscription information and a summary of seat counts:
- On the left sidebar, at the top, select Search GitLab ({search}) to find your group.
- Select Settings > Billing.
The usage statistics are updated once per day, which may cause a difference between the information in the Usage Quotas page and the Billing page.
Introduced in GitLab 13.8.
To search users in the Seat usage page, enter a string in the search field. A minimum of 3 characters are required.
The search returns those users whose first name, last name, or username contain the search string.
For example:
| First name | Search string | Match ? |
|---|---|---|
| Amir | ami |
Yes |
| Amir | amr |
No |
Introduced in GitLab 14.2.
To export seat usage data as a CSV file:
- On the left sidebar, at the top, select Search GitLab ({search}) to find your group.
- Select Settings > Billing.
- Under Seats currently in use, select See usage.
- Select Export list.
The generated list contains all seats being used, and is not affected by the current search.
A GitLab subscription is valid for a specific number of users.
If the number of billable users exceeds the number included in the subscription, known as the number of seats owed, you must pay for the excess number of users.
For example, if you purchase a subscription for 10 users:
| Event | Billable members | Maximum users |
|---|---|---|
| Ten users occupy all 10 seats. | 10 | 10 |
| Two new users join. | 12 | 12 |
| Three users leave and their accounts are removed. | 9 | 12 |
Seats owed = 12 - 10 (Maximum users - users in subscription)
In the Ultimate tier, users who are assigned the Guest role do not consume a seat. The user must not be assigned any other role, anywhere in the instance or in the namespace for GitLab SaaS.
- If your project is private or internal, a user with the Guest role has a set of permissions.
- If your project is public, all users, including those with the Guest role can access your project.
Your subscription cost is based on the maximum number of seats you use during the billing period. Even if you reach the number of seats in your subscription, you can continue to add users. GitLab bills you for the overage.
To add seats to a subscription:
- Log in to the Customers Portal.
- Navigate to the Manage Purchases page.
- Select Add more seats on the relevant subscription card.
- Enter the number of additional users.
- Select Proceed to checkout.
- Review the Subscription Upgrade Detail. The system lists the total price for all users on the system and a credit for what you've already paid. You are only be charged for the net change.
- Select Confirm Upgrade.
The following is emailed to you:
- A payment receipt. You can also access this information in the Customers Portal under View invoices.
To remove a billable user from your subscription:
- On the left sidebar, at the top, select Search GitLab ({search}) to find your group.
- Select Settings > Billing.
- In the Seats currently in use section, select See usage.
- In the row for the user you want to remove, on the right side, select the ellipsis and Remove user.
- Re-type the username and select Remove user.
If you add a member to a group by using the share a group with another group feature, you can't remove the member by using this method. Instead, you can either:
- Remove the member from the shared group. You must be a group owner to do this.
- From the group's membership page, remove access from the entire shared group.
- Introduced in GitLab 15.2 with a flag named
seat_flag_alerts.- Generally available in GitLab 15.4. Feature flag
seat_flag_alertsremoved.
If you have the Owner role of the top-level group, an alert notifies you of your total seat usage.
The alert displays on group, subgroup, and project pages, and only for top-level groups linked to subscriptions enrolled in quarterly subscription reconciliations. After you dismiss the alert, it doesn't display until another seat is used.
The alert displays based on the following seat usage. You cannot configure the amounts at which the alert displays.
| Seats in subscription | Seat usage |
|---|---|
| 0-15 | One seat remaining in the subscription. |
| 16-25 | Two seats remaining in the subscription. |
| 26-99 | 10% of seats have been used. |
| 100-999 | 8% of seats have been used. |
| 1000+ | 5% of seats have been used |
To change the namespace linked to a subscription:
-
Log in to the Customers Portal with a linked GitLab.com account.
-
Go to the Manage Purchases page.
-
Select Change linked namespace.
-
Select the desired group from the New Namespace dropdown list. For a group to appear here, you must have the Owner role for that group.
-
If the total number of users in your group exceeds the number of seats in your subscription, you are prompted to pay for the additional users. Subscription charges are calculated based on the total number of users in a group, including its subgroups and nested projects.
If you purchased your subscription through an authorized reseller, you are unable to pay for additional users. You can either:
- Remove additional users, so that no overage is detected.
- Contact the partner to purchase additional seats now or at the end of your subscription term.
-
Select Confirm changes.
For a demo, see Linking GitLab Subscription to the Namespace.
Only one namespace can be linked to a subscription.
To upgrade your GitLab tier:
- Log in to the Customers Portal.
- Select Upgrade on the relevant subscription card on the Manage purchases page.
- Select the desired upgrade.
- Confirm the active form of payment, or add a new form of payment.
- Check the I accept the Privacy Policy and Terms of Service checkbox.
- Select Confirm purchase.
When the purchase has been processed, you receive confirmation of your new subscription tier.
When your subscription expires, you can continue to use paid features of GitLab for 14 days. On the 15th day, paid features are no longer available. You can continue to use free features.
To resume paid feature functionality, purchase a new subscription.
To renew your subscription:
Before you renew your subscription:
- Log in to the Customers Portal.
- On the Account details page, verify or update the invoice contact details.
- On the Payment Methods page, verify or update the credit card on file.
- In GitLab, review your list of user accounts and remove inactive or unwanted users.
Starting 30 days before a subscription expires, GitLab notifies group owners of the date of expiry with a banner in the GitLab user interface.
To renew your subscription:
- Log in to the Customers Portal and beneath your existing subscription, select Renew. The Renew button remains disabled (grayed-out) until 15 days before a subscription expires. You can hover your mouse on the Renew button to see the date when it becomes active.
- Review your renewal details and complete the payment process.
- Select Confirm purchase.
Your updated subscription is applied to your namespace on the renewal period start date. It may take up to one day for the renewal to be processed.
An invoice is generated for the renewal and available for viewing or download on the View invoices page. If you have difficulty during the renewal process, contact the Support team for assistance.
For details on upgrading your subscription tier, see Upgrade your GitLab SaaS subscription tier.
When a subscription is set to auto-renew, it renews automatically on the expiration date without a gap in available service. Subscriptions purchased through Customers Portal or GitLab.com are set to auto-renew by default. The number of seats is adjusted to fit the number of billable users in your group at the time of renewal. You can view and download your renewal invoice on the Customers Portal View invoices page. If your account has a saved credit card, the card is charged for the invoice amount. If we are unable to process a payment or the auto-renewal fails for any other reason, you have 14 days to renew your subscription, after which your access is downgraded.
15 days before a subscription automatically renews, an email is sent with information about the renewal.
- If your credit card is expired, the email tells you how to update it.
- If you have any outstanding overages, the email tells you to contact our Sales team.
- If there are no issues, the email specifies the names and quantity of the products being renewed. The email also includes the total amount you owe. If your usage increases or decreases before renewal, this amount can change.
To view or change automatic subscription renewal (at the same tier as the previous period), sign in to the Customers Portal, and:
- If a Turn on auto-renew button is displayed, your subscription was canceled previously. Select it to resume automatic renewal.
- If a Cancel subscription button is displayed, your subscription is set to automatically renew at the end of the subscription period. Select it to cancel automatic renewal.
If you have difficulty during the renewal process, contact the Support team for assistance.
Contacts can renew a subscription, cancel a subscription, or transfer the subscription to a different namespace.
For information about how to transfer ownership of the Customers Portal account to another person, see Change account owner information.
To add a secondary contact for your subscription:
- Ensure an account exists in the Customers Portal for the user you want to add.
- Create a ticket with the Support team. Include any relevant material in your request.
Compute is the resource consumed when running pipelines on GitLab shared runners.
Refer to Compute usage for more information.
You can purchase additional compute minutes for your personal or group namespace. Compute minutes are a one-time purchase, so they do not renew.
NOTE: Free namespaces are subject to a 5 GB storage and 10 GB transfer soft limit. Once all storage is available to view in the usage quota workflow, GitLab will automatically enforce the namespace storage limit and the project limit is removed. This change is announced separately. The storage and transfer add-on can be purchased to increase the limits.
Projects have a free storage quota of 10 GB. To exceed this quota you must first purchase one or more storage subscription units. Each unit provides 10 GB of additional storage per namespace. A storage subscription is renewed annually. For more details, see Usage Quotas.
When the amount of purchased storage reaches zero, all projects over the free storage quota are locked. Projects can only be unlocked by purchasing more storage subscription units.
Prerequisite:
- You must have the Owner role.
You can purchase a storage subscription for your personal or group namespace.
NOTE: Storage subscriptions renew automatically each year. You can cancel the subscription to disable the automatic renewal.
- Sign in to GitLab SaaS.
- From either your personal homepage or the group's page, go to Settings > Usage Quotas.
- For each locked project, total by how much its Usage exceeds the free quota and purchased storage. You must purchase the storage increment that exceeds this total.
- Select Purchase more storage and you are taken to the Customers Portal.
- Select Add new subscription.
- Scroll to Purchase add-on subscriptions and select Buy storage subscription.
- In the Subscription details section select the name of the user or group from the dropdown list.
- Enter the desired quantity of storage packs.
- In the Billing information section select the payment method from the dropdown list.
- Select the Privacy Policy and Terms of Service checkbox.
- Select Buy subscription.
- Sign out of the Customers Portal.
- Switch back to the GitLab SaaS tab and refresh the page.
The Purchased storage available total is incremented by the amount purchased. All locked projects are unlocked and their excess usage is deducted from the additional storage.
Introduced in GitLab 14.6.
If you're using GitLab SaaS, you can purchase additional storage so your pipelines aren't blocked after you have used all your storage from your main quota. You can find pricing for additional storage on the GitLab Pricing page.
To purchase additional storage for your group on GitLab SaaS:
- On the left sidebar, at the top, select Search GitLab ({search}) to find your group.
- Select Settings > Usage Quotas.
- Select Storage tab.
- Select Purchase more storage.
- Complete the details.
After your payment is processed, the extra storage is available for your group namespace.
To confirm the available storage, go to your group, and then select Settings > Usage Quotas and select the Storage tab.
The Purchased storage available total is incremented by the amount purchased. All locked projects are unlocked and their excess usage is deducted from the additional storage.
Learn more about:
- The tiers of GitLab Support.
- Submit a request via the Support Portal.
We also encourage you to search our project trackers for known issues and existing feature requests in the GitLab project.
These issues are the best avenue for getting updates on specific product plans and for communicating directly with the relevant GitLab team members.
If your credit card is declined when purchasing a GitLab subscription, possible reasons include:
- The credit card details provided are incorrect. The most common cause for this is an incomplete or fake address.
- The credit card account has insufficient funds.
- You are using a virtual credit card and it has insufficient funds, or has expired.
- The transaction exceeds the credit limit.
- The transaction exceeds the credit card's maximum transaction amount.
Check with your financial institution to confirm if any of these reasons apply. If they don't apply, contact GitLab Support.
If you cannot link a subscription to your namespace, ensure that you have the Owner role for that namespace.