Environment Automation is a team within the [Dedicated Group](/handbook/engineering/infrastructure-platforms/gitlab-dedicated/). Our mission is to develop and operate the automated plumbing of the GitLab Dedicated solution.
Dedicated Commercial is a group of functional teams within the [Dedicated Group](/handbook/engineering/infrastructure-platforms/gitlab-dedicated/). Our mission is to develop and operate the automated plumbing of the GitLab Dedicated solution, focused mainly on Dedicated Commercial roadmap.
This group of functional teams is a spinoff from Environment Automation Team, after Act 2 at GitLab.
We follow the same processes as listed on the [Dedicated Group](/handbook/engineering/infrastructure-platforms/gitlab-dedicated/), unless a difference exists which is explicitly noted on this page.
## Team Members
## Team Members by Manager
{{<team-by-manager-slug"o-lluch">}}
{{<team-by-manager-slug"denhams">}}
{{<team-by-manager-slug"nitinduttsharma">}}
## Functional Teams after Act 2
R&D department shifted to an organization structure that privileges smaller teams, 3-4 engineers, fully focused on a functional area, with a manager owning 2-3 teams. It also encouraged the role of Functional Lead, a Tech Lead for each functional team, Staff+ responsible for team technical execution and growth.
To fulfill this intent, Environment Automation was split into 5 functional teams:
| Functional team | Serves | Scope and ownership | Key alignment | Manager | Functional Lead |
|---|---|---|---|---|---|
| **Platform Integration** | GitLab module development teams | Owns the integration path that brings external products and modular GitLab features into Dedicated, including Dedicated binding, productionization, and the testing strategy for integration paths. | Theseus and the Test Automation Framework. | Interim: {{<member-by-gitlab"o-olluch">}}| {{<member-by-gitlab"bmckitrick">}} |
| **Platform Resilience** | Dedicated operations teams | Owns resilience and self-healing products for individual tenants — including disaster recovery, autoscaling, automated capacity planning, rate limiting, and other mechanisms that allow an instance to detect, absorb, and recover from failures with minimal human intervention, while keeping infrastructure cost-effective. | Dedicated Orchestration Automation and Cloud Cost Utilization. | {{<member-by-gitlab"denhams">}}| {{<member-by-gitlab"ktchernov">}} |
| **Dedicated Responder Automation** | Dedicated SRE and DevOps responders | Owns responder workflows and tooling for Dedicated incidents, including signal and alert enrichment, alert routing, alert aggregation and automated troubleshooting. | Incident Management and Signals/Observability in Production Engineering. | {{<member-by-gitlab"o-olluch">}}| {{<member-by-gitlab"troblot">}} |
| **Dedicated Orchestration Automation** | Dedicated operators and DevOps teams | Owns the core orchestration platform and change-management automation: job workflows, underlying infrastructure changes, maintenance operations, and tenant-model segments. Platform Resilience, Responder Automation, and Platform Integration consume the platform and own their workflows and configuration within it. | Switchboard Orchestration APIs; also coordinates with Service Delivery Platform and Cells operations where interfaces overlap. | {{<member-by-gitlab"o-olluch">}}| {{<member-by-gitlab"SamirHafez">}} |
| **Dedicated Commercial Features** | Dedicated Product and Dedicated customers | Owns the commercial Dedicated feature roadmap and production-ready implementations, including customer-facing infrastructure and isolation capabilities such as BYOD, network configuration, and Geo Proxy. | Platform Integration and Dedicated Orchestration Automation for artifact injection, integration, and production quality. | {{<member-by-gitlab"denhams">}}| {{<member-by-gitlab"vmondo">}} |
## Working with us
To engage with the Environment Automation team:
We are in the transition to functional teams, so to engage with any functional team please refer to Environment Automation team (we will update this section when new communication channels are available per functional team):
-[Create an issue](https://gitlab.com/gitlab-com/gl-infra/gitlab-dedicated/team/-/issues/new) in the GitLab Dedicated team issue tracker
