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

CircleCI vs TeamCity vs Travis CI 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:
 

Mindshare comparison

As of October 2025, in the Build Automation category, the mindshare of CircleCI is 3.3%, down from 3.5% compared to the previous year. The mindshare of TeamCity is 6.8%, up from 6.5% compared to the previous year. The mindshare of Travis CI is 1.3%, up from 1.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Market Share Distribution
ProductMarket Share (%)
TeamCity6.8%
CircleCI3.3%
Travis CI1.3%
Other88.6%
Build Automation
 

Featured Reviews

reviewer0972521 - PeerSpot reviewer
Unhelpful support, unclear billing, and has offers ability to track usage
We've had occasional connectivity issues with cloud resources and build failure due to its own internal system setup and environment. That costs us credits. Support engineers do not thoroughly read and understand issues when emailing them. They reply to me with a totally different context about the problem. Just yesterday, my web applications failed to 'yarn build' after I downgraded the resource class from extr-large to large. I contacted support and got no reply. Billing is a mess. There is duplicate information in the bill downloaded from their website and when I asked for a consolidated bill, they just answered that they didn't have it. There is no transparency on how many billed minutes and credits I spent each day both on their website and the monthly bill which makes it difficult to understand when the monthly bill contains many refill item charges. It is difficult or impossible to track usage and burndown of my subscription and to gain total outstanding refill amounts on a daily basis. Their website doesn't provide sufficient information on credits allocated/calculated for my extra-large resource class.
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…
Pravar Agrawal - PeerSpot reviewer
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

"Enables us to detect exactly which build failed and why, and to push multiple builds to our production environment at a very fast rate."
"The automation workflow in CircleCI related to third-party applications is very good and allows standardization of applications."
"The ability to automate the build process in a seamless way and run workflows effortlessly. It supports parallel builds so it can scale well. Also, it covers the basics of any build and integration tool, including email notifications (especially when tests are fixed), project insights, etc."
"Some of the most valuable features include container-based builds, integration with Bit Bucket and being able to store artifacts."
"It's a stable product."
"The solution offers continuous integration and continuous delivery."
"It is very easy to use, and its speed is impressive, allowing the code to be ready for production in seconds."
"TeamCity is very useful due to the fact that it has a strong plug-in system."
"It's easy to move to a new release because of templates and meta-runners, and agent pooling."
"TeamCity is a very user-friendly tool."
"Time to deployment has been reduced in situations where we want to deploy to production or deploy breaking changes."
"I have not yet implemented the remote build feature, but this will be a big plus. We want to be able to build legacy products on a build agent without developers needing to have obsolete tool sets installed on their local PC."
"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."
"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."
"The only thing I like about Travis CI is that you have a YAML file to define a Travis flow."
 

Cons

"Integration with Microsoft Azure is one area for improvement. Azure is growing in its user base, and supports various cloud infrastructure components such as Service Fabric, App Service, etc. Some of Azure’s deployment models (like Kudu) require a steep learning curve, but if CircleCI would come up with such features (deployment to App Service) out of the box, it would be amazing."
"There needs to be some improvement in the user interface of CircleCI."
"Billing is a mess."
"The solution’s pricing could be better."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
"REST API support lacks many features in customization of builds, jobs, and settings."
"The UI for this solution could be improved. New users don't find it easy to navigate. The need some level of training to understand the ins and the outs."
"If there was more documentation that was easier to locate, it would be helpful for users."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
"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."
"I need some more graphical design."
"The interface is very basic and not user-friendly; it feels like it was stuck in 2010."
 

Pricing and Cost Advice

"The price of CircleCI could be less expensive."
"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.
869,202 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
Computer Software Company
19%
Financial Services Firm
9%
Comms Service Provider
9%
Manufacturing Company
7%
Financial Services Firm
20%
Computer Software Company
18%
Comms Service Provider
8%
Government
5%
No data available
 

Company Size

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

Questions from the Community

What do you like most about CircleCI?
The solution offers continuous integration and continuous delivery.
What is your experience regarding pricing and costs for CircleCI?
Beware of skyrocketing bills as CircleCI does not provide transparency into how they charge refills. Their monthly bi...
What needs improvement with CircleCI?
We've had occasional connectivity issues with cloud resources and build failure due to its own internal system setup ...
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 diff...
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...
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 ...
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 wor...
 

Comparisons

 

Overview

 

Sample Customers

Shopify, Zenefits, Concur Technologies, CyberAgent
Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
Facebook, Heroku, Mozilla, Zendesk, twitter, Rails
Find out what your peers are saying about GitLab, Google, GitHub and others in Build Automation. Updated: September 2025.
869,202 professionals have used our research since 2012.