Teams across the software delivery lifecycle function struggle with:
And they have processes which block reducing time to value, for example:
How does GitLab help solve the customer problems?
GitLab is The DevOps platform.
GitLab is The DevOps platform that empowers organizations to maximize the overall return on software development by delivering software faster, more efficiently, while strengthening security and compliance.
GitLab is The DevOps platform that empowers organizations to maximize the overall return on software development by delivering software faster and efficiently, while strengthening security and compliance. With GitLab, every team in your organization can collaboratively plan, build, secure, and deploy software to drive business outcomes faster with complete transparency, consistency and traceability.
For more information on messaging The DevOps Platform, please see the DevOps Platform Message House.
The company overview can be found here.
The press release boilerplate can be found here.
GitLab makes it easier for companies to achieve software excellence so that they can unlock great software for their customers by reducing the cycle time between having an idea and seeing it in production. GitLab does this with The DevOps platform, which combines the ability to develop, secure, and operate software in a single application that is easier to use and leads to faster cycle times. GitLab is fundamentally changing the way Development, Security, and Ops teams collaborate. GitLab helps teams accelerate software delivery from weeks to minutes, reduce development costs, and reduce the risk of application vulnerabilities while increasing developer productivity. An estimated 30 million users across the globe trust GitLab to deliver great software at new speeds.
GitLab is both a product and a platform. It is a product in that it is a single application that you can buy and use. It is a platform in that it enables multiple use cases, and is a framework on which to build an unlimited number of additional use cases (because most functions are available through an API), supported by an ecosystem enablement group. Users have a fully functional product out-of-the-box, but they are not limited in extending and integrating with other systems. Other examples of products that are also platforms are: the iPhone (which didn't even have an app store when it launched) and Facebook.
While some more traditional definitions of platforms are more limited, there are other perspectives that take a broader view of the definition of platform. Specifically, Adrian Bridgewater explains the Facebook example in this article and also quotes blogger Jonathan Clarks who says, "Platforms are structures that allow multiple products to be built within the same technical framework" - which, one could argue, describes GitLab very well. Another article by Platform Hunt, a blog that studies platform business models, outlines 9 types of software platforms. GitLab most closely resembles an interaction platform, where identity is the foundational characteristic and the platform facilitates digital interactions. In GitLab's case, those digital interactions are collaborative coding, facilitated through both MRs and Issues.
Referring to GitLab as a platform, delivered as a single application, does nothing to diminish the key competitive differentiation of GitLab, as a single application approach has many benefits. Referring to GitLab as a platform also increases the potential TAM (total available market) for GitLab, and decreases potential confusion, as some might think that 'single application' refers to SCM only.
We want to focus on the 'The DevOps platform, delivered as a single application' message. Since "Git" is in our company name, we do not need to re-enforce that we are a Git-based SCM in our messaging. We should always default to the 'The DevOps platform, delivered as a single application' messaging, and, at a minimum, message multiple stage solutions.
Sometimes, we will use headlines with the purpose of grabbing someone's attention on a billboard, banner ad or blog post. Headlines can be more experimental, and sometimes use different words than official messaging. This is acceptable, as long as they are truthful and authentic. For example, our advertising headlines might be different than our value driver language. This is an appropriate use of different messaging for the purpose of engagement and experimentation.
Go to the Pricing tier page to see Tier Messaging
Go to the GitLab positioning FAQ page.
