All Products
Browse all analyzed products with real user feedback patterns.
Browse all analyzed products with real user feedback patterns.
The complete DevSecOps platform
GitLab scores high on security (85) and integrations (85) as a comprehensive DevSecOps platform, but low on performance (50) due to acknowledged slowness, pricing (55) due to increases, and usability (55) due to cluttered UI. Overall 60/100 reflects powerful features undermined by execution issues.
GitLab is an all-in-one DevSecOps platform providing source code management, CI/CD pipelines, security scanning, project management, and more. Available as cloud-hosted (GitLab.com) or self-managed, it aims to replace multiple DevOps tools with a single integrated platform.
Patterns extracted from real user feedback — not raw reviews.
GitLab's CEO has acknowledged that GitLab.com is slow and unreliable. Users report page load times of 7-10 seconds minimum, with requests regularly taking longer. Both self-hosted and SaaS versions suffer from performance issues, especially with large repositories.
GitLab CI/CD can be slow due to repository size, pipeline complexity, and cache misconfiguration. Cache is a runner behavior, not GitLab feature - ephemeral Docker runners may never actually cache. Adding runners rarely fixes slow pipelines.
Self-hosted GitLab requires substantial server resources for acceptable performance. Users on modest servers report 5+ second page loads. Gitaly jobs can spike from 1,000-5,000 to 15,000 per minute when problems trigger, overwhelming systems.
Users find GitLab's interface cluttered and complicated, making navigation overwhelming. The learning curve is steep, particularly for newcomers. Feature-rich doesn't mean user-friendly - many struggle to find what they need among the extensive options.
GitLab's all-in-one approach means features for everything, but finding and using what you need is overwhelming. Simple tasks require navigating through layers of menus. The comprehensive feature set becomes a liability for teams wanting simplicity.
GitLab raised Premium pricing from $19 to $29/user/month (53% increase), leaving many customers frustrated. Users report the new price doesn't match the extra value received. Price increases create financial strain for teams that budgeted based on previous rates.
Full security features like DAST and license compliance sit in Ultimate ($99/user/month), not Premium. Teams feel they pay enterprise-level money for Premium only to get planning tools. The jump from Premium to Ultimate is a 242% increase.
Users report dirty 2-year contract lock-ins if you miss your cancellation period. GitLab then attempts to raise prices mid-contract. Internal sales documents discuss 'price lock negotiations' as a tactic. Customers feel trapped.
When documentation is viewed by internal users, those users suddenly cost $1,200/year for minimal features. Teams must either lock people out or pay enterprise rates for users who log in once a month. Seat-based pricing doesn't account for usage patterns.
Trustpilot reviews report bugs that are 8-11 years old with chains of complaints still unfixed. UX issues persist where there's a 50/50 chance a page will dynamically update with changes. Long-standing issues erode confidence in the platform.
If customers don't renew their GitLab subscription, their license key stops working and Enterprise Edition becomes non-functional. Downgrading to free Community Edition loses all premium features with no graceful degradation.
Documentation is often lacking in the workflows space, making complex systems tricky to understand. Users struggle to find clear guidance for advanced CI/CD configurations, security scanning setup, and integration patterns.
True all-in-one DevSecOps platform
GitLab integrates source code, CI/CD, security scanning, issue tracking, and project management in one platform. No need for separate tools like Jenkins, Jira, or SonarQube. Reduces tool sprawl and simplifies DevOps workflows.
Built-in CI/CD without additional tools
GitLab CI/CD is deeply integrated with repositories. Pipeline configuration lives in the repo (.gitlab-ci.yml). No need to set up Jenkins or configure external CI servers. Parent-child pipelines enable complex workflows.
Free self-hosting option with Community Edition
GitLab Community Edition is free forever for self-hosting. Full Git functionality, CI/CD, and many features without cost. Organizations wanting control over their code can self-host without subscription fees.
Comprehensive security scanning suite
GitLab Ultimate includes SAST, DAST, dependency scanning, container scanning, and license compliance. Security integrated into CI/CD pipeline rather than separate tools. DevSecOps in one platform.
Excellent merge request workflow
Merge requests (GitLab's pull requests) are feature-rich with inline comments, approval rules, merge trains, and automatic environment creation. Review Apps let reviewers test changes in live environments.
Strong Kubernetes and cloud-native integration
Native Kubernetes integration for deployments, Auto DevOps for automatic CI/CD setup, and built-in container registry. Cloud-native organizations benefit from tight integration with modern deployment patterns.
Users: 5 users per namespace
Storage: 5GB storage
Limitations: 5 user limit, 400 compute minutes, no advanced CI/CD features, limited support
Users: Per user/month
Storage: 50GB storage
Limitations: No DAST, no license compliance, no enterprise security features
Users: Per user/month
Storage: 250GB storage
Limitations: Very expensive at scale, 242% more than Premium
Unlimited repos
Feature-rich
.gitlab-ci.yml
Auto DevOps
Built-in
Premium+
Ultimate only
Ultimate only
Ultimate only
Built-in
Built-in
Free CE available
Extra $19/user
Limited (5 users)
DevSecOps teams needing integrated security
GitLab Ultimate provides comprehensive security scanning (SAST, DAST, dependency, container, license) integrated into CI/CD. One platform for everything reduces tool sprawl. The price is high but consolidates multiple tools.
Organizations requiring self-hosting
GitLab offers free Community Edition for self-hosting with substantial features. Premium and Ultimate are available for self-managed deployments. Full control over code and compliance-friendly.
Enterprises consolidating DevOps tools
GitLab replaces separate tools for source control, CI/CD, project management, and security scanning. Reduced integration complexity and single-vendor simplicity. Worth the premium for large organizations.
Small teams on tight budgets
Free tier limits to 5 users and 400 compute minutes. Premium at $29/user adds up quickly. Self-hosted Community Edition is free but requires server management. Evaluate if complexity is worth the cost savings.
Open-source project maintainers
GitLab offers free Ultimate for qualifying open-source projects. However, GitHub has the larger open-source community and better discoverability. Evaluate based on project needs and community preferences.
Teams wanting simple Git hosting
GitLab's all-in-one approach is overkill for basic Git needs. The complex interface and feature bloat overwhelm teams just wanting source control. GitHub or Bitbucket offer simpler experiences for basic hosting.
Teams prioritizing UI/UX simplicity
GitLab's interface is notoriously cluttered and overwhelming. Navigation is complex, and finding features requires learning the platform's structure. GitHub offers a cleaner, more intuitive experience.
Teams already invested in Atlassian
If you use Jira and Confluence, Bitbucket's native integration is more seamless. GitLab integrates with Atlassian tools but not as deeply. Consider if the all-in-one benefit outweighs integration friction.
Common buyer's remorse scenarios reported by users.
Teams chose Premium expecting sufficient security features, then discovered DAST and license compliance require Ultimate. The 242% price jump to Ultimate wasn't in budget, forcing compromise on security posture.
Organizations on long-term contracts faced unexpected price increases from $19 to $29/user. The 53% jump strained budgets that were planned based on original pricing. Negotiating price locks became necessary.
Teams self-hosting GitLab discovered acceptable performance required significantly more server resources than expected. 5+ second page loads on modest hardware led to unplanned infrastructure investment.
Teams adopted GitLab for consolidation but found the feature bloat overwhelming. Simple tasks became complex navigations. Some regretted not using simpler specialized tools that did one thing well.
When documentation or wikis were shared with internal stakeholders, those read-only users counted toward paid seats. Organizations faced paying enterprise rates for users who logged in once monthly.
After signing a 2-year contract, teams discovered issues with performance or pricing but couldn't switch without penalty. Missing cancellation windows extended lock-in further.
Scenarios where this product tends to fail users.
Free tier's 5-user limit forces upgrade to Premium ($29/user/month) when teams grow. The jump from free to paid is significant. Organizations must decide between paying or splitting workloads.
Security requirements demand DAST, license compliance, or compliance management - all Ultimate-only features. Premium teams face 242% price increase or security gaps.
As repos and users grow, self-hosted GitLab becomes slow. Gitaly spikes overwhelm the server. Performance optimization requires significant DevOps investment or hardware upgrades.
Free tier's 400 minutes or Premium's 10,000 minutes run out with active CI/CD. Projects block on depleted quotas. Must upgrade tier, purchase additional minutes, or set up self-hosted runners.
Onboarding developers familiar with GitHub's simpler UI find GitLab's cluttered interface overwhelming. Productivity suffers during the extended learning curve. Training investment required.
If GitLab subscription isn't renewed, the license key stops working. Enterprise Edition becomes non-functional. Must downgrade to Community Edition, losing all premium features instantly.
GitHub
9x mentionedTeams switch for the larger community (100M+ developers), cleaner UI, and faster performance. GitHub Actions provides CI/CD. Trade-off: lose GitLab's integrated security scanning and self-hosting flexibility.
Bitbucket
7x mentionedAtlassian shops switch for native Jira/Confluence integration. Pipelines provides CI/CD. Simpler pricing for small teams. Trade-off: smaller community, fewer integrated DevSecOps features.
Azure DevOps
6x mentionedMicrosoft-centric organizations switch for tight Azure integration. Repos, Pipelines, Boards, and Artifacts in one platform. Similar all-in-one approach. Trade-off: heavier Microsoft ecosystem lock-in.
Gitea
5x mentionedTeams wanting lightweight self-hosting switch to Gitea. Much faster, minimal resources required, easy to maintain. Open source. Trade-off: no built-in CI/CD (use external), fewer enterprise features.
Jenkins + GitHub
5x mentionedTeams frustrated with GitLab CI/CD complexity use Jenkins for CI and GitHub for source control. More control over CI configuration. Trade-off: managing multiple tools, integration overhead.
See how GitLab compares in our Best Developer Platform Software rankings, or calculate costs with our Budget Calculator.