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

Our stewardship of GitLab

Business model

GitLab Inc. is a for profit company that balances the need to improve the open source code of GitLab with the need to add source-available features to in order to generate income. We have an open core business model and generate almost all our revenue with subscriptions to paid tiers. We recognize that we need to balance the need to generate income and with the needs of the open source project.

We have tried different business models, and many didn’t work. As a company, we realized we needed recurring revenue to continue our mission, and we introduced source available code that is proprietary. Initially there was a worry we would stop working on the open source code but the community saw we were able to accelerate the work on open-source code too.

Promises

We promise that:

  1. We won't remove features from the open source codebase in order to make the same feature paid (features might be removed from the open source codebase due to changes in the application)
  2. We won't introduce features into the open source codebase with a fixed delay, if a feature is planned to land in both it will be released simultaneously in both
  3. We will always release and open source all tests that we have for a open source feature
  4. The open source codebase will have all the features that are essential to running a large 'forge' with public and private repositories
  5. The open source codebase will not contain any artificial limits (repositories, users, size, performance, etc.)
  6. All stages of the DevOps lifecycle (plan, create, verify, package, release, configure, monitor) will have some open source features.
  7. The majority of new features made by GitLab Inc. will be open source
  8. The product will be available for download without leaving an email address or logging in.
  9. We will always allow you to benchmark the performance of GitLab.

What features are paid-only

If the wider community contributes a new feature they get to choose if is open source or source-available (proprietary and paid) by sending labeling merge request with the tier they prefer. If the wider community contributes a feature that is currently source-available we use the process linked in Contributing an existing feature to open-source it.

When GitLab Inc. makes a new feature we ask ourselves who is the likely type buyer to determine into what tier the feature goes. If the likely buyer is an individual contributor the feature will be open source, otherwise it will be source-available.

There aren't any features that are only useful to managers, directors, and executives. So for every source-available feature there will be an individual contributor who cares about it. We're not saying that there aren't any individual contributors that care about the feature, just that we think that other buyers are relatively more likely to care about it. The more of GitLab that you use the more likely it is that you benefit from a higher tier. Even a single person using GitLab might be best off using our highest tier.

It is hard to get the tier right, and if we put something in a tier that is too high we won't hesitate to open-source it or move it to a lower tier. We listen to our community in order to find what we feel is the right balance, and we iterate and make changes based on their feedback. At the same time, the premium product needs to hold value, and we believe we provide that.

All stages of the DevOps lifecycle are available in GitLab CE. There are companies using GitLab unpaid with more than 10,000 users.

If people ask us why a certain feature is paid we might reply with a link to this section of the handbook. We do not mean to imply you don't need the feature. Feel free to make the argument for moving it to another tier, we're listening.

What features are in each paid tier?

The likely type of buyer determines what features go in what tier.

Why release simultaneously in both

Sometimes people suggest having features in EE for a limited time. An example of a limited time release strategy is the Business Source License that keeps features proprietary for 3 years.

At GitLab we want to give everyone access to most of the features (and all the essential ones) at the date they are announced. We want to give people the option to both run and contribute to an open source edition that is maintained and that includes the most recent security fixes.

From time to time we do open source a feature that used to be EE only. We do this when we realize that we've made a mistake applying our criteria, for example when we learned that a branded homepage was an essential feature or when we brought GitLab Pages to the Community Edition.

Our plan is to become the most popular tool for people’s own git hosting service; we’ve managed that so far. Secondarily, we want to get to be the one with the most revenue. Thirdly, we want to become the most popular tool for hosting private repos. Once we’ve reached that, we want to be the most popular tool for hosting public repos. And, lastly, we want to be the number one tool for people to host not just code but books, tech papers, visual models, movies, etc. More info on this is on our strategy page

How open source benefits from open core

GitLab Inc. has an open core business model that includes source-available code and selling subscriptions. This benfits the open source part of GitLab in the following ways:

  1. New features being made by GitLab Inc. that are open source
  2. Responsible disclosure process and security fixes
  3. Release management including a monthly release and patches
  4. Packaging GitLab in our Omnibus packages
  5. Running a packages server
  6. Dependency upgrades (Rails, gems, etc.)
  7. Performance improvements

Existing contributed open source features will not become source-available

We never move existing features already in CE, into EE. This applies regardless of whether the feature was created by GitLab Inc. or community contributors. On occasion, the reverse does happen where we open source a previously source-available feature.

Contributing an existing feature to open-source it

When someone contributes an existing source-available feature to open-source code base, we have a hard decision to make. We encourage contributors to focus on new features not already existing, so that both codebases of GitLab benefit from the feature, and we can avoid any difficult decisions.

We encourage contributors visit our direction page to see features that are welcomed and also review CONTRIBUTING.md.

When someone contributes an existing feature to open-source it, we weigh a number of factors to decide in accepting it, including:

  1. What is the quality of the submitted code?
  2. Is it a complete replacement of the source-available functionality?
  3. Does it meet the contribution acceptance criteria?
  4. Is it more relevant for mid-market organizations or larger?
  5. Is the person or organization submitting this using GitLab in an SMB?
  6. Did the person or organization submitting this contribute to GitLab before?
  7. Is it something that many of our existing customers chose our paid tiers for?
  8. Is it relevant for running a large open source forge?
  9. Is it an original work or based on the source-available code?
  10. Is there an actively maintained fork that incorporates this?
  11. How many organizations are using this code in production?
  12. How frequently has this functionality been requested and by whom?

We'll weigh all factors and you can judge our stewardship of the open source codebase based on the outcome. As of Dec 4, 2018, we had only two cases: One had low code quality and the other one copied the source-available code down to the last space. If you find these or other examples please link them here so people can get an idea of the outcome.

Contributing a not-yet-existing feature

When someone contributes a not yet existing feature on the EE issue tracker, and it has met the contribution acceptance criteria, we will accept it under whatever license (open-source or source-available) they prefer, provided that GitLab Inc. has not already started on working on the feature. (The contribution should not contain any already existing source-available features in it.) We encourage contributors to @-mention the relevant product manager earlier in the development process (in the issue or merge request) to ensure GitLab team-members are not already working on the feature in order to avoid conflicts.