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

Partner with GitLab

On this page

Collaborate and Integrate with GitLab

GitLab is open to collaboration and committed to building technology partnerships in the DevOps ecosystem to enable customer success. We are open to adding new integrations to our technology partners page in a self-service way.

We support integrations through our APIs or direct additions to our product, and we encourage integration partners to make and maintain those integration with us. The work required to deliver the integration will be provided by the partner.

If you want to talk to us about a partnership you can contact the Alliances team or open a new issue.

Requirements to become an Ecosystem partner

The requirements to be listed on our Technology Partners page include:

See current examples on our partner listing page.

Note: As we further develop our engagement with ecosystem partners, we also reserve the right to promote specific best practices to integrate with GitLab across our product's DevOps stages. To keep consistency and retain value to the UX within GitLab with external integration, GitLab may document details that give guidance on how specific types of integrations are expected to interoperate with GitLab.

Companies that are interested in becoming an ecosystem partner, and have the above requirements ready, they should follow the steps below for getting listed on our Partners page.

Prerequisites for Security Partners

If you want to integrate with the Secure Stage (which is integrated with the GitLab CI/CD Section), we have specific recommendations and requirements prior to any joint GTM activities and getting listed on our Partner Page. Below is an overview on best practices when integrating with GitLab for a consistent UX for our end users that are leveraging external security scanners with GitLab SCM and CI/CD. For a working example on the desired workflow, refer to Whitesource's integration with GitLab. At a high level, we encourage integrations to:

  1. Follow our Secure Partner Integration - Onboarding process (Link coming soon!)
  2. Provide checks prior to merging an MR if vunerabilities are found.
  3. Populate GitLab's security dashboard for a consistent UX.
  4. Provide outputs in artifacts that can be ingest by GitLab according to our documentation, particularly for SAST related outputs.

Below are links to our Documentation that go into further details on how to integrate security products with GitLab.

Steps to getting listed on our Partner page

Step 1: Submit a new partner issue

If you are interested in partnering with GitLab and have completed an integration with us, please start by submitting a New Partner issue. When creating an issue, please select new_partner issue template in the drop down.

The Alliances team manages new partner requests and will review the issue. Generally, you will receive a response from GitLab within two weeks of submitting a new partner issue. This will either be an update on the status or a request for additional information. If you have any questions about the status of your issue, please reach out to for support.

Step 2: Adding your app to the Partners page

The next step is to get your app listed. Partners with technology integrations are asked to submit a Merge Request to add themselves to the GitLab Technology Partners page. Follow these instructions on how to get your app listed.

Step 3: The Alliance team will review your information

Once the Merge Request has been created, the Alliances team will be notified and will review the information. If the requirements are met and ready for approval, the Alliances team will approve the MR to get your app listed on our website.

Step 4: Self-service GTM opportunities

We love spreading the word on new integrations with GitLab to our community and followers. We help promote ecosystem partners that have an integration or feature with us.

Note: This does require identifying a mutual customer or proof point ahead of time.

Brand Awareness

Marketing and External Communications

Joint Opportunities

Contact Us

We are here to help. The Alliance team works from issues and issue boards. If you are needing our assistance with any project, please open an issue and we’ll get back to you as soon as we can! When creating an issue, please select New_Partner issue template in the drop down. If it’s technical assistance you’re looking for, please see below for troubleshooting.


We're always here to help you through your efforts of integration. If there's a missing API call from our current API, or you ran into other difficulties in your development please feel free to create a new issue on the Community Edition issue tracker and apply the Ecosystem label. Gold Subscription Sandbox Request and GitLab EE share the same core code base. If you’re looking to quickly test and integrate with GitLab, often a project on can be the quickest way to get started. We’re happy to provision you a private sandbox subgroup in our Alliances Group where you can create projects for demo, R&D, and testing purposes. To make the project/sandbox public to share with external parties outside of GitLab and Partner, we request you first complete the file in your Public Project Repository. Here is an example. Also, it’s highly recommended to maintain a demo project as well for interested external parties.

Requesting EE Dev License for R&D

We are able to issue Ultimate licenses for integration testing and development upon request. These licenses are only open to those working on a GitLab Enterprise Edition specific integration. Licenses will be issued for 6 months and for up to 10 users. Please add it as a comment in the following issue template.