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

TeamCity vs Travis CI comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 5, 2025

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

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
Travis CI
Ranking in Build Automation
19th
Average Rating
6.0
Reviews Sentiment
3.1
Number of Reviews
2
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of October 2026, in the Build Automation category, the mindshare of TeamCity is 4.9%, down from 6.9% compared to the previous year. The mindshare of Travis CI is 3.6%, up from 1.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
TeamCity4.9%
Travis CI3.6%
Other91.5%
Build Automation
 

Featured Reviews

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.
Pravar Agrawal - PeerSpot reviewer
Senior SRE at a tech vendor with 10,001+ employees
YAML-based configuration and simple deployment but user interface needs modernizing
Travis CI is an okay tool, and I am forced to use it as part of my job. I don't maintain it; it is running somewhere else, and I don't have control over it. The interface is very basic and not user-friendly; it feels like it was stuck in 2010. It is very basic and designed for lightweight CI work, and it cannot handle heavy CI. You cannot do branched flows, and you will have to write shell scripts to send calls here and there. The pipelines are not as detailed as some other CI/CD tools. If Travis is down, you don't have any control over it and need to reach out to their customer support.

Quotes from Members

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

Pros

"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."
"TeamCity is more structured and user-friendly than other vendors."
"It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack."
"TeamCity is very stable, is easy to set up and maintain, and once everything is configured there is almost zero time needed to maintain it."
"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."
"It's easy to move to a new release because of templates and meta-runners, and agent pooling."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"When we discovered TeamCity, it totally speeded up our workflow."
"The only thing I like about Travis CI is that you have a YAML file to define a Travis flow."
 

Cons

"We would like to see better integration with other version controls, since we encountered difficulty when this was first attempted."
"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."
"However, in TeamCity, the whole build is like a whole block, and there is no way to stop."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
"We've called TeamCity tech support. Unfortunately, all their tech support is based in Europe, so we end up with such a big time crunch that I now need to have one person in the US."
"If there was more documentation that was easier to locate, it would be helpful for users."
"More build runners and more options are needed, although I have no worries they keep improving."
"The interface is very basic and not user-friendly; it feels like it was stuck in 2010."
 

Pricing and Cost Advice

"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."
Information not available
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
917,433 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Computer Software Company
10%
Comms Service Provider
9%
Manufacturing Company
9%
No data available
 

Company Size

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

Questions from the Community

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

Comparisons

 

Overview

 

Sample Customers

Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
Facebook, Heroku, Mozilla, Zendesk, twitter, Rails
Find out what your peers are saying about Jenkins, GitHub, GitLab and others in Build Automation. Updated: October 2026.
917,433 professionals have used our research since 2012.