GitLab (GTLB) Q2 2027 Earnings Call Transcript

GitLab reported Q2 FY2027 revenue of $286.3 million, up 21% year over year and roughly 5 percentage points above guidance, while non-GAAP operating income reached $42.6 million for a 15% margin. Net ARR rose 42%, first orders more than doubled to 1,700, and deals of at least $500,000 increased more than 150%, supporting record gross bookings and a raised full-year revenue outlook of $1.129 billion-$1.133 billion. The new Flex consumption model secured more than $20 million from over 130 customers in six weeks and helped paid consumption run rate exceed $40 million, though conversion from self-managed licenses could defer up to $13 million of FY2027 reported revenue through recognition timing. GitLab repurchased 3.5 million shares and had $245 million remaining under its authorization.

Analysis

GTLB's reacceleration changes the central debate from seat-growth durability to whether the company can monetize AI-driven workflow volume without sacrificing its software-like margin profile. The key competitive implication is pressure on Microsoft/GitHub: GitLab's integrated security, CI/CD and governance stack is most valuable where enterprises want to control agent-generated code rather than merely generate it. This favors GTLB in regulated verticals and could shift budget from point tools such as Snyk and CI/CD vendors, although Microsoft retains distribution leverage through Azure and Copilot bundling.

The near-term valuation issue is accounting, not demand. Flex can make reported revenue and current RPO look artificially softer while cash commitments and total RPO remain healthy; the market may initially discount this complexity, creating volatility around the next 1-3 earnings prints. Conversely, management's consumption-run-rate target is not equivalent to recognized revenue or proof of durable incremental spend: a meaningful portion could be reallocated seat budget, and gross-margin risk rises if hosted AI workloads become a larger share of mix.

Over 6-18 months, the upside case requires Flex to convert procurement simplification into net expansion, not just churn mitigation. The most important falsification signals are slowing net retention, consumption run rate missing the year-end target, a deterioration in gross margin below the guided range, or evidence that large customers use external agents while retaining GitHub as the system of record. The restructuring and elevated China-related expense also mean that apparent operating leverage should not be extrapolated mechanically.

Contrarian view: the market may over-credit the AI narrative before the company proves that agent usage produces high-margin paid consumption rather than infrastructure-intensive activity. However, the more underappreciated bull case is that AI expands the addressable user base beyond developers; if governance requirements force newly empowered business users into enterprise software-development controls, GTLB's Ultimate mix can support both retention and pricing power.

Key Decisions for Investors

• Initiate a 6-12 month long GTLB position on post-earnings or Flex-accounting-driven weakness rather than chase an initial gap; size modestly until Flex conversion cohorts are disclosed. Thesis is multiple expansion from sustained mid-teens-plus growth with durable operating leverage; exit/reduce if dollar-based net retention reverses or paid consumption run rate materially misses management's year-end target.
• Express relative share-gain with long GTLB / short MSFT in equal dollar beta-adjusted size for 3-6 months only if GTLB underperforms following revenue-recognition noise. The trade isolates the possibility that integrated DevSecOps captures incremental agent-governance spend; principal risk is GitHub Copilot bundling or Azure procurement leverage overwhelming product differentiation.
• Do not treat the reported consumption run rate as a revenue proxy. Set an alert for the next two quarters: if total RPO and cash collections remain resilient while current RPO decelerates, view the divergence as accounting-driven and add to GTLB; if total RPO also weakens, avoid adding because the Flex thesis is not offsetting underlying demand risk.
• Watch gross margin and hosted-workload disclosures at the next earnings release before using calls. A sustained margin outcome below the guided range would indicate that AI inference, runners, or infrastructure costs are more economically material than management suggests and would undermine the high-multiple software thesis.