GitLab for Open Source

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 OSI-approved open source license.

No. Members of the GitLab for Open Source Program do not receive support as part of their program subscriptions. Read more about seeking support.

Only groups you own with free tier are eligible for the program and are shown in the dropdown. Make sure the group you want to use meets those criteria. Note that personal namespaces are not eligible for licensing. If your project is located in your personal namespace you need to convert your personal namespace into a group.

No. You may use the GitLab subscription 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.

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 and join an open source project. As a result, we ask that all qualifying projects are publicly visible and allow users to request access to them.

When you activate the subscription you receive as a member 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 any additional seats you feel your project will need as its community grows. You’ll have the opportunity to request additional seats at time of renewal.

Yes. You’ll need to renew your membership in the GitLab for Open Source Program by completing the application form 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 subscription 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.