>>from our studios in the heart of Silicon Valley. Palo ALTO, California It is a cute conversation. >>Hi, and welcome to the Cube Studios for another cube conversation where we go in depth with thought leaders driving innovation across the tech industry. I'm your host, Peter Boris. Everybody's talking about the cloud and with the cloud might be able to do for their business. The challenge is there are a limited number of people in the world who really understands what it means to build for the cloud utilizing the cloud. It's a lot of approximations out there, but not a lot of folks are deeply involved in actually doing it right. We've got one here with us today. Wound Junk is thesis CEO and co founder of Clue Meo Womb. Welcome to the Cube. >>Happy to be here. >>So let's start with this issue of what it means to build for the cloud. Now Lou Meows made the decision to have everything fit into that as a service model. What does that practically need? >>So from the engineering point of view, building our sauce application is fundamentally different. So the way that I'll go and say is that at Cuneo. We actually don't build software and ship software. What we actually do, it builds service and service is what you're actually shipped our customers. Uh, let me give you an example. In the case of Kun, you they say backups fail like so far sometimes fails. We get that failures too. The difference in between Clooney oh, and traditional solutions is that if something were to fail, we are they one detecting that failure before our customers do Not only that, when something fails, we actually know exactly why it failed. Therefore, we can actually troubleshoot it, and we can actually fix it and operate the service without the customer intervention. So it's not about the books also or about the troubleshooting aspect, but it's also about new features. If you were to introduce a new features, we can actually do this without having customers upgraded call. We will actually do it ourselves. So essentially it frees the customers from actually doing all these actions because we will do them on behalf of them >>at scale. And I think that's the second thing I want to talk about quickly. Is that the ability to use the cloud to do many of the things that you're talking about at scale creates incredible ranges of options that customers have at their disposal. So, for example, a W s customers of historically using like snapshots to provide ah modicum of data protection to their AWS workloads. But there are other new options that could be applied if the systems are built to supply them. Give us a sense of how clue Meal is looking at this question of, you know, snapshots were something else. >>Yes, so, basically, traditionally, even on their own prints, out of the things you have something called the snapshots and you had your backups right, and they're they're fundamentally different. But if you actually shift your gears and you look at what A. W S offers today, they actually offers the ability for you to take snapshots. But actually that's not a backup, right? And they're they're fundamentally different. So let's talk about it a little bit more what it means to be snapshots and a backup. Right? So they say, there's a bad actor and your account gets compromised like your AWS account gets compromised. So then the bad actor has access not only to the EBS volumes, but also to the snap shows. What that means is that that person can actually go in and delete the E. V s volume as well as the TVs. No options. Now, If you had a backup, let's say you are should take a backup of that TVs William to whom? You, that bad actor would have access to the CVS volumes. However, it won't be able to delete the backup that we actually have, including you. So in the whole thing. The idea off Romeo is that you should be able to protect all of your assets, that being either an on Prem or neither of us by setting up a single policies. And these are true backups and not just snapshots. >>And that leads to the last question I have, which is ultimately the ability to introduce thes capabilities. At scale creates a lot of new opportunities that customers can utilize to do a better job of building applications, but also, I presume, managing how they use AWS because snapshots and other types of service can expand dramatically, which can increase your cost. How is doing it better with things like native backup service is improve customers ability to administer the AWS spend and accounts. >>So great question. So, essentially, if you look at the enterprises today, obviously they have multiple on premise data centers and also a different car providers that they use like AWS and azure and also a few sauce applications. Right? So then the idea is for Camilo is to create this single platform. What? All of the stains can actually be backed up in a uniform way where you can actually manage all of them. And then the other thing is all doing it in the cloud. So if you think about it, if you don't solve the problem, fundamental in the car, their stings that you end up paying later on. So let's take an example. Right. Uh, moving bites moving bites in between one server to the other, traditionally basically moving bites from one rack to the other. It was always free. You never had to pay anything for that. >>Certainly in the data center, >>right? But if you actually go to the public cloud, you cannot say the same thing, right? Basically, moving by across AWS recent regions is not free anymore. Moving data from AWS to the on premises. That's not for either. So these are all the things that any, you know, cop provider service provider, because has to consider and actually solved so that the customers can on Lee back it up into Clem you. But then they actually can leverage different cloud providers, you know, in a seamless way, without having to worry all of this costs associated with it so criminal we should be able to back it up. But we should be able to also offer mobility in between either aws back up the M word or the M. C. >>So if I can kind of summarize what you just said that you want to be able to provide to an account to an enterprise the ability to not have to worry about the back and infrastructure from a technical and process standpoint, but not also have to worry so much about the back and infrastructure from a cost of financial standpoint that by providing a service and then administering how that service is optimally handled, the customer doesn't have to think about some of those financial considerations of moving data around in the same way that they used to have. I got that right? >>I absolutely yes. Basically multiple accounts, multiple regions, multiple couple providers. It is extremely hard to manage. What come you does? It will actually provide you a single pane of glass where you can actually manage them all. But then, if you actually think about just and manageability this actually you can actually do that by just building a management layer on top of it. But more importantly, you really need to have a single data repository for you. For us to be able to provide a true mobility in between them. One is about managing. But the other thing is about if you're done, if you're done with the real divide way, it provides you the belly to move them and leverages the cloud power so that you don't have to worry about the cloud expenses but whom you internally is the one that actually optimizing all of this for our customers. >>Wound young cto and co founder of Cleo. Thanks very much for being on the Q. Thank you. And thank you for joining us for another cube conversation. I'm Peter Bursts. See you next time