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

Product Stage Direction - Ecosystem

Content last reviewed on 2022-01-14

Stage Overview

Ecosystem focus is on fostering GitLab as a platform. Ecosystem supports our Integrations with other products and Foundations functionality to enable our community of contributors to develop the application itself.

Ecosystem's goal is to make integrating with, extending the functionality of, or contributing to GitLab accessible to all of our users. We strongly believe that Everyone can contribute, and Ecosystem supports this value directly through its work.


The Ecosystem Stage is made up of two groups supporting the major areas of work, including:

3 Year Stage Themes

Freedom of choice

We firmly believe that a single application can successfully serve all the needs of the entire DevOps lifecycle. However, there are myriad reasons that many customers can't adopt GitLab in this way.

Customers may have specific tools they are committed to using for reasons such as:

  1. The cost of migrating off of it, either based on the volume of content to migrate, the risk of errors during the migration, the cost of training, etc.
  2. The cost of building new integrations with other tools in their existing toolchain
  3. Specific regulatory, security, or compliance needs they must be able to meet
  4. Niche or unique functionality that isn't available in GitLab

Because of these realities, we believe that our customers should have the freedom to choose their tools, and use what makes the most sense for their business—and we will support that freedom as best we can by playing well with others.

As examples, GitLab will provide:

Everyone Can Contribute

GitLab's Mission is that everyone can contribute, and Ecosystem supports that in the context of GitLab itself. To accelerate GitLab's growth as a project, and as part of our commitment to our community, it's vital that we ensure that contribution is possible by anyone.

GitLab's community is a large part of how we've gotten as far as we have today, and we'd like to make it even simpler for those contributors to get involved. By improving this experience, we invite more new community members, including current users, to get involved and improve the application. "Everyone can contribute" means that everyone has the opportunity to add features, fix bugs, and improve the experience of the application. While it's sometimes possible for users to fix problems locally, when we make it easy for these contributions to make it upstream in to the project, these improvements can be enjoyed by everyone.

As examples, GitLab will provide:

3 Year Strategy

In three years, the Ecosystem Stage will:

As a result, in three years, GitLab will:

1 Year Plan

What we have recently completed

What we are currently working on

The Ecosystem team is actively working on

What's next for us

To meet our audacious goals, the Ecosystem Stage will focus on the following over the next 12 months:

What we're not doing


Ecosystem's contribution to our company-level financial goals are driven by offering more complex integrations capabilities for larger organizations that need to closely knit 3rd party tools with GitLab.

We think about integrated functionality through the lens of the Buyer Based Tiering model, but with some integrations-specific considerations:

  1. Free integrations benefit a single developer, offering navigation and lightweight functionality (such as event notifications) between GitLab and a 3rd party system.
  2. Premium integrations benefit teams that require the integration for team cohesion, and may bring more complex functionality (such as issue management of a 3rd party system) inside of GitLab.
  3. Ultimate integrations enforce 3rd party integration workflows for large organizations which may override native GitLab functionality

Additionally, any functionality that is designed expressly to allow 3rd party systems to connect to GitLab (such as our APIs) will be offered for free. We will only monetize integration features that are available inside the GitLab application itself, whereas these types of resources are for 3rd party systems to leverage outside of the GitLab application.

Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license