GitLab Restructures for the Agentic Era
GitLab CEO Bill Staples published an unusually detailed strategic memo titled “GitLab Act 2,” announcing a restructuring that goes far deeper than typical workforce reductions. The company is betting its future on a thesis that software will be built by machines and directed by people, and is reshaping every layer of the business to match.
The operational changes are significant: GitLab plans to reduce its country footprint by up to 30%, flatten management layers, and reorganize R&D into roughly 60 smaller, more autonomous teams. But the strategic part is what makes this worth reading carefully.
Staples outlines five architectural bets that reveal where GitLab sees the industry heading:
Machine-scale infrastructure. Git itself, the core of every git-based platform, was never designed for agent-rate work — parallel merge requests, 24/7 pipeline triggers, and commits at machine velocity. GitLab is undertaking a generational rebuild of the underlying infrastructure, including reengineering Git itself and building agent-specific APIs so AI agents can act as first-class platform users.
Orchestration across the full lifecycle. A single agent opening a merge request produces activity, not value. GitLab is reimagining CI/CD as an orchestration layer that coordinates multiple agents, manages state, passes context, resolves conflicts, and enforces policy — keeping humans in the loop where judgment matters.
Context as competitive moat. Every vendor is converging on code generation. What doesn’t commoditize, Staples argues, is the connected data model tying planning, code, review, security, and deployment together across years of team history. GitLab is investing in this as a first-class API-accessible service.
Governance built in by default. As agents take on more work, enterprises need identity, audit, policy, and deployment flexibility baked into the core platform — not bolted on as a separate product.
Flexible business model. GitLab is introducing consumption pricing for agent work alongside traditional subscriptions, reflecting a belief that the developer platform market is moving from tens to hundreds (and eventually thousands) of dollars per user per month as agents multiply software output.
Staples also retired GitLab’s long-standing CREDIT values framework in favor of three new operating principles: Speed with Quality, Ownership Mindset, and Customer Outcomes — a sign that the company sees its culture as needing as much reinvention as its technology.
The memo is worth reading in full. It is one of the clearest strategic documents from a major platform company navigating the transition to AI-driven software development, and it lays out specific technical bets that will influence the broader DevSecOps and AI tooling ecosystem.