Retire the tech_stack.yml sync, shortcodes, and links

[Procedures can be found here](/handbook/security/security-operations/sirt/sec-incident-response/#internal-engagement--escalation-for-high-severity-incidents) in the event that an incident needs to be escalated within GitLab. SIRT maintains an [on-call schedule](/handbook/security/security-operations/sirt/engaging-security-on-call/) to ensure ongoing coverage and cross-training for incident response procedures.

Individual system outages should be escalated to system owners per the [Tech Stack](https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/tech_stack.yml).

Individual system outages should be escalated to system owners per the [Tech Stack](/handbook/business-technology/tech-stack-applications/).

### What triggers the Business Continuity Plan

Crisis situations as described above are also escalated and managed through this same process.

BCP for individual system outages are managed by system owners per the [Tech Stack](https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/tech_stack.yml).

BCP for individual system outages are managed by system owners per the [Tech Stack](/handbook/business-technology/tech-stack-applications/).

#### Engagement message template

| Is there a personnel impact? | [Handbook Page](/handbook/people-group/people-ops-tech-analytics/) | #peopleops-eng |

| Is there an infrastructure impact? | [Handbook Page](/handbook/engineering/infrastructure/) | #infrastructure_platforms |

| Is there a legal impact? | [Handbook Page](/handbook/legal/) | #legal |

| Is there a system impact | N/A - [Tech Stack](https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/tech_stack.yml) ownership | N/A - Tech Stack technical_owner |

| Is there a system impact | N/A - [Tech Stack](/handbook/business-technology/tech-stack-applications/) ownership | N/A - Tech Stack technical_owner |

### Vendor communication and service restoration plan

- Ensure/Clarify access being requested is specific to the system being requested.

  - Example: Instead of `Needs read only access to Netsuite`, the team will clarify with the requester that they are asking for the `Custom Auditor (read only)` role in Netsuite.

  - See matrix [here](/handbook/business-technology/enterprise-applications/finsys-access-requests/#-system-specific-access-request-requirements) for System specific requirements.

- Seek Business Owner's approval of the exact role and/or permission being requested, according to who is listed in the [Tech Stack.](https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/tech_stack.yml) This includes [baseline entitlement(s).](https://internal.gitlab.com/handbook/eta/corporate-it/end-user-services/access-request/baseline-entitlements/)

- Seek Business Owner's approval of the exact role and/or permission being requested, according to who is listed in the [Tech Stack](/handbook/business-technology/tech-stack-applications/). This includes [baseline entitlement(s).](https://internal.gitlab.com/handbook/eta/corporate-it/end-user-services/access-request/baseline-entitlements/)

- Once approved, the team will provision the user in the system and add to the corresponding Okta Google group (if necessary).

- Once provisioned, the team will take a screenshot of the user record in the system with a timestamp and attach it to the issue and then close.

---

title: "Tech Stack Applications"

description: "Instructions for how to access the GitLab tech stack and request updates to it"

extra_js:

  - libs/vue.min.js

  - tech-stack.js

---

## Tech Stack Process Has Now Moved to Compass

### Support

Are you experiencing issues with an application/system? Visit our [Tech Stack YAML](https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/tech_stack.yml) and under `Group Owner/Slack Channel`, you can find out what Slack channel you need to reach out to request support.

Are you experiencing issues with an application/system? Visit our [Tech Stack](https://techstack.gtlb.com) and under `Group Owner/Slack Channel`, you can find out what Slack channel you need to reach out to request support.

### Compliance

## Approach

The goal of this page is to describe how to document an application's `Tech Stack Guide`. **An apps Tech Stack Guide should live with the Functional Business Owner of the technology**. Our SSOT for all apps will be the [Tech Stack YAML](https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/tech_stack.yml) and the YAML will populate key portions of the page. However, other sections of the page can be populated that are not included in the YAML file as needed to ensure that the documentation is complete such as Data Model, Integrations, Key Reports/Dashboards.

The goal of this page is to describe how to document an application's `Tech Stack Guide`. **An apps Tech Stack Guide should live with the Functional Business Owner of the technology**. Our SSOT for all apps is the [Tech Stack](/handbook/business-technology/tech-stack-applications/). Populate the other sections of the page as needed to ensure that the documentation is complete, such as Data Model, Integrations, Key Reports/Dashboards.

Here's how to think about the relationship between the Tech Stack YAML nd the Tech Stack Guide:

Here's how to think about the relationship between the Tech Stack and the Tech Stack Guide:

- The Tech Stack YAML is a registry of all apps GitLab owns or operates (the What)

- The Tech Stack is a registry of all apps GitLab owns or operates (the What)

- A Tech Stack Guide covers the business and technical workflows (the Why and How) of each Tech Stack app

- The `handbook_link` key/property in the YAML links to the corresponding Tech Stack Guide(s)

- The Tech Stack entry links to the corresponding Tech Stack Guide(s)

We also plan to have a second YAML file for our security applications called the Security Stack YAML that lives in the internal handbook. We will use the same template approach for these applications.

## Tech Stack Application Name

The Tech Stack single source of truth is the [Tech Stack YAML](https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/tech_stack.yml) and contains more detail about this app.

```markdown

{{%/* tech-stack "Application Name" */%}}

```

The [Tech Stack](/handbook/business-technology/tech-stack-applications/) is the single source of truth and contains more detail about this app.

### Implementation

Important Notes:

1. This Tech Stack Guide lives in the [GitLab Professional Education Services](/handbook/customer-experience/professional-services-engineering/education-services) handbook because Professional Services are the business owners of the app

2. The `handbook_link` key in the [Tech Stack YAML](https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/tech_stack.yml) for Thought Industries Learning Management System references the Tech Stack Guide

2. The [Tech Stack](/handbook/business-technology/tech-stack-applications/) entry for Thought Industries Learning Management System references the Tech Stack Guide

## Tech Stack Guide Example #2: Zuora Billing

### Code

```markdown

The Tech Stack single source of truth is the [Tech Stack YAML](https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/tech_stack.yml) and contains more detail about this app.

{{%/* tech-stack "Zuora Billing" */%}}

The [Tech Stack](/handbook/business-technology/tech-stack-applications/) is the single source of truth and contains more detail about this app.

```

### Result

The Tech Stack single source of truth is the [Tech Stack YAML](https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/tech_stack.yml) and contains more detail about this app.

{{% tech-stack "Zuora Billing" %}}

The [Tech Stack](/handbook/business-technology/tech-stack-applications/) is the single source of truth and contains more detail about this app.

### Implementation

### Request Access

If you need to request access for any of the following tools, please refer to and follow the [Access Request process](/handbook/eta/corporate-it/end-user-services/access-requests/access-requests/).

If you need to request access for a tool, please refer to and follow the [Access Request process](/handbook/eta/corporate-it/end-user-services/access-requests/access-requests/).

## Tech Stack Applications

{{% all-tech-stack %}}

For the list of applications, their owners, and how to request updates, see [Tech Stack Applications](/handbook/business-technology/tech-stack-applications/).