More than 100,000 organizations and millions of users depend on GitLab for their software development and operations. Almost 2000 people contributed code to GitLab (See our 2011 - 2018 Feature Growth Chart) and we've liked thousands of tweets from our 50,000 followers. This rest of this page contains some of the external acknowledgement GitLab has received.
GitLab is now America's 4th fastest-growing private software company, and 44th overall on this year's Inc. 5000 list with revenue growth of 6,213 percent over the past three years. This is the first year GitLab has appeared on Inc.'s 5000 list.
This year's Inc. 5000 ranking system is based on the percentage of revenue growth qualifying companies saw from 2014 to 2017. For consideration, companies needed to be private, for-profit, independent and U.S.-based as of December 31, 2017. The companies must have also been incorporated by March 31, 2014 with a minimum revenue of $200,000 for that year and $2 million for 2017.
With more than 100,000 organizations self-hosting GitLab, we have the largest share of companies who choose to host their own code. We’re estimated to have two-thirds of the single tenant market. When Bitrise surveyed ten thousand developers who build apps regularly on their platform, they found that 67 percent of self-managed apps prefer GitLab’s on-premise solution.
Similarly, in their survey of roughly one thousand development teams, BuddyBuild found that 79% of mobile developers who host their own code have chosen GitLab:
In their articles, both Bitrise and BuddyBuild note that few organizations use self-managed instances. We think there is a selection effect since both of them are SaaS-only offerings.
Based on our experience, the vast majority of enterprises (organizations with over 5000 IT + TEDD employees) self host their source code server (frequently on a cloud service like AWS or GCP) instead of using a SaaS service.
Another assumption is that git is the most popular version control technology for the enterprise. Certainly not every enterprise has switched (completely) yet but it does seem that git is almost 10 times larger than SVN and Mercurial.
Our commitment to seamless integration extends to CI. Integrated CI/CD is both more time and resource efficient than a set of distinct tools, and allows developers greater control over their build pipeline, so they can spot issues early and address them at a relatively low cost. Tighter integration between different stages of the development process makes it easier to cross-reference code, tests, and deployments while discussing them, allowing you to see the full context and iterate much more rapidly. We've heard from customers like Ticketmaster that adopting GitLab CI can transform the entire software development lifecycle (SDLC), in their case helping the Ticketmaster mobile development team deliver on the longstanding goal of weekly releases. As more and more companies look to embrace CI as part of their development methodology, having CI fully integrated into their overall SDLC solution will ensure these companies are able to realize the full potential of CI. You can read more about the benefits of integrated CI in our white paper, Scaling Continuous Integration.
In his post on building Heroku CI, Heroku’s Ike DeLorenzo noted that GitLab CI is “clearly the biggest mover in activity on Stack Overflow,” with more popularity than both Travis CI and Circle CI.
GitLab is the second most popular CI system in a report on cloud trends from Digital Ocean.
When people first hear about a new product they frequently ask if it is any good. A Hacker News user remarked: 'Note to self: Starting immediately, all raganwald projects will have a “Is it any good?” section in the readme, and the answer shall be “yes."'. We took inspiration from that and added it to the GitLab readme. This page continues that tradition.