Self-host GitLab on-premises or in your private cloud

Hosted SaaS options are available using GitLab.com

Community Edition (CE)
For small teams, personal projects, or GitLab trials with unlimited time.
$0
per user
per year
Enterprise
Edition
Starter
For co-located teams with a single project who need professional support.
$39
per user
per year
Enterprise
Edition
Premium
Enterprise
Edition
Ultimate
Early adopter
For enterprises that want to align strategy and execution with enhanced security and compliance.
$999
per user
per year
Contact Sales

Still have questions? Get in touch.

Contact Us

Subscription & Licensing FAQ

  1. What is GitLab High Availability?

    High availability is a system design that ensures a prearranged level of operational performance throughout a specific time-period. The most common way to measure HA is through the notion of uptime, which measures how long a service is up and running. Learn more…

  2. Is there educational pricing?

    GitLab’s Educational pricing is that for educational institutions, students do not count towards the user count. The purchase of at least one subscription is required.

  3. How is GitLab EE licensed?

    Every person with a GitLab account that is not blocked by the administrator should be counted in the subscription.

  4. What is a user?

    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.

  5. Can I get an evaluation license of EE?

    It is possible to obtain a free evaluation license of our enterprise edition for a 30 day period for up to 100 users.

  6. What will happen to my evaluation license key at the end of the trial period?

    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.

  7. Can I add more users to my subscription?

    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 renewals@gitlab.com for a quote. In either case, the cost will be prorated from the date of quote/purchase through the end end of the subscription period. You may also pay for the additional licences per our true-up model.

  8. The True-Up model seems complicated, can you illustrate?

    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.

  9. Do students have to pay or do they receive a discount?

    GitLab’s Educational pricing is that for educational institutions, students do not count towards the user count. The purchase of at least one subscription is required.

  10. Do non-profits have to pay for the Enterprise Edition?

    Non-profits can use GitLab Community edition for free but need to purchase a subscription to the Enterprise Edition at our published rates.

  11. Why does GitLab use licenses?

    The code for Enterprise Edition is open and can be inspected by anyone. This makes it easier to offer a trial of Enterprise Edition.

  1. Can anyone download GitLab EE?

    Yes, but it will not be functional without a license key.

  2. How does the license key affect customers?

    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.

  3. Do blocked users count towards total user count?

    No, only active users count towards total user count.

  4. How does the license key work?

    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.

  5. How do I upgrade GitLab EE to 7.11 or above?

    After you upgrade GitLab to EE version 7.11 and higher, GitLab EE will stop working without a license key. If you don’t have a license key, please contact sales@gitlab.com and request a key. Once you deploy the key, GitLab EE will start functioning again.

  6. What happens when my subscription is about to expire or has expired?
    • Starting 30 days before the subscription end date, GitLab will display a notice to all administrators informing them of the impending expiration.
    • On the day the subscription expires, nothing changes.
    • 14 days after the subscription has ended, GitLab will display a notice to all users informing them of the expiration, and pushing code and creation of issues and merge requests will be disabled.
  7. What happens when I renew my license after it expires?

    You will receive a new license that you will need to upload to your GitLab instance. This can be done by following these instructions.

  8. Do I need an additional license if I run more than one server (e.g., for backup, high availability, failover, testing, and staging)?

    No, if your GitLab Enterprise Edition servers cover the same users, you can use the same license file for all of them.

  9. What happens if I decide to not renew my subscription?

    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.

  10. How does GitLab deal with bug fixes?

    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.

  11. How does GitLab help companies ensure HIPAA compliance?

    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.