>> Announcer: Live from Las Vegas, it's The Cube, covering AWS re:Invent 2017 presented by AWS, Intel, and our ecosystem of partners. >> Hey, welcome back everyone. Live here in Las Vegas, the Cube is covering exclusively the AWS re:Invent. We've got two sets. This is set one, set two behind me. We're here with a startup called Zettabytes, Rishi Yadav, Cube Alumni CEO, and Sudhir Janir, CTO. Hot new start-up, Zettabytes. Formerly, you're an entrepreneur, your other company's still going, Info Objects. Welcome back. >> Thanks for having us here. I dont know it's the seventh time, eighth time? I mean, we love Cube guys. Yes, so Info Objects is the mothership and doing really, really great, and today we are launching Zettabytes, which is our hybrid cloud, cloud integration platform. We are starting with AWS, and then it's going to have integration for the clouds. >> So start-ups are impacted, and we were talking yesterday about kind of a demarcation line between a point in time. I say 2012, maybe you can say 2014, if you were born before 2012 or 2014, you probably didn't factor the cloud as large scale as it is. But after that day, you're a new born start-up, you look at the cloud as a resource, an opportunity, so what's your perspective as an entrepreneur, a serial entrepreneur, you start a company, you look at the big beast in Amazon, opportunity, challenge, what's your view? >> So actually 2014 was an inflection point for two things. Number one is that the big data, big data, it started with the hyper scale companies, and at that time, you're talking about Facebook, and Yahoo and other places, but it was not enterprise-ready. And we suddenly saw the option. John, you have been following the big data directly from the, I think the cloud data basement days, right? So in 2014 it got a better option. And the things like security and governance, which were offered not much concern earlier, it became front and center. Another thing which happened was around 2014, 2015, timeframe, the public cloud, which were for eight, nine years, essentially AWS, that was about 70 start-ups about saving money for them. That also started getting an option, and the enterprise, and when you're talking about enterprise, there you cannot tell them that if you deploy 10 servers on AWS, it's going to save you $200,000. They would say you already have $500 million spent. We have these huge data centers, so they needed some more value than that. >> How about your company Zettabytes, so you're launching a new company, what is it, what does it do, why are you starting it? Take a minute to explain what you're doing. >> Yes, absolutely. So the Zettabytes idea came from this convergence of the big data, public cloud and IOT. And market is ripe for it, and the challenge was that we talked to a lot of customers, a lot of them have already started working in the cloud, and some of them were planning to start the journey in the cloud, and the challenge was that at the same time they also wanted to build a big data link, Andy talked about it a lot today, right, assuming the largest big data lake. So now the question was that do you really want to go the old school route in which you are using Hadoup and other services around it, and then you do lift and shift to AWS? And then you transform to PAS. So you spend one and a half, two years in doing Hadoup, and then you spend another one and a half, two years, doing the PAZ, that cloud-native transformation in a better way. And then realize that whether the clients are on AWS today, or they are going to be in one year, they need the same experience, the same cloud experience, the same AWS experience which they have on their AWS, they want on-prem. Now that includes the other cloud-native APIs, but also the agility and everything else. >> So let met ask Sudhir a question. So you're the CTO. I know you're technical too, so I have both of you. So the old days, I'm a developer, I have my local host, I'm banging away code, and then I go, okay I'm done. And I say, ship to the server for QA or whatever. And even the cloud. Businesses want that same kind of functionality on premise. They want to go to the cloud, so all the developers are changing, they want that local host like feel. They don't wanna have to write code, ship it to a server, put it through the cloud, they just want instant integration to Amazon. Is that what you're doing? >> Yeah. >> Did I get it right? 'Cause that seems what I think you're doing. >> Yes, you develop that seamless experience. So you have the same set of APIs, which you normally would do on AWS, so still use the same data, still use the same data blue CLI. Use all data blue APIs, we're accepted those APIs on this platform, build a good base, based on those APIs, now using Kubernetes, you decide where this workload will go. >> So one of the challenges of AWS though is that they release services like constantly. I think we had the announcer at the keynote today, it was like another hundred or so services that they were releasing. So how do you choose which ones? Do you support all of them, or do you focus on specific ones? >> No, first we are focusing on a few specific ones, which are mostly being used. We are starting with Lexi, for example, as three. Lamda, Kenesis, Kafka, and this bargain is DFS are there from day one also. And all of these are Lexi, we are doing Lexi, today official announcement, they have launched Kubernetes Now. Container management service. We have that flexibility from day one only. So we have that in our outlines, and using that, even for example, your workload says, some of the piece should run on that, on Lexi, on permalines. Some of the P should go to the cloud, that is also possible. >> So you're selling an appliance. >> Yeah, yeah. The one million Lexi, or Kubernetes million might run on the AWS, few of the menus might run on your uplines, you can easily Lexi's do the all the container management. >> This is model, they pay for the box, or is it a service? Or they get the box as part of a service? What's the business model? >> So we do both, so it's a (mumbles) format, as well as an appliance, so the beauty of appliances is that everything is already optimized for you, so that makes it very easy. But if a customer has a chosen hardware platform, and we can definitely deploy it on that also. And adding to the hunter services thing, I think that's a great point, that AWS has so many services now that can you really go and figure out which services are most optimized for your needs? So that's where you need a partner on prem-site, and that's what we are going to be, and another thing as Sudhir mentioned, the EKS which they announced today, Kubernetes, so you have Kubernetes on-prem, AWS is supporting Kubernetes, and we are also supporting Kubernetes, so if you want closer to that level, it's completely seamless. >> And you were saying before, your target is enterprise has been good, so the appliance delivery model and the simplicity of being able to manage a lot of different services. Clearly being able to manage things at scale is something that enterprisers are crying out for because otherwise I have to, AWS is great, if you wanna hand build everything yourself, it has all of those components that you can assemble like Lego, but if I'm an enterprise, I want to be able to do that at scale. Humans don't scale very well, so I need some technology to help with that. So it sounds like you are actually providing the leverage to get enterprise humans to be able to manage AWS. Is that a fair characterization? >> Absolutely, that is definitely a very important aspect of it, and another aspect of it is that if you do not want to have some workloads on AWS for one thing or another. IOT workloads by definition cannot be on AWS. Low intensive workloads. They cannot be on AWS. In the same way the workloads in which you need some actual level of security. So within your data center, as much as beat down the data center piece, you have your own security and governance. And you can do that, and that's coming back to your question that are we going to support all hundred services, yes, but the local execution we have only going to provide for some services, which by their very nature make more sense to learn on-prem. >> Yeah, keep the core services. >> Rishi: Core services. >> All right so how do you guys gonna sell this product, take us through the start-up situation, you're here, are you talking to customers? Why are they are buy you? What's the conversations like? When do they need you? Take us through your conversations here at re:Invent. >> Yeah, so before that, the AWS has been super successful for the green field applications. The new applications, the applications which are born in the cloud, but when it comes to transforming the existing application it becomes a big, big challenge. So a lot of customers are coming to us, they are interested in how I can seamlessly transform their-- >> John: What's an example workload? >> So the example workloads for us is going to be the big data workloads. Which we have specialized in for last so many years. So one of them can IOT. Sudhir, probably you can explain what that is. >> So that example could be for example from today's keynote, if you see Expedia case, or Lexi Goldman Sachs case, they spend a lot of time in converting their code to the AWS specific-word, right? Millions of lines, or billions of lines of code. What we are doing today, if you dealing with the application, tomorrow it could be future ready for AWS. It's more convenience, we are actually modeling your experience with AWS. >> So it's making for enterprisers to make that transition from what they're doing today across the cloud, because that's a big deal for them. >> Tomorrow when you are Lexi, then you go to AWS, your data will decide whether you want to earn your workload on our plans, or AWS. >> Okay, so your market is hybrid cloud, basically. People doing hybrid cloud should talk to you guys. >> Yeah, and code would be future proof. What you you are you developing today-- >> John: All right so is the product shipping? >> Yes, so we are in the early beta stage, we already have five beta customers. And the product is going to be ready in a week's time. >> So data now. >> Yeah, yes. >> Yeah, these guys are ready already. >> Open beta, restricted beta? >> It is going to be restricted beta for now. Then it's going to be open beta, so yes, we are going to five more customers in the next two months for the beta. >> Take a minute to explain the type of customer you're looking for. Are they all field spots, any more, you have five more spots, you said? >> Yeah, we have five more spots for the beta. >> John: Who are yo looking for out there? >> Any large enterprise which is planning to move to AWS, but are struggling with all the nitty gritties, looking at the hundred services, and how do you integrate your existing applications there. So how you could take baby steps, like so we are going to not just take that baby steps, but sprint through it, so that's what Zettabytes plans is for. >> Rishi, congratulations on the new start-up, launching here, Zettabytes, open beta, five more spots left. Check 'em out, Zettabytes, if you're doing hybrid cloud or true private cloud, they have five spots available. It's The Cube, bringing all the action, the start-up action here and also the conversations at re:Invent. I'm John Furrier, Justin Warren. We're back with more after this short break. (electronic jingle)