 All right, it's time. I hope you enjoyed my fun fact and if you haven't read it yet We are soon to be 222 weeks away from 2 2 2 2 2 2 2 2 on the second day of the week We count from Monday. I thought it was funny We probably won't be able to release Kidlife 22 by then unless we're very aggressive in a major release And this actually typo it should be no more than three minor releases We should have a major and a minor minor and you can have at most four releases including long story short Would be great, but let's see. Let's see when we're there Yeah, yeah, we could do lots of minor releases of 22 and release 22 and 22 but getting to the 22 major is very hard alright a product update of today, so Last few updates what I did is I went through the releases. I usually I shared something else with it And I saw that a lot of people are actually covering what we are shipping in releases Plus that tomorrow we have a kickoff where we announce what we are going to release in 10.3 Last time already gave you an update on what we're releasing in 10.2 So I figured I talked a little bit about what's on my mind And what is on my mind? So there's two Big things on my mind and it's the Enterprise Edition premium and ultimate So I wanted I want to discuss those two today so let's let's start with ultimate ultimate is a I Think one of the most exciting things to me that is coming It's a very important thing for GitLab releasing a new tier It means that all of us have to start thinking about how in terms of product How can we create additional value in terms of sales? We have to now have another product to sell So how do we bring it to customers and how do we balance that with the other things we already sell? And even in terms of engineering because there's a lot to think about because now we have yet another Point of complexity in a product right now We can have a feature committee in C, E, S, E, P and ultimate and or ultimate so That all is quite complex and the fact that we're doing this on a short term is very exciting But a lot comes looking at it So I figured I would go over some things To start your minds and to also help you think of questions that then we can discuss at the end And then hopefully we'll discover things that I haven't thought about and that we solve before we actually ship ultimate so To get into it. So the idea behind ultimate is is that it's the ultimate version of GitLab So everything we can release should be in ultimate with the idea that eventually it will be Worth and people will be more than happy to pay a thousand dollar per user per year or nine hundred nine nine And and I believe we can get there and I think we have a good vision to get there, but there's not to be the First steps we're gonna take is that today if you have GitLab it replaces your SEM tool Of course, it replaces also your CI tools and you should be tools And that's worth a lot in itself and it's definitely worth the price tag that people pay for Premium, but if you want to get to the price tag of ultimate We want to offer additional things and we're starting off with portfolio management tools and security tools But we want to add more things in the future And that's one of the things that I would like your help with with thinking about what and the way I think about it today is that a typical setup you see is something like you have Jenkins in an organization and I have some sort of Git Source control management system sometimes it's just GitLab and sometimes something else Then they use Jenkins for CI and Artifactory for Their artifacts and then like SonarCube something like SonarCube to do for instance Static analysis tests and then usually a whole bunch of more tools And I want ultimate to be replacing all of these tools So you know that today we can already replace the JIRA part for the most part if not almost all That should be all We do the full Git thing we do the full CI thing we can easily replace Jenkins And we're getting close to Artifactory but not close enough and in SonarCube the security part We're not doing yet and that is what Ultimate is supposed to be it's supposed to be that one tool that replaces all the other tools And having a single tool has all the benefits that of course you're aware of So what is the actual plan the actual plan is that we're going to release Release I say and I don't say lunch We're going to release ultimate with 10.2. So that's on the november 22nd That's very soon. You might be thinking and that's why I'm talking about this And initially it will be available for a limit time for the same prices at the price edition premium And the thinking here is that It will only have one feature, right? So if you're buying ultimate the only addition you get is epics and epics is a very nice feature and one that people are really waiting for But it's obviously not Worth a huge price jump, right? We are aware of that and our customers are definitely not Done so they're aware of that as well But the idea is is that if you lock in the price now then you get of course all the upgrades and all the Additional features that we're building over the coming year Um, and those features will of course be portfolio management features securities can web IDE Um, and and many other features and there's a link here where you can see What is the current roadmap in like high level and what are the specific issues and there's a number listed there But we're looking to add more of course over time Uh, let's move forward. All right. So that's the ultimate. That's the Quick summary of ultimate and I hope it spawns some questions you have you can drop them in the chat already if you have them now um But it's important to realize that introducing a new tier doesn't mean that we shouldn't look at the other tiers, right? Uh, we have right now enterprise addition starter and premium out. Those are the two things our customers can buy Um and enterprise addition starter is incredibly cheap. It's Ridiculously the cheap. It's cheap for a get solution let alone for a get solution with the number one leading ci product. So it's a very very good offering and therefore it's important that we Add additional value in enterprise addition premium. So let's go to that Premium also, this is like the coolest gift effort from adventure time great show should definitely watch it So premium it's right now. It's our most Important product, but it's also our best product, right? Because if you buy good luck today if you buy premium today pre 10.2 you get all the features that get left has um and premium has It's a large part of our revenue a very significant part and in particular It has a major impact on our average selling price in other words if we sell more of eap Every selling price of kitlet goes up and if this every selling price goes up That's very good for a revenue. And of course we want to grow the company um, so the real challenge here is not so much Selling eap in itself because it's a very good product The challenge is selling eap in compared to enterprise addition starter And when I say selling what I really mean from my perspective is Creating the value in the product. So making sure that eap is actually five times worth more in terms of product features Than enterprise addition starter And of course we're always competing with c eap. That's the biggest competitor, which is Free which is great and it's important So how are we doing that? um I I I am of the opinion and I believe that The current price for premium is a fair one. I think the value is there so One you get much more control. So you have things like audit logs audit user group single filters commit restrictions and writing a whole bunch more in 10.2 And on top of that, you get all these scaling features that are very very good it's even better integrated to JIRA and What I should address and one of the reasons why I didn't want to discuss this is that we are going to finally ship gl in ga meaning generally available meaning anyone can actually use gl in 10.2, which is What we're currently aiming at but I I like to be a little bit restrictive here because of our history So 10.2 10.3 gl will be available for everyone. So it means that we create this massive additional value with enterprise addition premium because it allows you to replicate your uh GitLab instance across geographies And in the beginning of next year and following that will continue to invest in enter the price addition premium um Yeah, they have another slide on this. Yes. I did so Given that we are shipping ultimate. How are we going to handle premium? Well, one thing that we're doing is we're prioritizing Features and things that are interesting for the typical customer of premium So we're thinking very much What are the things that we should add to GitLab? And then we try to prioritize the ones that are more likely to end up in enterprise decision premium So that we still continue to add value to premium over time So even though we're introducing ultimate will continue to invest in premium and continue to add Features there that I think are in line with the features that we've released so far If we're doing something completely new like the web IDE and like security That will end up in ultimate. But otherwise it will most likely end up in premium Given the restrictions that we have and the restrictions that we have I'll get back to later, but It's the same as always, right? We can't always release something in c because of technical uh in in e because of technical requirements Um, and if there's an existing feature in another tier, we have to always bring it to that but We do our best and we try to prioritize premium um I already discussed geo and disaster recovery And I think one important thing to mention here is that I think we can do a better job And I think everyone agrees with that in messaging the value of e Right a list of features is not an enticing offering, right? We want to bring you solutions not features And I'm working together with almost everyone I think everyone is very opinionated about this, but in particular William Chia and Joe's team to message the value of e better be better All right, um so far about ultimate and premium and then uh Now a few less left over things and then there will be time for questions So these are the questions I always get and I get them pretty much every week. So um I put links here for you. So how do we prioritize I answer this and every time I answer that I give a very nice answer But there's an even better answer. It's in the handbook product handbook and it's under prioritization where you would expect it to be This is one that came up a number of times over the past months and that Sid suggested to write down So I did I wrote down from the top of my head how I think we're going to use machine learning and things like ai in the future Of git lab and something my engineering heart is is teaching to get On it is working on but we have to be smart about this. Uh, so I wrote How can we use machine learning at git lab and how can we, you know, write away from this of this cool meal tool? Um What are the Just that have right now at product. Uh, I think it's what I mentioned today What I spoke about which is making enterprise decision premium valuable and also introducing e b and of course git lab is a big challenge for us We I believe that the future is sass. Uh, I just don't know how soon its future will come and we have to be ready for that so Making sure that git lab will come runs well But it's also pleasurable to use as a as a user, right that it's easy to sign up It's easy to scale up and down your organization. It's easy to move between tiers That should all be very good and doing all of that is an art in itself and and One that we are over the past months and over the many coming years will continue to have to study and hope the master and then Before I let you ask the question, uh, Jacob usually asks me what I'm the most excited about I put it in here for myself and and Right now I am most excited about Expanding the breadth of the product. I think that The idea that we have for complete deaf folks Um Is very powerful. I think I think the idea of a single tool has always been very Enticing and I think we were always convinced about the idea that a single tool Makes your the whole experience of developing much better. And I think if we can Bring that same kind of you know quality that say that that same experience to the upside of things and basically make that whole thing That those disjointed steps, you know going from idea to then especially the part where you have it in production And you have to manage your service if we can all bring that into git lab and make that Like a holistic experience. I think it's very powerful. That's what I'm most excited about So I took away that question, um, but there's plenty of time Let me know if you have any you can drop them a chat or you can just speak up Hey, yeah, this is phil here. Um wanted to chat about The migration tools so we're we're building the all-in-one platform to replace a lot of the tools From a sales perspective, it can be a very cumbersome conversation to have with with a prospect But where is and we've probably already gone over this but as far as the migration paths You know, how are we making it easier? What's the roadmap look like for there for for example if I want to migrate off of jinkins You're having a very easy streamlined migration path almost like an importer tool I know we're not there yet, but what's the roadmap for getting a solid migration path off of all of these different tools Since we're asking to replace all of them for the for the client I will give you the most honest answer Migrating from one tool to another is always going to be hard Because not because necessarily we can't build an integration or importer But because every customer is using these kind of things differently So there's always going to be some struggle there Even the customer side on our side now There's a lot we can do and I think what we should do here is prioritize What what gives us the biggest bang for a buck for instance We know that as we are expanding into portfolio management people want to migrate away from jira for instance So we're going to build a jira importer. That's on our roadmap. We're planning that and I hope to do that somewhere to be in up next year And that those kind of things are very doable Jenkins in particular is a very tricky one. Um, we are looking about Like we're looking into how we could possibly do something like that, but it's not arbitrary Especially considering the way the Jenkins users typically use many plugins and you know, there's just not a single translation It's not like you can directly translate one to the other So that path is always going to be tricky and the start really is like education So maybe the answer is not You know, I tend to think about from a product perspective Like what kind of technology can we build to solve this problem? But maybe the solution here is education training and services rather than Okay, here's the one click button solution Even though I wish to want to build that I think that's not always as effective as we can dream it to be And we also don't want to build a business. That's just us integrations, right? That this not our business goals. We want to build better tools So I hope to focus our engineering time as much as we can on that and do You know things that have a big impact as much as we can Thank you Any other okay. I see a bunch in the chat. So Joel says whoo-hoo geo and ha without running labels. It's huge for a customer Yes, that is huge And I'm very happy. We have a lot of extra people on geo James Ramsey is working on a longer term roadmap for geo. So we continue to adding value even on top of that So it won't be it won't be that we deliver jira geo jira Geo and then we're done. No, we're gonna do geo We're gonna do disaster recovery. We're gonna set up an active proxy so that you can push directly to the to the geo instance rather than to the main one And we're gonna continue iterating on this Okay, have we calculated cost of tools we replaced to show an ROI john may asks and yes, we have mark Edit the link there on the website that you can use To check the ROI, which is really really good Brandon says part of what made Jenkins horrible also makes it horrible to try and convert with the technology solution Yeah, I think so Kim says trying to create an import of a Jenkins would be moot since they have way too many plugins that need to be accounted for yeah Yeah, and and tone clarifies and I think I did but By the end of this year disaster recovery will not be ga. We're only expecting to deliver that next year Pedro, what are we not going to have an eu that customers would like to have? uh Lots of things like basically everything we ship in enterprise edition premium and Or do you mean Pedro? Things that we're just not going to do in general Maybe yeah, I think it's that just Are we thinking of eu? as the place where we put The features that we are not very fond of but that customers Pay a lot to do them No, we're never going to ship things that we're not very fond of I think that we should focus on building the tools that our customers need and the tools that we think are the future of software development and Collaboration and digital collaboration. I think that is the direction we should be going If the moment we start introducing things we don't like That means that we're taking on like product debt and and like we're making our product actually bloated Like one of the criticisms is of a product like the git lab, but you have a single tool as well You have a lot of glow to your product and that's That's true if we were not opinionated if we were just to add everything Instead of git lab because we take our time to think about like what are the tools that you actually need and what are actually the useful things? We're only building the kind of things that we really really think that should be there Sometimes we're schooled by our customers and they say well, you should build this and we thought we didn't need that But that's a different situation We we are opinionated about the things we built So eu is definitely not that eu is the best experience for git lab and even in eu Will be things that we think are important that we think are critical And we think we'll make the lives of our customers of all the individual engineers and managers and executives of companies that use git lab better Brandon says although interestingly enough people worry about plugins when converting I did an analysis that shows the most popular Jenkins plugins are actually built into git lab. That's very very great. That should be on our website I haven't checked that issue, but it should totally be on our website. Um, and also not surprising to be honest John may getting away from long-term complexity will make customers go through the process of converting um Yeah, we we don't we don't want to add any complexity. That's that's the thing All right, three more crickets to ask any questions. Can I also speak up? three No, no, you can literally ask me anything and I know questions Hey, york, um I've got a question here. Sorry Phil. Uh, just to the back git lab.com. Do we have an update on when, um Uh, authentication into git lab.com and an sla will be forthcoming Uh, no, I have no eta for you We're working on it and I believe mike is working on the exact timeline But I I don't know my heart. I didn't but I I can give you that in the short term. I just don't know it by heart Okay, no worries. And the other one was just about LFS I feel like there's a groundswell of interest in using You know basically get management platforms to manage binaries But there seems to be some shortcomings such as purging all files from the system things of that nature. Do we have any You know a bit of focus on enhancing LFS Yeah, if you check the last few releases, we actually Delivered a bunch of improvement related to LFS one of them being the ability to put it in object storage I am a personal believer that there is a big future for LFS in particular when Going to the market that per force is now leading in like such as the gaming market like big media market And so we have somewhat of a vision there. I think I need to spend some time to articulate it and your comments and your question Uh, did prompt me to do that. So I'm taking a note now and I will uh, I'll articulate a little bit more how I think we should be moving but I I I see the same issue Great. Yeah, great. Thanks Brandon says we'll are moving to security marketing for the dedicated team. Yes, probably So, yeah, there's a question above. I you might have answered but I missed it But it was about how long do we lock the price at 199 for eu And in case that was an obvious like there's a huge sales incentive right now If you're closing any eup deals basically just close them in this eu because it's free And then that not only helps them because they get these awesome features But it helps us get testers of these features, which is what one of the reasons we want to keep the price down But how long would that last for and should we be doing sales promotion around that? Yeah, I want to chime in here. I just uh, select job. Um, that hasn't been decided yet to do it for 200 dollars It's chat's call. I think what we'll do is we uh, we're going to stay on our website chat said call us for pricing But we might introduce it at 400 dollars. Um, so Still being decided. So, um, I I don't want people watching the recording of this to get the impression they're That 200 dollars is a is a thing. We'll decide before the 22nd. What exactly we'll do Thanks, it I wasn't I wasn't aware of that the last thing I saw was a document by william Which I think listed 200 dollars. I just created the pricing channel so we can Better stay abreast of this All right, cool Any other questions before we move on to the team call? three two One, all right. Thanks everybody Have a great day. See you team call