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
3rd
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 (12th), 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.2
Reviews Sentiment
4.9
Number of Reviews
4
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of August 2026, in the Build Automation category, the mindshare of GitLab is 6.3%, down from 14.7% 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.3%
Split0.6%
Other93.1%
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's best feature is Actions."
"Previously we used Team Foundation Server, but GitLab is better for local cloud deployment."
"We like the automatic deployment for different environments."
"The SaaS setup is impressive, and it has DAST solutioning."
"CI/CD is very good. The version control system is also good. These are the two features that we use."
"This product is always evolving, and they listen to the customers."
"A user friendly solution."
"I previously used Gerrit and I prefer GitLab, as it is much better in the interface and integration, and it is more than only Git software, it is more of a complete package."
"Split has positively impacted my organization by improving both developer experience and customer experience."
"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."
"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 facilitated a culture of data-driven decision-making, allowing us to validate our ideas and providing measurable outcomes for decisions."
 

Cons

"We are having a few problems integrating with Jira at the moment, which is something that our IT department is investigating."
"The solution should be more cloud-native and have more cloud-native capabilities and features."
"There are occasions where we usually see a lot of outages using GitLab; it happens at least once a week or something like that."
"I would like to see static analysis also embedded in GitLab. That would also help us. If there's something that it does internally by GitLab and then that is already tied up with your pipeline and then it can tell you that you're coding is good or your code is not great. Based on that, it would pass or fail. That should be streamlined. I would think that would help to a greater extent, in terms of having one solution rather than depending on multiple vendors."
"I would like to have some features to support peer review."
"GitLab needs to improve the CI/CD functionality because it is not compatible with Jenkins and other tools, as it is not that efficient."
"The user interface could be more user-friendly. We do most of our operations through the website interface but it could be better."
"Authentication can be a problem when you have an application and you want to configure it with them. I used Spring Cloud config and to connect that to GitLab was so hard."
"The UI of split.io can be improved."
"Initially, I had difficulty finding analytics and understanding setup."
"There are areas where Split can be improved, particularly around advanced reporting and visualization capabilities."
"Additionally, we tend to move towards other issues related to Split due to flickering issues, which we observed because of latency."
 

Pricing and Cost Advice

"The solution's standard license is paid annually. They have changed the pricing model and it used to be better. There is a free version available."
"This product is not very expensive but the price can be better."
"It is very expensive. We can't bear it now, and we have to find another solution. We have a yearly subscription in which we can increase the number of licenses, but we have to pay at the end of the year."
"As I work in a vast enterprise, I'm unsure about the licensing cost for GitLab. It's the management team that takes care of that."
"There are different licensing options available, including a free limited-user license."
"It seems reasonable. Our IT team manages the licenses."
"The open-source version is very good and the commercial version is reasonably priced."
"My company uses the free version of GitLab, which is GitLab Community Edition. There is a licensed version also available for GitLab."
Information not available
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
909,725 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Manufacturing Company
10%
Government
9%
Computer Software Company
8%
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 Business7
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 needs improvement with Split?
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 te...
What is your primary use case for Split?
I have used Split to perform AB tests, controlled releases, and measure business outcomes. While my focus has been on analytics and the decision-making side, I have also used this platform for admi...
 

Comparisons

 

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: August 2026.
909,725 professionals have used our research since 2012.