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

Incredibuild 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

Incredibuild
Ranking in Build Automation
26th
Average Rating
8.0
Reviews Sentiment
5.1
Number of Reviews
1
Ranking in other categories
No ranking in other categories
TeamCity
Ranking in Build Automation
10th
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 June 2026, in the Build Automation category, the mindshare of Incredibuild is 1.4%, up from 0.7% compared to the previous year. The mindshare of TeamCity is 5.2%, down from 7.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
TeamCity5.2%
Incredibuild1.4%
Other93.4%
Build Automation
 

Featured Reviews

ZM
DevOps Team Leader at Elbit Systems Ltd
Saves time for developers, which saves money for the company
We are using the Incredibuild agent to run multiple processes on all available cores. This is the improvement that we did. Instead of the machine's core doing task after task, it is now running on multiple machines. In my working environment, it is saving time for all our developers in regards to the time consumption of the builds. My team has four people who manage and interact with Incredibuild as a product.
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

"For each build that runs where I need to generate a code, it takes around half an hour instead of an hour and a half."
"It is saving time for developers, which is saving money for the company."
"The setup is extremely straightforward."
"There is much online documentation for TeamCity, with certain learning materials such as videos."
"It's easy to move to a new release because of templates and meta-runners, and agent pooling."
"One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."
"Do it! Very easy to use and very stable."
"I spend less time scripting to get a build working and more time configuring TeamCity through its web-based front end."
"The most valuable aspect of the solution is its easy configuration, and it also has multiple plugins that can be used especially for building .net applications."
"When we discovered TeamCity, it totally speeded up our workflow."
 

Cons

"Stability could be improved. I don't know the reason for the instability because there are no logs that help me to understand the problem."
"Features I would like to see in TeamCity: Allow for shared resource locks across multiple build configurations (i.e. deploy then run integration tests against the same environment)."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
"However, in TeamCity, the whole build is like a whole block, and there is no way to stop."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
"I would like to see an improvement where TeamCity alerts us via email or another medium if there are discrepancies between the code in the staging environment and what has been deployed to production, such as missing updates."
"There have been times when making copies of a project has caused major stability issues, especially when you have nested project structure based off of different build configuration templates."
"The integration between other solutions and TeamCity could be smoother."
"More build runners and more options are needed, although I have no worries they keep improving."
 

Pricing and Cost Advice

"Its pricing and licensing are annoying. Every year, I need to renew. If I miss the deadline date, all my processes will stop working. So, I would prefer that I wouldn't need to renew every year, instead have another solution for it. Or, if we could have an enterprise license agreement with the company, then the development team wouldn't need to spend time renewing licenses."
"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.
899,258 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Financial Services Firm
20%
Computer Software Company
11%
Comms Service Provider
8%
Marketing Services Firm
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise4
Large Enterprise15
 

Questions from the Community

Ask a question
Earn 20 points
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

Over 2,000 companies worldwide across industries inluding Epic Games, Microsoft, Playstation, Nintendo, Samsung, GM, Intel, CitiGroup, Qualcomm, Boeing, Motorola, Qt, and more accelerate their development and enhance their devs’ productivity with Incredibuild.
Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
Find out what your peers are saying about Jenkins, GitLab, GitHub and others in Build Automation. Updated: May 2026.
899,258 professionals have used our research since 2012.