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

Harness 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

Harness
Ranking in Build Automation
10th
Average Rating
7.8
Reviews Sentiment
7.9
Number of Reviews
4
Ranking in other categories
Static Application Security Testing (SAST) (29th), Cloud Cost Management (12th)
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 July 2025, in the Build Automation category, the mindshare of Harness is 7.5%, up from 4.3% compared to the previous year. The mindshare of TeamCity is 7.3%, up from 6.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

Linwei Yuan - PeerSpot reviewer
Streamline microservices deployment with integrated execution pipelines and comprehensive monitoring
Harness integrates all functions like execution pipelines, environment checks, and log monitoring in one place. It is very convenient since we have many microservices, so having one platform for all of them is beneficial. The dashboard allows me to monitor all core services' deployment status in one place, making it easier to find bugs and check logs.
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

"The features of Harness are valuable, supporting rolling deployments, basic deployments, and blue-green deployments with zero downtime."
"Harness starts integrating with organizations, making everything automated without the need for manual interruption."
"Harness integrates all functions like execution pipelines, environment checks, and log monitoring in one place, making it convenient."
"It's a highly customizable DevOps tool."
"Harness integrates all functions like execution pipelines, environment checks, and log monitoring in one place."
"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."
"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."
"The integration is a valuable feature."
"It's easy to move to a new release because of templates and meta-runners, and agent pooling."
"Time to deployment has been reduced in situations where we want to deploy to production or deploy breaking changes."
"Good integration with IDE and JetBrains products."
"The most valuable aspect of the solution is its easy configuration. It also has multiple plugins that can be used especially for building .net applications."
 

Cons

"I prefer the previous less compact UI version of Harness, which showed more details on the screen."
"When integrating Harness with more than twenty applications in one place, it becomes less stable, causing improvements to be necessary."
"There's also room for improvement in debugging pipeline issues, which can sometimes become complex."
"Even with automation, there's a requirement for manual change requests for approvals."
"When deploying multiple components to multiple environments, like production and BCP, failures sometimes occur. Improvements are needed when deploying one component to one environment."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
"REST API support lacks many features in customization of builds, jobs, and settings."
"The integration between other solutions and TeamCity could be smoother."
"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."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
"I need some more graphical design."
"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."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
 

Pricing and Cost Advice

Information not available
"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."
"The licensing is on an annual basis."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
862,514 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
32%
Computer Software Company
11%
Government
7%
Retailer
5%
Financial Services Firm
24%
Computer Software Company
18%
Comms Service Provider
7%
Manufacturing Company
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What do you like most about Harness?
It's a highly customizable DevOps tool.
What needs improvement with Harness?
When deploying multiple components to multiple environments, like production and BCP, failures sometimes occur. Improvements are needed when deploying one component to one environment.
What is your primary use case for Harness?
Our primary use case for Harness ( /products/harness-reviews ) is as a deployment tool. Although I am not a DevOps engineer, my team uses Harness ( /products/harness-reviews ) for deployment purpos...
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

 

Also Known As

Armory
No data available
 

Overview

 

Sample Customers

Linedata, Openbank, Home Depot, Advanced
Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
Find out what your peers are saying about Harness vs. TeamCity and other solutions. Updated: July 2025.
862,514 professionals have used our research since 2012.