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.
spk01: Welcome to the Q3 2021 Data Dog Earnings Conference call. My name is Adrienne. I'll be your operator for today's call. At this time, all participants are in listen-only mode. Later, we'll conduct a question and answer session. During the question and answer session, if you have a question, please press star and 1 on your touch-tone phone. I'll now turn the call over to Yuka Broderick, Head of Investor Relations. Yuka Broderick, you may begin.
spk11: Thank you, Adrienne. Good evening and thank you for joining us to review Datadog's third quarter 2021 financial results, which we announced in our press release issued after market close. Joining me on the call today are Olivier Pommel, Datadog's co-founder and CEO, and David Opsler, Datadog's CFO. During this call, we will make statements related to our business that are forward-looking under federal securities laws and are made pursuant to the safe harbor provisions of the Private Securities Litigation Reform Act of 1995, including statements related to our future financial performance, our outlook for the fourth quarter and the full year 2021, our strategy, the potential benefits of our products, partnerships, investments in R&D and go-to-market, our ability to capitalize on our market opportunity. The words anticipate, believe, continue, estimate, expect, intend, will, and similar expressions are intended to identify forward-looking statements or similar indications of future expectations. These statements reflect our views only as of today and not as of any subsequent date. These statements are subject to a variety of risks and uncertainties that could cause actual results to differ materially from expectations. For discussion of the material risks and other important factors that could affect our actual results, please refer to our quarterly report on Form 10-Q for the quarter ended June 30, 2021, filed with the SEC on August 6, 2021. Additional information will be made available in our quarterly report on Form 10-Q for the quarterly period ended September 30, 2021, and other filings and reports that we may file from time to time with the SEC. Our filings with the SEC are available on the investor relations section of our website. A replay of this call will also be available there for a limited time. Non-GAAP financial measures will be discussed on this conference call. Please refer to the tables in our earnings release, which you can find on the investor relations portion of our website, for reconciliation of these measures to their most directly comparable GAAP financial measures. With that, I'd like to turn the call over to Olivier.
spk03: Thank you, Gab, and thank you all for joining us this evening. We are extremely pleased with our performance in Q3, which was stronger than expected, on robust growth with existing customers, as well as strong new customer sales. We saw broad-based strengths across product lines and across customer segments. Let me give you a quick summary of the quarter. Revenue was $270 million, an increase of 75% year-over-year and above the high end of our guidance range. We ended the quarter with 1,800 customers with ARR of $100,000 or more, up from 1,082 in the year-ago quarter, These customers generated about 80% of our ARR. We have about 17,500 customers, which is up from about 13,100 last year. The leverage and efficiency of our business model is coming through, with free cash flow of $57 million. And our dollar-based net retention rate continued to be over 130% as customers increased their usage and adopted our newer products. At a high level, positive business trends from recent quarters continued in Q3. Usage growth from existing customers was very strong this quarter across products. Utilizable ARR was robust, with some large new deals closing. And churn remains low and in line with historical rates. Taking all these factors into account, we had a record quarter of ARR added. And we crossed the milestone by exceeding $1 billion in ARR in Q3. Next. Our platform strategy continues to resonate in the market. As of the end of Q3, 77% of customers are using two or more products, up from 71% a year ago. Additionally, 31% of customers are now using four or more products, which is up from 20% last year. And this quarter, about 70% of new logos landed with two or more products. Most strikingly, our whole platform saw strong growth in the third quarter. I point out in particular that all of our major products added a record amount of ARR during the quarter, but also that the year-over-year growth of infrastructure monitoring ARR on its own accelerated this quarter. And finally, that our log management and APM suite, which includes synthetics, reason monitoring, and continuous profiler, remain in hypergrowth mode. Together, in Q3, they exceeded 500 million in ARR. Now let's move on to product and R&D. Our teams continue to innovate at a rapid pace. We had 48 new product-related announcements in Q3, and we made many announcements last week at Dash, our annual user conference. You can review our Dash press releases as well as tonight's earnings for further description. But to summarize this briefly, we announced the availability of CI visibility, session replay, funnel analysis, network device monitoring, Datadog apps, and online archives for log management. We launched private betas for cloud cost management, observability pipelines, universal service monitoring, and application security. And we also announced official Datadog support of the Vector open source product. Now looking back at a couple of these announcements, some of them would increase Datadog's usefulness for business personas, users who are not engineers and can benefit from all the data flowing through Datadog. With session replay and send analysis, we believe support organizations, product designers, and product managers can get value from understanding user behavior and interactions with applications. And we expect cloud cost management will be useful to anyone involved in understanding and controlling the expense of cloud implementations, from engineering teams to product managers to finance teams. We are also advancing our efforts to support our customers with large-scale complex data needs. So I want to talk a bit about Vector, Observability Pipelines, and online archives. Nine months ago, we acquired Timber, the developer of Vector. Vector is an open source product that allows users to collect, enrich, and transform observability data and automatically route it to the destination of their choice. Our Observability Pipelines product extends Vector and increased enterprise-level capabilities for its data pipelines and the ability for users to seamlessly manage it from Datadog across both on-premise and cloud accounts. Vector and observability pipelines let customers make value-based decisions on data as early as possible before they send data to Datadog or any other partner. We are always looking for ways to give customers more control over how they use their data and how they manage the cost of their cloud deployments. This is another step in that direction. And with Online Archives, we are aiming to solve the growing problem of storing all logs and being able to run complex historical investigations on them. Online Archives is an always-on log warehousing solution that provides 15 months or more of extremely cost-effective storage and life-quaring ability. I also wanted to mention database monitoring, which we announced for general availability in August, and which gives our customers deep visibility to the performance and execution of queries across all of their databases. Finally, as announced in the press release issued this evening, we acquired HostCode, a live debugging solution for .NET applications, which lets developers solve problems in real time, whether in development or in production environments. It is another example of our growing push into developer workflows. So as you can tell, we are very busy in Q3, and I want to thank our engineering and product teams for their hard work and their relentless focus on our customers. Now, moving on to sales and marketing. Our go-to-market teams continue to be very productive, and we added 1,100 new customers this quarter. So let's review some of our Q3 wins. First, We had our largest deal ever by total contract value, an over $60 million five-year upsell with a multinational financial services company. Our history of success with this customer has led to the use of nine products, including early adoption of newer products such as ROM, Synthetix, and NPM. This customer began the second phase of their migration to the cloud and is standardizing on Datadog, adopting our newer products as we add them to our platform. Next, we had a seven-figure upsell with a global fashion retailer based in Asia. These customers saw e-commerce sales increase dramatically during the pandemic and then began to use Datadog after several outages resulted in missed sales. After a disappointing implementation of a competing solution, they chose Datadog APM across their global e-commerce sites and saw immediate improvement in stability. Next, we had a six-figure land with a US-based professional sports league which came in partnership with Google Cloud Platform. This customer experienced a large spike in application usage, as fans are returning to games following the pandemic. But they had no client-side monitoring, and therefore no way to analyze and optimize the user experience. With Datadog real user monitoring and synthetics, along with infrastructure monitoring and APM, the customer now has a single solution to manage experience from front-end to back-end. Next. We had a seven-figure land with the advertising division of a Fortune 10 company. This company has very strict SLAs for their platform, as their customers rely always on availability to adjust ad budgets in real time. After conducting a full evaluation of internal solutions and EPM providers, this customer began using Datadog infrastructure monitoring and EPM and are motivated to expand their usage of our platform within the enterprise. Finally, we had a large six-figure land with a US distributor of plumbing and building equipment. This company needed to migrate from on-premise to Azure and to deploy on Azure's Kubernetes services. But its existing APM solution had limited visibility into containers. With Datadog, this customer is able to effectively monitor the health of their Azure ecosystem, allowing them to confidently and efficiently complete migrations and retire legacy infrastructure. As you can see, Our go-to-market teams had another quarter of strong execution. I want to thank them for once more successfully helping both new and existing customers to generate value from Datadog. Now moving on to our longer-term outlook. If you could not join us for our investor meeting last week, I encourage you to watch the video on the investor relations section of our website. At the meeting, we described our long-term opportunities, our differentiators, and the expansion of our platforms over the years. To summarize my bit of the presentation, we see digital transformation and cloud migration as large forces driving exponential growth. We believe Datadog helps solve the growing problem of managing complexity for our customers, and that our open-ended unified platform designed to be simple but not simplistic is deployed everywhere and used by everyone at our customers, and that it helps break down silos between teams. We believe it is still early days for our opportunity in observability. And while we have made a lot of progress in building out a broad observability platform, we still have much to do to solve all of our problems customer pain points. One next step for us is in security with our cloud security platform. And we believe we have a part to play in breaking down silos between development, operations, and security teams. but we're also making our first inroads in pure developer workflows with the general availability of CI visibility. And we think over time, we have opportunities to help our customers in several other large adjacent markets as well. In other words, we are just getting started. With that, I would like to turn the call over to our CFO. David?
spk17: Thanks, Olivier. In summary, we had a very strong Q3. Revenue was $270 million, up 75% year over year, and up 16% quarter over quarter. Use trends were strong and showed broad-based growth. Customers continued to adopt more products across the platform, and new logo generation was also strong. To provide some more context, first, growth of existing customers was robust in Q3. and our dollar-based net retention rate remained above 130% for the 17th consecutive quarter. Usage growth was very strong, driven by customers' expanded usage of existing products and the adoption of new products. Our new customers from the last several quarters have expanded their usage quite rapidly, and we had some significant renewals with large customers in Q3. We also had a record quarter of ARR ads, including record ARR ads in all of our major products. And we saw strong growth across geographical regions with all regions accelerated on a year over year basis compared to Q2. New logo results were also strong. Our enterprise and commercial sales teams had a crisp execution in this quarter. and new logo ARR was up strongly year over year. We continue to see opportunities broadly across industries and customer sizes. Remember that given our usage-based revenue model, new logo wins generally do not immediately translate into meaningful revenue. Next, our platform strategy continues to resonate with customers. And as we mentioned, 77% of our customers are now using two or more products, and 31% of our customers are using four or more products. And lastly, churn remained low and in line with historical levels. Our dollar-based gross retention rate remained unchanged in the mid-'90s and is similar across all our customer segments and products. Turning to billings, The billings were $309 million, up 98% year-over-year. There were no pro forma impacts in the quarter. Note that we called out shorter term billings duration in Q3 of 2020 last year, and billing duration in 3Q of this year is in line with recent quarters, but is higher on a year-over-year basis. driving higher year-over-year billings growth. Remaining performance obligations, or RPO, was $719 million, up 127% year-over-year, driven by strong sales activity, increased contract duration, and it was growing against an easier compare in the third quarter of last year. The increase in contract duration was driven by several large renewals with multi-year terms, As a reminder, multi-year commitments are built annually and we don't incentivize our sales team towards multi-year deals. Current RPO growth was about 100% year-over-year as our mix shifted away from month-to-month deals on a year-over-year basis more towards semi-annual and annual. We continue to believe revenue is a better indicator of our business trends than billings and RPO as those can fluctuate relative to revenue based on the timing of invoicing and the duration of customer contracts. Now let's review the income statement in more detail. As a reminder, unless otherwise noted, all metrics are non-GAAP. We have provided a reconciliation of GAAP to non-GAAP financials in our earnings release. Starting with gross profit, our gross profit in the quarter was $210 million. representing a gross margin of 78%. This compares to a gross margin of 76% last quarter and 79% in the year-ago quarter. Due to our continued efforts to drive efficiencies in cloud costs, we expect our gross margin to increase sequentially in Q4. In the mid to long term, we expect gross margin to remain in the high 70s range, typical of a historical performance. R&D expense was $84 million, or 31% of revenue, compared to 30% in the year-ago quarter. We continued to invest significantly in R&D, including high growth in our engineering headcount. Sales and marketing expense was $65 million, or 24% of revenue, compared to 32% in the year-ago quarter. We continue to see strong efficiencies with our frictionless land and expand selling motion. We also had relatively few in-person events in Q3, but we continue to plan for increased travel and events costs going forward, depending on local health and travel guidelines. G&A expense was 17 million, or 6% of revenues, compared to 8% in the year-ago quarter. Operating income was $44 million, or a 16% operating margin, compared to an operating income of $14 million, or 9% in the year-ago quarter. We continue to invest heavily against the large and dynamic market opportunity we see in front of us. But our product innovation, coupled with a strong go-to-market effort and a frictionless land and expand model, is driving strong revenue growth and business model efficiencies. Non-GAAP net income in the quarter was $44 million, or 13 cents per share based on 344 million weighted average diluted shares outstanding. Turning to the balance sheet and cash flow, we ended the quarter with $1.5 billion in cash, cash equivalents, restricted cash, and marketable securities. Cash flow from operations was $67 million in the quarter. After taking into consideration capital expenditures, and capitalized software, free cash flow was $57 million for a free cash flow margin of 21%. Now for our outlook for the fourth quarter and the full year 2021. We remain highly optimistic about our long-term opportunities and we continue to work hard to execute against these opportunities. Taking this into account, with the usual conservativism applied, we are updating our guidance as follows. For the fourth quarter, we expect revenues to be in the range of $290 to $292 million, which represents 64% year-over-year growth at the midpoint. Non-GAAP operating income is expected to be in the range of $38 to $40 million, and non-GAAP net income per share is expected to be between 11 and 12 cents per share based on 347 million average diluted shares outstanding. For the full year 2021, revenue is expected to be in the range of 293 to 293, excuse me, to $995 million, which represents a 65% year-over-year growth at the midpoint. Non-GAAP operating income is expected to be in the range of $113 million to $135 million, And non-GAAP net income per share is expected to be in the range of $0.39 per share to $0.40 per share, based on approximately 344 million weighted average shares outstanding. Now some notes on guidance. While usage growth remains strong in Q3, when providing guidance, as usual, we use more conservative assumptions. We would note that we typically see slower business activity towards the end of the fourth quarter as employees take vacations around the winter holidays. Next, our strategic focus remains to invest aggressively in R&D and go to market to optimize for the long-term growth. And our model assumes greater expenses related to travel and in-person events going forward. However, we will remain flexible depending upon local regulations and our highest priority is protecting the health of our employees. Regarding items below operating income, we expect approximately 0.7 million of Q4 non-GAAP net interest and other income, which includes interest income on our cash and marketable securities and the interest expense of our convertible debt. We do not expect to be a federal taxpayer, but have a tax provision related to international entities. We expect that tax provision to be approximately $600,000 in Q4 and $2 million for the full year. And now to summarize, we are very pleased with the results of this quarter. Our platform is resonating in the marketplace, and we saw strong performance across our products in Q3. We continue to invest aggressively in R&D, and with the launch of database monitoring and CI visibility, we now have 13 generally available products to offer our customers. Our execution against our go-to-market goals remains strong. And our ability to help our customers manage through their cloud migration and digital transformation efforts continues to expand. And with that, we will open up the call for questions. Operator, let's begin the Q&A.
spk01: Thank you. We'll now begin the question and answer session. If you have a question, please press star, then one on your touch-tone phone. If you wish to be removed from the queue, please press the pound sign or the hash key. If you're using a speakerphone, you may need to pick up the handset first before pressing the numbers. Once again, if you have a question, please press star then 1 on your touchtone phone. And our first question comes from Sanjay Singh from Morgan Stanley. Your line is open.
spk12: Thank you for taking this question. So congrats on another really, really strong quarter. I had a question for Olivier. It's kind of more of a higher level product-related question coming off the user conference. And I guess the theme of it is that we hear the word observability much more often in 2021 and in 2019. And I think it's starting to refer to different aspects of software in different domains. And I'm wondering from your perspective, you guys obviously have a lot on your plate, plenty of opportunity there. When we're talking about bringing observability into other domains, whether it's the data pipeline or going to potentially in process mining, because you guys do have a log analytics solutions, are those potential opportunities in terms of bringing observability to different domains from the Datadog perspective? Or are you sort of kind of confining it to more of IT?
spk03: Well, you know, we're all about breaking down silos, you know, and bring more use cases and more personnel under the same roof. And we're strong believers that with digital transformation, the application is going to run the business. And so if you understand the application, you can understand everything that happens around the business, which gives you an opportunity to bring many more teams in. So long-term, yes. I mean, all of these are interesting things for us to do, and we see some of our customers implementing some new use cases that we haven't productized yet, on that dog already today. I would say today we're still focused on the products we have brought to market and the ones that are still in beta and we're taking it step by step. But yes, there's much more we can do and want to do.
spk12: Understood. And then sort of talking about some of the usage and cohort behaviors that we've seen over the last several quarters. Coming off the slowdown that we saw at the end of last summer, I think the theme has been is that, you know, the usage trends and the expansion trends have sort of been reverting to normal and getting back to even higher than the pre-pandemic, you know, sort of in line with the sort of pre-pandemic levels. As we stand in sort of going into the end of the year, how have those cohorts sort of changed? Is it just sort of continuing sort of usage or are you seeing difference in longer term contracts? In what sense or what commonalities are you seeing across these cohorts that are different than just sort of their recovery off the end of last year?
spk03: You know, there's actually not many differences between what we see in the most recent cohorts and the previous cohorts. The two main trends that we see that are underpinning the The success you've seen in the past two quarters are, as you identified earlier, the fact that the pace of cloud migration and digital transformation has resumed to where it was. That's the first ingredient. The second ingredient is that our newer products are reaching scale and are being successful and are basically propping up our growth as we solve a larger and larger problem for our customers. So the combination of those two things really is what drives the success you've seen.
spk17: And we continue to have our usage increase be about two-thirds usage of products the client had already and about one-third adoption of new products. That's been pretty consistent over time. So we continue to see similar types of adoption paths.
spk12: Makes total sense and very helpful, David, in terms of shedding some light on the split between those two vectors. Thank you very much, and congrats on the strong Q3s. Thanks.
spk01: And our next question comes from Ramu Lanchitao from Barclays. Your line is open.
spk09: Hey, thanks. Congrats from me as well. Olivier, you mentioned some of the large renewals you saw this quarter, and obviously you would think they're kind of heavy users of Datadogs. Can you just describe how much of their estate is actually getting monitored by you, i.e., how much have you penetrated them, and what kind of differentiates those customers from guys that are kind of smaller on your platform? So is that just a maturity thing, or what are the drivers here that we need to think about?
spk03: I think it depends a little bit on the customers, obviously, but for some of the customers we've mentioned, it's very clear that they're standardizing on Datadog. So I mentioned a very large five-year deal, which is still somewhat atypical for us. But what this shows is that this is a customer that is far enough in their cloud transformation that they know where they're going. They're standardizing on us. And they plan over those five years to basically bring substantially everything they have into the cloud and in Datadog. So that's what's behind it. Again, right now we only see that from those of our large customers that are far enough in their cloud migration, and many of our large enterprise customers have started this cloud migration more recently. But we think it is representative of what's going to happen at a larger scale a few years from now.
spk09: Yeah, and then one for David. If I look at the billing's growth, you pointed out that you were at slightly better duration this year than last year. Do you think you would be able to quantify that a little bit? Is that like a 20-point swing, a 10-point swing, like some material, some materiality, but not too much? Like, could you help us there?
spk17: What we said in billing duration was we had generally been in sort of the seven months plus or minus, then we had had some contraction when in COVID last year down into the sixes, and now we're you know, back up into that same range on billings duration that we had before in sort of the seven to eight months. The same thing happened in contract duration, although the contract duration, we said, was complemented by some multi-year contracts, which expanded the RPO in this quarter and may be a bit unique in terms of the number of multi-years that happened this quarter.
spk09: Okay, perfect. Congrats. Well done. Thanks.
spk01: And our next question comes from Cass Rangan from Goldman Sachs. Your line is open.
spk02: Hi, this is Nikolai Belioff sitting in Pukash. The question we have for you is, number one, can you please stack rank for us the factors that have been contributing to revenue re-acceleration? You talked about all the various pieces of the puzzle here, but is there any way to stack rank them in terms of most influential versus least influential? What drove the revenue acceleration here?
spk03: The two main factors really are the resumption of cloud migration to the speed it had before the pandemic. That's number one. And this one we don't fully control. I mean, that's something that is highly dependent on the business environment around us. The second factor is the success of our new products and the fact that we're, we mentioned on the call, our APM and Log products together reach more than 500 million in ARR. So not only are they growing very fast, like they say in HyperGrowth, but also they contribute quite a bit to the revenue of the company. And we have more products coming up after that that are also growing very fast. So this is the second factor. The third factor is that, you know, on the back of that, like with all the demand environment being there and with us solving a larger and larger problem, we successfully scaled the go-to-market teams so we can actually go after this opportunity. So combine all the three, that's who you get the direct generation of growth.
spk02: Thank you. Thank you. And as a follow-up, Can you please comment on the hyperscalers to what extent they've been contributing to growth? You signed a deeper relationship with Azure last year, GCP as well, and others. How important those partnerships have been coming to the go-to-market motion for you? Thank you. Thank you for taking our question.
spk03: We see that in a number of ideas. I would say there's no drastic change from what we've seen before. It's a continuation of what we've done with the hyperscalers before. I think in some areas we're a little bit more deliberate now in terms of the partnerships we put in place and I think they're a little bit more defined than they used to be before maybe in some cases. But I would say they're not, like these partnerships don't have any specific capacity, set capacity attached to them on our end. They're not part of our models for growth going forward. They're all upside from where we are. So we keep investing in those partnerships. We think they're a part of what we do. but they're not the main way we go to market. Got it. Thanks so much.
spk01: And our next question comes from Sterling Audie from J.P. Morgan.
spk07: Yeah, thanks. Hi, guys. I'm curious, in terms of your existing customer growth that you saw in the quarter, can you characterize how much of that growth is just coming from their growth and expansion in the number of cloud hosts versus adopting more data dog products?
spk17: Yeah, I think we said that similar to previous quarters, about two-thirds of our growth, and that's comparing the size of the customer today versus the previous year, has come from expansion of their use of products that they had already bought. And about one-third has come from their adoption of the new products. And that's been pretty consistent over time. So that's how that splits.
spk03: You know, as a back of the university, you know roughly how the cloud providers are growing, and you see how we're growing compared to them, so it gives you an idea, basically, of the lift we're getting from additional sales capacity and additional coverage, but also the growth of our product suite.
spk07: Understood. And then one quick one on sales. Can you characterize where you are on sales capacity and your efforts to continue to hire to fuel the growth?
spk03: Well, so we're doing – we have more capacity than last quarter and much less than next quarter. So we're still investing heavily. We're growing those teams. And we're also investing not only in the hiring and the retention, but also in all of the enablement and training and the career passing so we can make the most of our go-to-market team. So there's no big change there from previous quarters where we keep investing.
spk07: Got it.
spk03: Thank you.
spk01: And the next question comes from Brad Reback from Cecil. Your line is open.
spk08: Great. Thanks very much. Ali, on that massive financial services deal that you signed in the quarter, how much influence did newer on-prem products like networking and pipelines have on the decision there, or is that potential longer-term upside even with that large client?
spk03: With that specific client, without getting into too much detail, not much, because it's a client that is, I would say, a bit further along in their cloud migration, and they're moving a lot of their workloads into cloud environments in the end. For some other of our customers that we're not mentioning on this call, this is a big deal, and this is something that they're spending quite a bit of time on with us right now. you probably will hear about it in further calls, I would say.
spk08: That's great. Thanks very much.
spk01: And the next question comes from Tyler Radke from Citi. Your line is open. Tyler, if you're on mute, could you unmute your phone?
spk16: Hi there. Can you hear me now?
spk01: Yes.
spk16: Sorry about that. Wanted to talk about the strength that you saw on some of the larger lands, and I think you called out a number of seven-figure lands. I'm curious, do you think at a high level this is mainly driven by specific go-to-market investments? I know you've obviously been growing the sales force, including the enterprise, or is this simply just the product set at a maturity point where you're just kind of seeing this demand more organically.
spk03: It's a bit of everything, right? So obviously the product strength is what we rest on so that it solves the customer problem really well. And it's very easy to adopt and low friction, so that's not new. That's what we've built the company the whole time and it's still there. But also with a product that is growing very fast at customer's As you grow your go-to-market teams, you have to be deliberate about the way you organize these go-to-market teams so that you don't just stop at the customers you have today that already drive a lot of growth. You also go out of your way to acquire new ones. And so we're also always tweaking the way we run the go-to-market teams to make sure that we focus the teams and reward the teams for landing new customers. So yes, we keep tweaking that all the time to make sure that we don't become victims of the success of our product when it comes to organically growing within customers.
spk16: Yeah, thanks. And just to follow up on that, I'm curious, obviously at Dash you talked about a lot of security products. To what extent is the product roadmap around application security really influencing these larger deals? And is that an important consideration with these customers making these commitments, just kind of where they see your product roadmap going?
spk03: It starts coming up in conversations more and more, but it's still early for the convergence of DevOps and security. So when you talk about five-year strategic alignment with customers, security is a part of the conversation. But for most of our customers today, it's still a second step. They start with observability. They start with the cloud. They start with what we have today. And then they want to actually bring security under the same roof as the as the observability data. Thank you.
spk01: And our next question comes from Matt Hedberg from RBC.
spk06: Yeah, thanks. This is actually Matt Swanson. I'm from Matt Hedberg. I'll add my congratulations on the quarter as well as the new acquisition in OSCODE. Could you go a little bit more into the technology there, and specifically kind of what you're adding that's differentiated from your automated incident management product? Because I know you said you could do debugging and production. Is it just part of the actual beginning stages of the DevOps lifecycle? Or is that maybe could get merged into that product?
spk03: Yeah, so it's actually where it stands in the stack is it It's live debugging, meaning that the same way you can use a debugger on your laptop and place a breakpoint and see what the code is doing and what the variables in the code are and things like that, this is technology that lets you do that in production environments. So you can, in your IDE, you can place a breakpoint in the code, and the code in production is actually going to tell you what's going on in the code at that moment at that time. You don't have to update the code. You don't have to ship software, you know, So it's something that developers are used to doing in development environments, and this is technology that lets you do that in production as well. So it's very interesting to us. It's also something that corresponds to some work we've been doing internally. So there's three things that are interesting to us about the host code acquisition. One is the live debugging technology, which is very interesting. Second is it's a group that specializes on .NET, which is a capability that is very interesting to many of our large enterprise customers and is often underserved by newer, I would say, newer innovations in the market. And then the third thing that's interesting to us is that this is going to be our first engineering team in Israel. And we do intend to grow that team and invest quite a bit.
spk06: That's really helpful. One other thing, I guess, thinking more from a higher level, when we think about DevSecOps, I feel like it's a term that we're hearing more and more from more companies. So, I mean, kind of core to establishing, breaking down those silos is going to be consolidating spend down to certain vendors. Is there a way you guys think about kind of the gravity of those budgets between the three sections. Is there one area that you need to be at the core of? Do you think developers have the most power? Security has the most power? I'm just trying to think as more and more companies try to build across those three areas. What do you see as deciding who wins that consolidation?
spk03: Well, I think there are three things that are very massive. One is there's many more developers than any other role. So they have power by virtue of being the most populous and the largest salary mass and everything else. So there's quite a bit of yield in serving developers. The second thing that is massive is the amount of friction for instrumenting applications. And the third thing that is massive is the data volumes in terms of logs. And I think we have a strong advantage on all three compared to pure play. security vendors for that space.
spk06: Fantastic. Thank you.
spk01: And our next question, Council Brent Phil from Jefferies. Your line is open.
spk13: David, the numbers are obviously all accelerating. I guess kind of underpinning the numbers, is there anything new you would call it that was striking to you that you haven't seen? Is there... Is there any common themes that maybe we can't see in the numbers that also account to the strength and what you're seeing in the overall results this quarter?
spk17: I think it's the combination of a number of things at the same time. Strong lands over a number of quarters, which then began to use the product and accelerate. Acceleration of budgets around cloud migration, which caused the usage to increase and continue to be strong. and cross-sell of other products as our product suite gets adopted. And the success there, more of the products, as we showed, are getting adopted by the clients. So the combination of all of those at the same time and strength geographically across all the regions caused the acceleration from last year's post-COVID type of results.
spk13: And maybe for Olivier, just as it relates to cloud migrations, one of the themes we continue to hear about is a dual cloud strategy or even multi-cloud strategy. Are you seeing that starting to help your business or is that still yet to come?
spk03: We definitely see it. Customers are very clear on the fact that they're going to be multi-cloud. They often start multi-cloud even though initially they're going to have more weight in one cloud than another. So it's frequent for customers when they start their cloud migration to pick two of the major clouds to have maybe 95% of their volume in one and 5% in the other. But their goal is always to be able to, further down the road, choose whether they make further investment in one or the other or even on a third on-prem option that would be a private cloud. So this is a plan that we hear more and more from pretty much all of our customers. And we see that as we see our customers getting further along, like some of the ones we've mentioned in the call today, we definitely see them making multi-cloud decisions there.
spk13: Thank you.
spk01: And our next question comes from Michael Curtis from KeyBank. Your line is open.
spk10: Hey, guys. I just want to ask two overlapping questions about the sales force. On the one hand, and I think Tom may have talked about this a bit at Dash, but how are you addressing with a single primary sales force the different buying centers and buyers between security, developer, and business users? And also, how is the sales force evolving from reps that probably really sold essentially one product and now have to sell so many more products? That's frequently a tough time for transition in a sales force.
spk03: Yeah, so today we're still not specializing in Salesforce. We've discussed it a little bit in Pascal. We think with security we might have to do a little bit of specialization. We're testing a few things, but we haven't felt the need to do anything drastic just yet. For the rest of our products, today it works quite well to have the same Salesforce carry the various products. And a lot of that has to do with the fact that the adoption of those products tends to be frictionless. And so we don't need to land all the products at once. We're going to land a few. And then we need to nudge our customers a little bit to start adopting more of them over time as they get more and more value from Datadog. But the lift there is not as heavy as if we had to come back and do a big bank sale every single time. So today, no specialization yet. I think some of it is likely to happen over time. In all likelihood with security, but we haven't done anything yet there.
spk10: And as I said, do you find that the sales force that's been with you selling, I mean, your product is always diverse, but was essentially an observability product more in a traditional monitoring sense. Is that same sales force adapting to this much wider portfolio, or are you starting to see a turnover in that sales force to accommodate that?
spk03: Yes, the sales force is adapting. I think mostly what we're working on is the structures behind the scene to target the sales force and to enable the sales force so they know basically who to talk to about what product when. And it's actually one of the things that Adam Blitzer has been working on, bringing to us a bit of his experience with similar problems at his previous company.
spk10: Thanks, Olivier.
spk01: And our next question from Camille from William Blair. The line is open.
spk04: Hey, thanks for taking my question and congrats on the amazing quarter. It's great to hear about the record deal and the record ARR ads across the platform. As your largest customers scale and standardize on Datadog, can you talk about how conversations have changed around pricing? Are there any particular modules where maybe you're seeing relatively higher levels of pushback on costs and especially given the rapid growth in data and the pricing changes made by some of your competitors over the past two years?
spk03: Well, I mean, usually the module for which there's the most pushback is the one that happens to be the biggest item for that customer. Overall, there's one thing that you've currently identified, which is data volumes are just going to explode much faster than customers' revenues are going to go up. And so we need to be able to differentiate from a technical perspective to solve these problems in a different way for customers or to give them more control so they can target what data they need to keep. A number of the things we've announced at Dash last week actually were meant to help with that. So I've talked about observability pipelines is one of them. The live archives for logs is another one of them. and there's going to be more of a time to address that. So we didn't make any pricing changes, but we are innovating from a product perspective to have new ways of solving these problems and to give more control to our customers.
spk04: It makes a lot of sense. And following up on the product innovation, your R&D expense is up more than 80% year-to-date, well above the 2020 levels of growth. It's great to see the fruits of these investments with the numerous announcements of Datalog Dash, but can you give us more detail around the decision to accelerate the level of R&D spend over the past year? And has anything changed about the broader opportunity versus pre-pandemic to drive this elevated level of spend? And how should we think about the target cadence of future product introductions? I know there's a lot there, but thank you.
spk03: Well, we're growing as fast as we can on the engineering side. it so happens that we could sustain a very high growth on the recruiting and retention side. And we're very confident that our platform lends itself to solving bigger problems, more problems, and to making those products successful, so we're scaling them as fast as we can. It's important to go fast when scaling those teams because there's quite a bit of a lead time between the time when you hire engineers and the time when you to get new products on the other end. I've mentioned in other calls, maybe hiring now is a good predictor of output two years from now on the engineering side. So we should get started. That's why we're doing it.
spk04: That's great. Congrats again. Thank you. Thank you.
spk01: And our next question comes from Yoon Kim from Loop Capital Markets. Your line is open.
spk14: Great, thank you. Congrats on a solid quarter as well from me. But Ali, you're already bigger than all your near-term or nearest competitors, growing faster than all of them by a couple of magnitudes. You talked about enterprise standardization trend that led to your largest deal in the company's history. So are you seeing more and more of that enterprise standardization trend with large organizations and as a result, Are you seeing more and more displacement deals out there rather than just simply selling into large greenfield opportunities?
spk03: I would say the bulk of the standardization still has to come, right? And it depends on the maturity of our customers' migration into the cloud more than the adoption of our product, I would say. but we definitely think that it's something that's going to play a big role in the years to come. When that happens, when standardization happens, there is typically some displacement because what was used on the legacy side or on the other side of the shop is going to be left behind and we're going to replace that. And that's part of the rationalization that takes place. But again, today it's still a small part of what we do. The bulk of our business is still net new cloud environment, a lot of growth in this cloud environment, with the occasional replacement of unsuccessful deployments of previous tools.
spk14: So just for your existing customers, are you seeing many of your customers having mixed vendors of the observability product? Like, for instance, they have your product along with some of the other parts of the organization may have some of your competitors' products as well. So it's just matter of time before the customer needs to stand a right on one platform?
spk03: Yeah, so there's a, what we see is anytime we land into a large enterprise, for example, and we're going to start in the cloud environment, their on-prem environments are going to have a collection of other things. They're going to have older infrastructure monitors like the BMCs and Tivoli's of the world. They're going to have older APMs. They're going to have You know, Splunk on Elastic, somewhere on-prem as well. It's a given. But we're not going to display that from day one. We're going to be the solution. They're going to be in cloud environments. And we're going to display those products as the customers reach critical mass in the cloud and they start standardizing. So we think, from what we see, the customers that are doing that today are the ones who are far along in their cloud migration and started that one a few years ago. So we think this is going to play a big role in the years to come.
spk14: Thank you. And David, just a quick question on cash flow dynamics. Obviously, your contract length is increasing. You're doing more and more large number of deals. Do you expect the cash flow to be more or less, see more greater technology maybe weighted towards more second half of the year going forward?
spk17: No, I think we said in the script that even though we've had some more multi-years, there's still annual billing at most. We don't go for financing the company through collecting advance, so there really is very little, as we talked about, long-term change in the billing dynamics. In terms of cash flow, we tend to see a little bit of seasonality at the end of the year when we go through our end-of-the-year sales cycle and then collect in the first quarter. But I wouldn't see too much change in the cash flow dynamics from either the longer duration of contracts or seasonality.
spk14: Okay, great.
spk17: Thank you so much.
spk01: And our next question comes from Greg Moskowitz from Mizuho. Your line is open.
spk15: Okay, thank you. Olivier, just to follow up on the security go-to-market, your security monitoring product has now been GA for a while, whereas some of the other components of your cloud security platform are much newer. But what I'm wondering is, how would you assess the readiness of your sales force and your channel to sell security to your install base today?
spk03: Today, it's still a product that is being adopted by customers when they're already that are customers that we really land with it first. And that's by design, right? As we keep developing it and as we keep making it applicable to a broader set of customers. We are starting though, we're getting to the point where soon we'll have the full V1 of our cloud security platform. I think for that we're still missing the general availability of the application security component. Once we have that, I think we... we look into accelerating the go-to-market side a little bit and maybe doing some of the specialization we've been discussing earlier in this call. But we haven't done that yet.
spk15: Okay, perfect. Thank you.
spk01: And the next question comes from Cash Rangan from Goldman Sachs.
spk05: I suppose it's a two-for-one deal today. Thank you so much for seeing me along with my colleague here. As you look at calendar 22, you've had a slew of new products that you've added to the portfolio, including some of the demos that you aptly and ably demonstrated to us last week, I believe. Any changes, enhancements, or tweaks to go to market as you look at 2022? And also, as you look to clearly signing these five-year contracts and mega contracts or a change in the way customers look at Datadog. I'm curious if you're emboldened to pursue a specific enterprise sales channel and having a separate go-to-market effort that is pinpointedly in pursuit of mega deals. Thank you so much. Just like our friends at Salesforce started doing some five, six years back or so, and it was definitely fruitful. I'm wondering if you see the same kind of opportunity.
spk03: Yeah, so we do... So first of all, I mean, yes, customers see us differently over time. I mean, we are definitely becoming one of the platforms that they are going to standardize big parts of their business around, and that's definitely a different relationship with them than just something some people on their team are using. So that's a change we see, and we see across a large number of our customers. In terms of pursuing the larger deal, we do have different ways of structuring our teams internally so that we have folks that are going after new logos that might be smaller, folks that are going after growth of existing customers, folks that are going after the growth of the very biggest customers. And we have some segmentation internally on that, and we'll have more and more segmentation as we grow, as we need to focus a little bit everyone. But we're still not looking for those very large deals. We do them today when our customers want them, when they need for their own planning purposes, and when they want to commit their own organizations, we'll do those deals for them. but this is not something that we actively seek. Our products, and we've seen throughout the years that our product is very sticky and that our product grows very well within our customers, so there's no point on our end in pushing for very large, very long-term deals.
spk05: Wonderful. Thank you, Olivier. Congratulations.
spk03: And I think on these good words, I think we'll close the call. So I want to thank you all for this presentation for sticking with us through the call. We're all very happy with the performance this quarter, which is all thanks to the team at Datadog and Datadogs worldwide and their hard work. So I want to congratulate again everyone and thank everyone for a job very, very well done. And we'll see you all next quarter. Thank you.
spk01: Thank you, ladies and gentlemen. This concludes today's conference. Thank you for participating. You can now
Disclaimer