 From San Francisco, it's theCUBE. Covering GitLab Commit 2020. Brought to you by GitLab. Hi, and welcome to theCUBE'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, 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 the opening keynote. It talks about, there's the line we've been talking for years, softwares eating the world and what are the ripples that are happening on. So John, 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, it was the summer's airs ago, but it's not summer anymore, but Stu, it's football, playoffs, Patriots aren't in, so sorry to hear that our path 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 the CUBE, 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, developers, drill, drill. No, no, this is a whole nother game change. With cloud scale, with data, with AI, you're seeing, again, the importance of this. I think cloud native represents, to me, that next generation, because with multi-cloud, there are new criterias out there for success, new requirements. Same game, right, software, whole new dynamic. Networking stew, 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 is on the keynote stage this morning, Google is doing the closing keynote, and of course, one of the major acquisitions, 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 Ansible Fest, 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 to 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 way we've been seeing. Let's get into the keynote analysis, but before we get there, I want to put 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 multi-cloud is going to be a theme we're going to see more and more of, and so this idea of open and transparent community and 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 walk away. What's your thoughts on the GitLab keynote and those industry dynamics? Yes, 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. You said, hey, I didn't see them in the group. Oh, wait, that's a customer, that's a partner. Someone from the outside is doing it. Fully open and transparent and remote. They now have over 1,100 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, it's 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 where they are. From GitLab 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. We've talked for years about the future of work and how that happens. So the tooling as an enablement, not only to allow everybody to work together, but work together wherever they are and that remote capability. And it is very challenging. 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 integration or a big theme. Looks like GitLab's getting it. They made some good calls. We 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 variety through. Now mainstream, they got 1,100 employees. 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 of 2020, they will pass the 100 million of ARR and they've announced that they're going to IPO later this year. We're gonna 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. 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. Red 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 themselves. 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 at the core of what they're doing. But they're trying to be a single tool chain. Boy, when I look at 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 republics, some of them are unicorns. To say that, oh, we're gonna be all of your security chaining. We know how deep and gnarly the security world is. But GitLab being open, they're gonna 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 of 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 gonna need to go deeper. I'm still gonna use those best of breeds. And that's one of the things we're gonna 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 multi-cloud 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 enterprise have to be faster, not just enterprises, service providers, there's other new companies doing more cloud and on premises and edge, aka multi-cloud too. Yeah, so 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 multi-cloud, it's not just simple to say, oh, hey, I throw in a Kubernetes layer and therefore I can move from my Azure 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 gonna spread across the multiple cloud environments. But that is really where the meat on the bone is, John, if you talk about multi-cloud and cloud native, where are these pieces that are gonna 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 cloud. Yeah, I mean, to me, the big takeaways, too, on the keynote, 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 side of things, definitely real, you're seeing more and more so open and transparent key. But when you look at what they really have here is the integration story as cloud is forcing that, in my opinion. But 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, you know, GitLab has great adoption, the two pieces, 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. They, GitLab's made a number of acquisitions and in 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, where the three parties 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 started 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 taking advantage of that trend. Is there a tool problem in the dev space that GitLab's taking advantage of? Yeah, absolutely, John. And I think something we're going to dig in deep today. Love, 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 to commit 2020 and a massive schedule of the CUBE coverage throughout the entire cloud-native, multi-cloud ecosystems. All right, be sure to check out the CUBE.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.