 Live from Las Vegas, it's theCUBE, covering AWS re-invent 2017, presented by AWS, Intel, and our ecosystem of partners. Hey, welcome back everyone. Live here in Las Vegas, theCUBE is covering exclusively the AWS re-invent. Got two sets, this is set one, set two behind me. We're here in a startup called ZetaBytes, Rishi Yadav, CUBE alumni CEO, and suit here, Jen Gerr, CTO, hot new startup, ZetaBytes. Normally you're entrepreneurial, your other company's still going, InfoObjects. Welcome back. Thanks for having us here. I don't know, it's the seventh time, it's time. I mean, we love CUBE guys. Yeah, so InfoObjects is the mother ship and doing really, really great. And today we are launching ZetaBytes, which is our hybrid cloud integration platform. We are starting with AWS and then it's going to have integration for other clouds. So startups are impacted, and then we were talking yesterday about kind of a demarcation line between 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 date, your newborn startup, you get the cloud as a resource and 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 hyperscale 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 adoption, John, you have been following the big data journey from I think the cloud era basement days, right? So in 2014, it got enterprise adoption and the things like security and governance which were of not much concern earlier, they became a front and center. Another thing which happened was that around 2014, 2015 timeframe, the public cloud, which for eight, nine years, essentially AWS, that was about SMBs, startups, about saving money for them, right? That also started getting adoption in the enterprise. And when you're talking about enterprise, there you cannot tell them that, you know, if you deploy 10 servers on AWS, it's going to save you $200,000. They would say we already have $500 million spent. We have these huge data centers. So they needed some more value than that. But... Talk about your company, Zeta Bytes. 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 Zeta Bytes 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 the big data lake. And he talked about it a lot today, right? S3 being 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 Hadoop and other services around it? And then you do lift and shift to AWS and then you transform to PaaS. So you spend one and a half, two years in doing Hadoop. Then you spend another one and a half, two years doing the PaaS, the cloud-native transformation, or is there a better way? And then we realized 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 the AWS, they want on-prem. Now that includes the cloud-native APIs, but also the agility and everything else. Okay, so let me ask, should hear a question. So you're the CTO. I know you're technical too, so I'll 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 and 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 want to have to write code, ship it to a server, put it to the cloud. They just want instant integration to Amazon. Is that what you're doing? Is that something? Get it right, because that seems what I think you're doing. Yeah, so Zeta provides that seamless experience. So you have the same set of APIs which you normally would do on AWS. So you still use the same AWS SDK. You still use the same as the AWS CLI. Use all the AWS APIs. We have upset out those APIs on this platform. Build your code base based on those APIs. Now, using Kubernetes, you decide where this workload will go. Okay, so one of the challenges with AWS though is that they release services like constantly. I think we had the announcement at the keynote today. It's like another hundred or so services that they're releasing. So how do you choose which ones do you support? All of them or do you focus on specific ones? First, we are focusing on a few specific ones which are mostly being used. We are starting with, for example, S3, Lambda, Kinesis, Kafka, and Spark and SDFS are there from day one also. Right, okay. Then all of these are what we are doing. Today, if you see the announcement, they have launched Kubernetes now, the Container Management Service. We have that flexibility from day one only. So we have that in our appliance. And using that, even, for example, your workload says some of the pieces should run on the, let's say, on-prem appliance, some of the pieces should go to the cloud. That is also possible. Okay, so you're selling an appliance. Yeah, yeah, one Minion, let's say Kubernetes Minion might run on the AWS. Few of the Minions might run on your appliance. You can easily access, do all the control management. It's a business model. They pay for the box or is it a service? Oh, they get the box as part of a service. What's the business model? So we do both. So it's a software platform as well as an appliance. So the beauty of appliance is that everything is already optimized for you, right? So that makes it very easy. But if a customer has a chosen hardware platform, we can definitely deploy it on that also. And adding to the 100 services thing, and I think that's a great point, that AWS has so many services now that can you really go and figure out which service is most optimized for your needs. That's where you need a partner on-prem side, right, and that's what we are going to be. And another thing, as Sudhir mentioned, the EKS, which they announced today, the Kubernetes. So you have Kubernetes on-prem, AWS is supporting Kubernetes, and we are also supporting Kubernetes. So if you want to work your workloads at that level, it's completely seamless. And you were saying before that your target is enterprises, so the appliance delivery model and the simplicity of being able to manage a lot of different services, I mean, clearly, being able to manage things at scale is something that enterprises are crying out for because otherwise I have to, AWS is great if you want to hand-build everything yourself. It has all of these 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're actually providing the leverage to get enterprise humans to be able to manage AWS. Is that a fake 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 region or another, IoT workloads by definition cannot be on AWS. Low latency workloads, that they cannot be on AWS. In the same way, the workloads in which you need some extra level of security. So within your data center, as much as we 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 100 services? Yes, but the local execution, we are only going to provide for some services, which by their very nature, make more sense to run on-prem. Yeah, the core services. Core services. All right, so how do you guys going to sell this product? Take us through the startup situation. You're here, are you talking to customers? Why are they by 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 who are coming to us, they are interested in how I can seamlessly transform this. What's an example workload? An example workload. The example workload for us is going to be the big data workloads, which we have specialized in for last so many years, right? So one of them can be IoT, so you probably can explain more about that. Yeah, so the other example could be, for example, from today's keynote, if you see Expedia case, or like Goldman Sachs case, they spent a lot of time in converting their code to the AWS specific code, right? Millions of lines or billions of lines of code. What we are doing today, if you're developing your application, tomorrow it could be future ready for AWS. Okay. That's your convenience. We are actually merging your experience with AWS. Right. So it's making it easier for enterprise to make that transition from what they're doing today across to cloud. That's a big deal for them. Tomorrow when you're like, say, ready to go to AWS, you choose, your data will decide whether you want to run your workload on our clients or AWS. Okay. So your market is hybrid cloud basically? Yeah. Anyone doing hybrid cloud should talk to you guys. Yeah, and code would be future proof what you're developing today. All right, so is the product shipping? Okay. 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. Yeah. So beta now? Yeah, yes. You guys are already ready? Early access. Open beta or 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 add five more customers in the next two months for the beta. So. I'll take a minute to explain the type of customer you're looking for. Are they all filled spots anymore? You have five more spots, you said? Yeah, we have five more spots for the beta. Who are you looking for? I didn't know. Any large enterprise which is planning to move to AWS but start struggling with all the integrities, looking at the hundred services and how do you integrate your existing applications there? So how do you take those baby steps? So we are going to not just take the baby steps but sprint through it. So that's what our Zeta Bytes plans is for. Rishi, congratulations on the new startup. Launching here, Zeta Bytes open beta. Five more spots left. Check them out. If you're doing hybrid cloud or true private cloud, they have five more spots available. It's theCUBE bringing all the action, startup action here and also the conversations that reinvent. I'm John Furrier, Justin Warren. We'll be back with more after this short break.