Try our new research platform with insights from 80,000+ expert users

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
24th
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
11th
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 November 2025, in the Build Automation category, the mindshare of Incredibuild is 1.2%, up from 0.7% compared to the previous year. The mindshare of TeamCity is 6.7%, up from 6.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Market Share Distribution
ProductMarket Share (%)
TeamCity6.7%
Incredibuild1.2%
Other92.1%
Build Automation
 

Featured Reviews

ZM
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.
Almoeeni Fazal - PeerSpot reviewer
Impressive pipeline efficiency with helpful support and a fairly straightforward setup
We use TeamCity for the CI/CD pipeline. It is used for deploying code from the desktop to the production environment. We push our code to GitHub, which then creates a pipeline to a server using AWS, deploying automatically without errors or conflicts in GitHub branches.  We also use TeamCity's…

Quotes from Members

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

Pros

"It is saving time for developers, which is saving money for the company."
"TeamCity's GUI is nice."
"Using TeamCity and emailing everyone on fail is one way to emphasize the importance of testing code and showing management why taking the time to test actually does saves time from having to fix bugs on the other end."
"It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack."
"It's easy to move to a new release because of templates and meta-runners, and agent pooling."
"I have not yet implemented the remote build feature, but this will be a big plus. We want to be able to build legacy products on a build agent without developers needing to have obsolete tool sets installed on their local PC."
"TeamCity is very useful due to the fact that it has a strong plug-in system."
"TeamCity is more structured and user-friendly than other vendors."
"The integration is a valuable feature."
 

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."
"If there was more documentation that was easier to locate, it would be helpful for users."
"Their online documentation is fairly extensive, but sometimes you can end up navigating in circles to find answers. I would like them (or partner with someone)​ to provide training classes to help newcomers get things up and running more quickly."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
"If TeamCity could create more out of the box solutions to make it more user friendly and create more use cases, that would be ideal."
 

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.
872,846 professionals have used our research since 2012.
 

Comparison Review

it_user184734 - PeerSpot reviewer
Jan 22, 2015
I generally find TeamCity a lot more intuitive than Jenkins.
Moving to TeamCity from Jenkins At work, we’re slowly migrating from Jenkins to TeamCity in the hope of ending some of our recurring problems with continuous integration. My use of Jenkins prior to this job has been almost strictly on a personal basis, although I pretty much only use Travis…
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Computer Software Company
15%
Manufacturing Company
12%
Retailer
8%
Financial Services Firm
21%
Computer Software Company
17%
Comms Service Provider
9%
Performing Arts
5%
 

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 do you like most about TeamCity?
One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies.
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 ...
 

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 GitLab, Google, GitHub and others in Build Automation. Updated: November 2025.
872,846 professionals have used our research since 2012.