Team
See the SaaS Platforms Organizational Structure for teams in Infrastructure.
FinOps Team
The FinOps function brings experience in both Site Reliability Engineering (SRE) and Software Engineering (SWE), leveraging these skills to optimize the financial operations of our cloud services and data resources. This technical expertise enables us to not only ensure alignment with financial objectives but also drive operational efficiency at scale. Our team’s deep understanding of cloud cost structures, infrastructure, data management, and automation empowers us to manage the full lifecycle of cloud consumption, from cost allocation to detailed analysis, while maintaining the high standards of reliability and performance expected in modern cloud environments.
GitLab Dedicated Group
Mission
The GitLab Dedicated team’s mission is to create a fully managed, single-tenant GitLab environment, served through a GitLab Dedicated platform. It is developed to remove any manual interactions with customer tenant installations, and to ensure that the customer tenants are fully focused on unlocking the power of The One DevOps Platform.
Vision
The GitLab Dedicated group is a customer facing team, with team members focused on a high level of infrastructure automation, and enabling customer interactions with the GitLab Dedicated platform.
Production Engineering Foundations Team
Mission
The mission of the Production Engineering Foundations team at GitLab is to build and evolve the networking infrastructure that powers GitLab SaaS while maintaining the stability of select core platform services. We focus on developing innovative networking solutions that scale with GitLab’s growth, while ensuring our maintained services remain reliable and efficient.
Vision
The Foundations team’s North Star consists of two pieces:
- Excellence in networking infrastructure. We will drive GitLab’s networking capabilities for GitLab forward by building scalable, secure, and efficient solutions. This includes evolving our edge services, load balancing, rate limiting, and network security to meet the growing demands of all GitLab platforms. Through centralized networking tooling and infrastructure, we create a foundation that supports GitLab’s continued growth and innovation.
- Sustainable toil and service maintenance. While toil is inherent in SRE work, we will adopt processes and policies that create an effective balance between automation and manual work. This approach ensures we can maintain our core infrastructure services reliably while keeping operational overhead minimal as GitLab grows. We strive for efficiency in both our day-to-day operations and our maintenance of essential platform services.
Responsibilities
Primary Areas of Ownership
The Foundations team’s flagship focus is our networking infrastructure, which we actively work to improve and expand:
Production Engineering Ops Team
Mission
The Ops team is an infrastructure team under SaaS Platforms that focuses on improving processes that are vital to the succesfull operations of GitLab.
Vision
The Ops teams vision is to enable service onwers to operate their own services using standardized processes, frameworks, architectures and tools. Some of those processes and tools will be built by the Ops team, but many will be from other Infrastructure teams.
Runway Team
Mission
The Runway team builds and supports the Runway product, which aims to enable teams to deploy their code to staging & production quickly, safely and efficiently.
Ownership
The team has ownership over the following areas:
Services
The Runway team handles issues labeled Service::Runway
For services deployed to Runway, the Runway team is responsible for building functionality for the platform, operating the platform, and maintaining the platform for service owners.
Scalability Group
Common Links
Workflow | Team workflow |
GitLab.com | @gitlab-org/scalability |
Issue Trackers | Scalability |
Team Slack Channels | #g_scalability - Company facing channel #g_scalability-observability - Team channel #g_scalability-practices - Team channel #scalability_social - Group social channel |
Information Slack Channels | #infrastructure-lounge (Infrastructure Group Channel), #incident-management (Incident Management), #alerts-general (SLO alerting), #mech_symp_alerts (Mechanical Sympathy Alerts) |
Project Management Links
Group Level
- Scalability Epic Board
- Scalability Issue Board
- Scalability Issues not in an Epic
- Scalability Issues by Team
- Scalability Issues by Team Member
Teams
The Scalability group is currently formed of two teams:
46417d02
)