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

"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."
"TeamCity allows us to have self-sufficient development teams that can create their own builds and deployments."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"VCS Trigger: Provides excellent source control support."
"It's easy to move to a new release because of templates and meta-runners, and agent pooling."
"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."
"Continuous integration has reduced build failures and highlighted issues sooner."
"With Teamcity, our build/packaging process and the ensuing deployment via Octopus Deploy takes less than half an hour."
"The only thing I like about Travis CI is that you have a YAML file to define a Travis flow."
 

Cons

"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."
"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."
"Net deployment needs improvement. Also, I'd like to see more NuGet/Octopus style features and Azure stuff."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
"This product lacks real reporting for all the information it captures; we should be able to create reports or dashboards for management."
"Occasionally issues deploying software using the tool due to configuration issues within the tool (mostly around powershell configuration)."
"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.
913,806 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Computer Software Company
10%
Comms Service Provider
9%
Manufacturing Company
8%
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.
What is your experience regarding pricing and costs for Travis CI?
I'm not too sure about the pricing of Travis or how the agreement works.
What needs improvement with Travis CI?
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...
What is your primary use case for Travis CI?
Travis CI is mainly used to run integration tests as part of the deployment, which I do on Kubernetes. The Travis workflows are integrated with any changes in my code. It will have different jobs, ...
 

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: September 2026.
913,806 professionals have used our research since 2012.