About Us

GitLab Inc.

GitLab Inc. is the company behind the GitLab open-source project which is hosted on GitLab.com (our free hosted service). GitLab is a Rails application providing Git repository management with fine grained access controls, code reviews, issue tracking, activity feeds, wikis and continuous integration. GitLab Inc. has 4 offerings, 3 of which are free:

  1. GitLab.com - free SaaS for public and private repositories, support can be purchased
  2. GitLab Community Edition (CE) - free, self hosted application, support from Community
  3. GitLab Enterprise Edition (EE) - paid, self hosted application, comes with additional features and support
  4. GitLab Continuous Integration (CI) - free, self hosted application that integrates with GitLab CE/EE. Also available as SaaS at ci.gitlab.com

GitLab Inc. also offers:

  1. Git and GitLab Training
  2. Consulting
  3. Custom Development work

ReleaseTEAM is a reseller partner of GitLab in the US.

GitLab Inc. supports organizations and individuals using GitLab. To do this we offer services around GitLab such as subscriptions, consulting, development and training.

Above all, GitLab is a community project, over 1000 people worldwide have contributed to GitLab! GitLab Inc. is an active participant in this community, trying to serve its needs and lead by example.

A brief history of GitLab

2011: Start of GitLab

In 2011 Dmitriy was unsatisfied with the options for git repository management. So together with Valery, he started to build GitLab as a solution for this.

This commit was the very start of GitLab.

2012: GitLab.com

Sytse began a SaaS of GitLab, which until then was only an open source project that could be ran on your own servers. GitLab.com offered free and paid hosting of git projects to anyone.

In November 2012, Dmitriy also made the first version of GitLab CI.

2013: “I want to work on GitLab full time”

In 2013, Dmitriy tweeted that he wanted to work on GitLab full time. Sytse and Dmitriy teamed up and started bootstrapping GitLab as a company.

In the same year in August, we introduced GitLab Enterprise Edition.

2014: GitLab was incorporated

In 2014 GitLab was officially incorporated in the Netherlands.

GitLab released a new version every month in 2014, just as every year before it. The first release of the year at January 22nd: GitLab 6.5. At the end of 2014, December 2014, GitLab 7.6 was released.

2015: Y Combinator

In the very start of 2015, almost the entire GitLab team flew over to Silicon Valley to participate in Y Combinator.

At this point, over 800 people worldwide have contributed to GitLab and more than 100,000 organizations are using GitLab.


At GitLab we have one vision. To allow everyone to collaborate on all digital content. For more background and to see how we plan to achieve it please see our direction page.


Our Tanuki logo symbolizes this with a smart animal that works in a group to achieve a common goal. Please see our press page to download the logo.


Please see the values section in our handbook.

Our stewardship of GitLab CE

GitLab Inc. is a for profit company that balances the need to improve GitLab Community Edition (CE) with the need to add features to GitLab Enterprise Edition (EE) exclusively in order to generate more income.

We promise that:

  1. We won’t remove features from CE to make the same feature exclusive in EE
  2. We won’t introduce features into CE with a delay, if a feature is planned to land in both it will be released simultaneously in both
  3. CE will have all the features that are essential to running a large ‘forge’ with public and private repositories
  4. CE will not contain any artificial limits (repositories, users, size, etc.)
  5. The majority of new features made by GitLab Inc. will be for both CE and EE

Apart from making new features GitLab Inc. does a lot of work that benefits both CE and EE:

  1. Responsible disclosure process and security fixes
  2. Release management including a monthly release of both CE and EE
  3. Packaging GitLab in our Omnibus packages
  4. Running a packages server
  5. Dependency upgrades (Rails, gems, etc.)
  6. Performance improvements

When we make new features we ask ourselves, is this feature much more relevant for organizations that have more than 100 developers? If the answer is yes the feature is likely to be exclusive to EE. We always make sure that CE can do all essential things and there are companies using CE with more than 10,000 developers.

When someone contributes a feature to CE that is already in EE we have a hard decision to make. We hope that people focus on contributing features that are neither in CE nor EE. This way both edits benefit from a new feature and GitLab Inc. don’t have to make a hard decision. The features we plan to build for EE are shared on our direction page and we welcome people to contribute features to CE that are planned for future EE releases, if you pick one from the upcoming release please as in the issue if someone is already working on it. When someone does contribute a feature to CE that is already in EE we weigh a couple of factors in that decision:

  1. What is the quality of the code?
  2. Is it complete and does it meet the criteria of the definition of done?
  3. What is the use case for this, is it needed for organizations with less than 100 people?
  4. Is it an original work or clearly based on the EE code?

In case we’re not sure, we’ll consult with the core team to reach a conclusion.


If you’re interested, most of our internal procedures can be found in publicly viewable handbooks.


Some people contact us because they would like to donate to GitLab. If you have time to give please help spread the word about GitLab by mentioning us and/or contribute by reviewing issues and merge requests. If you would like to give money please donate to Rails Girls Summer of Code in our name.


GitLab is a community project with people participating from all over the world. GitLab Inc. has people in three continents to serve our customers better. Most of our customers are in the United States.

Most of our team is distributed. We’re proud to be working remotely, using GitLab Issues to coordinate. We have a Remote Manifesto, our team members have shared their experiences in our blog and did a Q&A for Remote.co. You can taste a bit of the GitLab team culture by visiting our culture page.