The following page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features or functionality remain at the sole discretion of GitLab Inc.
Our Vision for the Ops section is to set up developers for efficient and safe software delivery using the best practices in CI/CD, operations and integrated security.
The Ops Section is comprised of five stages: Verify, Package, Release, Configure, and Monitor. The Release and Configure stages are grouped under the Deployment direction. For a deeper view of the direction of each specific stage please visit the respective Direction Pages linked below:
Market analysts (internal) often describe these stages as automated software quality (ASQ, partially correlated with Verify, Package and Release), IT automation and configuration management (ITACM, correlated with Configure), and IT operations management (ITOM, partially correlated with Monitor). The Ops section also covers CI/CD (Verify/Release), IT Infrastructure Monitoring/APM (Monitor), CDRA (Release), Infrastructure Configuration (Configure) and Package and Binary Management (Package) analyst categories.
In some contexts, "ops" refers to operators. Operators were the counterparts to Developers represented in the original coining of the term DevOps. That definition highlighted the rift between the two groups and a need for collaboration. At GitLab, we use "ops" to mean operations - any component of the value stream delivery platform after a developer commits code. Our developer first perspective means our use of the word "ops" is focused on enabling developers to configure tools and perform operations tasks first. We have support for platform operations and SRE teams who provide Pipelines, Infrastructure and alert response tools to development teams, and ambitious plans to support traditional operators in the future.
GitLab's Ops strategy follows that of GitLab's company strategy. Just like our company mission, we will enable everyone to contribute beyond application code to other digital artifacts that increasingly define the performance, reliability, and resilience of the world's software. We will pursue that mission and capitalize on the opportunities (such as, developer buyer power, IT skills gaps, a move towards Kubernetes, and our roots in source-control and CI) by utilizing a dual-flywheel approach. This approach starts with attracting developers performing DevOps tooling and operations tasks to our Free/Core tier. As we build best of breed tools for them we will co-create to drive product improvements. This will generate revenue for higher product tiers and additional investment for supporting the modern development teams.
More specifically, we will achieve this by enabling easy-to-discover, working-by-default, workflows that support doing powerful, complex actions with a minimum configuration. We want to take advantage of our single application so that, while each team may have their own views or dashboards in the product that support their day to day, the information is available everywhere and to everyone, embedded naturally into their day-to-day workflow where it's relevant. For example:
The end result is that even complex delivery flows become part of everyone's primary way of working. There isn't a context shift (or even worse, a switch into a different tool) needed to start thinking about delivery or operations - that information is there, in context, from your first commit. The centerpiece of this strategy is our Get Things Done Easily theme.
The Ops Section stages represent over 50% of GitLab's future CSM expansion. In three years the Ops market will:
Our Ops Section themes are additive to our overall Yearly Themes, namely:
Each Stage maintains Direction content that contains upcoming plans.
Our plan is to continue to lean into adoption through usability and discoverability in our core stages of Verify, Package, Release and Configure. This will mean sustained focus on onboarding users and organizations from SCM, to CI to Deployment.
For the Monitor stage, we will pursue our common progression product approach to breadth, namely:
As a result our performance indicators and tier strategies are aligned to the maturity of each stage.
In doing so, over the next 12 months we will choose NOT to:
Each Product Group in the Ops Section maintains a version of their What's Next.
The Ops Section stages are at the forefront of GitLab's single DevOps platform vision of enabling everyone to contribute. These stages represent half of GitLab's Total Addressable Market expansion during the next five years and the markets where we have some of the lowest current penetration. As a result the opportunity and impact from R&D investment in these stages are the highest in the company.
User growth in Ops Section stages improves Stages per Organization beyond typical SCM customers - providing the value of a single DevOps platform to our customers. Adding new types of users in turn increases unique active users, while adding paid tier features increases Average Revenue Per User (ARPU) and broad adoption across users in our customers' organizations increases net retention. All of these are critical drivers of our GitLab's business performance.
The total addressable market (TAMkt) for DevOps tools targeting these stages was $5.2B in 2019 and is expected to grow to $10.7B by 2024 (18.8% CAGR) (internal). This analysis is considered conservative as it focuses only on developers and doesn't include additional potential users. This is a deep profit pool and represents a significant portion of GitLab's expanding addressable market. As organizations further adopt DevOps, developer focused ops tools account for a larger share of market. This market has traditionally targeted IT Architects, System Admins and Operators where large hardware budgets enabled expensive IT tools to flourish.
The market is well established (internal), but the participants are evolving rapidly. Existing leaders in single stages of the DevOps lifecycle are expanding to build value stream delivery platforms (internal), what GitLab calls complete DevOps platforms delivered as a single application. These existing players are doing so via acquisition and product development. The leaders run the gamut from GitHub with their strong position in the SCM market and their growing capabilities to compete in CI/CD, to Delivery focused tools such as Harness and JFrog, to Grafana, DataDog and New Relic with their strong positions in Observability and expansion into deployment and incident response. All are pivoting to pursue the value stream delivery platform market.
Despite many strong players, GitLab's market share in the Ops section is growing, especially in the Verify, Package, Release and Configure stages. For Monitor, our unique perspective as a single and complete DevOps application positions us for growth.
You can see how users currently use our various stages in our Ops Section product performance indicators (internal) and Ops Section Usage Dashboard (internal).
We are continually investing in R&D in all Ops Section stages. The maturity of each stage and category can be found in our maturity page. Our investment in the Ops section stages (internal) is critical to both enabling enterprise users to continue on their DevOps maturity journey and completing our complete DevOps platform vision. Driving adoption across multiple Ops stages enables early adopters to recognize the benefit of a single application.
We face a wide range of market challenges (in priority order):
Outside of market challenges we have some internal ones as well:
Given the above challenges, there are key opportunities we must take advantage of (in priority order):
Below are some additional resources to learn more about Ops:
The Ops Section Product Principles are additive to GitLab's Product Principles specifically:
GitLab CI/CD was built from the ground up with speed and scalability in mind. This is reflected both in the product design as well as Continuous Integration and Verify product direction. To enable our users to go from monthly shipping releases to truly enabling continuous delivery, everything that we do must be concerned with the scalability and speed of continuous integration and testing. Not that sword fighting on office chairs isn't fun, but we do want people to be able to contribute at the speed of development. We will achieve this through automated tuning where possible, and faster feedback on potential issues were not.
Wall clock time for a pipeline is an important measure here. You feel this many times every day - when you make a commit and a pipeline starts, but you need to go have lunch before you see the result, that's not fun for anyone. We produce best practices to ensure your pipeline is efficient. Issues like our auto-determining the test parallelization factor and running tests likely to fail first represent how we want GitLab CI/CD to automatically find and solve these problems for you. We are building more speed into the workflow itself with features like the dependency proxy to help speed up the tax you pay on every job invocation setting up the environment, fetching dependencies, and so on.
Progressive Delivery is a set of emerging Continuous Delivery (CD) best practices, oriented around implementing safety and automation in incrementally deliverying (sometimes without deployment) software changes over time. It takes Continuous Delivery to the next level by providing more options around how and when different users get access to your new features, making software delivery a continuous activity, rather than frequent but punctuated moments in time.
There have been four major trends impacting operations; they are all essential to enabling Developer style workflows for operational tasks by defining those activities as code (or data). They are Pipelines as Code, Infrastructure as Code (IAC), Observability as Code (OAC) and Policy as Code. At GitLab, our roots in SCM make us especially well suited for supporting these trends.
GitLab CI/CD is based on pipelines as code principles and a key competitive advantage against other tools that require manual configuration of pipelines. Standardizing on common CI/CD pipeline tools has been proven to increase business results. The value of defining pipelines as code (i) is evident:
GitLab will continue to lean into our pipelines as code capabilities by adding support for releases, advanced deployments and complex builds directly in your
.gitlab-ci.yml files. We'll also add more support for sharing common pipeline code across groups to create a consistent CI/CD platform within your organization.
IAC provides DevOps teams with a method to maintain consistency with the infrastructure their applications run on. The best practices defined in IAC prevent configuration drift, and allow teams to maintain consistent performance and security characteristics without the need for ongoing manual intervention.
IAC was made possible by the availability of rapidly deployed cloud infrastructure (IaaS platforms), and the corresponding buildup of tools to enable generic usage and consistent deployment to that infrastructure (Container Management Platforms).
With our roots as a source code management system, we will build on our existing workflows for code management, and extend our ability to define and manage infrastructure configuration in your project repositories so you can achieve reliability and consistency in your application.
Observability is a measure of your application which defines how well you can understand the state of your production system from its external outputs. The more observable your application is, the more reliably you can operate it, both manually and through automation. Our vision is to allow you to define your observability and operational automation in code, alongside your application code. Whether that is the configuration of dashboards, metrics, alerts, runbooks, automation scripts or incident issues - GitLab will source-control those configurations and ensure they are reliably deployed to your production systems.
Policy as Code is the idea that requirements for auditing and compliance teams can be collected with zero additional cognitive load from developers and other team members participating in software delivery. Because GitLab has an end-to-end view of the artifacts that are associated with releases (issues, merge requests, feature flags, and so on) we are uniquely positioned to provide a comprehensive view of compliance-related activity, collected on an ongoing basis throughout the build, test, and release process. Our vision here can be found in our strategy page for Release Evidence.
Truly integrated DevOps teams are difficult to create. While large organizations have the budget to staff dedicated teams with roles like "Cost Optimization Engineer" and "Site Reliability Engineer" smaller teams require "Jack of All Trades" engineers.
Our vision at GitLab is that everyone can contribute, and that small teams, without specialization, can leverage and adopt the same tools as those in larger organizations. By building on our preference for convention over configuration, we can take the guess work out of operations. We will enable you and your team to quickly build a production application and iterate on it. We'll make it easy for teams to utilize modern operations practices, avoiding alert fatigue by detecting real user events enabling them to resolve like a pro. Not just on its features, but on the overall experience delivered to your users. Rapidly.
Defining your infrastructure, observability, and operations as code is just the first step. The real magic happens when you rapidly iterate on those definitions. As a single-application for the entire DevOps lifecycle GitLab completes what is commonly a major gap in the DevOps loop - the feedback from ops back into planning.
Our vision is to provide not just an easy ability to identify, suggest, complete, and deploy changes to your production system, but also enable new insights that other tools can't. During incident response, GitLab can quickly identify the last deployed commit, lines of code changed, and author to guide the response to the right place. During deployment, GitLab can quickly tell you if your production system is already out-of-bounds from defined service-level indicator (SLI) metrics and roll back. During post-mortems, GitLab can suggest runbook or alert changes. We are very excited about enabling DevSecOps teams with these smart additions.
The performance of the Ops section is defined as the total adoption of its stages as measured by the Ops Section Total Stages Monthly Active Users (internal)) (Ops Section CMAU). Ops Section TMAU is a sum of all SMAUs across the five stages in the Ops Section (Verify, Package, Release, Configure & Monitor).
To increase the Ops Section TMAU, the product groups are focused on driving their stage adoption. We are especially focused on increasing adoption of the Verify and Release stages by driving CI usage from existing SCM users and driving CD usage from existing CI users. This will activate users into Ops Section TMAU and enable them to continue to adopt other Ops section stages as described on Ops section adoption journey (see also the product-wide adoption journey):
The majority of our Ops section product groups are focused on driving adoption first, and then monetization within their category scope. Some groups are well placed to focus on monetization right away by adding tier value for buyer personas (e.g. development manager, director) on top of existing stages which already have heavy usage.
We track our quarterly Product Performance Indicator goals in our internal handbook page. We track our long-term Product Performance Indicator goals here.
|Metric||End of FY24 (2024-01-31) Goal|
|Verify||SMAU to be 2.4M (33% growth), SaaS MAU to be 600K (77% growth), PSMAU to be 650K (24% growth), SaaS PSMAU to be 200K (75% growth)|
|Package||SMAU to be 550k, PSMAU to be 50k|
|Configure||SMAU: 312k; PSMAU: 187k|
Below is the rationale for why and how we believe we can achieve each goal listed above.
Expected exit SMAU for Verify is 1.8M in FY23. Historically we have had 20-25% YoY growth. I'd expect as we introduce new features in Ultimate we would support additional growth in the enterprise segment supporting a higher YoY growth in FY24. Our current projected forecast is 2M, with the addition of the CI/CD Catalog, additional Runner Fleet features, and visibility controls for CI/CD Consumption a 16% growth YoY is too small. With the release of GitLab Dedicated and macOS Runner support, I also anticipate greater growth in our SaaS segment.
Based on the Projected Forcast, in addition to releasing key features of virtual registries, Dependency Firewall, and Instance-level usage data we are anticipating this growth in FY24. With regard to PSMAU, since the virtual registries will mainly focus on Package, I'm taking 18% of 210k (the January 2024 projection) and increasing it by an additional 25% to account for a new market that we will introduce by having greater feature parity with Artifactory.
Estimate an aggressive target of 60% growth each year for SMAU. Growth would come from increased usage from existing customers, enhancing our Environment Management and Release Orchestration capabilities (and better feature parity with / differentiation against competitor tools), instrumentation, and restarting our Feature Flags offering. Another way to approach the target is to look at Release SMAU as a percentage of Verify SMAU (currently 28%) and set a target for this to increase rate of organic growth. We believe we can increase this % to 40%.
Estimates an SMAU of 312k is a 300% increase YoY from the FY23 SMAU forecast of 104k. The PSMAU is estimated to be 60% of SMAU as Kubernetes is likely used mostly by Premium users and we aim to position multi-tenant features to Premium. We plan to reach these goals by improving both the CI/CD and the GitOps flows for the GitLab agent for Kubernetes, by adding observability integrations and by simplifying complex deployments for the developers.
By end of FY24, we expect to have a complete incident management and on-call management solution that are increasingly lovable. We expect that the complete incident solution is useful to a large portion of the GitLab namespaces/instances because many companies still use DIY solutions for responding to incidents. Our goal is to triple our GMAU by the end of FY23 (50k) and double our GMAU again by the end of FY24 (100k). We believe this aggressive goal is possible because we are confident that our focus on establishing Incidents as SSOT is something that all GitLab users need. Once we can complete the incident management loop via the planned Slack integration, and eventually paging via SMS or call services, we can see the GMAU really takeoff.
This target is relatively low compared to other stage goals such as Verify or Create. The primary reason for this is the number of users that will interact with incidents is fewer, yet these interactions are for the benefit of the entire organization. We don't expect to build incident management in such a way to enable more people to participate. That said, there may be additional ways to understand the adoption, such as measuring the number of people that are participating in future on-call rotations.
The most critical are:
We identify the personas the Ops section features are built for. In order to be transparent about personas we support today and personas we aim to support in the future we use the following categorization of personas listed in priority order.
To capitalize on the opportunities listed above, the Ops section has features that make it useful to the following personas today.
As we execute our 3-year strategy, our medium term (1-2 year) goal is to provide a single application that enables collaboration between cloud native development and platform teams.
GitLab pursues acquisitions which will help accelerate our product roadmap. There are a few categories across the Ops Section stages which have a higher appetite for acquisition. We look for one of two things:
Some acquisition options in the Ops Section aren't immediate requirements for our single-devops platform. Instead they represent our vision for an expanded DevOps platform.
In the Ops Section we must diligently prioritize and sequence our investments in a very expansive market from CI adoption from existing SCM users to MVCs in Monitor and Log Management markets.
As a result we maintain a list of our +10% investment priorities to ensure we are balancing capturing short-term and long-term markets. The following are our current +10% investment priorities:
You can see a full list of investment cases using this issue search.
The Ops Section includes many market categories each with their own significant CSMs. We prioritize evaluating and developing a strategy for pursuing each of these markets via the following priority list:
Check out the following links for current problem validation cycles and solution validation cycles for the stages in the Ops section. You can also see the recently completed problem and solution validation issues in our issue tracker.
You can also find Opportunity Canvas artifacts for Ops Section Validation Track activities in our:
Some of our product groups maintain "Letters from the Editor" which provide a quick snapshot of the current state and future investment across that group's assigned categories. You can read those here.
Each stage has an overall strategy statement below, aligned to the themes for Ops. Each category within each stage has a dedicated vision page plus optional documentation, marketing pages, and other materials linked below.
Enabling the Continuous Integration use case is currently spread across four product groups (Pipeline Authoring, Pipeline Execution, Pipeline Insights, and Runner). In order to define our top focuses and intiatives, the Verify Stage needs to have a concerted perspective on what GitLab will offer for Continuous Integration. We are targeting the Ops Section Direction personas and will support these users with our Continuous Integration mission, vision, and one-year direction.
The Continuous Integration vision is a longer term investment. A core capability GitLab CI unlocks is the DevSecOps workflow. A key focus for the Verify Stage is supporting the automation of secure workflows in GitLab. In the next year, we expect to make progress on the following categories to support our target of being the leading CI platform of choice:
There are important things we won't work on to focus on our one year plan.
In the Verify Stage, we have several investment cases highlighted as top priorities for future investment in the Ops Section. Additionally, there are investment cases beyond the ones identified stack ranked by potential return on investment as indicated by priority below:
Gain the confidence to ship at blistering speed and immense scale with automated builds, testing, and out-of-the-box security to verify each commit moves you forward. This category is at the "complete" level of maturity.
Watch us reach 20M builds per day on GitLab.com.
Category containing features associated with editing/authoring your
Manage secrets and protect sensitive data to enable GitLab, or a component built within GitLab to connect to other systems. This category is at the "minimal" level of maturity.
GitLab Runner is the execution agent that is used to run your CI jobs and send the results back to GitLab.
GitLab hosted Runners for GitLab CI on SaaS
GitLab Runner fleet management at enterprise scale
The Jenkins Importer helps unblock teams from migrating to GitLab CI. This category is at the "viable" level of maturity.
Code testing and coverage ensure that individual components built within a pipeline perform as expected, and are an important part of a Continuous Integration framework. This category is at the "viable" level of maturity.
Keep build artifacts under control and actionable.
Be confident in the performance of your changes by ensuring that they are validated against real world scenarios. This category is at the "minimal" level of maturity.
Keeping master green and ensuring the stability of collaboration on branches is vitally important. GitLab has introduced Merge Trains as an important way to accomplish this. This category is at the "viable" level of maturity.
Get a fully functional pre-production environment for every merge request that updates on each commit. See code running, and enable user acceptance testing and automated smoke tests before you merge. This category is at the "complete" level of maturity.
The Verify group is at the entrypoint to the funnel in our user adoption journey, so our features are an critical enabler for users seeking a complete DevOps platform. While we do try to drive adoption in order to support multi-stage growth at least partially through features at the free tier, it's also important for us that we have features at the paid tiers. For our group, these will typically be cross-department and cross-company views related to CI templates, quality and pipelines. See below for the how we are thinking about each of the tiers, and the kinds of features that will be included.
The foundation of the Free strategy for Verify is that enhancements to baseline CI YAML features will be available in this tier by default. The rationale for this approach is that we want to preserve a consistent experience. Users must always be able to use the same
.gitlab-ci.yml in all tiers.
Beyond this, features that drive broad adoption and help with onboarding (including generally making it easier to get started with GitLab CI) are also good candidates for inclusion in this tier. Providing solutions to simplify the deployment and management of Runners at scale for self-managed is also critical for all tiers of users.
The default paid tier for enterprises, Premium will cater to directors operating a medium to large instance. We will focus on features that solve for typical entry-level enterprise needs: reporting and analytics supporting Ops Insights, operational efficiency driving effective project management, and supporting visibility in consumption related to 10,000 CI/CD minutes per month medium to large organizations.
You can see features that we are considering including in this tier in this issue search.
Using GitLab CI across hundreds or thousands of projects in large enterprises means a greater need for portfolio management and consistency of experience in development practices. This is accomplished by making templates discoverable via gitlab#320698 and a consistent authoring experience such as in these issues. Additionally, the larger the organization the greater the need for regulation and compliance which is where features like Protected Runners captured in gitlab&6058 or better integrations with Compliance Pipelines become especially attractive. For customers who self-manage a Runner Fleet, ensuring the security and compliance of the Runner execution environment is critical. Features such as the auto-removal of inactive runners and providing reporting and automation to manage outdated runner versions are just a few examples of features coming in Ultimate aimed at simplifying Runner operations and maintenance. To secure the flows for HashiCorp Vault users, we would like to automatically mask any Vault secrets that are fetched by GitLab CI. To ensure better pipeline compliance we plan to provide you with the ability to enforce the presence of specific variables when validating pipeline configuration. Lastly, our core promise for the Ultimate tier is enabling users to effectively monitor and best use their 50,000 CI/CD minutes by setting CI/CD Minute Limits on their projects.
You can see features that we are considering including in this tier in this issue search.
The goal of the Package Group is to build a product, that within three years, is our customer's single source of truth for storing and distributing images and packages.
You can read more about the Package stage plan on the Package Direction page.
The Package stage is made up of several categories:
Every team needs a place to store their packages and dependencies. GitLab aims to provide a comprehensive solution, integrated into our single application, that supports package management for all commonly used languages and binary formats. This category is at the "viable" level of maturity.
A secure and private registry for Docker images built-in to GitLab. Creating, pushing, and retrieving images works out of the box with GitLab CI/CD. This category is at the "viable" level of maturity.
Kubernetes cluster integrations can take advantage of Helm charts to standardize their distribution and install processes. Supporting a built-in helm chart registry allows for better, self-managed container orchestration. This category is at the "viable" level of maturity.
The GitLab Dependency Proxy can serve as an intermediary between your local developers and automation and the world of packages that need to be fetched from remote repositories. By adding a security and validation layer to a caching proxy, you can ensure reliability, accuracy, and auditability for the packages you depend on. This category is at the "viable" level of maturity.
GitLab ensures that the dependencies stored in your package registries conform to your corporate compliance guidelines. This means you can prevent your organization from using dependencies that are insecure or out of policy. This category is planned, but not yet available.
The former helps us to consider who the feature is for and the latter to consider how the feature fits within the broader GitLab application. If you are interested, consider reading more about the GitLab pricing strategy.
The below details how we are thinking about each of the tiers and the kinds of features that will be included.
The Free version of the product includes the ability to publish, download, and share dependencies using your GitLab credentials.
We'll focus on usability, reliability, and seamless integrations with GitLab continuous integration and delivery. We will ensure that our product is easy and rewarding to contribute to. We will continue to rely on the GitLab Community to help define and refine our product offering. This includes adding support for new package manager formats.
Roadmap features targeted for tier:
From a buyer perspective, Premium features will be focused on team(s) usage, with the purchasing decision led by one or more Directors. The features in this tier will generally align with the themes
Faster code reviews mean that you can deploy and iterate faster. By using GitLab for your project's dependencies, you can reduce the amount of time it takes to verify and validate that a package or container image has been built properly.
But we know that you likely rely on dependencies from a number of remote repositories. That's why we'll be focused on adding support for remote and virtual registries and a generic proxy for container registries. This set of features will ensure that your team can view and manage all of their dependencies in one central location, making code reviews easier and more efficient.
Once your team(s) are using GitLab to manage dependencies, it's important to understand how those dependencies are being used at your organization. That's where the theme of Ops insights comes in. On the roadmap, we have a feature planned to help you measure and display the number of downloads for dependencies.
Directed toward an executive likely buyer, we will focus our efforts here on serving the needs of our larger, enterprise customers. This means introducing features that align with the themes:
This means that the planned dependency firewall category will fall under this tier.
For details about the Release Stage Direction please check out that handbook page.
The details of how we'll achieve different elements of this can be found in the individual category pages below:
Deliver your changes to production with zero-touch software delivery; focus on building great software and allow GitLab CD to bring your release through your path to production for you. This category is at the "complete" level of maturity.
Mitigate the risk of production deploys by deploying new production code to a small subset of your fleet and then incrementally adding more. This category is at the "viable" level of maturity.
Feature flags enable teams to achieve CD by letting them deploy dark features to production as smaller batches for controlled testing, separating feature delivery from customer launch, and removing risk from delivery. This category is at the "viable" level of maturity.
Release Evidence includes all the assurances and evidence collection that are necessary for you to trust the changes you're delivering. This category is at the "minimal" level of maturity.
Management and orchestration of releases-as-code built on intelligent notifications, scheduling of delivery and shared resources, blackout periods, relationships, parallelization, and sequencing, as well as support for integrating manual processes and interventions. This category is at the "viable" level of maturity.
Enable organizations to operate and manage multiple environments directly from GitLab. Environments are encapsulated in GitLab as a target system with associated configurations. By facilitating access control, visualizing deployments and deployment history across teams and projects, adding the ability to query environments, and ensuring that environment's configurations are traceable, platform engineers can enact stronger controls and avoid costly mistakes in deployments. This category is at the "minimal" level of maturity.
To support our goals in 2020 and our 3-year strategy, Release will continue enriching the free features while adding tier value. In our adoption journey, the Release features are typically consumed after continuous integration and source code management, so we will work to expand the independent use of continuous delivery features. While investing in the reduction of barrier to entry into Release we will spend time meeting the needs of the Enterprise by adding visibility into the benefits of using GitLab end-to-end.
Release will continue investing in the free solution to reduce the barrier of entry into Release as both as part of additional Gitlab adoption from existing CI users and as an independent solution without needing to use CI or SCM. We will focus on simplifying the process of managing releases and deploying progressively while empowering developers to release independently using GitLab. Roadmap features targeted for this tier include:
As the default paid tier for enterprises, Premium will cater to directors operating a medium to large instance. We'll direct features that solve for typical entry-level enterprise needs: reporting and analytics, operational efficiency, deployment automation, security and compliance, and other needs that are must-haves for medium to large organizations. While this type of organization should be able to get started in GitLab at lower tiers, they won't be able to thrive at scale. Roadmap features targeted for this tier include:
This tier is directed toward an executive likely buyer. Release groups will direct capabilities into Ultimate which serve the organizational needs of a complex enterprise operating a large GitLab instance. We'll focus on features which will help drive compliance into the continuous delivery workflow and shift security left into the development pipelines. Roadmap features targeted for this tier include:
While the market for the Configure stage has many strong incumbent players, it is splintered across many traditional IT management tools (Ansible, Chef, Puppet). There are emerging trends (i) showing a consolidation on containers (i) and specifically Kubernetes (i) for cloud-native application development. This will have the effect of stymying commercial players from locking in market share based on proprietary tools. So while there are strong players, the current market dynamics means there is upside for us.
The Configure stage is made up of several categories:
Commit your code and GitLab does the rest to build, test, deploy, and monitor automatically. Eliminate the complexities of getting going with automated software delivery by automatically setting up the pipeline and necessary integrations, freeing up your teams to focus on the culture part. This category is at the "viable" level of maturity.
Connect Kubernetes clusters to GitLab for deployments and insights. This category is at the "viable" level of maturity.
Enable platform engineers to use GitLab as their deployment platform: platform engineers can define common DevOps practices, streamline compliance, and share common patterns to enable application development teams to be more efficient. This category is at the "minimal" level of maturity.
Tight integrations with Slack and Mattermost make it easy to manage and automate software development and delivery right from your chat app. This category is at the "minimal" level of maturity.
Manage your infrastructure effectively to create, configure, and manage a complete software development environment. This category is at the "viable" level of maturity.
Gain insights and recommendations about your cluster spending This category is planned, but not yet available.
The market for the Monitor stage is aligned around key players New Relic, Splunk, ServiceNow and Datadog. Datadog, New Relic and Splunk are all headed towards integrated observability platforms based on collecting all available product analytics. ServiceNow (i) is considered a standard for help-desk and Incident Management workflows. Strong existing players with large sustained R&D investment will make it difficult for GitLab to compete head-to-head for Monitor stage market share, especially with traditional Operations and System Administration users.
The Monitor stage is made up of several categories:
Runbooks are a collection of documented procedures that explain how to carry out a particular process, be it starting, stopping, debugging, or troubleshooting a particular system. Executable runbooks allow operators to execute pre-written code blocks or database queries against a given environment.
GitLab collects and displays performance metrics for deployed apps, leveraging Prometheus. Developers can determine the impact of a merge and keep an eye on their production systems, without leaving GitLab. This category is at the "minimal" level of maturity.
Track incidents within GitLab, providing a consolidated location to understand the who, what, when, and where of the incident. Define service level objectives and error budgets, to achieve the desired balance of velocity and stability. This category is at the "viable" level of maturity.
Track on-call responsibilities within your team by creating rotating schedules for responders. This category is at the "minimal" level of maturity.
GitLab makes it easy to view the logs distributed across multiple pods and services using log aggregation with Elastic Stack. Once Elastic Stack is enabled, you can view your aggregated Kubernetes logs across multiple services and infrastructure, go back in time, conduct infinite scroll, and search through your application logs from within the GitLab UI itself. This category is planned, but not yet available.
Tracing provides insight into the performance and health of a deployed application, tracking each function or microservice which handles a given request. This makes it easy to understand the end-to-end flow of a request, regardless of whether you are using a monolithic or distributed system. This category is planned, but not yet available.
Error tracking allows developers to easily discover and view the errors that their application may be generating. By surfacing error information where the code is being developed, efficiency and awareness can be increased. This category is at the "minimal" level of maturity.
Continuous verification is the process of querying external system(s) and using information from the response to make decision(s) to improve the development and deployment process. This category is at the "minimal" level of maturity.
To support our goals in 2020 and our 3-year strategy, Monitor will continue enriching the free features while adding tier value focusing on Incident Management. While investing in the reduction of barriers to entry into Monitor, we will spend time meeting the needs of the Enterprise by adding visibility into the benefits of using GitLab end-to-end.
Monitor will continue investing in the free solution which enables users to set up foundational incident management workflows directly in GitLab. Features in this tier include:
As the default paid tier for enterprises, Premium will cater to directors operating a medium to large instance. We'll direct features that solve for typical entry-level enterprise needs: with alert integrations, incident issues native to GitLab, on-call schedule management, escalation policies and runbooks. While this type of organization should be able to get started in GitLab at lower tiers, they won't be able to thrive at scale. Premium will offer features that enable directors to integrate their monitor tools. Features targeted for this tier include:
Monitor will direct capabilities into Ultimate which serve the organizational needs of a complex enterprise operating a large GitLab instance. Ultimate users will gain efficiency with all of their different tools working well together within and as a part of GitLab. Roadmap features targeted for this tier include: