No more typing reviews! Try our Samantha, our new voice AI agent.

GitLab vs Split comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

GitLab
Ranking in Build Automation
1st
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
91
Ranking in other categories
Application Security Tools (6th), Release Automation (2nd), Static Application Security Testing (SAST) (4th), Rapid Application Development Software (11th), Software Composition Analysis (SCA) (4th), Enterprise Agile Planning Tools (2nd), Fuzz Testing Tools (2nd), DevSecOps (1st)
Split
Ranking in Build Automation
21st
Average Rating
8.4
Reviews Sentiment
4.0
Number of Reviews
3
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of July 2026, in the Build Automation category, the mindshare of GitLab is 6.6%, down from 15.1% compared to the previous year. The mindshare of Split is 0.6%, up from 0.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
GitLab6.6%
Split0.6%
Other92.8%
Build Automation
 

Featured Reviews

BasilJiji - PeerSpot reviewer
System engineer at a retailer with 10,001+ employees
Role-based workflows have transformed daily deployments and improve team collaboration
GitLab has role-based access control, so when a team member needs to make a code change, they cannot directly apply it to the environment but must put in a merge request. Once a senior reviews the code and approves it, then it is implemented across the environment, making it safer and allowing everyone to experience the process. The best features GitLab offers are version control and automation, which are the major things that stand out to me. When it comes to access, the login is very smooth, with just one login integrated with our Okta, allowing everyone to log in easily. Deployments become much easier, and that is how GitLab helps. The automation features make my work easier because we use a tool called AWX, which is connected to GitLab. Whenever we run a job on AWX, it directly checks the code and uses it. Since the code is not preserved locally but kept in the cloud, it is safe and nobody can tamper with it. When it comes to safety, that is a major thing. Automation features allow the code to be accessed from any tools we use, so the jobs we run are helping tremendously and doing their work perfectly. For pipeline tasks, we have created a significant amount of pipelines, which are all hosted in GitLab. Running the pipelines has become much easier, and they are doing a perfect job, helping tremendously in our day-to-day activities. GitLab has positively impacted my organization because previously we stored code locally on servers, leading to many risks. Since GitLab came into our environment, our integration and deployments became much easier, helping our work become much smoother. Improvements from GitLab have led to better team collaboration because when several people are working, they can all edit the code and submit it as a merge request, and once approved, it reflects directly to the main branch. Many can work at the same time. When it comes to deployments, deploying has become much faster since we started using GitLab, and even if errors occur, we can spot them easily and troubleshoot, which has helped tremendously.
PM
Senior Decision Scientist at Tesco
Data-driven experiments have transformed feature rollouts and now validate business impact
I feel that overall my experience with Split has been positive regarding necessary improvements, particularly around user experience and enhancements to the user interface, especially for larger teams. As experimentation programs grow, users must navigate many feature flags and different environments, so making discovery, organization, and lifecycle management more intuitive would be beneficial. While Split integrates well with many tools, additional connectivity with analytics and BI reporting platforms could provide a more seamless experience for organizations. There are areas where Split can be improved, particularly around advanced reporting and visualization capabilities. While the platform manages experiments and feature rollouts effectively, having more robust, out-of-the-box reporting options would allow business stakeholders to interpret results without relying on external tools. Additionally, as organizations grow, managing and overseeing feature flags becomes more challenging, so enhancing governance capabilities would be beneficial. In terms of user experience and integrations, I think the platform could enhance those areas as well. Users often need to navigate through a large number of feature flags as experimentation programs scale, so improvements to the user interface that simplify discovery, organization, and lifecycle management would be valuable, especially for larger teams. While Split integrates effectively with many tools, increasing connectivity with analytics and BI reporting could help organizations enhance their operations.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"GitLab has impacted my organization positively in terms of version control systems, providing many smart features and reducing the sharing of dependencies compared to what we used to do previously."
"We like that we can create branches and then the branches can be reviewed and you can mesh those branches back. You can independently work with your own branch, you don't need to really control the core of other people."
"Git merging allows us to track the details of how and who has done what; this is the best feature which is useful for all companies."
"The code merging capability is something that we use very frequently."
"GitLab is a solution for source code management, container registry, pipelines, testing, and deployment."
"GitLab is used for pipeline development, automation, and deployment."
"We use the Git repository and tagging feature. We are a product-based company and use this solution to move to a forward or backward tag."
"The solution has an established roadmap that lays out its plans for upgrades over the next two to three years."
"Split facilitated a culture of data-driven decision-making, allowing us to validate our ideas and providing measurable outcomes for decisions."
"Split is a great way to handle the config based on checks and in a dynamic way if you want to control your software without doing any deployment."
"Split has increased some of our CVR; for example, in a recent pop-up model experiment, our conversion was around 15% and once we started the experiment, the on-variant won by increasing the CVR up to 35%, making it a really good tool for determining which particular feature would deliver the expected CVR."
 

Cons

"GitLab could consider introducing a code-scanning tool. Purchasing such tools from external markets can incur charges, which might not be favorable. Integrating these features into GitLab would streamline the pipeline and make it more convenient for users."
"Even if I say I want some improvement, they will say it is already planned in the first quarter, second quarter, or third quarter. That said, most everything is quite improved already, and they're improving even further still."
"Merge conflicts and repository maintenance could improve. If there is someone new to the system they would not know if there is a conflict."
"The solution could be faster."
"In the next release, I would like to see GitLab expand its integration capabilities to include platforms like DigitalOcean, which developers widely use for cloud infrastructure. Enhancing CI/CD automation features specifically tailored for DigitalOcean would be beneficial."
"GitLab would be improved with the addition of templates for deployment on local PCs."
"The integration and storage capabilities could be better."
"Perhaps the integration could be better."
"The UI of split.io can be improved."
"Additionally, we tend to move towards other issues related to Split due to flickering issues, which we observed because of latency."
"There are areas where Split can be improved, particularly around advanced reporting and visualization capabilities."
 

Pricing and Cost Advice

"The solution's pricing is acceptable."
"This is an open-source solution."
"The solution is free."
"We are currently using the open-source version."
"GitLab is comparatively expensive, but it provides value because it's feature-rich."
"It seems reasonable. Our IT team manages the licenses."
"Regarding pricing, I would rate GitLab as moderately priced, maybe around a seven or eight out of ten. It could be more flexible for clients but generally offers good value."
"There are different licensing options available, including a free limited-user license."
Information not available
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
902,988 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Manufacturing Company
11%
Government
9%
Computer Software Company
9%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business38
Midsize Enterprise10
Large Enterprise49
By reviewers
Company SizeCount
Small Business6
Large Enterprise4
 

Questions from the Community

What is your experience regarding pricing and costs for GitLab?
The setup cost for GitLab is minimal since the team has its own minimal resource balancing. The costing falls into an intermediate stage and is impactful across all results within the team. It allo...
What needs improvement with GitLab?
There are many improvements that GitLab can implement, such as addressing the issue of caching. Currently, when I have multiple tasks to merge or attempt multiple merges, the CI/CD and overall GitL...
What is your primary use case for GitLab?
My main use case for GitLab is as a version control system that we are using. Currently, I am working on an end-to-end AI pipeline, and I have deployed my whole code using GitLab so that all things...
What is your experience regarding pricing and costs for Split?
I have used Split for setup, cost, licensing, and pricing.
What needs improvement with Split?
Split is a strong feature management platform, but there are opportunities for improvement. Simpler onboarding with guided workflows and beginner-friendly documentation would help new users get sta...
What is your primary use case for Split?
Split has helped streamline our cloud-native application delivery by enabling safe feature rollouts and controlled releases through feature flags. The ability to separate deployment from release re...
 

Comparisons

No data available
 

Also Known As

Fuzzit
No data available
 

Overview

 

Sample Customers

1. NASA  2. IBM  3. Sony  4. Alibaba  5. CERN  6. Siemens  7. Volkswagen  8. ING  9. Ticketmaster  10. SpaceX  11. Adobe  12. Intuit  13. Autodesk  14. Rakuten  15. Unity Technologies  16. Pandora  17. Electronic Arts  18. Nordstrom  19. Verizon  20. Comcast  21. Philips  22. Deutsche Telekom  23. Orange  24. Fujitsu  25. Ericsson  26. Nokia  27. General Electric  28. Cisco  29. Accenture  30. Deloitte  31. PwC  32. KPMG
Information Not Available
Find out what your peers are saying about GitLab vs. Split and other solutions. Updated: June 2026.
902,988 professionals have used our research since 2012.