[DISCUSS] Language Changes and Process Reconciliation

title: "Component Ownership Model"

---

**_A paved path for adding new Infrastructure Components to GitLab.com_**

**_A paved path for adding new Infrastructure Components to all GitLab's Platforms**

![Component Ownership Model Diagram](/images/engineering/infrastructure/production/component_ownership_model.png)

## Understanding the Ecosystem

The Component Ownership Model extends GitLab's Production Readiness process with a focus on ownership,

and best practices using a paved-path to Production.

The Component Ownership Model extends GitLab's Production Readiness Enablement Process (PREP) with a focus on ownership,

and best practices using a paved-path to production in all of GitLab's platforms.

It guides teams through bringing non-Runway infrastructure components online for GitLab.com.

While focused on .com deployment,

This model is part of a larger transformation.

Other initiatives define the

[Self-Managed Foundation and Advanced (SMB/SMA) blueprint](https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/14414)

[Segmenting Self-Managed for a Cloud Native Future blueprint](/handbook/engineering/architecture/design-documents/selfmanaged_segmentation/)

and the

[GitLab Infrastructure Platforms Review Process](https://gitlab.com/groups/gitlab-org/-/epics/17136).

[Production Readiness Enablement Process](https://gitlab.com/groups/gitlab-org/-/epics/17136).

The Component Ownership Model is focused on accelerating and unifying the approach taken for delivering new software components to GitLab.com in a way which aligns expectations,

encourages ownership and reduces the need for manual (possibly slow) gatekeeping from Infrastructure Platforms department.