What is GitLab #
GitLab is a DevOps platform: source hosting, code review, CI/CD, registries and security scanning in one application. GitLab Inc. runs it as a service and ships it as software you install.
Three delivery models matter:
- GitLab.com, multi-tenant SaaS run by GitLab
- GitLab Self-Managed, which you install and run on premise or in your own cloud
- GitLab Dedicated, single-tenant SaaS run by GitLab, with a FedRAMP variant for government
Watch the edition naming. Community Edition (CE) is the open-source build under the MIT License. Enterprise Edition (EE) is the commercial build under the GitLab Enterprise Edition license. Both ship from one codebase, and EE features stay locked until you apply a subscription. Install EE with no license and it runs as Free.
Which license types does GitLab support #
Two things get called a GitLab license. Keep them apart.
Subscription tiers #
Free, Premium and Ultimate. As of September 2026, Premium lists at $29 per user per month billed annually, and Ultimate is quoted individually. Add-ons sit on top: GitLab Duo, Enterprise Agile Planning at $15 per user per month, compute minutes and storage.
How the entitlement reaches the instance #
An activation code is a 24-character alphanumeric string you paste into Admin > Subscription. Cloud licensing needs a connected instance. Air-gapped sites upload a license file instead.
In a scaled architecture, upload to one instance only. The license sits in the database and replicates. On GitLab Geo, that means the primary.
Who consumes a seat #
Billable roles are Guest on Premium, plus Planner, Reporter, Developer, Maintainer, Owner and Security Manager. This is where the money is. Auditor users are billable. So are administrators on Self-Managed Premium and Ultimate.
These consume nothing:
- users pending approval
- deactivated, banned or blocked users
- the Minimal Access role
- service accounts and bot users (Ghost User, Support Bot, Migration Bot, Alert Bot, project and group bots)
- on Ultimate only, users whose sole role is Guest
Maximum users #
GitLab charges on maximum users, the peak billable count during the billing period, minus the seats you bought. Ten seats purchased, a peak of thirteen, and you owe three. You still owe those three if the people left in month two.
GitLab settles at quarterly reconciliation or a true-up at renewal, and calls the shortfall users over subscription, or seats owed on SaaS.
Premium and Ultimate self-managed instances can export a license usage file from Admin > Subscription, holding daily billable counts. It’s manual, one instance at a time, and GitLab warns you not to open it before submitting.
Which software vendors work with GitLab, and what they cost you #
GitLab isn’t a license manager that software vendors build into their own applications, the way FlexNet, Reprise or Sentinel are. It doesn’t check out or enforce licenses for third-party software. What moves your GitLab bill is the tooling wired into it.
Start with the identity providers. Okta and Microsoft Entra ID provision GitLab users over SCIM. Deprovisioning in the IdP removes group access, but the GitLab account survives. If offboarding stops at the IdP, your peak count keeps climbing.
CI, code quality and security tools connect through tokens. Jenkins, SonarQube, Snyk, Trivy and Semgrep each need an identity on the instance. GitLab generally leaves service accounts and bot users out of the billable count, so they’re usually the cheapest place to point these tools. Run an integration under a named human account and it can end up holding a billable seat. Before you count an integration as free, check how it authenticates and which account type it runs under.
Jira, Confluence, Slack and Salesforce each run their own seat model, and none read yours. Same in the IDE: VS Code, JetBrains and Visual Studio connect to GitLab, and each IDE license is its own line item.
Duo is priced apart from all this. You buy and assign Duo Pro and Duo Enterprise seats separately, while Duo Core comes bundled with Premium and Ultimate from GitLab 18.0. Admin > GitLab Duo shows seat utilization with each user’s last activity date.
How Open iT supports your work with GitLab #
Open iT measures how software gets used and turns that into entitlement decisions. Discovery tools stop at what’s installed. The collector polls the GitLab API. An Open iT Core Client runs the license status utility hourly, on a five-minute sample interval. Preprocessed data reaches the Core Server at five past the hour, in the client’s timezone.
Setup asks for the base URL and a personal access token with read_api scope, kept in an encrypted credential file. That token needs Owner access to the group on gitlab.com, or Administrator on self-managed.
Few estates run a single GitLab. Configure one collector node per account, and a gitlab.com group and a self-managed server report into the same set.
Three levels, in license-manager terms. GitLab is documented as a Level 1 source.
Runtime Usage is Level 1: the hourly record of who held a GitLab seat and when. Every hour, all term. That’s the audit trail underneath the maximum-users figure, and the License Monitor Portal shows it live.
Levels 2 and 3 work across the rest of your estate. True Active Usage separates a seat that’s checked out from a seat someone is working in, reading CPU, elapsed time, keyboard, mouse and I/O. Managed Usage finds what sits idle and returns it to the pool.
For a mixed estate this is the part that matters. GitLab reports through the same pipeline as your FlexNet, Reprise, Dassault and Autodesk sources, so its seats land in the same chargeback report as every other vendor.
Foire aux questions #
What is a GitLab license manager?
There’s no GitLab license manager daemon like FlexNet Publisher or RLM. GitLab enforces the subscription inside the application, through an activation code or a license file. Managing GitLab licenses means tracking billable users against purchased seats over time. That’s a metering job, with no license server involved.
How do I add a license to GitLab?
Sign in as an administrator, go to Admin > Subscription, and paste your 24-character activation code. Offline instances upload a license file instead, and scaled or Geo deployments take it on one instance only. Adding a LICENSE file to a project is something else: declaring the open-source license of your own code.
Does a Guest user cost a GitLab seat?
On Ultimate, a user whose only role is Guest consumes no seat. On Premium, Guest is billable. That difference alone changes tier math for organizations with large read-only populations.
Why is my GitLab renewal higher than my current user count?
Because GitLab bills on the peak billable count reached during the billing period. Renewal-day headcount doesn’t enter into it. Users who joined and left still count, and daily usage history shows when the peak happened and why.
