Home / Transcripts / GitLab Inc. (GTLB) · September 1, 2026

GitLab Inc. (GTLB) Earnings Call Transcript

September 1, 2026

NASDAQ US Information Technology Software earnings 59 min

Earnings Call Speaker Segments

Nic Edwards executive
#1

Good afternoon, everyone, and thanks for joining GitLab's earnings call covering financial results for the second quarter of 2027. I'm Nic Edwards, Vice President of Finance, Strategy and Operations. Joining me today are Bill Staples, who serves as our CEO, and Jessica Ross, our CFO. On this afternoon's call, we'll walk through an overview of the business, share commentary on how we performed in the second quarter and for the full year, and offer guidance covering the second quarter and fiscal year 2027. Beyond the prepared remarks we'll deliver today, you can find further details in our shareholder letter, press release and investor presentation, along with SEC filings, all posted on the Investor Relations website at ir.gitlab.com. Ahead of getting started, let me address the safe harbor statement. I want to point you toward the cautionary statement about forward-looking statements, which appears on Page 2 of our presentation as well as in the earnings release we issued earlier today; you can access both in the Investor Relations section of our website. That presentation and earnings release lay out certain risks, uncertainties, assumptions and other factors that might cause our results to diverge from what's expressed in any forward-looking statements under the meaning of the Private Securities Litigation Reform Act. As usual, this language will govern the content of today's call and presentation; furthermore, we'll touch on certain non-GAAP financial measures during today's call; management believes these non-GAAP financial measures leave out certain unusual or nonrecurring items that affect how comparable the periods referenced are. For more on these non-GAAP financial measures, including reconciliations to the most directly comparable GAAP measure, please see our earnings release and presentation materials. At this point I'll hand things over to Bill. Bill?

Bill Staples executive
#2

Thank you, Nic, and hello to everyone this afternoon. The second quarter proved to be a remarkable one. I'll begin by walking through a few of the standout points. Our revenue reached $286.3 million, which marks a 21% increase compared to the same period last year, while non-GAAP operating income came in at $42.6 million, equal to a 15% operating margin. The sales organization booked the biggest quarter for gross bookings that this company has ever seen, and net ARR climbed over 40% versus a year ago — our strongest showing in quite a few years. We additionally surpassed every goal we set for first orders, which rose by more than 100% relative to last year. Beyond those headline items, I want to give a quick status report on all 5 growth initiatives we identified at the start of this year. To begin, we stated that speeding up first orders mattered. This past quarter ranked as our biggest for first orders in 3 years. The number of first orders jumped over 100% from a year earlier, and first order net ARR rose by close to 40%. Our specialized first order team is developing sales motions that are more repeatable, and our product-led spending is broadening the entry point of the pipeline. Together, these efforts are drawing far more new customers to GitLab. Bringing in customers of every size matters — including AI start-ups and others who place small orders initially — since over half of the $1 billion plus in run rate revenue we currently have originates from customers whose initial purchase was under $5,000. Our approach is to acquire customers at whatever point they wish to begin and then expand alongside them as time goes on. Next, we indicated that having more predictable sales capacity would serve as a key catalyst for reacceleration. During the second quarter, that idea started to show results. The number of account executives rose roughly 30% from a year ago, and output for each rep went up by about 10%. Attrition likewise showed year-over-year improvement for a second straight quarter. It's challenging to bring on more capacity while also lifting productivity, and we think this shows that the money we've poured into our sales force is starting to build on itself. What came out of it was the biggest gross bookings quarter in GitLab's history along with net ARR expansion exceeding 40%. Moving to the third point, we explained that broadening our monetization vectors was essential. Our seat-based operation keeps expanding, and AI is opening another avenue for GitLab to earn revenue from a growing share of work taking place throughout the software life cycle. Flex plays a key role in enabling that approach. Six weeks out from launch, more than 130 customers have committed north of $20 million to Flex. Seeing adoption move that quickly reinforces our belief that people want a simpler way to split their GitLab budget between seats and the newer consumption options as their needs evolve. Prior to Flex, the money customers put forward was tied to a fixed seat count for premium or ultimate platform access. Flex changes that dynamic. Under this model, the dollars are what customers commit, and on a monthly basis they decide how those dollars get allocated across seats and all of our consumption products. The commitment itself doesn't change, and it can be used for any product on the platform. As agents speed things up and additional developers join the mix, a huge chance lies ahead for us to build and seize value. Whatever shortens the gap between a customer showing interest and that customer actually realizing value benefits both the customer and GitLab. Flex was built to accomplish that through 3 key mechanisms. To start, it enables customers to extract greater worth out of each dollar they pledge to GitLab. Rather than letting unused capacity sit idle as shelfware, buyers can steer those dollars to the products delivering the greatest value for them. In our view, improved utilization ought to reinforce our already solid retention numbers by lowering the odds of churn and contraction that stem from unspent budget. Flex additionally cuts down on sales and procurement friction, since after the financial commitment is set, customers may distribute dollars among current and future products on their own schedule across the year with no need for a fresh commercial agreement every time. We've already boosted sales capacity and productivity. Flex ought to help us make that capacity still more productive by letting our teams devote fewer hours to incremental contracting and more hours to helping customers realize value. And third, it allows usage to scale up smoothly as customer requirements increase. When customers need more than what their reserved capacity allows, they can tap into any qualifying product on demand — that includes premium and ultimate seats. Any consumption that goes past their commitment or reservation is charged in the same month it occurs. This removes a lot of the true-up and contracting work that's currently required to capture that extra usage, and it gives customers more flexibility. For GitLab, that creates another potential growth tailwind as usage increases. Thanks to the launch of Flex, paid consumption run rate finished the quarter above $40 million, up from $15 million in Q1. Just to remind everyone, paid CRR is a point-in-time annualized metric covering GitLab credit commitments, Flex commitments and paid on-demand consumption; trials and promotional credits are not included. We think paid CRR gives investors a useful way to track the money moving through our consumption model as it grows. Our aim is to top $100 million in paid CRR before this fiscal year ends. At the start of the year, our business made all its money from seat subscriptions, and we now anticipate closing it with seats still expanding plus a consumption business that is significant and scaling. Fourth, we have to get better at how we serve our price-sensitive customer segments. And I'm happy to say that this quarter we've seen SMB and mid-market stabilize, with results beating our targets in those two segments for both expansion and first orders. We believed that putting more attention and money into this area would lead to better results, and the numbers we just posted give us reason for optimism. Before we get too excited, we'd like to see this hold up across several more quarters — though our confidence that we've found the right approach keeps growing. Number five on our list: we're pushing forward with an ambitious AI plan. During this period, CRR for the Duo Agent Platform rose by about 50% compared with the prior quarter, and that figure counts credit commitments, paid on-demand credits, and flex reservations. On top of that, we broadened our footprint beyond the geographic mix we saw in the first quarter, when the U.S. accounted for a larger share; also, one of the 20 biggest commercial banks in the U.S. expanded its AI credit pool by nearly ten times over the course of this quarter. Even so, my view is that the bigger story around AI carries greater significance. Over a span exceeding 10 years, GitLab has unified the context of how software gets built, secured and shipped across source code, issues, merge requests, pipelines, vulnerabilities, policies, approvals and deployments. As AI grows more capable, we think that connected context grows more valuable too, and we're seeing early signs of this through GitLab Orbit, our context graph for the software life cycle. Since the beta opened in June, over 2,200 organizations have turned on orbit indexing, a 70% rise within 4 weeks. Customers have produced over 170,000 queries, and approximately 80% of customer query volume originates from customers linking Orbit to external agents like Claude Code and Codex; we're also starting to see evidence that improved context boosts agent performance. Market tested Orbit against traditional RAG using 79 real merger requests and observed accuracy rise from 58% to 70%, and that same dynamic shows up across our platform. Compared with a year earlier, secure repositories climbed 60%, code pushes climbed 50%, CI/CD pipelines climbed 40%. Among certain customers pushing aggressively into AI-assisted development, we've watched code bases expand by as much as 500%. The pattern keeps getting clearer. When companies adopt additional AI development tools, their usage of GitLab grows as a result. That matters a lot, since our foundational business remains extremely robust. Ultimate represents 59% of ARR today, and it figured in 8 of our top 10 deals for this quarter. Premium and Ultimate together make up the foundation of a business that has now moved past $1 billion in trailing 4-quarter revenue, and we continue to see considerable room ahead. AI presents an opening for us to build on top of that foundation through new products, new consumption, and completely new categories of work moving through GitLab. Before I pass things over to Jessica, I'd like to recognize 2 key groups. First, Ian Steward, our CRO, along with the entire sales organization. Ian has been with GitLab for 5 quarters now. What we're reporting now reflects a long stretch of focused work—strengthening our core, refining how we compete, and assembling people who can carry that plan out. I also want to give special recognition to the whole GitLab team, since we began this quarter by making a difficult call to reorganize the business. A great number of colleagues chose to remain and contribute to what comes next for GitLab. Working as one, we produced a quarter among the best in GitLab's history. My thanks go out to each person at GitLab for your dedication, your ability to bounce back, and the confidence you've placed in us. I take enormous pride in all of you and in everything we've achieved. We're moving into Act 2 while standing on solid ground: our main business is in good shape, customer additions are picking up speed, fresh offerings are building momentum, and we've built a usage-based approach suited to a future in which people and agents write code side by side. With that said, I'll hand things over to Jessica.

Jessica Ross executive
#3

Thank you, Bill, and I appreciate all of you being here with us today. The second quarter was a remarkable one, and in our view it marks a significant turning point for this company. We brought in $286.3 million in revenue, which represents 21% growth compared to the same period last year and comes in about 5 points above what we had guided; bookings on a gross basis hit their highest level ever for the company in a single quarter. Net ARR rose 42% versus a year ago, making this our second-best quarter for growth in the past 4 years. Our dollar-based net retention went up from the prior quarter for the first time since 2024, and on top of all that, we surpassed what we had expected on profitability. This momentum showed up broadly — among new customers and existing ones, across several regions, for every customer size, and throughout our core platform. Because of that wide-ranging strength, our confidence in where this business is headed keeps growing. Our go-to-market organization performed at a very high standard. We signed far more big contracts than we had projected; linearity came in better than we anticipated and sales attainment got stronger. Agreements worth $500,000 or above jumped over 150% from a year earlier — an unmistakable sign that our biggest customers are expanding their relationship with GitLab. The public sector segment also made a solid comeback this quarter, and we believe there's more room for that improvement as purchasing behavior settles over the second half of the year. New customer acquisition likewise showed a true step change. We recorded roughly 1,700 first orders during the quarter — over twice what we saw a year ago — and net ARR from new logos climbed 39% year-over-year. The scale of what we achieved this quarter went beyond even the ambitious targets we had set for ourselves. Each and every one of our customers, no matter their size, is important to GitLab. More than 50% of the revenue in our current base, which exceeds $1 billion in run rate, came from buyers whose first order was under $5,000. One of our competitive advantages is getting them started with us early and growing together from there; this approach allows us to acquire customers in a cost-effective manner and expand alongside them over time. GitLab Ultimate also delivered an exceptional quarter. Compared with the prior year, Ultimate ARR grew by about 35%, and it now represents 59% of our total ARR. As artificial intelligence becomes more widespread across the software development life cycle, security, governance and compliance carry greater weight in purchasing choices. Demand is beginning to reach well past the conventional developer seat as AI opens up software creation to a far wider group of builders throughout the enterprise. In our view, that broadens the set of customers GitLab can serve in the long run. Now for customer metrics. Gross retention remained comfortably above 90%, in line with what we've seen historically. Dollar-based net retention came in at 117%, rising from the previous quarter for the first time since 2024. Total RPO increased 16% year-over-year to $1.2 billion, while current RPO rose 20% to $744.7 million. Calculated billings were up 24%, which is twice the 12% growth we reported only last quarter. Our newer products are building genuine momentum. Paid CRR for Duo Agent Platforms expanded 50% quarter-over-quarter, and paid consumption run rate across the platform came in above $40 million as we exited the quarter. The usage data reinforces this. CI pipelines created and push actions each rose by more than 40% compared to a year ago. Now let's continue down the income statement. Non-GAAP gross margin came in at 86.5%. SaaS accounted for 34% of total revenue, expanding 36% versus the prior year, driven by ongoing momentum in GitLab Dedicated and Duo. Non-GAAP operating income reached $42.6 million, compared with $39.6 million in the same period last year, producing a non-GAAP operating margin of roughly 15%, which beat what we had expected, thanks to better sales and marketing efficiency along with the timing of certain investments. Restructuring charges totaled about $23.3 million, consistent with the plan we described last quarter. Regarding JiHu, Q2 non-GAAP expenses came in essentially unchanged from a year earlier at $3.0 million. Deconsolidating JiHu continues to be our aim, although whether or when that occurs is something we cannot forecast. Adjusted free cash flow was $9.8 million, representing a 3% margin, with collection timing pressuring that figure during this quarter. Through buybacks, we returned capital to shareholders by acquiring about 3.5 million shares. Under our existing authorization, approximately $245 million remains open. We ended the second quarter holding $1.3 billion in cash and investments. Prior to discussing guidance, I want to spend a moment on Flex, because it's central to where this company is going and because it changes the way some results will show up in our reported financials; this is the first quarter that Flex appears in our results, so given how large our current revenue base is, the effect was immaterial. Even so, in the first six weeks after launch, more than 130 buyers made commitments totaling over $20 million to Flex — a quick and clear indication that people want a much better purchasing experience from us. Essentially, Flex lets a customer make a single commitment, whether for one year or several, and then pull from it as needed across premium and ultimate seats, GitLab credits, and other usage-based offerings, with no need to renegotiate or begin the procurement process again whenever their requirements change. We see this as a plainly better approach for customers, and we expect it will eventually become the standard way people do business with GitLab; it's also a better approach for us. So the takeaway is this: whether we grow depends on the value customers derive from the entire platform, rather than just the number of seats they purchase. Because customers are sending such a strong signal, our confidence in Flex's growth and adoption has increased. It also means that as this commercial model becomes the preferred way customers transact with us, Flex could have a material effect on our financial results. With that in mind, there are 2 reporting implications that investors need to clearly understand regarding the impact of broader Flex adoption across our customer base: revenue recognition and RPO. Let's start with revenue recognition. Right now, with a standard self-managed license, we recognize about 15% of it upfront. With Flex, that upfront recognition for the license fee goes away. Because buyers are able to move their product mix around inside the dollars they've committed, we recognize that revenue across the life of the contract instead. To illustrate how the numbers work: each time $50 million of our self-managed available-to-renew business converts to Flex in FY '27, we estimate that about $5 million in revenue — which would have been recorded in FY '27 under the old approach — gets deferred instead and recognized in subsequent periods. Considering how large the available-to-renew pool is in the back half of the year, plus what we can see in the H2 pipeline, the biggest hit we'd expect to revenue works out to about $13 million in FY '27. Let me be clear on this: what we're talking about is purely a shift in the timing of revenue recognition. It is not a modification to what the customer has committed, and it is not a modification to cash economics. The customer commitments stay exactly the same, and cash billings keep being invoiced annually upfront no matter which model the customer happens to be on. Since Flex represents a contractual dollar commitment, the entire committed amount shows up in total RPO. That said, Flex doesn't appear in current RPO, because upon signing, it's the customer who determines the timing, the product mix and the pace at which they'll consume going forward, so there's no reliable way for us to say how much ties to the next 12 months. So as Flex grows in scale, it's possible you'll observe total RPO and revenue growth advancing at differing rates, and that's something you should anticipate.

Jessica Ross executive
#4

In the quarter we just closed, cRPO faced a 3-point drag relative to RPO, and the whole of that drag stemmed from Flex commitments being left out of that metric. Since Flex uptake keeps growing quarter after quarter, we intend to lay out its impact in plain, explicit terms so that the accounting effect of Flex can be cleanly separated from genuine business performance; having said that, let's turn to our outlook. After the results we posted in the first half, we feel more confident about the underlying trajectory of this business. A few points are worth keeping in mind as you consider the second half. To start, we now feel more positive about the public sector, since purchasing activity picked up during this quarter, and we anticipate that this rebound will keep building steadily over the remainder of the year. Next, our second quarter gained from outstanding execution, a higher number of sizable deals than we had predicted, better linearity, and the strongest pipeline conversion we've ever achieved. For the back half of the year, our guidance presumes bookings will proceed at a more typical rate going forward, rather than matching the extraordinary heights seen in Q2. Finally, regarding Duo Agent Platform, we're factoring in only a modest amount of revenue in FY '27 when measured against our substantial installed customer base. What we're prioritizing during this year is driving adoption, turning pilot programs into live production rollouts, and laying groundwork so we can monetize the platform down the road. Last, staying true to the approach to guidance and the way we've forecast all year, Flex's possible effect hasn't been built into our guide, though we do plan to measure the revenue recognition impacts for the remainder of the year. Given all of that, I'm happy to report that our guidance is going up, reflecting both the strong momentum from the first half of the year and the momentum we expect to carry into the back half. For Q3 FY '27, our total revenue outlook is $281 million to $283 million, which works out to roughly 15% to 16% growth year over year. Looking at the quarter, our non-GAAP operating income should land between $35 million and $37 million, with non-GAAP net income per share coming in at $0.19 to $0.20, based on roughly 172 million weighted average diluted shares outstanding. Turning to the full year, total revenue is now projected at $1.129 billion to $1.133 billion, which works out to about 18% to 19% growth compared with last year. For that same period, we're anticipating non-GAAP operating income of $148 million to $152 million, and non-GAAP net income per share of $0.85 to $0.87, again assuming approximately 172 million weighted average diluted shares outstanding. Nothing has shifted when it comes to our underlying investment priorities or the way we balance growth against profitability. I'd also like to offer a few extra items to keep in mind for modeling purposes. To start, our projection for gross margins across the entire year remains in the 85% to 87% range. For JiHu-related costs, we're looking at roughly $15 million this year, up from $13 million the prior year. Taking a broader view, this quarter was truly outstanding and provides a solid base as we start shifting toward Flex. Even though this shift will create some short-term variability in when revenue is recognized and in the metrics we report, we're convinced Flex is the correct long-term approach for both our customers and GitLab. Our job during this transition is to give you sufficient transparency so you can see beyond those timing effects and focus on the actual underlying results. In this quarter, bookings reached a record level, net ARR growth picked up, retention was strong, we saw strength broadly across the business, and profitability came in above plan. That kind of result is exactly why we feel genuine confidence about the direction the business is taking. We appreciate your being with us today. At this point I'll hand things to Nic so we can begin the Q&A.

Nic Edwards executive
#5

<<operator_script>> We'll take our first question from Kingsley Crane at Canaccord Genuity.

Bill Kingsley Crane analyst
#6

Congratulations on a quarter that's genuinely monumental. Bill, you've discussed how AI labs construct custom systems around their Git providers since Git wasn't built for operations at agent scale; and after that, you're now rearchitecting source code management so it serves agents better. So I wanted to ask whether you could elaborate on that strategy. Does it apply to every customer? Does it let you accomplish more with AI natives or labs that you otherwise might not reach?

Bill Staples executive
#7

Thank you, Kingsley. What we delivered this quarter truly showed what we at GitLab have always thought possible. And at this point our focus is on methodically carrying out that opportunity so we can replicate those results. When it comes to the product road map, what AI requires is genuinely generating tailwinds for GitLab along with some very exciting possibilities. As you pointed out, the next-generation Git product is one of them. But allow me to frame it, since we kicked off this year by rolling out our first consumption product, Duo Agent Platform; it has now spent 2 quarters on the market and has been doing very well. In August, last month, we additionally introduced Secrets Manager and Dedicated Runners, which are our second and third new consumption products for this year. On top of that, we now also have GitLab Orbit, which went into public beta during Q2. That's our Knowledge Graph. It's genuinely the secret sauce at GitLab since we link code, issues, MRs, pipeline, security findings so that both agents and humans receive better answers to questions and higher quality Agentic outcomes at lower cost. We pointed out on the call that early beta adoption looks really promising. More than 2,200 organizations turned it on, a 70% increase across just 4 weeks, and 80% of the queries originate from external tools such as Claude Code and Codex. Those generate more consumption of the GitLab platform. The other item you brought up is the next-generation Git product. As experts in Git, we rank among the leading contributors to that project; we're currently rearchitecting that Git infrastructure to reach roughly 100x the scale humans have ever needed; that matters a great deal because agents function at that machine scale level, with one engineer or builder calling dozens and at times hundreds of agents to complete a particular task. Another product road map item I'd like to call out besides next-generation Git is our artifact management product, which sits in private beta right now, but we anticipate it will arrive in public beta this quarter; it broadens our platform so our customers can store, version, govern and sign binaries in artifacts, letting us finish out the software supply chain. We already hold their source code. We already build and test that source code, and we help them deploy it. And through artifact management, we'll also help them store those artifacts so they can achieve a secure end-to-end software supply chain entirely inside GitLab. One of the biggest worries enterprises have right now is trusting their software supply chain in an Agentic era, where agents handle a great deal of the work. DAP serves as our agentic layer. Beneath it sit our new consumption-based offerings, among them, as you mentioned, next-generation Git, GitLab Orbit and Artifact Management, each arriving on the market during the year ahead, with capabilities that let software engineers and their agents work at far greater scale. It's an exciting moment. And this may be a good point for me to preview our GitLab Transcend event, which is only about 6 weeks away. We'd love for you to join us and hear more about the road map ahead.

Nic Edwards executive
#8

Our following question will be from Matt Hedberg at RBC.

Matt Hedberg analyst
#9

Can you hear me okay?

Jessica Ross executive
#10

Yes.

Matt Hedberg analyst
#11

Nice work on these results. It's genuinely, genuinely great to see. I suppose for Bill or Jessica, there's plenty to consider here. Watching the seat growth is truly, truly encouraging. And when we factor in that along with the positive sentiment surrounding Flex, it seems like durability might be increasing. What I'm curious about on the seat front is, clearly developers are the priority. But might you discuss the opportunity beyond developers? I believe we all share the view that this could be quite a meaningful catalyst too; could you address that aspect as well?

Bill Staples executive
#12

For sure. AI is demonstrating itself to be a genuinely lasting secular tailwind for GitLab, and not simply for seats, but for each element of how we drive growth. This might be an opportune moment for a brief mention. As something new this quarter, we released an investor letter, authored by Jessica and myself, to provide insight into our thinking on GitLab's growth algorithm moving forward. Let me offer a brief overview and, as part of it, address your question regarding the seat opportunity. Our growth algorithm involves 3 elements. To begin, additional customers. And under additional customers, a greater number of builders than at any point before. We see GitLab's opportunity in this area as massive. Our penetration in the worldwide market remains low, and our competitive standing has grown stronger, as shown by our first — by the results this quarter. We brought in over 1,700 first orders during this quarter. That figure is over twice what it was a year ago, and net ARR from first orders has risen by almost 40%. Another element contained within that figure for new customers is really heightened demand for seats. AI has greatly empowered just about anyone to turn into a builder. I suspect lots of folks on this call have tried out AI tools and managed to build dashboards or applications where the code was produced entirely by the agent. Yet that code requires storage somewhere. If it's part of an enterprise, it must be governed by that organization. It needs to satisfy those organizational compliance and security requirements, and that's precisely where GitLab excels. So AI is generating a secular tailwind for additional customers and additional builders inside each one of our customer accounts. The second element of our growth algorithm concerns additional products. You've heard me discuss, in answering Kingsley's question, some of the thrilling product road maps coming up. But this matters greatly to our growth strategy, since we're moving past just the platform seat capabilities that we've offered, which built a $1 billion run rate business that continues to grow robustly. Evidence that this element of our growth algorithm is delivering also appears in this quarter. We've noted, for instance, that secure repositories are expanding at 60%, code pushes at 50% and CI/CD pipelines at over 40% year-over-year. That's our core platform at work. Beyond the main platform, another thing generating excitement is the rollout of credits along with our consumption model. As proof from this quarter, one thing we can point to is growth in our Duo Agent Platform, which rose 50% on a sequential basis. And then the third piece of how we grow involves opening up consumption for all customers. Flex plays that role, since it removes friction from usage across seats and credits through one commitment, letting buyers pick each month how they'd like to use the platform for their own particular needs. In the final 6 weeks of Q2, as Jessica noted, over 130 customers chose Flex. They pledged upwards of $20 million, and because of Flex our paid CRR climbed from $15 million at the close of Q1 to more than $40 million at the close of Q2. So zooming out, AI is bringing the bar way down for creating software. Just about anybody can turn into a builder. Customers need GitLab more than they ever have, and that trend has held for multiple quarters running. Appreciate the question.

Nic Edwards executive
#13

All right. Our following question will be from Sanjit Singh at Morgan Stanley.

Sanjit Singh analyst
#14

Great quarter — congratulations. It's wonderful to watch. Thinking about the way the business model and the pricing model keep developing, there's a lot on your plate. Zooming out, Bill: when we talk about ultimate compared with premium, does that framing still hold up? What I mean is, you're adding seats. Seems like non-developers could be a long-term growth engine there, so could the model eventually boil down to seats, with additional ways to monetize through product add-ons — and I'm certain there will be considerably more of that in the coming couple of years. I just wanted to get your bigger-picture take on where the business model and pricing model head from here.

Bill Staples executive
#15

Right. Appreciate it, Sanjit. Seats are unquestionably at the heart of what we do, they keep growing at a healthy pace, and we're thrilled to keep delivering those premium and ultimate capabilities that built a $1 billion run rate business which is still expanding robustly. That said, to take your question up a level, I believe the way investors ought to view our future growth is by grasping both the customer-side and the GitLab-side advantages of Flex; so let me break down the GitLab strategy here, since that's essential to grasping where our business model is headed. Flex launched in Q2, and I've already mentioned a few of the early wins: 130 customers, over $20 million committed. You may wonder, why bring that out? What's making customers embrace it so quickly at this early stage? The advantages are quite evident. On the customer side, Flex delivers greater value per dollar, because each month they can move unused capacity away from shelfware and toward whichever products generate the most value for them; take, for instance, the growing need to extend GitLab to people outside engineering — they can shift capacity onto additional premium or ultimate seats. Beyond that, those users might require a Duo Agent Platform to supply agents that support their work throughout the software life cycle, and they're able to assign a reservation on Duo Agent Platform. Next, it lets them bring on new products without entering a fresh contract cycle and without obtaining additional budget from procurement; this ranks among the biggest advantages of the Flex model, since within the Flex portal itself, new products appear, reservations can be allocated toward them, and budgets can even be set, giving them control over where their commitment is spent. And lastly, it lets customers expand usage smoothly past their commitment; if demand appears, they can provision additional seats and additional credits as required beyond their commitment, and those get billed monthly. On GitLab's side, then, the advantages are quite evident. To start, we think Flex will help us push an already solid retention profile to be even better. With a Flex commitment, we’re able to take any capacity that isn’t being used and let customers redirect it whenever they need to. That boosts retention, which, as Jessica said, is already above 90% on a gross basis. It should also help us keep making our productive sales capacity better, which is already improving. I noted that this quarter we raised capacity by 30% and saw a 10% gain in productivity per rep. Now, though, reps can devote more time to assisting customers in realizing value and less time haggling over contracts, true-ups, and procurement. Lastly, this creates a fresh growth tailwind, because customers can turn on usage whenever they want, and we invoice them right away when that usage occurs, which gives us one more monetization tailwind. So the approach to the business model is fairly straightforward: we want customers moving to Flex, since it delivers more value to them, cuts sales and contracting friction, and supports on-demand consumption. We began the year with a subscription business that was 100% seat-based. And now our focus is on finishing the year by continuing to grow that core platform, while also aiming to end the year with a meaningful consumption business scaling toward our second billion as we monetize the work that humans and agents are doing together.

Nic Edwards executive
#16

All right. Our following question will be from Ethan Weekes at Piper Sandler.

Ethan Weeks analyst
#17

Ethan here, sitting in for Rob this evening. Bill, I'd like to know your view on how much of the quarter's strength came from better internal execution on our part, versus the broader demand backdrop simply picking up speed as every organization starts considering the tool chain they're putting in place for their developers?

Bill Staples executive
#18

Yeah. Excellent question. Like we said, a record quarter for gross bookings in the history of the company. Net ARR up over 40% compared to a year ago. That ranks as our second-best growth quarter across the past 4 years, just to give you a feel for it. And I believe it truly stems from many quarters of investing plus some tailwinds arriving across several dimensions. As Jessica pointed out, PubSec came back in a meaningful way. That's a genuinely strong signal following a few quarters of results that fell short of ideal, due to government shutdowns and other factors. We're also seeing AI tailwinds, though, that help push large deals forward. Jessica noted that our deals of $500,000 and above rose by over 150% versus a year ago. Our biggest customers are going deeper in their commitment with GitLab. Those commitments cover both seats and credits for our new consumption products. Beneath all of that, we truly see AI starting to become a lasting tailwind for GitLab; and it genuinely touches all 3 levers of our growth algorithm. It's bringing in more customers; it's bringing early adoption of the new products, as we pointed out with GitLab Orbit, and it's bringing greater consumption. You should view net ARR as that output metric for the growth algorithm, since it accounts for all 3 of those dimensions compounding on each other.

Nic Edwards executive
#19

Our next question will come from Koji Ikeda from Bank of America.

Koji Ikeda analyst
#20

Great work on the commentary and the bookings growth. With so much attention on Flex over the coming, say, 2 years, there are plenty of shifting parts in the financial model tied to Flex. So which single metric would best measure how Flex is performing? And then one quick housekeeping item about the guide: if Flex didn't exist this year, would the guide have been $13 million higher? Really what I'm asking is whether the guide is actually downplaying what's going on in the business because of the shift with Flex?

Jessica Ross executive
#21

Thanks, Koji. Let me back up a bit and share some thoughts on how we approached guidance this quarter; so first, again, Flex has only been on the market for 10 weeks. That's simply too recent to incorporate into guidance with precision. That said, customer demand has been a genuine and pleasant surprise, and Flex could prove quite impactful in the back half of the year. So when we considered our guide, we didn't want accounting mechanics to skew the guidance discussion or how investors see the underlying health of the business. So I'd say we've used 2 key principles in our approach, consistency and transparency; so first, consistency. We wanted to guide the same way throughout the year. So we began FY '27 guiding without the accounting timing impact of Flex, and we've kept that methodology rather than switching midyear. Second, transparency. Consistent with our commitment to transparency, we're giving a couple of key data points to help you think about your models. First, the heuristic, which I mentioned in my prepared remarks. So for each $50 million of self-managed customers that convert to Flex, there's roughly a $5 million revenue recognition timing impact that pushes out of FY '27 into the future period and then the maximum FY '27 impact of $13 million. So going forward, we'll keep explicitly and transparently quantifying the flex accounting timing impact every quarter so all of you can separate the accounting effect from the underlying business performance. We are committed; and I think regarding that $13 million, the other thing I'd point out is we have a lot of visibility into our business; so in calculating that amount for us, we're confident in the precision because, one, we understand our self-managed available-to-renew for the back half of the year, and we also have very clear line of sight on pipeline.

Bill Staples executive
#22

And Koji, regarding the second half of what you asked — which metric should be watched — that paid CRR figure we rolled out during the prior quarter and refreshed in this one, now sitting above $40 million, is genuinely the clearest lens for seeing how money moves through our consumption-based model. Within paid CRR you'll find Flex commitments, credit commitments, and on-demand paid usage — all three sit inside that number. Promotional usage, trials, and any other unpaid usage are excluded from it. And like we said in the prepared remarks, we're putting forward a bold goal: crossing $100 million in paid CRR before this fiscal year wraps up.

Nic Edwards executive
#23

All right. Our following question will come from Radi Sultan at UBS.

Radi Sultan analyst
#24

Great. So now that you've got a few data points regarding conversion over to Flex, I mean, when you're figuring out the size of those first Flex agreements as you bring customers on board, is there perhaps a stronger tendency to make deals bigger given the added flexibility and, sort of, the new way products get consumed? What I'm trying to get at is how much of this is purely a shift in form factor toward Flex as opposed to factoring in expected new product usage or seat growth — that would be helpful.

Jessica Ross executive
#25

Yeah. No, once more, we're genuinely thrilled about it; it's roughly 10 weeks since launch, so it's too soon for us to say. But I just — I think really embracing the strategy, Bill, is there anything you'd like to add there from that perspective?

Bill Staples executive
#26

Yeah. When you look at it through the lens of how we sell, there are several things we can accomplish here. To start with, certain buyers move quickly and are already trialing the beta versions we've released; Flex provides a mechanism that allows us not just to keep their seat-based subscription going, but also to move that spend into a Flex arrangement, which opens up room for them to begin leveraging those offerings the moment they hit general availability. And any time there's an opening like that, where we can give customers extra room within their commitment, naturally, that's something we'd want to capitalize on. It also gives us a way to approach accounts sitting on capacity they aren't using, since in the past they had no choice but to lock in a seat projection covering the entire year, and instead of accepting some downsizing on that account, we can hold their commitment steady or push it upward and redirect those dollars toward new consumption-based offerings. So on the positive side it's a real boost, and on the negative side it helps us lessen or avoid potential losses, and we're genuinely eager to roll this out wherever we can get customers to see eye to eye with us on what their GitLab commitment is worth.

Nic Edwards executive
#27

All right. Our following question would be from Derrick Wood at TD Cowen.

Jim Wood analyst
#28

Nice work. Bill, can you speak to what you're observing regarding the competitive landscape, both with respect to new AI-native entrants appearing and also what your established rivals are doing? And in which areas do you believe you're competing more effectively or picking up share at present?

Bill Staples executive
#29

Sure. That's a great question. The competitive dynamics stayed very consistent during this quarter; we continue to have a single main competitor. Our standing relative to that rival is, in my view, the strongest it has ever been. They've had trouble with reliability and with satisfying what customers need in this new Agentic era around security, trust, and other aspects. As a result, we're seeing better win rates. We're seeing wins both on the first order side and on the expansion side, which our numbers reflect: 100% growth in first orders and over 40% net ARR expansion. Regarding AI natives, what I'd say is that this really represents an opportunity. They're generating tailwinds for us. They've made it dramatically simpler for anyone to produce code, and all of that code requires GitLab. So we're now seeing, as I mentioned, customers approaching us to say they need additional GitLab seats because nonengineering staff require access to the platform; and those very users who now need seats will eventually also need credits so they can use our consumption-based products. So we're glad to work alongside any Agentic coding tools out there, since we view it as generating tailwinds for the business we operate.

Nic Edwards executive
#30

The next person to ask something is Howard Ma from Guggenheim. Howard, can you hear us? Let's check that you're — Howard Ma, can you hear us? We'll go ahead to the question after that. The next person to ask something is Nick Altmann from U.S. Bancorp.

Nick Altmann analyst
#31

Great. I’d like to build on what Radi asked before. When it comes to the interest in Flex or that $100 million CRR goal, how much is coming from newer offerings such as Duo Agent Platform, Orbit, Secrets Manager, and the Dedicated Hosted Runners? Since I believe you said not every bit of it would add to revenue, yet presumably a portion of those newer offerings ought to be incremental; so any insight into how much those newer offerings are fueling some of the interest in Flex or that $100 million CRR goal would be really useful.

Jessica Ross executive
#32

On the financial side alone, it’s genuinely too soon to say, though I’ll have Bill address a bit more regarding the interest we’re seeing up to now.

Bill Staples executive
#33

Right, in Q2 we had just 6 weeks, so that 130 customers and $20 million represents what we've already booked. Still, I believe it's worth pulling back to grasp the strategy, since whenever customers move toward Flex and start using seats against that commitment, the character of the relationship shifts; grasping that matters as part of the strategy, because what software engineering teams need today transforms dramatically week to week, month to month, quarter to quarter. Fresh tools appear, fresh techniques appear, fresh models arrive on the market, and buyers want the freedom to direct their spending as their requirements change. Were the existing seat-based subscription model satisfying them, Flex wouldn't be necessary. There'd be no call for it. We wouldn't be witnessing the swift pickup and adoption we've already witnessed. So plainly, buyers recognize its value, and they might begin funding their Flex agreement using dollars from their prior seat-based subscription, yet they perceive the value proposition and the freedom to adjust and evolve it as our new products reach the market; and certainly, part of that stems from our present consumption product, Duo Agent Platform, which launched in January, plus the freshly emerging ones that launched in August, Secrets Manager and Dedicated Hosted Runners; but we already have substantial usage of our beta products underway. And I think buyers are likewise gazing forward and valuing the flexibility we're providing through the Flex agreement.

Nic Edwards executive
#34

Our following question will be from Shrenik Kothari at Baird.

Zach Schneider analyst
#35

Hey, this is Zach filling in for Srini. I want to add my congratulations as well on a solid quarter. My question is about gross margins. Clearly, they've dipped somewhat now that the business is backing more AI and usage-based workloads, even as credits keep increasingly monetizing both human and nonhuman activity. So I suppose what I'm really asking is how much of that recent gross margin shift actually stems from AI inference and infrastructure as opposed to other drivers? And then, as agent usage grows, what makes you confident that pricing, model efficiency, Orbit, and simply your capacity to route workloads between models can produce appealing incremental economics, instead of maybe generating a revenue mix with structurally lower margins?

Jessica Ross executive
#36

Yeah. No, I appreciate the question. And just, I believe regarding gross margins this quarter, there isn't really a significant change relative to what we've previously communicated. So our SaaS dedicated contribution sits at roughly 34%; that rose 36% year-over-year. And so that's genuinely consistent with what we told you around the IPO, when we stood at 22%. Therefore we anticipate those margins declining over time. And then, thinking about what lies ahead, again, this is a year for investment and execution; we've deliberately put money into consumption products and pushed customers toward prioritizing the shift from pilots into production. And so that's what you're observing there; but Bill, I'm not sure whether you'd like to add anything.

Bill Staples executive
#37

Yes. You brought up tokens and the possibility for AI optimization in the way GitLab approaches AI-native offerings. So I'll spend just a moment on that, since I believe we're still at a very early stage, and we actually hold a number of structural advantages compared with what you might call typical AI native tools, whose monetization rests almost entirely on tokens. One great thing about Duo Agent Platform is that we deliver it in a cloud-agnostic, model-agnostic fashion, which means we back all of the models, open source open weight models included, and we let customers deploy it and run it in any cloud, including, say, air-gapped data center environments that they operate. What that translates to is that for a large share of our customers, the token or inference cost isn't actually baked into the GitLab agreement; what they pay us for is access to the platform, plus the work performed in the platform, the context, the harness, the governance and auditability we deliver — not the inference. Those are all extremely high-margin products; beyond that, we're at a very early stage of AI adoption. There are quite straightforward items on the road map that we and others are moving toward over time, which would enable dynamic model routing and model optimization to produce high-quality agentic outcomes in a way that's more cost-efficient. Those are also things we intend to offer so customers get the very best experience along with price to value performance. So I'd encourage you to think about gross margins perhaps somewhat differently than you might with typical AI natives. And as Jessica brought up, much of the margin movement we've observed in the business has been driven more by the mix shift to SaaS than by the early AI adoption.

Nic Edwards executive
#38

Okay. Next up, we have Jonathan Ngo calling in from Truist Securities. Jonathan Ngo? Fine. For our final question, we'll hear from Miller Jump at Truist. Okay. And our concluding question comes from Lucky Schreiner with D.A. Davidson.

Lucky Schreiner analyst
#39

Can you guys hear me okay?

Jessica Ross executive
#40

We can.

Lucky Schreiner analyst
#41

Alright, sounds good. Lucky here from D.A. Davidson. Regarding that customer story — the one that grew their monthly commitments by 10x — was usage growth mainly what drove that, along with what they received? And what portion of it might have come from consolidating vendors and swapping out other tools? Also, how broadly do you think that sort of expansion motion applies across your customer base?

Bill Staples executive
#42

Yeah, it's a top U.S. bank, and they'd initially begun with a pretty modest commitment to Duo Agent Platform. Then, as they started rolling it out among their engineers and witnessing the value it delivers, they felt the need to boost their commitment 10x this quarter, which we'd love to see replicated across every single customer. We think Duo Agent Platform's value is there, and it complements other AI native tools that lean more toward the coding side of software. So yeah, that lighthouse customer has us really excited. We now have several spending multiples beyond their premium or ultimate seat price when it comes to credits; and that's a pattern we're working to learn from, optimize for, and repeat wherever possible.

Nic Edwards executive
#43

Okay, that wraps things up for us. Thanks to each of you for being part of our Q2 call for this quarter. We're genuinely thrilled about what we managed to achieve over these three months, and we appreciate you spending time with us. We look forward to seeing you at the upcoming investor conferences.

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.