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
8th
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 November 2026, in the Build Automation category, the mindshare of TeamCity is 4.9%, down from 6.8% compared to the previous year. The mindshare of Travis CI is 3.7%, up from 1.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
TeamCity4.9%
Travis CI3.7%
Other91.4%
Build Automation
 

Featured Reviews

Almoeeni Fazal - PeerSpot reviewer
Python Django developer at Cielo WiGle Inc.
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…
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

"When we discovered TeamCity, it totally speeded up our workflow."
"It is very easy to use, and its speed is impressive, allowing the code to be ready for production in seconds."
"I spend less time scripting to get a build working and more time configuring TeamCity through its web-based front end."
"I have used Jenkins, TFS, Cruise Control .net, and GO, and I switched from using Cruise Control .net as TeamCity is easier to use and displays important information very well, with great support for integrating to other products from JetBrains and other vendors such as Atlassian, JIRA, and Windows AD."
"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."
"VCS Trigger: Provides excellent source control support."
"TeamCity's GUI is nice."
"Do it! Very easy to use and very stable."
"The only thing I like about Travis CI is that you have a YAML file to define a Travis flow."
 

Cons

"However, in TeamCity, the whole build is like a whole block, and there is no way to stop."
"It'd be great to see future built-in support for Octopus Deploy."
"The UI could be more structured, as it is so customisable it is quite easy to get lost around the screens."
"For our system, it wasn't scalable due to storage issues."
"We would like to see better integration with other version controls, since we encountered difficulty when this was first attempted."
"The integration between other solutions and TeamCity could be smoother."
"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."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
"The interface is very basic and not user-friendly; it feels like it was stuck in 2010."
 

Pricing and Cost Advice

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

Top Industries

By visitors reading reviews
Financial Services Firm
13%
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.
920,769 professionals have used our research since 2012.