(upbeat music) >> Welcome back everyone to The Cubes coverage here in Seattle, Washington. For AWS's Marketplace Seller Conference. It's the big news within the Amazon partner network, combining with marketplace, forming the Amazon partner organization. Part of a big reorg as they grow to the next level, NextGen cloud, mid-game on the chessboard. Cube's got it covered. I'm John Furry, your host at Cube. Great guests here from Data bricks. Both cube alumni's. Jack Anderson, GM and VP of the Databricks partnership team for AWS. You handle that relationship and Joel Minick vice president of product and partner marketing. You guys have the keys to the kingdom with Databricks and AWS. Thanks for joining. Good to see you again. >> Thanks for having us back. >> Yeah, John, great to be here. >> So I feel like we're at Reinvent 2013. Small event, no stage, but there's a real shift happening with procurement. Obviously it's a no brainer on the micro, you know, people should be buying online. Self-service, Cloud Scale. But Amazon's got billions being sold through their marketplace. They've reorganized their partner network. You can see kind of what's going on. They've kind of figured it out. Like let's put everything together and simplify and make it less of a website, marketplace. Merge our partner organizations, have more synergy and frictionless experiences so everyone can make more money and customer's are going to be happier. >> Yeah, that's right. >> I mean, you're running relationship. You're in the middle of it. >> Well, Amazon's mental model here is that they want the world's best ISVs to operate on AWS so that we can collaborate and co architect on behalf of customers. And that's exactly what the APO and marketplace allow us to do, is to work with Amazon on these really, you know, unique use cases. >> You know, I interviewed Ali many times over the years. I remember many years ago, maybe six, seven years ago, we were talking. He's like, "we're all in on AWS." Obviously now the success of Databricks, you've got multiple clouds, see that. Customers have choice. But I remember the strategy early on. It was like, we're going to be deep. So this is, speaks volumes to the relationship you have. Years. Jack, take us through the relationship that Databricks has with AWS from a partner perspective. Joel, and from a product perspective. Because it's not like you guys are Johnny come lately, new to the scene. >> Right. >> You've been there, almost president creation of this wave. What's the relationship and how does it relate to what's going on today? >> So most people may not know that Databricks was born on AWS. We actually did our first $100 million of revenue on Amazon. And today we're obviously available on multiple clouds. But we're very fond of our Amazon relationship. And when you look at what the APN allows us to do, you know, we're able to expand our reach and co-sell with Amazon, and marketplace broadens our reach. And so, we think of marketplace in three different aspects. We've got the marketplace private offer business, which we've been doing for a number of years. Matter of fact, we were driving well over a hundred percent year over year growth in private offers. And we have a nine figure business. So it's a very significant business. And when a customer uses a private offer, that private offer counts against their private pricing agreement with AWS. So they get pricing power against their private pricing. So it's really important it goes on their Amazon bill. In may we launched our pay as you go, on demand offering. And in five short months, we have well over a thousand subscribers. And what this does, is it really reduces the barriers to entry. It's low friction. So anybody in an enterprise or startup or public sector company can start to use Databricks on AWS, in a consumption based model, and have it go against their monthly bill. And so we see customers, you know, doing rapid experimentation, pilots, POCs. They're really learning the value of that first, use case. And then we see rapid use case expansion. And the third aspect is the consulting partner, private offer, CPPO. Super important in how we involve our partner ecosystem of our consulting partners and our resellers that are able to work with Databricks on behalf of customers. >> So you got the big contracts with the private offer. You got the product market fit, kind of people iterating with data, coming in with the buyers you get. And obviously the integration piece all fitting in there. >> Exactly. >> Okay, so those are the offers, that's current, what's in marketplace today. Is that the products... What are people buying? >> Yeah. >> I mean, I guess what's the... Joel, what are people buying in the marketplace? And what does it mean for them? >> So fundamentally what they're buying is the ability to take silos out of their organization. And that is the problem that Databricks is out there to solve. Which is, when you look across your data landscape today, you've got unstructured data, you've got structured data, you've got real time streaming data. And your teams are trying to use all of this data to solve really complicated problems. And as Databricks, as the Lakehouse Company, what we're helping customers do is, how do they get into the new world? How do they move to a place where they can use all of that data across all of their teams? And so we allow them to begin to find, through the marketplace, those rapid adoption use cases where they can get rid of these data warehousing, data lake silos they've had in the past. Get their unstructured and structured data onto one data platform, an open data platform, that is no longer adherent to any proprietary formats and standards and something they can, very much, very easily, integrate into the rest of their data environment. Apply one common data governance layer on top of that. So that from the time they ingest that data, to the time they use that data, to the time they share that data, inside and outside of their organization, they know exactly how it's flowing. They know where it came from. They know who's using it. They know who has access to it. They know how it's changing. And then with that common data platform, with that common governance solution, they'd being able to bring all of those use cases together. Across their real time streaming, their data engineering, their BI, their AI. All of their teams working on one set of data. And that lets them move really, really fast. And it also lets them solve challenges they just couldn't solve before. A good example of this, you know, one of the world's now largest data streaming platforms runs on Databricks with AWS. And if you think about what does it take to set that up? Well, they've got all this customer data that was historically inside of data warehouses. That they have to understand who their customers are. They have all this unstructured data, they've built their data science model, so they can do the right kinds of recommendation engines and forecasting around. And then they've got all this streaming data going back and forth between click stream data, from what the customers are doing with their platform and the recommendations they want to push back out. And if those teams were all working in individual silos, building these kinds of platforms would be extraordinarily slow and complex. But by building it on Databricks, they were able to release it in record time and have grown at a record pace to now be the number one platform. >> And this product, it's impacting product development. >> Absolutely. >> I mean, this is like the difference between lagging months of product development, to like days. >> Yes. >> Pretty much what you're getting at. >> Yes. >> So total agility. >> Mm-hmm. >> I got that. Okay, now, I'm a customer I want to buy in the marketplace, but you got direct Salesforce up there. So how do you guys look at this? Is there channel conflict? Are there comp programs? Because one of the things I heard today in on the stage from AWS's leadership, Chris, was up there speaking, and Mona was, "Hey, he's a CRO conference chief revenue officer" conversation. Which means someone's getting compensated. So, if I'm the sales rep at Databricks, what's my motion to the customer? Do I get paid? Does Amazon sell it? Take us through that. Is there channel conflict? Or, how do you handle it? >> Well, I'd add what Joel just talked about with, you know, with the solution, the value of the solution our entire offering is available on AWS marketplace. So it's not a subset, it's the entire Data Bricks offering. And- >> The flagship, all the, the top stuff. >> Everything, the flagship, the complete offering. So it's not segmented. It's not a sub segment. >> Okay. >> It's, you know, you can use all of our different offerings. Now when it comes to seller compensation, we view this two different ways, right? One is that AWS is also incented, right? Versus selling a native service to recommend Databricks for the right situation. Same thing with Databricks, our sales force wants to do the right thing for the customer. If the customer wants to use marketplace as their procurement vehicle. And that really helps customers because if you get Databricks and five other ISVs together, and let's say each ISV is spending, you're spending a million dollars. You have $5 million of spend. You put that spend through the flywheel with AWS marketplace, and then you can use that in your negotiations with AWS to get better pricing overall. So that's how we view it. >> So customers are driving. This sounds like. >> Correct. For sure. >> So they're looking at this as saying, Hey, I'm going to just get purchasing power with all my relationships. Because it's a solution architectural market, right? >> Yeah. It makes sense. Because if most customers will have a primary and secondary cloud provider. If they can consolidate, you know, multiple ISV spend through that same primary provider, you get pricing power. >> Okay, Joel, we're going to date ourselves. At least I will. So back in the old days, (group laughter) It used to be, do a Barney deal with someone, Hey, let's go to market together. You got to get paper, you do a biz dev deal. And then you got to say, okay, now let's coordinate our sales teams, a lot of moving parts. So what you're getting at here is that the alternative for Databricks, or any company is, to go find those partners and do deals, versus now Amazon is the center point for the customer. So you can still do those joint deals, but this seems to be flipping the script a little bit. >> Well, it is, but we still have vars and consulting partners that are doing implementation work. Very valuable work, advisory work, that can actually work with marketplace through the CPPO offering. So the marketplace allows multiple ways to procure your solution. >> So it doesn't change your business structure. It just makes it more efficient. >> That's correct. >> That's a great way to say it. >> Yeah, that's great. >> Okay. So, that's it. So that's just makes it more efficient. So you guys are actually incented to point customers to the marketplace. >> Yes. >> Absolutely. >> Economically. >> Economically, it's the right thing to do for the customer. It's the right thing to do for our relationship with Amazon. Especially when it comes back to co-selling, right? Because Amazon now is leaning in with ISVs and making recommendations for, you know, an ISV solution. And our teams are working backwards from those use cases, you know, to collaborate and land them. >> Yeah. I want to get that out there. Go ahead, Joel. >> So one of the other things I might add to that too, you know, and why this is advantageous for companies like Databricks to work through the marketplace. Is it makes it so much easier for customers to deploy a solution. It's very, literally, one click through the marketplace to get Databricks stood up inside of your environment. And so if you're looking at how do I help customers most rapidly adopt these solutions in the AWS cloud, the marketplace is a fantastic accelerator to that. >> You know, it's interesting. I want to bring this up and get your reaction to it because to me, I think this is the future of procurement. So from a procurement standpoint, I mean, again, dating myself, EDI back in the old days, you know, all that craziness. Now this is all the internet, basically through the console. I get the infrastructure side, you know, spin up and provision some servers, all been good. You guys have played well there in the marketplace. But now as we get into more of what I call the business apps, and they brought this up on stage. A little nuanced. Most enterprises aren't yet there of integrating tech, on the business apps, into the stack. This is where I think you guys are a use case of success where you guys have been successful with data integration. It's an integrators dilemma, not an innovator's dilemma. So like, I want to integrate. So now I have integration points with Databricks, but I want to put an app in there. I want to provision an application, but it has to be built. It's not, you don't buy it. You build, you got to build stuff. And this is the nuance. What's your reaction to that? Am I getting this right? Or am I off because, no one's going to be buying software like they used to. They buy software to integrate it. >> Yeah, no- >> Because everything's integrated. >> I think AWS has done a great job at creating a partner ecosystem, right? To give customers the right tools for the right jobs. And those might be with third parties. Databricks is doing the same thing with our partner connect program, right? We've got customer partners like Five Tran and DBT that, you know, augment and enhance our platform. And so you're looking at multi ISV architectures and all of that can be procured through the AWS marketplace. >> Yeah. It's almost like, you know, bundling and un bundling. I was talking about this with, with Dave Alante about Supercloud. Which is why wouldn't a customer want the best solution in their architecture? Period. In its class. If someone's got API security or an API gateway. Well, you know, I don't want to be forced to buy something because it's part of a suite. And that's where you see things get sub optimized. Where someone dominates a category and they have, oh, you got to buy my version of this. >> Joel and I were talking, we were actually saying, what's really important about Databricks, is that customers control the data, right? You want to comment on that? >> Yeah. I was going to say, you know, what you're pushing on there, we think is extraordinarily, you know, the way the market is going to go. Is that customers want a lot of control over how they build their data stack. And everyone's unique in what tools are the right ones for them. And so one of the, you know, philosophically, I think, really strong places, Databricks and AWS have lined up, is we both take an approach that you should be able to have maximum flexibility on the platform. And as we think about the Lakehouse, one thing we've always been extremely committed to, as a company, is building the data platform on an open foundation. And we do that primarily through Delta Lake and making sure that, to Jack's point, with Databricks, the data is always in your control. And then it's always stored in a completely open format. And that is one of the things that's allowed Databricks to have the breadth of integrations that it has with all the other data tools out there. Because you're not tied into any proprietary format, but instead are able to take advantage of all the innovation that's happening out there in the open source ecosystem. >> When you see other solutions out there that aren't as open as you guys, you guys are very open by the way, we love that too. We think that's a great strategy, but what am I foreclosing if I go with something else that's not as open? What's the customer's downside as you think about what's around the corner in the industry? Because if you believe it's going to be open, open source, which I think open source software is the software industry, and integration is a big deal. Because software's going to be plentiful. >> Sure. >> Let's face it. It's a good time to be in software business. But Cloud's booming. So what's the downside, from your Databricks perspective? You see a buyer clicking on Databricks versus that alternative. What's potentially should they be a nervous about, down the road, if they go with a more proprietary or locked in approach? >> Yeah. >> Well, I think the challenge with proprietary ecosystems is you become beholden to the ability of that provider to both build relationships and convince other vendors that they should invest in that format. But you're also, then, beholden to the pace at which that provider is able to innovate. >> Mm-hmm. >> And I think we've seen lots of times over history where, you know, a proprietary format may run ahead, for a while, on a lot of innovation. But as that market control begins to solidify, that desire to innovate begins to degrade. Whereas in the open formats- >> So extract rents versus innovation. (John laughs) >> Exactly. Yeah, exactly. >> I'll say it. >> But in the open world, you know, you have to continue to innovate. >> Yeah. >> And the open source world is always innovating. If you look at the last 10 to 15 years, I challenge you to find, you know, an example where the innovation in the data and AI world is not coming from open source. And so by investing in open ecosystems, that means you are always going to be at the forefront of what is the latest. >> You know, again, not to date myself again, but you look back at the eighties and nineties, the protocol stacked with proprietary. >> Yeah. >> You know, SNA and IBM, deck net was digital. You know the rest. And then TCPIP was part of the open systems interconnect. >> Mm-hmm. >> Revolutionary (indistinct) a big part of that, as well as my school did. And so like, you know, that was, but it didn't standardize the whole stack. It stopped at IP and TCP. >> Yeah. >> But that helped inter operate, that created a nice defacto. So this is a big part of this mid game. I call it the chessboard, you know, you got opening game and mid-game, then you get the end game. You're not there at the end game yet at Cloud. But Cloud- >> There's, always some form of lock in, right? Andy Jazzy will address it, you know, when making a decision. But if you're going to make a decision you want to reduce- You don't want to be limited, right? So I would advise a customer that there could be limitations with a proprietary architecture. And if you look at what every customer's trying to become right now, is an AI driven business, right? And so it has to do with, can you get that data out of silos? Can you organize it and secure it? And then can you work with data scientists to feed those models? >> Yeah. >> In a very consistent manner. And so the tools of tomorrow will, to Joel's point, will be open and we want interoperability with those tools. >> And choice is a matter too. And I would say that, you know, the argument for why I think Amazon is not as locked in as maybe some other clouds, is that they have to compete directly too. Redshift competes directly with a lot of other stuff. But they can't play the bundling game because the customers are getting savvy to the fact that if you try to bundle an inferior product with something else, it may not work great at all. And they're going to be, they're onto it. This is the- >> To Amazon's credit by having these solutions that may compete with native services in marketplace, they are providing customers with choice, low price- >> And access to the core value. Which is the hardware- >> Exactly. >> Which is their platform. Okay. So I want to get you guys thought on something else I see emerging. This is, again, kind of Cube rumination moment. So on stage, Chris unpacked a lot of stuff. I mean this marketplace, they're touching a lot of hot buttons here, you know, pricing, compensation, workflows, services behind the curtain. And one of those things he mentioned was, they talk about resellers or channel partners, depending upon what you talk about. We believe, Dave and I believe on the Cube, that the entire indirect sales channel of the industry is going to be disrupted radically. Because those players were selling hardware in the old days and software. That game is going to change. You mentioned you guys have a program, let me get your thoughts on this. We believe that once this gets set up, they can play in this game and bring their services in. Which means that the old reseller channels are going to be rewritten. They're going to be refactored with this new kinds of access. Because you've got scale, you've got money and you've got product. And you got customers coming into the marketplace. So if you're like a reseller that sold computers to data centers or software, you know, a value added reseller or VAB or business. >> You've got to evolve. >> You got to, you got to be here. >> Yes. >> Yeah. >> How are you guys working with those partners? Because you say you have a product in your marketplace there. How do I make money if I'm a reseller with Databricks, with Amazon? Take me through that use case. >> Well I'll let Joel comment, but I think it's pretty straightforward, right? Customers need expertise. They need knowhow. When we're seeing customers do mass migrations to the cloud or Hadoop specific migrations or data transformation implementations. They need expertise from consulting and SI partners. If those consulting and SI partners happen to resell the solution as well. Well, that's another aspect of their business. But I really think it is the expertise that the partners bring to help customers get outcomes. >> Joel, channel big opportunity for Amazon to reimagine this. >> For sure. Yeah. And I think, you know, to your comment about how do resellers take advantage of that, I think what Jack was pushing on is spot on. Which is, it's becoming more and more about the expertise you bring to the table. And not just transacting the software. But now actually helping customers make the right choices. And we're seeing, you know, both SIs begin to be able to resell solutions and finding a lot of opportunity in that. >> Yeah. And I think we're seeing traditional resellers begin to move into that SI model as well. And that's going to be the evolution that this goes. >> At the end of the day, it's about services, right? >> For sure. Yeah. >> I mean... >> You've got a great service. You're going to have high gross profits. >> Yeah >> Managed service provider business is alive and well, right? Because there are a number of customers that want that type of a service. >> I think that's going to be a really hot, hot button for you guys. I think being the way you guys are open, this channel, partner services model coming in, to the fold, really kind of makes for kind of that Supercloud like experience, where you guys now have an ecosystem. And that's my next question. You guys have an ecosystem going on, within Databricks. >> For sure. >> On top of this ecosystem. How does that work? This is kind of like, hasn't been written up in business school and case studies yet. This is new. What is this? >> I think, you know, what it comes down to is, you're seeing ecosystems begin to evolve around the data platforms. And that's going to be one of the big, kind of, new horizons for us as we think about what drives ecosystems. It's going to be around, well, what's the data platform that I'm using? And then all the tools that have to encircle that to get my business done. And so I think there's, you know, absolutely ecosystems inside of the AWS business on all of AWS's services, across data analytics and AI. And then to your point, you are seeing ecosystems now arise around Databricks in its Lakehouse platform as well. As customers are looking at well, if I'm standing these Lakehouses up and I'm beginning to invest in this, then I need a whole set of tools that help me get that done as well. >> I mean you think about ecosystem theory, we're living a whole nother dream. And I'm not kidding. It hasn't yet been written up and for business school case studies is that, we're now in a whole nother connective tissue, ecology thing happening. Where you have dependencies and value proposition. Economics, connectedness. So you have relationships in these ecosystems. >> And I think one of the great things about the relationships with these ecosystems, is that there's a high degree of overlap. >> Yeah. >> So you're seeing that, you know, the way that the cloud business is evolving, the ecosystem partners of Databricks, are the same ecosystem partners of AWS. And so as you build these platforms out into the cloud, you're able to really take advantage of best of breed, the broadest set of solutions out there for you. >> Joel, Jack, I love it because you know what it means? The best ecosystem will win, if you keep it open. >> Sure, sure. >> You can see everything. If you're going to do it in the dark, you know, you don't know the outcome. I mean, this is really kind of what we're talking about. >> And John, can I just add that when I was at Amazon, we had a theory that there's buyers and builders, right? There's very innovative companies that want to build things themselves. We're seeing now that that builders want to buy a platform. Right? >> Yeah. >> And so there's a platform decision being made and that ecosystem is going to evolve around the platform. >> Yeah, and I totally agree. And the word innovation gets kicked around. That's why, you know, when we had our Supercloud panel, it was called the innovators dilemma, with a slash through it, called the integrater's dilemma. Innovation is the digital transformation. So- >> Absolutely. >> Like that becomes cliche in a way, but it really becomes more of a, are you open? Are you integrating? If APIs are connective tissue, what's automation, what's the service messages look like? I mean, a whole nother set of, kind of thinking, goes on in these new ecosystems and these new products. >> And that thinking is, has been born in Delta Sharing, right? So the idea that you can have a multi-cloud implementation of Databricks, and actually share data between those two different clouds, that is the next layer on top of the native cloud solution. >> Well, Databricks has done a good job of building on top of the goodness of, and the CapEx gift from AWS. But you guys have done a great job taking that building differentiation into the product. You guys have great customer base, great growing ecosystem. And again, I think a shining example of what every enterprise is going to do. Build on top of something, operating model, get that operating model, driving revenue. >> Mm-hmm. >> Yeah. >> Whether, you're Goldman Sachs or capital one or XYZ corporation. >> S and P global, NASDAQ. >> Yeah. >> We've got, you know, the biggest verticals in the world are solving tough problems with Databricks. I think we'd be remiss because if Ali was here, he would really want to thank Amazon for all of the investments across all of the different functions. Whether it's the relationship we have with our engineering and service teams. Our marketing teams, you know, product development. And we're going to be at Reinvent. A big presence at Reinvent. We're looking forward to seeing you there, again. >> Yeah. We'll see you guys there. Yeah. Again, good ecosystem. I love the ecosystem evolutions happening. This NextGen Cloud is here. We're seeing this evolve, kind of new economics, new value propositions kind of scaling up. Producing more. So you guys are doing a great job. Thanks for coming on the Cube and taking the time. Joel, great to see you at the check. >> Thanks for having us, John. >> Okay. Cube coverage here. The world's changing as APN comes together with the marketplace for a new partner organization at Amazon web services. The Cube's got it covered. This should be a very big, growing ecosystem as this continues. Billions of being sold through the marketplace. And of course the buyers are happy as well. So we've got it all covered. I'm John Furry. your host of the cube. Thanks for watching. (upbeat music)

>>Welcome back everyone to the cubes coverage here in Seattle, Washington, AWS's marketplace seller conference. It's the big news within the Amazon partner network, combining with marketplaces, forming the Amazon partner organization, part of a big reorg as they grow the next level NextGen cloud mid-game on the chessboard. Cube's got cover. I'm John fur, host of Cub, a great guests here from data bricks, both cube alumnis, Jack Anderson, GM of the and VP of the data bricks partnership team. For ADOS, you handle that relationship and Joel Minick vice president of product and partner marketing. You guys are the, have the keys to the kingdom with data, bricks, and AWS. Thanks for joining. Thanks for good to see you again. Thanks for >>Having us back. Yeah, John, great to be here. >>So I feel like we're at reinvent 2013 small event, no stage, but there's a real shift happening with procurement. Obviously it makes it's a no brainer on the micro, you know, people should be buying online self-service cloud scale, but Amazon's got billions being sold to their marketplace. They've reorganized their partner network. You can see kind of what's going on. They've kind of figured it out. Like let's put everything together and simplify and make it less of a website marketplace merge our partner to have more synergy and friction, less experiences so everyone can make more money and customer's gonna be happier. >>Yeah, that's right. >>I mean, you're run relationship. You're in the middle of it. >>Well, Amazon's mental model here is that they want the world's best ISVs to operate on AWS so that we can collaborate and co architect on behalf of customers. And that's exactly what the APO and marketplace allow us to do is to work with Amazon on these really, you know, unique use cases. >>You know, I interviewed Ali many times over the years. I remember many years ago, I think six, maybe six, seven years ago, we were talking. He's like, we're all in ons. Obviously. Now the success of data bricks, you've got multiple clouds. See that customers have choice, but I remember the strategy early on. It was like, we're gonna be deep. So this is speaks volumes to the, the relationship you have years. Jack take us through the relationship that data bricks has with AWS from a, from a partner perspective, Joel, and from a product perspective, because it's not like you got to Johnny come lately new to the new, to the scene, right? We've been there almost president creation of this wave. What's the relationship and has it relate to what's going on today? >>So, so most people may not know that data bricks was born on AWS. We actually did our first 100 million of revenue on Amazon. And today we're obviously available on multiple clouds, but we're very fond of our Amazon relationship. And when you look at what the APN allows us to do, you know, we're able to expand our reach and co-sell with Amazon and marketplace broadens our reach. And so we think of marketplace in three different aspects. We've got the marketplace, private offer business, which we've been doing for a number of years. Matter of fact, we we're driving well over a hundred percent year over year growth in private offers and we have a nine figure business. So it's a very significant business. And when a customer uses a private offer that private offer counts against their private pricing agreement with AWS. So they get pricing power against their, their private pricing. >>So it's really important. It goes on their Amazon bill in may. We launched our pay as you go on demand offering. And in five short months, we have well over a thousand subscribers. And what this does is it really reduces the barriers to entry it's low friction. So anybody in an enterprise or startup or public sector company can start to use data bricks on AWS and pay consumption based model and have it go against their monthly bill. And so we see customers, you know, doing rapid experimentation pilots, POCs, they're, they're really learning the value of that first use case. And then we see rapid use case expansion. And the third aspect is the consulting partner, private offers C P O super important in how we involve our partner ecosystem of our consulting partners and our resellers that are able to work with data bricks on behalf of customers. >>So you got the big contracts with the private offer. You got the product market fit, kind of people iterating with data coming in with, with the buyers you go. And obviously the integration piece all fitting in there. Exactly. Exactly. Okay. So that's that those are the offers that's current and what's in marketplace today. Is that the products, what are, what are people buying? I mean, I guess what's the Joel, what are, what are people buying in the marketplace and what does it mean for >>Them? So fundamentally what they're buying is the ability to take silos out of their organization. And that's, that is the problem that data bricks is out there to solve, which is when you look across your data landscape today, you've got unstructured data, you've got structured data, you've got real time streaming data, and your teams are trying to use all of this data to solve really complicated problems. And as data bricks as the lake house company, what we're helping customers do is how do they get into the new world? How do they move to a place where they can use all of that data across all of their teams? And so we allow them to begin to find through the marketplace, those rapid adoption use cases where they can get rid of these data, warehousing data lake silos they've had in the past, get their unstructured and structured data onto one data platform and open data platform that is no longer adherent to any proprietary formats and standards and something. >>They can very much, very easily integrate into the rest of their data environment, apply one common data governance layer on top of that. So that from the time they ingest that data to the time they use that data to the time they share that data inside and outside of their organization, they know exactly how it's flowing. They know where it came from. They know who's using it. They know who has access to it. They know how it's changing. And then with that common data platform with that common governance solution, they'd being able to bring all of those use cases together across their real time, streaming their data engineering, their BI, their AI, all of their teams working on one set of data. And that lets them move really, really fast. And it also lets them solve challenges. They just couldn't solve before a good example of this, you know, one of the world's now largest data streaming platforms runs on data bricks with AWS. >>And if you think about what does it take to set that up? Well, they've got all this customer data that was historically inside of data warehouses, that they have to understand who their customers are. They have all this unstructured data, they've built their data science model, so they can do the right kinds of recommendation engines and forecasting around. And then they've got all this streaming data going back and forth between click stream data from what the customers are doing with their platform and the recommendations they wanna push back out. And if those teams were all working in individual silos, building these kinds of platforms would be extraordinarily slow and complex, but by building it on data bricks, they were able to release it in record time and have grown at, at record pace >>To not be that's product platform that's impacting product development. Absolutely. I mean, this is like the difference between lagging months of product development to like days. Yes. Pretty much what you're getting at. Yeah. So total agility. I got that. Okay. Now I'm a customer I wanna buy in the marketplace, but I also, you got direct Salesforce up there. So how do you guys look at this? Is there channel conflict? Are there comp programs? Because one of the things I heard today in on the stage from a Davis's leadership, Chris was up there speaking and, and, and moment I was, Hey, he's a CRO conference, chief revenue officer conversation, which means someone's getting compensated. So if I'm the sales rep at data bricks, what's my motion to the customer. Do I get paid? Does Amazon sell it? Take us through that. Is there channel conflict? Is there or an audio lift? >>Well, I I'd add what Joel just talked about with, with, you know, what the solution, the value of the solution our entire offering is available on AWS marketplace. So it's not a subset, the entire data bricks offering and >>The flagship, all the, the top, >>Everything, the flagship, the complete offering. So it's not, it's not segmented. It's not a sub segment. It's it's, you know, you can use all of our different offerings. Now when it comes to seller compensation, we, we, we view this two, two different ways, right? One is that AWS is also incented, right? Versus selling a native service to recommend data bricks for the right situation. Same thing with data bricks. Our Salesforce wants to do the right thing for the customer. If the customer wants to use marketplace as their procurement vehicle. And that really helps customers because if you get data bricks and five other ISVs together, and let's say each ISV is spending, you're spending a million dollars, you have $5 million of spend, you put that spend through the flywheel with AWS marketplace. And then you can use that in your negotiations with AWS to get better pricing overall. So that's how we, >>We do it. So customers are driving. This sounds like, correct. For sure. So they're looking at this as saying, Hey, I'm gonna just get purchasing power with all my relationships because it's a solution architectural market, right? >>Yeah. It makes sense. Because if most customers will have a primary and secondary cloud provider, if they can consolidate, you know, multiple ISV spend through that same primary provider, you get pricing >>Power, okay, Jill, we're gonna date ourselves. At least I will. So back in the old days, it used to be, do a Barney deal with someone, Hey, let's go to market together. You gotta get paper, you do a biz dev deal. And then you gotta say, okay, now let's coordinate our sales teams, a lot of moving parts. So what you're getting at here is that the alternative for data bricks or any company is to go find those partners and do deals versus now Amazon is the center point for the customer so that you can still do those joint deals. But this seems to be flipping the script a little bit. >>Well, it is, but we still have VAs and consulting partners that are doing implementation work very valuable work advisory work that can actually work with marketplace through the C PPO offering. So the marketplace allows multiple ways to procure your >>Solution. So it doesn't change your business structure. It just makes it more efficient. That's >>Correct. >>That's a great way to say it. Yeah, >>That's great. So that's so that's it. So that's just makes it more efficient. So you guys are actually incented to point customers to the marketplace. >>Yes, >>Absolutely. Economically. Yeah. >>E economically it's the right thing to do for the customer. It's the right thing to do for our relationship with Amazon, especially when it comes back to co-selling right? Because Amazon now is leaning in with ISVs and making recommendations for, you know, an ISV solution and our teams are working backwards from those use cases, you know, to collaborate, land them. >>Yeah. I want, I wanna get that out there. Go ahead, Joel. >>So one of the other things I might add to that too, you know, and why this is advantageous for, for companies like data bricks to, to work through the marketplace, is it makes it so much easier for customers to deploy a solution. It's, it's very, literally one click through the marketplace to get data bricks stood up inside of your environment. And so if you're looking at how do I help customers most rapidly adopt these solutions in the AWS cloud, the marketplace is a fantastic accelerator to that. You >>Know, it's interesting. I wanna bring this up and get your reaction to it because to me, I think this is the future of procurement. So from a procurement standpoint, I mean, again, dating myself EDI back in the old days, you know, all that craziness. Now this is all the, all the internet, basically through the console, I get the infrastructure side, you know, spin up and provision. Some servers, all been good. You guys have played well there in the marketplace. But now as we get into more of what I call the business apps, and they brought this up on stage little nuance, most enterprises aren't yet there of integrating tech on the business apps, into the stack. This is where I think you guys are a use case of success where you guys have been successful with data integration. It's an integrator's dilemma, not an innovator's dilemma. So like, I want to integrate, so now I have integration points with data bricks, but I want to put an app in there. I want to provision an application, but it has to be built. It's not, you don't buy it. You build, you gotta build stuff. And this is the nuance. What's your reaction to that? Am I getting this right? Or, or am I off because no, one's gonna be buying software. Like they used to, they buy software to integrate it. >>Yeah, >>No, I, cause everything's integrated. >>I think AWS has done a great job at creating a partner ecosystem, right. To give customers the right tools for the right jobs. And those might be with third parties, data bricks is doing the same thing with our partner connect program. Right. We've got customer, customer partners like five tra and D V T that, you know, augment and enhance our platform. And so you, you're looking at multi ISV architectures and all of that can be procured through the AWS marketplace. >>Yeah. It's almost like, you know, bundling and unbundling. I was talking about this with, with Dave ante about Supercloud, which is why wouldn't a customer want the best solution in their architecture period. And it's class. If someone's got API security or an API gateway. Well, you know, I don't wanna be forced to buy something because it's part of a suite and that's where you see things get suboptimized where someone dominates a category and they have, oh, you gotta buy my version of this. Yeah. >>Joel, Joel. And that's Joel and I were talking, we're actually saying what what's really important about Databricks is that customers control the data. Right? You wanna comment on that? >>Yeah. I was say the, you know what you're pushing on there we think is extraordinarily, you know, the way the market is gonna go is that customers want a lot of control over how they build their data stack. And everyone's unique in what tools are the right ones for them. And so one of the, you know, philosophically I think really strong places, data, bricks, and AWS have lined up is we both take an approach that you should be able to have maximum flexibility on the platform. And as we think about the lake house, one thing we've always been extremely committed to as a company is building the data platform on an open foundation. And we do that primarily through Delta lake and making sure that to Jack's point with data bricks, the data is always in your control. And then it's always stored in a completely open format. And that is one of the things that's allowed data bricks to have the breadth of integrations that it has with all the other data tools out there, because you're not tied into any proprietary format, but instead are able to take advantage of all the innovation that's happening out there in the open source ecosystem. >>When you see other solutions out there that aren't as open as you guys, you guys are very open by the way, we love that too. We think that's a great strategy, but what's the, what am I foreclosing? If I go with something else that's not as open what what's the customer's downside as you think about what's around the corner in the industry. Cuz if you believe it's gonna be open, open source, which I think opens our software is the software industry and integration is a big deal, cuz software's gonna be plentiful. Let's face it. It's a good time to be in software business, but cloud's booming. So what's the downside from your data bricks perspective, you see a buyer clicking on data bricks versus that alternative what's potentially is should they be a nervous about down the road if they go with a more proprietary or locked in approach? Well, >>I think the challenge with proprietary ecosystems is you become beholden to the ability of that provider to both build relationships and convince other vendors that they should invest in that format. But you're also then beholden to the pace at which that provider is able to innovate. And I think we've seen lots of times over history where, you know, a proprietary format may run ahead for a while on a lot of innovation. But as that market control begins to solidify that desire to innovate begins to, to degrade, whereas in the open format. So >>Extract rents versus innovation. Exactly. >>Yeah, exactly. >>But >>I'll say it in the open world, you know, you have to continue to innovate. Yeah. And the open source world is always innovating. If you look at the last 10 to 15 years, I challenge you to find, you know, an example where the innovation in the data and AI world is not coming from open source. And so by investing in open ecosystems, that means you were always going to be at the forefront of what is the >>Latest, you know, again, not to date myself again, but you look back at the eighties and nineties, the protocol stacked for proprietary. Yeah. You know, SNA at IBM deck net was digital, you know, the rest is, and then TCP, I P was part of the open systems, interconnect, revolutionary Oly, a big part of that as well as my school did. And so like, you know, that was, but it didn't standardize the whole stack. It stopped at IP and TCP. Yeah. But that helped interoperate, that created a nice defacto. So this is a big part of this mid game. I call it the chessboard, you know, you got opening game and mid game. Then you got the end game and we're not there. The end game yet cloud the cloud. >>There's, there's always some form of lock in, right. Andy jazzy will, will address it, you know, when making a decision. But if you're gonna make a decision you want to reduce as you don't wanna be limited. Right. So I would advise a customer that there could be limitations with a proprietary architecture. And if you look at what every customer's trying to become right now is an AI driven business. Right? And so it has to do with, can you get that data outta silos? Can you, can you organize it and secure it? And then can you work with data scientists to feed those models? Yeah. In a, in a very consistent manner. And so the tools of tomorrow will to Joel's point will be open and we want interoperability with those >>Tools and, and choice is a matter too. And I would say that, you know, the argument for why I think Amazon is not as locked in as maybe some other clouds is that they have to compete directly too. Redshift competes directly with a lot of other stuff, but they can't play the bundling game because the customers are getting savvy to the fact that if you try to bundle an inferior product with something else, it may not work great at all. And they're gonna be they're onto it. This is >>The Amazon's credit by having these, these solutions that may compete with native services in marketplace, they are providing customers with choice, low >>Price and access to the S and access to the core value. Exactly. Which the >>Hardware, which is their platform. Okay. So I wanna get you guys thought on something else. I, I see emerging, this is again kind of cube rumination moment. So on stage Chris unpacked, a lot of stuff. I mean this marketplace, they're touching a lot of hot buttons here, you know, pricing compensation, workflows services behind the curtain. And one of the things he mentioned was they talk about resellers or channel partners, depending upon what you talk about. We believe Dave and I believe on the cube that the entire indirect sales channel of the industry is gonna be disrupted radically because those players were selling hardware in the old days and software, that game is gonna change. You know, you mentioned you guys have a program, want to get your thoughts on this. We believe that once this gets set up, they can play in this game and bring their services in which means that the old reseller channels are gonna be rewritten. They're gonna be refactored with this new kinds of access. Cuz you've got scale, you've got money and you've got product and you got customers coming into the marketplace. So if you're like a reseller that sold computers to data centers or software, you know, value added reseller or V or business, >>You've gotta evolve. >>You gotta, you gotta be here. Yes. How are you guys working with those partners? Cuz you say you have a part in your marketplace there. How do I make money? If I'm a reseller with data bricks with eight Amazon, take me through that use case. >>Well I'll let Joel comment, but I think it's, it's, it's pretty straightforward, right? Customers need expertise. They need knowhow. When we're seeing customers do mass migrations to the cloud or Hadoop specific migrations or data transformation implementations, they need expertise from consulting and SI partners. If those consulting SI partners happen to resell the solution as well. Well, that's another aspect of their business, but I really think it is the expertise that the partners bring to help customers get outcomes. >>Joel, channel big opportunity for re re Amazon to reimagine this. >>For sure. Yeah. And I think, you know, to your comment about how to resellers take advantage of that, I think what Jack was pushing on is spot on, which is it's becoming more about more and more about the expertise you bring to the table and not just transacting the software, but now actually helping customers make the right choices. And we're seeing, you know, both SI begin to be able to resell solutions and finding a lot of opportunity in that. Yeah. And I think we're seeing traditional resellers begin to move into that SI model as well. And that's gonna be the evolution that >>This gets at the end of the day. It's about services for sure, for sure. You've got a great service. You're gonna have high gross profits. And >>I think that the managed service provider business is alive and well, right? Because there are a number of customers that want that, that type of a service. >>I think that's gonna be a really hot, hot button for you guys. I think being the way you guys are open this channel partner services model coming in to the fold really kind of makes for kind of that super cloudlike experience where you guys now have an ecosystem. And that's my next question. You guys have an ecosystem going on within data bricks for sure. On top of this ecosystem, how does that work? This is kinda like hasn't been written up in business school and case studies yet this is new. What is this? >>I think, you know, what it comes down to is you're seeing ecosystems begin to evolve around the data platforms and that's gonna be one of the big kind of new horizons for us as we think about what drives ecosystems it's going to be around. Well, what is the, what's the data platform that I'm using and then all the tools that have to encircle that to get my business done. And so I think there's, you know, absolutely ecosystems inside of the AWS business on all of AWS's services, across data analytics and AI. And then to your point, you are seeing ecosystems now arise around data bricks in its Lakehouse platform, as well as customers are looking at well, if I'm standing these Lakehouse up and I'm beginning to invest in this, then I need a whole set of tools that help me get that done as well. >>I mean you think about ecosystem theory, we're living a whole nother dream and I'm, and I'm not kidding. It hasn't yet been written up and for business school case studies is that we're now in a whole nother connective tissue ecology thing happening where you have dependencies and value proposition economics connectedness. So you have relationships in these ecosystems. >>And I think one of the great things about relationships with these ecosystems is that there's a high degree of overlap. Yeah. So you're seeing that, you know, the way that the cloud business is evolving, the, the ecosystem partners of data bricks are the same ecosystem partners of AWS. And so as you build these platforms out into the cloud, you're able to really take advantage of best of breed, the broadest set of solutions out there for >>You. Joel, Jack, I love it because you know what it means the best ecosystem will win. If you keep it open. Sure. You can see everything. If you're gonna do it in the dark, you know, you don't know the outcome. I mean, this is really kind we're talking about. >>And John, can I just add that when I was in Amazon, we had a, a theory that there's buyers and builders, right? There's very innovative companies that want to build things themselves. We're seeing now that that builders want to buy a platform. Right? Yeah. And so there's a platform decision being made and that ecosystem gonna evolve around the >>Platform. Yeah. And I totally agree. And, and, and the word innovation get kicks around. That's why, you know, when we had our super cloud panel was called the innovators dilemma with a slash through it called the integrated dilemma, innovation is the digital transformation. So absolutely like that becomes cliche in a way, but it really becomes more of a, are you open? Are you integrating if APIs are the connective tissue, what's automation, what's the service message look like. I mean, a whole nother set of kind of thinking goes on and these new ecosystems and these new products >>And that, and that thinking is, has been born in Delta sharing. Right? So the idea that you can have a multi-cloud implementation of data bricks, and actually share data between those two different clouds, that is the next layer on top of the native cloud >>Solution. Well, data bricks has done a good job of building on top of the goodness of, and the CapEx gift from AWS. But you guys have done a great job taking that building differentiation into the product. You guys have great customer base, great grow ecosystem. And again, I think in a shining example of what every enterprise is going to do, build on top of something operating model, get that operating model, driving revenue. >>Yeah. >>Well we, whether whether you're Goldman Sachs or capital one or XYZ corporation >>S and P global NASDAQ, right. We've got, you know, these, the biggest verticals in the world are solving tough problems with data breaks. I think we'd be remiss cuz if Ali was here, he would really want to thank Amazon for all of the investments across all of the different functions, whether it's the relationship we have with our engineering and service teams. Yeah. Our marketing teams, you know, product development and we're gonna be at reinvent the big presence of reinvent. We're looking forward to seeing you there again. >>Yeah. We'll see you guys there. Yeah. Again, good ecosystem. I love the ecosystem evolutions happening this next gen cloud is here. We're seeing this evolve kind of new economics, new value propositions kind of scaling up, producing more so you guys are doing a great job. Thanks for coming on the Cuban, taking time. Chill. Great to see you at the check. Thanks for having us. Thanks. Going. Okay. Cube coverage here. The world's changing as APN comes to give the marketplace for a new partner organization at Amazon web services, the Cube's got a covered. This should be a very big growing ecosystem as this continues, billions of being sold through the marketplace. Of course the buyers are happy as well. So we've got it all covered. I'm John furry, your host of the cube. Thanks for watching.

>>from around the globe. It's the Cube with digital coverage of CONMEBOL. Future ready 2020. Brought to you by combo. >>Hi and welcome back. I'm Stew Minuteman, and we're at the Cube's coverage of Con Volt Future Ready. You've got the power panel to really dig in on the product announcements that happened at the event today. Joining me? We have three guests. First of all, we have Brenda Rajagopalan. He's the vice president of products. Sitting next to him is Don Foster, vice president of Storage Solutions. And in the far piece of the panel Mersereau, vice president of Global Channels and Alliances. All three of them with Conn Volt. Gentlemen, thanks all three of you for joining us. Exactly. All right, so first of all, great job on the launch. You know, these days with a virtual event doing, you know, the announcements, the engagement with the press and analyst, you know, having demos, customer discussions. It's a challenge to put all those together. And it has been, you know, engaging in interesting watch today. So we're going to start with you. You've been quite busy today explaining all the pieces, so just at a very high level if you put this really looks like the culmination of the update with Conn Volt portfolio new team new products compared to kind of a year, year and 1/2 ago. So just if you could start us off with kind of the high points, >>thank you still, yeah, absolutely exciting day for us today. You did comrade multiple reasons for that excitement and go through that we announced an exciting new portfolio today knows to not the culmination. It's a continuation off our journey, a bunch of new products that we launched today Hyper scaler X as a new integrated data protection appliance. We've also announced new offerings in data protection, backup and recovery, disaster recovery and complete data protection and lots of exciting updates for Hedwig and a couple of weeks like we introduced updates for metallic. So, yes, it's been a really exciting pain. Also, today happens to be the data, and we got to know that we are the leader in Gartner Magic Quadrant for the ninth consecutive. I am so a lot of goodness today for us. >>Excellent. Lots of areas that we definitely want to dig deep in to the pieces done. You know, we just heard a little bit about Hedvig was an acquisition a year ago that everybody's kind of looking at and saying Okay, you know, will this make them compete against some of their traditional partners? How we get integrated in So, baby, just give us one level deeper on the Hedvig piece on what that means to the portfolio? Yeah, sure, So I >>guess I mean, one of the key things that the random mentioned was the fact that had hyper scale that's is built off the head Day files. So that's a huge milestone for us. As we teased out maybe 10 months ago. Remember, Tomball, Go on the Cube and talking about, you know, kind of what our vision and strategy was of unifying data and storage management. Those hyper hyper scale X applying is a definite milestone improving out that direction. But beyond just the hyper scale ECs, we've also been driving on some of the more primary or modern workloads such as containers and the really interesting stuff we've come out with your recently is the kubernetes native integration that ties in all of the advanced component of the head to distribute storage architecture on the platform itself across multi cloud and on premise environments, making it really easy and policy driven. Um, for Dev, ops users and infrastructure users, the tie ins applications from a group, Friction >>Great and Mercer. There's some updates to the partner program and help us understand how all of these product updates they're gonna affect the kind of the partnerships and alliances beasts that you want. >>Absolutely. So in the time since our last meeting that go in the fall, which is actually right after I had just doing combo, we spent a good portion of the following six months really talking with partners, understanding the understand the impact of the partner program that we introduced last summer, looking at the data and really looking at barriers to evolve the program, which fell around three difference specific. Once you bet one was simplicity of the simplicity of the program, simplicity of understanding, rewards, levers and so forth. The second was paying for value was really helping, helping our partners to be profitable around things like deal registration on other benefits and then third was around co investment. So making sure that we get the right members in place to support our partners and investing in practices. Another training, another enablement around combo and we launched in over these things last week is a part of an evolution of that program. Today is a great follow on because in addition to all of the program evolutions that we we launched last week now we have an opportunity with our partners to have many more opportunities or kind of a thin into the wedge to open up new discussions with our customers now around all of these different use cases and capabilities. So back to that simplification angle, really driving more and more opportunities for those partners toe specific conversations around use cases. >>Okay, for this next question, I think it makes sense for you to start. Maybe maybe Don, you can get some commentary in two. But when he's firstly the announcements, there are some new products in the piece that you discuss but trying to understand, you know, when you position it, you know, do you call the portfolio? Is it a platform? You know, if I'm an existing Conn Volt customer, you know, how do I approach this? If I use something like metallic, how does that interplay with some of the new pieces that were discussed today. >>Sure, I can take the business. I'm sure Don and mostly will have more data to it. The simplest way to think about it is as a port for you. But contrary to how you would think about portfolio as independent products, what we have is a set off data management services granular. We're very aligned to the use case, which can all inter operate with each other. So maybe launched backup and recovery and disaster recovery. These can be handled separately, purchased separately and deployed standalone or for customers who want a combination of those capabilities. We also have a complete data protection are fine storage optimization, data governance E discovery in complaints are data management services that build on top off any of these capabilities now a very differentiating factor in our platform owners. All the services that you're talking about are delivered off the same software to make it simpler to manage to the same year. So it's very easy to start with one service and then just turn on the license and go to other services so I can understand the confusion is coming from but it's all the same. The customer simplicity and flexibility in mind, and it's all delivered off the same platform. So it is a portfolio built on a single Don. Would you like to add more to it? >>Yeah, I think the interesting thing due to add on top of that is where we're going with Hedvig Infrastructure, the head of distributed storage platform, uh, to to run this point, how everything is integrated and feed and work off of one another. That's the same idea that we have. We talked about unifying data and storage manager. So the intricate storage architecture components the way data might be maneuvered, whether it's for kubernetes for virtual machines, database environments, secondary storage, you name it, um, we are. We're quickly working to continue driving that level of of unification and integration between the portfolio and heads storage, distribute storage platforms and also deliver. So what you're seeing today going back to, I think wrong his first point. It's definitely not the culmination. It's just another step in the direction as we continue to innovate and integrate this >>product, and I think for our partners what this really does, it allows them to sell around customer use cases because it'll ask now if I have a d. Our use case. I can go after just PR. If I have a backup use case, I can just go after backup, and I don't have to try to sell more than that. Could be on what the customer is looking for in parallel that we can steal these things in line with the customer use case. So the customer has a lot of remote offices. They want to scale Hedvig across those they want to use the art of the cloud. They can scale these things independently, and it really gives us a lot of optionality that we didn't have before when we had a few monolithic products. >>Excellent. Really reminds me more of how I look at products if I was gonna go buy it from some of the public cloud providers living in a hybrid cloud. World, of course, is what your customers are doing. Help us understand a little bit, you know, Mercer talked about metallic and the azure partnership, but for the rest of the products, the portfolio that we're talking about, you know, does this >>kind >>of work seamlessly across my own data center hosting providers Public Cloud, you know, how does this fit into the cloud environment for your customer? >>Yes, it does. And I can start with this one goes to, um it's our strategy is cloud first, right? And you see it in every aspect of our product portfolio. In fact, I don't know if you got to see a keynote today, but Ron from Johns Hopkins University was remarking that comment has the best cloud native architectures. And that's primarily because of the innovation that we drive into the multi cloud reality. We have very deep partnerships with pretty much all the cloud vendors, and we use that for delivering joint innovation, a few things that when you think of it from a hybrid customers perspective, the most important need for them is to continue working on pram while still leveraging the cloud. And we have a lot of optimization is built into that, and then the next step of the journey is of course, making sure that you can recover to the cloud would be it work load. Typically your data quality and there's a lot of automation that we provide to our solutions and finally, Of course, if you're already in the cloud, whether you're running a science parents or cloud native, our software protects across all those use cases, either true sass with metallic auto downloadable software, backup and recovery so we can cover the interest victims of actual presence. You. We do definitely help customers in every stage of their hybrid cloud acceleration journey. >>And if you take a look at the Hedvig protect if you take a look at the head back to, um, the ability to work in a cloud native fast, it is essentially a part of the DNA of that storage of the storage, right? So whether you're running on Prem, whether you're running it about adjacent, set up inside the cloud head, that can work with any compute environment and any storage environment that you went to essentially then feed, we build this distributed storage, and the reason that becomes important. It's pretty much highlighted with our announcement around the kubernetes and container support is that it makes it really easy to start maneuvering data from on Prem to the cloud, um, from cloud to cloud region to region, sort of that high availability that you know as customers make cloud first a reality and their organizations starts to become a critical requirement or ensuring the application of and some of the things that we've done now with kubernetes in making all of our integration for how we deliver storage for the kubernetes and container environments and being that they're completely kubernetes native and that they can support a Google in AWS and Azure. And of course, any on premises community set up just showcases the value that we can provide in giving them that level of data portability. And it basically provides a common foundation layer, or how any sort of the Dev ops teams will be operating in the way that those state full container state workloads. Donna Oh, sorry. Go >>ahead, mark area >>because you mentioned the metallic and azure partnership announcement and I just want to get on that. And one thing that run dimension, which is we are really excited about the announcement of partnership with Microsoft and all the different news cases that opens up that are SAS platform with Azure with office 3 65 and all of the great application stack it's on. If you're at the same time, to run this point. We are a multi cloud company. And whether that is other of the hyper scale clouds Mess GC, P. Ali at Oracle and IBM, etcetera, or Oliver, Great service writer burners. We continue to believe in customer choice, and we'll continue to drive unique event innovations across all of those platforms. >>All right, Don, I was wondering if we could just dig in a little bit more on some other kubernetes pieces you were talking about. Let me look at just the maturation of storage in general. You know, how do we had state back into containers in kubernetes environments? Help us see, You know what you're hearing from your customers. And you know how you how you're ready to meet their needs toe not only deliver storage, but as you say, Really? You know, full data protection in that environment? >>Certainly it So I mean, there's been a number of enhancements that happened in the kubernetes environment General over the last two years. One of the big ones was the creation of what the visit environment calls a persistent volume. And what that allows you to do is to really present storage to a a communities application. Do it be typically through what's called a CSR container storage interface that allows for state full data to be written, storage and be handled and reattached applications as you leverage them about that kubernetes. Um, as you can probably imagine that with the addition of the additional state full applications, some of the overall management now of stateless and state collapse become very talent. And that's primarily because many customers have been using some of the more traditional storage solutions to try to map that into these new state. Full scenario. And as you start to think about Dev ops organization, most Dev ops organizations want to work in the environment of their choice. Whether that's Google, whether that's AWS, Microsoft, uh, something that might be on Prem or a mix of different on Prem environments. What you typically find, at least in the kubernetes world, is there's seldom ever one single, very large kubernetes infrastructure cluster that's set to run, Dev asked. The way and production all at once. You usually have this spread out across a fairly global configuration, and so that's where some of these traditional mechanisms from traditional storage vendors really start to fall down because you can apply the same level of automation and controls in every single one of those environments. When you don't control the storage, let's say and that's really where interfacing Hedvig and allowing that sort of extension distribute storage platform brings about all of this automation policy control and really storage execution definition for the state. Full statehood workloads so that now managing the stateless and the state full becomes pretty easy and pretty easy to maintain when it comes to developing another Dev branch or simply trying to do disaster recovery or a J for production, >>any family actively do. That's a very interesting response, and the reality is customers are beginning to experiment with business. Very often they only have a virtual environment, and now they're also trying to expand into continuous. So Hedwig's ability to service primary storage for virtualization as well as containers actually gives their degree of flexibility and freedom for customers to try out containers and to start their contingent. Thank you familiar constructs. Everything is mellow where you just need to great with continuous >>Alright, bring a flexibility is something that I heard when you talk about the portfolio and the pricing as to how you put these pieces together. You actually talked about in the presentation this morning? Aggressive pricing. If you talk about, you know, kind of backup and recovery, help us understand, You know, convo 2020 how you're looking at your customers and you know how you put together your products, that to meet what they need at that. As you said, aggressive pricing? >>Absolutely. And you use this phrase a little bit earlier is to blow like flexibility. That's exactly what we're trying to get to the reason why we are reconstructing our portfolio so that we have these very granular use case aligned data management services to provide the cloud like flexibility. Customers don't have the same data management needs all the time. Great. So they can pick and choose the exact solution that need because there are delivered on the same platform that can enable out the solution investment, you know, And that's the reality. We know that many of our customers are going to start with one and keep adding more and more services, because that's what we see as ongoing conversations that gives us the ability to really praise the entry products very aggressively when compared to competition, especially when we go against single product windows. This uses a lot of slammed where we can start with a really aggressively priced product and enable more capabilities as we move forward to give you an idea, we launched disaster recovery today. I would say that compared to the so the established vendors India, we would probably come in at about 25 to 40% of the Priceline because it depends on the environment and what not. But you're going to see that that's the power of bringing to the table. You start small and then depending on what your needs are, you have the flexibility to run on either. More data management capabilities are more workloads, depending on what your needs will be. I think it's been a drag from a partner perspective, less with muscle. If you want a little bit more than that, >>yes, I mean, that goes back to the idea of being ableto simply scale across government use functionality. For example, things like the fact that our disaster recovery offering the Newman doesn't require backup really allows us to have those Taylor conversations around use cases, applications >>a >>zealous platforms. You think about one of the the big demands that we've had coming in from customers and partners, which is help me have a D R scenario or a VR set up in my environment that doesn't require people to go put their hands on boxes and cables, which was one of those things that a year ago we were having. This conversation would not necessarily have been as important as it is now, but that ability to target those specific, urgent use cases without having to go across on sort of sell things that aren't necessarily associated with the immediate pain points really makes those just makes us ineffective. Offer. >>Yeah, you bring up some changing priorities. I think almost everybody will agree that the number one priority we're hearing from customers is around security. So whether I'm adopting more cloud, I'm looking at different solutions out there. Security has to be front and center. Could we just kind of go down the line and give us the update as to how security fits and all the pieces we've been discussing? >>I guess I'm talking about change, right, so I'll start. The security for us is built into everything that we do the same view you're probably going to get from each of us because security is burden. It's not a board on, and you would see it across a lot of different images. If you take our backup and recovery and disaster recovery, for instance, a lot of ransomware protection capabilities built into the solution. For instance, we have anomaly detection that is built into the platform. If we see any kind of spurious activity happening all of a sudden, we know that that might be a potential and be reported so that the customer can take a quick look at air Gap isolation, encryption by default. So many features building. And when you come to disaster recovery, encryption on the wire, a lot of security aspects we've been to every part of the portfolio don't. >>Consequently, with Hedvig, it's probably no surprise that when that this platform was developed and as we've continued development, security has always been at the core of what we're doing is stored. So what? It's for something as simple as encryption on different volume, ensuring the communication between applications and the storage platform itself, and the way the distributors towards platform indicates those are all incredibly secured. Lock down almost such for our own our own protocols for ensuring that, um, you know, only we're able to talk within our own, our own system. Beyond that, though, I mean it comes down to ensure that data in rest data in transit. It's always it's always secure. It's also encrypted based upon the level of control that using any is there one. And then beyond just the fact of keeping the data secure. You have things like immutable snapshots. You have declared of data sovereignty to ensure that you can put essentially virtual fence barriers for where data can be transported in this highly distributed platform. Ah, and then, from a user perspective, there's always level security for providing all seeking roll on what groups organization and consume storage or leverage. Different resource is the storage platform and then, of course, from a service provider's perspective as well, providing that multi tenanted access s so that users can have access to what they want when they want it. It's all about self service, >>and the idea there is that obviously, we're all familiar with the reports of increased bad actors in the current environment to increased ransomware attacks and so forth. And be a part of that is addressed by what wrong and done said in terms of our core technology. Part of that also, though, is addressed by being able to work across platforms and environments because, you know, as we see the acceleration of state tier one applications or entire data center, evacuations into service provider or cloud environments has happened. You know, this could have taken 5 10 years in a in a normal cycle. But we've seen this happen overnight has cut this. Companies have needed to move those I T environments off science into managed environments and our ability to protect the applications, whether they're on premises, whether they're in the cloud or in the most difficult near where they live. In both cases, in both places at once, is something that it's really important to our customers to be able to ensure that in the end, security posture >>great Well, final thing I have for all three of you is you correctly noted that this is not the end, but along the journey that you're going along with your customers. So you know, with all three of you would like to get a little bit. Give us directionally. What should we be looking at? A convo. Take what was announced today and a little bit of look forward towards future. >>Directionally we should be looking at a place where we're delivering even greater simplicity to our customers. And that's gonna be achieved through multiple aspects. 1st 1 it's more technologies coming together. Integrating. We announced three important integration story. We announced the Microsoft partnership a couple of weeks back. You're gonna see us more longer direction. The second piece is technology innovation. We believe in it. That's what Differentiators has a very different company and we'll continue building it along the dimensions off data awareness, data, automation and agility. And the last one continued obsession with data. What more can we do with it? How can we drive more insights for our customers We're going to see is introducing more capabilities along those dimensions? No. >>And I think Rhonda tying directly into what you're highlighting there. I'm gonna go back to what we teased out 10 months ago at calm Bolt. Go there in Colorado in this very on this very program and talk about how, in the unification of ah ah, data and storage management, that vision, we're going to make more and more reality. I think the, uh, the announcements we've made here today let some of the things that we've done in between the lead up to this point is just proof of our execution. And ah, I can happily and excitedly tell you, we're just getting warmed up. It's going to be, ah, gonna be some fun future ahead. >>And I think studio in the running that out with the partner angle. Obviously, we're going to continue to produce great products and solutions that we're going to make our partners relevant. In those conversations with customers, I think we're also going to continue to invest in alternative business models, services, things like migration services, audit services, other things that build on top of this core technology to provide value for customers and additional opportunities for our partners >>to >>build out their their offerings around combo technologies. >>All right, well, thank you. All three of you for joining us. It was great to be able to dig in, understand those pieces. I know you've got lots of resources online for people to learn more. So thank you so much for joining us. Thank you too. Thank you. Alright, and stay with us. So we've got one more interview left for the Cube's coverage of con vault. Future Ready, students. Mannan. Thanks. As always for watching the Cube. Yeah, Yeah, yeah, yeah, yeah, yeah

>> from our studios in the heart of Silicon Valley, Palo Alto, California. It is a cute conversation. >> Everyone. Welcome to this Special Cube conversation here at the Palo Alto Cube Studios. I'm John for a host of Cuba here. Moritz man is the head of the product management team at Open Systems A G. Great to see you again. Thanks for coming in. >> Hey, John. Thanks for having me. >> So last time we spoke, you had your event in Las Vegas. You guys are launching. You have a new headquarters here in Silicon Valley. Opened up this past spring. Congratulations. Thank you. >> Yeah, it's a great, great venue to start, and we set foot on the Silicon Valley ground. So to make our way to >> I know you've been super busy with the new building and rolling out, expanding heavily here in the Valley. But you guys were in the hottest area that we're covering Security Cloud security on premise, security. The combination of both has been the number one conversation pretty much in the cloud world right now. Honestly, besides a normal cloud, native cloud I t hybrid versus multi cloud out. See, that continues to be the discussion I think there's no more debate around multi cloud in hybrid public clouds. Great people gonna still keep their enterprises. But the security equation still is changing this new requirements. What's the latest that you guys are seeing with respect to security? >> Yeah. So, John, what we see is actually that cloud adoption had happens at different speeds. So you have usually the infrastructure of the service. Adoption would happens in a quite controlled way because there's a lift in shift. Do you have your old data center? You you take it and you transferred into azure I W S O G C P. But then there's also uncontrolled at option, which is in the SAS space. And I think this is where a lot off data risk occur, especially the wake off GDP are on where we see that this adoption happens. Maurin a sometimes control, but sometimes in a very uncontrolled way, >> explain that the uncontrolled and controlled expansion of of how security and multi cloud and cloud is going because this interesting control means this this plan's to do stuff uncontrolled means it's just by other forces explain uncontrolled versus controls >> eso controlled specifically means the IittIe team takes as a project plan and aches servers and workloads and moves them in a controlled fashion or in a dedicated project to the cloud. But what happened in the business world of business I t is actually did use those share content at any time with any device at any at any time and in all locations. So this is called the Mobile Enterprise on the Cloud First Enterprise. So it means that the classical security perimeter and the controls in that are my past, actually, by the path of least resistance or the shortest path >> available. And this is the classic case. People use Dropbox with some, you know, personal things. They're at home, they're at work, a p I based software. That's what you're getting at the >> and the issue of this is that that the data that has bean, like contained an pera meters where, you know, as it Caesar, where your data is. This has bean deployed too many edge devices, too many mobile devices, and it's get it gets shared, a nun controlled way. >> We'll get a couple talk tracks would like to drill down on that, because I think this is the trend. We're seeing a pea eye's dominant. The perimeter on the infrastructure has gone away. It's only getting bigger and larger. You got I, O. T and T Edge just and the networks are controlled and also owned by different people. So the packets of moving on it that's crazy so that that's the reality. First, talk track is the security challenge. What is the security challenge? How does a customer figure out what to do from an architectural standpoint when they're dealing with hybrid and multi cloud? So first of >> all, um, customers or BC enterprises try need to re think their infrastructure infrastructure centric view off the architecture's. So the architecture that had been built around data send us needs to become hybrid and multi cloud aware. So that means they need to define a new way off a perimeter, which is in cloud but also in the covering. Still the old, so to say, legacy hyper data center set up, which has the data still in the old data center and at the same time, they need to open up and become the cloud themselves, so to say, and but still draw a perimeter around their data and they users and not and their applications and not so much anymore around the physical infrastructure. >> So taking, changing their view of what a security product is, Is that really what you're getting at? >> Yeah, So the issues with the product point solution was that they fixed a certain part off off a tactile issue. So if you take a firewall in itself, firewall back then it was like a entry door to a big building, and you could could decide who comes out goes in. Now. If the the kind of the walls of the building are vanishing or arm or more FIC, you need to come over the more integrated concept. So having these stacked appliance and stacked security solutions trying to work together and chain them doesn't work anymore. So we think and we see that, >> Why is that? Why doesn't it work? Because in >> the end, it's it's it's hardly two to operate them. Each of those points solutions have their own end off life. They have their own life cycle. They have their own AP eyes. They have their own TCO, as all that needs to be covered. And then there's the human aspect where you have the knowledge pools around >> those technologies. So as an enterprise you have to content to continuously keep the very scar security experts to maintain content continues the depreciating assets running right, >> and they're also in it. We weren't built for tying into a holistic kind of platform. >> Yeah, What we see is that that enterprises now realize we have data centers and it's not accepted reality that you can abstracted with the cloud. So you have You don't own your own servers and buildings anymore. So you have a PAX model to subscribe to Cloud Service is and we think that this has to happen to security to so shift from cap ex to our pecs and the same way also for operational matters >> securities. The service is a crepe is a small I want to ask you on that front you mentioned mobile users. How do you secure the mobile uses when they use cloud collaboration? Because this is really what uses expect, and they want How do you secure it? >> So be secured by by actually monitoring the data where it actually gravitates, and this is usually in the cloud. So we enforce the data that is in transit through, ah, proxies and gators towards the cloud from the endpoint devices, but also then looking by AP eyes in the cloud themselves to look for threats, data leakage and also sandbox. Certain activities that happened. There >> are the next talk talk I want to get into is the expansion to hybrid and multi cloud so that you guys do from a product standpoint, solution for your customers. But in general, this is in the industry conversation as well. How how do you look at this from a software standpoint? Because, you know, we've heard Pat Gelsinger of'em were talking about somewhere to find Data Center S d n. Everything's now software based. You talk about the premiere goes away. You guys were kind of bring up a different approaches. A software perimeter? Yeah, what is the challenge for expanding to multi cloud and hybrid cloud? >> So So the challenge for enterprise and customers we talked to is that they have to run their old business. Gardner once called it by motile business, and it's still adopting not one cloud, but we see in our surveys. And this is also what market research confirms is that customers end up with 2 to 3 loud vendors. So there were will be one or two platforms that will be the primary to their major majority of applications and data gravity. But they will end up and become much more flexible with have running AWS, the old Davis Center. But it was the G, C, P and Azure, or Ali Baba glowed even side by side, right tow cover the different speeds at what their own and the price runs. And >> so I gotta ask you about Cloud Needed was one of the things that you're bringing up that just jumps in my head. And when I got to ask, because this is what I see is a potential challenge. It might be a current challenges when you have kubernetes growing such a rapid rate. You see the level of service is coming online much higher rate. So okay, people, mobile users, they're using the drop boxes, the boxes and using all these FBI service's. But that's just those wraps. As a hundreds and thousands of micro service is being stood up and Tauron down in there, you guys are taking, I think, an approach of putting a perimeter software premieres around these kinds of things, but they get turned on enough. How do you know what's clean? It's all done automatically, so this is becoming a challenge. So is this what you guys mean when you say software perimeter that you guys could just put security around things at any time? Is that explain this? >> Yeah, So? So if you talk about the service match so really mashing cloudy but native functions, I think it's still in the face where it's, I would say, chaos chaotic when you have specific projects that are being ramped up them down. So we draw a perimeter in that specific contact. So let's say you have You're ramping up a lot off cloud a function AWS. We can build a pyramid around this kind off containment and look especially for threats in the activity locks off. The different component is containers, but from from a design perspective, this needs to be, uh, we need to think off the future because if you look at Mike soft on AWS strategy, those containers will eventually move Also back to the edge. Eso were in preparing that to support those models also cover. Bring these functions closer back again to the edge on We call that not any longer the when, ej but it will become a cloud at at actually. So it's not an extension of the land that comes to the data. It's actually the data and the applications coming back to the user and much closer. >> Yeah. I mean, in that case, you could define the on premises environment has an edge, big edge, because this is all about moving, were close and data around. This is what the new normal is. Yeah, So okay, I gotta ask the next question, which is okay, If that's true, that means that kubernetes becomes a critical part of all this. And containers. How do you guys play with that at all? >> So we play with us by by actually looking at data coming from that at the moment. We're looking at this from a from a data transit perspective. We But we will further Maur integrate into their eighties AP eyes and actually become part off the C I C D. Process that building then actually big become a security function in approval and rolling out a cannery to certain service mesh. And we can say, Well, this is safe for this is unsafe This is, I think, the eventual goal to get there. But But for now, it's It's really about tracking the locks of each of those containers and actually having a parent her and segmentation around this service mash cloud. So to say, >> I think you guys got a good thing going on when you talk about this new concept that's of softer to find perimeter. You can almost map that to anything you get. Really think everything has its own little perimeter workload. Could be moving around still in these three secure. So I gotta ask on the next talk Trek is this leads into hybrid cloud. This is the hottest topic. Hybrid cloud to me is the same as multi cloud. Just kind of get together a little bit different. But hybrid cloud means you're operating both on premises and in the cloud. This is becoming a channel most si si SOS Chief admission Security officers. I don't want to fork their teams and have multiple people coding different stacks. They don't want the vendor lock in, and so you're seeing a lot of people pulling back on premises building their own stacks, deploying in the cloud and having a seamless operation. What is your definition of hybrid? Where do you see hybrid going? And how important is it? Have a hybrid strategy. >> So I think the key successfactors of a hybrid strategy is that standards standardization is a big topic. So we think that a service platform that to secure that like the SD when secure service platform rebuilt, needs to be standardized on operational level, but also from a baseline security and detection level. And this means that if you run and create your own work, those on Prem you need to have the same security and standard security and deployment standard for the clout and have the seamless security primary perimeter and level off security no matter where these these deployments are. And the second factor of this is actually how do you ensure a secure data transfer between those different workloads? And this is where S T win comes into play, which acts as a fabric together with when backbone, where we connect all those pieces together in a secure fashion >> where it's great to have you on the Q and sharing your insight on the industry. Let's get into your company. Open systems. You guys provide an integrated solution for Dev Ops and Secure Service and Security Platform. Take a minute to talk about the innovations that you guys were doing because you guys talk a lot about Casby. Talk a lot about integrated esti when but first define what Casby is for. The audience doesn't know what Casby is. C. A S B. It's kicked around all of the security conscious of your new to security. It's an acronym that you should pay attention to so defined casby and talk about your solution. >> Eso casby isn't theory. Aviation means cloud access security we broker. So it's actually becoming this centralized orchestrator that that allows and defines access based on a trust level. So saying, um, first of all, it's between networks saying I have a mobile workforce accessing SAS or I s applications. Can't be it in the middle to provide security and visibility about Where's my data moving? Where's married? Where do I have exposure off off GDP, our compliance or P C. I or he power risks And where is it exposed to, Which is a big deal on it's kind of the lowest level to start with, But then it goes further by. You can use the Casby to actually pull in data that that is about I s were close to toe identified data that's being addressed and stored. So are there any incidentally, a shared data artifacts that are actually critical to the business? And are they shared with extra resource is and then going one step further, where we then have a complete zero trust access model where we say we know exactly who can talkto which application at any time on give access to. But as everything this needs to be is in embedded in an evolution >> and the benefit ultimately goes to the SAS applications toe, have security built in. >> That's the first thing that you need to tackle. Nowadays, it's get your sass, cloud security or policy enforced on, but without disrupting service on business on to actually empower business and not to block and keep out the business >> can make us the classic application developer challenge, which is? They love to co they love the build applications, and what cloud did with Dev Ops was abstracted away the infrastructure so that they didn't have to do all this configuration. Sister. Right? APs You guys air enabling that for security? >> Exactly. Yeah. So coming back to this multi protein product cloud would, which is not keeping up anymore with the current reality and needs of a business. So we took the approach and compared death ops with a great service platform. So we have engineers building the platform. That's Integrated Security Service Platform, which promotes Esti Wen managed Detection response and Caspi Service is in one on the one platform which is tightly integrated. But in the in the customer focus that we provide them on or Pecs model, which is pretty, very predictable, very transparent in their security posture. Make that a scalable platform to operate and expand their business on. >> And that's great. Congratulations. I wanna go back for the final point here to round up the interview for the I T. Folks watching or, um, folks who have to implement multi cloud and hybrid cloud they're sitting there could be a cloud architect that could be an I T. Operations or 90 pro. They think multi cloud this in hybrid club. This is the environment. They have to get their arms around. How? What >> should they >> be thinking about? Around multi cloud and hybrid cloud. What is it, really? What's the reality now? What >> should they be considering for evaluation? What are some of the key things that that should be on their mind when they're dealing with hybrid cloud and all the opportunity around it? >> So I think they're they're like, four key pieces. Oneness. Um, they think they still have to start to think strategic. So what? It's a platform and a partner That helps them to plan ahead for the next 3 to 5 years in a way that they can really focus on what their business needs are. This is the scalability aspect. Secondly, it's a do. We have a network on security, our architecture that allows me to grow confidently and go down different venues to to actually adopt multi clouds without worrying about the security implication behind it. Too much, uh, and to implement it. And third is have this baseline and have this standardized security posture around wherever the data is moving, being at Mobil's being it SAS or being on Prem and in clouds workloads, the fourth pieces again, reading, thinking off where did you spend most of my time? Where do I create? Create value by by defining this framework so it really can create a benefit and value for the enterprise? Because if you do it not right your not right. You will have a way. You will end up with a an architecture that will break the business and not accelerated. >> Or it's made head of product that open systems here inside the Cube studios. Um, great job. Must love your job. You got the keys. A lot of pressure. Security being a product. Head of product for security companies. A lot of pressure before we wrap up. Just give a quick plug for the company. You guys hiring you have a new office space here in Redwood City. Looks beautiful. Give a quick shared play for the company. >> Yeah. So open systems the great company to work with. We're expanding in the U. S. On also, Amy, uh, with all the work force. So we're hiring. So go on our website. We have a lot off open positions, exciting challenges in a growth or into workspace. Andi. Yeah. As you said, security at the moment, it's one of the hottest areas to be in, especially with all the fundamental changes happening in the enterprise and architecture. I d landscape. So yeah, >> and clouds securing specifically. Not just in point. The normal stuff that people used to classify as hot as hot as Hades could be right now. But thanks for coming on. Strong insights. I'm jumping with Cuba here in Palo Alto with more Morris Man is the head of product management for open systems. Thanks for watching.

>> live from Las Vegas. It's the queue covering Dell Technologies. World twenty nineteen. Brought to you by Dell Technologies and its ecosystem partners. >> The one Welcome to the Special Cube Live coverage here in Las Vegas with Dell Technologies World 2019. I'm John Furrier with Dave Vellante breaking down day one of three days of wall the wall Coverage - 2 Cube sets. Uh, big news today and dropping here. Dell Technology World's series of announcements Cloud ability, unified work spaces and then multi cloud with, uh, watershed announced with Microsoft support for VMware with Azure are guests here theCUBE alumni that Seo, senior leader of'Em Where Sanjay *** and such a great to see you, >> John and Dave always a pleasure to be on your show. >> So before we get into the hard core news around Microsoft because you and Satya have a relationship, you also know Andy Jassy very well. You've been following the Clouds game in a big way, but also as a senior leader in the industry and leading BM where, um, the evolution of the end user computing kind of genre,  that whole area is just completely transformed with mobility and cloud kind of coming together with data and all this new kinds of applications. The modern applications are different. It's changing the game on how end users, employees, normal people use computing because some announcement here on their What's your take on the ever changing role of cloud and user software? >> Yeah, John, I think that our vision , as  you know, it was the first job I came to do at VMware almost six years ago, to run and use a computing. And the vision we had at that time was that you should be able to work at the speed of life, right? You and I happen to be on a plane at the same time  yesterday coming here, we should be able to pick our amps up on our devices. You often have Internet now even up at thirty thousand feet. In the consumer world, you don't lug around your CDs, your music, your movies come to you. So the vision of any app on any device was what we articulated with the digital workspace We. had Apple and Google very well figured out. IOS later on Mac,  Android,  later on chrome . The Microsoft relationship in end use the computing was contentious because we overlapped. They had a product, PMS and in tune. But we always dreamed of a day. I tweeted out this morning that for five and a half years I competed with these guys. It was always my dream to partner with the With Microsoft. Um, you know, a wonderful person, whom I respect there, Brad Anderson. He's a friend, but we were like LeBron and Steph Curry. We were competing against each other. Today everything changed. We are now partners. Uh, Brad and I we're friends, we'll still be friends were actually partners  now why? Because we want to bring the best of the digital workspace solution VMware brings workspace one to the best of what Microsoft brings in Microsoft 365 , active directory, E3 capabilities around E. M. S and into it and combined those together to help customers get the best for any device. Apple, Google and Microsoft that's a game changer. >> Tell about the impact of the real issue of Microsoft on this one point, because is there overlap is their gaps, as Joe Tucci used to say, You can't have any. There's no there's no overlap if you have overlapped. That's not a >> better to have overlapped and seems right. A gaps. >> So where's the gaps? Where this words the overlapping cloud. Next, in the end user world, >> there is a little bit of overlap. But the much bigger picture is the complementarity. We are, for example, not trying to be a directory in the Cloud That's azure active directory, which is the sequel to Active Directory. So if we have an identity access solution that connect to active directory, we're gonna compliment that we've done that already. With Octo. Why not do that? Also inactive Directory Boom that's clear. Ignored. You overlap. Look at the much bigger picture. There's a little bit of overlap between in tune and air Watch capabilities, but that's not the big picture. The big picture is combining workspace one with E. M s. to allow Office 365 customers to get conditional access. That's a game, so I think in any partnership you have to look past, I call it sort of these Berlin Wall moments. If the U. S and Soviet Union will fighting over like East Germany, vs West Germany, you wouldn't have had that Berlin wall moment. You have to look past the overlaps. Look at the much bigger picture and I find the way by which the customer wins. When the customer wins, both sides are happy. >> Tearing down the access wall, letting you get seamless. Access the data. All right, Cloud computing housely Multi cloud announcement was azure something to tell on stage, which was a surprise no one knew was coming. No one was briefed on this. It was kind of the hush hush, the big news Michael Delll, Pat Girl singer and it's nothing to tell up there. Um, Safia did a great job and really shows the commitment of Microsoft with the M wear and Dell Technologies. What is this announcement? First, give us your take an analysis of what they announced. And what does it mean? Impact the customers? >> Yeah, listen, you know, for us, it's a further That's what, like the chess pieces lining up of'Em wars vision that we laid up many years for a hybrid cloud world where it's not all public cloud, it isn't all on premise. It's a mixture. We coined that Tom hybrid loud, and we're beginning to see that realize So we had four thousand cloud providers starting to build a stack on VM, where we announced IBM Cloud and eight of us. And they're very special relationships. But customers, some customers of azure, some of the retailers, for example, like Wal Mart was quoted in the press, released Kroger's and some others so they would ask us, Listen, we're gonna have a way by which we can host BMO Workloads in there. So, through a partnership now with Virtue Stream that's owned by Dell on DH er, we will be able to allow we, um, where were close to run in Virtue Stream. Microsoft will sell that solution as what's called Azure V M, where solutions and customers now get the benefit of GMO workloads being able to migrate there if they want to. Or my great back on the on premise. We want to be the best cloud infrastructure for that multi cloud world. >> So you've got IBM eight of us Google last month, you know, knock down now Azure Ali Baba and trying you. Last November, you announced Ali Baba, but not a solution. Right >> now, it's a very similar solutions of easy solution. There's similar what's announced with IBM and Nash >> So is it like your kids where you loved them all equally or what? You just mentioned it that Microsoft will sell the VM wear on Azure. You actually sell the eight of us, >> so there is a distinction. So let me make that clear because everything on the surface might look similar. We have built a solution that is first and preferred for us. Called were MacLeod on a W s. It's a V m er manage solution where the Cloud Foundation stack compute storage networking runs on a ws bare metal, and V. Ember manages that our reps sell that often lead with that. And that's a solution that's, you know, we announced you were three years ago. It's a very special relationship. We have now customer attraction. We announce some big deals in queue, for that's going great, and we want it even grow faster and listen. Eight of us is number one in the market, but there are the customers who have azure and for customers, one azure very similar. You should think of this A similar to the IBM ah cloud relationship where the V C P. V Partners host VM where, and they sell a solution and we get a subscription revenue result out of that, that's exactly what Microsoft is doing. Our reps will get compensated when they sell at a particular customer, but it's not a solution that's managed by BM. Where >> am I correct? You've announced that I think a twenty million dollars deal last quarter via MacLeod and A W. And that's that's an entire deal. Or is that the video >> was Oh, that was an entirely with a customer who was making a big shift to the cloud. When I talked to that customer about the types of workloads, they said that they're going to move hundreds off their APs okay on premise onto via MacLeod. And it appears, so that's, you know, that's the type of cloud transformation were doing. And now with this announcement, there will be other customers. We gave an example of few that Well, then you're seeing certain verticals that are picking as yours. We want those two also be happy. Our goal is to be the undisputed cloud infrastructure for any cloud, any cloud, any AP any device. >> I want to get your thoughts. I was just in the analysts presentation with Dell technology CFO and looking at the numbers, the performance numbers on the revenue side Don Gabin gap our earnings as well as market share. Dell. That scales because Michael Delll, when we interviewed many years ago when it was all going down, hinted that look at this benefits that scale and not everyone's seeing the obvious that we now know what the Amazon scale winds so scale is a huge advantage. Um, bm Where has scale Amazon's got scale as your Microsoft have scales scales Now the new table stakes just as an industry executive and leader as you look at the mark landscape, it's a having have not world you'd have scale. You don't If you don't have scale, you're either ecosystem partner. You're in a white space. How do companies compete in this market? Sanjay, what's your thoughts on I thinkit's >> Jonah's? You said there is a benefit to scale Dell, now at about ninety billion in revenue, has gone public on their stock prices. Done where Dellvin, since the ideal thing, the leader >> and sir, is that point >> leader in storage leader inclined computing peces with Vienna and many other assets like pivotal leaders and others. So that scale VM, Where about a ten billion dollar company, fifth largest software company doing verywell leader in the softer to find infrastructure leader, then use a computing leader and softer, defined networking. I think you need the combination of scale and speed, uh, just scale on its own. You could become a dinosaur, right? And what's the fear that every big company should have that you become ossified? And I think what we've been able to show the world is that V M wear and L can move with scale and speed. It's like having the combination of an elephant and a cheetah and won and that to me special. And for companies like us that do have scaled, we've to constantly ask ourselves, How do we disrupt ourselves? How do we move faster? How do we partner together? How do we look past these blind spots? How do we pardon with big companies, small companies and the winner is the customer. That's the way we think. And we could keep doing that, you'll say so. For example, five, six years ago, nobody thought of VMware--this is going before Dell or EMC--in the world of networking, quietly with ten thousand customers, a two million dollar run rate, NSX has become the undisputed leader and software-defined networking. So now we've got a combination of server, storage and a networking story and Dell VMware, where that's very strong And that's because we moved with speed and with scale. >> So of course, that came to an acquisition with Nice Sarah. Give us updates on the recent acquisitions. Hep C e o of Vela Cloud. What's happening there? >> Yeah, we've done three. That, I think very exciting to kind of walk through them in chronological order about eighteen months ago was Velo Cloud. We're really excited about that. It's sort of like the name, velocity and cloud fast. Simple Cloud based. It is the best solution. Ston. How do we come to deciding that we went to talk to our partners like t other service providers? They were telling us this is the best solution in town. It connects to the data center story to the cloud story and allows our virtual cloud network to be the best softer. To find out what you can, you have your existing Mpls you might have your land infrastructure but there's nobody who does softer to find when, like Philip, they're excited about that cloud health. We're very excited about that because that brings a multi cloud management like, sort of think of it like an e r P system on top of a w eso azure to allow you to manage your costs and resource What ASAP do it allows you to manage? Resource is for materials world manufacturing world. In this world, you've got resources that are sitting on a ws or azure. Uh, cloud held does it better than anybody else. Hefty. Oh, now takes a Cuban eighty story that we'd already begun with pivotal and with Google is you remember at at PM world two years ago. And that's that because the founders of Cuban eighties left Google and started FTO. So we're bringing that DNA we've become now one of the top two three contributors to communities, and we want to continue to become the de facto platform for containers. If you go to some of the airports in San Francisco, New York, I think Keilani and Heathrow to you'LL see these ads that are called container where okay, where do you think the Ware comes from Vienna, where, OK, and our goal is to make containers as container where you know, come to you from the company that made vmc possible of'Em where So if we popularized PM's, why not also popularised the best enterprise contain a platform? That's what helped you will help us do >> talk about Coburn at ease for a minute because you have an interesting bridge between end user computing and their cloud. The service is micro. Services that are coming on are going to be powering all these APS with either data and or these dynamic services. Cooper, Nettie sees me the heart of that. We've been covering it like a blanket. Um, I'm gonna get your take on how important that is. Because back Nelson, you're setting the keynote at the Emerald last year. Who burn it eases the dial tone. Is Cooper Netease at odds with having a virtual machine or they complimentary? How does that evolving? Is it a hedge? What's the thoughts there? >> Yeah, First off, Listen, I think the world has begun to realize it is a world of containers and V ems. If you looked at the company that's done the most with containers. Google. They run their containers in V EMS in their cloud platform, so it's not one or the other. It's vote. There may be a world where some parts of containers run a bare metal, but the bulk of containers today run and Beyonce And then I would say, Secondly, you know, five. Six years ago, people all thought that Doctor was going to obliterate VM where, But what happened was doctors become a very good container format, but the orchestration layer from that has not become daugher. In fact, Cuban Eddie's is kind of taking a little of the head and steam off Dr Swarm and Dr Enterprise, and it is Cooper Navy took the steam completely away. So Senses Way waited for the right time to embrace containers because the obvious choice initially would have been some part of the doctor stack. We waited as Borg became communities. You know, the story of how that came on Google. We've embraced that big time, and we've stated a very important ball hefty on All these moves are all part of our goal to become the undisputed enterprise container platform, and we think in a multi cloud world that's ours to lose. Who else can do multi cloud better than VM? Where may be the only company that could have done that was Red Hat. Not so much now, inside IBM, I think we have the best chance of doing that relative. Anybody else >> Sanjay was talking about on our intro this morning? Keynote analysis. Talking about the stock price of Dell Technologies, comparing the stock price of'Em where clearly the analysis shows that the end was a big part of the Dell technologies value. How would you summarize what v m where is today? Because on the Kino there was a Bank of America customers. She said she was the CTO ran, she says, Never mind. How we got here is how we go floors the end wars in a similar situation where you've got so much success, you always fighting for that edge. But as you go forward as a company, there's all these new opportunities you outlined some of them. What should people know about the VM? We're going forward. What is the vision in your words? What if what is VM where >> I think packed myself and all of the key people among the twenty five thousand employees of'Em are trying to create the best infrastructure company of all time for twenty one years. Young. OK, and I think we have an opportunity to create an incredible brand. We just have to his use point on the begins show create platforms. The V's fear was a platform. Innocent is a platform workspace. One is a platform V san, and the hyper convert stack of weeks right becomes a platform that we keep doing. That Carbonetti stuff will become a platform. Then you get platforms upon platforms. One platforms you create that foundation. Stone now is released. ADelle. I think it's a better together message. You take VX rail. We should be together. The best option relative to smaller companies like Nutanix If you take, you know Veum Where together with workspace one and laptops now put Microsoft in the next. There's nobody else. They're small companies like Citrix Mobile. I'm trying to do it. We should be better than them in a multi cloud world. They maybe got the companies like Red Hat. We should have bet on them. That said, the end. Where needs toe also have a focus when customers don't have Dale infrastructure. Some people may have HP servers and emcee storage or Dell Silvers and netapp storage or neither. Dellery emcee in that case, usually via where, And that's the way we roll. We want to be relevant to a multi cloud, multi server, multi storage, any hardware, any cloud. Any AP any device >> I got. I gotta go back to the red hat. Calm in a couple of go. I could see you like this side of IBM, right? So So it looks like a two horse race here. I mean, you guys going hard after multi cloud coming at it from infrastructure, IBM coming at it with red hat from a pass layer. I mean, if I were IBM, I had learned from VM where leave it alone, Let it blossom. I mean, we have >> a very good partisan baby. Let me first say that IBM Global Services GTS is one about top sai partners. We do a ton of really good work with them. Uh, I'm software re partner number different areas. Yeah, we do compete with red hat with the part of their portfolios. Relate to contain us. Not with Lennox. Eighty percent plus of their businesses. Lennox, They've got parts of J Boss and Open Stack that I kind of, you know, not doing so well. But we do compete with open ship. That's okay, but we don't know when we can walk and chew gum so we can compete with Red Hat. And yet partner with IBM. That's okay. Way just need to be the best at doing containing platform is better than open shifter. Anybody, anything that red hat has were still partner with IBM. We have to be able to look at a world that's not black and white. And this partnership with Microsoft is a good example. >> It's not a zero sum game, and it's a huge market in its early days. Talk >> about what's up for you now. What's next? What's your main focus? What's your priorities? >> Listen, we're getting ready for VM World now. You know in August we want to continue to build momentum on make many of these solutions platforms. So I tell our sales reps, take the number of customers you have and add a zero behind that. OK, so if you've got ten thousand customers of NSX, how do we get one hundred thousand customers of insects. You have nineteen thousand customers of Visa, which, by the way, significantly head of Nutanix. How do we have make one hundred ninety thousand customers? And we have that base? Because we have V sphere and we have the Delll base. We have other partners. We have, I think, eighty thousand customers off and use of computing tens of millions of devices. How do we make sure that we are workspace? One is on billion. Device is very much possible. That's the vision. >> I think that I think what's resonating for me when I hear you guys, when you hear you talk when we have conversations also in Pat on stage talks about it, the simplification message is a good one and the consistency of operating across multiple environments because it sounds great that if you can achieve that, that's a good thing. How you guys get into how you making it simple to run I T. And consistent operating environment. It's all about keeping the customer in the middle of this. And when we listen to customs, all of these announcements the partnership's when there was eight of us, Microsoft, anything that we've done, it's about keeping the customer first, and the customer is basically guiding up out there. And often when I sit down with customers, I had the privilege of talking hundreds of thousands of them. Many of these CEOs the S and P five hundred I've known for years from S athe of'Em were they'LL Call me or text me. They want us to be a trusted advisor to help them understand where and how they should move in their digital transformation and compared their journey to somebody else's. So when we can bring the best off, for example, of developer and operations infrastructure together, what's called DEV Ops customers are wrestling threw that in there cloud journey when we can bring a multi device world with additional workspace. Customers are wrestling that without journey there, trying to figure out how much they keep on premise how much they move in the cloud. They're thinking about vertical specific applications. All of these places where if there's one lesson I've learned in my last ten twenty years of it has become a trusted advisor to your customers. Lean on them and they will lean on you on when you do that. I mean the beautiful world of technology is there's always stuff to innovate. >> Well, they have to lean on you because they can't mess around with all this infrastructure. They'LL never get their digital transformation game and act together, right? Actually, >>= it's great to see you. We'Ll see you at PM, >> Rollo. Well, well, come on, we gotta talk hoops. All right, All right, All right, big. You're a big warriors fan, right? We're Celtics fan. Would be our dream, for both of you are also Manny's themselves have a privileged to go up against the great Warriors. But what's your prediction this year? I mean, I don't know, and I >> really listen. I love the warriors. It's ah, so in some senses, a little bit of a tougher one. Now the DeMarcus cousins is out for, I don't know, maybe all the playoffs, but I love stuff. I love Katie. I love Clay, you know, and many of those guys is gonna be a couple of guys going free agents, so I want to do >> it again. Joy. Well, last because I don't see anybody stopping a Celtics may be a good final. That would be fun if they don't make it through the rafters, though. That's right. Well, I Leonard, it's tough to make it all right. That sounds great. >> Come on. Sanjay Putin, CEO of BM Wear Inside the Cube, Breaking down his commentary of you on the landscape of the industry and the big news with Microsoft there. Other partner's bringing you all the action here Day one of three days of coverage here in the Cubicle two sets a canon of cube coverage out there. We're back with more after this short break.

>> Hello everyone. Welcome to this CUBE conversation. I'm John Furrier host like you here in our Palo Alto studio here in Palo Alto. Here with Dominic Wilde, known as Dom, CEO of SnapRoute, a hot new startup. A great venture. Backers don. Welcome to skip conversation. So love having to start ups. And so talk about Snape route the company because you're doing something interesting that we've been covering your pretty aggressively the convergence between Dev Ops and Networking. We've known you for many, many years. You were a former Hewlett Packard than you woodpecker enterprise running the networking group over there. You know, networking. And you're an operator. Snap rows. Interesting, because, um, great names back behind it. Big venture backers. Lightspeed Norwest, among others. Yes. Take a minute. Explain what? A SnapRoute. >> So SnapRoute was founded to really address one of the big, big problems we see in infrastructure, which is that, you know, essentially the network gets in the way of the deployment the rapid and angel deployment of applications. And so in the modern environment that we're in, you know, the business environment, highly competitive environment of disruption, continuous disruption going on in our industry, every company out there is constantly looking over their shoulder is, you know, making sure that they're moving fast enough there innovating fast enough that they don't want to be disrupted. They don't want to be overrun by, you know, a new upstart. And in order to do that, you know the application is is actually the work product that you really want to deploy, that you you want to roll out, and you want to be able to do that on a continuous basis. You want to be really agile about how you do it. And, quite frankly, when it comes to infrastructure, networking has been fifteen years behind the rest of the infrastructure and enabling that it's, ah, it's a big roadblock. It's obviously, you know, some of the innovations and developments and networking of lag behind other areas on what we snap Brown set out to do was to say, You know, look, if we're if we're going to bring networking forward and we're going to try and solve some of these problems, how do we do that? In a way, architecturally, that will enable networking to become not just a part of Ah, you know a cloud native infrastructure but actually enable those those organizations to drive forward. And so what we did was we took all of our sort of devops principles and Dev ups tools, and we built a network operating system from the ground up using devops principles, devops architectures and devops tools. And so what we're delivering is a cloud native network operating system that is built entirely on containers and is delivered is a micro services architecture on the big...one of the big value propositions that we deliver is what we call see a CD for networking, which is your continuous integration. Continuous deployment is obviously, you know, Big devops principal there. But doing that for networking, allowing a network to be constantly up enabling network Teo adapt to immutable infrastructure principles. You know we're just replacing pieces that need to be replaced. Different pieces of the operating system can be replaced If there's a security vulnerability, for instance, or if there's ah, bugger and you feature needed so you know we can innovate quicker. We can enable the network to be more reliable, allow it to be more agile, more responsive to the needs of the organization on all of this, fundamentally means that your Operation shins model now becomes ah, lot more unified. A lot more simple. You. Now, we now enable the net ox teams to become a sort of more native part of the conversation with devils. Reduce the tension there, eliminate any conflicts and everything. And we do that through this. You know, this innovative offices. >> Classically, the infrastructure is code ethos. >> Yeah, exactly right. I mean, it's you know, a lot of people have been talking about infrastructure is code for a long, long time. But what we really do, I mean, if if you deploy our network operating system you employ onto the bare metal switching, then you really enable Dev ops to hang have, you know, I take control and to drive the network in the way they want using their native tool chains. So, you know, Cuba Netease, for instance, ears. You know that the big growing dev ops orchestration to all of the moment. In fact, we think it's more than of the moment. You know, I've never seen in the industry that sort of, you know, this kind of momentum behind on open source initiative like there is behind Cuba. Netease. And we've taken communities and baked it natively into the operating system. Such that now our network operating system that runs on a physical switch can be a native part off that communities and develops tool >> Dom, I want to get to the marketplace, dynamics. Kind of what's different. Why now? But I think what's interesting about SnapRoute you're the chief of is that it's a venture back with big names? Yeah. Lightspeed, Norwest, among others. It's a signal of a wave that we've been covering people are interested in. How do you make developers deploy faster, more agility at scale, on premises and in clouds. But I want you to before we get there, want to talk about the origin story of company? Yeah. Why does it exist? How did it come to bear you mentioned? Operation is a big part of cloud to cloud is about operating model so much a company. Yes. This is the big trend. That's the big way. But how did it all get started? What's the SnapRoute story? >> Yeah, it's an interesting story. Our founders were actually operators at at Apple back in the day, and they were responsible for building out some of Apple's biggest. You know, data centers for their sort of customer facing services, like, you know, like loud iTunes, all those good things and you know they would. They were tasked with, sort of, you know, sort of modernizing the operational model with with those data centers and, you know, and then they, like many other operators, do you know, had a sense of community and worked with their peers. You know, another big organizations, even you know, other hyper scale organizations and wanted to learn from what they did on DH. What they recognised was that, you know, cos like, you know, Google and Facebook and Microsoft is urine things. They had done some incredible things and some incredible innovations around infrastructure and particularly in networking, that enabled them to Dr Thie infrastructure from A from a Devil ops perspective and make it more native. But those words that if you know, fairly tailored for there, if you know, for their organizations and so what they saw was the opportunity to say, Well, you know, there's there's many other organizations who are delivering, you know, infrastructure is a service or SAS, or you know, who are just very large enterprises who are acting as these new cloud service providers. And they would have a need to, you know, to also have, you know, tools and capabilities, particularly in the network, to enable the network to be more responsive, more to the devil apps like. And so, you know, they they they founded SnapRoute on that principle that, you know, here's the problem that we know we can solve. It's been solved, you know, some degree, but it's an architectural problem, and it's not about taking, You know, all of the, you know, the last twenty five years of networking knowledge and just incrementally doing a sort of, you know, dot upgrade and, you know, trying to sort of say, Hey, we're just add on some AP eyes and things. You really needed to start from the ground up and rethink this entirely from an architectural perspective and design the network operating system as on with Dev ups, tools and principles. So they started the company, you know, been around just very late two thousand fifteen early two thousand sixteen. >> And how much money have you read >> The last around. We are Siri's, eh? We took in twenty five million. >> And who were the venture? >> It was Lightspeed Ventures on DH Norwest. And we also had some strategic investment from Microsoft Ventures and from teams >> from great name blue chips. What was their interest? What was their thesis? Well, and you mentioned the problem. What was the core problem that you're solving that they were attracted to? Why would that why was the thirst with such big name VCs? >> Yeah, I mean, I think it was, you know, a zip said, I think it's the the opportunity to change the operational more. And I think one of the big things that was very different about our company is and, you know, we like to say, you know, we're building for effort. Operators, by operators, you know, I've found is, as I said, well, more operators from Apple, they have lived and breathed what it is to be woken up at three. A. M. On Christmas Eve toe. You know, some outage and have to, you know, try and figure that out and fight your way through a legacy kind of network and figure out what's going on. So you know, so they empathize with what that means and having that DNA and our company is incredibly meaningful in terms of how we build that you know the product on how we engage with customers. We're not just a bunch of vendors who you know we're coming from, you know, previous spender backgrounds. Although I do, you know, I bring to the table the ability to, you know, to deliver a package and you know, So there's just a cloud scale its clouds, Gail. It's it's but it's It's enabling a bridge if you like. If you look at what the hyper scales have done, what they're achieving and the operational models they have, where a if you like a bridge to enable that capability for a much broader set of operators and C. S. P s and as a service companies and dry forward a an aggressive Angela innovation agenda for companies, >> businesses. You know, we always discussing the Cuban. Everyone who watches the Kiev knows I'm always ranting about how cloud providers make their market share numbers, and lot of people include sass, right? I think everyone will be in the SAS business, so I kind of look at the SAS numbers on, say, it's really infrastructures service platform to service Amazon, Google, Microsoft and then, you know, Ali Baba in China. Others. Then you got IBM or one of it's kind of in the big kind of cluster there top. That is a whole nother set of business requirements that sass driven this cloud based. Yeah, this seems to be a really growing market. Is that what you're targeting? And the question is, how do you relate Visa? Visa Cooper? Netease trend? Because communities and these abstraction layers, you're starting to hear things like service mesh, policy based state Full application states up. Is that you trying to that trend explain. >> We're very complimentary, Teo. Those trends, we're, you know, we're not looking to replace any of that, really. And and my big philosophy is, if you're not simplifying something, then you're not really adding back here, you know, what you're doing is complicating matters or adding another layer on top. So so yeah, I mean, we are of value to those companies who are looking at hybrid approaches or have some on prime asset. Our operating system will land on a physical, bare metal switch So you know what? What we do is when you look at it, you know, service most is your message measures and all the other, You know, technologies you talked about with very, very complimentary to those approaches because we're delivering the on underlying network infrastructure on network fabric. Whatever you'd like to call it, that can be managed natively with class native tools, squeezing the alliteration there. But but, you know, it means that you don't need toe add overlays. We don't need to sort of say, Hey, look, the network is this static, archaic thing that's really fragile. And And I mean, if we touch it, it's going to break. So let's just leave it alone and let's let's put some kind of overlay over the top of it on do you know, run over the top? What we're saying is you can collapse that down. Now what you can say, what you can do is you can say, Well, let's make the network dynamic responsive. Let's build a network operating system out of micro services so you can replace parts of it. You can, you know, fix bugs. You can fix security vulnerabilities and you can do all that on the fly without having to schedule outage windows, which is, you know, for a cloud native company or a sass or infrastructure service company. I mean, that's your business. You can't take outage windows. Your business depends on being available all the time. And so we were really changing that fundamentals of a principle of networking and saying, You know, networking is now dynamic, you know, in a very, very native way, but it also integrates very closely with Dev ops. Operational model >> is a lot of innovation that network. We're seeing that clearly around the industry. No doubt everyone sees late and see that comes into multi Cloud was saying that the trend moving the data to the compute coyote again that's a network issue network is now an innovation opportunity. So I gotta ask you, where do you guys see that happening? And I want to ask you specifically talking about the cloud architects out in the marketplace in these enterprises who were trying to figure out about the architecture of clowns. So they know on premises there, moving that into a cloud operations. We see Amazon, they see Google and Microsoft has clouds that might want to engage with have cloud native presence in a hybrid and multi cloud fashion for those cloud architects. What are the things that you like to see them doing? More of that relates to your value problems. In other words, if they're using containers or they're using micro services, is this good or bad? What? What you should enterprise to be working on that ties into your value proposition. >> So I think about this the other way around, actually, if I can kind of turn that turn that question. But on his head, I think what you know, enterprises, you know, organization C, S. P s. I think what they should be doing is focusing on their business and what their business needs. They shouldn't be looking at their infrastructure architecture and saying, you know, okay, how can we, you know, build all these pieces? And then you know what can the business and do on top of that infrastructure? You wanna look at it the other way around? I need to deploy applications rapidly. I need to innovate those applications. I need to, you know, upgrade, change whatever you need to do with those applications. And I need an infrastructure that can be responsive. I need an infrastructure that can be hybrid. I need infrastructure that can be, you know, orchestrated in the hybrid manner on DH. Therefore, I want to go and look for the building blocks out there of those those architectural and infrastructure building blocks out there that can service that application in the most appropriate way to enable the velocity of my business and the innovation from my business. Because at the end of the day, I mean, you know, when we talk to customers, the most important thing T customers, you know, is the velocity of their business. It is keeping ahead in the highly competitive environment and staying so far ahead that you're not going to be disrupted. And, you know, if any element of your infrastructure is holding you back and even you know, you know the most mild way it's a problem. It's something you should address. And we now have the capability to do that for, you know, for many, many years. In fact, you know, I would claim up to today without snap route that you know, you you do not have the ability to remove the network problem. The network is always going to be a boat anchor on your business. It introduces extra cycles. It introduces big security, of underplaying >> the problems of the network and the consequences that prior to snap her out that you guys saw. >> So I take the security issue right? I mean, everybody is very concerned about security today. One of the biggest attack vectors in the security world world today is the infrastructure. It's it's it's so vulnerable. A lot of infrastructure is is built on sort of proprietary software and operating systems. You know, it's very complex. There's a lot of, you know, operations, operational, moves out and change it. So there's there's a lot of opportunity for mistakes to be made. There's a lot of opportunity for, you know, for vulnerabilities to be exposed. And so what you want to do is you want to reduce the threat surface of, you know, your your infrastructure. So one of the things that we can do it SnapRoute that was never possible before is when you look at a traditional network operating system. Andreas, A traditional. I mean, any operating system is out there, other you know, Other >> than our own. >> It's basically a monolithic Lennox blob. It is one blob of code that contains all of the features. And it could be, you know, architect in in a way that it Sze chopped up nicely. But if you're not using certain features, they're still there. And that increases the threat surface with our sat proud plant native network operating system. Because it is a micro services are key picture. If you are not using certain services or features, you can destroy and remove the containers that contain those features and reduce the threat surface of the operating system. And then beyond that, if you do become aware ofthe vulnerability or a threat that you know is somewhere in there, you can replace it in seconds on the fly without taking the infrastructure. Damn, without having to completely replace that whole blob of software causing, you know, an outage window. So that's just one example of, you know, the things we can do. But even when it comes to simple things, like, you know, adding in new services or things because we're containerized service is a ll boot together. It's no, eh? You know it doesn't. It doesn't have a one after the other. It it's all in parallel. So you know this this operating system comes up faster. It's more reliable. It eliminates the risk factors, the security, you know, the issues that you have. It provides native automation capabilities. It natively integrates with, You know, your Dev Ops tool chain. It brings networking into the cloud. Native >> really, really isn't in frustrations. Code is an operating system, so it sounds like your solution is a cloud native operating system. That's correct. That's pretty much the solution. That's it. How do customers engage with you guys? And what do you say? That cloud architect this is Don't tell me what to do. What's the playbook, right? How you guys advice? Because I see this is a new solution. Talk about the solution and your recommendation to architects as they start thinking about building that elastic in that flexible environment. >> Yeah. I mean, I think you know, Ah, big recommendation is, you know, is to embrace, you know, that all the all of the cloud native principles and most of the companies that were talking to, you know, definitely doing that and moving very quickly. But, you know, my recommendation. You know, engaging with us is you should be looking for the network to in naval, your your goals and your you know your applications rather than limiting. I mean, that's that's the big difference that, you know, the people who really see the value in what we do recognize that, you know, the network should be Andi is an asset. It should be enabling new innovation, new capabilities in the business rather than looking at the network as necessary evil where we you know, where we have to get over its limitations or it's holding us back. And so, you know, for any organization that is, you know, is looking at deploying, you know, new switching infrastructure in any way, shape or form. I think, you know, you should be looking at Well, how am I going to integrate this into a dev ops? You know, world, how may going to integrate this into a cloud native world. So as my business moves forward, I'm actually servicing the application in enabling a faster time to service for the application for the business. At the end of the day, that's that's everybody's going, >> you know, we've been seeing in reporting this consistently, and it's even more mainstream now that cloud computing has opened up the aperture of the value and the economics and also the technical innovation around application developers coding faster having the kind of resource is. But it also created a CZ creating a renaissance and networking. So the value of networking and application development that collision is coming together very quickly. So the intersection you guys play. So I'm sure this will resonate well with customers Will as they try to figure out the role the network because against security number one analytics all the things that go into what Sadiq they care about share data, shared coat all this is kind of coming together. So if someone hears this story, they'll go, OK, love this snap around store. I gotta I gotta dig in. How do they engage you? What do you guys sell to them? What's the pitch? Give the quick plug for the company real >> quick. Engaging with us is, you know, is a simple issue. No, come to www snapper out dot com. And you know, you know contacts are up there. You know, we were currently obviously we're a small company. We sell direct, more engaged with, you know, our first customers and deploying our product, you know, right now, and it's going very, very well, and, you know, it's a PSE faras. You know how you know what and when to engage us. I would say you can engage us at any stage and and value whether or not your architect ing a whole new network deploying a new data center. Obviously. Which is, you know, it is an ideal is built from the ground up, but we add value to the >> data center preexisting data saying that wants >> the modernizing data centers. I mean, very want >> to modernize my data center, my candidate. >> So one of the biggest challenges in an existing data center in when one of the biggest areas of tension is at the top of rack switch the top of racks, which is where you connect in your you know, your your application assets, your servers are connected. You're connecting into the into the, you know, first leap into the network. One of the challenges there is. You know, Dev ops engineers, They want Teo, you know, deploy containers. They want to deploy virtual machines they wantto and stuff move stuff, change stuff and they need network engineers to help them to do that. For a network engineer, the least interesting part of the infrastructure is the top Arax. Which it is a constant barrage day in, day, out of request. Hey, can I have a villain? Can have an i p address. Can we move this? And it's not interesting. It just chews up time we alleviate that tension. What we enable you to do is network engineer can you know, deploy the network, get it up and running, and then control what needs to be controlled natively from their box from debits tool chains and allow the devil ups engineers to take control as infrastructure. So the >> Taelon is taking the stress out of the top of racks. Wedge, take the drama out of this. >> Take that arm around the network. Right. >> So okay, you have the soul from a customer. What am I buying? What do you guys offering? Is that a professional services package? Is it software? Is it a sad solution? Itself is the product. >> It is software, you know. We are. We're selling a network operating system. It lands on, you know, bare metal. He liked white box switching. Ah, nde. We offer that as both perpetual licenses or as a subscription. We also office, um, you know, the value and services around that as well. You know, Andre, right now that is, you know, that is our approach to market. You know, we may expand that, you know, two other services in the future, but that is what we're selling right now. It is a network operating >> system down. Thanks for coming and sharing this story of SnapRoute. Final question for you is you've been in this century. While we've had many conversations we'd love to talk about gear, speeds and feeds. I'll see softwares eating. The world was seeing that we're seeing cloud create massive amounts. Opportunity. You're in a big wave, right? What is this wave look like for the next couple of years? How do you see this? Playing out as Cloud continues to go global and you start to Seymour networking becoming much more innovative. Part of the equation with Mohr developers coming onboard. Faster, more scale. How do you see? It's all playing out in the industry. >> Yeah. So I think the next sort of, you know, big wave of things is really around the operational. But I mean, we've we've we've concentrated for many years in the networking industry on speeds and feeds. And then it was, you know, it's all about protocols and you know how protocol stacks of building stuff. That's all noise. It's really about How do you engage with the network? How do you how do you operate your network to service your business? Quite frankly, you know, you should not even know the network is there. If we're doing a really good job of network, you shouldn't even know about it. And that's where we need to get to is an industry. And you know that's that's my belief is where, where we can take >> it. Low latent. See programmable networks. Great stuff. SnapRoute Dominic. While no one is dominant industry friend of the Cube also keep alumni CEO of Snapper Out. Hot new start up with some big backers. Interesting signal. Programmable networks software Cloud Global all kind of big Party innovation equation. Here in Silicon Valley, I'm showing for with cube conversations. Thanks for watching