Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Support

GitLab Support

GitLab offers a variety of support options for all customers and users, on both paid and free tiers. You should be able to find help using the resources linked below, regardless of how you use GitLab. There are many ways to contact Support, but the first step for most people should be to search our documentation.

If you can't find an answer to your question, or you are affected by an outage, then customers who are in a paid tier should start by looking at:

If you're using one of GitLab's free options, please jump to the support options for free tier users.

Note that free GitLab Ultimate and Gold accounts granted through our solutions for educational institutions or open source projects do not come with support (however, support for these can be bought for 95 percent off, at $4.95 per user per month).

Finally, the Support Team asks that you check what is outside the scope of support before you contact support.

Please understand that any support that might be offered beyond the scope defined here is done at the discretion of the agent or engineer and is provided as a courtesy.

Contact Support

Plan Self-managed (hosted on your own site/server)
Core GitLab Community Forum
Starter Standard Support
Reply within 24 hours 24x5
Premium and Ultimate Priority Support
Tiered reply times based on priority (details below)

Scope of Support for GitLab Self-managed Licenses (Starter, Premium, Ultimate)

Plan GitLab.com
Free GitLab Community Forum
Bronze Standard Support
Reply within 24 hours 24x5
Silver and Gold Priority Support
Tiered reply times based on priority (details below)

Scope of Support for GitLab.com Paid Subscriptions (Bronze, Silver, Gold)

Additional resources for getting help, reporting issues, requesting features, and so forth are listed on our get help page.

GitLab Support Service Levels

Standard Support

Standard Support is included with all GitLab self-managed Starter, and GitLab.com Bronze plans)

'Next business day support' means you can expect a reply to your ticket within 24 hours 24x5.

Please submit your support request through the support web form. When you receive your license file, you will also receive an email address to use if you need to reach Support and the web form can't be accessed for any reason.

Priority Support

Priority Support is included with all self-hosted GitLab Premium and Ultimate licenses, as well as GitLab.com Gold and Silver plans. This includes:

Support Impact SLA Hours How to Submit
Emergency 30 minutes 24x7 When you receive your license file, you will also receive a set of email addresses to use to reach Support for emergency requests
Highly Degraded 4 hrs 24x5 Please submit requests through the support web form or via the regular support email.
Medium Impact 8 hrs 24x5 Please submit requests through the support web form or via the regular support email.
Low Impact 24 hrs 24x5 Please submit requests through the support web form or via the regular support email.

Definitions of Support Impact

Upgrading to Priority Support

Priority Support is automatically included on GitLab.com Silver and Gold plans as well as self-managed Premium and Ultimate plans. If your organization would like to upgrade to a plan with Priority Support, you can purchase it yourself online, email your account manager, or email renewals@gitlab.com.

Service Level Agreement (SLA) details

Support for GitHost

Subscribers to GitHost receive next business day support via e-mail.

Please submit your support request through the support web form.

Free Tier Support Options

Self-managed (Core and Community Edition)

If you are seeking help with your GitLab Core or Community Edition installation, note that the GitLab Support Team is unable to directly assist with issues with specific installations of these versions. Please use the following resources instead:

Our community advocates also spend time on the Community Forum and Stack Overflow to help where they can, and escalate issues as needed.

GitLab.com Users (Free Plan)

Technical and general support for those using our free options is “Community First”. Like many other free SaaS products, users are first directed to find support in community sources such as our own Community Forum, Stackoverflow, Google, etc. You can also follow GitLabStatus on Twitter for status updates for the GitLab.com site, or check https://status.gitlab.com/ to see if there is a known service outage.

The GitLab team does offer support for:

For help with these issues please open a support request. For free GitLab.com users seeking support, a support agent or engineer may determine that the request is more appropriate for community forums or the issue tracker than for the official GitLab Support Team.

Note that issues affecting paid users receive a higher priority. There are no SLAs or guaranteed response times associated with free accounts.

GitLab.com Specific Support Policies

Account Recovery

If you have lost access to your account, perhaps due to having lost access to your 2FA device or the original email address that the account was set up with, the account may be recovered provided the claimant can provide sufficient evidence of account ownership. Use the support web form to request assitance.

Please note that in some cases reclaiming an account may be impossible. Read "How to keep your GitLab account safe" for advice on preventing this.

Dormant Namespace Requests

The GitLab.com Support Team will consider a namespace to be "dormant" when the user has not logged in or otherwise used the namespace for an extended time.

User namespaces can be reassigned if both of the following are true:

  1. The user's last sign in was at least two years ago.
  2. The user is not the sole owner of any active projects.

Group namespaces can be reassigned if one of the following are true:

  1. There is no data (no project or project(s) are empty).
  2. The owner's last sign in was at least two years ago.

If the namespace contains data, GitLab Support will attempt to contact the owner over a two week period before reassigning the namespaces. If the namespace contains no data (empty or no projects) and the owner is inactive, the dormant namespaces will be released immediately.

Namespaces associated with unconfirmed accounts over 90 days old will also be released immediately.

Outside of the Scope of Support for all Tiers

Git

  1. git specific commands and issues (not related to GitLab)

CI/CD

  1. Helping debug specific commands or scripts in a .gitlab-ci.yml
  2. Issues other than configuration or setup of private runner hosts

General Support Practices

Issue Creation

When bugs, regressions, or any application behaviors/actions not working as intended are reported or discovered during support interactions, the GitLab Support Team will create issues in GitLab project repos on behalf of our customers.

For feature requests, both involving addition of new features as well as change of features currently working as intended, GitLab support will request that the customer create the issue on their own in the appropriate project repos.

Closing Tickets

If a customer explains that they are satisfied their concern is being addressed properly in an issue created on their behalf, then the conversation should continue within the issue itself, and GitLab support will close the support ticket. Should a customer wish to reopen a support ticket, they can simply reply to it and it will automatically be reopened.

Further resources

Additional resources for getting help, reporting issues, requesting features, and so forth are listed on our get help page.