>>Hello, uh, welcome to everyone. Uh, my name is Carlos lights. I'm a HP managing director, Portugal. Um, I have the privilege today where we make Hable, which is the business to business director for Altis Portugal. Uh, Paul, thank you very much. I want to start by faith you for your presence and availability to be with us today and to be able to share a few words about our partnership in particular use of our it consumption model, uh, as a service. So HP ring like, Oh, uh, maybe it's a good, uh, is a good way to start explaining a little bit about Altis right out. This is a multinational organization. Uh, you have presence in four countries, France, Portugal, Israel, and Dominica in a week, but today we will focus on, uh, on Portugal. Right. So could you please polo, uh, tell us about the Altis Portugal and, uh, your company's vision follow. >>Okay. Hello, Carlos, thank you very much for the invitation and regarding your question. Well, all this protocol was born as a telephone operator and after a few decades of transformation, namely on the B2B markets is now the leading Portuguese player in ICT. We have positioned ourselves as the preferred partner for digital transformation of organizations, both private and public. We have a large portfolio of an ICT portfolio of products and customized solutions from IOT, BPO, security payments, and many other areas. And we are committed to achieve a more competitive, collaborative, digital, and low carbon economy through our in-house products and our partner solutions like HBA, uh, regarding cloud. We have a decade of cloud presence in the market, uh, based on five data centers network that we have here in Portugal that are operating since 1999. Uh, so we have made this cloud journey with a strong focus on managing value added services, serving both in years and also top organizations. Uh, we started to believe that as a country, we cannot achieve the level of modernization and automation of operational models, or even the relation of company's cost structure without the throng and widespread adoption of a model as a set of display, as you go a lot of liken services, >>Paul, um, you know, um, as well, companies are currently, uh, facing many challenge, uh, and looking for solutions that address to their needs, but also, uh, should be future proof. Right? So how do you see everybody's cloud role on the elping, uh, achieve business goals and requirements? >>Well, uh, cloud approach is, are becoming a priority on organizations and customers are increasingly aware of the, of their solutions to their needs. So what coffee has shown us is how important is the agility flexibility, and thank to markets we all needed to bring, as far as you could, new solutions to the market, increase digital means and accomplished the use new workplace information because we are all working now, I'm in the office, I mean at house. And so what we see here in Portugal is that cloud enabled organizations were better prepared to this challenge and prior management visitations within companies, I think that will probably be now overcome by new decision-makers and some, so some verticals like healthcare banking got public administration, they have tight retirements, tight requirements on compliance that the security control. And I think that these are some of the verticals where only in a nightmarish cloud approach we'll compare unite with all these called VC cities. >>And so I think that under the present situation, budgets constraints, efficiency, and predictability are even more present at decision-making process. And I don't think that traditional it models will no longer cope with this challenge. And so therefore, uh, every thought strategy are presently delivering customers the best of both worlds. They want simplified it provisioning and operational LSD city, but never, but then nevertheless are compelled to keep that close to home when that the protection is critical and compliance, and that the governments are to shop every cloud service services supported by the right partners tools like GreenLake central. I think that will be the key to achieve a single as a service experience from edge to plow. They allow the security and of control of a non-brand model, along with the corporate agility and the OPEX flexibility so much demanded by our clients. >>So BOLO, uh, regarding the experience, uh, fortunately we have a ready common contracts and common customers, right? And the, well, from your experience, uh, what do you think are the benefits customers are getting from each beaming? Like, can you share some examples use cases? >>Okay. Of course. Well, uh, as I said before, HBA brings to the table a key differentiator, which is the GreenLake central. We have one portal to manage all cloud on prem having at the same time, the control, the easy to use and better capacity to plan future needs. So it serves both it finance and legal teams giving the proper visibility to all of these stakeholders. In terms of examples, we have customers that are using GreenLake to suppose, suppose private and public sector. We have implementations both at Altis and customers' premises that the centers on a very diverse type of business apps from mission critical help, sometimes legacy to SAP or some cloud native apps. For instance, we have solutions of stars as a service for the energy sector on the transport sector and a data center as a service on public administration on customers that need to keep the it on prem because of compliance, but look for the cloud flexibility and the model as a service. >>Good. I see, uh, I see in fact, uh, a positive, a very positive future, uh, in our partnership, but, uh, w what is your opinion about that, uh, uh, how you see the partnership with HP and, uh, and the position to, to give you the ability to even have more success? >>Well, I'm putting this question, talking a little bit about the near future. I think that the short to medium term, the future, uh, will be concentrating on solving possible endemic crisis and sell both customers and ourselves service providers. Uh, we faced this challenge and I think that we were able to cope with these challenges on 2021. And we are very supported on technology and digital solutions. And I think that with the help of HPA, we are being able to, to pass this reality check, uh, and under such critical circumstances. But now we need to step forward. We need to leverage the increase e-comm levels. Remote work breath is a way of in there. So we need to go towards the digital transformation of organizations. We need to extend the infrastructure to where business happens. Uh, we have to infuse cloud closer to the network. We are telco allowing for a new class of cloud native and innovative applications for customers. >>Some verticals where LTC is aiming for a new position, also urge for closer collaboration with called partners like HPA, for instance, e-health will bring us new opportunities in the near future. And the proper ICT foundations are crucial for the new health care services, patient focused approaches and that the driven decisions and being cloud markets made sure. Now, I think that some companies still count on their partners to facilitate the cloud journey, helping them underline the business cases on cloud users apart consulting skills to facilitate change, bring peers use cases that can easily apply NHPA is the most value for out. It says much to bring the new cloud technology, but also the existing experience, the use casing, the use cases and helping us go through the learning curve in other markets. So, uh, for the future, we hope for the best, and we will count on a leading partner like HPA to drivers too, >>On these uncertain, but promising future. Good. I want to reinforce the, thank you very much for your shares. Share this content, this information with us. Uh, it was a real, it is a real pleasure to work with you. Uh, it's a pleasure for all your work without these as a company, but as well, personally, we, your follow and the, because I think it's important to wherever address relationship, and we have now the trust relationship with the organization and with personally as well. So thank you very much, Paulo, and have a nice day. Thank you. Thank you. Thank you very much..

>>Okay, welcome back everyone. There's the cubes coverage of VMware Explorer, 22 formerly world. We've been here since 2010 and world 2010 to now it's 2022. And it's VMware Explorer. We're here at the CEO, regular writer. Welcome back to the cube. Great to see you in person. >>Yeah. Great to be here in person, >>Dave and I are, are proud to say that we've been to 12 straight years of covering VMware's annual conference. And thank you. We've seen the change in the growth over time and you know, it's kind of, I won't say pinch me moment, but it's more of a moment of there's the VMware that's grown into the cloud after your famous deal with Andy jazzy in 2016, we've been watching what has been a real sea change and VMware since taking that legacy core business and straightening out the cloud strategy in 2016, and then since then an acceleration of, of cloud native, like direction under your leadership at VMware. Now you're the CEO take us through that because this is where we are right now. We are here at the pinnacle of VMware 2.0 or cloud native VMware, as you point out on your keynote, take us through that history real quick. Cuz I think it's important to know that you've been the architect of a lot of this change and it's it's working. >>Yeah, definitely. We are super excited because like I said, it's working, the history is pretty simple. I mean we tried running our own cloud cloud air. We cloud air didn't work so well. Right. And then at that time, customers really gave us strong feedback that the hybrid they wanted was a Amazon together. Right. And so that's what we went back and did and the andjay announcement, et cetera. And then subsequently as we were continue to build it out, I mean, once that happened, we were able to go work with the Satia and Microsoft and others to get the thing built out all over. Then the next question was okay, Hey, that's great for the workloads that are running on vSphere. What's the story for workloads that are gonna be cloud native and benefit a lot from being cloud native. So that's when we went the Tansu route and the Kubernetes route, we did a couple of acquisitions and then we started that started paying off now with the Tansu portfolio. And last but not the least is once customers have this distributed portfolio now, right. Increasingly everything is becoming multi-cloud. How do you manage and connect and secure. So that's what you start seeing that you saw the management announcement, networking and security and everything else is cooking. And you'll see more stuff there. >>Yeah know, we've been talking about super cloud. It's kinda like a multi-cloud on steroids kind a little bit different pivot of it. And we're seeing some use cases. >>No, no, it's, it's a very great, it's a, it's pretty close to what we talk about. >>Awesome. I mean, and we're seeing this kind of alignment in the industry. It's kind of open, but I have to ask you, when did you, you have the moment where you said multicloud is the game changer moment. When did you have, because you guys had hybrid, which is really early as well. When was the Raghu? When did you have the moment where you said, Hey, multicloud is what's happening. That's we're doubling down on that go. >>I mean, if you think about the evolution of the cloud players, right. Microsoft really started picking up around the 2018 timeframe. I mean, I'm talking about Azure, right? >>In a big way. >>Yeah. In a big way. Right. When that happened and then Google got really serious, it became pretty clear that this was gonna be looking more like the old database market than it looked like a single player cloud market. Right. Equally sticky, but very strong players all with lots of IP creation capability. So that's when we said, okay, from a supplier side, this is gonna become multi. And from a customer side that has always been their desire. Right. Which is, Hey, I don't want to get locked into anybody. I want to do multiple things. And the cloud vendors also started leveraging that OnPrem. Microsoft said, Hey, if you're a windows customer, your licensing is gonna be better off if you go to Azure. Right. Oracle did the same thing. So it just became very clear. >>I am, I have gone make you laugh. I always go back to the software mainframe because I, I think you were here. Right. I mean, you're, you're almost 20 years in. Yeah. And I, the reason I appreciate that is because, well, that's technically very challenging. How do you make virtualization overhead virtually non-existent how do you run any workload? Yeah. How do you recover from, I mean, that's was not trivial. Yeah. Okay. So what's the technical, you know, analog today, the real technical challenge. When you think about cross cloud services. >>Yeah. I mean, I think it's different for each of these layers, right? So as I was alluding to for management, I mean, you can go each one of them by themselves, there is one way of Mo doing multi-cloud, which is multiple clouds. Right. You could say, look, I'm gonna build a great product for AWS. And then I'm gonna build a great product for Azure. I'm gonna build a great product for Google. That's not what aria is. Aria is a true multi-cloud, which means it pulls data in from multiple places. Right? So there are two or three, there are three things that aria has done. That's I think is super interesting. One is they're not trying to take all the data and bring it in. They're trying to federate the data sources. And secondly, they're doing it in real time and they're able to construct this graph of a customer's cloud resources. >>Right. So to keep the graph constructed and pulling data, federating data, I think that's a very interesting concept. The second thing that, like I said is it's a real time because in the cloud, a container might come and go like that. Like that is a second technical challenge. The third it's not as much a technical challenge, but I really like what they have done for the interface they've used GraphQL. Right? So it's not about if you remember in the old world, people talk about single pan or glass, et cetera. No, this is nothing to do with pan or glass. This is a data model. That's a graph and a query language that's suited for that. So you can literally think of whatever you wanna write. You can write and express it in GraphQL and pull all sorts of management applications. You can say, Hey, I can look at cost. I can look at metrics. I can look at whatever it is. It's not five different types of applications. It's one, that's what I think had to do it at scale is the other problem. And, and >>The, the technical enable there is just it's good software. It's a protocol. It's >>No, no, it's, it's, it's it's software. It's a data model. And it's the Federation architecture that they've got, which is open. Right. You can pull in data from Datadog, just as well as from >>Pretty >>Much anything data from VR op we don't care. Right? >>Yeah. Yeah. So rego, I have to ask you, I'm glad you like the Supercloud cuz you know, we, we think multi-cloud still early, but coming fast. I mean, everyone has multiple clouds, but spanning this idea of spanning across has interesting sequences. Do you data, do you do computer both and a lot of good things happening. Kubernetes been containers, all that good stuff. Okay. How do you see the first rev of multi-cloud evolving? Like is it what happens? What's the sequence, what's the order of operations for a client standpoint? Customer standpoint of, of multicloud or Supercloud because we think we're seeing it as a refactoring of something like snowflake, they're a data base, they're a data warehouse on the cloud. They, they say data cloud they'd they like they'll tell us no, you, we're not a data. We're not a data warehouse. We're data cloud. Okay. You're a data warehouse refactored for the CapEx from Amazon and cooler, newer things. Yeah, yeah, yeah. That's a behavior change. Yeah. But it's still a data warehouse. Yeah. How do you see this multi-cloud environment? Refactoring? Is there something that you see that might be different? That's the same if you know what I'm saying? Like what's what, what's the ne the new thing that's happening with multi-cloud, that's different than just saying I'm I'm doing SAS on the cloud. >>Yeah. So I would say, I would point to a, a couple of things that are different. Firstly, my, the answer depends on which category you are in. Like the category that snowflake is in is very different than Kubernetes or >>Something or Mongo DB, right? >>Yeah. Or Mongo DB. So, so it is not appropriate to talk about one multi-cloud approach across data and compute and so, so on and so forth. So I'll talk about the spaces that we play. Right. So step one, for most customers is two application architectures, right? The cloud native architecture and an enterprise native architecture and tying that together either through data or through networks or through et cetera. So that's where most of the customers are. Right. And then I would say step two is to bring these things together in a more, in a closer fashion and that's where we are going. And that is why you saw the cloud universal announcement and that's already, you've seen the Tansu announcement, et cetera. So it's really, the step one was two distinct clouds. That is just two separate islands. >>So the other thing that we did, that's really what my, the other thing that I'd like to get to your reaction on, cause this is great. You're like a masterclass in the cube here. Yeah, totally is. We see customers becoming super clouds because they're getting the benefit of, of VMware, AWS. And so if I'm like a media company or insurance company, if I have scale, if I continue to invest in, in cloud native development, I do all these things. I'm gonna have a da data scale advantage, possibly agile, which means I can build apps and functionality very quick for customers. I might become my own cloud within the vertical. Exactly. And so I could then service other people in the insurance vertical if I'm the insurance company with my technology and create a separate power curve that never existed before. Cause the CapEx is off the table, it's operating expense. Yep. That runs into the income statement. Yep. This is a fundamental business model shift and an advantage of this kind of scenario. >>And that's why I don't think snowflakes, >>What's your reaction to that? Cuz that's something that, that is not really, talk's highly nuanced and situational. But if Goldman Sachs builds the biggest cloud on the planet for financial service for their own benefit, why wouldn't they >>Exactly. >>And they're >>Gonna build it. They sort of hinted at it that when they were up on stage on AWS, right. That is just their first big step. I'm pretty sure over time they would be using other clouds. Think >>They already are on >>Prem. Yeah. On prem. Exactly. They're using VMware technology there. Right? I mean think about it, AWS. I don't know how many billions of dollars they're spending on AWS R and D Microsoft is doing the same thing. Google's doing the same thing we are doing. Not as much as them that you're doing oral chair. Yeah. If you are a CIO, you would be insane not to take advantage of all of this IP that's getting created and say, look, I'm just gonna bet on one. Doesn't make any sense. Right. So that's what you're seeing. And then >>I think >>The really smart companies, like you talked about would say, look, I will do something for my industry that uses these underlying clouds as the substrate, but encapsulates my IP and my operating model that I then offer to other >>Partners. Yeah. And their incentive for differentiation is scale. Yeah. And capability. And that's a super cloud. That's a, or would be say it environment. >>Yeah. But this is why this, >>It seems like the same >>Game, but >>This, I mean, I think it environment is different than >>Well, I mean it advantage to help the business, the old day service, you >>Said snowflake guys out the marketing guys. So you, >>You said snowflake data warehouse. See, I don't think it's in data warehouse. It's not, that's like saying, you >>Know, I, over >>VMware is a virtualization company or service now is a help desk tool. I, this is the change. Yes. That's occurring. Yes. And that you're enabling. So take the Goldman Sachs example. They're gonna run OnPrem. They're gonna use your infrastructure to do selfer. They're gonna build on AWS CapEx. They're gonna go across clouds and they're gonna need some multi-cloud services. And that's your opportunity. >>Exactly. That's that's really, when you, in the keynote, I talked about cloud universal. Right? So think of a future where we can go to a customer and say, Mr. Customer buy thousand scores, a hundred thousand cores, whatever capacity you can use it, any which way you want on any application platform. Right. And it could be OnPrem. It could be in the cloud, in the cloud of their choice in multiple clouds. And this thing can be fungible and they can tie it to the right services. If they like SageMaker they could tie it to Sage or Aurora. They could tie it to Aurora, cetera, et cetera. So I think that's really the foundation that we are setting. Well, I think, I >>Mean, you're building a cloud across clouds. I mean, that's the way I look at it. And, and that's why it's, to me, the, the DPU announcement, the project Monterey coming to fruition is so important. Yeah. Because if you don't have that, if you're not on that new Silicon curve yep. You're gonna be left behind. Oh, >>Absolutely. It allows us to build things that you would not otherwise be able to do, >>Not to pat ourselves on the back Ragu. But we, in what, 2013 day we said, feel >>Free. >>We, we said with Lou Tucker when OpenStack was crashing. Yeah. Yeah. And then Kubernetes was just a paper. We said, this could be the interoperability layer. Yeah. You got it. And you could have inter clouding cuz there was no clouding. I was gonna riff on inter networking. But if you remember inter networking during the OSI model, TCP and IP were hardened after the physical data link layer was taken care of. So that enabled an entire new industry that was open, open interconnect. Right. So we were saying inter clouding. So what you're kind of getting at with cross cloud is you're kind of creating this routing model if you will. Not necessarily routing, but like connection inter clouding, we called it. I think it's kinda a terrible name. >>What you said about Kubernetes is super critical. It is turning out to be the infrastructure API so long. It has been an infrastructure API for a certain cluster. Right. But if you think about what we said about VSE eight with VSE eight Kubernetes becomes the data center API. Now we sort of glossed over the point of the keynote, but you could do operations storage, anything that you can do on vSphere, you can do using a Kubernetes API. Yeah. And of course you can do all the containers in the Kubernetes clusters and et cetera, is what you could always do. Now you could do that on a VMware environment. OnPrem, you could do that on EKS. Now Kubernetes has become the standard programming model for infrastructure across. It >>Was the great equalizer. Yeah. You, we used to say Amazon turned the data center through an API. It turns, turns of like a lot of APIs and a lot of complexity. Right. And Kubernetes changed. >>Well, the role, the role of defacto standards played a lot into the T C P I P revolution before it became a standard standard. What the question Raghu, as you look at, we had submit on earlier, we had tutorial on as well. What's the disruptive enabler from a defacto. What in your mind, what should, because Kubernetes became kind of defacto, even though it was in the CNCF and in an open source open, it wasn't really standard standard. There's no like standards, body, but what de facto thing has to happen in your mind's eye around making inter clouding or connecting clouds in a, in a way that's gonna create extensibility and growth. What do you see as a de facto thing that the industry should rally around? Obviously Kubernetes is one, is there something else that you see that's important for in an open way that the industry can discuss and, and get behind? >>Yeah. I mean, there are things like identity, right? Which are pretty critical. There is connectivity and networking. So these are all things that the industry can rally around. Right. And that goes along with any modern application infrastructure. So I would say those are the building blocks that need to happen on the data side. Of course there are so many choices as well. So >>How about, you know, security? I think about, you know, when after stuck net, the, the whole industry said, Hey, we have to do a better job of collaborating. And then when you said identity, it just sort of struck me. But then a lot of people tried to sort of monetize private reporting and things like that. So you do you see a movement within the technology industry to do a better job of collaborating to, to solve the acute, you know, security problems? >>Yeah. I think the customer pressure and government pressure right. Causes that way. Yeah. Even now, even in our current universe, you see, there is a lot of behind the scenes collaboration amongst the security teams of all of the tech companies that is not widely seen or known. Right. For example, my CISO knows the AWS CSO or the Microsoft CSO and they all talk and they share the right information about vulnerability attacks and so on and so forth. So there's already a certain amount of collaboration that's happening and that'll only increase. Do, >>Do you, you know, I was somewhat surprised. I didn't hear more in your face about security would, is that just because you had such a strong multi-cloud message that you wanted to get, get across, cuz your security story is very strong and deep. When you get into the DPU side of things, the, you know, the separation of resources and the encryption and I'll end to end >>I'm well, we have a phenomenal security story. Yeah. Yeah. Tell security story and yes. I mean I'll need guilty to the fact that in the keynote you have yeah, yeah, sure time. But what we are doing with NSX and you will hear about some NSX projects as you, if you have time to go to some of the, the sessions. Yeah. There's one called project, not star. Another is called project Watchman or watch, I think it's called, we're all dealing with this. That is gonna strengthen the security story even more. Yeah. >>We think security and data is gonna be a big part of it. Right. As CEO, I have to ask you now that you're the CEO, first of all, I'd love to talk about product with you cuz you're yeah. Yeah. We just great conversation. We want to kind of read thet leaves and ask pointed questions cuz we're putting the puzzle together in real time here with the audience. But as CEO, now you have a lot of discussions around the business. You, the Broadcom thing happening, you got the rename here, you got multi-cloud all good stuff happening. Dave and I were chatting before we came on this morning around the marketplace, around financial valuations and EBIDA numbers. When you have so much strategic Goodwill and investment in the oven right now with the, with the investments in cloud native multi-year investments on a trajectory, you got economies of scale there. >>It's just now coming out to be harvest and more behind it. Yeah. As you come into the Broadcom and or the new world wave that's coming, how do you talk about that value? Cuz you can't really put a number on it yet because there's no customers on it. I mean some customers, but you can't probably some for form. It's not like sales numbers. Yeah. Yeah. How do you make the argument to the PE type folks out there? Like EBIDA and then all the strategic value. What's the, what's the conversation like if you can share any, I know it's obviously public company, all the things going down, but like how do you talk about strategic value to numbers folks? >>Yeah. I mean, we are not talking to PE guys at all. Right. I mean the only conversation we have is helping Broadcom with >>Yeah. But, but number people who are looking at the number, EBIDA kind of, >>Yeah. I mean, you'd be surprised if, for, for example, even with Broadcom, they look at the business holistically as what are the prospects of this business becoming a franchise that is durable and could drive a lot of value. Right. So that's how they look at it holistically. It's not a number driven. >>They do. They look at that. >>Yeah. Yeah, absolutely. So I think it's a misperception to say, Hey, it's a numbers driven conversation. It's a business driven conversation where, I mean, and Hawk's been public about it. He says, look, I look at businesses. Can they be leaders in their market? Yeah. Because leaders get, as we all know a disproportionate share of the economic value, is it a durable franchise that's gonna last 10 years or more, right. Obviously with technology changes in between, but 10 years or more >>Or 10, you got your internal, VMware talent customers and >>Partners. Yeah. Significant competitive advantage. So that's, that's really where the conversation starts and the numbers fall out of it. Got it. >>Okay. So I think >>There's a track record too. >>That culture >>That VMware has, you've always had an engineering culture. That's turned, you know, ideas and problems into products that, that have been very successful. >>Well, they had different engineering cultures. They're chips. You guys are software. Right. You guys know >>Software. Yeah. Mean they've been very successful with Broadcom, the standalone networking company since they took it over. Right. I mean, it's, there's a lot of amazing innovation going on there. >>Yeah. Not, not that I'm smiling. I want to kind of poke at this question question. I'll see if I get an answer out of you, when you talk to Hawk tan, does he feel like he bought a lot more than he thought or does he, did he, does he know it's all here? So >>The last two months, I mean, they've been going through a very deliberate process of digging into each business and certainly feels like he got a phenomenal asset base. Yeah. He said that to me even today after the keynote, right. Is the amazing amount of product capability that he's seeing in every one of our businesses. And that's been the constant frame. >>But congratulations on that. >>I've heard, I've heard Hawk talk about the shift to, to Mer merchant Silicon. Yeah. From custom Silicon. But I wanted to ask you when you look at things like AWS nitro yeah. And graviton and train and the advantage that AWS has with custom Silicon, you see Google and Microsoft sort of Alibaba following suit. Would it benefit you to have custom Silicon for, for DPU? I mean, I guess you, you know, to have a tighter integration or do you feel like with the relationships that you have that doesn't buy you anything? >>Yeah. I mean we have pretty strong relationships with in fact fantastic relationships with the Invidia and Intel and AMD >>Benon and AMD now. >>Yeah. Yeah. I mean, we've been working with the Pendo team in their previous incarnations for years. Right, right. When they were at Cisco and then same thing with the, we know the Melanox team as well as the invi original teams and Intel is the collaboration right. From the get go of the company. So we don't feel a need for any of that. We think, I mean, it's clear for those cloud folks, right. They're going towards a vertical integration model and select portions of their stack, like you talked about, but there is always a room for horizontal integration model. Right. And that's what we are a part of. Right. So there'll be a number of DPU pro vendors. There'll be a number of CPU vendors. There'll be a number of other storage, et cetera, et cetera. And we think that is goodness in an alternative model compared to a vertically integr >>And yeah. What this trade offs, right. It's not one or the other, I mean I used to tell, talk to Al Shugar about this all the time. Right. I mean, if vertically integrated, there may be some cost advantages, but then you've got flexibility advantages. If you're using, you know, what the industry is building. Right. And those are the tradeoffs, so yeah. Yeah. >>Greg, what are you excited about right now? You got a lot going on obviously great event. Branding's good. Love the graphics. I was kind of nervous about the name changed. I likem world, but you know, that's, I'm kind of like it >>Doesn't readily roll off your phone. Yeah. >>I know. We, I had everyone miscue this morning already and said VMware Explorer. So >>You pay Laura fine. Yeah. >>Now, I >>Mean a quarter >>Curse jar, whatever I did wrong. I don't believe it. Only small mistake that's because the thing wasn't on. Okay. Anyway, what's on your plate. What's your, what's some of the milestones. Do you share for your employees, your customers and your partners out there that are watching that might wanna know what's next in the whole Broadcom VMware situation. Is there a timeline? Can you talk publicly about what? To what people can expect? >>Yeah, no, we, we talk all the time in the company about that. Right? Because even if there is no news, you need to talk about what is where we are. Right. Because this is such a big transaction and employees need to know where we are at every minute of the day. Right? Yeah. So, so we definitely talk about that. We definitely talk about that with customers too. And where we are is that the, all the processes are on track, right? There is a regulatory track going on. And like I alluded to a few minutes ago, Broadcom is doing what they call the discovery phase of the integration planning, where they learn about the business. And then once that is done, they'll figure out what the operating model is. What Broadcom is said publicly is that the acquisition will close in their fiscal 23, which starts in November of this year, runs through October of next year. >>So >>Anywhere window, okay. As to where it is in that window. >>All right, Raghu, thank you so much for taking valuable time out of your conference time here for the queue. I really appreciate Dave and I both appreciate your friendship. Congratulations on the success as CEO, cuz we've been following your trials and tribulations and endeavors for many years and it's been great to chat with you. >>Yeah. Yeah. It's been great to chat with you, not just today, but yeah. Over a period of time and you guys do great work with this, so >>Yeah. And you guys making, making all the right calls at VMware. All right. More coverage. I'm shot. Dave ante cube coverage day one of three days of world war cup here in Moscone west, the cube coverage of VMware Explorer, 22 be right back.

(upbeat music) >> Narrator: From the Cube Studios in Palo Alto in Boston, connecting with thought leaders all around the world. This is the Cube Conversation. >> Welcome to this Cube Conversation. I'm Lisa Martin, excited to talk to the CEO of Styra, Bill Mann today. Bill, welcome to the Cube. >> Hi Lisa, how are you doing? >> I'm doing well. I should say welcome back. You've been on the Cube at a previous company, but we're excited to talk to you today about Styra, what's going on? So let's go ahead and start informing our audience who Styra is and what you do? >> Sure, so who Styra is and what do we do? So Styra is a company that's focused on reinventing policy and authorization in the cloud native stack. We're the company that created an open source project called Open Policy Agent, it's part of CNCF. And on top of Open Policy Agent, we built a control plane, a management plane to help organizations really put OPA into production and operationalized OPA. >> An OPA is Open Policy Agent. That's what the company actually developed with CNCF, correct? >> So, we actually founded Open Policy Agent and then we contributed Open Policy Agent to CNCF. And the real goal of contributing the Open Policy Agent to CNCF was we believe that we want to get authorization defacto in the market, right? And the only way to get something out there that everybody uses is to put it into the open source and having an entity like the CNCF supporting the project. So, really it's about getting everybody, all enterprises and vendors to use Open Policy Agent as a way of solving authorization for the cloud native environment. >> So you say Styra is reinventing policy and authorization for cloud native applications, your target audience, security folks, developer folks, what changes has cloud native brought to security and development teams? >> Sure, so what changes has cloud native brought to security and development teams? So fundamentally there've been three changes in the marketplace. One, as you know we're shifting from this monolithic architecture of building applications to now this new distributed architectures of kubernetes, microservices and Deep-coupled architecture. So fundamentally the way we build applications is fundamentally changed because everybody wants to have scale up and scale down and so forth. Second, the way we actually developed software, we've moved now to a DevOps model where we're doing more things earlier on in the cycle so we can innovate faster and we're producing code on an hourly basis versus when I joined the industry which was probably three releases a year. And then thirdly which is kind of a major topic that all of us kind of understand is our focus on privacy and security is higher than it's been before. And if these applications are going to be way more complex and more distributed and we're going to innovate faster than the way we focus on security and privacy has to be done differently as well. And if we don't do it differently, then we're going to have to all the breaches that we had in the previous generation of the app stack. >> And we don't want that, but you're right privacy and security are increasing concerns in any environment. How do you help address those and also with the thought of privacy and security are going to be concerned for quite a long time? >> Yeah, so let me take a step back. So how do we address privacy and security? So, at a fundamental level, authorization is a foundational part of security and authorization has never really been solved or re-imagined ever for the last 50 years or so. Every application developer or security vendor has built authorization into their own stack and done it in a very proprietary way. And it's been locked away within these applications and these stacks and so forth. So what happens now when you've got a highly distributed environment is that you've got so many moving parts, you still need to apply authorization. So, the way we've tackled it is by building Open Policy Agent. And there's three fundamental kind of tenants around Open Policy Agent that make it really ideal for this cloud native environment. Number one, it's policy as code and everything in the market now, everything is as code. You buy infrastructure as code. So this is now policy as code. So you can describe in a declarative model, how you want the policy for a system to be developed and you can use the language called Rego to do that. Second is the fact that all the cloud native projects out there which are all developed based upon open source technologies, kubernetes, microservices, envoy, SDO, cafco, all these kinds of buzzwords you hear in the marketplace, they all integrate with Open Policy Agent already. And then thirdly the architecture of Open Policy Agent is that it's distributed, which means that it's ideally suited for this distributed architecture for cloud native. And those are the three kind of characteristics of Open Policy Agent leading to developers loving it. And when I say they love it, we've got hundreds and thousands of users of Open Policy Agent. When you go to the CNCF shows co op con earlier this year and there's two more coming this year. There's many, many talks on it. You've got cloud vendors like Google and Microsoft adopting Open Policy Agent, got a lot of enterprises adopting Open Policy Agent. So, that's really fundamentally what we've built is we've built an authorization architecture for this new world to really address the security and privacy concerns, which have always existed and I'm going to be more exponential in this new world. >> And I think you've also built a community around OPA. Can you share a little bit of information about that and how they help with the co-development and even some of the other things that you're commercializing? >> Sure, yeah. So, now what have we done in from a community point of view with Open Policy Agents? So yeah, the community is a integral part of any open source project and we're lucky to have a great community. We've got a great community of enterprise users of Open Policy Agents and vendors as well, vendors like Microsoft and Google who are now contributing to OPA and building it up. And for me, the most important part of a community is that you learn how enterprises are using your software and they share ideas and they share use cases and you're able to innovate really, really fast. And what we've learned from that is the use cases that they use Open Policy Agent for, for instance, one of the major use cases for Open Policy Agent is for kubernetes Admission Control. So, essentially we can test the configuration of an application which is described in a file called YAML before it goes into production. So, think of it as pre-production tests, but companies are using it for microservices and applications and data and so forth. So, it helps us understand what they're using it for, but also we use it to help us develop our commercial product, which is the management control plane for OPA. So, we learn about what they're missing in the open source project that we can use to build our commercial product >> which is ready for enterprise use. >> So you've had a lot of success with OPA. Talk to me about Styra DAS and why the need for that? >> Sure, so why do we need Styra DAS recognizing that OPA is very, very successful. So, the fundamental difference is OPA is a very focused on developers and it's very focused on an environment for an individual node or cluster, but it doesn't have all the enterprise features necessary for a real enterprise to go into production. So what we notice is companies use OPA for pre-production, but when they want to go into production, they need a user interface. They need a way to author policies, distribute policies, monitor policies, do impact analysis and a whole bunch of other features and capabilities that are needed for enterprise deployments and so forth. So that's a fundamental difference between OPA and the commercial product. The commercial product is really operationalizing in OPA for an enterprise deployment. >> So the relationship between Styra and OPA seems very collaborative to me that what you just described with the commercial product of Styra DAS is really one that was developed based on what the OPA community and Styra have learned together? >> Correct, Yes. So, OPA was created by the CTO, the founders of the company saw early on several years ago, the need for distributed architectures and the need for unified policy so they left and created OPA. And from day one they wanted to get OPA into everybody's hands. That's why they contributed it to open source as part of CNCF. And then the next kind of strategy is to focus on the control apps aspects, the enterprise aspect. So yes, the same team that created OPA is the same team that's creating the Styra DAS commercial offering as well. >> So from the enterprise perspective, talk to me about some of the companies that you're talking to. I imagine any organization that's focused on cloud native, but any industry in particular that you see is really kind of leading edge right now? >> Yeah, so which industries are we talking to in terms of using Styra DAS and OPA? What we've actually found it's across the board. And we've seen in the early days that financial services and high tech were using OPA, but now it's really across the board. So it's all verticals really. And what we've noticed is any organization which is going through a cloud transformation project where they're either building new applications based upon cloud native app stacks like kubernetes and microservices and so forth or shift to the cloud are the companies that are also adopting OPA and the Styra DAS product, right? Because it's all part of the same solution set. And what we're noticing now and this is a fundamental difference is platform architects and developers are kind of prime to use these technologies. They learn about these technologies by going to the conferences and unlike the past which was very much top down selling from the sea level down, this is very much bottomed up. So developers learn about OPA from going to the conferences. They use it within their own environment and then they tell their management that, "Look, we're using OPA already. "We're missing these capabilities," or they come to us and we educate them about the Styra DAS product and so forth. So it's a very different sales model as well and that's why it's very important for ourselves and any open source company to really keep developers happy and provide a solution, that's meeting their requirements. >> On that side with so many of us and developers included working from home for the past nearly four months. We now are doing things like this virtual conversations, virtual events, how is Styra helping to continue to feed and educate those developers so that they can understand how you can impact their job functions and how they can then elevate you guys up the stack. >> Sure, so what's changed over the last three months or so in the market as a consequence of COVID-19 and from an educational point of view. So, what we've seen is fundamentally in the early days of COVID-19 everybody was kind of get the head around how to work from home and so forth, but what we've seen across the all verticals is developers have now really focused on educating themselves and just as a data point and the audience that we get to the OPA website is as high as it's ever been for the last three months. And what we're doing as a company is a lot of training sessions, video content, write-ups, blogs and so forth, right? And really helping the community learn about OPA and how to solve these kind of fundamental problems around policy and authorization within the environment. We've also been helped by the community as well. So there's been talks about a number of companies, Microsoft, Google, Palo Alto had a talk and many many companies are talking about OPA now and I love it because ultimately being an open source company and building a project which we want to become defacto, we want to raise the bar for security across the world, right? And if we can do that then it's going to be an achievement for us and it's very gratifying knowing that we're really fixing security problems for organizations because ultimately we always want to be able to use an application or a banking service and not worry about privacy and security concerns and that's ultimately what we're all after. But this is such a fundamental component that once we want to have developers learn this now because if they can incorporate this into the DevOps app stack then in future years when these applications are built and they're exposed there'll be more secure. >> And so it sounds like maybe there's even more engagement now during COVID when everybody is at home. Tell me about some of the things that are coming down the pipe for Styra in light of all of this exciting collaboration with the community. >> Sure, yeah. There's definitely been way more collaboration as a consequence of COVID-19. People are at home and they're focusing and they're going through learning sessions and browsing the website going through the video content and so forth. So what we're engaging as much as we have ever been, in fact I would argue that we're engaging even more so now, because it's just a different environment to work in. And what we're focused on now is really adding more features to the Styra DAS product, just to step back for a second, Open Policy Agent works across the cloud native stack and Styra DAS has been focused first on the kubernetes use case and now it also supports microservices as well. And then what we're continuing to do is add more of those enterprise features into Styra DAS and move up and up across the stack. But it is all driven by developers that we're talking to on a daily basis and that's leading to where the project is moving forward and the development for the roadmap and so forth. >> And Styra DAS was only launched in 2019, is that correct? >> 2019 yes, that's correct. That's correct. Yes, time flies, right? So, yes. >> A lot of change and a lot of development in a short period of time. >> That's right and 2019 was a big year for us, right? We started last 2019 with a soft launch at the RSA conference and we finished 2019 with series a funding led by Xcel. And yeah, it's great to see how the commercial product has been gaining traction in the marketplace as well as OPA as well and I think it's a combination of events. One, the fact that cloud native is now really well understood. Second, the fact that kubernetes at the beginning of 2019, it was still, "What does kubernetes mean, "is it going into production?" Now kubernetes is absolutely going into production and there's such a desire for organizations to make sure that security and policy and compliance are resolved before applications go into production otherwise we're going to have the same kind of challenges we had with previous app stacks. >> Well, the momentum is certainly with you. I can definitely hear that in your voice bell. Thank you so much for joining me talking about Styra, how you're reinventing policy and authorization for cloud native applications. >> Thank you, Lisa. >> For my guest Bill Mann, I'm Lisa Martin. You're watching the Cube Conversation. Thanks for your time. (upbeat music)

(upbeat music) >> Narrator: From the Cube Studios in Palo Alto in Boston, connecting with thought leaders all around the world. This is the Cube Conversation. >> Welcome to this Cube Conversation. I'm Lisa Martin, excited to talk to the CEO of Styra, Bill Mann today. Bill, welcome to the Cube. >> Hi Lisa, how are you doing? >> I'm doing well. I should say welcome back. You've been on the Cube at a previous company, but we're excited to talk to you today about Styra, what's going on? So let's go ahead and start informing our audience who Styra is and what you do? >> Sure, so who Styra is and what do we do? So Styra is a company that's focused on reinventing policy and authorization in the cloud native stack. We're the company that created an open source project called Open Policy Agent, it's part of CNCF. And on top of Open Policy Agent, we built a control flame, a management plane to help organizations really put OPA into production and operationalized OPA. >> An OPA is Open Policy Agent. That's what the company actually developed with CNCF, correct? >> So, we actually founded Open Policy Agent and then we contributed Open Policy Agent to CNCF. And the real goal of contributing the Open Policy Agent to CNCF was we believe that we want to get authorization defacto in the market, right? And the only way to get something out there that everybody uses is to put it into the open source and having an entity like the CNCF supporting the project. So, really it's about getting everybody, all enterprises and vendors to use Open Policy Agent as a way of solving authorization for the cloud native environment. >> So you say Styra is reinventing policy and authorization for cloud native applications, your target audience, security folks, developer folks, what changes has cloud native brought to security and development teams? >> Sure, so what changes has cloud native brought to security and development teams? So fundamentally there've been three changes in the marketplace. One, as you know we're shifting from this monolithic architecture of building applications to now this new distributed architectures of kubernetes, microservices and Deep-coupled architecture. So fundamentally the way we build applications is fundamentally changed because everybody wants to have scale up and scale down and so forth. Second, the way we actually developed software, we've moved now to a DevOps model where we're doing more things earlier on in the cycle so we can innovate faster and we're producing code on an hourly basis versus when I joined the industry which was probably three releases a year. And then thirdly which is kind of a major topic that all of us kind of understand is our focus on privacy and security is higher than it's been before. And if these applications are going to be way more complex and more distributed and we're going to innovate faster than the way we focus on security and privacy has to be done differently as well. And if we don't do it differently, then we're going to have to all the breaches that we had in the previous generation of the app stack. >> And we don't want that, but you're right privacy and security are increasing concerns in any environment. How do you help address those and also with the thought of privacy and security are going to be concerned for quite a long time? >> Yeah, so let me take a step back. So how do we address privacy and security? So, at a fundamental level, authorization is a foundational part of security and authorization has never really been solved or re-imagined ever for the last 50 years or so. Every application developer or security vendor has built authorization into their own stack and done it in a very proprietary way. And it's been locked away within these applications and these stacks and so forth. So what happens now when you've got a highly distributed environment is that you've got so many moving parts, you still need to apply authorization. So, the way we've tackled it is by building Open Policy Agent. And there's three fundamental kind of tenants around Open Policy Agent that make it really ideal for this cloud native environment. Number one, it's policy as code and everything in the market now, everything is as code. You buy infrastructure as code. So this is now policy as code. So you can describe in a declarative model, how you want the policy for a system to be developed and you can use the language called Rego to do that. Second is the fact that all the cloud native projects out there which are all developed based upon open source technologies, kubernetes, microservices, envoy, SDO, cafco, all these kinds of buzzwords you hear in the marketplace, they all integrate with Open Policy Agent already. And then thirdly the architecture of Open Policy Agent is that it's distributed, which means that it's ideally suited for this distributed architecture for cloud native. And those are the three kind of characteristics of Open Policy Agent leading to developers loving it. And when I say they love it, we've got hundreds and thousands of users of Open Policy Agent. When you go to the CNCF shows co op con earlier this year and there's two more coming this year. There's many, many talks on it. You've got cloud vendors like Google and Microsoft adopting Open Policy Agent, got a lot of enterprises adopting Open Policy Agent. So, that's really fundamentally what we've built is we've built an authorization architecture for this new world to really address the security and privacy concerns, which have always existed and I'm going to be more exponential in this new world. >> And I think you've also built a community around OPA. Can you share a little bit of information about that and how they help with the co-development and even some of the other things that you're commercializing? >> Sure, yeah. So, now what have we done in from a community point of view with Open Policy Agents? So yeah, the community is a integral part of any open source project and we're lucky to have a great community. We've got a great community of enterprise users of Open Policy Agents and vendors as well, vendors like Microsoft and Google who are now contributing to OPA and building it up. And for me, the most important part of a community is that you learn how enterprises are using your software and they share ideas and they share use cases and you're able to innovate really, really fast. And what we've learned from that is the use cases that they use Open Policy Agent for, for instance, one of the major use cases for Open Policy Agent is for kubernetes Admission Control. So, essentially we can test the configuration of an application which is described in a file called Yammer before it goes into production. So, think of it as pre-production tests, but companies are using it for microservices and applications and data and so forth. So, it helps us understand what they're using it for, but also we use it to help us develop our commercial product, which is the management control plane for OPA. So, we learn about what they're missing in the open source project that we can use to build our commercial product which is ready for enterprise use. >> So you've had a lot of success with OPA. Talk to me about Styra DAS and why the need for that? >> Sure, so why do we need Styra DAS recognizing that OPA is very, very successful. So, the fundamental difference is OPA is a very focused on developers and it's very focused on an environment for an individual node or cluster, but it doesn't have all the enterprise features necessary for a real enterprise to go into production. So what we notice is companies use OPA for pre-production, but when they want to go into production, they need a user interface. They need a way to author policies, distribute policies, monitor policies, do impact analysis and a whole bunch of other features and capabilities that are needed for enterprise deployments and so forth. So that's a fundamental difference between OPA and the commercial product. The commercial product is really operationalizing in OPA for an enterprise deployment. >> So the relationship between Styra and OPA seems very collaborative to me that what you just described with the commercial product of Styra DAS is really one that was developed based on what the OPA community and Styra have learned together? >> Correct, Yes. So, OPA was created by the CTO, the founders of the company when the team was actually part of Nicira and they left Nicira which got acquired by VMware and so on early on several years ago, the need for distributed architectures and the need for unified policy so they left and created OPA. And from day one they wanted to get over into everybody's hands. That's why they contributed it to open source as part of CNCF. And then the next kind of strategy is to focus on the control apps aspects, the enterprise aspect. So yes, the same team that created OPA is the same team that's creating the Styra DAS commercial offering as well. >> So from the enterprise perspective, talk to me about some of the companies that you're talking to. I imagine any organization that's focused on cloud native, but any industry in particular that you see is really kind of leading edge right now? >> Yeah, so which industries are we talking to in terms of using Styra DAS and OPA? What we've actually found it's across the board. And we've seen in the early days that financial services and high tech were using OPA, but now it's really across the board. So it's all verticals really. And what we've noticed is any organization which is going through a cloud transformation project where they're either building new applications based upon cloud native app stacks like kubernetes and microservices and so forth or shift to the cloud are the companies that are also adopting OPA and the Styra DAS product, right? Because it's all part of the same solution set. And what we're noticing now and this is a fundamental difference is platform architects and developers are kind of prime to use these technologies. They learn about these technologies by going to the conferences and unlike the past which was very much top down selling from the sea level down, this is very much bottomed up. So developers learn about OPA from going to the conferences. They use it within their own environment and then they tell their management that, "Look, we're using OPA already. "We're missing these capabilities," or they come to us and we educate them about the Styra DAS product and so forth. So it's a very different sales model as well and that's why it's very important for ourselves and any open source company to really keep developers happy and provide a solution, that's meeting their requirements. >> On that side with so many of us and developers included working from home for the past nearly four months. We now are doing things like this virtual conversations, virtual events, how is Styra helping to continue to feed and educate those developers so that they can understand how you can impact their job functions and how they can then elevate you guys up the stack. >> Sure, so what's changed over the last three months or so in the market as a consequence of COVID-19 and from an educational point of view. So, what we've seen is fundamentally in the early days of COVID-19 everybody was kind of get the head around how to work from home and so forth, but what we've seen across the all verticals is developers have now really focused on educating themselves and just as a data point and the audience that we get to the OPA website is as high as it's ever been for the last three months. And what we're doing as a company is a lot of training sessions, video content, write-ups, blogs and so forth, right? And really helping the community learn about OPA and how to solve these kind of fundamental problems around policy and authorization within the environment. We've also been helped by the community as well. So there's been talks about a number of companies, Microsoft, Google, Palo Alto had a talk and many many companies are talking about OPA now and I love it because ultimately being an open source company and building a project which we want to become defacto, we want to raise the bar for security across the world, right? And if we can do that then it's going to be an achievement for us and it's very gratifying knowing that we're really fixing security problems for organizations because ultimately we always want to be able to use an application or a banking service and not worry about privacy and security concerns and that's ultimately what we're all after. But this is such a fundamental component that once we want to have developers learn this now because if they can incorporate this into the DevOps app stack then in future years when these applications are built and they're exposed there'll be more secure. >> And so it sounds like maybe there's even more engagement now during COVID when everybody is at home. Tell me about some of the things that are coming down the pipe for Styra in light of all of this exciting collaboration with the community. >> Sure, yeah. There's definitely been way more collaboration as a consequence of COVID-19. People are at home and they're focusing and they're going through learning sessions and browsing the website going through the video content and so forth. So what we're engaging as much as we have ever been, in fact I would argue that we're engaging even more so now, because it's just a different environment to work in. And what we're focused on now is really adding more features to the Styra DAS product, just to step back for a second, Open Policy Agent works across the cloud native stack and Styra DAS has been focused first on the kubernetes use case and now it also supports microservices as well. And then what we're continuing to do is add more of those enterprise features into Styra DAS and move up and up across the stack. But it is all driven by developers that we're talking to on a daily basis and that's leading to where the project is moving forward and the development for the roadmap and so forth. >> And Styra DAS was only launched in 2019, is that correct? >> 2019 yes, that's correct. That's correct. Yes, time flies, right? So, yes. >> A lot of change and a lot of development in a short period of time. >> That's right and 2019 was a big year for us, right? We started last 2019 with a soft launch at the RSA conference and we finished 2019 with series a funding led by Xcel. And yeah, it's great to see how the commercial product has been gaining traction in the marketplace as well as OPA as well and I think it's a combination of events. One, the fact that cloud native is now really well understood. Second, the fact that kubernetes at the beginning of 2019, it was still, "What does kubernetes mean, "is it going into production?" Now kubernetes is absolutely going into production and there's such a desire for organizations to make sure that security and policy and compliance are resolved before applications go into production otherwise we're going to have the same kind of challenges we had with previous app stacks. >> Well, the momentum is certainly with you. I can definitely hear that in your voice bell. Thank you so much for joining me talking about Styra, how you're reinventing policy and authorization for cloud native applications. >> Thank you, Lisa. >> For my guest Bill Mann, I'm Lisa Martin. You're watching the Cube Conversation. Thanks for your time. (upbeat music)