Every person with a GitLab account that is not blocked by the administrator should be counted in the subscription.
User means each individual end-user (person or machine) of Customer and/or its Affiliates (including, without limitation, employees, agents, and consultants thereof) with access to the Licensed Materials hereunder.
It is possible to obtain a free evaluation license of our enterprise edition for a 30 day period for up to 100 users.
When you decide to purchase a subscription, you will be issued a new license key dependent on the type of subscription you sign up for. Should you not take out a subscription, your license key will expire at the end of your evaluation period.
Yes. You have a few options. You can add users to your subscription any time during the subscription period. You can log in to your account via the GitLab Customer Portal and add more seats or by either contacting email@example.com for a quote. In either case, the cost will be prorated from the date of quote/purchase through the end of the subscription period. You may also pay for the additional licences per our true-up model.
If you have 100 active users today, you should purchase a 100 user subscription. Suppose that when you renew next year you have 300 active users (200 extra users). When you renew you pay for a 300 user subscription and you also pay the full annual fee for the 200 users that you added during the year.
Non-profits can use GitLab Community edition for free but need to purchase a subscription to the Enterprise Edition at our published rates.
The code for Enterprise Edition is open and can be inspected by anyone. This makes it easier to offer a trial of Enterprise Edition.
Sure thing. It’s publicly available at https://gitlab.com/gitlab-org/gitlab-ee/blob/master/LICENSE.
Yes, without a license key it will function like CE.
Customers can now download and inspect the code for the latest GitLab EE version for free. However, they cannot use it without a valid subscription. They’re also free to make modification to the GitLab EE code as long as they have a license.
No, only active users count towards total user count.
The license key is a static file which, upon uploading, allows GitLab Enterprise Edition to run. During license upload we check that the active users on your GitLab Enterprise Edition instance doesn’t exceed the new number of users. During the licensed period you may add as many users as you want. The license key will expire after one year for GitLab subscribers.
You will receive a new license that you will need to upload to your GitLab instance. This can be done by following these instructions.
No, if your GitLab Enterprise Edition servers cover the same users, you can use the same license file for all of them.
14 days after the end of your subscription, your key will no longer work and GitLab Enterprise Edition will not be functional anymore. You will be able to downgrade to GitLab Community Edition, which is free to use.
Bugs that are reported to us always have a high priority, no matter which subscription you have. In most instances they will be fixed in the next release or the release after that, which means the turnaround is one month or two. Severe bugs will be fixed earlier in a patch release.
GitLab Enterprise Edition (EE) and GitLab Community Edition (CE) work seamlessly in HIPAA-controlled environments. These products do not store, process or transmit any patient related healthcare information. As a result, GitLab EE and GitLab CE have been implemented by hundreds of healthcare-related companies. If your company needs to ensure HIPAA compliance, GitLab will work with your security team to ensure that basic compliance criteria are met. If more extensive security procedures are required, GitLab has a number of partners that specialize in helping companies comply with industry accepted data security standards.
Normal business hours are from Sunday at 8:00pm PST (UTC-5) to Friday at 4:00pm PST (UTC-5). Christmas Day and New Year’s Day are holidays and not considered to be business days.
Pipeline minutes are the execution time for your pipelines on our shared runners. Execution on your own runners will not increase your pipeline minutes count and is unlimited.
The minutes limit only applies to private projects. Public projects include projects set to “Internal” as they are visible to everyone on GitLab.com.
There is no catch. Part of our strategy sequence is to make GitLab.com the most popular SaaS solution for private and public repositories. To achieve this goal you get unlimited public and private projects, and there is no limit to the number of collaborators on a project.
No, all users in the group need to be on the same plan.
Absolutely, GitLab Pages will remain free for everyone.
GitLab.com is monitored 24/7. Our servers are hosted on Google Cloud Platform (GCP), Amazon Web Services (AWS), Digital Ocean, and Azure, we use configuration management, and we patch our servers at least once a week. Our runbooks are public as is our operational issue tracker. GitLab offers Two-Factor Authentication (2FA) via a mobile application or a U2F device, rate limiting, audit logs, and passwords are one-way encrypted. Answers to other common security questions are available on our security page.
No. The limit will be applied to a group, no matter the number of users in that group.
The project and wiki repository, Git LFS files, attachments, build artifacts, and images in the container registry.
Size limitations, as well as more information on how to manage repository size, is available in our documentation
Not yet, but we are working on it, you will soon be able to track your storage usage across all features and buy additional storage space for GitLab.com.
Yes! As part of GitLab’s commitment to open source, Gold project features are available for free to public projects on GitLab.com. For organizations interested in free Gold features for groups, we also offer free Gold and Ultimate to educational institutions and open source projects.
Currently we are hosted on the Google Cloud Platform in the USA