If you spend enough time in GitLab forums, one number comes up again and again.

Seven hundred twenty-five percent.

That’s the effective price increase former Starter tier users absorbed when GitLab axed the $4/user/month plan and pushed everyone to Premium at $19 — now $29 — per user, per month. To a solo developer paying $4, that’s an inconvenience. To a 50-person team, it’s a line item that gets noticed. To a 500-person enterprise that was promised predictable pricing, it’s a governance problem.

The threads haven’t stopped. And they tell us something important about how engineering teams should evaluate platform pricing.

The Math

Here’s the actual trajectory:

  • Starter ($4/user/month): Discontinued. Users forced to upgrade or lose features.
  • Premium increase #1: $4 → $19. A 375% bump.
  • Premium increase #2: $19 → $29. Another 53% on top.
  • Cumulative: A team that signed up for Starter at $4 now pays $29. That’s 725%.

GitLab’s justification: they were becoming a DevSecOps platform, not just a git host. More features, more value, higher price.

The community’s response:

“You know what really grinds my gears? Their announcement talked about becoming a devsecops platform and that’s one reason for the price increase. I have been frustrated because most of their good security features are restricted to Ultimate tier at five times the cost.”

The security features that supposedly justified Premium’s price increase? Most of them require Ultimate. Which costs approximately $99/user/month equivalent.

The Billable User Problem

The pricing complaint that generates the most heat isn’t about the number. It’s about who gets counted.

Multiple practitioners report their GitLab instance counting system users as billable — root accounts created during setup, service accounts with no assigned role. These users can’t push code, can’t open issues, can’t do anything except exist. And GitLab’s license counter flags them.

“We have 6 users that meet that definition. We also have a root user that was created by the system. The UI clearly shows ‘Roles: None’ for these accounts. After applying the premium license, the server immediately displays ‘8 billable users’. I’m about ready to sic our lawyers on them.”

In a subsequent thread, someone else recounted the same experience with 30 phantom users on a 200-person license. That’s 15% padding. On five-figure annual contracts.

Why This Matters Beyond the Price Tag

Pricing resentment isn’t just about money. It corrodes the relationship between a platform and its users.

Every new feature announcement now arrives with suspicion. GitLab launches Duo AI features. The immediate community reaction: “Great, more features nobody asked for while basic filtering on boards is still broken.” Whether that’s fair or not — and it’s partially fair — the pricing history has burned the trust that would let users give new features the benefit of the doubt.

This is a structural problem for GitLab. They’re a public company losing $190 million a year. They need revenue growth. But their most natural growth lever — extracting more revenue from existing users — damages the community that advocates for the platform.

What You Can Do About It

If you’re evaluating GitLab right now, you have leverage that earlier buyers didn’t.

Negotiate hard. GitLab’s $29/user/month Premium pricing is a starting point, not a fixed price. Volume discounts of 20-40% for 500+ seats are standard practice. Multi-year commitments lock in rates and prevent the next surprise price increase.

Get the billable user definition in writing. Before signing, clarify exactly which users count. System accounts, service accounts, guest roles — define them all. If GitLab won’t include this in the contract, treat that as a signal.

Use guest users strategically. Ultimate tier includes unlimited guest users. Non-coding stakeholders — project managers, executives, auditors — don’t need paid seats. For an organization with 200 developers and 150 stakeholders, that’s roughly $45,000/year in avoided costs.

Consider the CE safety net. GitLab Community Edition is genuinely free and open source. If GitLab’s commercial pricing becomes untenable, CE is a functional fallback — missing enterprise features, but preserving your repositories.

This analysis draws from practitioner discussions on r/gitlab and r/devops, official GitLab pricing documentation, and financial reporting. Negotiation practices are based on practitioner accounts and should be evaluated against your specific procurement context.