Statement of Support

Starter (Legacy), Premium, and Ultimate Customers

We will help troubleshoot all components bundled with GitLab Omnibus when used as a packaged part of a GitLab installation. Any assistance with modifications to GitLab, including new functionality, bug-fixes, issues with experiment features or other code changes should go through the GitLab project's issue tracker. Moreover, support is not offered for local modifications to GitLab source code.

We understand that GitLab is often used in complex environments in combination with a variety of tools. We'll use commercially-reasonable efforts to debug components that work alongside GitLab.

If you obtained an Ultimate license as part of GitLab's Open Source or Education program, support is not included. Please see the GitLab OSS License/Subscription Details for additional details.

Version Support

Unless otherwise specified in your support contract, we support the current major version and previous two major versions only. For example, as 17.x is the current major version, GitLab installations running versions in the 17.x, 16.x and 15.x series are eligible for support.

GitLab only backports fixes, not features and that too on a limited number of prior releases. For more details please visit the maintenance policy.

If you contact support about issues you're experiencing while on an unsupported version, we'll link to this section of this page and invite you to upgrade.

Installation & New Features

For assistance with first-time installations and the configuration of new features, we highly recommend using our comprehensive documentation:

• First-time installation step by step guide
• Updating your GitLab instance
• High availability
• Kubernetes clusters

Please make sure to use the matching version of our documentation for the version of GitLab you plan to install. Our Docs archives site explains how to access older versions.

Alternatively, you can reach out to our Professional Services team who provide training and assistance with the design and implementation of new features and installations.

If you're facing challenges after attempting the installation of a new deployment or implementing new features, a support ticket can be opened using our support portal.

Free and Community Edition Users

If you are seeking help with your GitLab Free 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:

• GitLab Documentation: Extensive documentation regarding the possible configurations of GitLab.

• GitLab Community Forum: This is the best place to have a discussion about your Community Edition configuration and options.

• Stack Overflow: Please search for similar issues before posting your own, as there's a good chance somebody else had the same issue as you and has already found a solution.

Bronze (Legacy), Premium, and Ultimate Customers

GitLab.com has a full team of Site Reliability Engineers and Production Engineers monitoring its status 24/7. This means that often, by the time you notice something is amiss, there's someone already looking into it.

We recommend that all GitLab.com customers follow @gitlabstatus on Twitter and use our status page to keep informed of any incidents.

If you obtained an Ultimate license as part of GitLab's Open Source or Education program, support is not included. Please see the GitLab OSS License/Subscription Details for additional details.

Free Users

Technical and general support for those using the Free version of GitLab.com is “Community First”. Like many other free SaaS products, users are first directed to find support through community sources such as the following:

• GitLab Documentation: Extensive documentation on anything and everything GitLab.
• GitLab Community Forum: Get help directly from the community. When able, GitLab employees also participate and assist in answering questions.
• Stack Overflow: Please search for similar issues before posting your own, as there's a good chance someone else had the same issue as you and has already found a solution.

However, GitLab Support will assist Free users with the following types of issues:

• Your account or repository is in an unusable state. For example, you're unable to log in to your account or access a repository without receiving an error that you cannot bypass. Please note though that Account Recovery and 2FA Resets support is not available for Free users.

• Requests related to an email you received regarding a GitLab.com security or production incident.

To receive help for these types of issues please contact support, and be aware that if a Support Engineer determines that your request is more appropriate for community resources they will direct you to them. Please also note that there are no guaranteed response times associated with support tickets submitted by Free users.

Buying a subscription mid-ticket

Once a ticket is filed, the customer's current plan is used for the ticket. If you purchase a subscription during the life of a ticket, file a new ticket in order to have the updated service reflected properly in the support portal and in the execution of support.

Note: Purchasing a plan to circumvent restricted support features (such as 2FA resets or name-squatting requests) is prohibited. We do not encourage you to do this as the service requested is still likely to be denied.

GitLab.com Availability

You should follow @gitlabstatus on Twitter for status updates on GitLab.com, or check our status page to see if there is a known service outage and follow the linked issue for more detailed updates.

This section describes our approach to supporting GitLab Dedicated customers.

Access to GitLab Dedicated Tenant

The GitLab Support team does not have access to the GitLab application running on GitLab Dedicated tenants. In order to work effectively with Support, customers will need to share information from the GitLab application in support tickets.

If you encounter usability or performance issues while using GitLab Duo Pro features, we encourage you to submit a support ticket as we are committed to providing comprehensive support in line with the status of the specific features as covered in our Statement of Support for Experiment and Beta Features. For a comprehensive list of GitLab Duo features and their current status, please see the GitLab Duo documentation.

Please note that our Scope of Support does not cover the accuracy of, nor the responses generated by GitLab Duo Pro. If you would like to provide feedback on the accuracy of the data or responses generated, please refer to the "Feedback" section of the feature-specific documentation linked from the GitLab Duo documentation in the Statement of Support.

The following sections outline what is within the scope of support and what is not for GitLab Self-Managed customers, GitLab.com customers, and both customers and Free users of either.

GitLab Self-Managed Customers

Out of Scope	Example	What's in-scope then?
Debugging EFS problems	GitLab is slow in my HA setup. I'm using EFS.	EFS and GlusterFS are not recommended for HA setups (see our HA on AWS doc). GitLab Support can help verify that your HA setup is working as intended, but will not be able to investigate EFS or GlusterFS backend storage issues.
Debugging git repository issues stored on NFS	Commits vanished from our main branch. We're running 3 Gitaly servers, sharing data using NFS.	NFS cannot be used for repository storage
Troubleshooting non-GitLab Omnibus components	I'm trying to get GitLab to work with Apache, can you provide some pointers?	GitLab Support will only assist with the specific components and versions that ship with the GitLab Omnibus package, and only when used as a part of a GitLab installation.
Local modifications to GitLab	We added a button to ring a bell in our office any time an MR was accepted, but now users can't log in.	GitLab Support would direct you to create a feature request or submit a merge request for code review to incorporate your changes into the GitLab core.
Old versions of GitLab	I'm running GitLab 7.0 and X is broken.	GitLab Support will invite you to upgrade your installation to a more current release. Only the current and two previous major versions are supported.
Instance migration configuration and troubleshooting	We migrated GitLab to a new instance and cannot SSH into the server.	GitLab Support will assist with issues that arise from the GitLab components. GitLab Support will not be able to assist with any issues stemming from the server or its configuration (see GitLab Instance Migration on the Support page).
Debugging custom scripts and automations	We use custom scripts to automate changes to our GitLab deployment, and it is causing problems or downtime. Please create a custom script for me to leverage the GitLab API.	GitLab Support will assist in troubleshooting and resolving issues that occur in the course of interacting with an existing GitLab installation. GitLab Support will not be able to assist with debugging or fixing customer-written code used to deploy, upgrade or modify an in-place installation, or with creating custom scripts to use GitLab components.
Installation of GitLab using unofficial, community-contributed methods	We ran into an error installing GitLab using the FreeBSD package. Please help!	GitLab Support can only provide support for installation problems encountered when using an official installation method.
Upgrade Assistance for GitLab installed using unofficial, community-contributed methods	We installed GitLab using the Arch Linux community package and would like to request upgrade assistance	GitLab Support can only provide Upgrade Assistance when GitLab is installed using an official installation method.
Step-by-step instructions for upgrading GitLab on self-hosted infrastructure	We installed one of the HA reference architectures and need to know how and in which order to update the specific nodes	GitLab documentation describes the parts of a system that need to be upgraded, and describes certain dependencies. Because so many configurations are possible, we do not attempt to document all of them. We do provide support for the GitLab components of your setup, and can provide Upgrade Assistance, including a review of your upgrade plan.
Running raw SQL queries that modify the GitLab database	We used a mass update query in the GitLab database to change all of our usernames, and we are now experiencing issues as a result of that change.	GitLab Support will direct you to roll back to a known working backup, and then assist with debugging and resolving the problem via a safer method.

GitLab.com Customers

Out of Scope	Example(s)	What's in-scope then?
Troubleshooting non-GitLab components	How do I use git via CLI? How do I use a third party's IDE?	GitLab Support will happily answer any questions and help troubleshoot any of the components of GitLab
Consulting on language or environment-specific configuration	I want to set up a YAML linter CI task for my project. How do I do that?	The Support Team will help you find the GitLab documentation for the related feature and can point out common pitfalls when using it.

Training

GitLab Support is unable to provide training on the use of the underlying technologies that GitLab relies upon. GitLab is a product aimed at technical users, and we expect our users and customers to be versed in the basic usage of the technologies related to features that they're seeking support for.

For example, a customer looking for help with a Kubernetes integration should understand Kubernetes to the extent that they could retrieve log files or perform other basic tasks without in-depth instruction.

Git and LFS

We're unable to assist in troubleshooting issues with specific Git commands and cannot provide training for using Git. If the latter is needed, official Git documentation is comprehensive. The same applies to Git Large File Storage. For both topics, GitLab-relevant aspects are collected in our summary documentation.

CI/CD

GitLab Support cannot implement specific CI/CD solutions for you.
For example:

• In Scope: I implemented a CI/CD configuration to run tests on all my branches, but it doesn't work as I expected it to based on the documentation.

• Out of Scope: I need a CI/CD configuration that runs tests on all my branches.

GitLab Support cannot assist with debugging specific commands or scripts included in your .gitlab-ci.yml file. We also cannot troubleshoot issues outside of the configuration or setup of private GitLab Runner host machines.

For example:

• In Scope: I'm including a custom script in my .gitlab-ci.yml file, but it appears that GitLab does not actually execute it.
• Out of Scope: I'm including a custom script in my .gitlab-ci.yml file and can't get the script to work on my new GitLab Runner which uses a different Linux version than my existing GitLab Runners.

CI/CD Templates

GitLab provides a range of CI/CD templates that can be included in your pipeline. Some of these templates enable features like Secret Detection, Code Quality analysis and Static Application Security Testing while other templates are examples designed to demonstrate functionality like Load Performance Testing or Accessibility testing. GitLab Support will assist with documented customizations of these templates. Assistance with direct modifications to these templates or non-documented customizations is out of scope for GitLab Support. We welcome merge requests to improve the functionality of these templates.

For example:

• In Scope: I want to customize the settings so that SECRET_DETECTION_HISTORIC_SCAN is true.

• Out of Scope: I copied Security/License-Scanning.gitlab-ci.yml into my repository and am trying to modify it.

Third Party Applications & Integrations

GitLab Support cannot assist with the configuration or troubleshooting of third party applications, integrations, and services that may interact with GitLab. We can ensure that GitLab itself is sending properly formatted data to a third party in the bare-minimum configuration.
For example:

• "I can't get Jenkins to run builds kicked off by GitLab. Please help me figure out what is going on with my Jenkins server."

Publicly available internal Tooling

We provide most of our internal tooling publicly. Examples are the Congregate tool that Professional Services uses for migrations and the gitlab-triage gem that can automatically triage issues and merge requests. While you're free to use these tools to your benefit, GitLab Support cannot assist you with them. Please use the appropriate issue trackers or documented processes if you encounter problems.

Basic reporting or data analysis

Support engineers are not data analysts, so any data analysis request should be in pursuit of understanding and solving a problem. GitLab Support can not assist with extracting very basic or differently purposed insights from instance databases or repositories or log files.

For customer self-service, we collect useful examples of data extraction from repositories, log files, and share our various internal tools.

For example:

• In Scope: I've analyzed our GitLab logs and found these errors. How should we resolve them?
• In Scope: I've started a docs-comment issue/MR about querying these specific details: ...
  Can we collaborate to document a recommended example?
• Out of Scope: Our monitoring shows a ... spike. Please search through our logs to find what caused the spike.

Configuration of Deployment Environments

GitLab Support cannot assist with infrastructure, in terms of the creation, configuration, or maintenance of on-premises, cloud, or infrastructure-as-code environments beyond the general guidance from what is provided in our documentation. This includes, but is not limited to, the configuration of firewalls, private networks, virtual machines, and secrets.

Creation of SSL/TLS Certificates

GitLab Support cannot assist with the creation of SSL/TLS certificates, certificate signing requests, or the creation of certificate authorities.

Experiment Features

Experiment features are not yet completely tested for quality and stability, may contain bugs or errors, and prone to see breaking changes in the future. As such, support is not provided for these features and issues with them or other code changes should be opened in the GitLab issue tracker.

Beta Features

Your Support Contract will cover support for Beta features. However, because they are not yet completely tested for quality and stability, may contain bugs or errors, and may be prone to see breaking changes in the future, troubleshooting will require more time, usually need assistance from Development, that support will be conducted on a commercially-reasonable effort basis.