 I'm Eric Johnson, I'm the CTO at GitLab and I'm excited to be here at commit where this year's theme is innovate together. And with that, I want to welcome a special guest and partner, Rick Carey, the group CTO at UBS. So UBS is one of the world's largest financial firms and they provide advice and solutions to clients worldwide. And we announced our collaboration on DevOps about a year ago. And Rick, I thought you could start by talking about your initial goals for this collaboration when we set out together. Thanks, Eric. We want technology to be a differentiator for us at UBS and for that to be able to engineer solutions that offer a truly seamless client experience. To do that, we thought last year about how to actually change that experience for the engineers and developers and been giving them the best platforms and tools. So we created DevCloud. So DevCloud revolutionized the way UBS builds and engineers and develops with a single DevOps platform and allows a cloud-based service-oriented development lifecycle. Now, GitLab is a fundamental part of DevCloud. Out of it, we wouldn't be able to have that seamless experience. And it allowed us to pull ahead of many of our competitors and break down the barriers between coding, testing, and deployment. And we have an expression about at UBS that all developers wait at the same speed. And anything we can do to reduce where they are waiting for something is value added. And GitLab allows us to have that integrated experience where they're not waiting for what they have next, what goes on, previous things, next things, and so on and so forth. So they build cloud-native applications on a cloud-native platform and having a best-in-class developer experience. That was our goal and you couldn't have been better partner to us as we started to go forward with that. Great, this sounds like it was very much in line with how we view our differentiators where a single application for the whole DevOps lifecycle and of course we're open source and so it's not just GitLab developing our product, it's our community and it's our users and customers as well. And we typically see companies benefit from the faster cycle time, reduced admin and maintenance overhead and better quality and security as an output. And the end users benefit as well. So we see engineers talking about being more effective, how easy it is to collaborate on a single platform and how they're able to identify security risks much earlier in their process. So maybe you could take us through some of the details about us, the setup of that production environment. Well, the plan was pretty ambitious. We felt that doing this over a long period of time wouldn't really meet the ethos of what DevOps and being cloud-native and really what you offered to us. So we did a lot of work to get it up and running into a user format and then we did what we kind of called a soft launch and we did that at our hackathon. And if you remember the hackathon last year was in the right and smack in the middle of COVID. So your traditional hackathon where you're locking people in the same room and you have them all there and you have a very regional-centric approach, we knew we couldn't do that. And we wanted to have truly global development yet still have that seamless team experience. So that soft launch of DevCloud was our hackathon and boy, was it amazing. The output of there, it was hard to pick a winner because nearly every program, every team built something absolutely incredible in such a short amount of time and they got so much done that even they as they were channeling and chatting with each other saying, I can't believe how easy it is to get this done. It was tremendously hard to pick a winner and that's something we're really proud about. And then once the hackathon was successful, we knew that we were gonna be able to migrate the rest of our engineers to DevCloud. Yeah, collaboration is one of the GitLab's core values and it seemed key to this project. We set common goals, we're in constant communication and we were always working together to move those roadblocks. And I wanna highlight that again, that this was an all remote globally distributed project team required no in-person collaboration for the life cycle of this GitHub project. And it was completed as I understand this past winter, late 2021. And I must say, it's uncommon in my experience to see such a large organization let alone one in such a compliance driven industry as finance to take on such a large project and deliver it all in time. In my understanding it was not just source control management but also CI, which is incredibly impressive. What we made it possible was, and we have a little joke, whenever we give a DevCloud update, we say, we're far from perfect today, but we're improving. And I think as we looked and worked together, you know, in a kind of an open source model was every time there was a gap or an issue or something we just needed your help with, we could reach out to you and say, can we work on this together as the way to improve this? And that's the value. And that's one of the reasons we went with GitLab is your open source mantra allows the benefit for what we contribute, what you contribute, what others contribute and to build that fantastic experience. And it never, you will never have a perfect fit for purpose product day one for anybody. Every company is gonna be different. But what we found was when we worked with you together when we had a gap or an issue or something that needed to be improved upon, we found a really easy path to do that. We improved, we engaged and everybody benefited from that. And the teams are really proud of that. The teams are proud of that. They were able to do that work themselves sometimes, work with your engineers to get it done. And it was a fantastic experience because there's no one size fits all. You're gonna have to fit into a company that's complex financial services, a lot of complexity in that, but other industries as well. And what that is important is to be able to collaborate, work together and then when we improve the product for one and improve for all. Yeah, absolutely. I mean, we've seen a number of benefits from our open source model. As a board member of the Linux Foundation, I'll take the opportunity to quote Linus's law, which is with enough eyes, all bugs are shallow. We've certainly found that to be true. But I think more importantly, you view what most companies consider traditional product development as really a process of co-invention with our users and customers. And I think that was definitely realized in this case. We see UBS team members contributing to our forms, which is fantastic. And at a higher level, we're both meaning UBS and GitLab members of the Finos, the Fintech Open Source Foundation, as well as the CNCF, right? Yeah, I think they're both usually important for both of us and being able to set those standards and to understand what it is, especially being cloud native and having GitLab being a cloud native platform. And I wanna point out for a lot of people out there, is that just because we say dev cloud and it's cloud native and it doesn't, it doesn't mean we can't develop for non-cloud native or traditional applications. We do development for both our cloud native applications and our traditional applications on-prem, all on dev cloud, all through GitLab. And that contribution and being able to, as we create our journey to being cloud native and the cloud native computing foundation is a fantastic partner. It doesn't mean you have to make that big day one, right? You can have that kind of incremental journey to be able to have a cloud native experience for the engineers day one, even when they're building not cloud native applications. But you get encouraged to do that. What we find is they really love it and they wanna continue to be in that world and they continue to make that journey. And there are a number of examples of that cone mention I mentioned. I think most prominently the auto-scaled shared runners that the UBS contributed, that was great to see. I know there was some UBS specific self-paced training that we launched and the hackathon you mentioned, I wanna say there was something like 40 or so tier one applications that were launched in that single hackathon period, which is incredible. And it was bidirectional. I mean, from the GitLab side, we learned a tremendous amount about the compliance and risk processes that are unique to the financial sector. And we benefited from that and our community will benefit from that as well. So with that, that kind of brings us up to current day I'm curious to Rick, where you think we'll go from here? Well, we have over 12,000 people on DevCloud now and more to come. The best feedback we've gotten so far, I had a business person in the call and he wanted to actually do some development and he was complaining about all the ways that he was told that he had to do development. And then I said, well, then you should use DevCloud. And he said, oh, you, that's DevCloud. I love DevCloud. It's the other tools that I can't stand. Everything's great on DevCloud. So, and this was a business person. So not just our engineers, not just the hardcore developers, we look and expanding out DevCloud to anyone who's doing an engineering experience. And they rave about it when they get there. There's a little bit of a transition cost. Don't get me wrong, it's not free. You got to do the work to get there. But the payback is immediate to get there and you're more productive, you're faster. We never talk about the costs of doing things like this. We talk about the productivity, because that's what sells, right? We ran our hackathon, by the way. We never actually, we didn't make this an objective, but our hackathon this year was one seventh the cost from an infrastructure perspective from the year before because we ran on DevCloud. And so we'd like to see more templates in there. We've got things going on in the SRE space. There are more personas that we'd like to see be able to engage DevCloud and get the benefits of that type of integrated experience. And I understand, I've heard a rumor that you're getting into the machine learning space, which I'm very, very interested in. So I'd like to see where that roadmap takes us there. That's right, yeah. In June, we announced that we acquired a product called Unreview. And what this is gonna do is use machine learning, as you said, to identify the appropriate code reviewers for new merge requests entering a code base, which is exciting. And it's a chance for us to do applied ML and it's going to effectively balance review workloads across your team to make the team more efficient and more resistant to vacations and other things that are important to developers. There's some other things orthogonal to this project that I think UBS will be eventually benefiting from. I know there's gonna be some more workshops that UBS will be able to take part in. We're rolling out this so-called door four metrics. And so, deployment frequency, lead time for changes, change failure rate and time to restore service, a standard set of metrics that are becoming kind of a way to measure the health and the productivity and efficiency of any development organization. We'll be able to get that natively from GitLab. And that's just a piece of what we're broadly calling value stream analytics. And so, a benefit of the single application is you've got your issues, your merge requests, all the other sort of primitives or artifacts along that journey from taking an idea to production and because those all live in the single application we can extract intelligence about that life cycle and point you towards bottlenecks where there may be opportunities to improve. Now, I think the metrics and being in that one single ecosystem, Eric, is absolutely crucial and it gives us opportunities. We had over a million successful builds in the first six months of DevCloud and that's the difference. When you can see what's going on there in that entire experience and start to stream that was value stream and get them all aligned in that space, the insights that you can start to gain are tremendous and then using the machine learning on top of that to be able to start to not only report about the past, but to predict about the future, that's really exciting so that we can actually start to say, we'll have this delivered for you based on the complexity that we see in these sorts of time frames. Unbelievable, Eric, I can't wait for that. And I just think the more that we see the more that we work together, the better that these products become for us and for you as well. It's just fantastic experience. And when you talk about Agile and DevOps, it's a great concept until you get down to how do you actually implement it? And that DevCloud is, it's an implementation of all the great ideas, but in such a way, a fantastic experience for everybody involved. Good, as important as people are and that's primary for us, I always say you can't measure and it seems like you're now well on your way. It's living that role, which is fantastic. Well, Rick, I just wanna thank you again for the conversation today. It was a pleasure to see the teams collaborating with one another. We were very impressed by UBS's development culture. It was very complimentary to our own and I look forward to our continued partnership. And do I, Eric? I think that that complimentary nature allowed us to do something really spectacular and a really short amount of time, faster than a lot of people thought was possible and you couldn't have been a better partner to us and we look forward to continuing that.