Product sections, stages, groups, and categories
Principles - Processes - Categories - GitLab the Product - Being a PM - Leadership
Interfaces
We want intuitive interfaces both within the company and with the wider community. This makes it more efficient for everyone to contribute or to get a question answered. Therefore, the following interfaces are based on the product categories defined on this page:
- Home page
- Product page
- Product Features
- Pricing page
- DevOps Lifecycle
- DevOps Tools
- Product Direction
- Stage visions
- Documentation
- Engineering Engineering Manager/Developer/Designer titles, their expertise, and department, and team names.
- Product manager responsibilities which are detailed on this page
- Our pitch deck, the slides that we use to describe the company
- Strategic marketing specializations
Hierarchy
The categories form a hierarchy:
- Sections: Are a collection of stages. We attempt to align these logically along common workflows like Dev, Sec and Ops.
Sections are maintained in
data/sections.yml
. - Stages: are maintained in
data/stages.yml
. Each stage has a correspondingdevops::<stage>
label under thegitlab-org
group. - Group: A stage has one or more groups.
Groups are maintained in
data/stages.yml
. Each group has a correspondinggroup::<group>
label under thegitlab-org
group. - Categories: A group has one or more categories. Categories are high-level
capabilities that may be a standalone product at another company. e.g.
Portfolio Management. To the extent possible we should map categories to
vendor categories defined by analysts.
There are a maximum of 8 high-level categories per stage to ensure we can
display this on our website and pitch deck.
(Categories that do not show up on marketing pages
show up here in italics and do not count toward this limit.) There may need
to be fewer categories, or shorter category names, if the aggregate number of
lines when rendered would exceed 13 lines, when accounting for category names
to word-wrap, which occurs at approximately 15 characters.
Categories are maintained in
data/categories.yml
. Each category has a correspondingCategory:<Category>
label under thegitlab-org
group. Category maturity is managed in the product Category Maturity Change process - Features: Small, discrete functionalities. e.g. Issue weights. Some
common features are listed within parentheses to facilitate finding
responsible PMs by keyword.
Features are maintained in
data/features.yml
. It’s recommended to associate feature labels to a category or a group withfeature_labels
indata/categories.yml
ordata/stages.yml
.
Notes:
- Groups may have scope as large as all categories in a stage, or as small as a single category within a stage, but most will form part of a stage and have a few categories in them.
- Stage, group, category, and feature labels are used by the automated triage operation “Stage and group labels inference from category labels”.
- We don’t move categories based on capacity. We put the categories in the stages where they logically fit, from a customer perspective. If something is important and the right group doesn’t have capacity for it, we adjust the hiring plan for that group, or do global optimizations to get there faster.
- We don’t have silos. If one group needs something in a category that is owned by another group, go ahead and contribute it.
- This hierarchy includes both paid and unpaid features.
Naming
Anytime one hierarchy level’s scope is the same as the one above or below it, they can share the same name.
For groups that have two or more categories, but not all categories in a stage, the group name must be a unique word or a summation of the categories they cover.
If you want to refer to a group in context of their stage you can write that as “Stage:Group”. This can be useful in email signatures, job titles, and other communications. E.g. “Monitor:Health” rather than “Monitor Health” or “Monitor, Health.”
When naming a new stage, group, or category, you should search the handbook and main marketing website to look for other naming conflicts which could confuse customers or employees. Uniqueness is preferred if possible to help drive clarity and reduce confusion. See additional product feature naming guidelines as well.
More Details
Every category listed on this page must have a link to a direction page. Categories may also have documentation and marketing page links. When linking to a category using the category name as the anchor text (e.g. from the chart on the homepage) you should use the URLs in the following hierarchy:
Marketing product page > docs page > direction page
E.g Link the marketing page. If there’s no marketing page, link to the docs. If there’s no docs, link to the direction page.
Solutions
Solutions can consist of multiple categories and are typically used to align to a customer challenge (e.g. the need to reduce security and compliance risk) or to market segments defined by analysts such as Software Composition Analysis (SCA). Solutions are also often used to align to challenges unique to an industry vertical (e.g. financial services), or to a sales segment (e.g. SMB vs Enterprise).
Solutions typically represent a customer challenge, and we define how GitLab capabilities come together to meet that challenge, with business benefits of using our solution.
Market segments defined by analysts don’t always align to GitLab stages and categories and often include multiple categories. Two most frequently encountered are:
- Software Composition Analysis (SCA) = Dependency Scanning + License Compliance + Container Scanning
- Enterprise Agile Planning (EAP) = Team Planning + Planning Analytics + Portfolio Management + Requirements Management
We are intentional in not defining SCA as containing SAST and Code Quality despite some analysts using the term to also include those categories.
Capabilities
Capabilities can refer to stages, categories, or features, but not solutions.
Layers
Adding more layers to the hierarchy would give it more fidelity but would hurt usability in the following ways:
- Harder to keep the interfaces up to date.
- Harder to automatically update things.
- Harder to train and test people.
- Harder to display more levels.
- Harder to reason, falsify, and talk about it.
- Harder to define what level something should be in.
- Harder to keep this page up to date.
We use this hierarchy to express our organizational structure within the Product and Engineering organizations. Doing so serves the goals of:
- Making our groups externally recognizable as part of the DevOps lifecycle so that stakeholders can easily understand what teams might perform certain work
- Ensuring that internally we keep groups to a reasonable number of stable counterparts
As a result, it is considered an anti-pattern to how we’ve organized for categories to move between groups out of concern for available capacity.
When designing the hierarchy, the number of sections should be kept small and only grow as the company needs to re-organize for span-of-control reasons. i.e. each section corresponds to a Director of Engineering and a Director of Product, so it’s an expensive add. For stages, the DevOps loop stages should not be changed at all, as they’re determined from an external source. At some point we may change to a different established bucketing, or create our own, but that will involve a serious cross-functional conversation. While the additional value stages are our own construct, the loop and value stages combined are the primary stages we talk about in our marketing, sales, etc. and they shouldn’t be changed lightly. The other stages have more flexibility as they’re not currently marketed in any way, however we should still strive to keep them as minimal as possible. Proliferation of a large number of stages makes the product surface area harder to reason about and communicate if/when we decide to market that surface area. As such, they’re tied 1:1 with sections so they’re the minimal number of stages that fit within our organizational structure. e.g. Growth was a single group under Enablement until we decided to add a Director layer for Growth; then it was promoted to a section with specialized groups under it. The various buckets under each of the non-DevOps stages are captured as different groups. Groups are also a non-marketing construct, so we expand the number of groups as needed for organizational purposes. Each group usually corresponds to a backend engineering manager and a product manager, so it’s also an expensive add and we don’t create groups just for a cleaner hierarchy; it has to be justified from a span-of-control perspective or limits to what one product manager can handle.
Category Statuses
Categories can have varying level of investment and development work. There are four main investment statuses:
- Accelerated - Top category for product strategy that has received additional investment in the next year
- Sustained - Categories where new features will be added in the next year
- Reduced - Categories where scope and ambition is decreased although, new features will still be added in the next year
- Maintenance - Categories where no new features will added
Typically, product direction pages will transparently state the investment status of the category for the fiscal year based on annual product themes and investment levels.
Changes
The impact of changes to sections, stages and groups is felt across the company.
All new category creation needs to be specifically approved via our Opportunity Canvas review process. This is to avoid scope creep and breadth at the expense of depth and user experience.
Merge requests with changes to sections, stages and groups and significant changes to categories need to be created, approved, and/or merged by each of the below:
- Chief Product Officer
- PLT Leader relevant to the affected Section(s)
- The Director of Product relevant to the affected Section(s)
- The Director of Engineering relevant to the affected Section(s)
- Director of Product Design
_Note: Chief Product Officer approval should be requested once all other approvals have been completed. To request approval, post the MR link in the #chief-product-officer channel tagging both the Chief Product Offcer and cc’ing the EBA to the Chief Product Officer.
The following people need to be on the merge request so they stay informed:
- Chief Technology Officer
- Development Leader relevant to the affected Section(s)
- VP of Infrastructure & Quality Engineering
- VP of UX
- Director, Technical Writing
- Engineering Productivity (by @ mentioning
@gl-quality/eng-prod
) - The Product Marketing Manager relevant to the stage group(s)
After approval and prior to merging, ping the Engineering Manager for Quality Engineering in the MR, if there are changes that:
- Add a new category, group, stage or section
- Move an existing category to a new or existing group
- Move an existing group to a new or existing stage
- Move an existing stage to a new or existing section
- Rename a group, stage or section
- Delete a group, stage or section
This is to ensure that GitLab Bot auto-labeling can be updated prior to the change, which can be disruptive if missed.
Upon approval, tag the group Technical Writer in the merge request to ensure documentation metadata is updated after the category change is merged.
Ensure that relevant slack channels are updated following our slack channel naming convention, open an access request to have slack channel names updated as they can no longer be updated by creators.
Examples
Because it helps to be specific about what is a significant change and what should trigger the above approval process, below are non-exhaustive lists of examples that would and would not, respectively, require full approvals as outlined above.
Changes that require the above approvers include:
- Changes to a section, stage, group, or category name or
marketing
attribute - Removal or addition of a section, stage, group, or category
Changes that require approval only from the relevant Product Leadership Team member include:
- Changing name or removing a non-marketing category, per the
marketing
attribute.
Changes that require approval only from the relevant Product Director include:
- Changing a category maturity date
- Changes to section or group member lists
- Changes to a category vision page
Changing group name
When changing the name of a group, create a merge request to change the group name in data/stages.yml
using the Group-Stage-Category-Change template,
and make sure to complete all the steps in the template.
When changing the team tags, such as be_team_tag
, ensure that each team member’s individual data/team_members/person/
YAML has the relevant departments
entry updated. Alternatively, if the team tag is missing, add the tag under the list of departments
as the second or lower entry. The first departments
entry is controlled by the Workday sync and will be overwritten.
When deciding on the naming, ensure that each team tag is unique. For example, sre_team_tag
should have a different value compared to be_team_tag
. If they are the same, then all team members with the tag with be displayed, duplicating the list for BE and SRE.
Changing category name
When changing an existing category name, there are some considerations to the order of events:
- First, create a MR to change the name in
data/stages.yml
andspec/homepage/category_spec.rb
. - Get sign off from all required stakeholders listed in the instructions above.
- Merge the name change MR.
- Tag the category’s technical writer so that they can update the documentation metadata
- Re-name the category direction page with a new MR. Search for the old category name on the category direction page to ensure the name has been updated in all places.
- Use the
#it-help
Slack channel to request an update to Slack channel name for the re-named category
Changing category maturity
We primarily use the Category Maturity Scorecard process to determine category maturity.
Typically, category maturity moves up from planned to minimal to viable to complete to lovable. However, maturity can also be downgraded. For example, in cases where we discover a JTBD is not met (see example), or when we change the definition of maturity, we may choose to move category maturity down.
When downgrading product maturity, we adjust our customer’s current expectations about our product. This is particularly impactful to our go-to-market team members in customer success and product marketing. We need to do the following to enable alignment between all affected and interested parties:
- Raise an MR for the downgrade and clearly state the reasons for change in the description (see example)
- Inform VP, Product Management by adding them as Reviewer on the MR
- Notify the product group counterparts in the MR; Product Marketing, Product Designer, Engineering Manager, and Technical Writer
- Post the MR in the #customer-success slack channel prior to merging, to allow the team to assess impact and adjust
- Post the MR in the #product slack channel for awareness
DevOps Stages
Analytics section
Slack Channel | #analytics-section |
---|---|
Handbook Page | |
Product |
![]() |
Development |
![]() |
Product Design |
![]() |
UX Research |
![]() |
Legal & Corporate Affairs |
![]() |
graph TD; analytics[Analytics section]-->s_monitor[Monitor stage]; s_monitor-->g_analytics_instrumentation["Analytics Instrumentation group"]; click g_analytics_instrumentation "/handbook/<no value>"; s_monitor-->g_platform_insights["Platform Insights group"]; click g_platform_insights "/handbook/<no value>";
Click on a group name to see more details.
Monitor stage
Slack Channel | #analytics-section |
---|---|
Handbook Page | Development |
Development |
![]() |
Software Engineer in Test |
![]() |
Product Design |
![]() |
UX Research |
![]() |
Analytics Instrumentation group
Total Engineers | Backend |
---|---|
7 | 7 |
Slack Channel | #g_analyze_analytics_instrumentation |
---|---|
Handbook Page | |
Features in this Group | Features |
Product |
![]() |
Backend Engineering Manager |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
UX Research |
![]() |
Application Security Engineer |
![]() |
Internal Customers |
Sales Department
Marketing Department
Product Department
Customer Success
Data Team
|
Name | Maturity | Links |
---|---|---|
Service Ping | Viable | Documentation Page |
Application Instrumentation | Minimal | Direction Page |
Platform Insights group
Slack Channel | #g_monitor_platform_insights |
---|---|
Handbook Page | |
Features in this Group | Features |
Product |
![]() |
Backend Engineering Manager |
![]() |
Product Marketing |
![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Internal Customers |
Sales Department
Marketing Department
Product Department
Customer Success
Data Team
Infrastructure Department
Engineering Department
Security Operations Department
|
Name | Maturity | Links |
---|---|---|
Custom Dashboards Foundation | Minimal | Documentation Page Direction Page |
Observability | Planned 2024 | Direction Page |
Product Analytics | Minimal | Documentation Page Direction Page |
Incident Management | Communityled | Documentation Page Direction Page |
On-call Schedule Management | Communityled | Documentation Page Direction Page |
CD section
Slack Channel | #cd-section |
---|---|
Product |
![]() |
Development |
![]() |
Product Design |
![]() |
UX Research |
![]() |
Product Marketing |
![]() |
Legal & Corporate Affairs |
![]() |
graph TD; cd[CD section]-->s_deploy[Deploy stage]; s_deploy-->g_environments["Environments group"]; click g_environments "/handbook/product/categories/#environments-group";
Click on a group name to see more details.
Deploy stage
Slack Channel | #s_deploy |
---|---|
GitLab Group | @gitlab-org/ci-cd/deploy-stage/environments-group |
Handbook Page | Environments Group |
Product |
![]() |
Development |
![]() |
Product Design |
![]() |
Environments group
Total Engineers | Backend | Frontend |
---|---|---|
6 | 4 | 2 |
Slack Channel | #g_environments |
---|---|
Slack Alias | Environments Group |
Handbook Page | Environments Group |
Focus | TBD |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() |
Frontend Engineering |
![]() ![]() |
UX Research |
![]() |
Product Marketing |
![]() |
Support |
![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Internal Customers |
Quality Department
Delivery Team
Reliability Engineering
Distribution Team
AutoDevOps and Kubernetes Group
|
Name | Maturity | Links |
---|---|---|
Auto DevOps | Viable | Documentation Page Direction Page |
Continuous Delivery | Competitive | Marketing Page Documentation Page Direction Page |
Deployment Management | Viable | Marketing Page Documentation Page Direction Page |
Environment Management | Viable | Documentation Page Direction Page |
Feature Flags | Viable | Documentation Page Direction Page |
Infrastructure as Code | Viable | Documentation Page Direction Page |
Release Orchestration | Viable | Documentation Page Direction Page |
CI section
Slack Channel | #ci-section |
---|---|
Handbook Page | |
Product |
![]() |
Development |
![]() |
Site Reliability Engineering |
![]() ![]() |
Product Design |
![]() |
UX Research |
![]() |
Product Marketing |
![]() |
Legal & Corporate Affairs |
![]() |
graph TD; ci[CI section]-->s_package[Package stage]; s_package-->g_container_registry["Container Registry group"]; click g_container_registry "/handbook/product/categories/#package-group"; s_package-->g_package_registry["Package Registry group"]; click g_package_registry "/handbook/product/categories/#package-group"; ci[CI section]-->s_verify[Verify stage]; s_verify-->g_ci_platform["CI Platform group"]; click g_ci_platform "/handbook/<no value>"; s_verify-->g_hosted_runners["Hosted Runners group"]; click g_hosted_runners "/handbook/product/categories/#hosted-runners"; s_verify-->g_pipeline_authoring["Pipeline Authoring group"]; click g_pipeline_authoring "/handbook/product/categories/#pipeline-authoring-group"; s_verify-->g_pipeline_execution["Pipeline Execution group"]; click g_pipeline_execution "/handbook/product/product-categories/#pipeline-execution-group"; s_verify-->g_runner["Runner group"]; click g_runner "/handbook/product/categories/#runner-group";
Click on a group name to see more details.
Package stage
Slack Channel | #s_package |
---|---|
Handbook Page | Package Stage |
Product |
![]() |
Development |
![]() |
Software Engineer in Test |
![]() |
Product Design |
![]() |
Container Registry group
Total Engineers | Backend | Frontend |
---|---|---|
7 | 6 | 1 |
Slack Channel | #g_container-registry |
---|---|
Slack Alias | container-registry-group |
GitLab Group | @gitlab-org/ci-cd/package-stage/container-registry-group |
Handbook Page | |
Focus | Container Registry GMAU |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() ![]() |
Frontend Engineering |
![]() |
UX Research |
![]() |
Support |
![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Internal Customers |
Distribution Team
Infrastructure Department
Product Security Department
|
Name | Maturity | Links |
---|---|---|
Container Registry | Viable | Documentation Page Direction Page |
Virtual Registry | Viable | Documentation Page Direction Page |
Dependency Firewall | Planned 2025 | Direction Page |
Package Registry group
Total Engineers | Backend | Frontend |
---|---|---|
5 | 4 | 1 |
Slack Channel | #g_package-registry |
---|---|
Slack Alias | package-registry-group |
GitLab Group | @gitlab-org/ci-cd/package-stage/package-registry-group |
Handbook Page | |
Focus | Package Registry GMAU |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() |
Frontend Engineering |
![]() |
UX Research |
![]() |
Support |
![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Internal Customers |
Distribution Team
Infrastructure Department
|
Name | Maturity | Links |
---|---|---|
Package Registry | Viable | Documentation Page Direction Page |
Helm Chart Registry | Viable | Documentation Page Direction Page |
Verify stage
Slack Channel | #s_verify |
---|---|
Product |
![]() |
Development |
![]() |
Software Engineer in Test |
![]() |
Product Design |
![]() |
CI Platform group
Total Engineers | Backend |
---|---|
3 | 3 |
Slack Channel | #g_ci-platform |
---|---|
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() ![]() |
Support |
![]() |
Name | Maturity | Links |
---|---|---|
Continuous Integration (CI) Scaling | Viable | Direction Page |
Hosted Runners group
Total Engineers | SRE |
---|---|
1 | 1 |
Slack Channel | #g_hosted_runners |
---|---|
Focus | Verify & Hosted runners SMAU |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Site Reliability Engineering |
![]() |
Software Engineer in Test |
![]() |
Product Marketing |
![]() |
Support |
![]() ![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Infrastructure Security Engineer |
![]() |
Customer Success |
![]() ![]() |
Internal Customers |
Infrastructure Department
Engineering Department
Security Division
|
Name | Maturity | Links |
---|---|---|
GitLab Hosted Runners | Viable | Documentation Page Direction Page |
Pipeline Authoring group
Total Engineers | Backend | Frontend |
---|---|---|
6 | 5 | 1 |
Slack Channel | #g_pipeline-authoring |
---|---|
Focus | Verify & Runner SMAU |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() |
Frontend Engineering |
![]() |
UX Research |
![]() |
Product Designer |
![]() |
Product Marketing |
![]() |
Support |
![]() ![]() ![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Customer Success |
![]() ![]() |
Internal Customers |
Quality Department
UX Department
Infrastructure Department
Engineering Department
AutoDevOps and Kubernetes Group
Security Division
|
Name | Maturity | Links |
---|---|---|
Pipeline Composition | Viable | Marketing Page Documentation Page Direction Page |
Variables | Complete | Documentation Page Direction Page |
Component Catalog | Minimal | Marketing Page Documentation Page Direction Page |
Pipeline Execution group
Total Engineers | Backend | Frontend |
---|---|---|
8 | 6 | 2 |
Slack Channel | #g_pipeline-execution |
---|---|
Focus | Verify & Runner SMAU |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() ![]() |
Frontend Engineering |
![]() ![]() |
Software Engineer in Test |
![]() |
UX Research |
![]() |
Product Designer |
![]() |
Product Marketing |
![]() |
Support |
![]() ![]() ![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Customer Success |
![]() ![]() |
Internal Customers |
Quality Department
UX Department
Infrastructure Department
Engineering Department
AutoDevOps and Kubernetes Group
Security Division
|
Name | Maturity | Links |
---|---|---|
Continuous Integration (CI) | Competitive | Marketing Page Documentation Page Direction Page |
Merge Trains | Viable | Documentation Page Direction Page |
Code Testing and Coverage | Viable | Documentation Page Direction Page |
Review Apps | Competitive | Documentation Page Direction Page |
Job Artifacts | Minimal | Documentation Page Direction Page |
Pipeline Reports | Minimal | Documentation Page Direction Page |
Runner group
Total Engineers | Backend | SRE |
---|---|---|
13 | 12 | 1 |
Slack Channel | #g_runner |
---|---|
Focus | Verify & Runner SMAU |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Site Reliability Engineering |
![]() |
Software Engineer in Test |
![]() |
UX Research |
![]() |
Product Designer |
![]() |
Product Marketing |
![]() |
Support |
![]() ![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Infrastructure Security Engineer |
![]() |
Customer Success |
![]() ![]() |
Internal Customers |
Infrastructure Department
Engineering Department
|
Name | Maturity | Links |
---|---|---|
GitLab Runner Core | Viable | Documentation Page Direction Page |
Fleet Visibility | Viable | Documentation Page Direction Page |
Core Platform section
Product |
![]() |
---|---|
Development |
![]() |
Product Design |
![]() |
UX Research |
![]() |
Infrastructure Manager |
![]() |
Legal & Corporate Affairs |
![]() |
graph TD; core_platform[Core Platform section]-->s_foundations[Foundations stage]; s_foundations-->g_design_system["Design System group"]; click g_design_system "/handbook/product/categories/#design_system-group"; s_foundations-->g_global_search["Global Search group"]; click g_global_search "/handbook/product/categories/#global-search-group"; s_foundations-->g_import_and_integrate["Import and Integrate group"]; click g_import_and_integrate "/handbook/product/categories/#import_and_integrate-group"; s_foundations-->g_personal_productivity["Personal Productivity group"]; click g_personal_productivity "/handbook/product/categories/#personal_productivity-group"; s_foundations-->g_ux_paper_cuts["UX Paper Cuts group"]; click g_ux_paper_cuts "/handbook/product/categories/#ux_paper_cuts-group"; core_platform[Core Platform section]-->s_systems[Systems stage]; s_systems-->g_cloud_connector["Cloud Connector group"]; click g_cloud_connector "/handbook/product/categories/#cloud-connector-group";
Click on a group name to see more details.
Foundations stage
Slack Channel | #s_manage |
---|---|
Development |
![]() |
Software Engineer in Test |
![]() |
Product Design |
![]() |
Design System group
Total Engineers | Frontend |
---|---|
4 | 4 |
Slack Channel | #g_pajamas-design-system |
---|---|
GitLab Group | @gitlab-org/manage |
Focus | Driving Pajamas adoption |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Frontend Engineering |
![]() ![]() ![]() ![]() |
Product Design |
![]() |
Product Designer |
![]() ![]() ![]() |
Application Security Engineer |
![]() |
Internal Customers |
Alliances Department
Customer Success
Quality Department
Infrastructure Department
Engineering Department
|
Name | Maturity | Links |
---|---|---|
Pajamas Design System | Documentation Page Direction Page |
Global Search group
Total Engineers | Backend | Frontend |
---|---|---|
9 | 8 | 1 |
Slack Channel | #g_global_search |
---|---|
GitLab Group | @gitlab-org/search-team |
Handbook Page | Global Search Group |
Focus | Paid GMAU |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Frontend Engineering |
![]() |
UX Research |
![]() |
Support |
![]() ![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Internal Customers |
Engineering Department
Customer Success
Infrastructure Department
Product Security Department
|
Name | Maturity | Links |
---|---|---|
Global Search | Viable | Documentation Page Direction Page |
Code Search | Minimal | Documentation Page Direction Page |
Import and Integrate group
Total Engineers | Backend | Frontend |
---|---|---|
10 | 8 | 2 |
Slack Channel | #g_manage_import_and_integrate |
---|---|
GitLab Group | @gitlab-org/manage/import-and-integrate |
Focus | Manage Import and Integrate GMAU |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Frontend Engineering |
![]() ![]() |
Support |
![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Internal Customers |
Alliances Department
Customer Success
Quality Department
Infrastructure Department
Engineering Department
|
Name | Maturity | Links |
---|---|---|
API | Documentation Page Direction Page |
|
Integrations | Viable | Documentation Page Direction Page |
Webhooks | Documentation Page Direction Page |
|
Importers | Documentation Page Direction Page |
|
Internationalization | Documentation Page Direction Page |
Personal Productivity group
Total Engineers | Frontend |
---|---|
3 | 3 |
Slack Channel | #g_personal_productivity |
---|---|
GitLab Group | @gitlab-org/foundations/personal-productivity |
Focus | Driving Pajamas adoption |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Frontend Engineering |
![]() ![]() ![]() |
Product Design |
![]() |
UX Research |
![]() |
Product Designer |
![]() ![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Internal Customers |
Alliances Department
Customer Success
Quality Department
Infrastructure Department
Engineering Department
|
Name | Maturity | Links |
---|---|---|
Navigation | Direction Page |
|
Settings | Direction Page |
|
Notifications | Documentation Page Direction Page |
UX Paper Cuts group
Slack Channel | #g_ux_paper_cuts |
---|---|
GitLab Group | @gitlab-org/foundations/ux-paper-cuts |
Handbook Page | |
Focus | The UX Paper Cuts team is responsible for identifying and fixing small, impactful usability issues in the GitLab product. |
Features in this Group | Features |
Product Designer |
![]() ![]() ![]() ![]() |
Systems stage
Slack Channel | #s_core_platform |
---|---|
GitLab Group | @gitlab-org/core-platform-section |
Handbook Page | Core Platform Sub-department |
Product |
![]() |
Development |
![]() |
Software Engineer in Test |
![]() |
Cloud Connector group
Total Engineers | Backend |
---|---|
4 | 4 |
Slack Channel | #g_cloud_connector |
---|---|
GitLab Group | @gitlab-org/cloud-connector-team |
Handbook Page | Cloud Connector Group |
Focus | Cloud Connector PPI |
Features in this Group | Features |
Product |
![]() |
Backend Engineering Manager |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() |
UX Research |
![]() |
Support |
![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Internal Customers |
Quality Department
Infrastructure Department
|
Name | Maturity | Links |
---|---|---|
Cloud Connector | Direction Page |
Data Science section
Product |
![]() |
---|---|
Development |
![]() |
Product Design |
![]() |
UX Research |
![]() |
Legal & Corporate Affairs |
![]() |
graph TD; data-science[Data Science section]-->s_ai-powered[AI-powered stage]; s_ai-powered-->g_ai_framework["AI Framework group"]; click g_ai_framework "/handbook/product/categories/#ai-framework-group"; s_ai-powered-->g_ai_model_validation["AI Model Validation group"]; click g_ai_model_validation "/handbook/product/categories/#ai-model-validation-group"; s_ai-powered-->g_custom_models["Custom Models group"]; click g_custom_models "/handbook/product/categories/#custom-models-group"; s_ai-powered-->g_duo_chat["Duo Chat group"]; click g_duo_chat "/handbook/product/categories/#duo-chat-group"; s_ai-powered-->g_duo_workflow["Duo Workflow group"]; click g_duo_workflow "/handbook/product/categories/#duo-workflow"; data-science[Data Science section]-->s_modelops[ModelOps stage]; s_modelops-->g_dataops["DataOps group"]; click g_dataops "/handbook/product/categories/#dataops-group"; s_modelops-->g_mlops["MLOps group"]; click g_mlops "/handbook/product/categories/#mlops-group";
Click on a group name to see more details.
AI-powered stage
Slack Channel | #s_ai-powered |
---|---|
Handbook Page | Data Science |
Product |
![]() |
Development |
![]() |
Product Design |
![]() |
AI Framework group
Total Engineers | Backend | Frontend |
---|---|---|
11 | 10 | 1 |
Slack Channel | #g_ai_framework |
---|---|
Handbook Page | |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Frontend Engineering |
![]() |
UX Research |
![]() |
Product Designer |
![]() |
Support |
![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Infrastructure Security Engineer |
![]() |
Name | Maturity | Links |
---|---|---|
AI Abstraction Layer | Viable | Documentation Page Direction Page |
AI Model Validation group
Total Engineers | Backend |
---|---|
4 | 4 |
Slack Channel | #g_ai_model_validation |
---|---|
Handbook Page | |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() |
UX Research |
![]() |
Application Security Engineer |
![]() |
Infrastructure Security Engineer |
![]() |
Name | Maturity | Links |
---|---|---|
AI Evaluation | Minimal | Documentation Page Direction Page |
AI Research | Minimal | Documentation Page Direction Page |
Custom Models group
Total Engineers | Backend | Frontend |
---|---|---|
7 | 6 | 1 |
Slack Channel | #g_custom_models |
---|---|
Handbook Page | |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() ![]() |
Frontend Engineering |
![]() |
Product Designer |
![]() |
Support |
![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Infrastructure Security Engineer |
![]() |
Name | Maturity | Links |
---|---|---|
Model Personalization | Minimal | Direction Page |
Self-Hosted Models | Minimal | Documentation Page Direction Page |
Duo Chat group
Total Engineers | Backend | Frontend |
---|---|---|
7 | 6 | 1 |
Slack Channel | #g_duo_chat |
---|---|
Handbook Page | |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() ![]() |
Frontend Engineering |
![]() |
Support |
![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Infrastructure Security Engineer |
![]() |
Name | Maturity | Links |
---|---|---|
Duo Chat | Minimal | Documentation Page Direction Page |
Duo Workflow group
Slack Channel | #g_duo_workflow |
---|---|
Handbook Page | |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
UX Research |
![]() |
Product Designer |
![]() |
Support |
![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Infrastructure Security Engineer |
![]() |
Name | Maturity | Links |
---|---|---|
Duo Workflow | Minimal | Documentation Page Direction Page |
ModelOps stage
Slack Channel | #s_modelops |
---|---|
Handbook Page | Data Science |
Product |
![]() |
Development |
![]() |
Product Design |
![]() |
DataOps group
Slack Channel | #s_modelops |
---|---|
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Application Security Engineer |
![]() |
Name | Maturity | Links |
---|---|---|
DataOps | Planned 2025 | Direction Page |
MLOps group
Total Engineers | Backend |
---|---|
2 | 2 |
Slack Channel | #g_mlops |
---|---|
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() |
Product Designer |
![]() |
Application Security Engineer |
![]() |
Name | Maturity | Links |
---|---|---|
MLOps | Minimal | Documentation Page Direction Page |
AI Agents | Planned 2024 | Documentation Page Direction Page |
Dev section
Product |
![]() |
---|---|
Development |
![]() |
Product Design |
![]() ![]() |
UX Research |
![]() ![]() |
Product Marketing |
![]() |
Legal & Corporate Affairs |
![]() |
graph TD; dev[Dev section]-->s_create[Create stage]; s_create-->g_code_creation["Code Creation group"]; click g_code_creation "/handbook/product/categories/#code-suggestions"; s_create-->g_code_review["Code Review group"]; click g_code_review "/handbook/product/categories/#code-review-group"; s_create-->g_editor_extensions["Editor Extensions group"]; click g_editor_extensions "/handbook/product/categories/#editor-extensions"; s_create-->g_remote_development["Remote Development group"]; click g_remote_development "/handbook/product/categories/#remote-development-group"; s_create-->g_source_code["Source Code group"]; click g_source_code "/handbook/product/categories/#source-code-group"; dev[Dev section]-->s_plan[Plan stage]; s_plan-->g_knowledge["Knowledge group"]; click g_knowledge "/handbook/product/product-categories/#knowledge-group"; s_plan-->g_optimize["Optimize group"]; click g_optimize "/handbook/product/categories/#value-stream-management-group"; s_plan-->g_product_planning["Product Planning group"]; click g_product_planning "/handbook/product/categories/#product_planning"; s_plan-->g_project_management["Project Management group"]; click g_project_management "/handbook/product/categories/#project-management-group";
Click on a group name to see more details.
Create stage
Slack Channel | #s_create |
---|---|
Product |
![]() |
Development |
![]() |
Software Engineer in Test |
![]() |
Product Design |
![]() |
Code Creation group
Total Engineers | Backend |
---|---|
10 | 10 |
Slack Channel | #g_code_creation |
---|---|
Handbook Page | Create:Code Creation Group |
Features in this Group | Features |
Product |
![]() |
Backend Engineering Manager |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Support |
![]() |
Technical Writing |
![]() |
Name | Maturity | Links |
---|---|---|
Code Suggestions | Viable | Marketing Page Documentation Page Direction Page |
Code Review group
Total Engineers | Backend | Frontend |
---|---|---|
9 | 5 | 4 |
Slack Channel | #g_create_code-review |
---|---|
Handbook Page | Create:Code Review Group |
Focus | Create Code Review GMAU |
Features in this Group | Features |
Product |
![]() |
Backend Engineering Manager |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() |
Frontend Engineering Manager |
![]() |
Frontend Engineering |
![]() ![]() ![]() ![]() |
UX Research |
![]() |
Product Designer |
![]() |
Product Marketing |
![]() |
Support |
![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Internal Customers |
Engineering Department
Marketing Department
Product Department
Product Security Department
|
Name | Maturity | Links |
---|---|---|
Code Review Workflow | Complete | Documentation Page Direction Page |
GitLab CLI | Viable | Documentation Page Direction Page |
Editor Extensions group
Total Engineers | Backend | Frontend |
---|---|---|
11 | 6 | 5 |
Slack Channel | #g_editor-extensions |
---|---|
Handbook Page | Create:Editor Extensions Group |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() ![]() |
Frontend Engineering |
![]() ![]() ![]() ![]() ![]() |
UX Research |
![]() |
Technical Writing |
![]() |
Name | Maturity | Links |
---|---|---|
Editor Extensions | Minimal | Documentation Page Direction Page |
Remote Development group
Total Engineers | Frontend |
---|---|
2 | 2 |
Slack Channel | #g_create_ide |
---|---|
Handbook Page | Create:Remote Development Group |
Focus | Create Remote Development GMAU |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Frontend Engineering |
![]() ![]() |
Software Engineer in Test |
![]() |
UX Research |
![]() |
Product Designer |
![]() |
Product Marketing |
![]() |
Support |
![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Internal Customers |
Marketing Department
Engineering Department
Finance Department
People Operations
Product Department
Product Security Department
|
Name | Maturity | Links |
---|---|---|
Web IDE | Competitive | Documentation Page Direction Page |
Workspaces | Minimal | Documentation Page Direction Page |
Source Code group
Total Engineers | Backend | Frontend |
---|---|---|
14 | 10 | 4 |
Slack Channel | #g_create_source-code |
---|---|
Handbook Page | |
Focus | Create Source Code GMAU |
Features in this Group | Features |
Product |
![]() |
Backend Engineering Manager |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Frontend Engineering Manager |
![]() |
Frontend Engineering |
![]() ![]() ![]() ![]() |
UX Research |
![]() |
Product Designer |
![]() |
Product Marketing |
![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Customer Success |
![]() ![]() |
Internal Customers |
Engineering Department
Marketing Department
Product Department
Security Division
|
Name | Maturity | Links |
---|---|---|
Source Code Management | Complete | Marketing Page Documentation Page Direction Page |
Plan stage
Slack Channel | #s_plan |
---|---|
Product |
![]() |
Development |
![]() |
Software Engineer in Test |
![]() |
Product Design |
![]() |
Knowledge group
Total Engineers | Backend | Frontend |
---|---|---|
5 | 4 | 1 |
Slack Channel | #g_knowledge |
---|---|
Handbook Page | |
Focus | Plan Knowledge Paid GMAU |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() |
Frontend Engineering |
![]() |
UX Research |
![]() |
Product Designer |
![]() |
Product Marketing |
![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Customer Success |
![]() |
Internal Customers |
Technical Writing
|
Name | Maturity | Links |
---|---|---|
Wiki | Viable | Documentation Page Direction Page |
Pages | Competitive | Documentation Page Direction Page |
Text Editors | Competitive | Documentation Page Direction Page |
Markdown | Complete | Documentation Page Direction Page |
Optimize group
Total Engineers | Backend | Frontend |
---|---|---|
5 | 2 | 3 |
Slack Channel | #g_plan_optimize |
---|---|
Focus | Plan Optimize GMAU |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() |
Frontend Engineering |
![]() ![]() ![]() |
Product Design |
![]() |
UX Research |
![]() |
Product Designer |
![]() |
Product Marketing |
![]() |
Support |
![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Internal Customers |
Engineering Department
Product Department
Quality Department
Development Department
|
Name | Maturity | Links |
---|---|---|
Value Stream Management | Viable | Marketing Page Documentation Page Direction Page |
DORA Metrics | Viable | Marketing Page Documentation Page Direction Page |
DevOps Reports | Minimal | Documentation Page Direction Page |
Product Planning group
Total Engineers | Backend | Frontend |
---|---|---|
7 | 3 | 4 |
Slack Channel | #g_product-planning |
---|---|
Focus | Plan Product Planning Paid GMAU |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() ![]() |
Frontend Engineering |
![]() ![]() ![]() ![]() |
UX Research |
![]() |
Product Designer |
![]() |
Product Marketing |
![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Internal Customers |
Engineering Department
Product Department
Security Division
|
Name | Maturity | Links |
---|---|---|
Portfolio Management | Viable | Marketing Page Documentation Page Direction Page |
OKR Management | Minimal | Documentation Page Direction Page |
Design Management | Viable | Documentation Page Direction Page |
Requirements Management | Minimal | Documentation Page Direction Page |
Quality Management | Minimal | Documentation Page Direction Page |
Project Management group
Total Engineers | Backend | Frontend |
---|---|---|
11 | 6 | 5 |
Slack Channel | #g_project-management |
---|---|
Handbook Page | Plan:Project Management |
Focus | Plan Project Management Paid GMAU |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() ![]() |
Frontend Engineering |
![]() ![]() ![]() ![]() ![]() |
UX Research |
![]() |
Product Designer |
![]() |
Product Marketing |
![]() |
Support |
![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Internal Customers |
Engineering Department
Product Department
Security Division
|
Name | Maturity | Links |
---|---|---|
Team Planning | Viable | Documentation Page Direction Page |
Service Desk | Viable | Documentation Page Direction Page |
Fulfillment section
Product |
![]() |
---|---|
Development |
![]() |
Product Design |
![]() |
UX Research |
![]() ![]() |
Infrastructure Manager |
![]() |
Legal & Corporate Affairs |
![]() |
graph TD; fulfillment[Fulfillment section]-->s_fulfillment[Fulfillment stage]; s_fulfillment-->g_fulfillment_platform["Fulfillment Platform group"]; click g_fulfillment_platform "/handbook/product/categories/#fulfillment-platform-group"; s_fulfillment-->g_provision["Provision group"]; click g_provision "/handbook/product/categories/#provision-group"; s_fulfillment-->g_subscription_management["Subscription Management group"]; click g_subscription_management "/handbook/product/categories/#subscription-management-group"; s_fulfillment-->g_utilization["Utilization group"]; click g_utilization "/handbook/product/categories/#utilization-group";
Click on a group name to see more details.
Fulfillment stage
Slack Channel | #s_fulfillment |
---|---|
Product |
![]() |
Development |
![]() |
Software Engineer in Test |
![]() ![]() |
Product Design |
![]() |
UX Research |
![]() ![]() |
Fulfillment Platform group
Total Engineers | Backend | Frontend |
---|---|---|
7 | 6 | 1 |
Slack Channel | #g_fulfillment_platform |
---|---|
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() ![]() |
Frontend Engineering |
![]() |
Product Designer |
![]() ![]() |
Support |
![]() |
Application Security Engineer |
![]() |
Name | Maturity | Links |
---|---|---|
Fulfillment Infradev | Viable | Direction Page |
CustomersDot and quote to cash integrations | Viable | Direction Page |
Fulfillment Internal Admin Tooling | Minimal | Direction Page |
Provision group
Total Engineers | Backend |
---|---|
4 | 4 |
Slack Channel | #g_provision |
---|---|
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() |
Product Designer |
![]() ![]() |
Support |
![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Name | Maturity | Links |
---|---|---|
Plan Provisioning | Viable | Direction Page |
Add-on Provisioning | Viable | Direction Page |
User Management | Viable | Documentation Page Direction Page |
Subscription Management group
Total Engineers | Backend | Frontend |
---|---|---|
6 | 3 | 3 |
Slack Channel | #g_subscription_management |
---|---|
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() ![]() |
Frontend Engineering |
![]() ![]() ![]() |
UX Research |
![]() |
Product Designer |
![]() ![]() |
Support |
![]() |
Application Security Engineer |
![]() |
Name | Maturity | Links |
---|---|---|
Subscription Management | Viable | Direction Page |
Utilization group
Total Engineers | Backend | Frontend |
---|---|---|
7 | 3 | 4 |
Slack Channel | #g_utilization |
---|---|
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() ![]() |
Frontend Engineering |
![]() ![]() ![]() ![]() |
UX Research |
![]() |
Product Designer |
![]() ![]() |
Support |
![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Name | Maturity | Links |
---|---|---|
Consumables Cost Management | Viable | Direction Page |
Seat Cost Management | Viable | Direction Page |
Growth section
Product |
![]() ![]() |
---|---|
Development |
![]() ![]() |
Infrastructure Manager |
![]() |
Legal & Corporate Affairs |
![]() |
graph TD; growth[Growth section]-->s_growth[Growth stage]; s_growth-->g_acquisition["Acquisition group"]; click g_acquisition "/handbook/<no value>"; s_growth-->g_activation["Activation group"]; click g_activation "/handbook/<no value>";
Click on a group name to see more details.
Growth stage
Slack Channel | #s_growth |
---|---|
GitLab Group | @gitlab-org/growth |
Handbook Page | |
Development |
![]() |
Internal Customers |
Sales Department
Marketing Department
Product Department
Finance Department
|
Acquisition group
Total Engineers | Backend |
---|---|
6 | 6 |
Slack Channel | #g_acquisition |
---|---|
Handbook Page | |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() ![]() |
Application Security Engineer |
![]() |
Name | Maturity | Links |
---|---|---|
Acquisition | Direction Page |
|
Onboarding | Direction Page |
Activation group
Slack Channel | #g_activation |
---|---|
Handbook Page | |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Application Security Engineer |
![]() |
Name | Maturity | Links |
---|---|---|
Activation | Direction Page |
Infrastructure Platforms section
Product |
![]() |
---|---|
Development |
![]() |
Product Design |
![]() |
UX Research |
![]() |
Infrastructure Manager |
![]() |
Legal & Corporate Affairs |
![]() |
graph TD; infrastructure_platforms[Infrastructure Platforms section]-->s_data_access[Data Access stage]; s_data_access-->g_database_frameworks["Database Frameworks group"]; click g_database_frameworks "/handbook/product/categories/#database-group"; s_data_access-->g_database_operations["Database Operations group"]; click g_database_operations "/handbook/product/categories/#database-group"; s_data_access-->g_durability["Durability group"]; click g_durability "/handbook/<no value>"; s_data_access-->g_git["Git group"]; click g_git "/handbook/product/categories/#git-group"; s_data_access-->g_gitaly["Gitaly group"]; click g_gitaly "/handbook/product/categories/#gitalycluster-group"; infrastructure_platforms[Infrastructure Platforms section]-->s_gitlab_dedicated[GitLab Dedicated stage]; s_gitlab_dedicated-->g_environment_automation["Environment Automation group"]; click g_environment_automation "/handbook/product/categories/#gitlab-dedicated-group"; s_gitlab_dedicated-->g_pubsec_services["US Public Sector Services group"]; click g_pubsec_services "/handbook/product/categories/#us-public-sector-services-group"; s_gitlab_dedicated-->g_switchboard["Switchboard group"]; click g_switchboard "/handbook/product/categories/#switchboard"; infrastructure_platforms[Infrastructure Platforms section]-->s_gitlab_delivery[GitLab Delivery stage]; s_gitlab_delivery-->g_build["GitLab Build group"]; click g_build "/handbook/product/categories/#distribution-group"; s_gitlab_delivery-->g_deploy["GitLab Deploy group"]; click g_deploy "/handbook/<no value>"; s_gitlab_delivery-->g_framework["Framework group"]; click g_framework "/handbook/<no value>"; s_gitlab_delivery-->g_release["GitLab Release group"]; click g_release "/handbook/<no value>"; s_gitlab_delivery-->g_self_managed["Self Managed group"]; click g_self_managed "/handbook/product/categories/#distribution-group"; infrastructure_platforms[Infrastructure Platforms section]-->s_production_engineering[Production Engineering stage]; s_production_engineering-->g_foundations["Foundations group"]; click g_foundations "/handbook/product/categories/"; s_production_engineering-->g_observability["Observability group"]; click g_observability "/handbook/product/categories/"; s_production_engineering-->g_ops["Ops group"]; click g_ops "/handbook/product/categories/"; s_production_engineering-->g_runway["Runway group"]; click g_runway "/handbook/product/categories/"; infrastructure_platforms[Infrastructure Platforms section]-->s_tenant_scale[Tenant Scale stage]; s_tenant_scale-->g_cells_infrastructure["Cells Infrastructure group"]; click g_cells_infrastructure "/handbook/<no value>"; s_tenant_scale-->g_geo["Geo group"]; click g_geo "/handbook/product/categories/#geo-group"; s_tenant_scale-->g_organizations["Organizations group"]; click g_organizations "/handbook/product/categories/#tenant-scale-group";
Click on a group name to see more details.
Data Access stage
Slack Channel | #s_data_access |
---|---|
Product |
![]() |
Development |
![]() |
Software Engineer in Test |
![]() |
Product Design |
![]() |
Database Frameworks group
Total Engineers | Backend |
---|---|
9 | 9 |
Slack Channel | #g_database_frameworks |
---|---|
GitLab Group | @gitlab-org/database-team |
Handbook Page | |
Focus | Database PPI |
Features in this Group | Features |
Product |
![]() |
Backend Engineering Manager |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
UX Research |
![]() |
Support |
![]() |
Application Security Engineer |
![]() |
Internal Customers |
Quality Department
Infrastructure Department
|
Name | Maturity | Links |
---|---|---|
Database | Direction Page |
Database Operations group
Slack Channel | #g_database_operations |
---|---|
GitLab Group | @gitlab-org/database-team |
Handbook Page | Database Operations Team (formerly known as the Database Reliablity Engineering (DBRE) team) |
Features in this Group | Features |
Product |
![]() |
Backend Engineering Manager |
![]() |
UX Research |
![]() |
Support |
![]() |
Application Security Engineer |
![]() |
Internal Customers |
Quality Department
Infrastructure Department
|
Durability group
Slack Channel | #g_durability |
---|---|
Handbook Page | Data Access Durability Team |
Features in this Group | Features |
Product |
![]() |
UX Research |
![]() |
Internal Customers |
Infrastructure Department
|
Name | Maturity | Links |
---|---|---|
Backup/Restore of GitLab instances | Minimal | Documentation Page Direction Page |
Redis | Direction Page |
Git group
Total Engineers | Backend |
---|---|
5 | 5 |
Slack Channel | #g_git |
---|---|
Handbook Page | Git Team |
Focus | Driving Git adoption |
Features in this Group | Features |
Product |
![]() |
Backend Engineering Manager |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() |
Support |
![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Internal Customers |
Quality Department
Infrastructure Department
|
Name | Maturity | Links |
---|---|---|
Git | Documentation Page Direction Page |
Gitaly group
Total Engineers | Backend |
---|---|
10 | 10 |
Slack Channel | #g_gitaly |
---|---|
Handbook Page | Gitaly Team |
Focus | Gitaly GMAU |
Features in this Group | Features |
Product |
![]() |
Backend Engineering Manager |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Software Engineer in Test |
![]() |
Support |
![]() ![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Customer Success |
![]() ![]() |
Internal Customers |
Quality Department
Infrastructure Department
|
Name | Maturity | Links |
---|---|---|
Gitaly | Documentation Page Direction Page |
GitLab Dedicated stage
Slack Channel | #f_gitlab_dedicated |
---|---|
GitLab Group | @gitlab-com/gl-infra/platform |
Handbook Page | Development |
Product |
![]() |
Software Engineer in Test |
![]() |
Product Design |
![]() |
Environment Automation group
Slack Channel | #f_gitlab_dedicated |
---|---|
GitLab Group | @TBD |
Handbook Page | GitLab Dedicated Group |
Focus | GMAU |
Features in this Group | Features |
Product |
![]() |
Backend Engineering Manager |
![]() |
Product Design |
![]() |
UX Research |
![]() |
Support |
![]() ![]() ![]() ![]() ![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Infrastructure Security Engineer |
![]() |
Customer Success |
![]() |
Name | Maturity | Links |
---|---|---|
GitLab Dedicated | Documentation Page Direction Page |
US Public Sector Services group
Slack Channel | #TBD |
---|---|
Slack Alias | TBD |
GitLab Group | @TBD |
Focus | GMAU |
Features in this Group | Features |
Backend Engineering Manager |
![]() |
Software Engineer in Test |
![]() |
Support |
![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Name | Maturity | Links |
---|---|---|
US Public Sector Services | Documentation Page Direction Page |
Switchboard group
Slack Channel | #g_dedicated_switchboard |
---|---|
GitLab Group | @TBD |
Handbook Page | Switchboard team |
Focus | GMAU |
Features in this Group | Features |
Product |
![]() |
Backend Engineering Manager |
![]() |
Product Design |
![]() |
UX Research |
![]() |
Product Designer |
![]() |
Support |
![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Customer Success |
![]() |
Name | Maturity | Links |
---|---|---|
Switchboard | Documentation Page Direction Page |
GitLab Delivery stage
Slack Channel | #s_software_delivery |
---|---|
Product |
![]() |
Development |
![]() |
Software Engineer in Test |
![]() |
Product Design |
![]() |
GitLab Build group
Total Engineers | Backend |
---|---|
8 | 8 |
Slack Channel | #g_distribution |
---|---|
Slack Alias | distributionteam |
GitLab Group | @gitlab-org/distribution |
Handbook Page | Distribution |
Focus | Distribution PPI |
Features in this Group | Features |
Product |
![]() |
Backend Engineering Manager |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
UX Research |
![]() |
Technical Writing |
![]() ![]() |
Application Security Engineer |
![]() |
Internal Customers |
Quality Department
Infrastructure Department
Customer Success
Product Security Department
|
Name | Maturity | Links |
---|---|---|
Build | Viable | Documentation Page Direction Page |
GitLab Deploy group
Total Engineers | Backend | SRE |
---|---|---|
5 | 2 | 3 |
Slack Channel | #g_delivery |
---|---|
GitLab Group | @gitlab-org/delivery |
Handbook Page | |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() |
Site Reliability Engineering |
![]() ![]() ![]() |
UX Research |
![]() |
Name | Maturity | Links |
---|---|---|
Delivery | Documentation Page Direction Page |
Framework group
Slack Channel | #g_software_delivery-framework |
---|---|
Features in this Group | Features |
Development |
![]() |
UX Research |
![]() |
Name | Maturity | Links |
---|---|---|
Delivery | Documentation Page Direction Page |
GitLab Release group
Total Engineers | Backend | SRE |
---|---|---|
5 | 2 | 3 |
Slack Channel | #g_delivery |
---|---|
GitLab Group | @gitlab-org/delivery |
Handbook Page | |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() |
Site Reliability Engineering |
![]() ![]() ![]() |
UX Research |
![]() |
Application Security Engineer |
![]() |
Name | Maturity | Links |
---|---|---|
Delivery | Documentation Page Direction Page |
Self Managed group
Total Engineers | Backend |
---|---|
6 | 6 |
Slack Channel | #g_distribution |
---|---|
Slack Alias | distributionteam |
GitLab Group | @gitlab-org/distribution |
Handbook Page | Distribution |
Features in this Group | Features |
Product |
![]() |
Backend Engineering Manager |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() ![]() |
UX Research |
![]() |
Support |
![]() |
Technical Writing |
![]() ![]() |
Application Security Engineer |
![]() |
Internal Customers |
Quality Department
Infrastructure Department
Customer Success
|
Name | Maturity | Links |
---|---|---|
Omnibus Package | Complete | Documentation Page Direction Page |
Cloud Native Installation | Competitive | Documentation Page Direction Page |
Production Engineering stage
Slack Channel | #s_production_engineering |
---|---|
Product |
![]() |
Development |
![]() |
Software Engineer in Test |
![]() |
Product Design |
![]() |
Foundations group
Slack Channel | #g_foundations |
---|---|
Handbook Page | Production Engineering Foundations Team |
Focus | TBD |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Internal Customers |
Infrastructure Platforms Department
|
Name | Maturity | Links |
---|---|---|
Rate Limiting Framework | Direction Page |
Observability group
Slack Channel | #g_observability |
---|---|
Handbook Page | |
Focus | TBD |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Internal Customers |
Infrastructure Platforms Department
|
Name | Maturity | Links |
---|---|---|
Error Budgets | Documentation Page Direction Page |
|
Capacity Planning | Documentation Page Direction Page |
|
Scalability | Documentation Page Direction Page |
Ops group
Slack Channel | #g_production-engineering_ops |
---|---|
Handbook Page | |
Focus | TBD |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Internal Customers |
Infrastructure Platforms Department
|
Name | Maturity | Links |
---|
Runway group
Slack Channel | #g_runway |
---|---|
Handbook Page | |
Focus | Service enabblement |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Internal Customers |
Quality Department
Infrastructure Department
|
Name | Maturity | Links |
---|
Tenant Scale stage
Slack Channel | #s_tenant_scale |
---|---|
Product |
![]() |
Development |
![]() |
Software Engineer in Test |
![]() |
Product Design |
![]() |
Cells Infrastructure group
Total Engineers | Backend |
---|---|
11 | 11 |
Slack Channel | #g_cells_infrastructure |
---|---|
Focus | Cells |
Features in this Group | Features |
Backend Engineering Manager |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Infrastructure Security Engineer |
![]() |
Name | Maturity | Links |
---|---|---|
Cell | Direction Page |
Geo group
Total Engineers | Backend | Frontend |
---|---|---|
10 | 9 | 1 |
Slack Channel | #g_geo |
---|---|
GitLab Group | @gitlab-org/geo-team |
Handbook Page | |
Focus | Geo Paid GMAU |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Frontend Engineering |
![]() |
Software Engineer in Test |
![]() |
UX Research |
![]() |
Support |
![]() ![]() ![]() ![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Internal Customers |
Infrastructure Department
|
Name | Maturity | Links |
---|---|---|
Geo-replication | Viable | Marketing Page Documentation Page Direction Page |
Disaster Recovery | Competitive | Documentation Page Direction Page |
Organizations group
Total Engineers | Backend | Frontend |
---|---|---|
9 | 8 | 1 |
Slack Channel | #g_organizations |
---|---|
GitLab Group | @gitlab-org/tenant-scale-group |
Handbook Page | |
Focus | Database PPI |
Features in this Group | Features |
Product |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Frontend Engineering |
![]() |
UX Research |
![]() |
Support |
![]() ![]() ![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Infrastructure Security Engineer |
![]() |
Internal Customers |
Quality Department
Infrastructure Department
|
Name | Maturity | Links |
---|---|---|
Groups & Projects | Competitive | Documentation Page Direction Page |
User Profile | Documentation Page Direction Page |
|
Organization | Minimal | Documentation Page Direction Page |
Sec section
Product |
![]() |
---|---|
Product Design |
![]() |
Legal & Corporate Affairs |
![]() |
graph TD; sec[Sec section]-->s_application_security_testing[Application Security Testing stage]; s_application_security_testing-->g_composition_analysis["Composition Analysis group"]; click g_composition_analysis "/handbook/product/categories/#composition-analysis-group"; s_application_security_testing-->g_dynamic_analysis["Dynamic Analysis group"]; click g_dynamic_analysis "/handbook/product/categories/#dynamic-analysis-group"; s_application_security_testing-->g_secret_detection["Secret Detection group"]; click g_secret_detection "/handbook/product/categories/#secret-detection-group"; s_application_security_testing-->g_static_analysis["Static Analysis group"]; click g_static_analysis "/handbook/product/categories/#static-analysis-group"; s_application_security_testing-->g_vulnerability_research["Vulnerability Research group"]; click g_vulnerability_research "/handbook/product/categories/#vulnerability-research-group"; sec[Sec section]-->s_security_risk_management[Security Risk Management stage]; s_security_risk_management-->g_security_infrastructure["Security Infrastructure group"]; click g_security_infrastructure "/handbook/product/categories/#security-infrastructure-group"; s_security_risk_management-->g_security_insights["Security Insights group"]; click g_security_insights "/handbook/product/categories/#security-insights-group"; s_security_risk_management-->g_security_platform_management["Security Platform Management group"]; click g_security_platform_management "/handbook/product/categories/#security-platform-management-group"; s_security_risk_management-->g_security_policies["Security Policies group"]; click g_security_policies "/handbook/product/categories/#security-policies-group"; sec[Sec section]-->s_software_supply_chain_security[Software Supply Chain Security stage]; s_software_supply_chain_security-->g_authentication["Authentication group"]; click g_authentication "/handbook/product/product-categories#authentation-group"; s_software_supply_chain_security-->g_authorization["Authorization group"]; click g_authorization "/handbook/<no value>"; s_software_supply_chain_security-->g_compliance["Compliance group"]; click g_compliance "/handbook/product/product-categories#compliance-group"; s_software_supply_chain_security-->g_pipeline_security["Pipeline Security group"]; click g_pipeline_security "/handbook/product/categories/#pipeline-security-group";
Click on a group name to see more details.
Application Security Testing stage
Slack Channel | #s_application-security-testing |
---|---|
GitLab Group | @gitlab-org/secure |
Handbook Page | Secure Sub-Department |
Product |
![]() |
Development |
![]() |
Software Engineer in Test |
![]() |
Product Design |
![]() |
Composition Analysis group
Total Engineers | Backend |
---|---|
9 | 9 |
Slack Channel | #g_ast-composition-analysis |
---|---|
Slack Alias | secure_composition_analysis_dev |
GitLab Group | @gitlab-org/secure/composition-analysis-dev |
Focus | Composition Analysis Paid GMAU |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Product Marketing |
![]() |
Support |
![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Customer Success |
![]() ![]() ![]() |
Internal Customers |
Product Security Department
Engineering Department
|
Name | Maturity | Links |
---|---|---|
Software Composition Analysis | Viable | Documentation Page Direction Page |
Container Scanning | Viable | Documentation Page Direction Page |
Dynamic Analysis group
Total Engineers | Backend |
---|---|
4 | 4 |
Slack Channel | #g_ast-dynamic-analysis |
---|---|
Slack Alias | secure_dynamic_analysis_be |
GitLab Group | @gitlab-org/secure/dynamic-analysis-be |
Focus | Dynamic Analysis Paid GMAU |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() |
Product Marketing |
![]() |
Support |
![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Customer Success |
![]() ![]() ![]() |
Internal Customers |
Product Security Department
Engineering Department
|
Name | Maturity | Links |
---|---|---|
DAST | Viable | Documentation Page Direction Page |
Fuzz Testing | Viable | Documentation Page Direction Page |
API Security | Viable | Documentation Page Direction Page |
Attack Emulation |
Secret Detection group
Total Engineers | Backend | Frontend |
---|---|---|
8 | 7 | 1 |
Slack Channel | #g_ast-secret-detection |
---|---|
Slack Alias | ast_secret_detection_team |
GitLab Group | @gitlab-org/secure/secret-detection |
Focus | Secret Detection Paid GMAU |
Features in this Group | Features |
Product |
![]() |
Backend Engineering Manager |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Frontend Engineering |
![]() |
Product Marketing |
![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Customer Success |
![]() ![]() ![]() |
Internal Customers |
Product Security Department
Engineering Department
|
Name | Maturity | Links |
---|---|---|
Secret Detection | Viable | Documentation Page Direction Page |
Static Analysis group
Total Engineers | Backend |
---|---|
8 | 8 |
Slack Channel | #g_ast-static-analysis |
---|---|
Slack Alias | secure_static_analysis_team |
GitLab Group | @gitlab-org/secure/static-analysis |
Focus | SAST Paid GMAU |
Features in this Group | Features |
Product |
![]() |
Backend Engineering Manager |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Product Marketing |
![]() |
Support |
![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Customer Success |
![]() ![]() ![]() |
Internal Customers |
Product Security Department
Engineering Department
|
Name | Maturity | Links |
---|---|---|
SAST | Viable | Documentation Page Direction Page |
Code Quality | Minimal | Documentation Page Direction Page |
Vulnerability Research group
Total Engineers | Backend |
---|---|
6 | 6 |
Slack Channel | #g_ast-vulnerability-research |
---|---|
Focus | Paid GMAU |
Features in this Group | Features |
Product |
![]() |
Backend Engineering Manager |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() ![]() |
Product Marketing |
![]() |
Support |
![]() |
Application Security Engineer |
![]() |
Internal Customers |
Product Security Department
Engineering Department
|
Name | Maturity | Links |
---|---|---|
GitLab Advisory Database | Direction Page |
Security Risk Management stage
Slack Channel | #s_srm |
---|---|
Product |
![]() |
Software Engineer in Test |
![]() |
Product Design |
![]() |
Security Infrastructure group
Total Engineers | Backend |
---|---|
8 | 8 |
Slack Channel | #g_srm_security_infrastructure |
---|---|
Focus | Threat Insights Paid GMAU |
Features in this Group | Features |
Backend Engineering Manager |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Name | Maturity | Links |
---|---|---|
Vulnerability Management | Viable | Documentation Page Direction Page |
Dependency Management | Viable | Documentation Page Direction Page |
Security Insights group
Total Engineers | Backend | Frontend |
---|---|---|
10 | 5 | 5 |
Slack Channel | #g_srm_security_insights |
---|---|
Focus | Threat Insights Paid GMAU |
Features in this Group | Features |
Product |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() |
Frontend Engineering |
![]() ![]() ![]() ![]() ![]() |
Fullstack Engineering Manager |
![]() |
Product Designer |
![]() |
Product Marketing |
![]() |
Support |
![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Customer Success |
![]() ![]() |
Internal Customers |
Product Security Department
|
Name | Maturity | Links |
---|---|---|
Vulnerability Management | Viable | Documentation Page Direction Page |
Dependency Management | Viable | Documentation Page Direction Page |
Security Platform Management group
Total Engineers | Backend | Frontend |
---|---|---|
7 | 4 | 3 |
Slack Channel | #g_srm_security_platform_management |
---|---|
Focus | Sec section GMAU |
Features in this Group | Features |
Product |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() |
Frontend Engineering |
![]() ![]() ![]() |
Fullstack Engineering Manager |
![]() |
Product Designer |
![]() |
Product Marketing |
![]() |
Support |
![]() |
Application Security Engineer |
![]() |
Customer Success |
![]() ![]() |
Internal Customers |
Product Security Department
|
Name | Maturity | Links |
---|---|---|
Security Testing Configuration | Planned 2024 | Direction Page |
Security Asset Inventories | Planned 2024 | Direction Page |
Security Testing Integrations | Planned 2024 | Direction Page |
Security Policies group
Total Engineers | Backend | Frontend |
---|---|---|
8 | 5 | 3 |
Slack Channel | #g_srm_security_policies |
---|---|
Focus | Security Policies Paid GMAU |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() |
Frontend Engineering |
![]() ![]() ![]() |
Product Designer |
![]() |
Product Marketing |
![]() |
Support |
![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Customer Success |
![]() ![]() |
Internal Customers |
Product Security Department
Security Assurance Department
Infrastructure Department
|
Name | Maturity | Links |
---|---|---|
Security Policy Management | Minimal | Documentation Page Direction Page |
Software Supply Chain Security stage
Slack Channel | #s_govern |
---|---|
GitLab Group | @gitlab-org/govern |
Handbook Page | |
Development |
![]() ![]() |
Software Engineer in Test |
![]() |
Product Design |
![]() |
Authentication group
Total Engineers | Backend | Frontend |
---|---|---|
8 | 6 | 2 |
Slack Channel | #g_software_supply_chain_security_authentication |
---|---|
Focus | Software Supply Chain Security Authentication Paid GMAU |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() ![]() |
Frontend Engineering |
![]() ![]() |
Product Marketing |
![]() |
Support |
![]() ![]() ![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Internal Customers |
Customer Support Department
Product Security Department
Corporate Security Department
Infrastructure Department
|
Name | Maturity | Links |
---|---|---|
System Access | Viable | Documentation Page Direction Page |
Authorization group
Total Engineers | Backend | Frontend |
---|---|---|
9 | 8 | 1 |
Slack Channel | #g_sscs_authorization |
---|---|
Focus | Software Supply Chain Security Authorization Paid GMAU |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Frontend Engineering |
![]() |
Product Designer |
![]() |
Product Marketing |
![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Internal Customers |
Product Security Department
Corporate Security Department
Security Operations Department
|
Name | Maturity | Links |
---|---|---|
Permissions | Viable | Documentation Page Direction Page |
Instance Resiliency | Minimal | Documentation Page Direction Page |
Insider Threat | Minimal | Direction Page |
Compliance group
Total Engineers | Backend | Frontend |
---|---|---|
8 | 5 | 3 |
Slack Channel | #g_sscs_compliance |
---|---|
Focus | Software Supply Chain Security Compliance Paid GMAU |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() |
Frontend Engineering |
![]() ![]() ![]() |
Product Marketing |
![]() |
Technical Writing |
![]() |
Application Security Engineer |
![]() |
Internal Customers |
Customer Support Department
Product Security Department
Security Assurance Department
Infrastructure Department
|
Name | Maturity | Links |
---|---|---|
Audit Events | Viable | Documentation Page Direction Page |
Compliance Management | Viable | Documentation Page Direction Page |
Release Evidence | Minimal | Documentation Page Direction Page |
Software Supply Chain Security | Viable | Marketing Page Documentation Page Direction Page |
Pipeline Security group
Total Engineers | Backend | Frontend |
---|---|---|
7 | 6 | 1 |
Slack Channel | #g_sscs_pipeline-security |
---|---|
Focus | Pipeline Security Sum of AMAUs |
Features in this Group | Features |
Product |
![]() |
Development |
![]() |
Backend Engineering |
![]() ![]() ![]() ![]() ![]() ![]() |
Frontend Engineering |
![]() |
Product Designer |
![]() |
Support |
![]() ![]() ![]() |
Technical Writing |
![]() |
Internal Customers |
Quality Department
UX Department
Infrastructure Department
AutoDevOps and Kubernetes Group
Product Security Department
|
Name | Maturity | Links |
---|---|---|
Artifact Security | Minimal | Documentation Page Direction Page |
Secrets Management | Minimal | Documentation Page Direction Page |
Single-Engineer Groups section
graph TD; seg[Single-Engineer Groups section]-->s_mobile[Mobile stage]; s_mobile-->g_mobile_devops["Mobile DevOps group"]; click g_mobile_devops "/handbook/product/categories/#mobile-devops-group";
Click on a group name to see more details.
Mobile stage
Slack Channel | #s_mobile |
---|---|
Product |
![]() |
Mobile DevOps group
Slack Channel | #mobile-devops |
---|---|
Features in this Group | Features |
Name | Maturity | Links |
---|---|---|
Mobile DevOps | Direction Page |
Possible future Stages
We have boundless ambition, and we expect GitLab to continue to add new stages to the DevOps lifecycle. Below is a list of future stages we are considering:
- Data, maybe leveraging Meltano product
- Networking, maybe leveraging some of the open source standards for networking and/or Terraform networking providers
- Design, we already have design management today
Stages are different from the application types you can service with GitLab.
Maturity
Not all categories are at the same level of maturity. Some are just minimal and some are lovable. See the category maturity page to see where each category stands.
Other functionality
This list of other functionality so you can easily find the team that owns it. Maybe we should make our features easier to search to replace the section below.
Other functionality in Plan stage
Plan stage
Project Management group
- assignees
- milestones
- due dates
- labels
- issue weights
- quick actions
- email notifications
- to-do list
- Real-time features (excluding real-time collaboration)
Knowledge group
- markdown functionality
- rich text editor
Other functionality in Create stage
Create stage
Code Review group
Remote Development group
Other functionality in Verify
CI Group
Pipeline Authoring Group
Other functionality in Monitor stage
Other functionality in Engineering Productivity
Other functionality in Developer Experience
- Reference Architectures
- GitLab Environment Toolkit (GET)
- GitLab Performance Tool (GPT)
- Performance Test Data
- Zero Downtime Testing Tool
Internal Customers: Gitaly, Core Platform section, SaaS Platforms section, Infrastructure Department, Support Department, Customer Success
Other functionality in Analytics
Product Analytics group
- Analytics Dashboards - used by many groups to add visualizations or provide pre-configured dashboards to users
Facilitated functionality
Some product areas are have a broad impact across multiple stages. Examples of this include, among others:
- Shared project views, like the project overview and settings page.
- Functionality specific to the admin area and not tied to a feature belonging to a particular stage.
- UI components available through our design system, Pajamas.
- Dashboards for displaying analytics, such as Product Analytics, Value Stream Analytics, and others.
While the mental models for these areas are maintained by specific stage groups, everyone is encouraged to contribute within the guidelines that those teams establish. For example, anyone can contribute a new setting following the established guidelines for Settings. When a contribution is submitted that does not conform to those guidelines, we merge it and “fix forward” to encourage innovation.
If you encounter an issue falling into a facilitated area:
- For issues that relate to updating the guidelines, apply the
group::category
label for the facilitating group. - For issues that relate to adding content related to a facilitated area, apply the
group::category
label for the most closely related group. For example, when adding a new setting related to Merge Requests, apply thegroup::source code
label.
Shared responsibility functionality
There are certain product capabilities that are foundational in nature and affect or refer to horizontal components of the architecture that have an impact across functional groups and stages.
These capabilities may refer to “Facilitated Functionality” (see section above) where the mental models are owned by a particular group, while anyone can contribute. However, there may be others that will not have a clear owner because they don’t fall squarely into any particular group’s purview of product categories. Prime examples of this are issues related to the improvement or evolution of foundational components, frameworks and libraries that are used by several or all groups across the organization. Another example could be components created by special task groups in the past that have been since dissolved and that have not required continued development to justify the funding of a dedicated permanent group to maintain them.
Whatever the source of the functionality, rather than thinking of these components as “not having an owner”, it is important to think of them as being owned by everyone through the lens of shared responsibility. “Shared responsibility” means that every group should be committed and responsible to contribute to their continued maintenance, improvement and innovation.
Contribution, in this context, may manifest in different ways:
- Triage by coordinating conversations with stakeholders from different functions and at different levels to find the right owner and/or set the right level of priority.
- Product feature scoping and UX design by fleshing out the details of implementation in requirements documents and/or mockups.
- Technical scoping and feasibility analysis for possible technical and architectural approaches to implementation
- Actual implementation and release activities
It does not mean, however, that a single group should necessarily be solely responsible for all of these activities. Multiple groups could end up collaborating in execution. This coordination however requires a careful triage of the shared responsibility issues in the issue tracker where a single DRI coordinates these activities.
For more information please review this section in the quality department handbook to learn more about a decentralized approach to triaging these types of issues.
Categories A-Z
Category | Group |
---|---|
Acquisition acquisition |
Acquisition |
Activation activation |
Activation |
Add-on Provisioning add-on_provisioning |
Provision |
GitLab Advisory Database advisory_database |
Vulnerability Research |
AI Abstraction Layer ai_abstraction_layer |
AI Framework |
AI Agents ai_agents |
MLOps |
AI Evaluation ai_evaluation |
AI Model Validation |
AI Research ai_research |
AI Model Validation |
API api |
Import and Integrate |
API Security api_security |
Dynamic Analysis |
Application Instrumentation application_instrumentation |
Analytics Instrumentation |
Artifact Security artifact_security |
Pipeline Security |
Attack Emulation attack_emulation |
Dynamic Analysis |
Audit Events audit_events |
Compliance |
Auto DevOps auto_devops |
Environments |
Backup/Restore of GitLab instances backup_restore |
Durability |
Build build |
GitLab Build |
Capacity Planning capacity_planning |
Observability |
Cell cell |
Cells Infrastructure |
Continuous Integration (CI) Scaling ci_scaling |
CI Platform |
Variables ci_variables |
Pipeline Authoring |
Cloud Connector cloud_connector |
Cloud Connector |
Cloud Native Installation cloud_native_installation |
Self Managed |
Code Quality code_quality |
Static Analysis |
Code Review Workflow code_review_workflow |
Code Review |
Code Search code_search |
Global Search |
Code Suggestions code_suggestions |
Code Creation |
Code Testing and Coverage code_testing |
Pipeline Execution |
Compliance Management compliance_management |
Compliance |
Component Catalog component_catalog |
Pipeline Authoring |
Consumables Cost Management consumables_cost_management |
Utilization |
Container Registry container_registry |
Container Registry |
Container Scanning container_scanning |
Composition Analysis |
Continuous Delivery continuous_delivery |
Environments |
Continuous Integration (CI) continuous_integration |
Pipeline Execution |
Custom Dashboards Foundation custom_dashboards_foundation |
Platform Insights |
CustomersDot and quote to cash integrations customersdot_and_quote_to_cash_integrations |
Fulfillment Platform |
Database database |
Database Frameworks |
DataOps dataops |
DataOps |
GitLab Dedicated dedicated |
Environment Automation |
Delivery delivery |
GitLab Deploy Framework GitLab Release |
Dependency Firewall dependency_firewall |
Container Registry |
Dependency Management dependency_management |
Security Infrastructure Security Insights |
Deployment Management deployment_management |
Environments |
Design Management design_management |
Product Planning |
Pajamas Design System design_system |
Design System |
DevOps Reports devops_reports |
Optimize |
Disaster Recovery disaster_recovery |
Geo |
DORA Metrics dora_metrics |
Optimize |
Duo Chat duo_chat |
Duo Chat |
Duo Workflow duo_workflow |
Duo Workflow |
DAST dynamic_application_security_testing |
Dynamic Analysis |
Editor Extensions editor_extensions |
Editor Extensions |
Environment Management environment_management |
Environments |
Error Budgets error_budgets |
Observability |
Feature Flags feature_flags |
Environments |
Fleet Visibility fleet_visibility |
Runner |
Fulfillment Infradev fulfillment_infradev |
Fulfillment Platform |
Fulfillment Internal Admin Tooling fulfillment_internal_admin_tooling |
Fulfillment Platform |
Fuzz Testing fuzz_testing |
Dynamic Analysis |
Geo-replication geo_replication |
Geo |
Git git |
Git |
Gitaly gitaly |
Gitaly |
GitLab CLI gitlab_cli |
Code Review |
GitLab Documentation Site gitlab_docs |
|
Global Search global_search |
Global Search |
Groups & Projects groups_and_projects |
Organizations |
Helm Chart Registry helm_chart_registry |
Package Registry |
GitLab Hosted Runners hosted_runners |
Hosted Runners |
Importers importers |
Import and Integrate |
Incident Management incident_management |
Platform Insights |
Infrastructure as Code infrastructure_as_code |
Environments |
Infrastructure Cost Data infrastructure_cost_data |
|
Insider Threat insider_threat |
Authorization |
Instance Resiliency instance_resiliency |
Authorization |
Integrations integrations |
Import and Integrate |
Internationalization internationalization |
Import and Integrate |
Job Artifacts job_artifacts |
Pipeline Execution |
Markdown markdown |
Knowledge |
Merge Trains merge_trains |
Pipeline Execution |
MLOps mlops |
MLOps |
Mobile DevOps mobile_devops |
Mobile DevOps |
Model Personalization model_personalization |
Custom Models |
Navigation navigation |
Personal Productivity |
Notifications notifications |
Personal Productivity |
Observability observability |
Platform Insights |
OKR Management okr_management |
Product Planning |
Omnibus Package omnibus_package |
Self Managed |
On-call Schedule Management on_call_schedule_management |
Platform Insights |
Onboarding onboarding |
Acquisition |
Organization organization |
Organizations |
Package Registry package_registry |
Package Registry |
Pages pages |
Knowledge |
Permissions permissions |
Authorization |
Pipeline Composition pipeline_composition |
Pipeline Authoring |
Pipeline Reports pipeline_reports |
Pipeline Execution |
Plan Provisioning plan_provisioning |
Provision |
Portfolio Management portfolio_management |
Product Planning |
Product Analytics product_analytics |
Platform Insights |
US Public Sector Services pubsec_services |
US Public Sector Services |
Quality Management quality_management |
Product Planning |
Rate Limiting Framework rate_limiting |
Foundations |
Redis redis |
Durability |
Release Evidence release_evidence |
Compliance |
Release Orchestration release_orchestration |
Environments |
Requirements Management requirements_management |
Product Planning |
Review Apps review_apps |
Pipeline Execution |
GitLab Runner Core runner |
Runner |
Scalability scalability |
Observability |
Seat Cost Management seat_cost_management |
Utilization |
Secret Detection secret_detection |
Secret Detection |
Secrets Management secrets_management |
Pipeline Security |
Security Asset Inventories security_asset_inventories |
Security Platform Management |
Security Policy Management security_policy_management |
Security Policies |
Security Testing Configuration security_testing_configuration |
Security Platform Management |
Security Testing Integrations security_testing_integrations |
Security Platform Management |
Self-Hosted Models self-hosted_models |
Custom Models |
Service Desk service_desk |
Project Management |
Service Ping service_ping |
Analytics Instrumentation |
Settings settings |
Personal Productivity |
Software Composition Analysis software_composition_analysis |
Composition Analysis |
Source Code Management source_code_management |
Source Code |
Software Supply Chain Security sscs |
Compliance |
SAST static_application_security_testing |
Static Analysis |
Subscription Management subscription_management |
Subscription Management |
Switchboard switchboard |
Switchboard |
System Access system_access |
Authentication |
Team Planning team_planning |
Project Management |
Text Editors text_editors |
Knowledge |
User Management user_management |
Provision |
User Profile user_profile |
Organizations |
Value Stream Management value_stream_management |
Optimize |
Virtual Registry virtual_registry |
Container Registry |
Vulnerability Management vulnerability_management |
Security Infrastructure Security Insights |
Web IDE web_ide |
Remote Development |
Webhooks webhooks |
Import and Integrate |
Wiki wiki |
Knowledge |
Workspaces workspaces |
Remote Development |
7aa0e635
)