GitLab Strategy

1. You are here:
2. GitLab Strategy

On this page

• Why
• Mission
• How
• Goals
• Sequence
• Breadth over depth
• Principles
• Assumptions
• Pricing
• Quarterly Objectives and Key Results (OKRs)
• Why is this page public?

Why

We think that it is logical that our collaboration tools are a collaborative work themselves. More than 1800 people have contributed to GitLab to make that a reality. We believe in a world where everyone can contribute. Allowing everyone to make a proposal is the core of what a DVCS (Distributed Version Control System) such as Git enables. No invite needed: if you can see it, you can contribute.

In summary, our vision is as follows:

We believe that all digital products should be open to contributions, from legal documents to movie scripts and from websites to chip designs. GitLab Inc. develops great open source software to enable people to collaborate in this way. GitLab is a single application based on convention over configuration that everyone should be able to afford and adapt. With GitLab, everyone can contribute.

Mission

Change all creative work from read-only to read-write so that everyone can contribute.

When everyone can contribute consumers become contributors and we greatly increase the rate of human progress.

How

Everyone can contribute to digital products with GitLab, to GitLab itself, and to our organization.

1. To ensure that everyone can contribute with GitLab we allow anyone to create a proposal, at any time, without setup, and with confidence.

   • Anyone: Every person in the world should be able to afford great DevOps software. GitLab.com has free private repos and CI runners and GitLab CE is free as in speech and as in beer. But open source is more than a license, that is why we are a good steward of GitLab CE and keep both GitLab CE and EE open to inspection, modifications, enhancements, and suggestions.
   • Create: It is a single application based on convention over configuration.
   • Proposal: with Git, if you can read it, you can fork it to create a proposal.
   • At any time: you can work concurrently to other people, without having to wait for permission or approval from others.
   • Without setup: you can make something without installing or configuring for hours with our web IDE, auto build.
   • With confidence: reduce the risk of a flawed proposal with review apps, integrated CI, automatic code quality, security scans, performance testing, and automatic monitoring.

2. To ensure that everyone can contribute to GitLab the application we actively welcome contributors. We do this by having quality code, tests, documentation, using popular frameworks, offering a comprehensive GitLab Development Kit, and a dedicated GitLab Design Kit. We use GitLab at GitLab Inc., to drink our own wine and make it a tool we continue to love. We celebrate contributions by recognizing a Most Valuable Person (MVP) every month. We allow everyone to anticipate, propose, discuss, and contribute features by having everything on a public issue tracker. We ship a new version every month so contributions and feedback are visible fast. To contribute to open source software people must be empowered to learn programming. That is why we sponsor initiatives such as Rails Girls.

3. To ensure that everyone can contribute to GitLab the company we have open business processes that allow all team members to suggest improvements to our handbook. We hire remotely so everyone with an internet connection can come work for us and be judged on results, not presence in an office. We offer equal opportunity for every nationality. We are agnostic to location and create more equality of opportunity in the world. We engage on Hacker News, Twitter, and our blog post comments. And we strive to take decisions guided by our values.

Goals

1. Ensure that everyone can contribute in the 3 ways outlined above.

2. Become most used software for the software development lifecycle and collaboration on all digital content by following the sequence below.

3. Complete our product vision of a single application based on convention over configuration.

4. Offer a sense of progress in a supportive environment with smart colleagues.

5. Stay independent so we can preserve our values. Since we took external investment we need a liquidity event. To stay independent we want that to be an IPO instead of being acquired.

Sequence

We want to achieve our goals in the following order:

1. In 2015 we became the most popular on-premises software development lifecycle solution, and we want to continue that.

2. We want to become the most revenue generating on-premises software development lifecycle solution before our IPO.

3. Around our IPO we want to become the most popular SaaS solution for private repositories (a complete product that is free forever is competitive since network effects are smaller for private repositories than for public ones).

4. After our IPO we want to become the most popular SaaS solution for public repositories. This market has a strong network effect since more people will participate if you host your public project on a site with more people. It is easier to overcome this network effect if many people already use GitLab.com for hosting private repositories. Having people on our SaaS helps drive awareness and familiarity with GitLab.

5. Our BHAG is to become the most popular collaboration tool for knowledge workers in any industry. For this, we need to make the git workflow much more user friendly. The great thing is that sites like Penflip are already building on GitLab to make it.

We want to IPO in 2020, specifically on Wednesday November 18. 2020 is five years after the first people got stock options with 4 years of vesting. To IPO we need more than $100m in revenue. To achieve that we want to double Incremental Annual Contract Value (IACV) every year. We focus on an incremental number instead of growth of our Annual Recurring Revenue (ARR) because ARR growth is misleading. So far we achieved the goal of doubling IACV in 2013, 2014, 2015, 2016, and 2017.

While we achieve our goals one by one, this doesn't mean we will focus on only one goal at a time. Simultaneously, we'll grow our userbase, get more paid subscribers, grow GitLab.com, realize our scope, and make version control usable for more types of work.

During phase 2 there is a natural inclination to focus only on on-premises since we make all our money there. Having GitHub focus on SaaS instead of on-premises gave us a great opportunity to achieve phase 1. But GitHub was not wrong, they were early. When everyone was focused on video on demand Netflix focused on shipping DVD's by mail. Not because it was the future but because it was the biggest market. The biggest mistake they could have made was to stick with DVDs. Instead they leveraged the revenue generated with the DVDs to build the best video on demand service.

Breadth over depth

We realize our competitors have started earlier and have more capital. Because we started later we need a more compelling product that covers the complete scope with single application based on convention over configuration in a cloud native way. Because we have less capital, we need to build that as a community. Therefore it is important to share and ship our vision for the product. The people that have the most knowledge have to prioritize breadth over depth since only they can add new functionality. Making the functionality more comprehensive requires less coordination than making the initial minimal feature. Shipping functionality that is incomplete to expand the scope sometimes goes against our instincts. However leading the way is needed to allow others to see our path and contribute. With others contributing, we'll iterate faster to improve and polish functionality over time. So when in doubt, the rule of thumb is breadth over depth, so everyone can contribute.

If you want an analogy think of our product team as a plow way in front that tills the earth. It takes a while for the plants (complete features) to grow behind it. This tilled earth is ugly to look at but it surfaces the nutrients that the wider community needs to be inspired and to contribute.

Principles

1. Founder control: vote & board majority so we can keep making long term decisions.

2. Independence: since we took financing we need to have a liquidity event; to maintain independence this needs to be an IPO rather than an acquisition.

3. Low burn: spend seed money like it is the last we’ll raise, maintain 2 years of runway.

4. First time right: last to market so we get it right the first time, a fast follower with taste.

5. Values: make decisions based on our values, even if it is inconvenient.

6. Free SaaS: to make GitLab.com the most popular SaaS for private projects in 2020 it should not have limits for projects or collaborators.

7. Reach: go for a broad reach, no focus on business verticals or certain programming languages.

8. Speed: ship every change in the next release to maximize responsiveness and learning.

9. Life balance: we want people to stay with us for a long time, so it is important to take time off, work on life balance, and being remote-only is a large part of the solution.

Assumptions

1. Open source user benefits: significant advantages over proprietary software because of its faster innovation, higher quality, freedom from vendor lock-in, greater security, and lower total cost of ownership.

2. Open Source stewardship: community comes first, we plays well with others and share the pie with other organizations commercializing GitLab.

3. Innersourcing is needed and will force companies to choose one solution top-down.

4. Git will dominate the version control market in 2020.

5. An single application where interdependence creates exceptional value is superior to a collection of tools or a network of tools. Even so, good integrations are important for network effects and making it possible to integrate GitLab into an organization.

6. To be sustainable we need an open core model that includes a proprietary GitLab EE.

7. EE needs a low base price that is publicly available to compete for reach with CE, established competitors, and new entrants to the market.

8. The low base price for EE is supplemented by a large set of options aimed at larger organizations that get a lot of value from GitLab.

Pricing

Most of GitLab functionality is and will be available for free in Core. Our paid tiers includes features that are more relevant for organizations that have more than 100 potential users. We promise all major features in our scope are available in Core too. Instead of charging for specific parts of our scope (CI, Monitoring, etc.) we charge for smaller features that you are more likely to need if you use GitLab with a lot of users. There are a couple of reasons for this:

1. We want to be a good steward of our open source product.
2. Giving a great free product is part of our go to market, it helps create new users and customers.
3. Having our scope available to all users increases adoption of our scope and helps people see the benefit of an single application.
4. Including all major features in Core helps reduce merge conflicts between CE and EE

Because we have a great free product we can't have one price. Setting it high would make the difference from the free version too high. Setting it low would make it hard to run a sustainable business. There is no middle ground that would work out with one price.

That is why we have a Starter, Premium, and Ultimate tiers. The price difference between each of them is half an order of magnitude (5x).

We charge for making people more effective and will charge per user, per application, or per instance. We do include free minutes with our subscriptions and trials to make it easier for users to get started. As we look towards more deployment-related functionality on .com it's tempting to offer compute and charge a percent on top of, for example, Google Cloud Platform (GCP). We don't want to charge an ambiguous margin on top of another provider since this limits user choice and is not transparent. So we will always let you BYOK (bring your own Kubernetes) and never lock you into our infrastructure to charge you an opaque premium on those costs.

Quarterly Objectives and Key Results (OKRs)

To make sure our goals are clearly defined and aligned throughout the organization, we make use of OKR's (Objective Key Results). Our quarterly Objectives and Key Results are publicly viewable.

Why is this page public?

Our strategy is completely public because transparency is one of our values. We're not afraid of sharing our strategy because as Peter Drucker said: "Strategy is a commodity, execution is an art.".