Get started with GitLab

Head over to the GitLab Customers Portal, choose the plan that is right for you.

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 Customers Portal and add more seats or contact sales 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 licenses per our true-up model.

If you have quarterly subscription reconciliation enabled (default option for new and renewing subscriptions after Aug 1, 2021), users added during a quarter will only be charged for the remaining quarters of their subscription term as opposed to the full annual subscription fee(s) with annual true-ups. For example, if you add 50 users to your subscription during the third quarter of your subscription term, the 50 users will only be charged for the fourth quarter of your subscription term as opposed to all four quarters as per annual true-ups.

If you do not have quarterly subscription reconciliation enabled, add-on users will be charged annual true-ups for the full term during which they were added. For example, 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.

If you most recently used an Activation Code to activate your GitLab Paid Plan, once you renew your subscription the new subscription terms will synchronize to your GitLab self-managed instance during the next subscription data synchronization. If you most recently used a license key, you will receive a new license that you will need to upload to your GitLab instance. This can be done by following these instructions.

If you choose not to renew your GitLab 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.

No, all users in the GitLab.com group or on the self-managed instance need to be on the same plan.

The license key is a static file which, upon uploading, allows GitLab Enterprise Edition to utilize paid features. 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. As of 2022, license keys are a legacy method to activate GitLab paid plans and have been substituted by an Activation Code for most paid subscriptions.

An Activation Code refers to GitLab's method for activating your self-managed subscription with Cloud Licensing, which provides a more seamless subscription experience. This is required for all customers on version 14.1 or higher. For more information on Cloud Licensing, please see What is Cloud Licensing? as well as How do I activate with an Activation Code?.

Enterprise Agile Planning add-on is available to GitLab Ultimate subscriptions and seamlessly integrates into the GitLab DevSecOps platform, enabling non-technical users to collaborate with engineers throughout the software development lifecycle. Enterprise Agile Planning add-on users should be invited with Reporter access, providing them the ability to view and interact with project information, including issues, milestones, and boards. This level of access ensures that non-technical stakeholders can stay informed about project progress and provide valuable input. View permissions for Reporter users here.

GitLab partners with license resellers around the globe, where many are solution providers and professional service experts. For a complete list of resell partners, please check out the GitLab Partner Locator.

See Acceptable Use of User Licenses for user licensing documentation.

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 Software hereunder. Every user (with the following exceptions) within a namespace (top level group) is counted in a subscription.

The listed prices may be subject to applicable local and withholding taxes. Pricing may vary when purchased through a partner or reseller.

Yes. You can import your projects from most of the existing providers, including GitHub and Bitbucket. See our documentation for all your import options.

Yes! We provide free Ultimate licenses, along with 50K compute minutes/month, to qualifying open source projects, educational institutions, and startups. Find out more by visiting our GitLab for Open Source, GitLab for Education, and GitLab for Startups program pages.

You can learn more about how we make tiering decisions by reviewing our pricing handbook page. On this page we represent our pricing strategy which can be further filtered based on our buyer-based open core pricing model.

All of the features and benefits of the different GitLab offerings can be found on the feature comparison pages. Read more about Premium and Ultimate to learn whether these are the right tiers for you.

You can run basic scans for SAST, Secret Detection, and Container Scanning in all tiers, but enterprise-grade scanning and management features are only available in Ultimate.

Ultimate adds proprietary technology and more ways to customize scans to fit your organization's needs. Ultimate-tier SAST includes proprietary technology to suppress false positive results and track vulnerabilities as they move. Ultimate-tier Container Scanning uses GitLab's proprietary advisory database and offers auto-generated solutions for vulnerabilities. With Ultimate, you can also customize the rulesets used for SAST and Secret Detection, and manage CVE allowlists for Container Scanning.

Additionally, the Ultimate tier adds key usability, workflow, and governance improvements. The basic scans in Free and Premium only output results as JSON-formatted artifact files, but Ultimate shows new findings in merge requests and pipelines, and tracks vulnerabilities and dependencies over time. The Ultimate tier allows users to view the results in the GitLab UI on the vulnerability report, dependency list, and inline in their merge requests. With Ultimate, you can also require security approvals for merge requests that affect your security posture.

You can see all the differences between GitLab and other popular DevSecOps solutions on our competitive comparison pages.

For paid plans, the hours in which your support request has SLA is dependent upon the Support Impact of the request itself. Something at Emergency (Severity 1) level would receive support 24/7, whereas other Support Impact levels would receive 24/5. For more information on the hours of support, please see Definitions of GitLab Global Support Hours and Effect on Support Hours if a preferred region for support is chosen.

You can learn more about GitLab's success offerings on the services page.

Currently GitLab.com is hosted on the Google Cloud Platform in the USA.

GitLab Self-Managed is a version of GitLab that allows you to install, configure, and maintain on your own infrastructure (both on-prem and in the cloud), making it ideal for customers who need complete control over their environment, data, and security.

To see all installation methods of GitLab Self-Managed, visit our documentation.

For Self-Managed customers to use GitLab Duo Agent Platform, the minimum supported version is 18.8. For Self-Managed users to trial GitLab Ultimate and Duo Agent Platform with GitLab Credits, the minimum supported version is 18.9.

GitLab Dedicated is a fully isolated, single-tenant SaaS service that is:

• Hosted and managed by GitLab, Inc.
• Deployed on AWS in a cloud region of your choice (see the regions that are not supported)

The 5-user limit is applicable only to users of the Free tier of the GitLab.com offering in a top-level group with private visibility. These changes do not apply to users of the Free tier of the GitLab.com offering in a public top-level group, paid tiers, the Free tier of the self-managed offering and community programs, including GitLab for Open Source, GitLab for Education, and GitLab for Startups users. Learn more here.

Compute minutes are the units used during the execution time for your pipelines on our shared runners. Execution on your own runners will not use your compute minutes and is unlimited.

If you use all of your compute minutes, you can manage your compute minutes usage, purchase additional compute minutes, or upgrade your account to Premium or Ultimate. Your own runners can still be used even if you reach your limits.

No. We will only restrict for GitLab.com only. If you have a specific runner setup for your projects, there is no limit to your build time on GitLab.com.

No. The quota will be applied to a group, no matter the number of users in the group or the number of users in the subscription.

There has been a massive uptick in abuse of free compute minutes available on GitLab.com to mine cryptocurrencies, which creates intermittent performance issues for GitLab.com users. To discourage such abuse, credit/debit card details are required if you choose to use GitLab.com shared runners. Credit/debit card details are not required if you bring your own runner or disable shared runners. When you provide the card, it will be verified with a one-dollar authorization transaction. No charge will be made and no money will transfer. Learn more here.

Yes, you can bring your own GitLab CI/CD runner with all plans.

Projects on GitLab.com Free have an initial 10 GiB limit on Git repository and LFS storage. Users can purchase additional storage to increase the set project limit. Projects on Premium and Ultimate have a fixed limit of 500GiB per project. For more information, see fixed project limit.

Purchased storage applies to Git repository size and LFS usage. It does not apply to other storage types, such as the container registry.

For Free users, 10 GiB total of combined Git repository and LFS usage per project. For Premium and Ultimate users, 500 GiB total of combined Git repository and LFS usage per project. Storage limits for Premium and Ultimate customers are fixed per project. Buying additional storage does not increase the maximum limit for a single project. It only expands your overall available storage. For example, purchasing 1 TB of storage will not cause one project to exceed its 500 GiB ceiling. For more information, see fixed project limit.

Advanced Capacity is coming soon and is not yet available to buy. Advanced Capacity raises the GitLab.com rate limits for a top-level group on a Premium or Ultimate plan. It comes in three forms:

• The Advanced Capacity Pack, a flat annual add-on for sustained need.
• Overage, which covers occasional spikes for a fixed daily price.
• The Enterprise Capacity Pack, for sustained need above the Advanced Capacity Pack. Our sales team works out its limits and price with you.

Advanced Capacity is available for GitLab.com only.

API requests, web requests, and authenticated Git over HTTPS requests all count. Each Git clone, fetch, or push counts as one request, and so does each Git LFS transfer. Advanced Capacity raises the limits for your top-level group. For the full list of what counts and what doesn't, see GitLab.com rate limits.

With overage off, requests above the limit receive an HTTP 429 Too Many Requests response. The Retry-After header tells you how long to wait before you try again. Nothing is queued, and you aren't charged.

With overage on, your group can keep going above its limit, up to the band you authorize. You pay that day's overage price.

Overage has three bands, priced at $100, $500, and $1,500 a day. You authorize one band, and your group can't go past it. New and renewing subscriptions start on the $100 band.

On each day your top-level group goes above the standard GitLab rate limit, you pay the daily price of the highest overage band it reached that day. You never pay for a band above the one you authorized, and days when your group stays within the standard GitLab rate limit it costs nothing. The most you can be billed is the daily price of your authorized band multiplied by the number of days you go over. For example, a full 31-day month on the $100 band costs at most $3,100.

The $100 band gives the same capacity as the Advanced Capacity Pack. If your group uses it on more than 120 days a year, the Pack costs less.

Overage will be on by default when you buy or renew a Premium or Ultimate subscription. An Owner of the top-level group can turn it off at any time. With overage off, your group stays at its plan limit, or at its Advanced Capacity Pack limit if you have one, and no overage is charged.

Advanced Capacity is sold through our sales team. Premium and Ultimate rate limits are planned to take effect in January 2027 and won't be enforced until Advanced Capacity is available to buy. To discuss it now, contact sales.

GitLab Credits can be acquired in three ways:

Included credits: For a limited time, Premium customers receive 12 credits/user/month, and Ultimate customers receive 24 credits/user/month at no additional cost. These included promotional credits are available for a limited time after GA, and subject to change at GitLab’s discretion. See Promo Terms.

Monthly commitment pool: Purchase a shared pool of credits for your organization to draw from. The more credits you commit to, the better pricing you receive. These credits refresh monthly.

On-demand credits: If you’ve used all your included and committed credits, you can continue using GitLab Duo Agent Platform on a pay-as-you-go basis at the standard rate of $1/credit. Once you’ve enabled on-demand billing for your account, it will remain enabled for the remainder of your subscription term. You will be billed at the end of each month for any on-demand credits consumed.

For Self-Managed customers, to ensure access to the latest GitLab Duo Agent Platform capabilities, please upgrade to version 18.7. If you accept on-demand billing, you will be charged for use of GitLab Duo Agent Platform regardless of your GitLab version.

For more information, please visit our usage billing documentation.

GitLab.com Free top-level group namespaces and Self-Managed Free EE instances can purchase and share a pool of credits. Personal namespaces cannot purchase monthly commitments.

Credit sharing depends on how the credits were acquired:

Included credits are allocated on a per-user basis and cannot be shared between users.

Monthly commitment pool credits are shared across your entire organization. This pool creates an efficient way for teams to access GitLab Duo Agent Platform capabilities based on actual usage rather than seat assignments.

Yes, different AI models draw down credits at different rates based on their capabilities and underlying costs. We will continue to update these draw down rates when new models are made available and new features are introduced. For the most up to date information, please visit our documentation page.

No. GitLab Flex is available only through sales-assisted channels.

Contact your GitLab account team to discuss conversion options. In most cases, you can convert at your next renewal date.

Deployment model (GitLab.com, Self-Managed, GitLab Dedicated) is set at contract signing and cannot be changed mid-term. Contact your account team to discuss options at renewal.

Reserved: seats and GitLab Credits you commit to in advance for a given month. The full reserved amount is locked at the start of each month and is use-it-or-lose-it. Your Flex discount applies.

On-demand: any usage above your reserved amounts. GitLab Credits are billed at list rate ($1/credit); seats are billed at the same discounted rate as your reserved seats.

When your GitLab Flex commitment balance hits zero, further usage is invoiced directly.

Your GitLab Flex balance, current reservations, and usage to date are available in the Customers Portal.

Yes. You can set usage caps that limit on-demand usage for each capability, and adjust them month to month alongside your reservation. Usage notifications alert you as you approach your limits.

New capabilities that are generally available can be enabled within GitLab by your group Owner or instance administrator. No contract change or amendment is required.

If you enable a capability without reserving credits for it, its consumption draws from your GitLab Flex commitment as on-demand usage at list rate ($1/credit). GitLab Orbit is the exception: Orbit query packs are paid in GitLab Credits reserved for Orbit and purchased separately, so Orbit usage does not draw from your GitLab Flex commitment.

To get the discounted reserved rate, add a reservation for that capability in the Customers Portal.

Yes. GitLab Flex supports multi-instance allocation and aggregated billing against your GitLab Flex commitment. Contact your GitLab account team for more details.

If your commitment is exhausted before the end of your term, GitLab invoices you directly each remaining month for both your contracted minimum monthly reservation and any on-demand on top of it. You can use spend caps and usage notifications to control consumption, or contact your GitLab account team to increase your commitment mid-term.

No. Reserved GitLab Credits and seats are use-it-or-lose-it and expire at the end of each month.

No. Your GitLab Flex commitment is a use-it-or-lose-it annual spend agreement. Unused balance at the end of the term is forfeited.

Orbit is priced around a shared pool of queries that can be consumed across your organization, rather than individual query allowances or seats for each user. That pool is sold as query packs, and the number of paid GitLab users in your organization determines how many packs you need. That way, everyone has access to Orbit, and usage can flow naturally between occasional users, power users, and AI agents.

Queries are sold in query packs, which form one shared pool for your organization. Query packs are paid in GitLab Credits reserved for Orbit. Each subscription also includes graph capacity, the storage for your organization's Orbit graph.

People and agents draw from the same shared pool, and there is no separate agent charge.

Orbit is available to Premium and Ultimate customers through your GitLab account team, who can size the query packs for your organization.

No. Orbit query packs are paid in GitLab Credits reserved for Orbit, purchased separately, and can sit alongside your GitLab Flex agreement.

Usage above the included query allotment is metered so you can see it, but it isn't billed during your first year.