The following page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features or functionality remain at the sole discretion of GitLab Inc.
Today GitLab lacks visibility into who our free self-managed users are. Users can simply follow the self managed install steps and be up and running with GitLab in minutes. This open-core model is a huge strategic advantage as it lowers the barrier to entry for our product. The downside is that users are not required to register or "sync" their instance with GitLab preventing us from knowing who they are, providing better support and GTM motions, and offering services that may enable them to get even more value out of GitLab.
This problem has compounding effects as you think through the implications:
GitLab:
End Users & Customers:
We aim to solve this problem by focusing on a couple of key areas. Cloud Licensing will provide a modernized approach to license management for our customers. While only avaliable for instances on a paid tier today, in the future it will address visibility and provide a conduit for GitLab inc to support users who sync their instacnes with GitLab. Registration Features (internal handbook) will provide an incentive for instances to opt-in to syncing their instances with GitLab and deliver additional value to users who may not be ready to upgrade to a paid tier.
As a piece of underlying infrastructure, we need to enable a way for a customer to "sync" a self managed instance with us. This new system's primary purpose will be to activate and sync paid self-managed licenses for new customers, but can be used to sync unpaid licenses. We launched the first iteration of Cloud License in 14.1 and in 15.1 we've begun to onboard all customers to the new licensing system by default.
The value to GitLab includes increased visibility into seat utilization along with improved efficiency for sales and support. To the customer, we can provide real-time visibility into an account's utilization and improved tools for user management.
Allow free self-managed EE instances that register with GitLab and activate Service Ping to access otherwise paid features. These features would add value to the customer's installation and give them a "preview" of what features they could access at a paid tier. Our initial user target for registration features was GitLab Administrators, as they are the users most likely making the decision to activate registration features. We will initially looked at paid features that are unrelated to a pricing theme for registration features candidates. As we progress beyond our initial phase, we will look to expand our scope and add features that could also be beneficial to users as well as those with pricing themes. In FY23 we've completed some research which will provide a framework and guidance to make rapid decisions on which features may be a good fit for Registration Features, and intend to release additional registration features on a regular basis going forward.