(upbeat music) >> Hello, and welcome to Supercloud2. I'm John Furrier, host of theCUBE here. We're exploring all the new Supercloud trends around multiple clouds, hyper scale gaps in their systems, new innovations, new applications, new companies, new products, new brands emerging from this big inflection point. Got a great guest who's going to unpack it with me today, Ramesh Prabagaran, who's the co-founder and CEO of Prosimo, CUBE alumni. Ramesh, legend in the industry, you've been around. You've seen many cycles. Welcome to Supercloud2. >> Thank you. You're being too kind. >> Well, you know, you guys have been a technical, great technical founding team, multiple ventures, multiple times around the track as they say, but now we're seeing something completely different. This is our second event, kind of we're doing to start the the ball rolling around unpacking this idea of Supercloud which evolved from a riff with me and Dave to now a working group paper, multiple definitions. People are saying they're Supercloud. CloudFlare says this is their version. Someone says there over there. Fitzi over there in the blog is always, you know, challenging us on our definitions, but it's, the consensus is though something's happening. >> Ramesh: Absolutely. >> And what's your take on this kind of big inflection point? >> Absolutely, so if you just look at kind of this in layers right, so you have hyper scalers that are innovating really quickly on underlying capabilities, and then you have enterprises adopting these technologies, right, there is a layer in the middle that I would say is largely missing, right? And one that addresses the gaps introduced by these new capabilities, by the hyper scalers. At the same time, one that actually spans, let's say multiple regions, multiple clouds and so forth. So that to me is kind of the Supercloud layer of sorts. One that helps enterprises adopt the underlying hyper scaler capabilities a lot faster, and at the same time brings a certain level of consistency and homogeneity also. >> What do you think the big driver of Supercloud is? Is it the industry growing up or is it the demand for new kinds of capabilities or both? Or just evolution? What's your take? >> I would say largely it depends on kind of who the entity is that you're talking about, right? And so I would say both. So if you look at one cohort here, it's adoption, right? If I have a externally facing digital presence, for example, then I'm going to scale that up and get to as many subscribers and users no matter what, right? And at that time it's a different set of problems. If you're looking at kind of traditional enterprise inward that are bringing apps into the cloud and so forth, it's a different set of care abouts, right? So both are, I would say, equally important problems to solve for. >> Well, one reality that we're definitely tracking, and it's not really a debate anymore, is hybrid. >> Ramesh: Yep >> Hybrid happened. It happened faster than most people thought. But, you know, we were talking about this in 2015 when it first got kicked around, but now you see hybrid in the cloud, on premises and the edge. This kind of forms that distributed computing paradigm that we've always been predicting. And so if that continues to play out the way it is, you're now going to have a completely distributed, connected internet and sets of systems, intra and external within companies. So again, the world is connected 100%. Everything's changing, right? >> And that introduces. >> It wasn't your grandfather's networking anymore or storage. The game is still the same, but the play, the components are acting differently. What's your take on this? >> Absolutely. No, absolutely. That's a very key important point, and it's one that we always ask our customers right at the front end, right? Because your starting assumptions matter. If you have workloads of workloads in the cloud and data center is something that you want to connect into, then you'll make decisions kind of keeping cloud in the center and then kind of bolt on technologies for what that means to extend it to the data center. If your center of gravity is in the data center, and then cloud is let's say 10% right now, but you see that growing, then what choices do you have? Right, do you want to bring your data center technologies into the cloud because you want that consistency in operations? Or do you want to start off fresh, right? So this is a really key, important question, and one that many of our customers are actually are grappling with, right? They have this notion that going cloud native is the right approach, but at the same time that means I have a bifurcation in kind of how do I operate my data center versus my cloud, right? Two different operating models, and slowly it'll shift over to one. But you're going to have to deal with dual reality for a while. >> I was talking to an old friend of mine, CIO, very experienced CIO. Big time company, large deployment, a lot of IT. I said, so what's the big trend everyone's telling me about IT's going. He goes no, not really. IT's not going away for me. It's going everywhere in the company. >> Ramesh: Exactly. >> So I need to scale my IT-like capabilities everywhere and then make it invisible. >> Ramesh: Correct. >> Which is essentially code words for saying it's going to be completely cloud native everywhere. This is what is happening. Do you agree? >> Absolutely right, and so if you look at what do enterprises care about it? The reason to go to the cloud is to get speed of operations, and it's apps, apps, apps, right? Do you ever have a conversation on networking and infrastructure first? No, that kind of gets brought into the conversation because you want to deal with users, applications and services, right? And so the end goal is essentially how do users communicate with apps and get the right experience, security and whatnot, and how do apps talk to each other and make sure that you get all of the connectivity and security requirements? Underneath the covers, what does this mean for infrastructure, networking, security and whatnot? It's actually going to be someone else's job, right? And you shouldn't have to think too much about it. So this whole notion of kind of making that transparent is real actually, right? But at the same time, us and all the guys that we talk to on the customer side, that's their job, right? Like we have to work towards making that transparent. Some are going to be in the form of capability, some are going to be driven by data, but that's really where the two worlds are going to come together. >> Lots of debates going on. We just heard from Bob Muglia here on Supercloud2. He said Supercloud's a platform that provides programmatically consistent services hosted on heterogeneous cloud providers. So the question that's being debated is is Supercloud a platform or an architecture in your view? >> Okay, that's a tough one actually. I'm going to side on the side on kind of the platform side right, and the reason for that is architectural choices are things that you make ahead of time. And you, once you're in, there really isn't a fork in the road, right? Platforms continue to evolve. You can iterate, innovate and so on and so forth. And so I'm thinking Supercloud is more of a platform because you do have a choice. Hey, am I going AWS, Azure, GCP. You make that choice. What is my center of gravity? You make that choice. That's kind of an architectural decision, right? Once you make that, then how do I make things work consistently across like two or three clouds? That's a platform choice. >> So who's responsible for the architecture as the platform, the vendor serving the platform or is the platform vendor agnostic? >> You know, this is where you have to kind of peel the onion in layers, right? If you talk about applications, you can't go to a developer team or an app team and say I want you to operate on Google or AWS. They're like I'll pick the cloud that I want, right? Now who are we talking to? The infrastructure guys and the networking guys, right? They want to make sure that it's not bifurcated. It's like, hey, I want to make sure whatever I build for AWS I can equally use that on Azure. I can equally use that on GCP. So if you're talking to more of the application centric teams who really want infrastructure to be transparent, they'll say, okay, I want to make this choice of whether this is AWS, Azure, GCP, and stick to that. And if you come kind of down the layers of the stack into infrastructure, they are thinking a little more holistically, a little more Supercloud, a little more multicloud, and that. >> That's a good point. So that brings up the deployment question. >> Ramesh: Exactly! >> I want to ask you the next question, okay, what is the preferred deployment in your opinion for a Supercloud narrative? Is it single instance, spread it around everywhere? What's the, do you have a single global instance or do you have everything synchronized? >> So I would say first layer of that Supercloud really kind of fix the holes that have been introduced as a result of kind of adopting the hyper scaler technologies, right? So each, the hyper scalers have been really good at innovating and providing really massive scale elastic capabilities, right? But once you start to build capabilities on top of that to help serve the application, there's a few holes start to show up. So first job of Supercloud really is to plug those holes, right? Second is can I get to an operating model, so that I can replicate this not just in a single region, but across multiple regions, same cloud, and then across multiple clouds, right? And so both of those need to be solved for in order to be (cross talking). >> So is that multiple instantiations of the stack or? >> Yeah, so this again depends on kind of the capability, right? So if you take a more solution view, and so I can speak for kind of networking security combined right? There you always take a solution view. You don't ever look at, you know, what does this mean for a single instance in a single region. You take a macro view, and then you then break it down into what does this mean for region, what does it mean for instance, what does this mean for AZs? And so on and so forth. So you kind of have to go top to bottom. >> Okay, welcome you down into the trap now. Okay, synchronizing the data, latency, these are all questions. So what does the network Supercloud look like to you? Because networking is big here. >> Ramesh: Yes, absolutely. >> This is what you guys do. >> Exactly, yeah. So the different set of problems as you go up the stack, right? So if you have hundreds of workloads in a single region, the set of problems you're dealing with there are kind of app native connectivity, how do I go from kind of east/west, all of those fun things, right? Which are usually bound in terms of latency. You don't have those challenges as much, but can you build your entire enterprise application architecture in one region? No, you're going to have to create multiple instances, right? So my data lake is invariably going to be in one place. My business logic is going to be spread across a few places. What does that bring in? I need to go across regions. Am I going to put those two regions right next to each other? No, I'm not going to, right? I'm going to have places in Europe. I'm going to have APAC, and I'm going to have a North American presence, and I need to bring all these things together. So this is where, back to your point, latency really matters, right? Because I need to be able to find out not just best path but also how do I reduce the millisecond, microseconds that my application cares about, which brings in a layer of optimization and then so on and so on and so forth. So this is what we call kind of to borrow the Prosimo language full stack networking, right? Because I'm not just dealing with how do I go from one region to another because that's laws of physics. I can only control so much. But there are a few elements up the application stack in software that you can tweak to actually bring these things closer and closer. >> And on that point, you're seeing security being talked a lot more at the network layer. So how do you secure the Supercloud at the network layer? What's that look like? >> Yeah, we've been grappling with essentially is security kind of foundational, and then is the network on top. And then we had an alternative viewpoint which is kind of network and then security on top. And the answer is actually it's neither, right? It's almost like a meshed up sandwich of sorts. So you need to have networking security work really well together, right? Case in point, I mean we were talking to a customer yesterday. He said, hey, I have my data lake in one region that needs to talk to an analytics service in a completely different region of a different cloud. These two things just need to be able to talk to each other, which means I need to bring elements of networking. I need to bring elements of security, secure access, app segmentation, all of those things. Very simple, I have an analytics service that needs to contact a data lake. That's what he starts with, but then before you know it, it actually brings up a whole stack underneath, so that's. >> VMware calls that cloud chaos. >> Ramesh: Yes, exactly. >> And then that's the halfway point between cloud smart. Cloud first, cloud chaos, cloud smart, and the next thing, you can skip that whole step. But again, again, it's pick your strategy right? Again, this comes back down to your earlier point. I want to ask you from a customer standpoint, you got the hyper scalers doing very, very well. >> Ramesh: Yep, absolutely. >> And I love what their Amazon's doing. I think Microsoft again though they had a little bit of downgrade are catching up fast, and they have their installed base. So you got the land of the installed bases. >> Correct. >> First and greater, better cloud. Install base getting better, almost as good, almost as good is a gift, but close. Now you have them specializing. Silicon, special silicon. So there's gaps for other services. >> Ramesh: Correct. >> And Amazon Web Services, Adam Selipsky's a open book saying, hey, we want our ecosystem to pick up these gaps and build on them. Go ahead, go to town. >> So this is where I think choices are tough, right? Because if you had one choice, you would work with it, and you would work around it, right? Now I have five different choices. Now what do I do? Our viewpoint is there are a bunch of things that say AWS does really, really well. Use that as a foundational layer, right? Like don't reinvent the wheel on those things. Transit gateways, global accelerators and whatnot, they exist for a reason. Billions of dollars have gone into building those things. Use that foundational layer, right? But what you want to build on top of that is actually driven by the application. The requirements of a lambda application that's serverless, it's very different than a packaged application that's responding for transactions, right? Like it's just completely very, very different. And so bring in the right set of capabilities required for those set of applications, and then you go based on that. This is also where I think whether something is a regional construct versus an overall global construct really, really matters, right? Because if you start with the assumption that everything is going to be built regionally, then it's someone else's job to make sure that all of these things are connected. But if you start with kind of the global purview, then the rest of them start to (cross talking). >> What are some of the things that the enterprises might want that are gaps that are going to be filled by the, by startups like you guys and the ecosystem because we're seeing the ecosystem form into two big camps. >> Ramesh: Yep. >> ISVs, which is an old school definition of independent software vendor, aka someone who writes software. >> Ramesh: Exactly. >> SaaS app. >> Ramesh: Correct. >> And then ecosystem software players that were once ISVs now have people building on top of them. >> Ramesh: Correct. >> They're building on top of the cloud. So you have that new hyper scale effect going on. >> Ramesh: Exactly. >> You got ISVs, which is software developers, software vendors. >> Ramesh: Correct. >> And ecosystems. >> Yep. >> What's that impact of that? Cause it's a new dynamic. >> Exactly, so if you take kind of enterprises, want to make sure that that their apps and the data center migrate to the cloud, new apps are developed the right way in the cloud, right? So that's kind of table stakes. So now what choices do they have? They listen to AWS and say, okay, I have all these cloud native services. I want to be able to instantiate all that. Now comes the interesting choice that they have to make. Do I go hire a whole bunch of people and do it myself or do I go there on the platform route, right? Because I made an architectural choice. Now I have to decide whether I want to do this myself or the platform choice. DIY works great for some, but you don't know what you're getting into, and it's people involved, right? People, process, all those fun things involved, right? So we show up there and say, you don't know what you don't know, right? Like because that's the nature of it. Why don't you invest in a platform like what what we provide, and then you actually build on top of it. We will, it's our job to make sure that we keep up with the innovation happening underneath the covers. And at the same time, this is not a closed ended system. You can actually build on top of our platform, right? And so that actually gives you a good mix. Now the care abouts are interesting. Some apps care about experience. Some apps care about latency. Some apps are extremely charty and extremely data intensive, but nobody wants to pay for it, right? And so it's a interesting Jenga that you have to play between experience versus security versus cost, right? And that makes kind of head of infrastructure and cloud platform teams' life really, really, really interesting. >> And this is why I love your background, and Stu Miniman, when he was with theCUBE, and now he's at Red Hat, we used to riff about the network and how network folks are now, those concepts are now up the top of the stack because the cloud is one big network effect. >> Ramesh: Exactly, correct. >> It's a computer. >> Yep, absolutely. No, and case in point, right, like say we're in let's say in San Jose here or or Palo Alto here, and let's say my application is sitting in London, right? The cloud gives you different express lanes. I can go down to my closest pop location provided by AWS and then I can go ride that all the way up to up to London. It's going to give me better performance, low latency, but I'm going to have to incur some costs associated with it. Or I can go all the wild internet all the way from Palo Alta up to kind of the ingress point into London and then go access, but I'm spending time on the wild internet, which means all kinds of fun things happen, right? But I'm not paying much, but my experience is not going to be so great. So, and there are various degrees of shade in them, of gray in the middle, right? So how do you pick what? It all kind of is driven by the applications. >> Well, we certainly want you back for Supercloud3, our next version of this virtual/live event here in our Palo Alto studios. Really appreciate you coming on. >> Absolutely. >> While you're here, give a quick plug for the company. Next minute, we can take a minute to talk about the success of the company. >> Ramesh: Absolutely. >> I know you got a fresh financing this past year. Plenty of money in the bank, going to ride this new wave, Supercloud wave. Give us a quick plug. >> Absolutely, yeah. So three years going on to four this calendar year. So it's an interesting time for the company. We have proven that our technology, product and our initial customers are quite happy with it. Now comes essentially more of those and scale and so forth. That's kind of the interesting phase that we are in. Also heartened to see quite a few of kind of really large and dominant players in the market, partners, channels and so forth, invest in us to take this to the next set of customers. I would say there's been a dramatic shift in the conversation with our customers. The first couple of years or so of the company, we are about three years old right now, was really about us educating them. This is what you need. This is what you need. Now actually it's a lot of just pull, right? We've seen a good indication, as much as a hate RFIs, a good indication is the number of RFIs that show up at our door saying we want you to participate in this because we want to understand more, right? And so as a, I think we are at an interesting point of the, of that shift. >> RFIs always like do all this work and hope for the best. Pray for a deal. You know, you guys on the right side of history. If a customer asks with respect to Supercloud, multicloud, is that your focus? Is that the direction you guys are going into? >> Yeah, so I would say we are kind of both, right? Supercloud and multicloud because we, our customers are hybrid, multiple clouds, all of the above, right? Our main pitch and kind of value back to the customers is go embrace cloud native because that's the right approach, right? It doesn't make sense to go reinvent the wheel on that one, but then make a really good choice about whether you want to do this yourself or invest in a platform to make your life easy. Because we have seen this story play out with many many enterprises, right? They pick the right technologies. They do a simple POC overnight, and they say, yeah, I can make this work for two apps, right? And then they say, yes, I can make this work for 100. You go down a certain path. You hit a wall. You hit a wall, and it's a hard wall. It's like, no, there isn't a thing that you can go around it. >> A lot of dead bodies laying around. >> Ramesh: Exactly. >> Dead wall. >> And then they have to unravel around that, and then they come talk to us, and they say, okay, now what? Like help me, help me through this journey. So I would say to the extent that you can do this diligence ahead of time, do that, and then, and then pick the right platform. >> You've got to have the talent. And you got to be geared up. You got to know what you're getting into. >> Ramesh: Exactly. >> You got to have the staff to do this. >> And cloud talent and skillset in particular, I mean there's lots available but it's in pockets right? And if you look at kind of web three companies, they've gone and kind of amassed all those guys, right? So enterprises are not left with the cream of the crop. >> John: They might be coming back. >> Exactly, exactly, so. >> With this downturn. Ramesh, great to see you and thanks for contributing to Supercloud2, and again, love your team. Very technical team, and you're in the right side of history in this one. Congratulations. >> Ramesh: No, and thank you, thank you very much. >> Okay, this is Supercloud2. I'm John Furrier with Dave Vellante. We'll be back right after this short break. (upbeat music)

(upbeat music) >> Hello, welcome to this Cube Conversation here in Palo Alto, California. I'm John Furrier, host of theCube. We have a returning Cube alumni, Ramesh Prabagan, who is the co-founder and CEO of Prosimo.io. Great to see you, Ramesh. Thanks for coming in to our studio, and welcome to the new layout. >> Thanks for having me here, John. After a series of Zoom conversations, it's great to be live and in the flesh! >> Great to be in person. We also got a new stage for our Supercloud event, which we've been opening up to the community, looking forward to getting your perspective on that soon as well. But I want to keep the conversation really about you guys. I want to get the story down. You guys came out of stealth, Multicloud, Supercloud is right in your wheelhouse. >> Exactly. >> You got to love Supercloud. >> Yeah. As I walked in, I saw Supercloud all over the place, and it just gives you a jolt of energy. >> Well, you guys are in the middle of the action. Your company, I want you to explain this in a minute, is in the middle of this next wave. Because we had the structural change I called Cloud One. Amazon, use case, developers, no need to build a data center, all that goodness happens, higher level service of abstractions are happening, and then Azure comes in. More PaaS, and then more install base, now they're nipping at the heels. So full on hyperscale, Cap Backs growth, great for everybody. Now comes new use cases. Cloud to cloud, app to app, you see Databricks, Snowflake, MongoDB, all doing extremely well by leveraging the Cap Backs, now it's an ops problem. >> Exactly. >> Now ops and security. >> Yeah. It's speed of applications. >> How are you guys vectoring into that? Explain what you guys do. >> Absolutely. So let me take kind of the customer pain point first, right? Because it's always easier to explain that, and then we explain what is it that we do. So, it's no surprise. Applications are moving into the cloud, or people are building apps in the cloud in masses. The infrastructure that's sitting in front of these applications, cutting across networking, security, the operational piece associated with that, does not move at the same speed. The apps sometimes get upgraded two, three times a day, the infrastructure gets touched one time a week at best. And so increasingly, the cloud platform teams, the developers are all like, "Hey, why? Why? Why?" Right? "I thought things were supposed to move fast in the cloud." It doesn't. Now, if you double click on that, really, it's two reasons. One, those that won't have consistency across the stack that they hired in the data center, they bring a virtual form factor of that stack and line it up in the cloud, and before you know it, it's cost, it's operation complexity, there are multiple single panes of glass, all the fun stuff associated... >> Just to interject real quick. It is fast in the cloud if you're a developer. >> Exactly. >> So it's kind of like, hurry up, slow down, wait. >> Correct. >> So the developers are shifting left, open source is booming. Things are fine for developers right now. If you're a developer, things are good. >> But the guy sitting in front of that... >> The ops guys, they've got to deal with things like lock-in, choice, security. >> Exactly. And those are really the key challenges. We've seen some that actually said, "Hey, know what, I don't want to bring my data center stack into the cloud. Let me go cloud-native. And they start to build it up. 14 services from AWS, 15 from iGR, 14 more from GCP, even if you are in a single cloud. They just keep it to that. I need to know how to put this together. Because all these services are great, but how do I put this together. And enterprises don't have just one application, they have hundreds of these applications. So the requirements of a database is different than a service mesh, different than a serverless application, different than a web application. And before you know it, "How do I put all these things together?" And so we looked at this problem, and we said, "Okay. We subscribe to the fact that cloud-native is the way to go, right, but something needs to be there to make this simple." Right? And so, first thing that we did was bring all these cloud-native services together, we help orchestrate that, and we said, "okay, know what, Mr. Enterprise? We got you covered." Right? But now, it doesn't stop there. That's like, 10% of the value, right? What do you really need? What do you care about now? Because the apps are in the center of the universe, and who's talking to it? It's another application sitting either in the same cloud, or in a different cloud, or it's a user connecting into the application. So now, let's talk about what are the networking security operational requirements required for these apps to talk to each other, or the user to talk to the application. That's really what we focus on. >> Yeah. And I think one of the things that's driving this opportunity for you, and I want to get your reaction to this, is that the modern application movement is all about cloud-native. Okay, they're obviously doing great. Now, kind of the kumbaya moment in enterprise is that the security team and ops teams have to play ball and be friends with the developer, and vice versa. So harmony's coming there. So the little harmony. And two, the business is driving apps. IT is transforming over. This is why the Supercloud idea is interesting to Dave and I. Because when we coined that term, multi-cloud was not a market. Everyone has multiple clouds, 'cause they have Microsoft Office, that's now in the cloud, they got SQL Server, I mean it's really kind of Microsoft Cloud. >> Exactly. >> So you have a cloud. But do you have ops teams building on the stack? What about the network layer? This is where the rubber meets the road. >> Absolutely, yeah. And if you look at the challenges there, if you just focus on networking and security, right? When applications need to talk to each other, you have a whole bunch of underlying services, but somebody needs to put this thing on top. Because what you care about is "can these group of users talk to these class of applications." Or, "these group of applications, can they talk to each other," right? This whole notion of connectivity is just table stakes. Everybody just assumes it's there, right? It's the next layer up, which is, "how do I bring Zero Trust access? How do I get the observability?" And observability is not just a bunch of pretty donut chats. I have had people look to me in my previous company, the start-up, and said, "okay, give me all these nice donut chats, but so what? What do you want me to do with this?" And so you have to translate that into real actions, right? "How do I bring Zero Trust capabilities? How do I bring the observability capabilities? How do I understand cloud-native and networking and bring those things together so that you can help solve for the problem." >> It's interesting, one of the questions I had here to ask you was "what does it mean to be cloud-native, and why now?" And you brought up Zero Trust, trust and verify, these are security concepts. But if you look at what's going on at KubeKon and CNCF and Linux Foundation, software supply chain's a huge issue, where trust is the issue. They want trust there, so you got Zero Trust here. What is it? Zero Trust or trust? I mean, what's there? Is one hardware based, perimeter, networking? That kind of perimeter's dead, ton of... >> No, the whole- >> Trust or Zero Trust. >> The whole concept of Zero Trust is don't trust what is underlying, just trust what you're talking to. So if you and I talking to each other, John, you need to trust me, I need to trust you, and be able to have this conversation. >> You've been verified. >> Exactly, right? But in the application world, if you talk about two apps that are talking to each other, let's say there is a web application in one AWS region talking to a database in a different region, right? Now, do you want to make sure you are able to build that trust all the way from the application to the application? Or do you want to move the trust boundary to the two entities that are talking to each other so that irrespective of what they go on underneath the covers, you can be always sure that these two things are trusted. >> So, Ramesh, I was on LinkedIn yesterday, I wrote a comment, Dave Vallante wrote a post on Supercloud, we're talking about it, and I wrote, "Cloud as a commodity," question, and then a bunch of other stuff that we're going to talk about, and Keith Townsend jumped on that, and got on Twitter, put a poll, "Is cloud a commodity? Source: me." So, it started a big thread. And the reaction was interesting. And my point was to be provocative on "Cloud isn't commodity, but there's commodity elements." EC2 and S3, you can look at that and say, "that's commodity IaaS," but Amazon Web Services has done an amazing job for higher level services. Okay, so how does that translate into the use cases that you see that you guys are going after and solving, because it's the same kind of concept. IaaS and SaaS have to work together to solve problems, but that's in an integrated environment, say, in a native-cloud. How does that work across clouds? >> Yeah, no, you bring up a great point, John. So, let's take the simple use case, right? Let's keep the user to app thing to the side. Let us say two apps need to talk to each other, right? There are multiple ways in which you can solve this problem. You can build highways. That's what our customers call it. I'll build highways. I don't care what goes on those highways, I'll just build highways. You bring any kind of application workload on it, I just make sure that the highways are good, right? That's kind of the lowest common denominator. It's the path to least resistance. You can get stuff done, but it's not going to move the needle, right? Then you have really modern, kind of service networking, where, okay, I'm looking at every single HTTP, API, n:point, whatnot, and I'm optimizing for that. Right? Great if you know what you're doing, but, like, if you have thousands of these applications, it's not going to be really feasible to do that. And so, what we have seen customers do, actually, is employ a mixed approach, where they say, "I'm going to build these highways, the highways are going to make sure that I can go from one place to another, and maybe within regions, across clouds, whatnot, but then, I have specific requirements that my business needs, that actually needs tweaking, right? And so I'm going to tweak those things. That's why, what we call as like, full stack transit, is exactly that, right, which is, I'll build you the guts of it so that hey, you know what, if somebody screams at you, "Hey, why is my application not accessible?" You don't have that problem. It is always accessible. But then, the requirements for performance, the requirements for Zero Trust, the requirements for segmentation, and all of that are things that... >> That's a hard problem. >> That's a hard problem to solve. >> And you guys are solving that? >> Absolutely, exactly. >> So, let me throw this at you. So, okay, I get that. And by the way, that's exactly what we're seeing. Dave and I were also debating about multi-cloud as what it is. Now, the nirvana definition is, "Well, I have a workload, that's going to work the same, and just magically just shift to Azure." (Ramesh laughs) >> Like, 'cause there's better resources. >> There is no magic there. >> So, but this brings up the point of operations. Now, Databricks and Snowflake, they're building their software to run on multi-cloud seamlessly. Now they can do that, 'cause it's their application. What is the multi-cloud use case, so that's a Supercloud use case in your mind, because right now it's not yet there. What is the Supercloud use case that's going to allow this seamless management or workloads. What's your view? >> Yeah, so if you take enterprise, right? Large enterprise in particular. They invariably have some workloads that are on, let's say, if the primary cloud is AWS, there are some workloads in Azure. Maybe they have acquired a new company, maybe a start-up that uses GCP, whatnot. So they have sprinkles of workloads in other clouds. >> So that's the breed kind of thing. >> Yeah, exactly. That's not what causes anybody to wake up in the morning and say, "I need to have a Supercloud strategy." That's not the thing, right? But now, increasingly you're seeing "pick the right cloud for the appropriate workload." That is going to change quite a bit. Because I have my infrastructure heavy workloads in AWS. I have quite a bit of like, analytics and mining type of applications that are better on GCP. I have all of my package applications work well on Azure, right? How do I make sure all of this. And it's not apps of this kind. Even simple things like VDI. VDI always used to be, "I have this instance I run up" and whatnot. Now every single cloud provider is giving you their own flavor of virtual desktop. And so, how do you make sure all of these things work together, right? And once again, what we have seen customers do is they settle on one cloud as their primary, but then you always have sprinkles of workloads across all of the clouds. Now, you could also go down the path, and you're increasingly seeing this, you could go down the path of, "Hey, I'm using cloud as backbone," right? Cloud providers have invested massive amounts of dollars to make sure that the infrastructure reaches there. Literally almost to the extent that every user in a metro city is ten milliseconds from the public cloud. And so they have allowed for that. Now, you can actually use cloud backbones to get the availability, the liability and whatnot. So these are some new use cases that we have seen actually blew up in customers. I was just doing an interview, and the topic was the innovator's dilemma. And one of the panelists said, "It's not the innovator's dilemma, it's the integrator dilemma." Because if you have commodity, and you have choices on, say, backbones and whatnot for transit, the integration is the key glue now. What's your reaction to that? >> Absolutely. And we have seen, we used to spend quite a bit of time in kind of what is the day zero problem, right? Like, how do I put this together? Conversations are moved past that, because there are multiple ways in which you can do that right now, right? Conversations are moving to kind of, "this is more of an operational problem for me." It's not just operations in the form of "Hey, I need to find out where the problem is, troubleshoot it, and so forth. But I need to make like really high quality decisions." And those decisions are going to be guided by data. We have enterprise customers that acquire new companies. Or they have a new site that they open up. >> It's a mishmash. >> Yeah, exactly. It's a New York based company and they acquire a team out in Sidney, Australia, right? Does your cloud tell you today that you have new users, or new applications that are in Sidney, and naturally just extend? No, it doesn't. Somebody has to look at the macro problem, look at "Where are all my workloads?" Do a bunch of engineering to make that work, right? We took it upon ourselves to say "Hey, you know what, twenty-four hours later, you're going to get a recommendation in the platform that says, 'okay, you have new set of applications, a new set of users coming from Sidney, Australia, what have you done about it?' Click a button, and then you expand on it. >> It's kind of like how IT became the easy way to run the data center. Before IT you had to be a PhD, and roll out, I mean, you know how it was, right? So you're kind of taking that same approach. Okay, well, Ramesh, great stuff. I want to do a followup, certainly with you on this. 'Cause you're in the middle of where this wave is going, this structural change, and certainly can participate in that Supercloud conversation. But for your company, what's going on there? Give us an update, customer activity, what's it like, you guys came out of stealth, what's been the reaction, give a plug for the company, who you going to hire, take a minute to plug it. >> Oh, wonderful, thank you. So, primary use cases are really around cloud networking. How do you go within the cloud, and across clouds, and to the cloud, right? So those are really the key use cases. We go after large enterprises predominantly, but any kind of mid enterprise that is extremely cloud oriented, has lot of workloads in the cloud, equally applicable, applicable there. So we have about 60 of the Fortune 500s that we are engaged in right now. Many of them are paying customers as well. >> How are they buying, service? Is it... >> Yeah. So we provide software that actually sits inside the customer's own administrative control, delivered as a service, that they can use to go- >> So on-premise hosting or in the cloud? >> Entirely in the cloud, delivered as a service, so they didn't need to take care of the maintenance and whatnot, but they just consume it from the cloud directly, okay? And so, where we are right now is essentially, I have a branch of repeatable use cases that many customers are employing us for. So again, building highways, many different ways to build highways, at the same time take care of the micro-segmentation requirements, and then importantly, this whole NetDevOps, right? This whole NetDevOps is a cultural shift that we have seen. So if you are a network engineer, NetDevOps seems like it's a foreign term, right? But if you are an operational engineer, then NetDevOps, you know exactly what to do. So bringing all those principles together, making sure that the networking teams are empowered to essentially embrace the cloud that I created, the single biggest thing that we have done, I would say done well, is we have built very well on top of the cloud provider. So we don't go against cloud-native services. They have done that really, really well. It makes no sense to go say, "I have a better transit gateway than you." No. Hands down, an AWS transit gateway, or an Azure V1 and whatnot, are some of the best services that they have provided. But what does that mean? >> How do you build software into it? >> Exactly, right? And so how can you build a layer of software on top, so that when you attach that into the applications, right, that you can actually get the experience required, you can get the security requirements and so forth. So that's kind of where we are. We're also humbled by essentially some of the mega partners that have taken a bet on us, sometimes to the extent that, we're a 70% company, and some of the partners that we are talking to actually are quite humbling, right? >> Hey, lot more resource. >> Exactly, yeah. >> And how many rounds of financing have you done? >> So we have done two rounds of financing, we have raised about 55,000,000 in capital, again, really great set of investors backing us up, and a strong sense of conviction, on kind of where we are going. >> Do you think you're early, or not? 'Cause, that's always probably the biggest scary, I can see the smile, is that what keeps you up at night? >> So, yeah, exactly, I go through these phases internally in my head. >> The vision's right on the money, no doubt about it. >> So when you win an opportunity, and we have like, a few dozen of these, right, when you win an opportunity, you're like, "Yes, absolutely, this is where it is," right, and you go for a week and you don't win something, and you're like, "Hey man, why are we not seeing this?" Right, and so you go through these cycles, but I'll tell you with conviction, the fact that customers are moving workloads into the public cloud, not in dozens but in like, the hundreds and the thousands, essentially means that they need something like this. >> And the cloud-native wave is driving big time. >> Exactly, right. And so, when the customer as a conversation with AWS, Azure, GCP, and they are privy to all the services, and we go in after that and talk about, "How do I put this together and help you focus on your outcomes?" That mentally moves them. >> It's a day zero opportunity, and then you got headroom beyond that. >> Exactly. So that's the positive side of it, and enterprises certainly are sometimes a little cautious about when they're up new technologies and so forth. It's a natural cycle. Fortunately, again we are humbled by the fact that we have a few dozen of the pioneering customers that are using our platform. That gives you the legitimacy for a start-up. >> You got great pedigree on clients. Real quick, final question. 30 seconds. What's the pain point, for people watching, when do they call you in? What's their environment look like, what are some of the things that give the signals that you guys got to get the call? >> If you have more than, let's say five or ten VPCs in the cloud, and you have not invested in building a networking platform that gives you the connectivity, the security, the observability, and the performance requirements, you absolutely have to do that, right? Because we have seen many, many customers, it goes from 5 to 50 to 100 within a week, and so you don't want to be caught essentially in the midst of that. >> One more final final question. Since you're a seasoned entrepreneur, you've been there, done that previous times, >> Yeah, I've got scars. (laughs) >> Yes, we've all got scar tissue. We've been doing theCube for 12 years, we've seen a lot of stuff. What's the difference now in this market that's different than before? What's exciting you? What's the big change? What's, in your opinion, happening now that's really important that people should pay attention to? >> Absolutely. A lot of it is driven by one, the focus on the cloud itself, right? That's driving a sense of speed like never before. Because in the infrastructure world, yeah you do it today, oh, you do it six months from now, you had some leeway. Here, networking security teams are being yelled at almost every single day, by the cloud guy saying, "You guys are not moving fast enough, fast enough, fast enough." So that thing is different. So it helps, going to shrink the sale cycle for us. So second big one is, nobody knows, essentially, the new set of use cases that are coming about. We are seeing patterns emerge in terms of new use cases almost every single day. Some days it's like completely on the other end of the spectrum. Like, "I'm only serverless and service mesh." On the other end, it's like, "I have a package application, I'm moving it to the cloud." Right? And so, we're learning a lot as well. >> A great time for Supercloud. >> Exactly. >> Do the cloud really well, make it super, bring it to other use cases, stitch it all together, make it easy to use, reduce the complexity, it's just evolution. >> Yeah. And our goal is essentially, enterprise customers should not be focused so much on building infrastructure this way, right? They should focus on users, application services, let vendors like us worry about the nitty-gritty underneath. >> Ramesh, thank you for this conversation. It's a great Cube conversation. In the middle of all the action, Supercloud, multi-cloud, the future is going to be very much cloud-based, IaaS, SaaS, connecting environments. This is the cloud 2.0, Superclouds. And this is what people are going to be working on. I'm John Furrier with theCube, thanks for watching. (soft music)