GitLab restructuring – GitLab begins a June 1 restructuring tied to the “agentic era,” flattening management, reshaping R&D, and embedding AI agents into internal workflows.

A major software company has kicked off a high-stakes restructuring that is likely to define jobs, organization, and strategy for years—at least until the financial details are finalized.

GitLab said it is restructuring to prepare for what CEO Bill Staples described as “the agentic era,” and that it plans to cut an unspecified number of employees by June 1. The company reported it had 2,580 employees as of January. After the announcement, GitLab shares fell 7% in after-hours trading.

In a memo to employees and investors, Staples said the process would be conducted “openly,” including a voluntary separation window.. He acknowledged this creates uncertainty for team members over the coming weeks. while the company works toward finalizing the “new shape” of GitLab on or before June 1 where possible.

The CEO laid out that some changes could be delayed where local requirements apply. In those locations, GitLab said it would not make organizational adjustments until local processes are complete—underscoring that the restructuring timeline could vary across geographies.

The workforce reduction is tied, in part, to operational changes.. GitLab said it plans to reevaluate its operational footprint and reduce the number of countries it operates in by up to 30% where small teams exist.. The company said it will continue serving customers in those markets through a partner network.

GitLab also plans to flatten parts of its organization by removing up to three layers of management in some functions so leaders are “closer to the work.” This is meant to shift day-to-day decision-making nearer to execution as the company redesigns how software production happens.

A central element of the plan is a reorganization of research and development. GitLab said its R&D teams will be reorganized into roughly 60 smaller, more empowered teams with end-to-end ownership, a move that nearly doubles the number of independent teams.

To support the new operating model, GitLab said it is “rewiring” internal processes with AI agents.. Staples wrote that the company will embed AI into tasks such as reviews. approvals. and handoffs. with the goal of speeding up execution.. He added that GitLab will “right-size” roles across the company in response to how work changes with automation.

While the restructuring is under way, GitLab framed its changes as part of a broader strategic transition.. The company said it is evolving its strategy for the “future state of software engineering. ” building on the idea that the cost of producing software is collapsing. which should expand demand for it.

Staples offered a market argument for why the company believes timing matters: he said the developer platform market has shifted quickly in perceived pricing power. moving from tens of dollars per user per month last year to hundreds per user per month this year. and potentially to thousands.. The memo also asserted that as software becomes cheaper to build. more builders and more software will follow—an outcome GitLab aims to serve.

The memo further argued that the “consequential work” remains with engineers.. Staples said the supply of deep technical problems is multiplying and that engineers capable of solving them will become among the most scarce and valuable talent in the market—an implicit rationale for why restructuring is paired with a push to refocus on higher-level problem-solving.

GitLab’s CEO also laid out what he described as five architectural bets needed to support what agents do at machine scale.. He said agent-based systems can open merge requests in parallel. trigger pipelines around the clock. and push commits at rates beyond human teams.. That, he argued, is why platforms not built for agent-scale performance are likely to break under pressure.

Among those bets. GitLab said it is undertaking a generational rebuild of infrastructure so it can handle agent-rate work by default.. Staples described efforts that include reengineering Git itself for machine scale. moving away from a monolith toward modern. API-first. composable services. and building agent-specific APIs so agents can interact as first-class users rather than as add-ons to human-shaped workflows.

GitLab also described “orchestration across the full lifecycle” as a key layer.. The memo distinguishes between agent activity and business outcomes. saying enterprises do not need visible agent actions; they need running software that moves the business forward.. GitLab said this orchestration coordinates agents across planning. execution. conflict resolution. policy enforcement. and keeping a human in the loop where it matters most.

Another pillar of the plan is that GitLab views “context” as its superpower.. Staples wrote that while code generation capabilities are spreading across the industry and driving higher AI spending for enterprises. what may not commoditize is the connected context the model gains—linking planning. code. review. security. deployment. and operations across projects and repositories built over years.

On governance. the memo says control will be built into the core of the platform rather than treated as a separate add-on.. Staples argued that as agents take on more work. enterprises will need identity. auditability. policy enforcement. and deployment flexibility embedded by default into how agents. pipelines. and merge requests function.

GitLab also set out a framework it called “one platform. three modes. ” reflecting different degrees of agent involvement: human-owned work. agent-assisted work. and agent-autonomous work.. The memo said GitLab is building a single platform. data model. and governance system that operates across these modes and remains deployable in both cloud environments and with model neutrality.

On business strategy. Staples said GitLab intends to keep a subscription foundation for predictability while introducing consumption pricing for agent-related work. noting that the company has already added such pricing and that other major players have followed suit.. He said GitLab plans to introduce more flexibility as the way work evolves.

For customers, GitLab emphasized continuity. The memo said support, roadmap commitments, and contractual terms would continue without disruption, and that account teams remain available to discuss the changes.

GitLab also pointed to innovation as the proof point it wants to deliver.. Staples said the company plans to treat itself as “customer zero” of its platform for agentic engineering. aiming to show success through its own product and results.. GitLab said it will share the next wave of its innovation roadmap at GitLab Transcend on June 10, 2026.

For investors. the CEO framed the restructuring as a deliberate move to lead in a market he believes is entering its largest shift in about twenty years.. He said the goal is not incremental growth on a DevSecOps platform. but becoming the trusted enterprise platform for software creation in the AI era.

GitLab said it reaffirmed its Q1 and full-year FY27 guidance as the restructuring begins. but that the final scope and financial impact will be shared on the June 2 earnings call after planning is finished and once the company receives board approval.. The memo added that GitLab anticipates reinvesting most of the savings into accelerating growth and specific technology initiatives already outlined.

The message to employees and markets was clear: GitLab believes the restructuring is tied to how software will be produced and managed when machines and agents move faster than human teams.. Now. the company’s next milestones—final planning. board approval. and the June 2 financial update—will determine how large the cuts are. how quickly the organization adapts. and whether the strategy translates into measurable momentum.

GitLab restructuring AI agents software engineering workforce cuts developer platform market corporate governance earnings call