>>Hey, everyone. Welcome back to San Francisco. Lisa Martin and John furrier live on the floor at VMware Explorer, 2022. This is our third day of wall to wall coverage on the cube. But you know that cuz you've been here the whole time. We're pleased to welcome up. First timer to the cubes we saw is here. The CEO and founder of ZDA. Saed welcome to the program. >>Thank you for having me >>Talk to me a little bit about what ZDA does in edge. >>Sure. So ZDA is a company purely focused in edge computing. I started a company about five years ago, go after edge. So what we do is we help customers with orchestrating their edge, helping them to deploy secure monitor application services and devices at the edge. >>What's the business model for you guys. We get that out there. So the targeting the edge, which is everything from telco to whatever. Yeah. What's the business model. Yeah. >>Maybe before we go there, let's talk about edge itself. Cuz edge is complex. There's a lot of companies. I call 'em lens company nowadays, if you're not a cloud company, you're probably an edge company at this point. So we are focusing something called the distributed edge. So distributed edge. When you start putting tiny servers in environments like factory floors, solar farms, wind farms, even inside machines or well sites, et cetera. And a question that people always ask me, like why, why would you want to put, you know, servers there on servers supposed to be in a data center in the cloud? And the answer to the question actually is data gravity. So traditionally wherever the data gets created is where your applications live. But as we're connecting more and more devices to the edge of the network, we basically customers now are required to push the applications to the edge cause they can't go all the data to the cloud. So basically that's where we focus on people call it the far edge as well. You know, that's the term we've heard in the past as well. And what we do in our business model is provide customers a, a software as a service solution where they can basically deploy and monitor these applications at these highly distributed environments. >>Data, gravity comes up a lot and I want you to take a minute to explain the definition as it is today. And people have used that term, you know, with big data, going back to 2010 leads when we covering the Hadoop wave, which ended up becoming, you know, data, data, bricks, and snowflake now, but, but a lots changed, but what does it mean to be data gravity? It means that staying local, it's just what specifically describe and, and define what data gravity is. >>Yeah. So for me, data gravity is where you need to process the data, right? It's where the data usually gets created. So if you think about a web app, where does the data get created? Where people click on buttons, they, they interface with it. They, they upload content to it, et cetera. So that's where the data gravity therefore is therefore that's where you do your analytics. That's where you do your visualization processing, machine learning and all of those pieces. So it's really where that data gets created is where the data gravity in my view says, >>What are some of the challenges that data and opportunities that data gravity presents to customers? >>Well, obviously I think every enterprise in this day is trying to take data and make it a competitive advantage, right? Like faster decisions, better decisions, outcompete your competition by, you know, being first with a product or being first with a product with the future, et cetera. So, so I think, you know, if you're not a data driven enterprise by now, then I think the future may be a little bit bleak. >>Okay. So you're targeting the market distributed edge business model, SAS technology, secret sauce. What's that piece. >>Yeah. So that's, that's what the interesting part comes in. I think, you know, if you kind of look at the data center in the cloud, we've had these virtualization and orchestration stacks create, I mean, we're here in VMware Explorer. And as an example, what we basically, what we saw is that the edge is so unique and so different than what we've seen in the data center, in the cloud that we needed to build a complete brand new purpose-built illustration and virtualization solution. So that's really what we, we set off to do. So there's two components that we do. One end is we built a purpose-built edge operating system for the edge and we actually open sourced it. And the reason we opensource it, we said, Hey, you know, edge is so diverse. You know, depending on the environment you're running in a machine or in a vehicle or in a well site, you have different hardware, different networks, different applications you need to enable. >>And we will never be able to support all of them ourselves. As a matter of fact, we actually think there's a need for standardization at the edge. We need to kind of cut through all these silos that have been created traditionally from the embedded way of thinking. So we created basically an open source project in the Linux foundation in LFS, which is a sister organization through the CNCF it's called project Eve. And the idea is to create the Android of the edge, basically what Android became for mobile computing, an a common operating system. So you build one app. You can run in any phone in the world that runs Android, build an architecture. You build one app. You can run in any Eve powered node in the world, >>So distributed edge and you get the tech here, get the secret sauce. We'll get more into that in a second, but I wanna just tie one kick quick point and get your clarification on edge is becoming much more about the physical side too. I mean, absolutely. So when you talk about Android, you're making the reference of a phone. I get that's metaphor to what you're doing at the edge, wind farms, factories, alarms, light bulbs, buildings. I mean, that's what you're talking about, right? Yes. We're getting down to that very, >>Very physical, dark distributed locations. >>We're gonna come back to the CISO CSO. We're gonna come back to the CISO versus CSO question because is the CISO or CIO or who runs that anyway? So that's true. What's the important thing that's happening because that sounds like old OT world, like yes. Operating technology, not it information technology, is it a complete reset of those worlds or is it a collision? >>It's a great question. So what we're seeing is first of all, there is already compute in these environments, industrial PCs of existed well beyond, you know, an industrial automation has been done for many, many decades. The point is that that stuff has been done. Collect data has been collected, but never connected, right? So with edge computing, we're connecting now this data from an industrial machine and industrial process to the cloud, right? And one of the problems is it's data that comes of that industrial process too much to upload to the cloud. So I gotta analyze, analyze it locally. So one of the, the things we saw early on in edge is there's a lot of brownfield. Most of our customers today actually have applications running on windows and they would love to make in Linux and containers and Kubernetes, but it took them 20, 30 years to build those apps. And they basically are the money makers of the enterprise. So they are in a, in a transitionary phase and they need something that can take them from the brown to the Greenfield. So to your point, you gotta support all of these types of unique brownfield applications. >>So you're, you're saying I don't really care if this is a customer, how you get the data, you wanna start new start fresh. That's cool. But if you wanna take your old data, you'll >>Take that. Yeah. You don't wanna rebuild the whole machine. You're >>Just, they can life cycle it out on their own timetable. Yeah. >>So we had to learn, first of all, how do we take and lift and shift windows based industrial application and make it run at the edge on, on our architecture. Right? And then the second step is how do we then Sen off that data that this application is generating and do we fuse it with cloud native capability? Like, >>So your cloud, so your staff is your open source that you're giving to the Linux foundation as part of that Eve project that's available to everybody. So they can, they can look at the code, which is great by the way. Yeah. So people wanna do that. Yeah. Your self source, I'm assuming, is your hardened version with support? >>Well, we took what we took, what the open source companies did, opensource companies traditionally have sold, you know, basically a support model around the open source. We actually saw another problem. Customers has like, okay, now I have this node running and I can, you know, do this data analytics, but what if I have 15 or 20,000 of these node? And they're all around the world in remote locations on satellite links or wireless connectivity, how do I orchestrate them? So we actually build an orchestration service for these nodes running this open source >>Software. So that's a key secret sauce right there. >>That is the business model that taking open store and a lot. >>And you're taking your own code that you have. Okay. Got it. Cool. And then the customer's customer piece is, is key. So that's the final piece, I guess who's using it. >>Yeah. Well, and, >>And, and one of the business outcomes that they're achieving. Oh >>Yeah. Well, so maybe start with that first. I mean, we are deployed in customers in all and gas, for instance, helping them with the transition to renewable energy, right? So basically we, we have customers for instance, that deploy us in the, how they drill Wells is one use case and doing that better, faster, and cheaper and, and less environmental impacting. But we also have customers that use us in wind farms. We have, and solar farms, like we, one of the leading solar energy companies in the world is using us to bring down the cost of power by predicting failures ahead of time, for >>Instance. And when you're working with customers to create the optimal solution at the distributed edge, who are you working with in, within an organization? Yeah. >>It's usually a mix of OT and it people. Okay. So the OT people typically they're >>Arm wrestling, well, or they're getting along, actually, >>I think they're getting along very well. Okay, good. But they also agree that they have to have swim lanes. The it folks, obviously their job is to make sure, you know, everything is secure. Everything is according to the compliance it's, it's, you know, the, the best TCO on the infrastructure, those type of things, the OT guy, they, they, or girl, they care about the application. They care about the services. They care about the support new business. So how can you create a model that too can coexist? And if you do that, they get along really well. >>You know, we had an event called Supercloud and@theurlsupercloud.world, if you're watching check it out, it's our version of what we think multicloud will merge into including edge cuz edge is just another node in the, in the, in the network. As far as we're concerned, hybrid is the steady state. That's distributed computing on premise, private cloud, public cloud. We know what that looks like. People love that things are happening. Edge is like a whole nother new area. That's blossoming and with disruption, yeah. There's a lot of existing market and incumbents that need to be disrupted. And there's also a new capabilities that are coming that we don't yet see. So we're seeing it with the super cloud idea that these new kinds of clouds are emerging. Like there could be an edge cloud. Yeah. Why isn't there a security cloud, whereas the financial services cloud, whereas the insurance cloud, whereas the, so these become super clouds where the CapEx could be done by the Amazon, whatnot you've been following them is edge cloud. Can you make that a cloud? Is that what you guys are trying to do? And if so, what does that look like? Cause we we're adding a new track to our super cloud site. I mentioned on edge specifically, we're trying to figure out you and if you share your opinion, it'd be great. Can the E can edge clouds exist and be run by companies? Yeah. Or is that what you guys are trying to do? >>I, I, I mean, I think first of all, there is no edge without cloud, right? So when I meet any customer who says, Hey, we're gonna do edge without cloud. Then I'm like, you're probably not gonna do edge computing. Right. And, and the way we built the company and the way we think about it, it's about extending the cloud experience all the way into these embedded distributed environments. That's really, I think what customers are looking for, cuz customers love the simplicity of the cloud. They love the ease of use agility, all of that greatness. And they're like, Hey, I want that. But not in a, you know, in an Amazon or Azure data center. I want that in my factories. I want that in my wealth sites, in my vehicles. And that's really what I think the future >>Is gonna. And how long have you guys been around? What's the, what's the history of the company because you might actually be that cloud. Yeah. And are you on AWS or Azure? You're building your own. What's the, >>Yeah. Yeah. So >>Take it through the, the architecture because yeah, yeah, sure. You're a modern startup. I mean you gotta, and the edges you're going after you gotta be geared up. Yeah. To win that. Yeah. >>So, so the company's about five years old. So we, when we started focusing on edge, people didn't necessarily talk as much about edge. We kind of identified the it's like, you know, how do you find a black hole in, in the universe? Cuz you can't see it, but you sort of look around that's why you in it. And so we were like looking at it, like there's something gonna happen here at the edge of the network, because everybody's saying we're connecting these vice upload the data to the cloud's never gonna work. My background is networking. I worked at companies like Juniper and Ericsson ran several products there. So I know how the internet networks have built. And it was very Evan to me. It's not gonna be possible. My co-founders come from open source companies like pivotal and Cloudera. My auto co-founder was a, an engineer at sun Microsystems built the first network stack in the solar is operating system. So a lot of experience that kind of came together to build this. >>Yeah. Cloudera is a big day. That's where the cube started by the way. Yeah. >>Yeah. So, so we, we, we have, I think a good view on the stack, the cloud stack and therefore a good view of what the ed stack needs to look like. And then I think, you know, to answer your other question, our orchestration service runs in the cloud. We have, we actually are multi-cloud company. So we offer customers choice where they want to orchestrate the node from the nodes themself, never sit in a data center. They always highly embedded. We have customers are putting machines or inside these factory lines, et cetera. Are >>You running your SAS on Amazon web services or which >>Cloud we're running it on several clouds, including Amazon, all of, pretty much the cloud. So some customers say, Hey, I'd prefer to be on the Amazon set. And others customers say, I wanna be on Azure set. >>And you leverage their CapEx on that side. Yes. On behalf of yeah. >>Yeah. We, yes. Yes. But the majority of the customer data and, and all the data that the nodes process, the customer send it to their clouds. They don't send it to us. We don't get a copy of the camera feed analytics or the machine data. We actually decouple those though. So basically the, the team production data go straight to the customer's cloud and that's why they love us. >>And they choose that they can control their own desktop. >>Yeah. So we separate the management plane from the data plane at the edge. Yeah. >>That's a good call >>Actually. Yeah. That was another very important part of the architecture early on. Cause customers don't want us to see their, you know, highly confidential production data and we don't wanna have it either. So >>We had a great chat with Chris Wolf who works with kit culvert about control plane, data, plane. So that seems to be the trend data, plane customers want full yeah. Management of that. Yeah. Control plane. Maybe give multiple >>Versions. Yeah. Yeah. So our cloud consumption what the data we stories about the apps, their behavior, the networking, the security, all of that. That's what we store in our cloud. And then customers can access that and monitor. But the actual machine that I go somewhere else >>Here we are at VMware. Explore. Talk a little bit about the VMware relationship. You just had some big news the other day. >>Yeah. So two days ago we actually made a big announcement with VMware. So we signed an OEM agreement with VMware. So we're part now of VMware's edge compute stack. So VMware customers, as they start using the recently announced edge compute stack 2.0, that was announced here. Basically it's powered by Edda technology. So it's a really exciting partnership as part of this, we actually building integrations with the VMware organization products. So that's basically now extending to more, you know, other groups inside VMware. >>So what's the value in it for VMware customers. >>Yeah. So I think the, the, the benefit of, of VMware customers, I think cus VMware customers want that multi-cloud multi edge orchestration experience. So they wanna be able to deploy workloads in the cloud. They wanna deploy the workloads in the data center. And of course also at the edge. So by us integrating in that vision customers now can have that unified experience from cloud to edge and anywhere in between. >>What's the big vision that you see happening at the edge. I mean, a lot of the VMware customers here, they're classic it that have evolved into ops now, dev ops. Now you've got second data ops coming. The edge is gonna right around the corner for them. They're dealing with it now, probably just kicking the tires, towing the water kind of thing. Where do you see the vision going? Cuz now, no matter what happens with VMware, the Broadcom, this wave is still here. You got AWS, got Azure, got Google cloud, you got Oracle, Alibaba internationally. And the cloud native surges here. How do you see that disrupting the existing edge? Because let's face it the O some of those OT players, a little bit old and antiquated, a little bit outdated. I mean, I was talking to a telco person. They, they puked the word open source. I mean, these people are so dogmatic on, on their architecture. Yeah. They're gonna get disrupted. It's a matter of time. Yeah. Where's the new guard come in. How do you see the configuration changing in the landscape? Because some people will cross over to the right side of the street here. Yeah. Some won't yeah. Open circle. Dominate cloud native will be key. Yeah. >>Well, I mean, I think, again, let's, let's take an example of a vertical that's heavily disrupted now as the automotive market, right? The, so look at Tesla and look at all these companies, they built, they built software first cars, right? Software, first delivery of capabilities and everything else. And the, and the incumbents. They have only two options, right? Either they try to respond by adopting open source cloud, native technologies. Like the, these new entrants have done and really, you know, compete with them at that level, or they can become commodity. Right. So, and I think that's the customers we're seeing the smart customers go like, we need to compete with these guys. We need to figure out how to take this technology in. And they need partners like us and partners like VMware for them. >>Do you see customers becoming cloud super cloud players? If they continue to keep leveraging the CapEx of the clouds and focus all their operational capital on top line revenue, generating activities. >>Yeah. I, so I think the CapEx model of the cloud is a great benefit of the cloud, but I think that is not, what's the longer term future of the cloud. I think the op the cloud operating model is the future. Like the agility, the ability imagine embedded software that, you know, you do an over the year update to fix a bug, but it's very hard to make a, an embedded device smarter over time. And then imagine if you can run cloud native software, you can roll out every two weeks new features and make that thing smarter, intelligent, and continue to help you in your business. That I think is what cloud did ultimately. And I think that is what really these customers are gonna need at their edge. >>Well, we talked about the value within it for customers with the VMware partnership, but what are some of your expectations? Obviously, this is a pretty powerful partnership for you guys. Yeah. What are some of the things that you're expecting that this is gonna drive? Yeah, >>So we, we, we have always operated at the more OT layer, distributed organizations in retail, energy, industrial automotive. Those are the verticals we, so we've developed. I think a lot of experience there, what, what we're seeing as we talk to those customers is they obviously have it organizations and the it organizations, Hey, that's great. You're looking at its computing, but how do we tie this into the existing investments we made with VMware? And how do we kind of take that also to this new environment? And I think that's the expectation I have is that I think we will be able to, to talk to the it folks and say, Hey, you can actually talk to the OT person. And both of you will speak the same language. You probably will both standardize on the same architecture and you'll be together deploying and enabling this new agility at the edge. >>What are some of the next things coming up for ZDA and the team? >>Well, so we've had a really amazing few quarters. We just close a series B round. So we've raised the companies raised over 55 million so far, we're growing very rapidly. We opened up no new international offices. I would say the, the early customers that we started deploying, wait a while back, they're now going into mass scale deployment. So we have now deployments underway in, you know, the 10 to hundred thousands of nodes at certain customers and in amazing environments. And so, so for us, it's continuing to prove the product in more and more verticals. Our, our product is really built for the largest of the largest. So, you know, for the size of the company, we are, we have a high concentration of fortune 500 global 500 customers, and some of them even invested in our rounds recently. So we we've been really, you know, honored with that support. Well, congratulations. Good stuff, edges popping. All right. Thank you. >>Thank you so much for joining us, talking about what you're doing in distributed edge. What's in it for customers, the VMware partnership, and by the way, congratulations on >>That too. Thank you. Thank you so much. Nice to meet you. Thank >>You. All right. Nice to meet you as well for our guest and John furrier. I'm Lisa Martin. You're watching the cube live from VMware Explorer, 22, John and I will be right back with our next guest.

>> Announcer: From San Francisco, it's theCUBE, covering GitLab Commit 2020. Brought to you by GitLab. >> Hi and welcome to CUBE's coverage of GitLab Commit 2020. We're here in San Francisco, actually, the first CUBE event of the year, and I'm Stu Miniman here with John Furrier, the founder of SiliconANGLE, one of our main CUBE hosts. John, always great to kick off the year with you, and of course, we're digging in on the developer world, cloud native. Nothing better than, you know, the opening keynote talks about, you know, there's a line we've been talking for years, software's eating the world and what are the ripples that are happening on. So, Tom, great to see you, and how come it's so cold here in San Francisco? I mean, I could be back in Boston. >> Coldest winter. I've spent summers here years ago, but it's not summer anymore. But Stu, it's football playoffs. Patriots aren't in, so sorry to hear that our Pats didn't make it. But great to see you. I think one of the things this year in 2020, a new decade, 10 years of theCUBE, looking back, we have been on all the major developer waves since 2010. We jumped on the Hadoop wave with Cloudera. We saw the beginning of that wave of OpenStack to cloud, Kubernetes, containers, the whole nine yards. We've been in the developer community. But this year, cloud native not only is going to continue that expansion of developer CUBE action, but the cross-connect with mainstream, and this is to me the biggest trend of the next 20 years is going to be the open systems model of cloud, just like the open systems interconnect in the '80s created a whole new computer industry, changed the landscape, changed the value proposition, this year, I think we're going to start to see real visibility of value creation where the developers are not just the cliche of the value proposition. That's the cliche. Oh yeah, developers (mumbles). No, no, this is a whole nother game change. With CloudScale, with data, with AI, you're seeing again the importance of this. I think cloud native represents to me that next generation, because with multicloud, there are new criterias out there for success, new requirements. Same game, writing software. Whole new dynamic. Networking, Stu. >> Yeah. >> Compute. >> Yeah, John, and I love actually, I think this was a great show to help us kick it off because you talked about those mega waves out there. We've been watching the growth of some of the huge platforms. AWS was on the keynote stage this morning, Google is doing the closing keynote, and of course one of the major acquisitions, you know, in the relatively recent past was Microsoft buying GitHub. And so we know that developers are so important, but the message we heard from GitLab is it's not about silos anymore. They said not only the dev, the sec, and the ops, but finance and marketing. Everyone needs to get on the same page. GitLab's vision, of course, is that everyone should be using the same tools. That was something that I heard, that we both heard last year at AnsibleFest, that if you're in the same tools, sharing the same information, in the same communication channels, you're going to be able to move fast, and that is what companies need to do. They need to be able to react fast. The business should be able to move. Those software cycles need to be shortened. And that's the mission and the big goal that GitLab has, and I think it's representative of the wave we've been seeing. >> Let's get into the keynote analysis, but before we get to that, I want to, you brought up a point about GitHub. I think there's a real dynamic of GitHub being acquired by Microsoft for many reasons. One is Microsoft's got this cloud called Azure, and not the only cloud in town. Amazon has AWS. And so multicloud is going to be a theme we're going to see more and more of. And so this idea of open and transparent community in open source is interesting in a world where everyone's siloing. I mean, let's face it, GitHub is owned by Microsoft. LinkedIn was acquired by Microsoft. You're starting to see the walled garden world come back again where data is really valuable. And so what's interesting to see is you're seeing a company with GitLab, really one of the first ones to say, "Hey, you know what? "We're going to be anti-walled garden. "We're going to be open. "We're going to be transparent." And again, integrated platform. The cloud is demanding companies have integration requirements that are well above what we saw years ago, and this is now a new table stake. This to me is the real walkaway. What's your thoughts on the GitLab keynote and those industry dynamics? >> Yeah, some great points there, John. Right, first of all, open, fully open. You know, the CEO and the CMO, some of the things they were talking about is sometimes the team doesn't know who's doing the contribution because they're getting regular contribution. They said, "Hey, I didn't see them in the group." Oh wait, that's a customer, that's a partner, someone from the outside doing it. Fully open and transparent and remote. They now have over 1100 employees. Four years ago there were nine of them. And it is fully remote. Actually, do a little compare and contrast. Talk about Amazon. John, how many people do we know that have joined Amazon, and the first thing you do is you move to Seattle, because that's just where they have. Now, of course they've got multiple locations. They've got thousands of employees down in DC, in Massachusetts, in New York City, all over the place, but the core decision-making, even though they are very distributed, Seattle is where everything happens. That's where most of the people live. So GitLab, not only is the company remote, but that's the tooling that they've built really is to enable people to work wherever they are. From GitLab's standpoint, they said hey, we have, one of our software people, she lives in New Zealand, and she has her own power. She's completely off the grid except for her internet. As long as she has internet, she can contribute to the team and participate in the building of GitLab. So it's fascinating. You know, we've talked for years ago the future of work and how that happens. So the tooling as enablement not only to allow everybody to work together, but work together wherever they are and that remote capability, and it is very challenging. You know, we watched Zoom IPO last year, and they're trying to help with that whole wave, but we know that there's a challenging dynamic of being able to work wherever you are. >> So they brought up some stats, interesting. Scale and integration are a big theme. Looks like GitLab's getting it. They made some good calls. Have integration, very friendly integration, very open. And they're essentially consolidating a lot of the different tool chains out there. You look at Jenkins and other things out there, from continuous integration and variety through now mainstream. They got 1100 employees, okay. They got a valuation of $2 billion. They just raised $436 million. They have cash on hand of 350 million and they're going to do revenue. So you have essentially scale in GitLab with an integration story which the cloud guys are being forced. That's my opinion. Do you agree with that and do you think that GitLab can continue the pace of growth given where they're at? >> Well, John, they have something that everybody wants. It's that recurring revenue. So in February 2020, they will have passed the 100 million of ARR, and they've announced that they're going to IPO later this year. We're going to have the CEO on later. I'm a little surprised how fast they are looking to IPO, John. We've seen so many companies that not only do they do big raises, but it's not $100 million, it's two or $300 million. You know, when do you have profitability? When do you go public? So I'm a little curious why there's almost a race for GitLab to go IPO. But absolutely they are catching a lot of these waves. When GitHub was taken off the table, boy did I see Google moving fast to work closer with them. It's no coincidence that Amazon is here, because there's been a little bit of concern from GitHub as to, oh, if I'm doing GitHub, does that mean that I'm kind of being pushed closer to Microsoft Azure, as you said, that cloud. I've read recently GitHub's trying to make sure that they stay independent. We know the GitHub team. And the other big thing we saw is GitLab, about three years ago, they really differentiated themself. They are not just a GitHub alternative. You talked about Jenkins. The CICD is a huge piece of what they're doing. The source code management and CICD, putting those together are the core of what they're doing, but they're trying to be a single tool chain. Boy, when I look at the, you know, the mesh of tooling that GitLab kind of is poking at a little bit, we know a lot of these companies. Some of them are public. Some of them are unicorns. You know, to say that, oh, well, we're going to all of your security chaining. We know how deep and gnarly the security world is. But GitLab, being open, they're going to partner with all of these environments. It's not that you can only use the GitLab pieces. But the audacious goal to say that they are going to be kind of the one tool chain to rule them all is a good goal. I'm hugely supportive my entire career of trying to get rid of silos. But we know that you're still going to have corner cases and use cases that I'm going to need to go deeper. I'm still going to use those best of breeds. And that's one of the things that we're going to look at this year, John, that platform, just like I could go all in on AWS, but I'm still going to use lots of tools on Amazon and I'm going to use other clouds. >> What's your take on, great analysis, by the way. What's your take on as cloud native becomes multicloud where you got edge developing, we got outposts. You're seeing Azure with their stuff. Outposts is Amazon. You now have more pressure on speed and agility than ever before. How does GitLab's story play well into that, and as enterprises have to be faster. Not just enterprises, service providers. There's other new companies doing more cloud and on-premises and edge, AKA multicloud, too. >> Yeah, so I actually, I loved the problem statement that they nailed with talking about the tool chain that's out there is they said more than 50% of devops time is wasted on logistics and repetitive tasks. And John, if you talk about multicloud, it's not just simple to say, "Oh, hey, I threw in a Kubernetes layer "and therefore I can move from my Auzre "to my GCP to my AWS." That's not how it works. I have all the underlying things. I have the interface. That tool and user interface knowledge is challenging to overcome. There are some tools like GitLab, of course, that help me span across those environments. HashiCorp is here at the show, a partner of GitLab. I was just meeting with them recently. And of course, they're going to spread across the multiple cloud environments. But that is really where the meat on the bone is, John, if you talk about multicloud and cloud native. Where are these pieces that can help customers make sure that I'm not too deeply locked into one environment and still being able to leverage the various services that I might want to use across multiple clouds. >> Yeah, I mean, to me, the big takeaway, Stu, on the keynote I made in my notes here is that what I was impressed with is, obviously the transparency that they have is, I love the openness. You know, I mean, this whole silo thing's definitely real. You're seeing more and more. So open and transparent's key. But when you look at what they really have here is the integration story, and cloud is forcing that, in my opinion. But they announced what they call a complete devops platform delivered as a single application, from manage, plan, create, verify, package, secure, release, configure, monitor, and defend. The spectrum of a devops platform. So that to me, I think, is the step that needs to be taken. The question I have is how real is it, in your opinion? Is that what a lot of other people are saying that they have? What's your analysis of that story, reality, legit, and what's their prospects? >> Yeah, well, definitely GitLab has great adoption. The two pieces is the SCM and the CI are the core of what they're doing, and they know that's where people usually kind of walk in the door. Then they kind of land and they look to expand from that. GitLab's made a number of acquisitions, and from 2020, they are going to really double down on making sure that they dig deeper into some of those environments, especially security, planning, and ops were the three priorities that they had there. So, you know, John, we know when you talk about you're trying to be all things to all people, there are going to be things that you will do well and things that you can do great, but, so it is an audacious goal, and with a broad community supporting it. >> Well, we know, you've reported on this and we've told stories about it is that if there's too many tools in an enterprise, you have this tool shed effect where there's no real platform around it, and I call it a tool shed, but if you have too many tools laying around, they're not cohesively integrated, that's a problem that becomes tool sprawl. So this has become an issue. We saw it in the big data world. We saw unification as a strategy for that. Databricks, for example, is a great example of one company that's taken advantage of that trend. Is there a tool problem in the dev space that GitLab's taken advantage of? >> Absolutely, John. And I think something we're going to dig in deep today, we've got a couple of practitioners on, we've got the partners, we've got the executive team from GitLab. John, thank you so much for helping me kick off GitLab Commit 2020 and a massive schedule of theCUBE coverage throughout the entire cloud native multicloud ecosystem. All right, be sure to check out thecube.net for all of the shows that we will be out in 2020 as well as a tremendous back catalog that you can search. For John Furrier, I'm Stu Miniman. Thank you for watching theCUBE. (electronic music)