>>Live from Denver, Colorado. It's the cube covering com vault go 2019 brought to you by Combolt. >>Hey, welcome back to the cube at Lisa Martin with Steve men and men and we are coming to you alive from combo go 19 please to welcome to the cube, a gent from Microsoft Azure. We've got Ben call principal program manager. Ben, welcome. Thank you. Thanks for having me on. Thanks for coming on. So Microsoft combo, what's going on with the partnership? >>They wouldn't have have great storage pond is in data management space. We've been working with Convult for 20 years now in Microsoft and and they've been working with us on Azure for that as long as I can remember not being on that the Azure business for about seven years now. So just a long time in cloud terms like dog ears and it's sort of, they've been doing a huge amount there around getting customer data into the cloud, reducing costs, getting more resiliency and then also letting them do more with the data. So they're a pretty good partner to have and they make it much easy for their customers to to go and leverage cloud. >> So Ben, you know, in my career I've had lots of interactions with the Microsoft storage team. Things have changed a little bit when you're now talking about Azure compared to more, it was the interaction with the operating system or the business suite at had. >>So maybe bring us up to date as those people that might not have followed where kind of the storage positioning inside of Microsoft is now that when we talk about Azure and your title. Yeah, we, we sort of can just, just briefly, we worked very heavily with our own premises brethren, they are actually inside the O team is inside of the Azure engineering old male, which is kind of funny, but we do a load of things there. If he started looking at, firstly on that, that hybrid side, we have things like Azure files. It's a highly resilient as a service SMB NFS file Shafter a hundred terabytes, but that interacts directly with windows server to give you Azure file sync. So there is sort of synergies there as well. What I'm doing personally, my team, we work on scale storage. The big thing we have in there is owl is out blood storage technology, which really is the underpinning technology fault. >>Preapproval storage and Azure, which is an including our SAS offerings, which are hosted on Azure too. So disc is on blood storage of files on blood storage. You look at Xbox live, all these kind of stuff is a customer to us. So we build that out and we were doing work there and that's, that's really, really interesting. And how we do it. And that's not looking at going, we're gonna buy some compute, we're going to buy some storage, we're going to build it out, we're going to run windows or hyper V or maybe VM-ware with hoc with windows running on the VMware, whatever else. This is more a story about we're gonna provide you storage as a service. You didn't get a minimum of like 11 nines at your ability. And and be able to have that scale to petabytes of capacity in one logical namespace and give you multiple gigabytes, double digit gigabytes of throughput to that storage. >>And now we're even that about to multiple protocols. So rest API century. Today we've got Azure stack storage, EU API, she can go and use, but we give you that consistency of the actual backend storage and the objects and the data available via more than just one protocol. You can go and access that via HDFS API. We talk about data lakes all the time. For us, our blood storage is a data Lake. We turn on hierarchal namespace and you can go and access that via other protocols like as I mentioned HDFS as well. So that is a big story about what we want to do. We want to make that data available at crazy scale, have no limits in the end to the capacity or throughput or performance and over any protocol. That's kind of our lawn on the Hill about what we want to get to. >>And we've been talking to the Combolt team about some of the solutions that they are putting in the cloud. The new offering metallic that came out. They said if my customer has Azure storage or storage from that other cloud provider, you could just go ahead and use that. Maybe how familiar and how much I know you've been having about run metallic. >> We were working, we work pretty tightly with the product team over Convolt around this and my team as well around how do we design and how do we make it work the best and we're going to continue working to optimize as they get to beyond initial launch to go, wow, we've got data sets we we can analyze. We knew how to, we wanted out of tune it. Now really we love the solution particularly more because you know the default if you don't select the storage type where you want to go, you will run on Azure. >>So really sort of be cued off to the relationship there. They chose us as a first place we'll go to, but they've also done the choice for customers. So some customers may want to take it to another cloud. That's fine. It's reasonable. I mean we totally understand it's going to be a multicloud world and that's a reality for any large company. Our goal is to make sure we're growing faster than the competitors, not to knock out the competitors altogether because that just won't happen. So they've got that ability to go and, yeah, Hey, we'll use Azure as default because they feel we're offering the best support and the best solution there. But then if they have that customer, same customer wants to turn around and use a competitor of ours, fine as well. And I see people talking about that today where they may want to mitigate risks and say, I'm going to do, I'm doing off office three, six five on a, taken off this three 65 backup. It's cool. You use metallic, it'll take it maybe to a different region in Asia and they're backing up. They still going, well, I'm still all in on Microsoft. They may want to take it to another cloud or even take it back to on premise. So that does happen too because just in case of that moment we can get that data back in a different location. Something >>so metallic talking about that is this new venture is right. It's a Convolt venture and saw that the other day and thought that's interesting. So we dug into it a little bit yesterday and it's like a startup operating within a 20 year old company, which is very interesting. Not just from an incumbent customer perspective, but an incumbent partner perspective. How have you seen over the last few years and particularly bad in the last nine months with big leadership and GTM changes for condo? How has the partnership with Microsoft evolved as a result of those changes? >>Um, it's always been interesting. I guess when you start looking at adventure and everything seems to, things change a little bit. Priorities may change just to be fair, but we've had that tight relationship for a long time and a relationship level and an exec leadership level, nothing's really changed. But in the way they're building this platform, we, we sit down out of my team at the Azure engineering group and we'll sit down and do things like ideations. Like here's where we see gaps in the markets, here's what we believe could happen. And look back in July, we had inspire, which is our partner conference in Las Vegas and we sat down with their OT, our OT in a room, we'll talking about these kinds of things. And this is I think about two months after they may have started the initial development metallic from what I understand, but we're talking about exactly what they're doing with metallic offered as a service in Azure as, Hey, how about we do this? So we think it's really cool. It opens up a new market to convert I think too. I mean they're so strong in the enterprise, but they don't do much in the smaller businesses because with the full feature product, it also has inherent complexibility complexity around it. So by doing metallic, is it click, click, next done thing. They really opening I think new markets to them and also to us as a partner. >>I was going to add, you know, kind of click on that because they developed this very quickly. This is something that I think what student were here yesterday, metallic was kind of conceived, designed, built in about six months. So in terms of like acceleration, that's kind of a new area for Combolt. >>Yeah, and I think, I think they're really embracing the fact about let's release our code in production for, for products which are sort of getting the, getting to the, Hey, the product is at the viable stage now, not minimum viable, viable, let's release in production, let's find out how customers are using it and then let's keep optimizing and doing that constant iteration, taking that dev ops approach to let's get it out there, let's get it launched, and then let's do these small batches of changes based on customer need, based on tele telemetry. We can actually get in. We can't get the telemetry without having customers. So that's how it's going to keep working. So I think this initial product we see today, it's just going to keep evolving and improving as they get more data, as they get more information, more feedback, which is exactly what we want to see. >>Well, what will come to the cloud air or something you've been living in for a number of years. Ben, I'd love to hear you've been meeting with customers, they've been asking you questions, gives us some of the, you know, some of the things that, what's top of mind for some of the customers? What kinds of things did they come into Microsoft, Dawn, and how's that all fit together? >>There's many different conferences of interrelate, many different conversations and there'll be, we'll go from talking about, you know, Python machine learning or AI fits in PowerPoint. >>Yeah. >>It's a things like, you know, when are we gonna do incremental snapshots from the manage disks, get into the weeds on very infrastructure centric stuff. We're seeing range of conversations there. The big thing I think I see, keep seeing people call out and make assumptions of is that they're not going to be relevant because cloud, I don't know cloud yet. I don't know this whole coup cube thing, containers, I don't really understand that as well as I think I need to. And an AI, Oh my gosh, what do we even do there? Cause everyone's throwing the words and terms around. But to be honest, I think would still really evident is cloud is still is tiny fraction of enterprise workloads. So let's be honest, it's growing at a huge rate because it is that small fraction. So again, there's plenty of time for people to learn but they shouldn't go and try. >>And so it's not like you go and learn everything in the technology stack from networking to development to database management to, to running a data set of power and cooling. You learn the things that are applicable to what you're trying to do. And the same thing goes to cloud. Any of these technologies go and look at what you need to build for your business. Take it that step and then go and find out the details and levels you want to know. And as someone who's been on Azure for, like I said, almost seven years, which is crazy long. That was, that was literally like being in a startup instead of Microsoft when I joined and I wasn't sure if I wanted to join a licensing company. It's been very evident to me. I will not say I'm an Azure expert and I've been seven years in the platform. >>There are too many things for for me to be an expert in everything on, and I think people sort of just have to realize that anyone's saying that it's bravado. Nothing else. Oh, people. The goal is Microsoft as a platform provider. Hopefully you've got the software and the solution does make a lot of this easier for the customer, so hopefully they shouldn't need to become a Coobernetti's expert because it's baked into your platform. They shouldn't have to worry about some of these offerings because it's SAS. Most customers are there. Some things you need to learn between going from exchange to go into Oh three 65 absolutely. There's some nuances and things like that, but once you get over that initial hurdle, it should be a little easier. I think it's right and I think going back to that, sort of going back to bear principles going, what is the highest level of distraction that's viable for your business or that application or this workload has to always be done with everything. If it's like, well, class, not even viable, running on premises, don't, don't need to apologize for not running in cloud. If I as this, what's happening for you because of security, because of application architecture, run it that way. Don't feel the need and the pressure to have to push it that way. I think too many people get caught up in this shiny stuff up here, which is what you know 1% of people are doing versus the other 99% which is still happening in a lot of the areas we work and have challenges in today. >>That's a great point that you bring up because there is all the buzz words, right? AI, machine learning cloud. You've got to be cloud ready. You've got to be data-driven to customer. To your point going, I just need to make sure that what we have set up for our business is going to allow our business one to remain relevant, but to also be able to harness the power of the data that they have to extract new opportunities, new insights, and not get caught up with, shoot, should we be using automation? Should we be using AI? Everybody's talking about it. I liked that you brought up and I find it very respectfully, he said, Hey, I'm not an Azure expert. You'd been there seven, seven dog years like you said. And I think that's what customers probably gained confidence in is hearing the folks like you that they look to for that guidance and that leadership saying, no, I don't know everything to know. But giving them the confidence that their tribe, they're trusting you with that data and also helping look, trusting you to help them make the right decisions for their business. >>Yeah, and that's, we've got to do that. I mean, I as a tech guy, it's like I've, I've loved seeing the changes. When I joined Microsoft, I, I wasn't lying. I was almost there go enough. I really want to join this company. I was going to go join a startup instead and I got asked to one stage in an interview going, why do you want to join Microsoft? We see you've never applied to, I'd never wanted to. A friend told me to come in and it's just been amazing to see those changes and I'm pretty proud on that. So when we talk about those things we're doing, I mean, I think there is no shame going, I'm just going to lift and shift machines because cloud's about flexibility. If you're doing it just on cost, probably doing it for the wrong reason. It's about that flexibility to go and do something. >>Then change within months and slowly make steps to make things better and better as you find a need as you find the ability, whatever it may be. And some of the big things that we focus on right now with customers is we've got a product called Azure advisor. It'll go until people, when one, you don't build things in a resilient manner. Hey, do you know this has not ha because of this and you can do this. It's like, great. We'll also will tell you about security vulnerabilities that maybe should a gateway here for security. Maybe you should do this or this is not patched. But the big thing of that, it also goes and tells you, Hey, you're overspending. You don't need this much. It provisions, you provision like a Ferrari, you need a, you just need a Prius. Go and run a Prius because it's going to do what you need. >>I need a paler list and that's part of that trusted suit. Getting that understanding, and it's counterintuitive, but we're now like, it's coming out of mozzarella too, which is great. But seeing these guys were dropping contracts and licenses and basically, you know, once every three years I may call the customer, Hey, how about renewal? Now, go from that to now being focused on the customer's actual success. I've focused on their growth in Azure as a platform. Our services growth, like utilization not in sales has been a huge change. It scared some people away, but it's brought a lot more people in and and that sort of counterintuitive spend less money thing actually leads in the longterm to people using more. >>Absolutely. That's definitely not the shrink wrap software company of Microsoft that I remember from the 90s yeah. might be similar to, you know, just as to get Convolt to 2019 is not the same combo that many of us know from 15 years ago. A good >>mutual friend of ours, sort of Simon and myself before I took this job, he and I sat down, we're having a beer and discussing the merits, all not Yvette go to things like that. Same with Convolt there. They're changing such such a great deal with, you know, what they're putting in the cloud, what they're doing with the data, where they're trying to achieve with things like for data management across on premises and cloud with microservices applications and stuff going, Hey, this won't work like this anymore. When you now are doing it on premises and with containers, it's pretty good to see. I'm interested to see how they take that even further to their current audience, which is product predominantly. You know the it pro, the data center admin, storage manager. >>It's funny when you talked about just the choice that customers have and those saying, aye, we shouldn't be following the trends because they're the trends. We actually interviewed a couple of hours ago, one of customers that is all on prime healthcare company and said, he's like, I want to make a sticker that says no cloud and proud and it just what there was, we don't normally hear from them. We always talk about cloud, but for a company to sit down and look at what's best for our business, whether it's, you know, FedRAMP certification challenges or HIPAA or GDPR, other compelling requirements to keep it on prem, it was just refreshing to hear this customer say, >>yeah, I mean it's just appropriate for them. You do what's right for you. I, yeah, it's no shame in any of it. It's, I mean you don't, you definitely don't get fans by it by shaming people about not doing something right. And I mean I've, I'm personally very happy to fee fee, you know, see sort of hype around things like blockchain die down a little bit. So it's a slow database and we should use it for this specific case of that shared ledger. You know, things like that where people don't have to know blockchain. Now I have to know IOT. It's like, yeah, and that hype gets people there, but it also causes a lot of anxiety and it's good to see someone actually not be ashamed of it. And they agree the ones when they do take a step and use cloud citizen may be in the business already, they're probably going to do it appropriately because have a reason, not just because we think this would be cool, right? >>Well not. And how much inherit and complexity does that bring in if somebody is really feeling pressured to follow those trends. And maybe that's when you end up with this hodgepodge of technologies that don't work well together. You're spending way more in as as business it folks are consumers, you know, consumers in their personal lives, they expect things to be accessible, visible, but also cost efficient because they have so much choice. >>Yeah, the choice choice is hard. It's just a, just the conversation I was having recently, for example, just we'll take the storage cause of where we are, right? It's like I'm running something on Azure, I'm a, I'm using Souza, I want an NFS Mount point, which is available to me in Fs. Great, perfect. what do I use as like, well you can use any one of these seven options like that, but what's the right choice? And that's the thing about being a platform can be, we give you a lot of choices, but it's still up to you or up to app hotness. It can really help the customers as well to make the most appropriate choice. And, and I, I pushed back really hard in terms of best practices and things. I hate it because again, it's making the assumption this is the best thing to do. >>It's not. It's always about, you know, what are the patterns that have worked for other people? What are the anti-patterns and what's the appropriate path for me to take? And that's actually how we're building our docs now too. So we, we keep, we keep focusing on our Azure technology and we're bringing out some of the biggest things we've done is how we manage our documentation. It's all open sourced, it's all in markdown on get hub. So you can go in and read a document from someone like myself is doing product management going, this is how to use this product and you're actually, this bit's wrong, this bit needs to be like this and you can go in yourself even now, make a change and we can go, Oh yeah and take that committed in and dual this kind of stuff in that way. So we're constantly taking those documents in that way and getting realtime feedback from customers who are using it, not just ourself in an echo chamber. >>So you get this great insight and visibility that you never had before. Well, Ben, thank you, Georgie stew and me on the queue this afternoon. Excited to hear what's coming up next for Azure. Makes appreciate your time. Thank you for steam and event. I, Lisa Martin, you're watching the cue from Convault go 19.

>> from our studios in the heart of Silicon Valley, Palo Alto, California It is a cute conversation. >> Welcome to this Cube conversation here in Palo Alto, California. At the Cube Studios. I'm John for a host of the Cube. We're here for a company profile coming called De Monte. Here. Tom Barton, CEO. As V M World approaches a lot of stuff is going to be talked about kubernetes applications. Micro Service's will be the top conversation, Certainly in the underlying infrastructure to power that Tom Barton is the CEO of De Monte, which is in that business. Tom, we've known each other for a few years. You've done a lot of great successful ventures. Thehe Monty's new one. Your got on your plate here right now? >> Yes, sir. And I'm happy to be here, so I've been with the Amante GIs for about a year or so. Um, I found out about the company through a head turner. Andi, I have to admit I had not heard of the company before. Um, but I was a huge believer in containers and kubernetes. So has already sold on that. And so I had a friend of mine. His name is Brian Walden. He had done some massive kubernetes cloud based deployments for us at Planet Labs, a company that I was out for a little over three years. So I had him do technical due diligence. Brian was also the number three guy, a core OS, um, and so deeply steeped in all of the core technologies around kubernetes, including things like that CD and other elements of the technology. So he looked at it, came back and gave me two thumbs up. Um, he liked it so much that I then hired him. So he is now our VP of product management. And the the cool thing about the Amanti is essentially were a purpose built solution for running container based workloads in kubernetes on premises and then hooking that in with the cloud. So we believe that's very much gonna be a hybrid cloud world where for the major corporations that we serve Fortune 500 companies like banks like energy and utilities and so forth Ah, lot of their workload will maintain and be maintained on premises. They still want to be cloud compatible. So you need a purpose built platform to sort of manage both environments >> Yeah, we certainly you guys have compelling on radar, but I was really curious to see when you came in and took over at the helm of the CEO. Because your entrepreneurial career really has been unique. You're unique. Executive. Both lost their lands. And as an operator you have an open source and software background. And also you have to come very successful companies and exits there as well as in the hardware side with trackable you took. That company went public. So you got me. It's a unique and open source software, open source and large hardware. Large data center departments at scale, which is essentially the hybrid cloud market right now. So you kind of got the unique. You have seen the view from all the different sides, and I think now more than ever, with Public Cloud certainly being validated. Everyone knows Amazon of your greenfield. You started the cloud, but the reality is hybrid. Cloud is the operating model of the genesis. Next generation of companies drive for the next 20 to 30 years, and this is the biggest conversation. The most important story in tech. You're in the middle of it with a hot start up with a name that probably no one's ever heard of, >> right? We hope to change that. >> Wassily. Why did you join this company? What got your attention? What was the key thing once you dug in there? What was the secret sauce was what Got your attention? Yes. So to >> me again, the market environment. I'm a huge believer that if you look at the history of the last 15 years, we went from an environment that was 0% virtualized too. 95% virtualized with, you know, Vienna based technologies from VM Wear and others. I think that fundamentally, containers in kubernetes are equally as important. They're going to be equally as transformative going forward and how people manage their workloads both on premises and in the clouds. Right? And the fact that all three public cloud providers have anointed kubernetes as the way of the future and the doctor image format and run time as the wave of the future means, you know, good things were gonna happen there. What I thought was unique about the company was for the first time, you know, surprisingly, none of the exit is sick. Senders, um, in companies like Nutanix that have hyper converse solutions. They really didn't have anything that was purpose built for native container support. And so the founders all came from Cisco UCS. They had a lot of familiarity with the underpinnings of hyper converged architectures in the X 86 server landscape and networking, subsistence and storage subsystems. But they wanted to build it using the latest technologies, things like envy and me based Flash. Um, and they wanted to do it with a software stack that was native containers in Kubernetes. And today we support two flavors of that one that's fully open source around upstream kubernetes in another that supports our partner Red hat with open shift. >> I think you're really onto something pretty big here because one of things that day Volonte and Mine's too many men and our team had been looking at is we're calling a cloud to point over the lack of a better word kind of riff on the Web to point out concept. But cloud one daughter was Amazon. Okay, Dev ops agile, Great. Check the box. They move on with life. It's always a great resource, is never gonna stop. But cloud 2.0, is about networking. It's about securities but data. And if you look at all the innovation startups, we'll have one characteristic. They're all playing in this hyper converged hardware meat software stack with data and agility, kind of to make the original Dev ops monocle better. The one daughter which was storage and compute, which were virtualization planes. So So you're seeing that pattern and it's wide ranging at security is data everything else So So that's kind of what we call the Cloud two point game. So if you look at V m World, you look at what's going on the conversations around micro service red. It's an application centric conversation in an infrastructure show. So do you see that same vision? And if so, how do you guys see you enabling the customer at this saying, Hey, you know what? I have all this legacy. I got full scale data centers. I need to go full scale cloud and I need zero and disruption to my developer. Yeah, so >> this is the beauty of containers and kubernetes, which is they know it'll run on the premises they know will run in the cloud, right? Um and it's it is all about micro service is so whether they're trying to adopt them on our database, something like manga TB or Maria de B or Crunchy Post Grey's, whether it's on the operational side to enable sort of more frequent and incremental change, or whether it's on a developer side to take advantage of new ways of developing and delivering APS with C I. C. D. Tools and so forth. It's pretty much what people want to do because it's future proofing your software development effort, right? So there's sort of two streams of demand. One is re factoring legacy applications that are insufficiently kind of granule, arised on, behave and fail in a monolithic way. Um, as well as trying to adopt modern, modern, cloud based native, you know, solutions for things like databases, right? And so that the good news is that customers don't have to re factor everything. There are logical break points in their applications stack where they can say, Okay, maybe I don't have the time and energy and resource is too totally re factor a legacy consumer banking application. But at least I can re factor the data based here and serve up you know container in Kubernetes based service is, as Micro Service's database is, a service to be consumed by. >> They don't need to show the old to bring in the new right. It's used containers in our orchestration, Layla Kubernetes, and still be positioned for whether it's service measures or other things. Floor That piece of the shirt and everything else could run, as is >> right, and there are multiple deployments scenarios. Four containers. You can run containers, bare metal. Most of our customers choose to do that. You can also run containers on top of virtual machines, and you can actually run virtual machines on top of containers. So one of our major media customers actually run Splunk on top of K B M on top of containers. So there's a lot of different deployment scenarios. And really, a lot of the genius of our architecture was to make it easy for people that are coming from traditional virtualized environments to remap system. Resource is from the bm toe to a container at a native level or through Vienna. >> You mentioned the history lesson there around virtualization. How 15 years ago there was no virtualization now, but everything's virtualized we agree with you that containers and compares what is gonna change that game for the next 15 years? But what's it about VM? Where would made them successful was they could add virtualization without requiring code modification, right? And they did it kind of under the covers. And that's a concern Customs have. I have developers out there. They're building stacks. The building code. I got preexisting legacy. They don't really want to change their code, right? Do you guys fit into that narrative? >> We d'oh, right, So every customer makes their own choice about something like that. At the end of the day, I mentioned Splunk. So at the time that we supported this media customer on Splunk, Splunk had not yet provided a container based version for their application. Now they do have that, but at the time they supported K B M, but not native containers and so unmodified Splunk unmodified application. We took them from a batch job that ran for 23 hours down the one hour based on accelerating and on our perfect converged appliance and running unmodified code on unmodified K B m on our gear. Right, So some customers will choose to do that. But there are also other customers, particularly at scale for transaction the intensive applications like databases and messaging and analytics, where they say, You know, we could we could preserve our legacy virtualized infrastructure. But let's try it as a pair a metal container approach. And they they discovered that there's actually some savings from both a business standpoint and a technology tax standpoint or an overhead standpoint. And so, as I mentioned most of our customers, actually really. Deficiencies >> in the match is a great example sticking to the product technology differentiate. What's the big secret sauce describe the product? Why are you winning in accounts? What's the lift in your business right now? You guys were getting some traction from what I'm hearing. Yeah, >> sure. So look at the at the highest level of value Proposition is simplicity. There is no other purpose built, you know, complete hardware software stack that delivers coup bernetti coproduction kubernetes environment up and running in 15 minutes. Right. The X 86 server guys don't really have it. Nutanix doesn't really have it. The software companies that are active in this space don't really have it. So everything that you need that? The hardware platform, the storage infrastructure, the actual distribution of the operating system sent the West, for example. We distribute we actually distributed kubernetes distribution upstream and unmodified. And then, very importantly, in the combinations landscape, you have to have a storage subsystem in a networking subsystem using something called C s I container storage interface in C N I. Container networking interface. So we've got that full stack solution. No one else has that. The second thing is the performance. So we do a certain amount of hardware offload. Um, and I would say, Amazons purchase of Annapurna so Amazon about a company called Annapurna its basis of their nitro technology and its little known. But the reality is more than 50% of all new instances at E. C to our hardware assisted with the technology that they thought were offloaded. Yeah, exactly. So we actually offload storage and network processing via to P C I. D cards that can go into any industry server. Right? So today we ship on until whites, >> your hyper converge containers >> were African verge containers. Yeah, exactly. >> So you're selling a box. We sell a box with software that's the >> with software. But increasingly, our customers are asking us to unbundle it. So not dissimilar from the sort of journey that Nutanix went through. If a customer wants to buy and l will support Del customer wants to buy a Lenovo will support Lenovo and we'll just sell >> it. Or have you unbundled? Yetta, you're on bundling. >> We are actively taking orders for on bundling at the present time in this quarter, we have validated Del and Lenovo as alternate platforms, toothy intel >> and subscription revenue. On that, we >> do not yet. But that's the golden mask >> Titanic struggle with. So, yeah, and then they had to take their medicine. >> They did. But, you know, they had to do that as a public company. We're still a private company, so we can do that outside the limelight of the public >> markets. So, um, I'm expecting that you guys gonna get pretty much, um I won't say picked off, but certainly I think your doors are gonna be knocked on by the big guys. Certainly. Delic Deli and see, for instance, I think it's dirty. And you said yes. You're doing business with del name. See, >> um, we are doing as a channel partner and as an OM partner with them at the present time there, I wouldn't call them a customer. >> How do you look at V M were actually there in the V M, where business impact Gelsinger's on the record. It'll be on the Cube, he said. You know Cu Bernays the dial tone of the Internet, they're investing their doubling down on it. They bought Hep D O for half a billion dollars. They're big and cloud native. We expect to see a V M World tons of cloud Native conversation. Yes, good, bad for you. What's the take? The way >> legitimizes what we're doing right? And so obviously, VM, where is a large and successful company? That kind of, you know, legacy and presence in the data center isn't gonna go anywhere overnight. There's a huge set of tooling an infrastructure that bm where has developed in offers to their customers. But that said, I think they've recognized in their acquisition of Hep Theo is is indicative of the fact that they know that the world's moving this way. I think that at the end of the day, it's gonna be up to the customer right. The customer is going to say, Do I want to run containers inside? Of'em? Do I want to run on bare metal? Um, but importantly, I think because of, you know, the impact of the cloud providers in particular. If you think of the lingua franca of cloud Native, it's gonna be around Dr Image format. It's gonna be around kubernetes. It's not necessarily gonna be around V M, d K and BMX and E s X right. So these are all very good technologies, but I think increasingly, you know, the open standard and open source community >> people kubernetes on switches directly is no. No need, Right. Have anything else there? So I gotta ask you on the customer equation. You mentioned you, you get so you're taking orders. How you guys doing business today? Where you guys winning, given example of of why people while you're winning And then for anyone watching, how would they know if they should be a customer of yours? What's is there like? Is there any smoke signs and signals? Inside the enterprise? They mentioned batch to one hour. That's just music. Just a lot of financial service is used, for instance, you know they have timetables, and whether they're pulling back ups back are doing all the kinds of things. Timing's critical. What's the profile customer? Why would someone call you? What's the situation? The >> profile is heavy duty production requirements to run in both the developer context and an operating contact container in kubernetes based workloads on premises. They're compatible with the cloud right so increasingly are controlled. Plane makes it easy to manage workloads not just on premises but also back and forth to the public cloud. So I would argue that essentially all Fortune 500 companies Global 1000 companies are all wrestling with what's the right way to implement industry standard X 86 based hardware on site that supports containers and kubernetes in his cloud compatible Right? So that that is the number one question then, >> so I can buy a box and or software put it on my data center. Yes, and then have that operate with Amazon? Absolutely. Or Google, >> which is the beauty of the kubernetes standards, right? As long as you are kubernetes certified, which we are, you can develop and run any workload on our gear on the cloud on anyone else that's carbonated certified, etcetera. So you know that there isn't >> given example the workload that would be indicative. >> So Well, I'll cite one customer, Right. So, um, the reason that I feel confident actually saying the name is that they actually sort of went public with us at the recent Gardner conference a week or so ago when the customer is Duke Energy. So very typical trajectory of journey for a customer like this, which is? A couple years ago, they decided that they wanted re factor some legacy applications to make them more resilient to things like hurricanes and weather events and spikes in demand that are associated with that. And so they said, What's the right thing to do? And immediately they pick containers and kubernetes. And then he went out and they looked at five different vendors, and we were the only vendor that got their POC up and running in the required time frame and hit all five use case scenarios that they wanted to do right. So they ended up a re factoring core applications for how they manage power outages using containers and kubernetes, >> a real production were real. Production were developing standout, absolutely in a sandbox, pushing into production, working Absolutely. So you sounds like you guys were positioned to handle any workload. >> We can handle any workload, but I would say that where we shine is things that transaction the intensive because we have the hardware assist in the I o off load for the storage and the networking. You know, the most demanding applications, things like databases, things like analytics, things like messaging, Kafka and so forth are where we're really gonna >> large flow data, absolutely transactional data. >> We have customers that are doing simpler things like C I. C D. Which at the end of the day involves compiling things right and in managing code bases. But so we certainly have customers in less performance intensive applications, but where nobody can really touch us in morning. What I mean is literally sort of 10 to 30 times faster than something that Nutanix could do, for example, is just So >> you're saying you're 30 times faster Nutanix >> absolutely in trans actually intensive applications >> just when you sell a prescription not to dig into this small little bit. But does the customer get the hardware assist on that as well >> it is. To date, we've always bundled everything together. So the customers have automatically got in the heart >> of the finest on the hard on box. Yes. If I buy the software, I got a loaded on a machine. That's right. But that machine Give me the hardware. >> You will not unless you have R two p C I. D. Cards. Right? And so this is how you know we're just in the very early stages of negotiating with companies like Dell to make it easy for them to integrate her to P. C. I. D cards into their server platform. >> So the preferred flagship is the is the device. It's a think if they want the hardware sit, that they still need to software meeting at that intensive. It's right. If they don't need to have 30 times faster than Nutanix, they can just get the software >> right, right. And that will involve RCS. I plug in RCN I plug in our OS distribution are kubernetes distribution, and the control plane that manages kubernetes clusters >> has been great to get the feature on new company, um, give a quick plug for the company. What's your objectives? Were you trying to do. I'll see. Probably hiring. Get some financing, Any news, Any kind of Yeah, we share >> will be. And we will be announcing some news about financing. I'm not prepared to announce that today, but we're in very good shape with respected being funded for our growth. Um, and consequently, so we're now in growth mode. So today we're 55 people. I want to double back over the course of the next 4/4 and increasingly just sort of build out our sales force. Right? We didn't have a big enough sales force in North America. We've gotta establish a beachhead in India. We do have one large commercial banking customer in Europe right now. Um, we also have a large automotive manufacturer in a pack. But, um, you know, the total sales and marketing reach has been too low. And so a huge focus of what I'm doing now is building out our go to market model and, um, sort of 10 Xing the >> standing up, a lot of field going, going to market. How about on the biz, Dev side? I might imagine that you mentioned delicate. Imagine that there's a a large appetite for the hardware offload >> absolution? Absolutely. So something is. Deb boils down to striking partnerships with the cloud providers really on two fronts, both with respect the hardware offload and assist, but also supporting their on premises strategy. So Google, for example, is announced. Antos. This is their approach to supporting, you know, on premises, kubernetes workloads and how they interact with cool cloud. Right. As you can imagine, Microsoft and Amazon also have on premises aspirations and strategies, and we want to support those as well. This goes well beyond something like Amazon Outpost, which is really a narrow use case in point solution for certain markets. So cloud provider partnerships are very important. Exit E six server vendor partnership. They're very important. And then major, I s V. So we've announced some things with red hat. We were at the Red Hat Open summit in Boston a few months ago and announced our open ship project and product. Um, that is now G a. Also working with eyes, he's like Maria de be Mondo di B Splunk and others to >> the solid texting product team. You guys are solid. You feel good on the product. I feel very good about the product. What aboutthe skeptics are out there? Just to put the hard question to use? Man, it's crowded field. How do you gonna compete? What do you chances? How do you like your chances known? That's a very crowded field. You're going to rely on your fastballs, they say. And on the speed, what's the what's What's your thinking? Well, it's unique. >> And so part of the way or approve point that I would cite There is the channel, right? So when you go to the channel and channel is afraid that you're gonna piss off Del or E M. C or Net app or Nutanix or somebody you know, then they're not gonna promote you. But our channel partners air promoting us and talking about companies like Life Boat at the distribution level. Talking about companies like CD W S H. I, um, you know, W W t these these major North American distributors and resellers have basically said, Look, we have to put you in our line car because you're unique. There is no other purpose built >> and why that, like they get more service is around that they wrap service's around it. >> They want to kill the murder where they want to. Wrap service's around it, absolutely, and they want to do migrations from legacy environments towards Micro Service's etcetera. >> Great to have you on share the company update. Just don't get personal. If you don't mind personal perspective. You've been on the hardware side. You've seen the large scale data centers from racquetball and that experience you'll spit on the software side. Open source. What's your take on the industry right now? Because you're seeing, um, I talked a lot of sea cells around the security space and, you know, they all say, Oh, multi clouds a bunch of B s because I'm not going to split my development team between four clouds. I need to have my people building software stacks for my AP eyes, and then I go to the vendors. They support my AP eyes where you can't be a supplier. Now that's on the sea suicide. But the big mega trend is there's software stacks being built inside the premise of the enterprise. Yes, that not mean they had developers before building. You know, Kobol, lapse in the old days, mainframes to client server wraps. But now you're seeing a Renaissance of developers building a stack for the domain specific applications that they need. I think that requires that they have to run on premise hyper scale like environment. What's your take on it >> might take is it's absolutely right. There is more software based innovation going on, so customers are deciding to write their own software in areas where they could differentiate right. They're not gonna do it in areas that they could get commodities solutions from a sass standpoint or from other kinds of on Prem standpoint. But increasingly they are doing software development, but they're all 99% of the time now. They're choosing doctor and containers and kubernetes as the way in which they're going to do that, because it will run either on Prem or in the Cloud. I do think that multi cloud management or a multi multi cloud is not a reality. Are our primary modality that we see our customers chooses tons of on premises? Resource is, that's gonna continue for the foreseeable future one preferred cloud provider, because it's simply too difficult to to do more than one. But at the same time they want an environment that will not allow themselves to be locked into that cloud bender. Right? So they want a potentially experiment with the second public cloud provider, or just make sure that they adhere to standards like kubernetes that are universally shared so that they can't be held hostage. But in practice, people don't. >> Or if they do have a militant side, it might be applications. Like if you're running office 3 65 right, That's Microsoft. It >> could be Yes, exactly. On one >> particular domain specific cloud, but not core cloud. Have a backup use kubernetes as the bridge. Right that you see that. Do you see that? I mean, I would agree with by the way we agreed to you on that. But the question we always ask is, we think you Bernays is gonna be that interoperability layer the way T c p I. P was with an I p Networks where you had this interoperability model. We think that there will be a future state of some point us where I could connect to Google and use that Microsoft and use Amazon. That's right together, but not >> this right. And so nobody's really doing that today, But I believe and we believe that there is, ah, a future world where a vendor neutral vendor, neutral with respect to public cloud providers, can can offer a hybrid cloud control plane that manages and brokers workloads for both production, as well as data protection and disaster recovery across any arbitrary cloud vendor that you want to use. Um, and so it's got to be an independent third party. So you know you're never going to trust Amazon to broker a workload to Google. You're never going to trust Google to broker a workload of Microsoft. So it's not gonna be one of the big three. And if you look at who could it be? It could be VM where pivotal. Now it's getting interesting. Appertaining. Cisco's got an interesting opportunity. Red hats got an interesting opportunity, but there is actually, you know, it's less than the number of companies could be counted on one hand that have the technical capability to develop hybrid cloud abstraction that that spans both on premises and all three. And >> it's super early. Had to peg the inning on this one first inning, obviously first inning really early. >> Yeah, we like our odds, though, because the disruption, the fundamental disruption here is containers and kubernetes and the interest that they're generating and the desire on the part of customers to go to micro service is so a ton of application re factoring in a ton of cloud native application development is going on. And so, you know, with that kind of disruption, you could say >> you're targeting opening application re factoring that needs to run on a cloud operating >> model on premise in public. That's correct. In a sense, dont really brings the cloud to theon premises environment, right? So, for example, we're the only company that has the concept of on premises availability zones. We have synchronous replication where you can have multiple clusters that air synchronously replicated. So if one fails the other one, you have no service disruption or loss of data, even for a state full application, right? So it's cloud like service is that we're bringing on Prem and then providing the links, you know, for both d. R and D P and production workloads to the public Cloud >> block locked Unpack with you guys. You might want to keep track of humaneness. Stateville date. It's a whole nother topic, as stateless data is easy to manage with AP Eyes and Service's wouldn't GET state. That's when it gets interesting. Com Part in the CEO. The new chief executive officer. Demonte Day How long you guys been around before you took over? >> About five years. Four years before me about been on board about a year. >> I'm looking forward to tracking your progress. We'll see ya next week and seven of'em Real Tom Barton, Sea of de Amante Here inside the Cube Hot startup. I'm John Ferrier. >> Thanks for watching.