 Hello everyone, welcome to the CUBE Conversation here at the Palo Alto Studios for theCUBE. I'm John Furrier, the co-founder of SiliconANGLE Media. We're here for some news analysis with Peter Schmails with the CMO of Datos.io, D-A-T-O-S.io, hot new startup with some news. Peter was just here for a thought leader segment with Chris Cummings talking about the industry breakdown, but the news is hot prior to re-invent which you'll be at. Recovery X is the product, 2.5, it's a release. So you got a point release on your core product. Correct. Welcome to this conversation. Thanks for having me. Yeah, we're excited to share the news, big day for us. All right, so let's get into the hard news. You guys are announcing a point release of the latest product, which is your core flagship, Recovery X. Correct. Love the name, love the brand, the X in there, it reminds me of the iPhone, so it makes me want to buy one. But, you know, it's the X-Factor. We can make that happen. You guys are the X-Factor. So we've been pretty bullish on what you guys are doing. Obviously like the positioning, it's cloud, you're taking advantage of the growth in the cloud. What is this new product release? Why? What's the big deal? What's in it for the customer? So what's, so I'll start with the news and then we'll take a small step back and sort of talk about why exactly we're doing what we're doing. So Recovery X 2.5 is the latest in our flagship Recovery X line. It's a cloud data management platform. And the market that we're going after and the market we're disrupting is the traditional data management space. The proliferation of modern applications. It includes which companies? So the Veritas's of the world, the Commvault's of the world, the Dell EMC's of the world. Anybody that was in the traditional backup recovery data. 20-year-old architected data backup and recovery software. You stole my fun fact, which is no, but very fair point, which is that the average age approximately of the leading backup and recovery software products is approximately 20 years. So a lot's changed in the last 20 years. Not the least of which has been this proliferation of modern applications, which are geo-distributed, microservices-oriented, and the rapid proliferation of multi-cloud. That disrupts the traditional notion of data management, specifically backup and recovery. That's what we're going after with Recovery X. Recovery X 2.5 is the most recent version. News on three fronts. One is around advanced recovery, and we can double click into those, but it's essentially all about giving you more data awareness, more granularity to what data you want to recover and where you want to put it, which becomes very important in the multi-cloud world. Number two is around what we call data center aware backup and recovery. That's all about supporting geo-distributed application environments, which again is the new normal in the cloud, and then number three is around enterprise hardening, specifically around security. So it's all about us increased flexibility and new capabilities for the multi-cloud environment and continued enterprise hardening the product. Okay, so you guys say significant upgrade. I want to just look at that. I'm also pretty critical, and you know how I feel on this, so don't take it personal. Multi-cloud is not a real deal yet. It's in statement of value that customers are saying, it's coming, but clouds here today, regularly clouds. So multi-cloud, what does multi-cloud actually mean? I mean, I can have multiple clouds, but I'm not actually moving workloads across clouds yet. Or are they? I disagree. I actually disagree. We've got, we have multiple customers, so. Debunk that. I will debunk that. So number one use case for RecoverX is backup recovery, okay? But with the twist of the fact that it's for these modern applications, running these huge distributed environments, which means it's not about backing up my data center. It's about, I need to make a copy of my data, but I want to back it up in the cloud. I'm running my application natively in the cloud, so I want to back up in the cloud. I'm running my application in the cloud, but I actually want to back up from the cloud, back to my private cloud. So that's, in lies, a backup and recovery, an operational recovery use case that involves multi-cloud. That's number one. Number two use case for RecoverX is what we talk about around data mobility, okay? You have a different definition of multi-cloud. Yeah, well, sorry, what was your, our definition of multi-cloud is fundamentally a customer using multiple clouds, whether it be a private on-prem, GCP, AWS, Oracle, any mix and match. That's our definition. I buy that. Where I was getting critical was a workload. I have a workload and I'm running it on Amazon. It's been architected for Amazon. Then I also want to run that same workload on Azure and Google or Oracle or somewhere else. I have to re-engineer it to move and I can't share the data. So to me, well, multi-cloud means I can run it anywhere, my app, anywhere. Backup is a little bit different. You're saying the cloud environments can be multiple environments for your solution. So you're looking at it from the other perspective. Correct. And the category, the way we define ourselves is application-centric data management. And what that essentially means is we don't care what the underlying infrastructure is. So if you look at traditional backup and recovery products, they're LUN-based, so I'm going to backup my storage LUN, or they're VM-based. And a lot of big companies made a lot of money doing that. The problem is there are no LUNs and VMs in a hybrid cloud or multi-cloud environment. The only thing that's consistent across cloud environments is the data and the applications that are running. So where we focus is we're 100% application-centric. So we integrate at the database level. The database is the foundation of any application you create. We integrate there, which makes us agnostic to the underlying infrastructure. We run, as examples, we have customers running next-generation applications on-prem. We have customers running next-generation applications on AWS and GCP, any permutation of the above. And to your point about back to the multi-cloud, we've got organizations doing backup with us, but then we also have organizations using us to take copies of their backup data and put them on whatever clouds they want for things like test every refresh, or performance testing, or business analytics, whatever you might want to do. So you're pretty flexible, I like that. So we talked before, another segment, and certainly even this morning, about modern stacks, modern applications. This is the big-to-do item for all CXOs and CIOs. I need a modern infrastructure, I need modern applications, I need modern developers. I need modern everything, hyper, micro, whatever, ultra. Whatever buzzword you use. But you guys in this announcement have a couple key things I want to just get more explanation on. One, advanced recovery, backup anywhere, recover anywhere, and you said enterprise grade, security, the third thing. So let's just break them down one at a time. Advanced recovery for GATOS 2.5, RecoverX 2.5. What is advanced recovery? It's very specifically about providing high levels of granularity for recovering your data on two fronts. So the use case is, again, backup, I need to recover data, but I don't want to necessarily recover everything. I want to get smarter about the data I want to recover. Or it could be for non-operational use cases, which is I want to spin up a copy of data to run test dev or to do performance testing on. What advanced recovery specifically means is, number one, we've introduced the notion of queryable recovery. What that means is that I can say things like star.johnstar, and the results returning from that, because we're application-centric and we integrate at the database, we give you visibility to that. I want to see everything star.johnstar. Or I want to recover data from a very specific row and a very specific column. Or I want to mask data that I do not want to be recovered and I don't want people to see. The implications of that are, think about that from a performance standpoint. Now I only recover the data I need, so I'm very, very high levels of granularity based upon a query, so I'm fast from an RTO standpoint. The second part of it is for non-operational requirements, I only move the data that is selected to that data set, and number three is it helps you with things like GDPR compliance and PII compliance, because you can mask data. So that's query-based recovery. That's number one. The second piece of advanced recovery is what we call incremental recovery. That is granular recovery based upon a time stamp. So you can get within individual points in time, so you can get to a very high level of granularity based upon time. So it's all about visibility at your data and getting very granular in a smart way to what you want to recover. So if I kind of hear what you're saying, what you're saying is essentially you built in the operational effectiveness of being effective operationally. Time to back recovery, all that good RTO stuff, getting stuff restoring operationally very, very fast. So there's a speed game there, which is table stakes, but your real value here is all these compliance nightmares that are coming down the pike, GDPR and others, there's going to be more. Absolutely. I mean, it could be HIPAA, it could be GDPR, anything that involves policy, anything that requires, we're completely policy driven and you can create a policy to mask certain data based upon the criteria you want to put in. So it's all about. So you have the best of performance and you got some tune ability. And it's all about being data aware. It's all about being data aware. So that's what advanced recovery is. Okay, backup anywhere, recover anywhere, what does that mean? So what that means is the old world of backup and recovery was I had a database running in my data center and I would say database, please take a snapshot of yourself so I can make a copy. The new world of cloud is that these microservices based modern applications typically run, by definition distributed and in many cases they run distributed across their geo-distributed. So what data center aware backup and recovery is, use a perfect example, we have a customer, they're running their e-commerce, it's a leading online reservation, restaurant reservations company. They're running their e-commerce application on-prem, interest enough, but it's based on Cassandra, distributed database. They're run, excuse me, MongoDB, sorry. They're running geo-distributed, sharded MongoDB clusters. That's a mouth, anybody in the traditional backup and recoveries, their head would explode when you say that. In the modern application world, that's a completely normal use case. They have a data center in the US, they have a data center in the UK. What they want is they want to be able to do local backup and recovery while maintaining complete global consistency of their data. So again, it's about recovery time, ultimately, but it's also being data aware and focusing only on the data that you need to backup and recoveries. So it's about performance, but then it's also about compliance, it's about governance. That's what data center aware backup is. And that's the global phenomenon people are having with the geo. Absolutely. Yeah, I mean you could be within country, it could be any number of different things that drive that, we can do it because we're data aware. And that creates complexity for the customer. You guys can take that complexity away from the whole, the global regional, where the data can set. Correct, I'd say two things actually. Do you have the customer's credit? The customer's building these apps are actually getting a lot smarter about what their data is. So they expect this feature. Oh, absolutely. So this is, I wouldn't call it table stakes because we're the only kids on the block that can do it, but this is a direct response to our customers that are building these new apps. I want to get into some of the environmental and customer drivers in a second, but we'll nail one last segment down because I want to unpack the whole, why is this trend happening? What's the gestation period? What's the main enabler for you? But a final point on the key advance, significant announcements. My favorite topic, enterprise grade security. What the hell does that mean? First of all, from your standpoint, what industry is trying to solve the same thing? So enterprise grade security, what are you guys providing in this? It's number one, it's basically security protocol. So TLS and SSL, this is weed stuff. TLS, SSL, so secure protocol support. It's integration with LDAP. So if organizations are running, primarily if they're running on-prem and they're running in an LDAP environment, we're supported there, and then we've got Kerberos support for Kerberos authentication. So it's all about just checking the boxes around the different security and transfer protocols. So this is like in between the toes, the details around compliance, identity management. Bingo. I mean, we just had centralized cyber connect conference and you're seeing a lot of focus on identity. Absolutely, and the reason that that's sort of from a market standpoint, the reason that these are very important now is because the applications that we're supporting are not, these are not science experiments. These are e-commerce applications. These are core business applications that mainstream enterprises are running and they need to be protected and they're bringing the true classic enterprise security, authentication, authorization. Are you guys aligning with those features or is there anything significant in that section? From an enterprise security standpoint, it's primarily about we provide the support so we integrate with all of those environments and we can check the boxes. Oh, absolutely, TLS, absolutely. We've got that box check. You're not competing with other cyber security. No, this is purely, we need to do this. This is part of our enterprise role. This is where you partner. Well, no, this is literally, for these things, it's literally just us providing the protocol support so that LDAP's a good example. We support LDAP, so we show up and if there's somebody who's in identity management. Yeah, but did you look at the other security solutions as a way to integrate with? Yeah. Not so much. Oh, absolutely. No, this has nothing to do with competition. It's just supporting, I mean, Google has their own protocol, you know, security protocols, we support those. So does Amazon. I really don't want to go into some of the customer benefits to let the folks go to the Dados website, D-A-T-O-S dot I-O is the website. If you want to check out all their customer references, I don't want to kind of drill on that. I kind of want to really end this segment on the core issue for me is kind of reading the tea leaves. You guys are different. You're now kind of seeing some traction and some growth. You're a new kind of animal in the zoo, if you will. You're kind of, and you got a relevant product. Why is it happening now? And I'm trying to get to understanding cloud obviously is enabling a lot of stuff. You guys are an effect of that, a data point of what the cloud has enabled as a venture. Everything that you're doing, the value you create is a functional cloud and data and how data is moving. Where is this coming from? How is it? So just recently, is it a gestation period of a few years? Where did this come from? You mentioned some comparisons to like Oracle and... So I'll answer that in sort of, we like to use history as our guide. So I'll answer that both in macro terms and then I'll answer it in micro terms. From a macro term standpoint, this is being driven by the proliferation of new data sources is the easiest way to look at it. So if you let history be your guide, there was about a 78 year proliferation or gap between proliferation of Oracle as the primary, traditional, relational, database, data source and the advent of Veritas who really defined themselves as de facto standard for traditional on-prem data center relational data management. You look at that same model, you look at the proliferation of VMware in the late 90s, about a 78 year gestation with the rapid adoption of Veeam. You know, in the early days, a lot of folks laughed at Veeam like who's going to back up VMs? People aren't going to use VMs in the enterprise. Now you look at Veeam, great company that's done some really tremendous things, carving out much more than a niche, providing backup and recovery and availability in a VM based environment. The exact same things happening now. If you go back six to seven years from now, you had the early adoption of the MongoDBs, the Cassandras, the couches. More recently, you've got a much faster acceleration around the DynamoDBs and the cloud databases. We're writing that same way. This is a side effect of the enabling of the growth of cloud. So similar to what you do in VMware with VMs and database for Oracle, you've got to take it to the next level. These new data sources are completely driven by the fact that the cloud is enabling this completely distributed, far more agile, far more dynamic, far less expensive application deployment model and a new way of providing data management is required. That's what we do. Yeah, I mean, it's a function of maturity. One, as Jeff Frick, our general manager of theCUBE always says, the industry moves to its next point of failure. In this case, failure is problem that you solve, right? So the headaches that come from the awesomeness of the growth. Absolutely, the cloud. And to answer that, micro wise briefly. So that was the macro. The macro is the proliferation of the migration of, you know, the movement from monolithic apps to microservices based app, it's happening. And the cloud is what's enabling that. The move from traditional on-prem to hybrid cloud is absolutely happening. That's by definition the cloud. The third piece, which is cloud-centric is the world's moving from a scale-up world to an elastic compute, elastic storage model. We call that the modern IT stack. Traditional backup recovery, traditional data management doesn't work in the new modern IT stack. That's the market we're playing in. That's the market we're disrupting is all that traditional stuff moving to the modern IT stack. Okay, Datos.io announcing a 2.5 release of RecoverX, their flagship product, their startup growing out of Los Gatos. Peter Schmalz here, the CMO. Where are you going to be next? What's going on? I know we're going to see it reinvented in a week and a half. Absolutely, so we got two stops. Well, actually the next stop on the tour is reinvented. So looking forward to being back on the Cube, it reinvented. And company feels good about this. Things are good. You got good money in the bank, you're growing. We feel fantastic. I mean, it's been, it's fascinating to watch as things evolve. Conversations we have now versus even six months ago. It's sort of the tipping point of people get it. You sort of explain it. So yeah, it's data management for modern applications. Are you deploying modern applications? Absolutely. Share one example to end the segment on what you hear over and over again from customers that illuminates what you guys are about as a company, the DNA, the value proposition, and the impact and the results and value for customers. So I'll use a case study as an example. We're the world's largest home improvement retailers. Old way was they ran their multi-billion dollar e-commerce infrastructure, running on IBM DB2 database, running in their on-prem data center. They've moved their world. They're now running. They've re-architected their application. It's now completely microservices based running on Cassandra deployed 100% in Google Cloud Platform. So they fund them and they did that because they wanted to be more agile. They wanted to be more flexible. It's a far more cost effective deployment model. They're all in on the cloud. And they needed the next generation backup and recovery data protection, data management solution, which is exactly what we do. So that's the, the value, backup's not a new problem. People need to protect data and they need to be able to take that advantage. Here's the final, final question. I don't, I'm a customer watching this video. You know, bottom line me, I'm kind of hearing all this stuff. When do I call you? What are the signals? What are the little smoke signals I see in my organization burning that I need, when do I need to call you guys? You should call Data SIO anytime. If you're doing anything with development of modern applications, number one, if you're doing anything with, with hybrid cloud, you should call us because you're going to need to reevaluate your overall data management strategy. It's that simple. All right, Peter Spence, the CMO of Datos, one of the hot companies here in Silicon Valley at a low Scados, California, of course. We're in Palo Alto at theCUBE Studios. I'm John Furrier. This is theCUBE conversation. Thanks for watching.