Join the GitLab for Open Source Program
GitLab Ultimate and 50,000 CI/CD minutes are free for qualifying open source projects
About
Hundreds of thousands of open source contributors around the world have helped make GitLab what it is today. We’ve created the GitLab for Open Source Program to give back to this community, helping open source teams be more efficient, secure, and productive through access to GitLab’s top-tier capabilities.
Public projects on GitLab.com do not automatically receive top-tier functionality at the project level. Apply to this program if your project needs top-tier functionality at the project/group level or the additional CI minutes this program provides.
Program benefits
Enroll in the GitLab for Open Source Program and receive:
-
GitLab Ultimate (self-managed or SaaS) with unlimited seats per license
-
50,000 CI/CD minutes (users can purchase 1,000 additional minutes for a one-time, $8 fee)
Requirements
In order to be accepted into the GitLab for Open Source Program, applicants must:
-
Use OSI-approved licenses for their projects: Every project in your namespace must be published under an OSI-approved open source license
-
Not seek profit: Your organization can accept donations to sustain its work, but it can’t seek to make a profit by selling services, by charging for enhancements or add-ons, or by other means. Read more about this requirement.
-
Be publicly visible: Both your GitLab.com group or self-managed instance and your source code must be publicly visible and publicly available.
Read our full list of program exceptions to determine whether your project qualifies. If you believe your project meets all program requirements, we welcome your application!
As you apply, keep in mind
- Benefits of the GitLab for Open Source Program apply to a namespace. To qualify, every project in an applicant’s namespace must carry an OSI-approved open source license.
- Free top-tier accounts do not include support.
- You’ll need to renew your program membership annually. If you don’t renew, your account will be downgraded.
- Acceptance into the GitLab for Open Source Program is at GitLab’s sole discretion, and we reserve the right to terminate the Program (or change the program requirements) at any time.
GitLab for Open Source Agreement
Upon acceptance, all program members are subject to the GitLab for Open Source Program Agreement.
Applications will not be processed during U.S. holidays and responses may be delayed during those periods. Furthermore, a few extra steps are required before we transition to a more automated application process. We appreciate your patience during this transition. To help us prioritize, please let us know if your request is urgent by including “Urgent: [your request]” in the subject line of any email to opensource@gitlab.com.
Before you begin
-
Set up a GitLab account. You’ll need to have a GitLab group already configured for your open source project or organization, via either a Free account or Free Trial. For help setting up a GitLab group, please see the relevant FAQ below. If you are considering a migration, you do not need to have finished the migration before applying to the GitLab for Open Source Program. You will need at least one project (repository) set up under your GitLab group to comply with our requirements.
-
Take screenshots. During the application process, you’ll need to provide 3 screenshots of your project. We suggest taking them in advance, since you’ll need to submit them on page two of the application form.
-
Complete the form. Submit the application form on this page to help us verify that you meet all program requirements.
What to expect
-
Wait time. Gitlab uses SheerID, a trusted partner, to verify that you meet the GitLab for Open Source requirements. In most cases, you can expect a decision about your application within 15 business days. You may be asked to provide additional information.
-
After you’re verified. If you qualify for the GitLab for Open Source Program, you’ll receive a verification email with specific instructions for obtaining your license. Please follow the instructions carefully.
Help and support
If you experience any issues obtaining your license in the Customer Portal please open a support ticket on the GitLab Support Portal and Select “Licensing and Renewal Problems.”
Thanks for subscribing! Follow us on twitter for even more updates!
Frequently Asked Questions
GitLab for Open Source Program benefits apply to an entire namespace. To qualify for the program, every project in the applicant’s namespace must carry an open source license. When you apply, submit materials for the single project you believe represents all the projects in your namespace.
No. While members of the GitLab for Open Source Program receive GitLab Ultimate at no cost, they do not receive support as part of their license. Read more about seeking support.
The goal of the GitLab for Open Source Program is to enable collaboration on open source projects. As a pre-condition to collaboration, people must be able to view an open source project. As a result, we ask that all qualifying projects are publicly visible.
When you activate the license you receive as part of the GitLab for Open Source Program, you’ll specify the number of seats your account will require.
GitLab uses a concurrent (seat) model, which refers to the maximum number of users enabled at once. Every occupied seat is counted, including the owner’s, with the exception of members with Guest permissions. We are happy to grant you the number of seats you think you’ll need for current project members as well as additional ones to plan for growth during the year. You’ll have the opportunity to request additional seats at time of renewal, or you can email us at opensource@gitlab.com to request more while you’re a program member.
No. You may use the GitLab license you receive from the GitLab for Open Source Program only for the publicly visible open source projects for which it was approved. In some cases, we allow program members to host a small number of private projects if those projects contain sensitive data. Please email us at opensource@gitlab.com to ask about your case. You must obtain written permission from us in order to use the license outside of program requirements. Note that any user capable of creating new projects in a namespace is responsible for ensuring that project complies with the GitLab for Open Source Program eligibility requirements. If you’re concerned about users creating projects that violate the program’s eligibility requirements, we recommend restricting the number of users capable of creating new projects in your namespace.
Yes. You’ll need to renew your membership in the GitLab for Open Source Program annually. Our program requirements may change periodically, and we’ll need to make sure that you continue to meet them. Read and follow the renewal procedure to maintain your membership. Please begin the renewal process at least one month in advance to ensure sufficient processing time. You will receive email reminders to do so and can renew as early as three months in advance of your membership’s expiration.
To avoid delays, we recommend that you renew your license at least one month in advance of the deadline. If your license is about to expire, here’s what to expect.
GitLab is available to people all over the world in many languages. However, since we are a U.S.-based company, we do not offer our services in U.S. embargoed countries.
Some web browsers and privacy extensions block the application form because they identify it as a pop-up. Please disable the pop-up blocker on this page, refresh the page, and check again.