 Okay. Thank you for that. And hi, everyone. And thank you for joining. My name is Cormac Foster, as you've heard a couple of times now. So I'm really excited today to show you a bit of what makes GitLab single application approach to delivering the DevOps platform special. Over the last 25 years or so I have worked for a lot of technology companies and that approach is exactly why I'm here right now. I will try to keep these slide presentation fairly short, then head into the product itself so you can see how that shakes out in the real world. And again, please ask questions throughout. I'll try to reserve some time at the end for it. If we don't get to them, we will follow back up with you with an answer. So let's get going. So first, let's talk about the problem. For those of you who answered five or more or potentially the folks who answered I don't know this will probably look familiar but when you see most DevOps visualizations in a textbook or marketing copy. It's usually represented as kind of a left to right diagram of stages or an infinity diagram which we have and you'll see that in a second too. And that is the right way to think about the process, I think, but it's not necessarily the right way to think about what the tools actually look like they often look a lot more like this. So in this image, you have multiple tools to support all of those things we just asked you about, you know, project planning and creating the code and testing it CI and deployment and security and monitoring and everything you need to do to take that idea and turn it into software in the hands of users. They all need to function. Now that's the first thing all these things need to be kept running, and they need to communicate. Ideally, any one of those tools should be able to communicate with any other tool. So that you can have a steady flow of information but at the very least they need to be able to connect to the tools that they would sit next to in that end to end diagram. And that and that's something that you're going to need to potentially build or at least maintain yourself so that's the first problem you encounter is just the overall cost of this integration complexity. So you need to not only, you know, design and build and maintain the integrations potentially, you need to manage upgrades, you may need to establish high availability and disaster recovery for each one of those with a separate plan. Those integrations can fail on you they're fairly brittle in many cases if they're especially if they're if you're doing something kind of new or novel and you're out there on the leading edge of that. If you are on the hook for maintaining that or you're paying a very large sum of money to someone else to do it. So the second problem that comes from all of that is time, even if you have all the money in the world you're losing time and it's time from people who may not do this as part of their job. In many cases, they may be developers or operations folks who who really could be doing something more productive and more fun and something that they were actually hired to do. So that's, that's, that's a lot of time you're going to lose and a lot of productivity you're going to lose from it. And finally, I think you're there's there's visibility, every one of these connections is a potential choke point, whether that's a plugin or an API. If it's something someone else has created there may be a limit to how much information can pass through and how much information you can query so you may need something from a tool that the creators of the API never really thought of. And you may not be able to get that so what that means is that people working in other tools may not have the full picture of a story which means that you have emails going back and forth and slack messages, and a bunch of stuff that should be happening within your tools that isn't happening within your tools. And that that's a big problem, an even bigger problem if you work in an industry where compliance and you know regulations generally are a big thing. So this can make a lot of sense to build when there's no other option and when you're early in a in the life cycle of a technology. So 25 years ago, when I was fresh faced and new I was working at a company called CNET comm editorial company they're still around, and we built our own content management and publishing and caching system. And I did that, because at that point everyone was just using static HTML files where our design and our presentation logic and our content were in one document. And that was really lousy for doing things like syndicating content to partners or changing your design on the fly or all the things that we wanted to do to be competitive so we built our own system. It was a competitive advantage for us, but we also became an infrastructure company, and that took a lot of resources. So a few years later we actually sold that system to a software vendor that then sold it as a product and we became, we made some money on the sale which was great and then we became customers of that product. So we didn't have to maintain that anymore and we could focus on our business. These days, no one is going to build that system themselves in the publishing industry because they're just too many good solid platforms out there. And that's what's, that's what I think personally is happening with the DevOps industry right now. The platforms are, you know, are well just speak to us, our single app platform is mature enough so that you don't have to do all of that. So these problems that you're experiencing if you're experiencing those problems if you're in the five plus category those are only going to get worse because we are broadening the concept of what a DevOps team is so security and business teams are critical to software development their stakeholders in this kind of software value chain, but traditionally they've been left on the outside there things that have happened before the process to the left or in this case above, and after the process. So, integrating those folks into the system is going to be those are going to be additional points of integration additional visibility problems you're going to have, if it isn't already built in there to start with and a lot of these tools, especially some of the open source legacy is, you know, an easy word to throw around and I don't know I try to avoid it but a lot of these, these were purpose built systems that didn't really take that into perspective and again you're going to have to manage developments that are that are kind of on the cutting edge. Okay, so that brings us to the idea of delivering your DevOps platform as a single application you know without all those choke points and multiple points of failure so get lab has been doing this since the beginning it's who we are but we've recently seen increased interest in that approach. Gartner recently coined the term value stream delivery platform or vstp to describe that sort of system, something that provides everything you need to create deliver visualize manage all of your value in that sdlc and get it out to the people who need it so we will send each of you a link to a free copy of the report after this session. If you haven't read it. It's it's really a good read and it's not about us specifically it's about the category into which we fit, but we're really happy that the industry has reached the point where they're recognizing the approach that we take as as a category and a way forward. Finally, I think it's important to note that while we want to give you everything you need to run DevOps in one place we don't want to tell you where that place should be. If you want to run it on your cloud or our cloud or on prem behind a firewall, you know on a raspberry pi that's entirely up to you. We run the same software in every location so you get a few more admin features if you're running a self managed instance versus kind of the multi tenant hosted instance that we provide on get lab calm. Our core software is the same so your user experience is the same. You're not going to have any surprises and again, you should be able to run your company and your development your way. We have customer stories on the website at the URL at the bottom of every page but I'll just quickly call it three outcomes directly related to that platform approach. Worldwide started with get lab for source code management and continuous integration delivery, but the single app platform meant they could adopt other aspects of automation like security, like easily without friction they could just light that up. So we have 20 different tools and replace them with get lab. Good news for this view using five or more. And then finally Goldman Sachs went from bi weekly build and release cadence to merging and testing more than 1000 builds per day and that kind of velocity brings a bunch of other benefits which we'll talk about later so they're real world benefits to this. Now let's look at why but I encourage you to check out that page. So there are lots of things I can't show you today. Be happy to demo any of them for you in the future just reach out to us and we'll look at that setup. But today I'd like to focus on two things visibility and action ability. So like those tools and that Franken stack in the beginning, you know, get lab also has dashboards and metrics and role specific interfaces. You know your security team won't be using the same interfaces as your product managers most of the time but they will want to see data from those tools from those other interfaces and other areas of the business. Unlike those other tools and that the stack earlier, all of our share a common data store and a common UX so everything stored in the same place and it's all one application so you can connect from anywhere in the app to anywhere else and just a few clicks as I'll show you. And since get lab is also where you do your work. So this is where the code lives and where the code changes live. That means that you can not just, you know, view the work top down but contribute to it. So quickly here are some examples of what those interfaces look like. We have analytics of your pipelines. We have roadmap views of key initiatives with drill downs into sub projects and work items will demo that. We have high level metrics to just benchmark how well your agile processes are being adopted in the organization and that I'll call this out because it's something that would normally take a ton of integration just to get those high level metrics because each one of these columns here could be a separate tool. At our 2020 virtual commit event which is available on YouTube roles Royce talked about how this interface was actually really helpful to them as they moved a group on to get lab and onto agile processes so they actually use this interface to benchmark their own progress and their own success in their agile transformation. We have lots of out of the box reporting because it is a single app we can we can give you this reporting without integration so you just turn it on start using it we've got a ton of data that we can surface. So very briefly, we allow you to cut issues that you've created by time period by a number of factors to monitor your productivity and your throughput. We'll see that a little bit. Insights provides a really flexible way to monitor any workflow that you can label and it comes with pre canned reports out of the box for things like bug reports. We have a lot of reporting around velocity and productivity of your developers. We have a more detailed view of work in progress to help you identify work that might be stalling. And again, all this is available from day one with no integration, because we're a single app with that end to end visibility. We have a report that reaches across issues which would normally be in something like a project management system, and then your code commits that might be in your source code management system, and then your deploys which could come from a third system that you use for, you know, CD to give you this kind of detailed but well rounded step about your team so we pull that all together again automatically without needing to build those integrations. We're taking a lot of that same information but we're surfacing it in a way that allows your ops team to understand what they need to know about what's going on so again same data store different visualization of it, but all connected. And then here's a dashboard designed for the security team. The neat about this is that they receive that information about vulnerabilities as soon as those are introduced as soon as the code is committed, we're running security tests, and the results of the security tests are going to the, to the folks in the security department through this dashboard. They're also getting surfaced as we'll see in the demo back to the, the person who introduced them so they can learn from that and make changes as well. And it's really easy, as we'll see again in the demo to trace these back to the precise commit where they were created so you don't have to spend a week, kind of untangling spaghetti code built on top of other code. And you can just, you know, quickly figure out what the root cause was undo that and and get going again with you know before it gets complicated. And with that, enough slides, let's see how this actually works in real life. So I'm going to switch over to get lab comm right now as I switch the share. And I will be pulling from live projects that we use to run our business so it get lab everyone uses the product including my organization marketing. So what you're going to see is a system that really can be used by a cross functional team in a production setting. So if I can use it, you can use it. Yeah, someone once said it's, it's so simple even a marketer can do it and as a marketer I can't deny that. So, let's share screen there. Okay, great. To show you the value of a single DevOps platform I'd like to show you a few different experiences from different types of users as they work within a single system so to start with. Let's say I am a CMO or I manage a, you know, product development, and I want an overview of how multiple projects are progressing toward quarterly goals or monthly goals or in this case what we're showing here. It's a quarterly map but I could just as easily, you know, break that down by by months or weeks. I can look at things by, you know, sprint or whatever time box construct I want there. So, in this case, I have searched on a string of use case now that's what we call our campaigns and marketing. As you can see, there's a use case go to market overview. Within that the continuous delivery use case go to market. I can see here that that is 58% complete. Now that may be all I need in which case I can look at it I can open this up and say 58% complete looks like it's on track and I can go about my business, or if I want to know more I can just click in. I can look at sub epics I can look at the projects that are sitting within this. I can look at individual issues that might be sitting within this. And again that may be all I need but let's say I want to dive deeper into that. I can then go into one of them in this case will go into the use case GTM overview epic. This is this is a view of the epic which contains sub epics as well again, these could be whatever you want they could be products or projects or any initiatives that you would want to create at a high level that would be used to organize other work. So, here I can look and see that here in my VC and see version control and collaboration use case. There's one issue that needs my attention. So I can open that up. I can see something going on. See that that issue is in the resource page. And it's in solution demos. Okay, so from there and just a couple of clicks I've gotten into a detailed say project or initiative, and I can see that there's something going on. So if I go into the issue itself that that had the notification, what I'm looking at here is I can see pretty quickly that there's a due date of May 8. So somebody slipped to due date, or someone forgot to close this out or something happened, and I need to know the context behind that so I know whether this is just something that's an oversight where I can remove that due date, or if I, you know, somebody's what I can do here is all of that collaboration that happened around this is in one document it's in this issue. So I can look down. I can see that there was a bunch of collaboration. I can see that ultimately this was closed seven months ago so it was closed on time. It looks like someone just forgot to to update the due date, but I can also see that there was a code change, or a merge request and all the merge request is the code change in the workspace around that that is attached to that. So that's a merge request right here and I can see that that was actually committed, the pipeline passed and this code was, and this code was pushed live. So I can then click into that merge request. And in one spot I can see, here are all the code changes that were made to all the files that were changed. So if I really wanted to dig in from with that context I hadn't say okay what was changed you know here's the copy that was there. Here's what it was changed to all the way down. I can see the pipelines that ran from all of those those code changes and what happened to them that anything break and it didn't get pushed to the website. I can see the individual commits that happened, every person who who made a change that and push that. So I can then say I see that a problem happened here during this commit I'm going to roll that back. And then again, the overview there is collaboration as well. So this is collaboration that happened in the workspace itself. So that is always going to be tied back to the issue that spawned it as well. So, with just a couple of clicks I can go from this into the actual code changes. And when I talk about action ability that's that's what I meant so there's visibility there's you know having a power BI dashboard that tells you whether things are on track. But that's not necessarily connected to anything and usually the output of that is I need to send an email to someone to say what's the problem with this or make this happen. But what we have here is the ability to just drive all the way into the work should I choose to go all the way into the work. I can unblock things myself. I can assign this to someone new. I can make a comment I can approve a code a code change and if you're in a, you know, a smaller company, perhaps where you're wearing multiple hats. This is what you do on your, you know, your daily job you don't want to be context switching. You're looking at high level reporting here and then trying to, you know, search through files to find out where that change was made, and then going into a third system to tell someone that they need to go take a look at this. You want to be able to do that all in one place so that's what we mean when we say action ability. One other thing I'd like to point out. When you look at an issue. Over here we have something called labels. So labels are really neat. I'm a, I'm a big fan of labels because they're super flexible and super powerful. A label is a customizable attribute that get lab users can apply to issues, but also to merge requests that code change we just saw in that workspace, or to epics. So you can define whatever classification you want. So here we have this identified as something of interest through the strategic marketing team. If you want to do that should probably be removed given that we've already established that this is already done. And then we have something here, so marketing status plan. And that's what we call a scoped label. So scope labels are mutually exclusive labels that you can use to create. So let's just say we go to marketing status. You can see here their marketing status work in progress plan design review. Now, these are mutually exclusive so if I mark this as marketing status review, it's going to remove the marketing status plan label. One of the great things that you can do with something like this is you can model a custom workflow. So we have a backup at CNET and we have an editorial workflow where I'm going to create a document, and then I'm, I'm going, so we'll have a writing stage or a spec stage a writing stage, a copy edit, an edit copy edit and a design stage and then we'll have a publishing stage final review or something like that. I can create these very simply as these scoped labels here. And when a document moves from one stage to another the new label gets applied. The old label automatically gets gets removed and I can track that all of these labels of things I can search on I can sort by, and then I can track in something that we have here called insights. Insights allows you to track anything you can label in issues. So this is a live dashboard that we use in the strategic marketing department in which product marketing sits. So here we're looking at the volume of requests coming into strategic marketing by by status you know are these new are they in the triage state have they already been assigned are they done. We have a number of things we're tracking here. Again, is this for competitive intelligence is this something that goes to the tech marketing teams is something that goes to product marketing. Now within product marketing, we've also created our own reports, where we can look at different labels. So labels like you know what's open and closed. Are these are these going to be external facing, are they internal facing projects we're working on. Is it something else. So again, anything you can label there are a ton of different things we can look at with labels here who are we doing this for we're doing it for sales we're doing for public relations. So this means to you, you can label and once you can label it you can visualize it because it's all one system. And again labels can be applied not just to issues but to merge requests and epics. So you can search across different kinds of work and different categorizations of work and get to where you need to get to. I am again a huge fan, but I also wanted to show you something called value stream analytics because we don't want you to have to write something custom to start tracking your productivity. So because we are a single, a single application for everything you're doing and because the work is actually happening here in get lab. Value stream analytics just runs as soon as you start pushing issues and merge requests and and code through the system. This is going to start tracking that information. So let's just assume for instance that I am something like I'm a development manager, and I want to be able to identify blockages in the delivery of value to to my end users, and then I want to do something about that. So I can see here, you know how many commits I'm doing over the last 30 days how many deploys we're doing deployment frequency, not total number of deploys and how many new issues are coming in so that's great at a top level that's that's very useful information that that I'm probably going to reference on a daily basis, but I can also look at the workflow. So what we've done here is created a default set of steps that we feel reflects a large portion of the software development lifecycle for most of our customers and this is what you get out of the box. So we can see that, you know, in this case it's taking me less than a minute to create an issue. Great. That might sit with someone in the planning stage where an issue is being worked on or revised for a day. And then it takes three minutes to make some of these code changes so these code changes here since we're dealing with the public website a lot of these are probably just copy copy edits, small changes that sort of thing. It's a testing process but you know look at this 18 hours, things are sitting in review for 18 hours. And some of these are very small code changes that only took three minutes to make so you could probably review these very quickly. So, you know, overall it's taking me, you know, a couple of days to get these changes out which doesn't sound so bad. But if I could assign a few more people to review code, then I could potentially start delivering that you know four or five or six times as fast because it's just after the issue is live and people start coding, because the vast majority of my time is being spent there. Now since we're connected again, I can look at something so this for instance this has been in there for four days. So one of the contributing, one of the contributing merge requests, I can jump in there. And see what the changes were I can comment on these. You know, so I could for instance, say, you know, why are we doing this. And I could, you know, make a suggestion instead where I suggest something else, and then I could start a review from that and someone could accept that or reject that or I could push it along or do whatever it is I need to do. And all of that, again, from what would otherwise be an analysis only tool and another and you know with it required and integration underneath it to actually get that information into one place so not only can I see it but I can do something with it. And then finally, I'll skip to a project that has less information but I have, I have greater permissions on this particular one. This doesn't work for you. You can hide the stage, you can just make it disappear I won't do that now because other people are still using this project but I could, I could get rid of any of these that I don't like or that don't match what I'm doing. I can also add a stage. So I could call this, let's say it's from issue created to issue label added. And let's say I wanted to call this category categorization, fine, you know, And I could add that as a stage if it really mattered to me how long does an issue sit in a queue before someone says oh that's what this is they do their triage and they assign a label to it. And that would show up there and I could order that stage however I wanted. So, while we do want to give you tools out of the box we don't want to constrain you to using this tools if they aren't going to fit for what you do the same way that we want to give you a DevOps platform but we don't want to tell you what you know where you want to run that because it's your business it's not ours so we'll give you a place to get started, but we want you to be able to build on that. And then we were talking about MRs earlier one last thing I want to show you the merge request again, your changes, your pipelines that have run different commits, and then any collaboration that happens there if I say you know this is a great idea is a bad idea I'm going to upvote this or downvote this I can do all of that sort of stuff. And again I can label it just like I could with an issue. But what's, what's, I think the best part of this to me is that we showed you the interface that might be the kind of go to interface for someone who's a product manager of CMO. This is probably the go to interface in most cases for a developer, as developers are committing code all day, and they're interacting, they're either reviewing other people's code as we just saw, or other folks are reviewing their code and they need to collaborate that explain what they did, accept some changes make some new changes that sort of thing. Now, when I'm a developer and I do one of these commits here, it's going to run a pipeline, and that pipeline is going to include tests. We include the ability in the product to run security tests of various sorts, you know, static application scanning where we're looking for standard vulnerabilities in the code, dynamic application scanning where we will actually automatically create what we call a review app where we set up a, we set up a running instance of your application so that we can then test from the outside against that. And all of those results, so all the results of that so the scans run every time you commit code and all those results wind back in the same system in the interface that you're already using so the security folks are going to see the results of security scans, but so are you. So here if I'm a developer. I can see that we've detected three potential vulnerabilities, none of them in this case are critical, that's great. I can see I can then if I want a desk dynamic scanning detected for high level vulnerabilities I can click into that for more information to license and policy violations, all these things that normally would take forever to unpack, because they're going to get pushed along and people are going to build on top of that code until security finally looks at the output and says wait there's a problem, and then that could take anywhere from hours to weeks to figure out. And you might have to undo a whole lot of work one fine so I as a developer I can make this fix right now before it goes any farther makes me a better developer I learn so I won't do that again. But it also saves all that time and money. And then finally, if you're audited. This is wonderful I don't know how many of you have been audited before but I've worked at companies that have been audited and it's a terrible experience for everyone including the auditors. If you're up spend two weeks trying to figure out what you do then they spend another month trying to figure out where you didn't do what you normally do, and then they interview you for another two weeks about what went wrong and how to fix that. And in this case, I can hand this merge request over to an auditor and I can say, here's you know you can trace this back to the issue, the discussion that created the merger that ultimately led to the merge request. You can see every code commit you can see the impact of every one of those. You can see all the vulnerabilities that were exposed you can see how they were fixed. And if they weren't fixed you can see why and you can see who signed off on it and what that means. And if I'm an auditor this just made my day and I can move on to do something else very quickly and everybody wins. So, again, these are just examples of how visibility and action ability really work well with a single app DevOps platform. There's a ton more that we can do there are some great demos we have out there on things called auto DevOps, where you can spin up your entire DevOps process. Just kind of out of the box it's essentially push button DevOps. There's a lot more we can talk about and we'd be happy to but now I will stop the share and be happy to take any questions. All right, excellent. Thanks so much kormick. Let's see. I know that we've got some questions already bear with me just a second. What my doc here. All right. The next question we have is, can I use the rest of get lab with Jira, we're using Jira right now and that is not something that we can change at the moment. So yes, absolutely. So, thank you for asking that actually because we do have a platform deployed as a single app. This is not one of those. I won't name companies but back in the 90s there were several companies that would sell kind of platforms as lifestyles where you would have to adopt everything and then they would, you know, you buy the software for half a million dollars and they'd sell you a million dollars of teaching you how to turn it on, and you'd have to rip and replace everything so this is absolutely not that we have a lot of customers who are working with Jira and other tools. So this is the, you know, Jira just works for them, and they prefer to use Jira and you know that's great if there's a long term coexistence kind of thing we we actually in the last few months we've come out with several new integrations with Jira, and we want our users to be happy to be able to view get lab issues for instance inside of Jira and the results of those security scans inside of Jira and the kinds of things that would otherwise take again a lot of integration effort on your part. And then we have some folks who say that, you know, whatever, whatever tool that is is something that you know I like the value of this, this platform but, you know, for the foreseeable future for these projects I don't want to, to move off of that yet. And, and that's something as well we see a lot of those kind of hybrid environments where new projects might be entirely on get lab and others might have, you know, a different kind of architecture behind them, and we can absolutely do that. Awesome. I'm going to just keep moving along and if anyone else has questions please feel free to go ahead and continue to add those to Q&A and we will get to as many of them as we can. Next question we are trying to initialize our first repo. Can you offer some recommendations on how to handle secrets for Kubernetes. So yes, I am not the right person to talk about secrets management we have a whole ops and GitOps team that does that but we can follow up with the right person for that there's a fellow on the marketing team named William Chia who does a lot with that. We have, we have a number of folks from our solutions architects to, to product marketing to the actual product managers themselves you can get better answers than I can. Awesome, appreciate that answer and I have made a note for the individual that asked that question and we will get an answer to you and direct you to William. Next question do you have the chance to view a side by side view of the changes instead of interweave can you comment on a peer review in line with the code to ask questions. Yes, so we actually offer as well a web ID that, you know, people, the developers love their IDs and their editors and are very wedded to them. But sometimes you just want something that you know will always be there and will run and so our web ID is great, particularly if you're making, you know, some people spend their whole day in there but if you're just making a quick change to a file that sort of thing. So if you don't want to, to spin up what in some cases some of those ideas are pretty monstrous, we have that and the web ID actually has that functionality integrated into it as well. So yes, and you, you absolutely can comment on those those code changes as well. We have a very long discussion threads that go on in MRs. We have a long to offer consultant services to help establish an initial repo. We have a demonstration product that works locally but fails when deployed. So yes, again there are other folks who probably have a better answer to that but we do have a professional services arm. We do not want to be, we are not a services company and the way that some other folks are where you know the product exists to sell you the product. So we do have professional services to help with things. We also have, you know, customer success managers and solutions architects who can show you those sorts of things and we have a number of partners at various levels who do various who build on top of GitLab in different ways so there are probably a number of ways to answer that question and we can put you in touch with someone who can answer that more accurately in terms of what makes most sense for your situation. How can I integrate GitLab with a chaos engineer platform such as Gremlin. We actually did a partner webcast with AWS and Gremlin in September. I've actually sent the link to that recording in the slide deck over for that question so because we're kind of running up against time I'd like to get to the last two questions here before we close. Next question is this a hosted solution or is it only on cloud for government work there are certain programs we are not allowed to use cloud for anything that has to be hosted on site. Do you have options. Absolutely you have options and we have a number of government clients. You can run this in just about any cloud. And again you can run it in our cloud as well for you it sounds like that would not be an option but we have. I believe hundreds of thousands of self managed instances running right now. So you can absolutely run this on prem. Right. Let's get to our last question and we will wrap up. What is the minimum subscription level to modify the stages you showed adding and removing some in the psycho analytics. Oh, that is a, you know what I so value stream analytics exists at all levels of the product and to be honest I will I will confirm that I will confirm that right right after this and get right back to you. Very, very good question I but I don't want to I think I know the answer but I don't want to be wrong so there may have been a move lately so I will I will check that. That is totally fair. Awesome. Well, thank you everyone for joining today if there was a question that Cormac was not able to get to I have taken notes here and we will reach out directly to you with specific answers for those so we really appreciate the questions we appreciate everyone being here today. Just a reminder this was recorded and this will go out to everyone on today's call in the next few days. So with that said, thank you all for joining have a wonderful day, and we hope to see you soon. Thank you.