Ladies and gentlemen, thank you for joining us and welcome to JFrog's second quarter 2024 financial results conference call. I'll now hand the conference over to Jeffrey Schreiner, VP Investor Relations. Jeffrey, please go ahead. Good afternoon, and thank you for joining us as we review JFrog's second quarter 2024 financial results, which were announced following market close today via a press release. Leading the call today will be JFrog's CEO and co-founder, Shlomi Ben Haim, and Ed Grabscheid, JFrog's CFO. During this call, we may 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 and including our outlook for Q3 and the full year of 2024. 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. You are cautioned not to place undue reliance on these forward-looking statements, which reflect our views only as of today and not as of any subsequent date. Please keep in mind that we are not obligating ourselves to revise or publicly release the results of any revision to these forward-looking statements in light of new information or future events. These statements are subject to a variety of risks and uncertainties that could cause actual results to differ materially from expectations. For a discussion of material risks and other important factors that could affect our results, please refer to our Form 10-K for the year ended December 31, 2023, which is available on the Investor Relations section of our website and the earnings press release issued earlier today. Additional information will be made available in our Form 10-Q for the quarter ended June 30, 2024, and other filings and reports that we may file from time to time with the SEC. Additionally, non-GAAP financial measures will be discussed on this conference call. These non-GAAP financial measures, which are used as a measure of JFrog's performance, should be considered in addition to, and not as a substitute for, or in isolation from GAAP measures. Please refer to the tables in our earnings release for a reconciliation of those measures to their most directly comparable GAAP financial measures. A replay of this call will be available on the JFrog Investor Relations website for a limited time. With that, I'd like to turn the call over to JFrog CEO, Shlomi Ben Haim. Shlomi? Thank you, Jeff. Good afternoon to you all, and thank you for joining our call. Q2 was a productive quarter for JFrog, demonstrating solid results in our revenue, gross margin, free cash flow, and EPS. We extended JFrog on all fronts, evolving into a provider of a comprehensive software supply chain platform fortified by enhanced security capabilities that are being adopted by the world's leading organizations. Our total revenue for the quarter was $103 million, up 22% year-over-year. We are successfully transitioning to strategic outbound enterprise sales and increasing our average selling price, all while achieving an impressive business efficiency. Our performance highlights the sustainability of our business. As we expand our platform infused with innovation aligned with current and future market demands, JFrog plays a crucial role in organization's software supply chain flow, encompassing DevOps, DevSecOps, and now MLOps. During the second quarter, JFrog's cloud revenue reached $39.3 million, representing a 42% year-over-year growth. Ed will further discuss our cloud business and dynamics on today's call. Throughout the past year, we added 115 net new logos to the greater than $100,000 ARR category. In Q2, JFrog's customers in this category grew to 928, up from 813 in the previous year. The number of customers with an ARR exceeding $1 million increased by two during the quarter, reaching a total of 42, which represents 75% year-over-year exceptional growth. These enterprise growth numbers are the results of our successful shift from a purely inbound inside sales model to a hybrid approach that combines enterprise sales with bottom-up inbound sales. The rewards of this shift to enterprise sales are evident, with an increase in ASPs for both new and existing customers. However, high TCV deal cycles are taking longer than anticipated due to budget constraints. This reality will be addressed as we look into the second half of 2024. Our 97% exceptional gross retention rate indicates that the vast majority of our customers consistently choose JFrog on every renewal. Given the innovation added to our platform with new capabilities and a significant portion of our customer base that has yet to upgrade to the full platform, we believe we can deliver durable expansion in the future. Based on first-hand results, the strict budget environment, rigid procurement processes, longer sales cycles, and projects being delayed, we anticipate slower growth in customer expansion for the time being. With that, let me address ongoing adoption of the JFrog Platform by some of the world's most influential companies. A little over three years ago, we embarked on the journey of creating a software supply chain platform centered around Artifactory, which has become the gold standard for software packages, single source of truth, and database of DevOps. We developed a holistic solution now coupled with security capabilities that cater to various enterprise personas and expand our offerings and total addressable market. For example, one of the world's Big Four accounting firms recently chose JFrog as a strategic partner to scale, secure, and deliver the software components. After experiencing multiple security breaches in the past, they noted their prior security solution couldn't scale and did not holistically protect their software supply chain. Working with our technical team, they were able to architect and begin execution on a security-driven deal to elevate their security posture, migrate to the cloud with JFrog Advanced Security and JFrog Curation while displacing a competitive solution. In another new logo deal, one of the United Kingdom's top insurance service organizations, Admiral, migrated to the JFrog Platform away from Sonatype Nexus suite of tools. As they sought to move to a hybrid infrastructure and consolidate their security offerings, they discovered JFrog's comprehensive security suite was a match for their needs: a robust single system of records for binary management. Admiral's head of capabilities for DevOps and applications, Kevin Foley, noted, "With JFrog, we're embracing a strategic partner that allows us to modernize to a cloud-based, scalable solution. JFrog is aligned with our mission to modernize and enhance security across our development processes with its comprehensive cloud-based DevSecOps platform. It empowers us with end-to-end security capabilities crucial for maintaining the integrity and security of our software products." As more companies discover the power of the JFrog Platform with Artifactory at its core, infused by security and machine learning solutions, we anticipate driving unmatched value for large-scale enterprises. I would now like to address one of our strategic partnerships. JFrog continues to revolutionize the domains of DevOps, DevSecOps, and MLOps. In Q2, we completed and publicly announced the first phase of a strategic partnership with GitHub, the leader in source code management and AI-assisted development technologies. This collaboration was driven by strong demand from our joint customers, including AT&T, Fidelity, Ansys, and Morgan Stanley, to name a few, who desired a seamless native workflow between these two best-of-breed platforms: GitHub for source code management and JFrog for binary management. We were proud to co-engineer this painsolving solution with GitHub and excited to launch the first phase of a deep integration between our platforms that begins to marry the world of code and binaries in a single platform experience. Once the integration is completed, we expect to see contributions to the business that will drive JFrog Advanced Security goals as a result of the tight integration with GitHub Advanced Security. Additionally, we anticipate higher shift-left exposure to the SMB and AI market due to GitHub's Developer Relations and Copilot solutions. John Nuttle, Director of Technology for AT&T, noted, "Beyond DevOps and DevSecOps practices, the future will require advanced interactions with AI tools. Chatting with GitHub Copilot to select the right and secure software package based on the extensive metadata stored in JFrog Catalog can be a game changer. This integration will significantly enhance the efficiency of Copilot users across the software supply chain, binary-focused, and code environments. The partnership offers the best of both worlds. At our upcoming user conference, swampUP, we are excited to welcome GitHub to our keynote stage to unveil the next phase of integrations, including Copilot, AI, and Advanced Security capabilities. Finally, the expansion of our platform goes beyond DevOps and DevSecOps. I'm excited to share more about our acquisition of Qwak AI and our expansion into the world of MLOps and AI-powered software. In late June, we announced that we would be acquiring the MLOps platform company, Qwak AI, in a deal that was finalized in early Q3. With this acquisition, JFrog is the first company to offer a comprehensive end-to-end EveryO ps solution for developing, securing, and delivering both traditional and AI-powered applications in one platform. With Qwak's platform to build, train, and experiment with the model, JFrog Artifactory as the model registry of choice, and with JFrog Xray and Advanced Security protecting the machine learning lifecycle into production, we believe the JFrog Platform is uniquely positioned to bring data scientists and machine learning engineers the same level of agility, reliability, and efficiency as developers and DevOps engineers already enjoy. Our teams look forward to building an integrated solution to offer our users comprehensive coverage across DevOps and MLOps lifecycles. To the Qwak team, welcome to the Swamp. We are now one, united not only as a team, but also as the creators of the first platform to unify the world of developers, machine learning engineers, and data scientists. Before we dive deeply into the financials, I want to take a moment to welcome our newest board member, Luis Visoso. Luis's experience as the CFO of Unity, AWS, and Palo Alto Networks, along with his role as an independent board director at companies like Splunk, will be invaluable to the growth and scale of JFrog. I look forward to working with him and having him on board. With that, I'll turn the call over to our CFO, Ed Grabscheid, who will provide an in-depth recap of Q2 financial results and update you on our outlook for both Q3 and full fiscal year 2024. Ed? Thank you, Shlomi, and good afternoon, everyone. During the second quarter of 2024, total revenues were $103 million, up 22% year-over-year. Our second quarter results were within range of our guidance across all measures. Customers continue to highlight the need to consolidate their software supply chain tools towards a best-of-breed platform solution, such as the JFrog Platform plus security, and now MLOps with the recent acquisition of Qwak AI. As noted by Shlomi, cloud revenues in the quarter equaled $39.3 million, up 42% year-over-year, representing 38% of total revenues versus 33% in the prior year. Self-managed revenues or on-prem were $63.8 million, up 13% year-over-year during the second quarter. We anticipate self-managed revenue growth trends to slightly decline in 2024 compared to 2023, as customers waiting to migrate to the cloud have paused investment in their on-prem deployments. Net dollar retention for the four trailing quarters was 118%, in line with our guidance. Our gross retention rate remained at 97%. In Q2, 50% of total revenue came from Enterprise Plus subscriptions, up from 45% in the prior year. Revenue contribution from Enterprise Plus subscriptions grew 35% year-over-year. Now, I'll review the income statement in more detail. Gross profit in the quarter was $86.9 million, representing a gross margin of 84.4% compared to 83.6% in the year-ago period. The increase in gross margin relative to the year-ago period is due to the elimination of outsourced costs derived from synergies related to the acquisition of Vdoo and ongoing cost discipline efforts. We reiterate expectations for annual targets remaining between 83% and 84% in the near future, then trending towards the low 80s, aligned with our long-term model and cloud growth. Operating expenses for the second quarter were $73.3 million, up $2 million sequentially, equaling 71.1% of revenues, up from $62.2 million or 73.8% of revenues in the year-ago period. We remain focused on expense discipline while absorbing the operating expenses through our acquisition of Qwak and continuing to maintain the proper level of investment in scaling our enterprise sales team, channel partner ecosystem, and strategic R&D spending. Our operating profit in Q2 was $13.6 million or 13.2% operating margin compared to an operating profit of $8.2 million or 9.7% operating margin in the year-ago period, an improvement of 3.5 percentage points. Diluted earnings per share equaled $0.15 based on approximately 115.2 million weighted average diluted shares compared to $0.11 per share in the prior year on 108.1 million weighted average diluted shares. Turning now to the balance sheet and cash flow, we ended the second quarter of 2024 with $591.3 million in cash and short-term investments, up from $579.6 million as of March 31st, 2024. Cash flow from operations was $16.7 million in the quarter. After taking into consideration our CapEx requirements, free cash flow was $16 million or 15.5% free cash flow margin. We remain committed to our free cash flow margin targets provided within our long-term model, implying an estimated midpoint of 28% over the coming years. As of June 30th, 2024, our remaining performance obligation totaled $272 million. Now, I'd like to speak about our outlook and guidance for the third quarter and full year of 2024. For the third quarter, we expect revenues to be in the range of $105 million-$106 million. We forecast non-GAAP income from operations to be in the range of $10 million-$11 million, and non-GAAP net income per share to be in the range of $0.09-$0.11, based on 115 million estimated diluted weighted average shares outstanding. For the full fiscal year 2024, we expect revenue to be in the range of $422 million-$424 million, non-GAAP income from operations to be in the range of $52 million-$54 million, and non-GAAP net income per share to be in the range of $0.54-$0.56, based on 116 million estimated diluted weighted average shares outstanding. Let me provide more context around our guidance. The revised guidance for fiscal year 2024 reflects a more challenging macroeconomic environment entering the third quarter, lower anticipated cloud revenue growth, and changes in customer purchasing habits. We anticipated our cloud revenue to achieve mid-40s year-over-year growth in 2024. However, we experienced customer migrations being postponed during the second quarter, a pronounced slowdown in cloud consumption for our monthly subscribers who have no usage commitments. Coupled with increased macro uncertainty, we now expect cloud revenue growth to slow relative to prior expectations. Given the macro uncertainty, headwinds within our monthly cloud subscribers, and de-risking future enterprise customer migration projects in the second half, we now believe full year 2024 cloud growth will be around 40%. We would note that our revised cloud growth still represents strong execution in a challenging market. We continue to see security becoming a critical driver of larger customer deals and view the JFrog Platform, combined with security, as the industry's choice for enterprise customers looking to manage and secure their software supply chain and consolidate point solutions. We remain optimistic that JFrog Advanced Security and Curation will deliver durable revenue growth in the future. We're stepping into the second half of the year with a solid sales pipeline. However, given longer sales cycle and proof of concept processes, in a challenging purchasing environment, we now anticipate material revenue from our security core will be achieved in 2025. Given the noted changes compared to our prior expectations, we now believe our net dollar retention range for the full year is likely in the mid-teens versus the high teens expectation we had exiting the first quarter of 2024. Finally, the acquisition of Qwak closed in the beginning of July. We do not anticipate any meaningful revenue contribution in the third quarter or for the full year 2024. As we integrate Qwak into JFrog, we will provide further updates regarding our anticipated contribution to growth and profitability. Now, I'll turn the call back to Shlomi for some closing remarks before we take your questions. Thank you, Ed. Last week, we marked 300 days since the war in Israel began. We continue to pray for the safe return of the 115 hostages still held in underground Gaza and for more peaceful days in the region and the world. In the face of these geopolitical and macroeconomic challenges, I'm honored and proud to walk with a team that remains steadfast in pursuing our company's strategic goals and upholding the culture that drives us forward. Qwak, you continue to inspire me daily, and I thank you for the effort, devotion, and commitment to building and growing our company. The world depends on the seamless flow and trusted delivery of rapid software updates, whether through DevOps practices reinforced by holistic software supply chain security capabilities or MLOps powered by machines. The JFrog Platform is engineered to address one of the world's greatest challenges, ensuring software runs efficiently and securely from developers to the edge. We are excited about the future and the limitless possibilities it holds for us. With that, thanks for attending our call, and may the Frog be with you. Operator, we are now open to take questions. Thank you, sir. Everyone, if you would like to ask a question, please press star one on your telephone keypad. We do ask that you limit yourself to one question and one follow-up. We'll take our first question today from Pinjalim Bora, JPMorgan. Oh, great. Thanks for taking the questions. I just wanted to understand a little bit more on what transpired. You had reaffirmed guidance, I think, about five days remaining in the quarter. Did you notice the changes in the sales cycle dynamics, mainly in the month of July? Did it deteriorate towards kind of the end of July? Maybe help us think through that. Hi, Pinjalim. This is Ed. Thank you for your question. We noticed a push-out in the final few days of the quarter and a remarkable change in the macroeconomic environment in the first month of the new quarter. So therefore, we didn't see much during Q2 until the final days of the quarter. We also noticed in that time, strategic deals, significant large strategic deals being pushed out, which indicated to us a change in the purchasing environment. Therefore, we revisited our forecast and de-risked and adjusted our guidance going forward for the full year as well. Yeah, understood. One more question on the cloud revenue guidance now coming down 5 points. Is it possible to understand how much of that is driven by the monthly cloud part and the annual cloud? The monthly subscribers from our cloud for cloud growth is around 2-3 percentage points. If I may remind you, Pinjalim, cloud subscribers have no commitments. So it's a pay-as-you-go, and it's very much aligned with what Ed articulated regarding the macro environment. Up next, we'll take a question from Ryan MacWilliams, please. Hey, guys. Thanks for taking the question. Just on the Microsoft partnership, from what we heard so far, it seems like this is more than just a sales and go-to-market partnership, but also more on the product side. So Shlomi, we'd love to hear what you think this JFrog GitHub partnership means from a product standpoint for the customers, and how do you think about the potential opportunity, the size of this opportunity for JFrog going forward? Yeah, thank you, Ryan, for the question. Obviously, every partnership, especially with the best-of-breed other platforms, when it's driven by customer demand and our biggest customers' joint customer demand, it shows the rapid adoption of both tools and the expectation from the market to have a one-platform experience. So we have high hopes. We released the first phase of this integration a bit more than a month ago, and we are going to complete this phase with the announcement to swampUP next month in Austin, Texas. We're very much excited about it. We like co-engineering with GitHub, and we hear the customers are excited about it, so we have high hopes. I think it's too early to say how it will change the narrative and the adoption, but with everything that happens in our environment, DevOps, DevSecOps environment, this integration around DevOps, security, and AI is what our customers, joint customers, expect. Appreciate the color. And then for Ed, is there a way for us to think about the historical contribution to cloud revenue growth from existing customers moving over from on-prem? And then for the customers that are now delaying their cloud transition, is this something that is put on pause, like slipped from Q2 to 3Q, or is this something that they're going to maybe relook at in a better macro in 2025 and so on? Yeah, thank you for your question. First, for those customers that are migrating from self-hosted to cloud, we see anywhere from 20%-80% in terms of an uplift in the subscription, therefore providing an increase in expansion for those customers. Regarding the timing of that and the push-outs that we saw, we looked at our forward-looking forecast, and we de-risked for any migrations going forward at this point. The next question comes from Sanjit Singh, Morgan Stanley. Yeah, thank you for taking the question. I wanted to go back to where you saw the weakness. So we've talked about migrations and the monthly pay-as-you-go cloud business. In terms of whether it's enterprise, mid-market, versus SMB, or geographic exposures, or even across different industries, were there any particular segments that stood out that drove the incremental weakness, or what you saw towards the end of the quarter going into July was that broad-based? Hi, Sanjit. This is Shlomi. No, it goes across geographies, customer's profile, different demands, whether it's security or DevOps. It's more about budget concerns, and it's more about a rigid procurement environment. This is what we hear from our customers. Understood. And then on sort of the timing of sort of the contribution of Advanced Security, I guess I'd be a little bit surprised why it would push out. I mean, you obviously have the GitHub integration coming online. But I mean, globally, we just had a major outage with the CrowdStrike situation. So it would seem to me that the focus on the software supply chain and how we roll out updates becomes more critical than ever. And I would have expected a potential tailwind to the business from big outages like that in the second half. So any reason behind the push-out of Advanced Security and maybe just the broader business, not seeing more of a benefit post a pretty material global outage that the industry is experiencing? Yes, Sanjit. I can share with you what we hear from our customers and what led us to look again at the expectation. When we entered 2024, we thought about early adoption of our security solution. What happened was that most of our strategic customers started to look at the consolidation of point solutions, which was higher than expected in SaaS perspective. So we are looking at a higher potential, but then again, higher potential also leads to longer proof of concept processes and longer procurement processes. And this is why we want to be a bit more conservative about the security. With regard to GitHub, the security piece is something that will be announced next month, as I mentioned. And then we hope that it will generate even more motivation for consolidations of point solutions to the platform security solution. Koji Ikeda from Bank of America has the next question. Yeah, hey, guys. Thanks for taking my questions here. I wanted to follow up to the first question that was asked in the Q&A and really try and understand a little bit more about the linearity of cloud deals. With the guidance that was given on 6/25, you guys mentioned the demand environment deteriorated in the final few days of the month. Just even coming off the first quarter results, I think one of the big debates on JFrog is understanding how this cloud component is consumed. So is that typically how the buyers are consuming cloud? It comes in big in the final few days of the quarter or the month. Is that the way we should be expecting how the users are buying this product? So the seasonality of purchasing in the quarter will typically see towards the end of the quarter. So the majority of deals are done in the end of the quarter. This is something that is not unique to Q2. We see that every quarter where the majority of that. In terms of what we're seeing around large migration deals, and specifically around what we saw during Q2, was that decisions that we felt were high probability with proof of concepts that were completed, those were pushed. Those were pushed to later periods. We reevaluated, as I mentioned, our forecast. We de-risked these large deals based on a very challenging macro environment, a rigid purchase environment. Therefore, in the second half where we had significant migration deals, those have been removed from our forecast going forward. Okay. And then to follow up on that, with the revised guidance for the full year on the cloud, that does imply somewhere around a mid-30s growth rate in the cloud for the second half. And so it sounds like you've taken out a bunch of the migration assumptions, but is there anything else within that guidance that you're taking into consideration aside from the migrations for that cloud number? Thanks, guys. Sure. In addition to that, because of the macro environment and this rigid purchasing environment, we're not seeing the level of expansion that we expected in the second half. Therefore, the combination of the migrations and expansion on renewals are being factored into the guidance going forward. Koji, if I may add to it, we are looking at the 40% growth over here in the cloud. We are looking at a profitable business here. We have to be conservative and to think about what the market is telling us. And therefore, in a very responsible way, we looked at our pipeline and the big projects that the pipeline introduced and reacted based on what we saw in the first half of the year. We'll go to our next question from Kingsley Crane, Canaccord Genuity. Hi, thanks for taking the question. So I want to return to the cloud guidance that everyone's talking about. It makes sense that you saw some changes and you want to be conservative. The new guidance, I still believe, would imply sequential re-acceleration in the back half. So I just want to get a sense of how de-risked the guidance is here and then what's the risk that this could deteriorate further despite the conservative take we've taken out here. Thanks. Yeah, thank you for the question, Kingsley. So what we know today, we feel comfortable with the number that we're presenting, around 40% year-over-year growth in the cloud, which Shlomi had mentioned, and I mentioned during the call, still represents a very good year-over-year growth in the cloud. 2%-3% of that decline is coming from our monthly customers that do not have commitments with us, and we've stated that in the past. In addition to that, we've taken a very close look at our forecast going forward and de-risked as much as we felt comfortable with de-risking any deals in our pipeline and in the forecast for the second half of 2024. Okay, thank you. That's helpful. And Shlomi, just one for you. It's great to hear about the GitHub partnership and how it can help Copilot users bring the best of both worlds. Just want to think through how it could translate to business impacts. Is this sort of a nice feature for existing users? How much of this can be an on-ramp for GitHub's large user base to explore JFrog? I think, Kingsley, it's relevant to any organization that is using GitHub or JFrog first, and then to any organization that might migrate from Bitbucket or GitLab. So obviously, the potential is very high, mainly because of the fact that it also brings some differentiators that other vendors cannot provide, like enhanced security consolidation with these two platforms, Copilot and JFrog security collaboration. So users can actually chat with Copilot and get binary information. The collaboration with GitHub is based on our customers' feedback. So I don't see how this can go wrong. And also the trend in the market for consolidation, moving from point solutions to best-of-breed platforms. We are very honored and very excited about this partnership. Great to hear. Thank you. The next question comes from Mike Cikos, Needham. Hey, thanks for taking the question, guys. I know my colleagues and I are all a little confused by the 40% growth that we're calling out for cloud. And just to put a finer point on it, I want to think in a sense, does guidance currently contemplate a lift in Q4 for true-ups under these take-or-pay commitments like what we experienced in Q4 of 2023? Does that help explain some of the growth dynamics in the second half of the year we're looking at? Hi, Mike. This is Ed. Yeah, thank you for that question. As we move our customers, cloud customers, from an annual use-it-or-lose-it to a monthly use-it-or-lose-it, we would expect over time that we would have fewer true-ups. Therefore, we don't see as large of a true-up during Q4 of 2024 as we did during 2023. So I wouldn't expect the same level of what we saw during 2023. Okay. But just to be clear, there is an anticipated benefit of some sort that's currently baked into this guide we have today? No, we do not consider that. Oh, there's not. Okay. Okay. Thank you. Thank you for closing the loop on that. And then I did just want to come back to some of the comments there on the weakness or the changes in behavior that were showing up. Since I know Shlomi in the prepared remarks, you had cited the increased ASPs and the higher TCV deals. Can you help us think about for those delayed cycles, is it more prevalent for those larger tickets, or it's really across the board? We're calling out the monthly for the cloud users, but any more granularity as far as these different customer segments would really be helpful. Yeah, thanks, Mike. Yes, it's across the board. Geographies, different customers, different industries, different sectors. And not only that, but also DevOps and security, which leads us to understand that it's more about the procurement habits than the technology demanded the successful proof of concept. What we see, however, this higher TCV requires a longer process. So sales cycles are longer when you deploy more funds in today's environment. If it was under $100,000, maybe it would be easier. But when you consolidate a set of tools around the platform, it leads to a higher TCV. This is the good news, but it takes longer. This is not such a good news. We want to be conservative, and this is why we implement what we see in H1 on the projection of H2. Brad Reback from Stifel has the next question. Great. Thanks very much. Ed, can you remind us what% of the cloud is month-to-month? Yeah, the percentage is approximately 25% of our cloud business monthly. Okay. And I guess just going back at it, last quarter, you were fairly adamant that the mid-40s would be achieved just on your commits. What changed? Yeah, what we saw last quarter was visibility into a pipeline that had significant migration deals. That has been de-risked. In addition to that, the purchasing and rigidness of purchases have certainly changed. The monthly consumption, which again, do not have commitments, we saw a significant decline in those monthly customers. Both of those factors are being taken into consideration going forward. Therefore, we've made that adjustment to our cloud growth. Andrew Sherman from TD Cowen has the next question. Oh, great. Thanks. Following up on Brad's question there, we're all kind of scratching our heads on the same topic, obviously, but just want to be clear that the 40% now has no migrations assumed in it, and it's all committed with no SMB, no usage. So the 40% should be the bottom, if you will. Oh, 40% is yet a very significant goal. So of course, we assume that some migrations will happen, but we de-risk the big strategic migrations, and we are looking at what we've learned from the second quarter, and this is why we adjusted. Okay. And is there something that happened in June industry-wide that may have slowed migrations kind of across the board? You're not the only vendor that's called this out, but what changed abruptly budget-wise or cloud migration-wise in June, do you think? Yeah, well, it's not even June. It's the last week of the quarter, the last few days of the quarter, when we started to see that more of these strategic big projects are being pushed. And yes, you heard it from not only JFrog, you heard it from the market. We saw the same. It's mainly around budget constraints and procurement processes, and this is why we took action based on what we saw in the last few days of the quarter. The next question comes from Miller Jump, Truist Securities. Thank you for taking the question. I guess last quarter, you guys called out digestion in the customer base. I'm just curious, did this quarter have a continuation of that theme as a headwind in addition to the deal cycle changes, or did you see improvement there? Hey, Miller. Thank you for that question. So we did not see anything related to digestion. What we're seeing is customers that are delaying purchasing decisions. We saw that towards the last week of the quarter. We're now starting to see optimization in terms of their spend as they continue to think about this uncertain macro environment, the very rigid purchasing environment that we're faced with. But we didn't see anything related to a digestion. Okay. Thanks. And then I actually might come back to you on this one as well. Ed, just given the cuts of guidance, it looks like now we're in a position where you need to see a re-acceleration to hit the low end of your FY27 revenue targets. Can you just talk about the drivers and more specifically the timing of how you see that playing out from here? Yeah. So first off, we changed our guidance only 1%. So we went from 22% to 21% on our annual guidance. We continue to maintain our focus on execution of the three pillars or the three legs of the stool of our long-term model, which is adoption of full platform, migration to the cloud, and of course, security. So based on those factors and the fact that we have not baked in the potential tailwind that we may get from AI and MLOps, when we think about that in the long-term model with multiple years to go, even though we're faced with a macro environment right now, we still feel very confident in the long-term model and the top-line growth that we presented in that model. The next question comes from Jeff Kvaal, UBS. Hey, everyone. Thank you for taking the question. So the first one would just be maybe more color just on how customer conversations have been. And obviously, your cloud business in general is driven by kind of a project-oriented model. There was, I think, an expectation that in H2, you'd start to see more projects come online as customers got more visibility into their work plans. How have those conversations evolved? Have those changed in any way, or is it still just a lot more focus of elongated sales cycles just from a budget procurement scrutiny perspective? So, customer conversation, if I heard the question right, I'm sorry, it would be tough to hear. Customer conversation, what we hear from our customers is the following. The first thing that everybody points to is consolidations of point solutions into a platform. There are a lot of our on-prem customers that are speaking about future migration to the cloud. Obviously, this is not happening in today's environment. And third, that security is embedded into the solution. So there is no DevOps standalone or security standalone. It comes together. A lot of them are also pointing to the future with what MLOps brings and the fact that they will have to support MLOps with the DevOps practices, so they know that it will be part of those services. Therefore, when we push not only to extend our platform, but also to look at the ecosystem, we chose the partners that we want to go with. This is what we hear on the technology side. What we hear on the procurement and the budget side is that they have to be very strict, very disciplined to their commitments, and also to apply all types of optimization on the cost as long as this situation in the market is going on. Got it. Thank you for that, Colin. One quick one for you, Ed. You made a comment earlier. I want to just be crystal clear on this. You said as we move customers from annual to monthly, we'd expect fewer true-ups. Is that something that you're witnessing? Should we expect that 25% of monthly business to shift up as we edge closer to Q4? No, I think let me clarify the question. I believe the question was when we move customers from self-hosted to cloud, we see an uplift anywhere from 20%-80%. Customers that move from monthly, which do not have commitments to us, to an annual within cloud, we don't see an uplift in those customers immediately, but over time, as budgets allow, we would start to see an improvement in the uplift and expansion of those customers. We'll take the next question from Jason Ader, William Blair. Yeah, thank you. I just wanted to ask whether you guys are very confident that there's no competitive issue here or execution issue. You talked about macro. I think we all get that. But you are moving to this new strategic outbound sales model. That's not simple for an organization. I never had that. So just wanted to know if you've identified any execution issues on top of the macro issues or competitive. Jason, thank you for this question. This is Shlomi. Well, there are a few parameters that we mentioned in the call and need to be kind of taken into consideration. A, we said that we have 97% retention rate of our ARR, which is suggesting that these customers are not moving or installed base is not moving to competitors. The second thing is that I never saw an enterprise customer invest 2, 3 quarters in a proof of concept and at the end telling me that they need a bit more time, but then moving to a competitor. We never saw that happening. In addition to that, when we are looking at our pipeline and we speak with our customers, we don't hear them looking for another solution in the market. Usually, there's always competition, but this is not the narrative that we see in the pipeline. And the last thing is that when you think about the partnership between JFrog and GitHub, think about the CIOs and the CISOs of the market. Who will go and check something else when the two best of breed are coming together to provide you with one platform experience? So it's less about the competitive environment. It's more about the macro environment. I'm certain about that. And this is what we hear from our customers as well. All right. And a quick follow-up on the GitHub partnership. What do you think their main motivation is to do this deal? Do you think it's the Advanced Security capabilities that you had that they can now kind of co-sell with? And then just is that special in any way to their range of partnerships? I mean, do they have partnerships with other security vendors, for example, that would be sort of an alternative for the GitHub reps to recommend? Yeah. Well, I can speak for myself, and I can speak maybe on behalf of my customers of what we've heard from them. First of all, there are a few differentiators in this partnership. A, it's the binary expertise next to the source code expertise. That's kind of the long run coming together of binary and source code. The second thing is security. Both JFrog and GitHub bring Advanced Security capabilities that protect your software supply chain. And we are complementary to each other. We coexist one next to the other. They protect your source code. We protect your binaries. And it goes together, and it's very appealing to the customers, especially when they can see it on one platform with one view. The third thing, and this is a very fast-growing adoption, Copilot and AI-driven application is something that requires more insights from the metadata and the binaries and the collaboration between JFrog and GitHub. Introducing a chat of a developer with Copilot getting the information from Artifactory and Xray is very appealing for our customers as well. As mentioned in the quote, our customers are driven by consolidation and the differentiations that can come from this collaboration. We'll take the next question from Yi Fu Lee, Cantor Fitzgerald. Thank you for taking my question, gentlemen. I guess my question is more to reconcile. We've seen great hyperscale growth rates this quarter above average. And in terms of, I appreciate the comment on the migration slowdown. I guess, Shlomi and Ed, what are the dashboards that you guys look at on a daily basis, monthly basis, weekly basis to get you more comfortable that the animal spirits of the CIOs, CTOs will continue with that migration going forward? We just want to get more clarity on that. Hi, this is Ed. Yeah, so we're always looking at the pipeline. This is an indication of how we believe the forward-looking will play out and through those discussions that we have with our customers as well as with the internal sales team. In addition to that, we also look at behaviors in the market. Based on what we see now and the change in the macro environment, the change in the purchasing environment, and what we see in terms of the de-risk of those forecasts, this is how we make the decision, and this is why we opted to be conservative in our approach and lower our cloud guidance. If I may add to it, when Ed is saying we're looking at our pipeline, it's not just a general number. We are looking at different stages. What gave us the confidence to your question is looking at our pipeline after the technology win. This is also what brought us to the conclusion that we had to de-risk those big projects. Looking at late stage after the tech win before budget discussions, this is the main dashboard that we are looking at. Okay. Thanks, Shlomi. Then my follow-up is more of a if I step out a little bit. I think last month, there were news of a chatter of direct competitor GitLab on some M&A activities, I should say. Your thoughts on the consolidation in this space? Any commentary on that? So if the question is about the landscape and the competition with the hyperscale, we see co-selling, co-marketing potential there. With GitLab specifically, well, we don't hear from our customers that they're migrating to GitLab package management solution, no security solution. We don't see any MLOps capabilities with GitLab. Under 30% of our customers are using GitLab. I guess that this partnership with GitHub is aligning us more with what our customers prefer to see in the future when they speak about consolidation. But we don't see a lot of GitLab competition in our pipeline. We'll take the next question today from Rob Owens, Piper Sandler. Great. Thank you for taking my question. And I guess just to shift a little bit, we'd like to ask on the Qwak acquisition. From a clarification standpoint, you said no revenue in the expectations moving forward. Guessing there is that expense in the expectations. So can you quantify that, number one, and how should we think about integration? Is this relatively simple from a plug-and-play standpoint, or will this require increased investment over some period of time that we should contemplate margins from that perspective? Thank you. Yeah. Hi, this is Ed. Yeah, so we're still in the process. We closed the deal the first week of July, and we're still in the process of integrating them. There is expense that we're absorbing. As you know, JFrog has proven history of being very diligent in terms of the way that we manage our expenses, and we'll continue to be focused on profitability. The integration, which, as we complete that integration, we will, of course, balance the operational efficiency and the ongoing investment. This will be very much aligned with our expectations from a long-term model as well. If I may answer it, Rob, on the integration and the solution to the market, it's not a matter of MLOps yes or no. It will be adopted. It will be. And as you know, and as we announced in the previous quarters, we integrated with MLflow, we integrated with AWS SageMaker, and with Qwak. So this is based not only on the trends in the market of adopting AI technologies, but also the fact that it's a very logical next leap forward for JFrog. Artifactory is already serving as the model registry of choice. Xray is already scanning your models. So improving or expanding our platform was a mandatory next step forward for JFrog. And as Ed mentioned, once the integration will be completed, we will also share our expectations with you. We'll go next to Nick Altmann, Scotiabank. Hey. Awesome. Thanks, guys. I wanted to follow up on Advanced Security and Curation. Maybe just talk about what gives you confidence this is more macro-related or more scrutiny on budgets versus product-market fit, given this is a newer product offering. And then secondly, I think historically we talked about Advanced Security and Curation becoming a material portion of revenue for this year. I guess, how should we think about the timeline now as to when that can be material to revenue or just any sort of goalposts as to what that can contribute this year? Thanks. Yes. Thank you. Thank you for this question. Well, we came into 2024 very humbled with the adoption. We wanted to see our portfolio starting to look at Advanced Security and Curation. What we saw is that they are willing to consider a full consolidation around JFrog Advanced Security and JFrog Curation. We are looking at the pipeline. We are looking at the strategic deals. We are hearing about the proof of concept in the world's leading organizations. This gives me the confidence that it's not only the security solution, but also the movement from point solution and consolidation around one platform. A. B, JFrog Advanced Security is displacing a lot of point solutions, secret detection, infrastructure as code, static analysis, and so on. JFrog Curation has less competition in the market, and it's very innovative based on what we see. It's also appealing not only to the security persona, but also to the DevOps persona. Therefore, we see more interest coming from two directions in the enterprise. We are looking at the pipeline. We are looking at the size of the deals. We are looking at the names of the customers. We also know that they face their own challenges with this macro environment. We have patience, but I will take a big deal with a higher TCV any day over a small deal just to get in somewhere and not to displace my competitors. This is what we see now, and this is why we decided to de-risk this project and the pipeline accordingly. Thank you. Everyone, at this time, there are no further questions. I'd like to hand the conference back to Shlomi for any additional or closing remarks. Thank you very much for joining us today. May the JFrog be with you, and may we have more peaceful days moving forward. Thank you very much. Once again, everyone, that does conclude today's conference. Thank you for your participation. You may now disconnect.