Delighted to have with us Charles Giancarlo, CEO of Everpure, formerly Pure Storage. Formerly Pure Storage. I guess before we get started, I'm just going to read a few statements on behalf of Everpure. Statements made in these discussions which are not statements of historical facts are forward-looking statements based on current expectations. Actual results could differ materially from those projected due to a number of factors, including those referenced in Everpure's most recent SEC filings on Forms 10-Q, 10-K, and 8-K. Thank you very much. Perfect. Anytime. Well, Charlie, thanks a lot for being here. Really appreciate your time. Maybe just even before we get kicked off, start off with all the questions, you folks reported earnings a couple of weeks ago. Correct. Very strong numbers in Q1. There's a lot of questions around the guide and the back half expectations. Right. Maybe just level-set kind of some of the key points on the earnings call. Yeah. How you folks thought about the back half, and then we'll dig into the questions from there? Sure. Well, the key points about the first quarter is it was another billion-dollar quarter and the first time ever a billion-dollar quarter in our first quarter, building on a billion-dollar quarter in our fourth quarter of last year. Just as a reminder, our quarters end roughly the end of January each year. We reported 35% overall revenue growth, which is certainly a significant pickup in overall revenue growth. I think even more importantly, 55% increase in our product revenue growth, which, by all accounts, is a proof point of a significant gain in market share overall as a company. We also raised our guide for Q2 and for the year as a whole. To give you a sense, last year, at the beginning of the year, we had guided to 11%. We delivered over 15%, close to 16% for the year. Thank you so much. This year, we guided, at the beginning of the year, to 19%. The guide at the end of Q1 for the year is 22%, already a 3% increase. What we did do is that 22%, that extra 3% came about because of the beat we had in Q1, as well as we increased for the full year by the amount that we're projecting for Q2, which is, again, a significant increase in terms of our guide as well as year-over-year. What we didn't do is raise the second half of the year. There's a lot going on in this market. Prices are increasing, which is creating all sorts of effects. Supply chains are tightening, which creates other types of effects. We didn't think it was really worthwhile or that we were adding anything by trying to define the macro in the second half of the year. We have a history of not changing guidance for a second half of the year after a first quarter, because we just don't believe that there's enough information. Generally, if you will, we guide on the basis of our pipeline and, to some extent, our backlog, which is only one to two quarters in advance. Guiding towards for the end of the year is just we generally don't do that after a first quarter. There was some disappointment, I think, by some people in the stock that we didn't guide even higher for the second half of the year. On the other hand, we're not trying to be the best crystal ball viewers. We're trying to run a company by improving and gaining market share each and every quarter, which we are doing. Perfect. No, it certainly seems a lot more prudent of a guide that's perhaps more de-risked, I would say, than maybe some of the other ones that are out there. I'm sure we'll come back and talk about memory a bit. Maybe at a very high level, think about it, these massive investments in AI infrastructure, more from hyperscalers. Correct. Heavily on compute, but certainly on memory storage as well. As enterprises start to get AI- ready. Right. Some signs this is happening. Can you just talk about what role does storage play for enterprises as they get AI- ready, as they look to build out their AI infrastructure? Where does Everpure really play into that? Sure. Well, for enterprises to get ready for AI, it's very interesting. A lot of the focus on the media is getting ready for AI on the compute side, right? Building out compute farms, super pods, adding components for that, whether it's networking or storage. What the media doesn't pay a lot of attention on is the fact that getting ready for AI is much more, in the enterprise, about getting their data ready for AI. What do I mean by that? Well, for decades, we've had an application-centric, application-focused model for how we build infrastructure. Across the board. Doesn't matter, enterprises, hyperscalers, it's all been application- focused. What that's done is it's fragmented the data across the enterprise. We hope to be, soon actually, part of the Fortune 500, but we're not yet. Despite that, we've cut our application use in half just to be more efficient. We're still well over 500 applications, okay? That's the ones we know about. Most of the enterprises we sell to are thousands of applications. Every one of those applications has their own data set, okay? Every one has their own data set, which is slightly different than another application. To do anything in an enterprise, such as issue a quote or an invoice, you have to pull information from many different applications. What's happened is the data is not consistent across these applications. When you have inconsistent data such as a customer name means one thing in one application, a different thing in a second, a different thing in the third, then coming up with the correct answers to an AI inquiry. It's a data problem. It is not specifically a compute problem. There's a lot of work going on. If you were to ask enterprises, "What are your biggest challenges for AI?" They will say it's their data. There's a lot that we are doing in helping customers get their data ready. It's part of the reason why we acquired 1touch. It allows customers to create a complete catalog of their data. It allows them to rationalize the different data that exists in these different data sets that they have. Enabling customers to get their data ready for AI, in my opinion, in the enterprise, is a huge market opportunity. That is still very nascent in its infrastructure. That being said, let's go to what the popular media talks about. Our FlashBlade product has been in place for six to seven years in AI environments. It can easily handle up to several hundred GPUs, which is what most enterprises, to the extent they build their own infrastructure, will be using. Our FlashBlade//EXA, which now goes up to several hundred thousand GPUs, is available for sovereign clouds, for GPU clouds, for tech titans who scale to that level. Finally, Portworx is in tremendous use right now in data pipelines around ETL. We have a lot of irons in the fire when it comes to AI. Got it. Maybe in the spirit of the irons in the fire with AI, you folks have this engagement with hyperscaler. Meta is the one you folks have talked about a fair amount. Clearly, I think investors have a lot of focus on thes hyperscaler engagements. Maybe we just stick with Meta because you have publicly discussed this. What are you helping Meta with? What is Everpure offering them that they can't do organically, perhaps? I'm going to genericize this a little bit. It's the same set of values that we can offer to any of the hyperscalers, so it's not specific to one, and we're developing this hyperscale solution to be roughly the same solution. Each of them will have their little differences here or there, but it's the same solution for any of the hyperscalers, and that's one of the things that makes it attractive to them. What are the advantages? Well, first of all, we're the only company literally in the world that has what we call DirectFlash technology. What is that? Most people think, as we would, as consumers, that an SSD is flash, and that's what everybody uses today, with the exception. of our customers. They use SSDs. What is an SSD? Well, the truth is that an SSD is flash masquerading as a hard drive. In order to get flash into things like laptops and everything else, instead of forcing all of the different operating system vendors to have to change their operating system, the flash manufacturers came up with a brilliant idea. Let's just make it look like a hard drive, and then anybody can use it. No change in software necessary. That's great, except that hard drives and flash work entirely differently. By developing software that works directly with flash, we automatically have about a 30%-40% price performance improvement. We're not going to spend time on that now. We have lots of patents and papers in this area. People can go reference that. That's valuable to a hyperscaler as well, right? Storage is their second-largest spend in infrastructure after servers. As more and more of their business goes to flash, we can not only save them a lot of money, but we have a number of other advantages as well. One is we make better use of the flash, so better space, power, and cooling. Our lifetimes are at least twice as long as an SSD, if not longer. Our failure rate is one-tenth of SSDs. One-tenth. There are those benefits, and then finally, if that weren't enough, every SSD, every hard disk, every different size, every different vendor, when there is a flash change, new flash changes, requires tweaks to the operating system because that's where disks are managed, out of the operating system. Our software goes into what's called user space in an operating system, so no changes to the operating system, and the hyperscaler doesn't have to worry about modifying the operating system for the next generation or just for a different scale. Our software takes care of all of that. We're just a much easier infrastructure to be able to manage. A lot of advantages to the hyperscaler. Of course, it's a big change from what they do today. Hyperscalers only modify their environment on roughly a three-year development cycle. There's a lot, obviously, of qualification, so it takes time, and it's an engineering-to-engineering interface, so it takes time. If I just think of a lot of the stuff, the way you described it, the way I've understood Pure, right, it's a lot about we can help you do this in a more efficient manner, right? Correct. Be that raw NAND, raw memory, right? Maybe hyperscalers could ignore it historically because it's like the price of NAND just kept going down, so your problem was getting smaller, not bigger, in a way. Correct. If you're in a place where memory just keeps going up at this point for several years, isn't, in a way, it's not TAM but the problem you solve is getting bigger. Even if you keep the percentage the same of our advantage, the dollar value of that percentage goes up. Therefore, it's more attractive. Charlie, maybe two things on that, right? A, why wouldn't the hyperscalers accelerate qualification processes? You're going to save them a lot of money. I'd rather do it now than later. Right. Secondly, maybe you can just talk about how does this engagement work from a financial basis for you? Is it here's the install, here's how much data we manage, and here's how we get paid for it? Is it à la carte? Just talk about those two vectors a bit. Yeah. Well, what the current environment has done is open the aperture or widen the funnel. We're getting more interest. I'd also say that the hyperscalers are more busy now, and have got more to do. It hasn't shortened the qualification cycle. Secondly, we're only one part of their design process. We're a relatively small part of their design process. Their design process is governed by the next-generation processor, the next generation of their own software the next generation of the switching systems that go in there. The qualification could be sped up, but not their design element. Right. That doesn't get sped up at all. Right. Unfortunately, while we're getting more interest, it hasn't sped up the design cycle. All right, now on the economics. It's a different set of economics than our traditional economics in that we're not selling a system per se. We're providing technology. A large portion of it is not our supply chain. We allow, in a sense, the hyperscalers. They're responsible for the NAND. They're also responsible. They buy a completed product from their supply chain. Now, our involvement is it's our design. We work with their supply chain so that they can supply it, but the NAND is sourced by the customer, in this case, the hyperscaler. What we get is a royalty on every, what we call, DirectFlash Module that the hyperscaler buys. We have some COGS because while the hyperscaler contracts, if you will, for the NAND directly, there are other components that they don't want to be responsible for. We're responsible for that. Our gross margins, and there are mix issues that will vary the gross margin, but generally in the 75%-85% range, given the mix. Got it. A lot of your, not your peers, but a lot of companies right now are talking about, "Hey, we're seeing this uplift in general purpose x86 servers in a very profound manner, actually. Yes. Historically, I think there's been a decent relationship between, hey, if you want to spin up these new servers and create new workloads, you've got to store your data somewhere, i.e., storage will follow through at some point. Yeah. Just talk about, historically, how has that lagged in between compute versus storage, and does that happen as you go into an AI world as well? Well, they have somewhat different cycles, sales cycles. On the other hand, storage in a traditional data center, so let's leave AI out of this for the moment. In a traditional data center, compute will generally be on the order of 60%-70% of spend, storage 20%-25%, and what's left over is networking at 5%-10% broadly speaking, about correct. Storage is larger than a lot of people think in terms of percentage of spend on infrastructure in a data center. I'm not counting power supplies and air conditioning and stuff like that. In an AI world, because of the cost of both HBM and GPUs, storage is much smaller. Because AI uses the fastest, highest performance networking is actually number two, storage is number three in a AI environment. No, the bottom is sort of lag between. It's not so much that. Yeah, I would say that the purchase cycle around processors and the purchase cycle around storage tends to, they're not tightly connected because a lot of times you can buy processors and you have spare capacity on your existing storage. Sometimes you start running out of storage because the data increases. It may not be tied so directly to a compute purchase cycle. Got it. Memory's been another topic that everyone's been focused on. I'm sure you spend a lot of time on it, from an input cost basis. If I think about what's happening with memory, maybe in a bit more of a strategic basis versus just the prices, historically, when you've had these periods of component tightness, it's reshaped a lot of competitive dynamics in the industry as well at the same time. Can you just maybe talk about how do you think the current memory environment influences your competitive positioning and how do customers' value proposition change with us? Right. When we talk about memory, I want to broaden it a little bit. There's the memory such as DRAM, and now HBM, but there's also storage, a storage memory, right? Both of them are going through the same significant price rises. The way it affects us is quite interesting. We, as you know, up until recently, we can talk about that, our gross margin on the product side has been in the upper 60s%, right? Even past 70%. 70, yeah. Whereas our competitive set, the storage industry as a whole, generally has about 50% gross margins on product. Right away, the equivalent increase of cost in our BOM results in a lower requirement for us to raise prices. We've been able to raise prices less and later than our competition because we don't use as much memory or storage, okay, for us to be able to deliver the same capacity of storage. Secondly, we've chosen to share some of the pain with our customers, who are operating at the lower end of our guidance while these price rises are taking place. For a variety of reasons, but at the end of the day, I can't go into a customer and say, "I'm so sorry that you have to pay more, and we're going to take more profit at the same time." Our first value as a company is customer first, and we live that. It's not just a saying. In the short term, we have chosen to operate at the lower end of our 65%-70% guidance. At the same time, that also makes us more competitive. I think we're going to see enhanced growth from a competitive standpoint, a market share standpoint, because we don't have to raise as much, and we're choosing to be in league with our customers. Maybe just on the price increase, I think there's been three price increases that I can track in the last, since the start of this year, at least, right? Since the start of the year. It is the best we can track. Your price increases are being less benign. They're all crazy numbers. Yeah They're less benign than what others are doing. You actually had a letter out to your customers, which I thought was very well-read. You mean more benign, less increase. Less increases, more benign to your customers. You touched on this a bit already, but just talk about it, why are you able to provide or have a lot lower price increases than your customers, and is it resulting in you winning more business over time, actually? One of it is just the physics of the financials, which is if traditionally our COGS were 30% of our product sales versus 50%, a 15%, let's say, or a 50% rise in your COGS would take you to 45% for the same price. You only have to raise prices by 15%, roughly speaking to make it up. Versus if it's 50%, you have to raise it higher to keep the same margin. Right? Just the physics of the financials make it possible to raise it less. Secondly, we are choosing to share some of the pain with our customers, that's even less. We bring it down to roughly 65%. If that doesn't raise market share, then I don't know what will. What I will say is that Q1 still, because of the lag between pricing, shipments, and backlog. Q1 was still mostly at Q4 pricing. Right? Q2 will be much more on Q1 pricing, which, as you said, has increased. I think what you're going to see as we go forward, or what I hope to see, I should say, going forward, is increasing market share. Got it. Now, I will say, let me just go further than that. Yeah. When we announced last quarter, I mentioned, you asked me about it right up front, 35% growth. Right? Rough estimate, we thought about a third of that was on the basis of price increases in pull-ins. That would be about, what, 10%-12%. We grew 35%, which means 20% growth. If you look at our competitors, they all grew less than 12%. I don't think we're special in terms of how many pull-ins are coming in, no matter what anybody says. If their pull-ins are roughly the same because everybody's responding to price increases by trying to get in a bit early to avoid future price increases. We're growing quite substantially. It's totally fair. Beyond pull-ins, which I think everyone's going to debate is it happening and how much is it happening, but there's certainly this element of it. When you talk to your customers, right, IT budgets at the end of the day are relatively finite. Correct. How are they navigating this surge in storage pricing very specifically? Are they saying, "I'll take a lower-tier storage. I'll take maybe some HDDs," I've heard from people, for example. Just how are customers dealing with this right now? It is, in fact, from a numbers standpoint, too early to say, because the prices are just starting to take place, and customers are attempting to get ahead of future price increases by ordering early. Right now, demand is very high. Which is why we're trying to parse out what is true demand, what is market share gains, versus what is pull-ins, right? Because what we care about is market share gains. Those will last. Market share gains will last. Short- term activities by customers associated with price rises or anticipated price rises, that's temporary, right? I think it's a bit early to say, but historically our experience is that with price rises or price declines. Environment that one lives in, is that demand of bits, right, does vary, does change with price rises or decreases, but not so much as to overcome the price itself. Price trumps capacity, but capacity does respond to price changes i n both directions. Yep. What about a desire to shift to slower storage or even HDD or hybrid arrays? Are you seeing customers actively make the decision? Historically, it's been a one-way train, everything goes more flash. Right. Well, yes, that has changed because the ratio, and it's still in transition changing now, because both flash and hard disks on the source side are sold out through 2028. Okay? There's no more supply of flash, that hasn't been accounted for, of hard disk until 2028. Prices are still, demand, sorry, supply has not kept up with demand, or looked upon another way, demand has not declined enough to match supply, and that's why we're seeing continuing price increases. What we can say right now is that the market that we were very active in about a year ago of flash being competitive on a total cost of ownership basis with hard disk, that doesn't exist right now. That's gone into stasis. Right. I'm a big believer in reversion to the mean. It'll come back, but just not with us right now. Got it. From your advantage point, you have to buy a lot of memory to meet your customers' demand as well. Just talk about what sort of visibility, what sort of conviction do you have with your memory as an input cost. You're talking about both flash and in RAM. More flash because it's a bigger input cost for you, I feel, right, than DRAM. In broad, just talk about your LTAs, the visibility on bits and pricing or just bits. We have very good visibility on both, and part of that is because of our hyperscale commitments that we currently have in place. We have plenty of flash. What has changed is that there's a separation now between being able to get long-term commitments on volume and getting long-term commitments on price. There are no long-term commitments on price right now. It's an allocation game, and pricing is basically every 30 days, right? We have allocation on capacity. Price was at 30, which is part of the reason why prices are escalating, is because you can no longer say, "I can buy ahead for six months." You can't. You can get capacity but not price. Does that change how you quote business to your customers at a 30-day increment as well or? Yes. For our entire life as a company, we have been quoting with a 90-day quote expiration. We're down to 30-day quote expiration. By the way, that's longer than most of our competitors. Yeah. Yeah. I've heard stories about right for cancellation, right to change pricing up until shipment. Yeah, until shipment. It's all kinds of fun clauses that are getting implemented. Exactly. We'll see how well they stick over time. One of the dynamics that's emerged is this neo clouds as a category, right? CoreWeave and others of the world, they have a lot of spending dollars. They're doing a lot of stuff. How do you think of that as an emerging customer base for Everpure? You, I think, have a relationship with CoreWeave? With CoreWeave, yeah. On a couple of different levels. Just talk about the neo clouds. What do they want? How are you tackling that kind of customer base? The neo clouds or GPU clouds, or for that matter, the sovereign clouds, was a market that we did not have a product to engage with up until the last year or so. To put that in perspective, most of the large-scale, sorry, LLM, large scale AI environment grew out of the HPC market, the high-performance computing market. For storage, was typically somewhat of a cul-de-sac. It was a very specialized market, very scientific in nature, very specs-oriented versus reliability-oriented. You were selling to scientists, and they like to tune things. They liked a lot of what we call nerd knobs in the business. Think of it sort of like, what was the name of the company that HP bought? What's it? No. The supercomputer company. Cray. Cray. Thank you so much. Think of it like Cray. Cray didn't expand to do other things in the standard commercial market, right? That was a lot like the companies that satisfied the HPC market. Well, AI grew out of that. It turns out that it was the people that were in HPC that now people all of the large-scale GPU environments, whether it's sovereign clouds or the tech titans or the GPU clouds. We didn't have a product in the race. We didn't speak the same language. We didn't go to the same schools. We didn't have the secret decoder ring. We certainly have certain beliefs as a company, in particular, that all of our systems should operate on the same software and have the same abilities, if you will, reliability, upgrade ability, the Evergreen capabilities that we have. It took us a while to modify or add a new set of capabilities to our FlashBlade product. Now, as I said, we introduced FlashBlade//EXA about a year ago, same Purity operating system, different configuration, where we are now publishing the best performance specs in the business, bar none. While we are still a little bit behind in features, we're catching up and not only are we replacing some of the traditional competitors in that market, but we're starting to play a bigger role in these GPU environments. Got it. It's still early days, but we feel that as these GPU clouds start to have to perform, you have to be able to provide a higher quality, more reliable, consistent service. They're going to appreciate a lot of our abilities that come with our product, versus some of the ones that were designed specifically for the scientific community. I was wondering where you would stack up. One of the things I hear is like, "Hey, these neo clouds with GPUs need a parallel file system. That's sort of what you need to deploy. That, to your point, doesn't come with all the redundancies and services that you want. That's right. Is that the delta that as they get more mature, Purity will work or? Purity will work. These are all just features. I personally, having been in the business a long time, things like reliability, sustainability, diagnostics, that's really hard stuff that you only get over a lot of experience over a lot of period of time. Things like individual features, like a parallel file system or KV cache. Quality of service guarantees. These are all just features. One of the other things that distinguishes us is at a much more foundational business level, is that we are a dyed-in-the-wool R&D company. One of the things that 70% gross margins allows us to do is we spend 20% of our revenue on R&D. By the way, in storage, that makes us the largest R&D spender in storage, bar none. Okay? We invest more than anybody else. I think that accrues to our growth, it accrues to the quality of the product that we can put out, but it also allows us to expand in other areas. Unless you believe that we're not terribly efficient at that, but it's something we work on a lot to make sure we are efficient in the way we invest our R&D, and I think our growth shows that. I don't worry about a feature gap if we're focused on the market segment. Got it. Perfect. If you shift gears a bit, Evergreen//One, right? It's sort of your subscription services offering. I would imagine in a time where memory's inflationary, it would resonate with customers versus not. I'm sure it is. Just talk about a bit more of the Evergreen//One offering. Are you seeing a better uptake of it in an environment like this? Yeah. Just to put some numbers behind that, Evergreen//One grew, I think it was 50% year-over-year, in Q4, and roughly 70% in Q1. That indicates that it is growing faster than our CapEx product. Our historical experience with this is that as prices go up, it becomes more competitive. By the way, our price increases on Evergreen //One is far less than our price increases on the CapEx. We can go into why, there are reasons why it is not as directly affected by price increases or input cost increases. What that would say as we go forward, and we only have one quarter of price increases really so far to measure this off of, but I'd be surprised if it didn't mean that the relative amount of bookings that come in via Evergreen// One will be higher than the CapEx. Got it. Maybe just two things on Evergreen//One. What are the gating factors? Why wouldn't customers adopt it faster than they already have? What limits them in that? Maybe I'll ask you the second one after that. Well, first of all, it's a different way. It's so funny. Even though they're used to buying on subscription in the cloud, right or for SaaS or for the hyperscalers, they're very unused to doing it inside their own data center. It's a CapEx model inside their data center. Honestly, sometimes we spend two to three months with the finance organization in the customer, trying to train them on how they do it. Obviously, it's growing faster than our CapEx product, but it's not unusual for them to finally say, "You know, it's just going to be easier if we do CapEx, so we're just going to do that." Now, pricing does make a difference, so we'll see. That is customer financial models sometimes are more difficult to change than their technical model. Right. Why isn't it just automatic? It's generally for those reasons. Got it. Why is the investment, or from your side, lower for Evergreen//One versus the traditional product side? Yeah. Well, first of all, obviously, our terms are longer, but it's more than that. Our Evergreen//One is a true subscription, so it's not a lease, it is not a financing. What do we mean by this? What we sell to the customer is purely a service- level agreement. It's a service level agreement on performance. It's a service level agreement on capacity. It's a service level agreement on reliability, right? That's it. There's no serial number involved. We own the equipment. We get to choose. There's no guarantee of new equipment. If you go to Amazon, do they tell you, "We're delivering new equipment to you?" No. You're just getting a service. We provide a service. Our Evergreen//Forever subscription, which is for customers that do purchase, they are guaranteed hardware upgrades every few years. That hardware that comes back has more life associated with it. We're able to use that in our Evergreen//One service. What does that mean? That means we're blending costs over a long period of time. We refurbish it, of course. All the data is erased. We're using refurbished equipment in addition to new equipment, and we get to sell it at prices that are competitive with as-a-service pricing. Our costs don't go up automatically, and we happen to be in a great cycle because we just went through a refresh on our CapEx product, which means we have a lot of equipment coming back for refresh that was priced at three years ago. All right. Perfect. That is helpful. You folks recently changed your name from Pure Storage to Everpure. You've certainly done a few deals like 1touch, Portworx a couple of years back. You are trying to become more than just, "Hey, here's the storage layer," right? Just talk about like, maybe this should've been my question to you at the start, not the end. What is the vision with this? Is it more like we're going to be a storage bottleneck solution provider? Yeah It's more than just traditional storage medium. No. We fundamentally believe, I alluded to this early on, that the nature of applications and data is fundamentally changing. It's fundamentally changing because the app world has fragmented the customer's data environment. AI, if left to the current way of doing things, is going to fragment it even further. Everything wants another copy of your data. Every SaaS company's strategy right now is give me all your data and I'll give you the AI answers. The Databricks of the world and the Snowflake of the world, they all say, "Give us all your data and we will provide you all the AI answers." How many different organizations is a customer going to give all their data to? I don't think it's scalable. I don't think it's a viable solution. Our belief is that if these applications are no longer systems of record, which they can't be because in order to do anything, you have to have information from all of these different systems. If that information is not consistent, the world's in big trouble. What can be consistent is no longer the application, but the data has to be consistent. If the world's going to migrate from app-centric to data-centric, data primacy, what we're calling data primacy, we're in a very good position to help customers get there. What does 1touch do? 1touch, for example, allows customers to get a catalog of all their data, all of it, not just what's on our stuff, what's on competitive stuff, what's in SaaS, what's in the cloud, what is with partners, and allows them, first of all, to not only get a catalog, but to get a map of how this data set relates to that data set. That it has the same name of the customer in two different places, but it has different semantics for what that customer is doing. It has different information about that customer. 1touch, like the name sounds, brings that all together so you can have a common semantic understanding of an entity like a customer or like an asset, or like a quote, all right, or an order. Where we're going is we're going from pure data storage, pun intended, to data management, where we can help customers manage their data and have fewer copies, have more comprehensive understanding of their data as we go into this world. It's not just about AI. There is a data crisis going on. If you ask any customer, "What is your biggest challenge to implementing AI?" They're going to say right away that it's their data. Their data is a mess. Perhaps we're taking a what is not a well-known or untraditional approach to helping customers in this world of AI, but we believe it's fundamentally a data problem, and that's what we're going after. Yeah. I was going to say, I certainly have an affinity to the name Everpure, but maybe it's because I work at Evercore. Yeah. There's a link there. I certainly think it's more than just a data storage problem. It does make a lot of sense. I think the time's almost up. Maybe I'll pause my questions there, Charlie. I'll turn it back to you. Anything we did not touch on that we did not cover that you think folks should be aware about? You were very kind in not spending half the time on the hyperscale challenge, so I appreciate that. We are very pleased with the progress we're making there overall. Outside of that, no, it was a great conversation. Thank you. Thank you very much. We appreciate the time. Yeah. Thank you. Thank you.
Loading workspace