GitKraken Licensing Explained: GitLens, Seat Caps and Git Integration for Jira
This page answers the GitKraken licensing questions buyers actually ask — whether your developers using GitLens for free owe anything, why the seat caps force a tier change, and how Git Integration for Jira is counted. Figures are GitKraken list prices in USD.
The short answer: GitLens is not licensed separately. One email-based subscription covers GitKraken Desktop, GitLens, the CLI and gitkraken.dev — so a company standardising on GitLens is buying GitKraken platform seats whether or not anyone realises it. The free/paid line is drawn at the repository, not the feature: GitLens’s advanced features work only on local and public repos, which by design makes them unavailable in commercial use.
We use GitLens for free. Do we owe anything?
This is the most consequential question on the page, and the answer has two halves.
What stays genuinely free forever: inline blame annotations, hovers, CodeLens, revision navigation and in-editor Git insights. There is no licence exposure from merely installing GitLens, however many developers do it.
What requires a paid seat: Commit Graph on private repos, Worktrees, Visual File History, Launchpad, Cloud Patches, the GitLens Home View, GitKraken AI features, and enterprise integrations including SSO.
The mechanism is subtle and worth understanding. Those advanced features exist in the free tier — but they are restricted to local and public repositories only. Every developer at a company works on private repos. So the free tier’s advanced functionality is unavailable in commercial use by design. The restriction is precisely calibrated to make open source work free and commercial work paid.
Two consequences follow. You cannot buy a cheap “GitLens-only” seat — a GitLens Pro user is a full platform user at platform pricing. And on lapse, Desktop reverts to free with no data loss, but private repos become inaccessible.
What are the tiers, and why do the seat caps matter?
| Tier | Seat cap | What it adds |
|---|---|---|
| Community | Unlimited | Free. Basic Desktop, CLI and GitLens. Local repos and public remotes only. Limited AI |
| Pro | Max 2 | Private repos, cloud integrations, 1M AI credits/week |
| Advanced | Max 10 | Self-hosted Git integrations, enterprise integrations, SSO, 2M AI credits/week |
| Business | Max 100 | Multi-domain SSO, GitKraken Insights access, success manager, 3M credits/week |
| Enterprise | 20+ required | Custom contracts, security audits, 6-hour support SLA, 4M credits/week |
The seat caps are the pricing mechanism, not the feature list. Pro is capped at 2 seats and Advanced at 10. Any team above ten developers is on Business or Enterprise regardless of which features they actually need. That is the cliff to model — teams routinely scope on features, then discover the cap decides for them. The 20–100 seat overlap between Business and Enterprise is a negotiation zone.
Published pricing
| Tier | Price |
|---|---|
| Advanced | $14/user/month |
| Business | $216/user/year |
| Enterprise | $336/user/year |
| On-Premise | $336/user/year — but see note |
| GitKraken Insights | $25 per contributor per month, billed annually |
Every published tier price is quoted as paid annually; monthly billing does not appear to be offered at the team tiers.
Two things to verify before you quote. GitKraken’s own On-Premise page shows $24 per user per month ($288/year) while the current reseller list shows $336/year — these disagree, and the vendor page is probably stale post-increase. And list prices changed in mid-2026: new sales from 16 June, renewals from 8 July. Any purchase order already sent at a previously quoted price is honoured at that price, which matters if you have quotes in flight. Contact us and we will confirm the current figures against your seat count.
Note that Insights is priced per contributor rather than per seat — a distinct unit, and contributor count and licensed-seat count are rarely the same number.
Which tier do we need for SSO?
Advanced at minimum. Enterprise for multi-domain SSO. SAML 2.0 against any compliant identity provider, with documented support for Entra ID, Okta, Ping and Google Workspace. A company with several email domains after an acquisition is pushed to Enterprise for that reason alone.
One mechanic to watch: just-in-time provisioning auto-adds verified users on first SSO login when enabled and licences are available. SSO plus JIT can silently consume seats. No SCIM provisioning is documented.
How is Git Integration for Jira licensed?
Standard Atlassian Marketplace rules apply, and GitKraken states it plainly: all active Jira users require a licence for Atlassian Marketplace apps. The app tier must match your Jira tier.
The quirk worth flagging: despite being a repository-integration tool, there is no repository-count component and no free tier. Cost scales with your total Jira seat count even though only your developers connect repositories. A 2,000-seat Jira with 40 developers using Git integration pays the 2,000-user tier.
Two editions on Cloud. Standard covers up to 200 repositories. Advanced raises that to 30,000, and adds 6-hour priority support, Signals analytics and SOC 2 compliance reports. Both support GitHub, GitLab, Azure DevOps and Bitbucket.
Cloud and Data Center are maintained as separate products with separate documentation. There are also two Marketplace listings in circulation — confirm which one a customer is actually on before quoting a renewal.
GitKraken deliberately publishes no price table for this app; it is transacted through Atlassian, so pricing comes from the Atlassian calculator or the Marketplace listing for your specific seat count.
Where GitKraken licensing catches buyers out
Licences are per person, not per device
Accounts are email-based, so one developer can run their seat on multiple machines. Conversely two people cannot share one seat. Some roles — billing contact, for example — do not consume a licence.
AI credits are a new consumption meter
Weekly credit allowances scale by tier, from 1M on Pro to 4M on Enterprise, and are pooled across the organisation at Business and above. Add-on credit packs are sold separately. This is a genuinely new dimension layered on per-seat pricing in 2026 and a likely source of overage conversations — model it rather than assuming the included allowance covers you.
Self-hosted has a 10-user minimum
Two flavours: Self-Hosted Server with automatic licence tracking and LDAP, and Serverless for air-gapped or low-connectivity environments with manual tracking by agreement. Minimum 10 users, no maximum. On lapse, Serverless clients lock entirely until a new licence file is applied — a harder failure than the Desktop downgrade.
The 2026 price increases are live
If your renewal is this quarter, you are likely facing an increase. Quotes already issued at the old price are honoured, so check whether anything is in flight before re-quoting.
Frequently asked questions
Is GitLens licensed separately from GitKraken Desktop?
No. One email-based subscription spans Desktop, GitLens, the CLI and gitkraken.dev. You cannot buy GitLens standalone at a lower price.
How are seats counted, and do inactive users cost us?
Each active organisation member requires a licence. Billing-only roles do not consume one. Watch JIT provisioning, which can add users automatically on first SSO login and consume seats without an admin action.
Can we self-host, and does it work air-gapped?
Yes to both — Self-Hosted Server or Serverless, with a 10-user minimum. Serverless is the air-gapped option and uses manual licence tracking by agreement.
What happens if we stop paying?
GitKraken Desktop reverts to the free tier: no data is lost, but private repositories become inaccessible and you are limited to one profile. Serverless on-premises clients lock completely until a new licence file is applied.
What are AI credits and what do overages cost?
A weekly allowance per tier, pooled organisation-wide at Business and above, with add-on packs available. Overage pricing is not published. Given this is new in 2026 and not well understood, get the overage rate in writing before committing.
Can we licence only our developers for Git Integration for Jira?
No. All active Jira users must be licensed and the app tier must match the Jira tier. This is an Atlassian Marketplace rule rather than a GitKraken choice, and it applies to every paid app on the Marketplace.
What is Kepler, and is it included?
Kepler is GitKraken’s 2026 agentic development environment — a place to run AI coding agents across repositories, built on the Agent Client Protocol and deliberately agent-agnostic. We found no pricing or tier-gating information published for it at all, which for a flagship launch is a notable gap. Confirm before assuming it is included in a tier.
Pricing and licensing terms verified 19 September 2026 against GitKraken’s published help documentation, pricing pages and current reseller list pricing. GitKraken’s pricing pages render figures client-side and several returned placeholders; per-tier prices above come from the current published reseller list. The On-Premise price is disputed between sources — confirm before quoting.
GitLens spreading quietly across your engineering team?
It is worth knowing what that actually costs before a renewal conversation forces the issue — including whether the seat caps push you past the tier you planned for. We size GitKraken against real usage and handle the Atlassian-side Git Integration licensing alongside it.