GitLab Inc. (GTLB) Earnings Call Transcript
June 2, 2026
Earnings Call Speaker Segments
Good afternoon, and thanks for being here on this call about GitLab's financial results for the first quarter of 2027. Joining me are Bill Staples, who serves as our CEO, and Jessica Ross, our CFO. Over the next stretch of time, we'll walk through how the business is doing, share our thoughts on the first quarter and the full year, and offer guidance for the second quarter along with fiscal year 2027. Prior to getting into that, let me go over the safe harbor statement. I'd point everyone toward the cautionary language about forward-looking statements, which appears on Page 2 of the presentation we've prepared and in the earnings release that went out earlier today — you can find both in the Investor Relations portion of our website. Within the presentation and that release, there's a discussion of particular risks, uncertainties, assumptions and other factors that might lead our actual results to diverge from what's expressed in any forward-looking statements as defined under the Private Securities Litigation Reform Act. As always, everything said on today's call and shown in the presentation falls under that language. Also, we'll be covering some non-GAAP financial measures during this call. Those non-GAAP financial measures leave out specific unusual or nonrecurring items that management considers to have an effect on how comparable the referenced periods are. For more detail on these non-GAAP financial measures, and for the reconciliations to the most directly comparable GAAP measure, please look at our earnings release and presentation materials. At this point I'll hand things over to Bill. Bill?
I'm happy to share our Q1 results. We posted $264 million in revenue, which is 23% growth, along with $38 million in operating profit, a 14% non-GAAP operating margin, and 1,519 customers who pay us over $100,000 annually — that's an 18% increase year-over-year. Our dollar-based net retention came in at 117%, and these figures helped make clear something that's been growing more evident. The opportunity in front of us is enormous and speed is essential; a few weeks ago we unveiled GitLab's Act 2. Jessica will soon walk through the financial side of the restructuring in detail. I'll use my time to focus on the signal we're seeing around that opportunity and the strategic bets we're placing to unlock GitLab's advantages against this structural tailwind. Our core enterprise DevSecOps business is still going strong. Gross bookings growth reached its highest point in 4 quarters. GitLab Dedicated hit another milestone, reaching $70 million in ARR. Ultimate now accounts for 57% of ARR and appears in 7 of our top 10 deals. DAP brought in more net new ARR during its first quarter than Duo Pro and Duo Enterprise did together in any quarter before, and it was part of 4 of our top 10 deals. Throughout FY '27, our plan is to move Duo Pro and Duo Enterprise subscriptions over to DAP, bringing our AI portfolio together into one agentic platform and shifting onto the consumption business model. Platform activity is climbing too. Code pushes throughout our paid SaaS customer base rose 49% year-over-year. CI pipeline growth sped up from the mid-20s in late FY '26 to 38% in April. One of our most sophisticated agentic customers increased the volume of Code in their repositories by 2.5x within just 6 months, and that's still accelerating. The agentic era is generating structural tailwinds for DevSecOps platforms, and GitLab sits on the critical path to scaling agentic engineering in the enterprise. Let's discuss the 5 growth initiatives I laid out last call. First, accelerating first order growth. We achieved 30% higher new logo growth compared with the same period a year ago. The dedicated first order team is ramping faster than planned, and a strong resurgence in product-led growth gave us our highest absolute first order count in 10 quarters. Why does this matter? It's simple. The changes we've implemented over the past year are letting GitLab compete and win new business at a much faster pace. And while net ARR contribution from many of these customers is small in year 1, history is crystal clear about what follows. Take our 2016 cohort, for instance — it has expanded more than 100 times over the past 10 years. That's the kind of customer journey we're aiming to replicate with every new customer. Second, we told you we're scaling sales capacity. Our FY '26 quota-carrying headcount investments are already driving gross bookings as planned, and we keep growing capacity. Given the timing of these hires and our historical ramp time, consistent with what we shared last quarter, we expect most of the benefit to land in the second half of the year. Now for the third item: the ways we can make money are broadening. I want to point out three particular forces at work. To begin with, our clients are beginning to bring in people who aren't engineers — product managers, designers, and security teams — to work with GitLab and agentic workflows. That means seat counts will rise down the road, and governance, version control, audit trails, and approval workflows become their responsibility as well, opening up a fresh footprint we can expand into. Next, agentic workloads are straining DevSecOps infrastructure well past what it was built to handle. The reliability failures and outages at our rivals, which everyone has been reading about, are coming up in discussions with customers. In those discussions, our cloud-neutral architecture and dependable platform set us apart in a genuine way, and some of the architectural wagers I'll describe shortly will put us in position to seize the agentic infrastructure chance that lies ahead. Third, our consumption business has gotten off to a very strong beginning. Consumption run rate, or CRR, is an internal figure we monitor to measure how quickly GitLab credits are being taken up. We're disclosing CRR this quarter as an early indicator. Still, one quarter isn't enough to prove a meaningful trend, and that's worth stressing, since this marks the close of our first full quarter of consumption. The paid consumption run rate for the Duo agent platform came to almost $20 million. This figure covers minimum usage commitments entered into before GA and during Q1, plus on-demand credits. As adoption of the Duo Agent platform grows and we launch new offerings, paid CRR will probably turn into a more meaningful forward-looking signal of where our commercial model is going. We'll offer more formal metrics and a disclosure cadence once this motion matures further. Fourth, we keep serving customers who are sensitive to price. Headwinds have continued for this group, which represents roughly 20% of our ARR; the efforts around broader coverage and quicker time to value are in motion and will need time to show results. Fifth, we're carrying out our AI strategy. The GitLab Duo Agent platform hit general availability 2 weeks prior to the start of the quarter. And as I noted at the beginning of the call, it added more net ARR in its first quarter than Duo Pro and Duo Enterprise did together in any earlier quarter. As cogeneration speeds up, the AI paradox is genuine. Every customer I speak with outlines bottlenecks in code review, testing, security remediation, pipeline management, and elsewhere. The Duo Agent platform takes on the repetitive engineering workflows throughout the software life cycle, freeing engineers to concentrate on work that matters. Even so, the pattern beneath these figures is what counts most. DAP is opening the door to additional AI budgets that go beyond what's already spent on DevSecOps. That's a commercial dynamic distinct from seat expansion, and it alters the opportunity we can address within accounts. We also revealed broader relationships with AWS, Google Cloud, and Anthropic during the quarter. Spending on the Duo Agent platform can now count against committed cloud budgets on the Google, AWS, and Anthropic marketplaces, eliminating a genuine procurement sticking point. A single customer example makes this dynamic tangible: a top 10 U.S. A Duo Agent platform pilot was operated by the bank covering routine engineering workflows; throughout Q1, per task developers saved 1.5 hours on average, and an active rollout now reaches hundreds of developers, with adoption plus daily credit consumption rising quickly. Every cohort accelerates its ramp compared with the one before. Moreover, according to the customer's present rollout plan, once fully deployed later this year, the active user base should expand by almost 20x. Now I'd like to pass along what we learned from the changing environment and discuss the direction the market is taking. Our Executive Advisory Board meeting took place recently, and there we gathered leaders from our biggest and most strategic customers. From that event I wanted to share 3 insights, since they help show where the market is headed along with GitLab's expanding value proposition. To start, the Head of Engineering at a major technology platform described it this way: agents resemble psychopathic interns. Good judgment is missing, and there's no human who would go to jail for particular decisions — but what happens with an agent? No legal answer exists for that question as of yet. Governance and control is a problem at the systems level that requires an answer at the platform level. That platform happens to be GitLab. Second, upon hearing our road map, the Head of Software Engineering at a top 10 bank said he would purchase the entire platform the following day. Tool optionality for developers was his single stipulation.
Put differently, there are two sides to what GitLab offers. First, neutrality across clouds, models, and tools, plus all the surrounding work around cogeneration — the testing, the controls, the governance. And then there's this: one customer who oversees more than 200,000 repositories explained that configuring governance project by project is simply no longer possible for them. Their ask is for something they describe as mission control logic — policy applied at the platform layer throughout their whole estate. That's a problem of machine scale, and it's one of the architectural bets I'll get into shortly. The indicators coming out of our Q1 results and from customers are powerful, but to make the most of our capacity to seize this chance, we need changes in how our infrastructure is monetized and in how we run things. I detailed those in my Act 2 letter. What follows are the 5 architectural bets we're making to deliver fresh value to customers, put ourselves in position to gain even more from AI's structural tailwinds, and broaden our monetization vectors. Next week's Transcend will be live streamed on our website and will truly bring these to life. Okay, Bet #1, machine scale infrastructure — agents operate at machine scale and they're forcing competitors to the brink; during this quarter, we started a generational rebuild of Git to handle the scale and features that 100x growth demands. This scale requirement is something that never existed previously and has turned into a genuine pain point for every team on their agentic journey. We're working with an AI lab on designing and implementing the new service, including APIs optimized so agents can store and retrieve context, code included. As today's leading contributor to Git, we have a right to win this layer of infrastructure. You won't want to miss the demo next week. Bet #2 concerns orchestration. Agents generate activity, but what businesses require is software that produces business outcomes. Orchestration is the link between those two. For years we've been connecting and automating the steps of software delivery through our CI/CD pipelines. We own the assembly line for code — building, testing, shipping and securing it in a defined sequence — and with Duo Agent platform, GitLab can now coordinate software development life cycle tasks between humans and agents. The following step extends our agentic infrastructure across artifact management, governance and compliance and continuous deployment. With these new services, value scales alongside the work performed, exactly as it does with Duo Agent platform. Architectural Bet #3 is entirely about context. Code generation is commoditizing quickly and enterprise AI bills are rising as quickly as adoption. What isn't commoditizing is the connected data model spanning every project, every repo and team built up over years; we're creating a first-class API accessible service named GitLab Orbit that boosts outcome quality and lowers the cost of agentic actions. Orbit access will be monetized via consumption credits and will hold value for both DAP users and external agents, Claude Code, Cursor, Codex, whichever ones customers pick. Context is a compounding asset. Each human and agent action actually makes it richer. Architectural Bet #4 concerns governance. When we think about adoption at enterprise scale, governance isn't something you can treat as optional; that's why identity, audit policy, and flexibility in deployment are being built as core platform services right from the beginning. As a result, each agent pipeline and merger request passes through those services automatically. This extends the work that sets GitLab Ultimate apart already, and at Transcend next week you'll see further developments in that space. Our fifth architectural bet is that having a single platform covering every mode of software engineering will deliver enormous value to customers. Today's world holds trillions of lines of code, and the bulk of that code cannot and will not be rewritten in the near term. Over the next 10 years, software teams are going to build and manage software in 3 ways. They will follow the manual human software development life cycle approach that we've led with for the past 10 years. They will apply agents to tasks, as they currently do through the Duo Agent platform, and they will move into autonomous agentic engineering. Much like what happened in the cloud era, picking a vendor strategy that divides your infrastructure from your developer experience is a painful and expensive decision. GitLab customers are spared that. GitLab stands alone as the platform that already covers planning, coding, reviewing, securing, deploying, and operating, with a single control plane, a single data plane, and governance beneath it all. Bringing in autonomy extends the platform rather than creating a separate stack. Customers receive one location to manage all of their software systems, with neutrality across cloud and models. That's the structural edge competitors just cannot replicate. I'd also like to discuss GitLab Flex. As you can see, AI workloads are shifting how cost, value, and predictability relate to one another, so our business model has to adapt accordingly. Consumption is the appropriate model for that. That's why we brought GitLab Credits into our business, and it's growing clearer that customers require still more flexibility in the way they use our platform. So next week at Transcend, we'll be introducing GitLab Flex, a buying program allowing customers to combine seat-based and credit-based products in ways we think will be exciting both for them and for GitLab. We're eager to tell you more then and in the coming quarters. Let me wrap up with 2 customer stories from the quarter; they make a simple point. The problems GitLab addresses, security, compliance, and governance at scale, only become tougher in the agentic world that lies ahead. Zillow Group runs the largest real estate marketplace in the U.S. and has been a GitLab customer for more than 10 years. Their internal AI-powered pipeline engine produces thousands of GitLab projects and pipelines. AI scale workloads brought in by Zillow's coding agent providers and Zillow's internal agents have created fundamentally different infrastructure needs, as AI-assisted workflows help engineering teams ship 40% more code per engineer and concentrate on broader development priorities. This quarter, they are moving over 2,000 engineers to GitLab Dedicated in order to strengthen security and compliance through platform-level enforcement and to scale alongside AI-driven growth; they're also piloting GitLab Duo Agent platform as the context layer that makes their AI investments even more effective. CSL Behring is a worldwide biotech frontrunner and one more longstanding GitLab client. This quarter they committed across multiple years to GitLab Ultimate plus the Duo Agent platform, which takes the partnership even deeper. What they faced wasn't merely the job of pulling scattered tools together — they also had to build out an AI development capability that their AI Governance Board would sign off on, and GitLab's consolidated platform delivered enterprise model controls, logs, and security analysis, all baked into the very pipeline their developers already work in. Before passing things to Jessica, I'd like to pause and express gratitude to every team member who played a part in getting GitLab where it stands now, among them those leaving as part of the workforce changes tied to Act 2. The effort you put in here counted, and it still counts. You joined GitLab at the moment we required you. You built the groundwork we stand on now. Thank you. What's in front of us isn't incremental growth on a DevSecOps platform; at this point we sit on the critical path toward scaling agentic engineering across the enterprise and toward becoming the trusted enterprise platform for software creation in the agentic era. I'm genuinely excited about our Transcend event happening next week. You'll see Orbit. You'll see Flex.
You're going to witness agents operating Git at a scale of 100x, along with our initial shipment of autonomous engineering. The next chapter begins right there. The finest days we've ever had lie in front of us. Having said that, I'll hand things over to Jessica.
Thanks, Bill, and I’m glad everyone could join us today. I’ll cover three things right now: what took place in the first quarter, the factors driving those results, and how we see the rest of the year shaping up. Revenue came in at $264 million, up 23% year over year, and that topped our guidance by 4 points. Our enterprise segment delivered a strong performance, with that momentum distributed pretty evenly across geographies. The public sector likewise outperformed what we had expected, and GitLab Dedicated passed another milestone, reaching $70 million in ARR. Beyond that, the quarter benefited from $2 million in nonrecurring overages plus early renewals. All of this occurred while the macro backdrop stayed challenging. As we had anticipated, the roughly 20% of ARR represented by our price-sensitive cohort remained under pressure. Across the company, seat contraction was heavier than we had forecast, mainly due to layoffs at our customers. Contraction related to M&A added another headwind. Without those dynamics, this quarter would have looked even stronger. It’s within enterprise that GitLab’s platform really demonstrates its worth, and there we continue to see resilience. Customers spending more than $100,000 grew 18% from a year ago, reaching 1,519, and they now represent slightly over 75% of ARR. We currently have 10,831 customers paying us $5,000 or more in ARR, and that accounts for more than 95% of our total ARR base. Gross retention remains comfortably above 90%, in line with our historical experience. Dollar-based net retention came in at 117%. As we expected, that tale of two cities we’ve mentioned before is still playing out. Larger customers displayed healthy spending behavior, while pressure in the mid-market and SMB segments weighed on net retention. Total RPO rose 18% versus a year ago, reaching $1.1 billion. Current RPO increased 24% to $724 million. Let’s go further down the income statement now. Non-GAAP gross margin was 88%, as SaaS continues to grow as a share of our revenue mix. Subscription offerings now make up nearly a third of all revenue, having grown 37% compared with the prior year, fueled by ongoing traction in GitLab Dedicated and Duo. For Q1, non-GAAP operating income was $38 million, up from $26 million in the same quarter last year. Our non-GAAP operating margin was 14%, about 200 basis points better than twelve months earlier. Turning to JiHu, non-GAAP expenses for Q1 totaled $3.1 million, which matches the $3.1 million figure from the same quarter last year. Our objective remains to deconsolidate JiHu, though neither the likelihood nor the timing of such a step can be predicted. Adjusted free cash flow was $147 million, producing a free cash flow margin of 56%. The timing of collections worked in our favor here. Before I move into guidance, here’s a brief capital allocation update. The framework I laid out three months ago is still guiding us today: prioritize investing in growth, maintain a robust balance sheet, and lean on share repurchases to create shareholder value while controlling dilution. All three showed up in Q1. At quarter's end, we had $1.36 billion in cash and investments, repurchased about 2.4 million shares, and have $350 million remaining under the authorization. Now for guidance. Let me take you through our key assumptions for the remainder of the year. I'll begin with our Act 2 plan, announced last month. A core element of that plan is reorganizing our workforce. Our objective is an operating structure that sets us up to seize future opportunities. In the original announcement, we noted that we worked hand in hand with our teams to reshape the business as efficiently and transparently as we could. Those decisions are nearly finalized, and we anticipate that about 14% of our staff — 350 people — as of January 31, 2026, will be affected. In addition, we intend to leave 22 countries and shrink our team member geographic footprint by approximately 37%. We're flattening the organization, which means eliminating as many as 3 levels of management. We expect pretax restructuring charges of $30 million to $35 million, with approximately $19 million landing in Q2. The rest should largely be recognized across the next 3 quarters. Most of the savings from this restructuring is expected to be reinvested into a limited set of targeted initiatives meant to speed up our Act 2 strategy. These include investing in our team members, reallocating resources to lean into the architectural bets Bill described, and scaling internal AI tooling together with its associated costs. On top of that, our outlook bakes in caution around 4 key items. Let's begin with the broader picture. Public sector results improved this quarter, but we aren't assuming a meaningful recovery for FY '27. We also continue to believe the group most sensitive to price — about 20% of ARR — will remain under pressure. Second, despite encouraging early signals, our FY '27 assumptions still factor in no meaningful revenue from the GitLab Duo Agent platform, and there's $50 million set aside in that outlook. What we're focused on this year is moving pilots into production and helping new adopters scale. Third, job cuts are accelerating and falling mainly on tech, which is causing customers to behave more cautiously. And fourth, as we implement Act 2, some near-term turbulence from the organizational changes is possible. When we examined any restructuring affecting quota-carrying sales team members, keeping the business operating smoothly was a top priority. So we deliberately chose to offer a voluntary separation program. The aim was to head off potential attrition later tied to the changes we made. Even so, short-term disruption is unavoidable when changes are this significant, and our guidance accounts for that. Given what we delivered in Q1 and the continued progress we're seeing across our 5 strategic priorities, we're raising our guidance for the full year. For Q2 FY '27, we expect total revenue to land between $272 million and $274 million, representing growth of about 15% to 16% versus the prior-year period. Looking forward, we're forecasting non-GAAP operating income in the $30 million to $32 million range. We also expect non-GAAP net income per share of $0.17 to $0.18, based on 168 million weighted average diluted shares outstanding. Now for the full year: our revised guidance anticipates total revenue of $1.112 billion to $1.118 billion, reflecting growth of approximately 16% to 17% over last year. On non-GAAP operating income, we're looking at somewhere between $135 million and $141 million, and non-GAAP net income per share should come in between $0.79 and $0.82, assuming 166 million weighted average diluted shares outstanding. A few more items I want to flag for modeling purposes. To start, our gross margin guidance for the full year remains in the 85% to 87% range. Second, we expect profitability to bottom out in Q3, due to the timing of investments following restructuring. And third, we're anticipating approximately $15 million of expenses related to JiHu, compared with $13 million a year ago. Throughout this year, we're making intentional investments designed to seize the Act 2 opportunity. The financial strength we've established — exceeding $1 billion in run rate revenue, producing robust cash, and carrying $1.36 billion on the balance sheet, including $50 million — is the foundation from which we invest, rather than something we invest to reach. That's exactly what gives us the room to redirect resources toward our highest return initiatives while also returning capital to shareholders. The opportunity in front of us is larger than any we've had before, and the base we're funding has never been more solid. Thank you for being with us. With that, I'll hand it over to Yao, who will lead the Q&A.
Operator, we’re ready to begin. Our first question will come from Matt Hedberg at RBC, and after that, we’ll hear from Sanjit Singh with Morgan Stanley.
Congratulations on the quarter. It's genuinely wonderful to witness things leveling off during this period. So, Bill, my question is for you: given everything innovative your team keeps rolling out, could you describe what competition looks like right now? To be specific, when it comes to GitHub, how have win rates been moving? Are prices staying firm? Any details you can offer there — it seems like your company is enjoying a good deal of momentum lately.
Many thanks, Matt. Indeed, the setting we find ourselves in is quite fascinating. Agents are pushing infrastructure demand beyond anything people previously managed or even could manage, and as everyone has witnessed, that's pushing some rivals right to the edge; keep in mind that each competitor serves a distinct blend of audiences. Our attention stays firmly on enterprise clients. Consequently, our communities differ, our tempo differs, and far greater consequences ride on what we deliver to those clients; genuine potential clearly exists for us here. Still, bear in mind that for those we serve, this workload is absolutely essential to operations. Moving it elsewhere is difficult and demands patience, particularly when you're talking about enterprise scale. The reason is that choosing GitLab as a platform amounts to a foundational infrastructure choice. Getting there means the whole organization must come together and commit to it. It isn't like a person simply installing some tool on a laptop. Therefore an abrupt reversal shouldn't be expected, yet here's what we are observing. During Q1, we witnessed a significant rise in large companies seeking to bring GitLab in as their platform, encompassing fresh initial purchases plus consolidation across our current customer base; that produced a modest yet meaningful year-over-year gain compared with win rates from prior periods. And as I noted during the prepared remarks, we likewise observed a turning point in the number of first orders. That figure now stands 30% above where it was year-over-year, stemming from combining product-led and sales-led growth initiatives we've spent the last few quarters putting money behind. We're executing focused go-to-market campaigns aimed at capturing this chance, and initial outcomes are appearing. However, what I'd highlight for investors as carrying even greater weight is something I brought up earlier on this call. We're working alongside an AI lab on designing and developing what our Git infrastructure will become. Our design target for that effort calls for 100x scale relative to what people require presently, since we expect enterprise customers will need exactly that as we progress beyond early adoption of agentic engineering toward entire teams adopting agentic engineering practices. So that represents a genuinely fresh and thrilling prospect for us. You'll hear additional details next week at Transcend, and I'd urge you to listen in.
Sanjit Singh with Morgan Stanley has the next question, and after him it will be Radi Sultan from UBS. Sanjit, the floor is yours.
Oscar Saavedra here, filling in for Sanjit. Perhaps I could dig a little deeper into the guidance and whether there have been any shifts in the philosophy. You mentioned anticipated gains from expanding sales capacity during the back half of the year. Yet there's also talk about a difficult macro environment, and you've factored in that it won't get better moving forward, plus possibly some execution-related turmoil. So I was hoping to understand, perhaps with more precision, the greater caution being built into the guidance compared with what you're actually observing in the market right now?
Yes. Thanks for asking. A few points. Regarding the prior quarter, we intentionally provided a broader range, and we pointed to numerous moving pieces within the business. When we consider how this quarter has unfolded so far, our assumptions have mostly materialized as anticipated. We've now completed 1 quarter in which we exceeded expectations on both revenue and NGOI. And once more, keep in mind, the business is mostly ratable, and our visibility is extremely strong. When we think about added prudence, as we mentioned, we did experience some effects from churn and contraction tied to risk, and we had certain items specific to this quarter connected to M&A. And once more, with a sizable — despite being extremely deliberate with the RIF about safeguarding quota-carrying sales capacity and our engineering head count, we recognize that with any large-scale RIF, there's some possibility of disruption. So we've incorporated that into the guide too. So I'd list the 4 items, again, with 2 continuing from the prior quarter. We don't — although we witnessed solid performance in PubSec this quarter, we still don't anticipate an instant rebound. And while we're extremely happy with what we're seeing on DAP thus far, we aren't anticipating meaningful revenue from it. Then the fresh additions are the RIFs and the execution risk.
Next question, Radi Sultan from UBS, followed by Ethan Weeks from Piper.
Great. Bill, during your prepared comments, you brought up the chance to attract additional nontechnical users onto the platform. What I want to know is, how do you envision making money from those users? Do you believe the existing SKUs adequately capture what that group needs? Perhaps you could simply take us through your thinking on how you'd shape the product and the monetization opportunity so as to capture that growing cohort of nontechnical users?
Yes. This quarter saw a noteworthy rise in customers requesting and looking into extra seats for those nonengineering users. I believe it's come up a handful of times over recent quarters — are we witnessing that possibility — and although we had a few discussions this quarter, a pattern was emerging more clearly, in which teams are choosing to have project managers, designers, program managers and others start contributing code with agentic tools. Naturally, they require GitLab seats to do so, so they can contribute to the code repository and make use of the CI pipelines and all the rest we offer. Right now we're in several such discussions, and we're proposing the very same seat-based pricing model we give engineers, since the value and the requirements match. Thus we expect our seat-based model to gain from these discussions, along with our Duo Agent platform, approach, because those users share identical requirements when it comes to agentic engineering throughout the software life cycle.
Ethan here, filling in for Rob this evening. Bill, I'd like to ask about this effort to rebuild Git, and the significantly bigger scope you're pursuing with it. In particular, the remarks you made regarding a partnership with an AI lab tied to that vision. In the past, there have been some concerns about those AI labs wanting to handle this themselves, or turning into rivals of yours. So I was hoping you could speak to why they chose to work with you on developing this instead of attempting to go head-to-head with you.
There are likely several reasons behind that. First, as I see it, we're the top contributor to the open source Git community right now. On top of that, we provide GitLab to a number of those AI labs; so being both a customer and a prominent GitLab and Git open source contributor likely played a part in their decision to join forces with us. Beyond that, I think we currently serve over 50% of the Fortune 100. We're a major DevSecOps player in this space, with hundreds of thousands of organizations relying on GitLab at present, and they want to provide an excellent experience to their customers via GitLab. So the partnership has been excellent. During next week's session, you'll get to see the demo, which will cover the latest progress on it along with further specifics.
Great. Next question, Derrick Wood from TD Cowen, followed by Matt Calitri from Needham.
Cole here, filling in for Derrick. Bill, would you mind expanding a bit on the seat compression you're observing and what you anticipate happening with it? Then, on that same topic, how might the new monetization approach assist in counterbalancing that within the model?
In fact, during this quarter we've observed seats increasing. Clearly, given the expansion we achieved, seats did rise; that remains our main monetization approach at present. I believe Jessica referenced some churn along with contraction and M&A activity specific to this quarter, and absent those, the quarter would have come in even stronger, yet seats are certainly increasing. Regarding new monetization, our GitLab Credits consumption program is likewise assisting us in beginning to capture new AI budgets, as I noted. It has also given us our strongest net ARR quarter, our best AI quarter ever. As I said, it exceeded expectations in its first quarter, with Duo Pro and Duo Enterprise together surpassing any prior quarter. And I think we've been in the Duo business for 2 or 3 years. So that's an impressive beginning for the GitLab Credits program and the Duo Agent platform, and seats keep on growing.
Right. And on that note, I'd say AI workloads are truly shifting how cost, value, and predictability relate to one another, and we view all of this as additive, giving our customers greater optionality and flexibility.
Great. Next question, Matt Calitri from Needham followed by Kingsley Crane from Canaccord Genuity.
Thanks; Matt Calitri here, filling in for Mike Cikos at Needham. Could you give us details about which areas you plan to put restructuring savings back into so that the architectural strategy Bill described can be driven forward? Also, what method will you use to gauge ROI on those changes?
Yes. No, that's a terrific question. Thank you; so honestly we see it across 3 areas: people, technology and process. Through a people perspective, we're requesting a great deal from those remaining with us for Act 2. And we want to make sure we put money into them and keep them, since they will be — take on a very important part in this journey. Next, regarding technology. We're truly committing to the architectural bets Bill set out in his script. And we will be shifting and directing R&D resources so our road map speeds up. Once more, we're genuinely eager to reveal more at Transcend next week. So be sure to look at that. And last, through a process perspective, we're examining our processes so we can leverage AI and move more quickly as an organization. And I think this aligns closely with our capital allocation strategy; we hold strong conviction that this is genuinely the finest route to durable growth, operating leverage and long-term shareholder value. And then regarding the second point, through an ROI perspective, look, it's genuinely too soon to give details, but we are, as with everything else, going to be extremely deliberate about how we invest, with clear guardrails and the proper trade-off. I think we're very clear eyed about both the risks and opportunities, but I believe the market opportunity here is too big for us not to capitalize on it now.
Next question, Kingsley Crane from Canaccord, followed by Howard Ma from Guggenheim.
Thanks. Bill, there's plenty of chatter going around, but before anything else, I want to praise how candid you were in the Act 2 letter — the transparency you're showing and the way you've steered things through a tough yet decisive period, and you've handled transitions in the past. So I believe we all recognize it comes down to people and trust, not merely technology; with that in mind, two things. First, let's discuss talent. Could you speak to deep technical problem solvers being the rarest, most precious asset? What's your read on attrition across the last couple of weeks, and more broadly on keeping 10x engineers? Then, regarding disruption, I realize the guide mentions some market disruption, yet the letter commits to no customer disruption. Could you give us more assurance on that side?
Yes. Thanks, Kingsley. Certainly, these periods are hard for any business to go through. Perhaps I should take a moment and once more say how thankful I am for everyone we parted ways with and those in consultation, which began yesterday; we truly value what all who've been at GitLab contributed — both those who left and those who opted for the voluntary departure. They joined when GitLab required them. They accomplished incredible work, and the basis they established is what we'll keep building upon. We took great care in how we approached the restructuring. Actually, as you can likely see from the leader — from the letter, we began by plainly spelling out the why, our view of the market, where software engineering is headed, the first principles behind our future investments. After that we laid out the what, the product strategy, business strategy too, for pursuing the opportunity. Then we addressed the how with team members; plus a few of the hard problems we're working to solve so we can move quicker as an organization and seize this opportunity; that covers some items I mentioned in the letter, such as shrinking our operational footprint and cutting management layers, letting us decide faster and move communication faster. We're additionally creating smaller teams within R&D. So all of that — I bring up all this context because it relates to your retention question; it matters greatly that team members grasp the changes we're making and the opportunity in front of us and feel as enthusiastic as we do, which is yet another reason we actually launched the voluntary departure program, since we recognize this is a great deal of change and perhaps it isn't for everyone, and we aimed to prevent future attrition by offering those team members who arrived maybe in a different era with different expectations the chance to leave if the new direction didn't excite them. So that's now been carried out. We took real care to safeguard our selling capability, making sure we stay on track to hit the goals we laid out for this year. And as we told you, we're putting money into our people too — especially in R&D. In fact, over the next few quarters we anticipate expanding our capacity there, and that's so we can follow through on those architectural bets. We're putting investment into our team members, and R&D spending will keep going as well, so that delivery happens as fast as we possibly can.
Turning to what you mentioned about exposure to customers, that's quite minimal. In the regions we've pulled out of, we never had any sales footprint, and in places where customers are present, we're handling those transitions in a highly intentional way, supported by a communications plan that's tightly focused.
Great. Next question, Howard Ma from Guggenheim, followed by Nick Altmann from BTIG.
I'd like to get clarity on a couple of points, and I'll put both of them out there at once. First, regarding that $20 million figure for annualized consumption on the Duo Agent platform — I want to confirm whether it's a clean number, meaning it excludes any Duo Pro or enterprise spending that got converted into DAP commitments. Then my second item concerns the 30% growth in new logos. Could you help bridge that to the net additions of customers with greater than $5,000 in ARR? What I'm seeing is roughly 149, though that was lower — perhaps that mirrors the one-time tech-related layoffs along with M&A-related churn.
Starting with DAP, yes, it is a clean number, though I want to be very, very clear that nobody ought to be plugging this into their models. It's a very early signal — one we're excited about, but at the same time, it's like 1 quarter's worth of data. Our forecast isn't based on that, and I hope yours isn't either. Then on the customer count, once again, the bottom layers can get pretty noisy. I'd point you back to looking at it holistically. I think the big message is that our enterprise business remains strong. Our $100,000 customer cohort grew 18%, and I'd again encourage everyone to view this really through a more holistic lens.
We'll take our next question from Nick Altmann at BTIG, and after that, Raimo Lenschow from Barclays. Nick, please proceed.
Jessica, could you give us a bit more detail on bookings? My understanding is you mentioned gross bookings came in quite strong, yet it looks as though there may be some distortion showing up in deferred revenue, since total RPO growth quarter over quarter was somewhat softer than what we've seen historically. So could you break apart that gross booking momentum you referred to and set it against RPO and billings growth?
Let me zero in on the forward-looking metrics. Once more, I'd say the broad takeaway is that you can combine billings, cRPO, RPO and the total figure to get a read on the business, though each one carries its own particular wrinkles. Ultimately, in my view, revenue gives us the clearest line of sight, and that's the number we guide on. But yes, starting with guidance: those came in at 12% growth for this quarter, and that followed an especially hard comparison, since we posted 35% growth in Q1 of FY '26. As I mentioned earlier, we saw larger seat contraction during that period than we had expected, and it was largely connected to layoffs among our customers. On top of that, we experienced some M&A-related contraction that was genuinely specific to that quarter. Absent those forces, the quarter would have looked even better, and we have a very clear-eyed view of that. Regarding the remaining forward-looking metrics, let me spend a moment on RPO. There are a few points worth flagging. True, we are picking up somewhat more uncertainty across the market, and that is producing greater customer hesitation around longer-dated agreements, yet we have consistently taken pride in letting customers choose and in meeting them wherever they happen to be, and offering flexibility in contract terms is one of the ways we've delivered on that. At the same time, we are quite focused on giving the field incentives to secure more multiyear contracts where that makes sense. Still, returning to the discussion about monetization, over the longer horizon we see a chance to change how we monetize alongside our customers as developer unit economics shift, and that is precisely why we keep broadening our portfolio through Flex and other monetization avenues, about which you'll hear more at Transcend. But stepping all the way back once more, it always pays to examine this through our retention rate, which remains comfortably above 90% and, to my mind, is what really reflects the underlying health of the business.
All right. Our next question comes from Raimo Lenschow at Barclays, and after that we'll hear from Ryan MacWilliams at Wells. Raimo, please go ahead.
Amy Carl here, filling in for Raimo. Could you give us some insight into how we ought to frame the recent momentum within your self-managed business? We saw that self-managed subscription revenue came in roughly flat versus the prior quarter — the first such occurrence since the IPO — and we're wondering whether that related to Core Pacific seat contraction as well as M&A?
Yes, whenever we approach customers, we present three options: self-managed, dedicated, or multi-tenant cloud. And truly, that stands as one of GitLab's strong value propositions, since you pick whichever cloud you wish to deploy, and from there it falls to our customers to make that call. And I believe we called out that multi-tenant and dedicated cloud growth came in higher during this quarter, which naturally offsets the self-managed growth you seem to be pointing to there; so those fluctuations do appear from time to time. Customers hold control over where they wish to deploy. And we continue to see a strong signal on the cloud side, which has been a trend ever since the IPO. So beyond the dynamics of what customers select, and where customers select to deploy, there's nothing further to note.
Great. Next question, Ryan MacWilliams from Wells, followed by Lucky Schreiner from D.A. Davidson.
The move toward charging per seat for people while billing agents by usage is something I really like. My guess is that additional software companies will follow suit. Regarding the Duo Agent platform specifically, credits come bundled within the premium and ultimate tiers. I realize it's still very early, but how frequently do accounts exceed the credits that come bundled? Do you expect that, because of this, customers will move toward yearly credit subscriptions throughout their organizations? Also, which use cases are driving the most adoption of GitLab Duo Agent among customers right now?
Yeah. Those bundled credits you mentioned are promotional ones we provided during this initial quarter of availability, allowing individual developers and engineers to try out the Duo Agent platform prior to their organization having to make a commitment. Among some early-adopting customers, we are indeed seeing solid usage of those. Worth noting, as I've mentioned during earlier quarters, a substantial portion of our revenue — 70% — comes from self-managed, and upgrading to a build containing new capabilities such as Duo Agent platform can take as long as 2 quarters for those customers. So the early adoption observed in Q1 comes mostly from our SaaS customer base on gitlab.com. We aren't disclosing figures regarding the patterns we're observing; it remains too soon to disclose how many customers exceed those promotional credit amounts and where their usage settles, yet we are seeing solid early adoption, and we'll keep pushing that forward. On the use cases you inquired about, we're experiencing quite solid adoption among our top 5 use cases, which include, for instance, code reviews — something that virtually every code change needs when fixing failed pipelines. We also have a fantastic feature for security vulnerability resolution: once our scanners detect a security vulnerability, you can have Duo Agent platform automatically generate a merge request addressing that vulnerability, so the engineer only has to come in, review the vulnerability, and approve it. Plus we offer Duo Developer capabilities enabling engineers alongside nonengineering users to take requirements and specify a set of tasks for the agent, and the Duo Developer agent carries those through all the way to creating an MR and eventually to deployment; so across our top 5 use cases, we've enjoyed considerable success, and they deliver a proven ROI that we now sell with customers when going to market.
<<operator_script>>. Next question from Lucky Schreiner, D.A. Davidson.
I'd like to pick up on something said earlier regarding how long deals are lasting and the fact that they're getting shorter. Just to be clear, is this entirely a macro issue? Or does part of it come from customers being cautious about the pricing adjustments you've introduced, wanting to be sure that with consumption they're comfortable with the visibility available to them, or perhaps you could go a bit deeper on some of these shifts in deal length.
Yeah. What I believe you're getting at is multiyear contracts, and Jessica laid out roughly 3 dynamics there. First, particularly in our space, which relates to software coding, quite a bit of uncertainty exists because the software engineering life cycle is shifting, new tools keep appearing, more spending is moving toward AI, and customers are seeing all those possibilities — above all when budgets are constrained. They're opting for shorter agreements since the landscape is evolving so quickly. That uncertainty is widely recognized. Second, we're extremely accommodating toward customers. Should they be in a position to select a multiyear option, clearly that works well for us, and we give our field teams incentives to pursue those. Yet should they prefer a single year agreement, which may stem from various reasons on their end, we're glad to accommodate that too. And last, there's genuine opportunity in this area. The unit economics for developers are shifting quite substantially. Consider the past: our ultimate seat price today, the retail price, stands at $99 per user; however, when you factor in AI tools, what companies are spending per engineer is transforming substantially. So in many respects, I think customers recognize this too. They're making choices, carefully considered ones, regarding what they're prepared to spend this year and monitoring those patterns closely to ensure their multiyear agreements remain in check. That's likewise an opportunity for us. As I said, we're launching Flex next week; and it will create new avenues for customers to commit across seats and credits, which we're enthusiastic about. We'll tell you more next week.
That's all the questions we have lined up, so this wraps up the Q&A portion. This week we'll be attending the Bank of America Global Tech Conference, and we're eager to connect with plenty of you face to face. Thanks for joining GitLab's First Quarter and Fiscal '27 Earnings Call. You're welcome to disconnect at this point.
Read the full transcript via the API
You're viewing the first half of this call. Get the complete GitLab Inc. transcript - plus 131,000+ transcripts from 7,000+ companies, speaker segments and full-text search - through the EarningsAPI REST API or hosted MCP server.
Get an API key View API docs →For developers and AI pipelines
Programmatic access to GitLab Inc. earnings transcripts and 131,000+ others is available through the
EarningsAPI REST API and the hosted MCP server.
Quarterly plans from $162 - full transcripts, speaker segments, full-text search,
and the /api/v1/transcripts/recent polling endpoint for ETL pipelines.