This conference call transcript was computer generated and almost certianly contains errors. This transcript is provided for information purposes only.EarningsCall, LLC makes no representation about the accuracy of the aforementioned transcript, and you are cautioned not to place undue reliance on the information provided by the transcript.
spk00: Thank you for joining us today for GitLab's second quarter of fiscal year 2023 financial results presentation. GitLab's co-founder and CEO, Sid Sibrandi, and GitLab's chief financial officer, Brian Robbins, will provide commentary on the quarter and fiscal year. Please note, we will be opening up the call for panelists questions to ask a question, please use the chat feature and post your question directly to our question using the drop down menu before we begin i'll cover the safe harbor statement. During this conference call, we may make forward-looking statements within the meaning of the federal securities laws. These statements involve assumptions and are subject to known and unknown risks and uncertainties that could cause actual results to differ materially from those discussed or anticipated. For a complete discussion of risks associated with these forward-looking statements in our business, we encourage you to refer to our earnings release distributed today and our SEC filings, including our most recent quarterly report on Form 10-Q. Our forward-looking statements are based upon information currently available to us. We caution you to not place undue reliance on forward-looking statements and we do not undertake any duty or obligation to update or release any revisions to any forward-looking statement or to report any future events or circumstances or to reflect the occurrence of unanticipated events. In addition, during this call certain financial performance measures may be discussed that differ from comparable measures contained in our financial statements prepared in accordance with US generally accepted accounting principles referred to as non-GAAP financial measures. These non-GAAP measures are not intended to be a substitute for our GAAP results. We believe that these non-GAAP financial measures assist management and investors in evaluating our performance and comparing period-to-period results of operations as discussed in greater detail in the supplemental schedules to our earnings release. A reconciliation of these non-GAAP measures to the most comparable GAAP financial measures is included in our earnings press release submitted to the SEC. These reconciliations, together with additional supplemental information, are available at the Investor Relations section of our website. A replay of today's call will also be posted on the website. I will now turn the call over to GitLab's co-founder and Chief Executive Officer, Sin Sibrandi.
spk10: Thank you for joining us for our fiscal year 2023 second quarter earnings presentation. We continue to see strong momentum in our business, and we believe that our second quarter results indicate that the market is embracing our DevOps platform leadership position. We also executed well in the quarter, demonstrating our ability to achieve high growth with increasing operating leverage. In the second quarter of fiscal 2023, we exceeded our guidance with revenue of $101 million. This represents revenue growth of 74% year over year. Our dollar-based net retention rate exceeded our own reporting threshold of 130%. This remains best in class and consistent with our track record as a public company. Our second quarter results also continue to demonstrate the attractive unit economics underlying our business. Our non-GAAP operating margin improved by 1500 basis points year over year, and we remain committed to growing in a responsible manner. Every company needs to be great at developing, securing and operating software, or they will be disrupted. This core capability, what's called DevOps, is a must-have in any macroeconomic environment. Enterprises are navigating economic uncertainty while still needing to embrace the imperatives of digital transformation, cloud migration, and app modernization. Our customers choose GitLab to accomplish more with the people that they already have. Delivering software fast and efficiently in a secure way is essential for success. Our one DevOps platform empowers them to do exactly that. With one data model and a single interface, we create a more efficient and captivating user experience. With GitLab, everything from planning, building, securing, deploying, and monitoring software all resides in a single application. This mission critical software helps companies eliminate the costly integration work you have when using point solutions. And it also allows them to create and release software faster while strengthening software security and compliance. This combination drives business and technology transformation. There are three main topics that I will cover today. First, I will explain how we enable all types of customers to realize the promise of DevOps by moving to a platform approach. Second, I will discuss how we are leading the industry in product innovation and highlight the recent enhancements from our major GitLab 15 launch. Third, I will share our view of GitLab's value proposition and how we are well positioned to succeed. Our differentiation starts with our core value of iteration, which in turn drives our rapid pace of innovation. GitLab is far ahead in the comprehensiveness of its DevOps platform. Every month on the 22nd, we ship a new version of GitLab with many new features and improvements. We've done this for 130 months in a row. Our innovation is also driven by the open core nature of GitLab, which means that our customers and users contribute to the capabilities of the platform, enabling us to drive even more differentiation and value for all of our customers. Every quarter, hundreds of improvements are contributed by our customers. Our differentiation also extends to security and compliance. In today's environment, security is a business imperative. We believe we have the most comprehensive security offering in the market, enabling companies to truly adopt DevSecOps practices. With GitLab, security is integrated throughout the software development and deployment process. Our capabilities include dynamic and static testing, vulnerability management, dependency and container scanning, and coverage guided first testing, which enables customers to find vulnerabilities that other QA processes cannot find. Organizations shouldn't have to trade off compliance requirements with their speed of innovation. developers should be able to easily verify the compliance of their code without having to leave their workflow. In GitLab, this ability to perform compliance is automated and resides within the platform. This removes the need for compliance managers to require developers to context switch among different point solutions, losing productivity and efficiency in the process. We believe the future of compliance requires automation, When you create software today, you don't write all of the code yourself. Instead, you have a supply chain of external dependencies like open source libraries that are bundled into a modern software development. However, a problem arises with so many dependencies. There's no way to accurately and efficiently check all of it manually for security vulnerabilities. This can have devastating effects when failing to identify security threats. Roll back vulnerable code and fix and redeploy that code. This manual process can translate into significant financial and brand damages given the existing threat landscape. The only effective pathway forward is to automate that process, making the cycle time from identifying a vulnerability, rolling back code and redeploying it shorter and shorter. GitLab makes that level of automation seamless for our customers. We have the most advanced offering in the market as validated by customers like HackerOne and Deutsche Telekom. They use our comprehensive capabilities to secure their software supply chain and make their security and compliance checks more efficient. Our differentiated value to customers is that this security is integrated into our product. It's not bolted on as an afterthought. GitLab's comprehensive security offering with so many features allows customers to consolidate their spend. They no longer have to integrate with so many other security vendors. More importantly, they can create more secure software by shifting security practices earlier in the development process, performing threat and vulnerability analysis as developers create the code, not after they deployed it. The earlier you integrate security, the easier it is to address potential concerns. So you become more productive. and you can enforce it for every project and every change. Furthermore, because all of the security checks are happening on the same platform, customers can prove that they performed all of the security checks for that code. With a do-it-yourself or DIY DevOps approach that requires stringing together disparate point solutions, a similar endeavor would require much more personnel and resources. Next, I would like to discuss the new advancements in GitLab 15, our latest major release. We focused on three main areas of innovation across the DevOps lifecycle. The first area of innovation is enterprise agile planning. When we talk to customers, a primary pain point we hear is that existing point solutions lead to a poor user experience. While they may meet the needs of the individual, they fall short of addressing the needs of the broader organization. As an end-to-end platform, GitLab is uniquely positioned to integrate planning with execution in a seamless manner. We enable business leaders to drive their vision while empowering DevOps teams to deliver value more effectively and efficiently by improving how they collaborate. The second area of innovation is continuous security and compliance. Our customers are looking to solve the pain point of a fragmented security experience which slows down development cycle time and creates more risk. They don't want to make a false trade-off between speed and security. They want security and compliance to be embedded end-to-end across the software development lifecycle without sacrificing speed. In GitLab 15, we've introduced new capabilities around software supply chain security, advanced security scanning, streamed audit events, and more comprehensive governance. The third area of innovation involves our use of artificial intelligence and machine learning. This area is particularly exciting because it makes our product better and it enables us to broaden the appeal of our platform to even more use cases and personas. To illustrate how we are leveraging AI to improve the product, we now have a feature where GitLab will suggest to developers who should review their code. They can find an expert who can provide better feedback, which creates more efficiency, as well as higher quality, more secure code. To invite more personas to the platform, like data scientists, we are also integrating the DevOps process with the MLOps process. We see this as the next big step in consolidating historically separate development workflows. Today, machine learning is an essential part of modern application development. Every significant application is going to have both code and models. Those models go through a lifecycle themselves, which includes training, testing, and deploying. Data scientists and engineers are critical stakeholders in this process. Yet traditionally, they have been excluded from the collaboration and efficiency benefits of DevOps and automation, relying on either manual processes or bespoke tool chain that they need to maintain. The benefits of our platform will help data scientists and engineers in a number of ways, from collaboration with other teams, planning and managing project sprints, version control for automated workflows, streamline testing and validation, and simplified infrastructure management across multiple cloud providers. We are excited about the significant amount of innovation on our platform, from enterprise agile planning to security to compliance to AI and machine learning. Finally, I would like to address why our one DevOps platform value proposition is mission critical and resonating with customers in the market. From speaking with customers and prospects, we've assessed that companies are looking to achieve five main outcomes from their DevOps IT budget. They want to consolidate their software spend. They don't want to spend money and engineering time integrating tools. They would like to get more productivity from the current people they already hired. They would like the DevOps process to better enable their entire organization to deliver value to their customers faster. And they would like to generate more revenue by releasing customer facing applications faster. GitLab provides the solution to achieve all of these outcomes. R1 DevOps Platform helps companies reduce costs by consolidating from many vendors down to one. It frees up people from integration work. And in addition, moving to a platform allows for closer collaboration between development, security, and operations teams with fewer contact switches, which increases productivity and user satisfaction. What GitLab delivers is a faster cycle time, faster execution on cost-saving initiatives, and the opportunity for revenue acceleration. To quantify these benefits, based on a study conducted by Forrester Consulting and commissioned by GitLab, our customers saw a 407% return on investment within three years of deployment of our DevOps platform. Having a comprehensive platform that solves so many problems while at the same time saving money is a superpower in economically challenging times. This value proposition translated into a number of strong business highlights in the second quarter. I'm proud to share that we added 696 net new base customers. And let me give you an example of a new logo win, an uptier and a customer expansion. First, a North American-based global leader in cross-border peer-to-peer payments needed a DevOps platform that streamlined and automated processes, reduced cycle time, and provided the ability to set and enforce organizational policy across every stage of their development process. From a GitLab proof of value engagement, they realized a 30% efficiency improvement in building, securing, and deploying versus their previous tool chain implementation for both new and changing applications. As a result, they became a GitLab SaaS ultimate customer, replacing a previous vendor's implementation. Second, a North American consumer research data and analytics firm, who has been a GitLab starter customer since 2015, merged multiple business units, which had completely siloed DevOps tools. a new corporate initiative to move to the cloud catalyzed the need to quickly consolidate onto a single platform to standardize their entire devops lifecycle to increase operational efficiencies decrease cycle time and increase developer productivity by migrating to gitlab they immediately saw a 3x increase in productivity due to less maintenance time and fewer costs with a fully integrated gitlab scm ci and subsequently upgraded to premium And finally, the North American-based motor vehicle manufacturing company was looking for an alternative to their existing DevOps products because their workloads far exceeded the scaling capabilities of those tools. After working closely with GitLab, we demonstrated our unique ability to scale to meet their volume needs while also enabling them to consolidate their tools. As a result, the customer expanded in the second quarter, increasing their number of premium licenses by 40%. Another key strength of our go-to-market value proposition is our relationship with cloud hyperscalers. They view GitLab as an accelerant for customers to move to the cloud faster. We're also pleased with the number of higher-level strategic conversations that are happening at the C-level, addressing how GitLab can help them solve their business problems. In fact, in Q2, we were named as Google Cloud Partner of the Year for application development. following up from last year when GitLab was awarded Google Cloud Partner of the Year for DevOps. A powerful example of the result from these alliances is KeyBank, one of North America's largest financial services companies. KeyBank recently formed a partnership with Google Cloud Platform, or GCP, to move workloads from data centers to Google Cloud. In addition to their cloud migration effort, app development and modernization are key parts of their digital transformation goals. Their employees embrace a continuous integration and continuous deployment software development model, which the industry calls CI-CD. They choose GitLab to bring together their DevOps process, making an initial purchase of several hundred ultimate licenses. We see this type of close alignment with other cloud providers, including AWS. In the second quarter, GitLab and AWS worked together to help a major airline manufacturer significantly reduce their risk of loss and downtime that was required for their business critical development needs. GitLab is now critical to this customer's developer team success. They have now standardized us across thousands of users and crossed the million-dollar threshold as a customer. These customer success stories, in combination with the growth of our alliances and partnerships, clearly show that the market is moving towards a platform approach to DevOps. We recently published our sixth annual State of DevSecOps report, a landmark research study of over 5,000 DevOps professionals from around the world. Among the many findings, we see a continued need for tool consolidation. 85% of DevOps teams use between 2 and 10 tools. And with 69% of survey participants saying they'd like to consolidate their tool chains, the need for DevSecOps platform is clear. In summary, I'm very pleased with the quarter. We continue to innovate and create new capabilities for an expanded set of customers. We continue to demonstrate the promise of a platform over point solution approach, and we continue to show that GitLab is mission critical. And we continue to believe that we are early in a large and growing market. Our Q2 results demonstrate that we're well positioned to drive durable growth with improving unit economics. I'm grateful to all our team members, partners, the wider GitLab community, and customers who contributed to our results. I also want to thank Eric Johnson, our CTO. He has resigned effective October 1st and will stay on as an advisor for six months. Eric has been with GitLab since 2017, and I want to thank Eric for our partnership over the last five years and wishing the best of luck. And I'll now turn the call over to Brian Robbins, GitLab's Chief Financial Officer.
spk13: Thank you, Sid, and thank you again to everyone joining us today. I'd like to spend a moment reviewing the key characteristics of our business model and what we're seeing in the macro environment. Then I will quickly recap our second quarter financial results and key operating metrics and conclude with our guidance. Our platform delivers a strong ROI and positive business outcomes. Customers continually tell us that they strongly support our pricing model. Our platform is offered with a free version and two paid subscription tiers, which we call premium and ultimate. Our paid tiers are priced per user with different features per tier. Every user within an organization is on the same plan, which helps to keep our business model transparent and easy to understand. Our second quarter results continue to demonstrate our ability to drive high growth with improving incremental margins. Fueling these results are a number of key aspects of our business model that I would like to discuss briefly. These include the predictability of a subscription model that provides high visibility, a platform sale rather than a point solution sale, a diversified customer base across industry verticals, customer sizes, and geographic regions. a short implementation cycle, and an established and well-documented ROI. In addition, we price our platform in US dollars, so we have no currency impact. These attributes contribute to the results we are seeing. To illustrate this, customer cohorts from seven years ago are still expanding today. Despite the volatility in the macroeconomic environment in the second quarter, we have not seen any impact to our business. Customers increasingly recognize the need to address multi-year digital transformation challenges. The current environment is not slowing down customer decisions, nor elongating our sales cycles. Buying cycles have actually sped up across the business, and we continue to see strong win rates. We're also happy with how we executed on hiring. We added a similarly strong number of new team members as we did in 1Q, and we experienced lower attrition. We view the uncertainty in the macro economy as a benefit for hiring new team members, and we currently have over 225 open positions that we're actively looking to fill. Next, turning to the numbers. Revenue of $101 million this quarter represents an increase of 74% organically from the prior year. we added the largest number of base customers ever in a single quarter. We ended 2Q with over 5,800 customers with ARR of at least $5,000 compared to over 5,100 customers in the prior quarter and over 3,600 customers in the prior year. This represents a year-over-year growth rate of approximately 61%. Currently, customers with greater than $5,000 in ARR represent approximately 95% of our total ARR. We also measure the performance and growth of our larger customers who we define as those spending more than $100,000 in ARR with us. At the end of the second quarter of FY 2023, we had 593 customers with ARR of at least $100,000 compared to 545 customers in the prior quarter and 383 customers in the second quarter of FY 2022. This represents a year-over-year growth rate of approximately 55%. As many of you know, we do not believe calculated billings to be a good indicator of our business. Given that prior period comparisons can be impacted by a number of factors, most notably our history of large prepaid multi-year deals, this quarter total RPO grew 76% year-over-year to $362 million. We ended the second quarter with a dollar-based net retention rate consistent with the previous quarter. This exceeded our reporting threshold of 130%, which remains best in class and consistent with our track record as a public company. The ultimate tier continues to be our fastest growing tier, representing 39% of ARR for the second quarter of FY 2023, compared with 29% of ARR in the second quarter of FY 22, and continue to grow in excess of 100%. Non-GAAP gross margins were 89% for the quarter, which compares to 90% in the immediate preceding quarter and 88% for the second quarter of FY 2022. As we move forward, we are estimating a moderate reduction in this metric due to the rapid year-over-year growth rate of our SAS offering. We saw improved operating leverage across the business this quarter, largely driven by revenue outperformance. Non-GAAP operating loss was $27 million or 27% of revenue compared to a loss of 24.8 million or 42% of revenue in Q2 of FY 2022. Q2 FY 2023 includes 5 million of expenses related to our JV and majority and subsidiary. We incurred a $2.3 million cancellation fee in Q2 as a result of our decision to postpone contribute, our annual GitLab team event. Operating cash use was $36.3 million in second quarter of FY 2023 compared to $17.1 million used in the same quarter last year. In summary, we're pleased with our operating performance during the second quarter of FY 2023 on both the top and bottom line and believe our business is set up for continued strength. We continue to see rapid growth while improving the underlying unit economics in the business. we monitor the key leading indicator metrics of our business and we are not seeing any softening in these indicators now let's turn to guidance for the third quarter of fy 2023 we expect total revenue of 105 million to 106 million dollars representing a growth rate of 57 to 59 year-over-year We expect a non-GAAP operating loss of $27.5 million to $26.5 million. And we expect a non-GAAP net loss per share of $0.16 to $0.15, assuming 149 million weighted average shares outstanding. For the full year FY 2023, we now expect total revenue of $411 million to $414 million, representing a growth rate of 63% to 64% year-over-year. We expect a non-GAAP operating loss of $111.5 million to $108.5 million. And we expect a non-GAAP net loss per share of $0.67 to $0.64, assuming 148 million weighted average shares outstanding. On a percentage basis, our new annual FY 2023 guidance implies non-GAAP operating margin improvement of approximately 1,250 basis points year-over-year with the midpoint of our guidance ranges. A few more details on guidance in our model. We now estimate that we will incur approximately $17 million of incremental expenses related to the resumption of travel and in-person customer and marketing events, as well as new public company costs that were not incurred in the first three quarters of FY 2022. In addition, we forecast approximately $20 million of expenses related to Jihoo, our China joint venture. This compares with $12 million of combined Jihoo and Meltano costs in FY 2022. I'd like to note we have deconsolidated Meltano, our majority-owned subsidiary. on the finance team front dale brown our principal accounting officer has shared his intentions of retiring next year i want to thank dale for all his contributions over the last three years in allowing for a smooth transition as sid mentioned earlier we believe we're addressing a very substantial market opportunity that is currently under penetrated and that we're well positioned to capture our outsized portion of it There has been no philosophical change in how we run the business to maximize shareholder value over the long term. We continue to be focused on growth while driving improvements in the unit economics of our business. With that, we'll now move to Q&A. To ask a question, please use the chat feature and post your question directly to IR questions. We're ready for the first question.
spk00: Thank you, Sid and Brian. We'll begin by going to Cash at Goldman Sachs. Cash, will you please verbalize your question?
spk09: Sure. Happy to. Thank you so much. Congrats on the quarter and great operating margin improvement. Sid, when you look at the landscape competition, Microsoft has been talking about how it's not just about collaboration with developers, the collaboration among office workers is a big thrust behind Teams. You also see Atlassian going through a cloud transition. They've made collaboration amongst developers and non-developers a key priority. And Monday has chosen developer persona. So everybody is trying to make inroads into a domain that you have natural focus and concentration. How does this change the comparative landscape? Is there an accelerant because there's more awareness of what you can do for productivity in the software development lifecycle? and how does your competitive position change or not change? And one for you, Brian, as you go through the puts and takes of the income statement, cash flow, et cetera, with the one-time joint venture expenses, how should we be thinking about the trajectory of next year, calendar 23, with respect to some of the underlying improvements in operating efficiencies that may not be otherwise apparent? Thank you so much.
spk10: Thank you so much, Kesh, for those questions. So if you look at GitLab, it's not just for developers. It's for developers, security people, and operations people. And getting them to collaborate, well, that's the essential part. Because then you can get from, hey, we plan to do this, to getting it out there, getting it in the hands of your customers, getting feedback. So closing that loop is the most important thing. And we have the leading DevSecOps platform, in our opinion. really spectacular because think about security. It's a really big market. We are replacing vendors like check marks, Veracode, Synopsys, because we have the whole thing. We have static and dynamic analysis. We have container and dependency scanning. We have the best processing tools in our opinion in the market. And not only do we have the most comprehensive security offering, we're able to link it with a really compelling dev solution. We are expanding into operations so people can do the entire cycle. That's the power of one platform. And we believe that is really attractive in the market. And so we're not in a chat tool business or something like that, but we do have the most comprehensive DevSecOps solution.
spk13: cash i'll answer the question just around cash flow and so forth yeah i'm really happy uh you know with the business and the fact that you know we have a ratable business so it's got a lot of visibility we're really pleased with the trends that we're seeing um the number one thing that said and i have articulated to on the roadshow as well as to the investor bases growth is the number one thing that we want to do but we'll do that responsibly if you look at the second quarter uh we delivered 101 million in revenue with the non-gap operating loss of 27 million if you compare that to second quarter of last year we added 43 million of incremental revenue at the same operating loss if you extract jihu if you look at our guidance at the midpoint uh we're gonna we're gonna deliver approximately 160 million of additional revenue this year over last year at an improved absolute operating loss than what we did last year You take away Jihoo and some of the one time events that we went through. So I'm really happy on the incremental improvements that we've been making and the improving union economics. Thanks so much.
spk00: Our next question is from Carl at UBS.
spk10: Oh, if you're talking, you're muted.
spk13: Charlie, we go to the next one.
spk00: Next, we have Matt at RBC.
spk04: Hey, guys. Thanks for taking my questions. Congrats on the quarter. Sid, I wanted to start with you. You know, I'm curious, in your prepared remarks, you called out a cloud or a SaaS win. And I asked you this a couple of years ago, but I'm curious for an update here. Is there a network effect that customers see from increased cloud adoption? Do they all benefit from your learnings of what's happening with your SaaS deployment?
spk10: I think there's something to that with SaaS. You're able to run experiments on a more gradual level and you're able to see more detailed results. So the data we get from our SaaS services on like how new features are performing helps us improve the product for everyone. So increased SaaS users means we know better how our customers are using the platform, what features they enjoy, what we should improve, and that improves the product for both SaaS and self-managed customers.
spk04: Super helpful. Yeah, we love seeing the increased traction there. And then Brian, one for you. I mean, it sounds like you're not seeing any real macro pressure. It doesn't feel like you're embedding anything into your guide. Was it sort of just, you know, like the linearity question? Was it sort of business as usual for you guys? Was there any more back end loaded nature of the quarter? Just maybe a little bit more granularity on that side?
spk13: Yeah, absolutely. We're super happy with the quarter to grow 74% year over year. And then also to add the largest number of base customers in the company history. When we went back and looked at the sales cycles, the sales cycles are actually compressing this quarter. So we didn't see any elongation. One of the things that as I was preparing for this earnings call and listened to a number of other CEOs and CFOs talk, you know, really with the mission-critical applications and software, people are seeing, you know, moving away from the point solutions into a platform. And so we saw a lot of that this quarter and really happy with the results that we delivered. Congrats, guys. Thank you.
spk00: Next, we'll move on to Michael from KeyBank.
spk08: Hey, guys. Maybe I'll ask both at once, but first, Sid, you know, I think there are It's fantastic what you've done. And it's in an environment where people are cutting back, including some reports of developer hiring cutting back. So at that high level, what's making it work that you continue to grow up with these rates, even while some developer hiring is cutting back? And there are probably some projects that are being cut. And then I have a quick sort of housekeeping question for Brian.
spk10: Awesome. Well, thank you very much, Michael. We're definitely seeing that companies are coming back on hiring developers, that they are sometimes instituting a hiring freeze. And the situation they're faced with is that they have to do more with the people they already have. And GitLab enables them to do that. When they move to GitLab, they save on the integration effort. So the people who before were doing the integration of DevOps tools can start doing something that adds value to the business directly. Second, older existing people get more efficient with GitLab because you don't have to go from point solution to point solution to point solution to get more work done in a day. So they can, without hiring, it kind of feels like they have more development capacity. And last, but certainly not least, by GitLab helps them to go faster. So they're able to move to the cloud faster, close their data centers and free up those people to directly add to their business. So on three levels, moving to a platform helps. And that's why in this environment, GitLab is mission critical. Companies are willing to free up budget for it. And it's not an option to not do this. They have to undergo the digital transformation. They have to move to the cloud.
spk08: James Rattling Leafs. Thanks and then Brian somewhat like last time you didn't have strong upside on the license side of the business, but last quarter, there was something of a boost from. James Rattling Leafs. The way that you account it says your your standalone selling accounting and so it boosted reverence a little bit, but was there any change in in what that year over year boost would have been I think we're looking forward to for a couple million dollars.
spk13: Yeah, before I answer that, let me just add on to Sid's comments just a little. Our cohorts from seven years ago are still expanding with us today. So you were asking about developer hiring. One of the things that we look at internally is landed TAM. And so when we land an account, cohorts from seven years ago are still expanding with us today. Every single quarterly cohort has been doing that. And so there is a lot of upsell within all of these accounts. that we currently have today. And they start with premium, they expand division departments, eventually they upgrade to ultimate and so forth. And so we feel that there's, despite some of the hiring things, there's a lot of landed TAM for us to address. On the license side, I talked about the record quarter of base customer ads. We just had a great quarter, and we do recognize a small portion of the revenue up front, and that's what impacted the license revenue. With ASC 606, you do an annual assessment. And so the percentage that we use this year versus last year, slightly higher. And we will use that every quarter for the remainder of this year. And then as we go into first quarter of next year, we'll do another annual assessment and see where that's at.
spk08: Thanks, Brian. Thanks.
spk13: Thanks, Michael.
spk00: Our next question is from Rob from Piper Sandler.
spk11: Great. Thanks for taking my question. I'd love to just drill down a little bit more relative to the record quarter of base customer ads. And so is this maturity of the platform? Is this economic? Is it channel? Can you kind of stack rank for us why you're seeing such success right now in this environment relative to those new net ads? And then I do have a follow up for Brian.
spk10: Yeah, thanks for that. We believe that we're very early in a big market opportunity. Us and our biggest competitor together, we're less than 5% of a $40 billion market. Gartner said that DevOps platform adoption is 20% now, going to 60% over a couple of years. And if anything, the need to consolidate, the need to have fewer tools, less integration efforts is only accelerating. Companies can't afford anymore to spend and solve everything by hiring more people. So the macroeconomic challenges that company faces only makes it more of an imperative to consolidate, to go to the cloud faster and to embrace platforms like GitLab.
spk11: Great. And then, Brian, building a little bit on Matt Hedberg's question around linearity, you did see AR creep up. And so if we match that kind of a Billings days outstanding, higher than previous quarters. So is this linearity? Is this economic? Is this big deals? Are these new levels should be sustained moving forward? Can you help us out a little bit on that front? Thanks.
spk13: Yeah, I would just say that on the billing, we had two invoices, one that's been collected, one that we'll get any day now. And so that's on the billing that you've seen sort of the DSOs take up a little. And I would just say for the quarter, there wasn't really anything outside. in the quarter that happened that hasn't happened in other quarters and so you know we landed a you know we had our we had a record quarter as well with aws and gcp contribution and so once again another large quarter income the largest quarter in company history of what they contributed as well and do those tend to lag relative to to payments They do not. They're relatively same payment terms.
spk10: All right. Thanks. And Rob, maybe to add to that, maybe give you an example. We had a global airline manufacturer sign with us this quarter. And they are not in the business of spending more money right now. They're in the business of spending less money. But it is an imperative to get better at development, security, and operations. And they became a customer this quarter, even though there's a lot of ways in which every company needs to save money, they make the budget available to become a customer from previously using GitLab for free. Great. Thanks for the color.
spk00: Next, we'll move on to Joel Atruist.
spk05: Thank you for taking my questions, one for Sid, one for Brian. Just to follow up on that, Sid, I would love to get your take on some of the partnerships that are really driving value for you right now and how you're positioned with them. And Brian, just to double down on that operating leverage, I know you talked about some of the operating leverage was driven by revenue outperformance, but I'd love to know what the other major drivers are of operating leverage going forward. Thank you.
spk10: Thanks so much. I'll go first. I'll let Brian add. The most important partnerships for us are the ones with the hyperclouds. And they're important for us because more and more of the purchasing is happening via these hyperclouds. They're influential in accounts. They have access to the important C-level people. We are important to AWS, GCP. We mentioned we won a GCP award because they know if GitLab is in the account, they move to the cloud faster. The fastest way to do the cloud migration is to first get on one platform and then move, not to try to move 10 different point solutions at different speeds. That is way more hassle. So it's a partnership that's very symbiotic, and we're super excited about the additional opportunities that are in partnering with hyper clouds like that and great partners like IBM that we love to work with.
spk13: And Joel, on the operating leverage side of me, we're seeing operating leverage across the business in all aspects. One great example I'll give is 2Q of this quarter versus 2Q of last year. Last year was 88%. non-gap gross margin and this quarter was 89 so even though with sas growing as fast as it is and cost us more to deliver um we're still putting in operational efficiencies to improve you know our delivery cost you know within the company we pretty much have uh you built out the management layer most of the net ads that we're doing is for capacity and in r d to improve to continue the enhancements and the releases that we've done. And so across the entire business, we're seeing operating leverage in the business model.
spk05: Thank you very much.
spk00: Next, we have Koji from Bank of America.
spk02: Hey, Sid. Hey, Brian. Thanks for taking the questions. Just kind of a follow-up here on the record net new customer ads. Really great number there. Wanted to ask kind of on the average land ASP for those customers. Are they coming in bigger now, or are they coming in about the same from a historical perspective? And how are you thinking about customer land ASPs in the future, given all the macro factors that are going on out there?
spk13: Yeah, I'm happy to take that, Koji. Thank you. The trends that we've seen, we've seen increasing ASPs across all segments in the business. And so we haven't seen, you would expect on some of the reports that people have talked about in the industry that you may see a decline. We haven't seen that. And so we've seen an uptick across the board, and that's been consistent with all the other quarters.
spk02: Got it. Thanks, Brian. And then just one follow-up here for maybe Sid or Brian. I noticed in the press release, you announced a partnership with a bunch of companies like Dynatrace and LaunchDarkly to launch this feature, open feature. So I guess, could you explain maybe from a high level, what is open feature and what sort of opportunity does this unlock for GitLab? Thanks, guys.
spk10: Yeah, thanks for the question. So open feature is a standardized way to make feature flags. Feature flags is functionality that allows you to put mostly new functionality to turn that on and off really quickly. It helps a company to release faster and more frequently while being able to quickly remediate if something gets broken. We already offer feature flags in GitLab today, but we want to make them better over time. And we're excited to partner with Dynatrace, Google, LaunchDarkly, a whole bunch of great companies in order to standardize this. And we believe that feature flags are much better as part of a platform. Feature flags hook into your source code. They need to hook into your observability. And with GitLab, we can make that work right out of the box. Got it. Thanks, guys. Thanks for taking the questions.
spk02: Thank you.
spk00: Derek at Cohen, will you please verbalize your question?
spk12: Great. Thanks. Good to see you guys. I mean, so we've heard from a lot of CIOs that consolidation, vendor consolidation is certainly a priority. Obviously, that caters to your strategy very well, and it sounds like that's been a driver. Would you say that the macro environment has actually accelerated the rate of legacy displacements in the last quarter or two? And are there certain verticals that you would say consolidation is a bigger trend or a bigger tailwind for you?
spk10: Yeah, we're certainly seeing that with customers that say, look, we need to consolidate and we want to move to fewer tools. And that's why we're considering GitLab. So there's a tailwind in this macroeconomic environment. You have to be able to save people money, do more with fewer people. So that's been a great thing. We are seeing that across all verticals. All verticals are cutting back and want to consolidate. We do see that the more projects companies have and the more tools they have, the more compliance they need, the more attractive it is to consolidate because kind of their complexity grows almost exponentially. But we believe that's also kind of just the future, like companies are going to have more and more future software projects. Companies are going to need more compliance, whatever industry you're in. So it's been consistent across verticals.
spk12: Great. Thanks. Maybe one for you, Brian. Last quarter, you talked about, you know, me having a record pipeline. Clearly, it doesn't sound like you're seeing any macro headwinds, but could you just compare and contrast what you're seeing out of, you know, Europe versus the U.S.? ?
spk13: Yeah, I would just say we have strong macro tailwinds around digital transformation and the growing security threat landscape. The pipeline across the entire company is the strongest it's ever been. Win rates have been pretty consistent with last quarter, and we're not seeing deals being pushed. Great to hear. Thanks. Thank you.
spk00: Now we move on to Jason from William Blair.
spk06: Thank you. Hi, guys. First one for Sid, on their earnings call last week, MongoDB talked about the consumption-based model and linkage to application utilization as reflecting almost a real-time view of the macro environment, which according to them is getting worse. My question is, how would you compare and contrast where you guys sit relative to Mongo and your confidence in terms of how close you are to feeling macro impact in real time?
spk10: Yes, we're a different model. We charge per user per year. And we're seeing that there's a lot of upside for us still. So there's a lot of ways to grow within the companies we're already at. We're nowhere near having all their users. And we have a lot of room to grow in up-tiering from free to paid, but also from premium to ultimate. So we're not seeing those consumption headwinds. And in fact, as we talked about before, companies now need to save money. And GitHub is a way to save money and make your existing people more effective to do more despite having a hiring stop. Brian, anything you want to add?
spk13: I would, you know, same thing. I mean, we have great visibility. You know, one of the great things about being a ratable model is we have great visibility into the revenue. And then, you know, with having, you know, over 200 open recs and being able to see the pipeline, we can adjust anything from a macro perspective. But we haven't, you know, we haven't seen anything. And so we're super happy with, you know, the base customer ads, our net dollar retention rate, you know, the operating leverage that we're having in the business. And so across the board, you know, we're very pleased with the trends.
spk06: And then one quick follow-up for you, Brian. Can you remind us at a high level on expectations for Jihoo for next year, both in terms of OpEx and revenue contribution?
spk13: We haven't given out anything for next year yet on Jihoo.
spk06: Okay. But at some point you're going to get some revenue contribution, correct?
spk13: That is correct.
spk06: Okay. Thank you.
spk13: Thank you.
spk00: Next we have Carl at UBS.
spk03: Michael Perlmutter, Okay, great thanks for taking the question sorry about before hey Brian maybe this is for you on the on the three Q revs guide 59% pretty phenomenal but optically it's a 15 point D cell on an 11 point easier compare. so i just wanted to press you is there anything either in the year ago period or in the coming october period that might be distorting that comparison any one-time stuff maybe anything related to the ssp issue you call the last quarter to uh to share with all of us thank you
spk13: Yep. Thanks for your question. You know, we're super, super happy with our performance and guidance. We beat by 7 million, we raise the full year by 12 and a half million at the midpoint. We're currently guiding to a 63 to 64% year over year revenue growth. And then our guidance includes impact of Russia, the true ups. We don't have FX exposure, but we bill and collect in US dollars. And so there's other companies out there who, based on the currency devaluation, it's more expensive for them to buy. And so all that we've put into our guidance. I'm really happy that we've been able to raise the annual guidance and continue to get operating leverage in the business. If I look at the guidance from the beginning of the year, we've increased guidance by 24 million at the midpoint of 1Q, and we're doing this for 30 million less in non-GAAP operating income.
spk03: Yeah. Okay. Agreed. Thank you, Brian.
spk13: Thanks, Carl. Appreciate it.
spk00: Next, we have Pendulum at J.P. Morgan.
spk01: Oh, great. Hey, thank you for taking the questions and congrats from me as well for the fantastic order. I want to ask you about the free user moments that you're seems like putting in place that will go into October of this year, I believe. Is it possible to quantify kind of number of users that will be impacted or should we, how should we think about the impact of that change to the business or in Q4 next fiscal year or do you say it's going to be material?
spk10: Yeah, thanks for that. So we want to make sure that our free plan is sustainable. So we've instituted storage and user limits, and that's going to help us become more efficient. Some of the users will opt to reduce their usage or leave, and some of them will opt to to become a paid customer. And that that is baked into our guidance.
spk01: OK, understood. And one for Brian. The net retention rate seems like it's 130% pretty good. Is it possible to directionally understand that number, maybe in terms of the gross expansion of the gross churn within that particular number directionally, if it is up or down versus last quarter?
spk13: Yeah, let me just a point of clarification. We report that is a threshold greater than 130%. So it's not 130%. And in my prepared remarks, I said it was actually consistent with prior quarters. And so that should give you some indication where that's at. You know, number one thing from a net dollar retention rate is additional seats. And then number two is up-tearing to ultimate.
spk01: Got it. Thank you.
spk00: Our next question comes from Nick at Scotiabank.
spk14: Yeah, great. Thanks, guys. You guys mentioned that, you know, sales cycles are shortening, land ASPs are increasing. Can you just talk about what's driving that? Because I think it's something you guys have called out several times recently. Like, is it more just, you know, you guys have a more mature go to market motion now? Is it more that the top-down sales motion is allowing for quicker budget approvals? Just any color you can give around that I think would be helpful.
spk13: Yeah, happy to. Thanks for the question. When we were getting ready to go public, one of the things I talked about was we're adding a whole bunch of new go-to-market motions. Up until that time, the company was primarily a direct sales go-to-market. And since then, we added alliances, hyperscalers, a channel program and so forth. And so we've added a number of new go to market motions. They're still relatively early, but we're very happy with the progress we've seen. As I mentioned, the hyperscalers, AWS and GCP combined had their largest quarter with us in company history, and we're seeing a lot more deals come through that channel. And so really happy across the board. We wanted to be aware of a lot of other comments that were made. And so we went and looked at deal cycles and looked at that. We looked at ASPs. And I think it just goes, as Sid alluded earlier, we're so early in such a big market and people are wanting to get rid of point solutions and move on a platform. to develop software better, faster, more secure. And that's what our platform does. And so as we get greater penetration, you'll see the results that we're publishing.
spk14: Great. And then just another quick one. The federal side of the business is roughly 10% of revenue. Can you just give an update there, just given that fiscal year is closing? How's that pipeline looking? Was there any contribution from that sector that fell into 2Q? Any color around that would be helpful.
spk10: We're super happy with how we're doing in the public sector and in the government market. And that's what we're doing is baked into our guidance, but we're seeing increased adoption and we're very happy with how that is developing.
spk14: Great. Thank you.
spk00: Our final question comes from Mike at Needham.
spk07: Great. Thanks for squeezing me on, guys. First question I had was with respect to these sales cycles we're talking to and wanted to see if we could slice it up just a little bit differently here. Is there a way to give a sense for the magnitude of what the delta is when thinking through those shortening sales cycles? Or better said, I guess, how much would you attribute to the elevated conversations or engagement that you guys are having with the c-suite what is the durability in your view of these shortened sales cycles or is it really just a data point today not yet calling a trend as far as these these shorter cycles we're seeing and then i have a follow-up as well thank you
spk13: Yeah, I think you're right on that. It's just a data point that we wanted to point out. As we prepare for these calls and look at all the data across the board, this is something that was mentioned or asked about on a lot of other calls. And so I think the awareness of just a DevOps platform and GitLab helps. And then also the time to value and business outcomes that we're driving. And a number of people wanting to get rid of point solutions to get on a platform for the efficiency. I think all these are key characteristics that contribute to the shortening of sales cycles.
spk07: Thank you for that. I appreciate it. And if I could just follow up with one other question, it was more around the GitLab v15 launch that you guys spoke about. You highlighted three things, one of them being the AIML. And I think it probably goes back to some of the earlier comments from you guys with respect to how early we are in this $40 billion tan. But I just want to take broad, broad strokes here for a second. If I think about DevOps, like we've been talking about this now since I want to say like 2008, 2009 timeframe, and DevSecOps, maybe 2014, 2015 timeframe. And both of those are still very, very early. Now we're talking about DevOps plus MLOps, which is intuitive, makes all the sense of the world to me, but just wanted to get a sense, again, how early stage are we I have to imagine that the decision to combine those two workflows is based on customer feedback. But if you could frame out those parameters in any way, I would definitely appreciate it.
spk10: Yeah, thanks for that question. If we look at AIML, there's two things happening. We're using it to make GitLab better. And a great example of that is code reviewers. GitLab will now suggest, hey, this person might be the best person to review your code. So that's making GitLab, the DevSecOps workflow better for everyone. The other thing is helping data scientists do their work. Today they have a completely different tool stack. And that tool stack kind of would really benefit from kind of the practices that are already prevalent in DevOps. We're starting there now with features like better Jupyter Notebook divs. And after launching that, we've seen the usage of Jupyter Notebooks in GitLab increase. We'll continue to add to that. For example, while our planning is fluid, we're considering a model registry, adding that to GitLab in the future. We're not sure we will do that, but that's something we're looking at. These investments will bear fruit over a very long period of time. So it's not that we're going to be great tomorrow, but we're sowing the seeds and together with the wider community, we see a great convergence happening where the AI ML engineers have to collaborate with the DevSecOps people and vice versa, because every significant application in the future will need both.
spk07: Thank you for that. I appreciate the color and I totally appreciate how this is all very early, but great to see how you guys are thinking about the broader picture here and looking forward to seeing more with respect to the evolution of the platform. Thank you. Thanks so much.
spk00: With that, I'll turn things back over to Sid for closing remarks.
spk10: Thank you for your time today. I'd like to thank our customers for trusting GitLab. I'd also like to thank our partners and the wider GitLab community and all of our GitLab team members for all of their contributions. We all have a big part in our continued success. Thank you very much.
spk00: Thanks again, everyone, for joining us. Have a great day.
Disclaimer