Accelerate GitLab’s trajectory by connecting the great work every team is doing with the outside world
GitLab Team: Please visit the Private Alliance Handbook Page for additional information about Alliance Partners.
GitLab is an open product with a Core, open-source edition and an enterprise, open-core edition, with additional features that are closed-source.
We're open to integrations with companies and tools that are interested in harnessing GitLab's platform capabilities, user flows and data with their products.
Traditionally GitLab had defaulted to a competitive voice when talking about other companies. This is counterproductive for the following reasons:
Messaging going forward (Oct 2019):
For all areas where we are not yet lovable:
GitLab is open to collaboration and committed to building technology partnerships in the DevOps ecosystem. If you are interested in becoming a GitLab Technology Partner, learn more on our Integrate with us page.
If you want to talk to us about a partnership please create a New Partner Issue and share details about the technical integration, end user benefits and business relationship that you would ideally want. When creating an issue, please select new_partner issue template in the drop down.
Primary monetization is through the sales of software licensing/support that integrates with GitLab
For details on how to we work with Channel partners please go to the Channel Handbook page: Channel Partner Types
We are able to connect with sales and technical teams at platform partners to accelerate deals and add value for customers.The best way to engage with platform partners is with active opportunities that include expansion for an existing customer and POV or technical evaluation for a prospect.
There are many ways that GitLab can be both installed (/install/) and once installed many deployment environments that GitLab can target. Below is a structure to think about those options and some of the trade-offs that are made depending on the model.
|Installation Package||Omnibus/Helm||Omnibus/Helm||Helm||Moving to Helm|
|Billing Ownership||GitLab/Partner||GCP, AWS, DO, etc||Cloud||GitLab|
|Pricing||user/yr||user/month or hour||user/yr||user/yr|
If you are interested to inquire about a potential acquisition of your company please visit our acquisition handbook.
If you've received an inbound alliance request please post a new message to the #alliances Slack channel with the brief description of the request. Once posted, the alliances team will declare who will take lead on that request and the necessary next steps to take.
For Context of the Partnerships we are working on please reference : GitLab Partner Dashboard
When applying for MDF funds which are reimbursed in the form of cloud credits to a GitLab account follow the following process to make sure all relevant parties are informed:
When partners and potential partners request free licenses to develop integrations with GitLab most need a self-managed license key. To generate a license follow the steps below according to the type of license.