GitLab Free vs Premium vs Ultimate: Licensing and Pricing Compared
This page answers the GitLab licensing questions buyers actually ask — what separates Free, Premium and Ultimate in practice, how seats are counted, and what the 2026 move to consumption-based AI billing does to a GitLab budget. Figures are GitLab list prices in USD.
The short answer: Premium is $29 per user per month on both SaaS and self-managed, billed annually. Ultimate no longer has a public list price — it is sales-quoted, with $99 as the long-standing anchor. The Free-to-Premium decision is about approval rules and governance. The Premium-to-Ultimate decision is about security management, not security scanning, plus the fact that Guest users are free on Ultimate and billable on Premium.
What do GitLab Free, Premium and Ultimate cost?
| Tier | GitLab.com SaaS | Self-Managed |
|---|---|---|
| Free | $0 | $0 |
| Premium | $29/user/month | $29/user/month |
| Ultimate | Custom — contact sales | Custom — contact sales |
Per-seat pricing is identical on SaaS and self-managed. There is no licensing discount for hosting GitLab yourself. What changes is that self-managed has no storage or compute allowances and no overage charges — you carry the infrastructure cost directly instead.
Premium has held at $29 since GitLab raised it from $19 in April 2023. Enterprise Agile Planning is a separate add-on at $15 per user per month.
GitLab is annual-commitment only. GitLab’s own licensing FAQ states that all subscriptions are paid in annual payments and monthly payment is not available. The per-month figures on GitLab’s pricing page are display conventions, not a billing option.
Why can’t I see Ultimate’s price any more?
GitLab removed Ultimate from its public pricing page and replaced it with “contact us for custom pricing” on both SaaS and self-managed. GitLab’s own handbook still documents Ultimate at $99 per user per month, and cloud marketplace listings still carry $1,188 per user per year, so $99 remains the realistic anchor for a negotiation — but it is no longer a published list price, and what you are quoted will depend on volume and term.
What is included in each tier?
| Included per user/month | Free | Premium | Ultimate |
|---|---|---|---|
| Compute minutes | 400 | 10,000 | 50,000 |
| Storage | 10 GiB | 500 GiB | 500 GiB |
| Included AI credits | — | $12 | $24 |
| Users per top-level group (SaaS) | 5 | Unlimited | Unlimited |
Overage runs $10 per 1,000 compute minutes and $5 per month per 10 GiB of storage. Compute minutes are hard-enforced — pipelines stop when you run out. Storage limits on SaaS are currently soft: GitLab contacts you rather than blocking you.
What actually forces the jump from Free to Premium?
Not merge requests or protected branches — the basics of both are on Free. The Premium gates that drive real decisions are the governance layer around them:
- Approval rules. Free gives you merge request approvals. Premium gives you rules — multiple approval rules, and the ability to require Code Owner approval. You can define a CODEOWNERS file on Free; you cannot enforce it.
- Granular protected branches. Free protects branches. Premium lets you specify which users and groups may push or merge, control who can unprotect a branch, and set protection at group level rather than per project.
- Epics and roadmaps for portfolio-level planning. Multi-level child epics are Ultimate.
- Audit events at group and project level, and compliance frameworks.
- Custom value stream stages. Value stream analytics itself is on Free; customising the stages is Premium.
In short, Free is a capable place to write and review code. Premium is where you can prove to an auditor that the review actually happened the way you say it does.
Is Ultimate worth it just for security scanning?
This is the most commonly misread part of GitLab’s packaging. The scanners are not the gate — the results management is. SAST, secret detection and container scanning all run on Free. What Ultimate buys is the ability to do anything useful with the output, plus DAST and dependency scanning outright.
| Security capability | Available from |
|---|---|
| SAST (runs the scan) | Free |
| Secret detection, incl. push protection | Free |
| Container scanning | Free |
| GitLab Advanced SAST | Ultimate |
| Dependency scanning | Ultimate |
| DAST | Ultimate |
| Vulnerability report & triage workflow | Ultimate |
| Security findings shown in the merge request | Ultimate |
| Scanner configuration in the UI, ruleset customisation | Ultimate |
The practical test: on Free and Premium you get JSON artifacts. If your plan is to pipe those into a third-party application security platform you already own, Premium may genuinely be enough. If you want a developer to see a finding in the merge request and triage or dismiss it there, that workflow only exists on Ultimate, and there is no partial version of it.
How are GitLab seats counted?
GitLab bills on billable users — users who occupy a seat.
Billable: direct members, inherited members, invited users holding any role from Guest through Owner, Auditor users, and on self-managed Premium and Ultimate, administrators.
Not billable: users pending approval, deactivated, banned or blocked users, users with only the Minimal Access role, and bot accounts such as the Support Bot and Migration Bot.
Are Guest users free?
On Ultimate, yes. On Premium, no. Ultimate users assigned the Guest role do not consume a seat — but only if Guest is their only role anywhere in the instance. A single Reporter role on one project makes that person billable across the board.
For organisations with a large population of read-only stakeholders — product managers, support staff, compliance, executives who want visibility but never push code — this is frequently the single largest factor in the Ultimate business case, and it is often worth more than the security features people think they are buying. On Ultimate, users with no group or project membership at all are also non-billable.
What happens if we exceed our seat count mid-term?
It depends which reconciliation regime your contract uses, and the difference is expensive.
- Quarterly reconciliation is the default for subscriptions since August 2021. You are billed only for the remaining quarters. Add 50 users in Q3 and you pay for Q4 only.
- Without quarterly reconciliation — typically offline or air-gapped licences — you pay a full-year true-up retroactively for every user added during the term.
Self-managed true-ups are high-water-mark, not point-in-time. GitLab charges on the maximum number of users enabled at any point during the subscription period. Removing a user in month nine does not reduce what you owe for the peak reached in month four. If you run seasonal contractors, block their accounts the day they finish, not at renewal.
Shrinking at renewal has a matching rule: renewal seat counts must meet or exceed your current billable users. You have to actually remove or block people before you renew, not as part of renewing.
What changed with GitLab Duo and AI in 2026?
The AI model changed substantially, and it is the biggest forecasting risk in a current GitLab contract.
Duo Core is included free
Duo Core ships at no additional charge with Premium and Ultimate from GitLab 18.0, providing Code Suggestions and Duo Agentic Chat. So yes — AI is now bundled into the paid tiers rather than being purely an add-on.
Beyond that, AI is consumption-billed
GitLab introduced GitLab Credits in January 2026, generally available with GitLab 18.8. Credits are a usage currency at $1 per credit, consumed by the Duo Agent Platform, Code Suggestions, Code Review Flow, security analysis flows and Agentic Chat, at a rate that varies by which model is selected.
Premium includes $12 per user per month of credits; Ultimate includes $24. Included credits reset monthly and do not roll over.
Treat the included credit allowances as temporary. GitLab explicitly describes them as available for a limited time at GA and subject to change at its discretion. Do not build a multi-year model that assumes $12 and $24 per user stay included. Budget credit overage as a real, variable line item.
If you already bought Duo Pro or Duo Enterprise
Those seat-based plans continue and do not consume credits. On migrating to the Agent Platform, GitLab exchanges the remaining dollar value of your seat commitment for monthly credits with volume-based discounts. You are not stranded.
Run the numbers on your own instance. ReleaseTEAM’s GitLab Credits Planner reads your own GitLab licence, billable-user and Duo usage exports and projects your seat true-up exposure, your renewal cost and your GitLab Credits burn-down. It runs entirely in your browser: nothing you load is uploaded.
Frequently asked questions
Is self-managed GitLab cheaper than GitLab.com?
Not on licensing — the per-seat price is the same $29 for Premium either way. Self-managed removes GitLab’s storage and compute metering, but you take on the infrastructure, upgrades and operational cost instead. The decision should be driven by data residency, network isolation and control requirements, not by an expected licence saving.
What is GitLab Dedicated, and what does it cost?
Dedicated is single-tenant SaaS, fully isolated, deployed in your chosen AWS region and operated by GitLab. It requires Ultimate. GitLab does not publish pricing or a seat minimum for it — both are sales-quoted. Pre-production environments are a separate add-on. A 1,000-seat minimum circulates widely online but is not stated in any GitLab source, so do not plan around it without written confirmation. We can get you Dedicated pricing and the actual minimum for your situation — contact us for details or a special quote.
Is there a minimum seat count for Premium or Ultimate?
GitLab publishes none for Free, Premium or Ultimate. The Free tier’s 5-users-per-top-level-group limit on SaaS is a cap, not a purchase minimum.
Can we move a subscription between GitLab.com and self-managed?
No. Subscriptions cannot be transferred between the two. Switching means buying a new subscription, which makes the hosting decision worth getting right the first time.
What is GitLab Flex?
A newer commercial model that folds seats and credits into a single annual dollar commitment drawn down monthly, with volume discounts applied automatically based on total commitment. Seat and credit reservations can be adjusted month to month without contract amendments. Worth asking about in any large negotiation. Note that multi-year Flex contracts operate as separate annual pools — unused balance does not carry forward between years.
Do bot and service accounts consume seats?
GitLab’s own bot accounts — Support Bot, Migration Bot, Alert Bot — do not. A service account you create as an ordinary user with a role on projects will.
Pricing and licensing terms verified 18 September 2026 against GitLab’s published pricing, documentation and handbook. GitLab’s AI packaging in particular is changing quickly — confirm current terms before budgeting. ReleaseTEAM is a GitLab partner and delivers GitLab migrations, implementations and managed services.
Premium or Ultimate? Let’s do the maths on your estate.
The answer usually turns on how many Guest users you have and whether you need security findings in the merge request. We model both, and handle the migration if you decide to move.
Speak With An Expert