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

Split vs TeamCity 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

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
TeamCity
Ranking in Build Automation
12th
Average Rating
8.2
Reviews Sentiment
7.7
Number of Reviews
28
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of August 2026, in the Build Automation category, the mindshare of Split is 0.6%, up from 0.0% compared to the previous year. The mindshare of TeamCity is 4.9%, down from 7.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
TeamCity4.9%
Split0.6%
Other94.5%
Build Automation
 

Featured Reviews

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.
RG
IT Professional at NatWest Group
Versatile agent support boosts builds but UI and setup costs need refinement
TeamCity's user interface could be improved; specifically, the tree structure on the homepage is not clear, making it difficult to search for projects. Moreover, there are some limitations related to the version we were using. For instance, there were issues with agent specifications for particular build jobs and a timeout issue where jobs running longer than three hours would fail automatically.

Quotes from Members

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

Pros

"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 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 positively impacted my organization by improving both developer experience and customer experience."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"The solution has been fantastic for our organization due to the fact that we do not need a designer having to build the product and we don't need to figure out how to deploy it either, creating improved efficiencies which have saved us time and expense."
"VCS Trigger: Provides excellent source control support."
"The setup is extremely straightforward."
"Time to deployment has been reduced and it has helped in preventing us from deploying breaking changes into production."
"One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."
"It is vital to our business to have quick and robust builds, and TeamCity is helping us to keep everything tidy and under control."
"I have used Jenkins, TFS, Cruise Control .net, and GO, and I switched from using Cruise Control .net as TeamCity is easier to use and displays important information very well, with great support for integrating to other products from JetBrains and other vendors such as Atlassian, JIRA, and Windows AD."
 

Cons

"The UI of split.io can be improved."
"Initially, I had difficulty finding analytics and understanding setup."
"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."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
"Occasionally issues deploying software using the tool due to configuration issues within the tool (mostly around powershell configuration)."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
"The UI for this solution could be improved. New users don't find it easy to navigate; they need some level of training to understand the ins and the outs."
"I need some more graphical design."
"However, in TeamCity, the whole build is like a whole block, and there is no way to stop."
"For our system, it wasn't scalable due to storage issues."
 

Pricing and Cost Advice

Information not available
"The licensing is on an annual basis."
"Start with the free tier for a few build configs and see how it works for you, then according to your scale find the enterprise license which fits you the most."
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
No data available
Financial Services Firm
17%
Computer Software Company
10%
Comms Service Provider
8%
Manufacturing Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business7
Large Enterprise4
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise4
Large Enterprise15
 

Questions from the Community

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...
What is your experience regarding pricing and costs for TeamCity?
Compared to new technologies, TeamCity is more expensive and is an older tool compared to tools like GitLab.
What needs improvement with TeamCity?
TeamCity's user interface could be improved; specifically, the tree structure on the homepage is not clear, making it difficult to search for projects. Moreover, there are some limitations related ...
What is your primary use case for TeamCity?
We use TeamCity for build configuration and pipeline creation, as well as for automation purposes. We provide working pipelines for different teams internally.
 

Comparisons

 

Overview

 

Sample Customers

Information Not Available
Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
Find out what your peers are saying about Split vs. TeamCity and other solutions. Updated: August 2026.
909,725 professionals have used our research since 2012.