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

Depot 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

Depot
Ranking in Build Automation
22nd
Average Rating
7.4
Reviews Sentiment
5.0
Number of Reviews
3
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 Depot is 0.5%. 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%
Depot0.5%
Other94.6%
Build Automation
 

Featured Reviews

RS
Senior Technical Lead at HCLSoftware
Managing complex code branches has been challenging but has improved team collaboration
Depot needs improvement as it was stable but also very slow. Depot's slow speed arises when we perform different integrations. On the positive side, it provides mono-repo scalability, meaning it can handle multiple users at any given time without crashing, which is a strong point. Depot should be improved for remote work because it functions poorly in that regard. Depot's branching style is also poor and could be improved. There is a steep learning curve that makes it difficult for people who previously worked on decentralized systems to adapt. It would be beneficial if Depot could become more similar to Git.
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

"Depot has positively impacted my organization in an awesome way, and the fact that I can save time gives me the possibility to have more clients during the day, saving at least 20% each day because of Depot."
"Depot has positively impacted my organization by helping us manage our code better where multiple developers are working on the system."
"Depot has positively impacted our organization by ensuring that everything works fully, which makes other clients really happy."
"There is much online documentation for TeamCity, with certain learning materials such as videos."
"TeamCity is a very user-friendly tool."
"TeamCity allows us to have self-sufficient development teams that can create their own builds and deployments."
"With Teamcity, our build/packaging process and the ensuing deployment via Octopus Deploy takes less than half an hour."
"Do it! Very easy to use and very stable."
"It is very easy to use, and its speed is impressive, allowing the code to be ready for production in seconds."
"The integration is a valuable feature."
"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."
 

Cons

"Depot is a useful tool and there is space for improvement, but I can't figure out what can be done, which is why I chose eight out of ten."
"Depot needs improvement as it was stable but also very slow."
"However, they need improvement with older servers due to storage space issues, which prevents me from giving a perfect score of ten."
"If there was more documentation that was easier to locate, it would be helpful for users."
"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."
"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."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
"More build runners and more options are needed, although I have no worries they keep improving."
"Occasionally issues deploying software using the tool due to configuration issues within the tool (mostly around powershell configuration)."
"However, in TeamCity, the whole build is like a whole block, and there is no way to stop."
"Deployment functions need work."
 

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
Construction Company
42%
Manufacturing Company
13%
Comms Service Provider
9%
University
5%
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
No data available
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise4
Large Enterprise15
 

Questions from the Community

What is your experience regarding pricing and costs for Depot?
Regarding my experience with pricing, setup cost, and licensing for Depot, I have faced many challenges with cost optimization. We need to manage what services we can use and optimize the cost, whi...
What needs improvement with Depot?
Depot needs improvement as it was stable but also very slow. Depot's slow speed arises when we perform different integrations. On the positive side, it provides mono-repo scalability, meaning it ca...
What is your primary use case for Depot?
My main use case for Depot was for storing production code and deploying it through pipelines. A specific example of how I used Depot for storing production code and deploying through pipelines inv...
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 Depot vs. TeamCity and other solutions. Updated: August 2026.
909,725 professionals have used our research since 2012.