CircleCI vs. TeamCity

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
CircleCI
Score 8.7 out of 10
N/A
CircleCI is a software delivery engine from the company of the same name in San Francisco, that helps teams ship software faster, offering their platform for Continuous Integration and Continuous Delivery (CI/CD). Ultimately, the solution helps to map every source of change for software teams, so they can accelerate innovation and growth.
$0
per month
TeamCity
Score 8.1 out of 10
N/A
TeamCity is a continuous integration server from Czeck company JetBrains.N/A
Pricing
CircleCITeamCity
Editions & Modules
Free
$0
per month
Performance
$30
per month
Server
$35
per month
Scale
Custom Pricing
No answers on this topic
Offerings
Pricing Offerings
CircleCITeamCity
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
CircleCITeamCity
Considered Both Products
CircleCI
Chose CircleCI
Circle was the first CI with simple setup, great documentation, and tight integration with GitHub. Using Jenkins was too much maintenance and overhead, TeamCity was limited in how we could customize it and run concurrent builds, TravisCI was not available for private repos when …
TeamCity
Chose TeamCity
This application is easy to install and deploy at site than most of the similar solutions in market. Easy user interface is one of the reason it can be installed. However each software have its good points and bad points. Study your organizations case and then only choose …
Chose TeamCity
TeamCity by far has the best interface TeamCity still supported our old SubVersion reports as well.
Top Pros
Top Cons
Best Alternatives
CircleCITeamCity
Small Businesses
GitLab
GitLab
Score 8.8 out of 10
GitLab
GitLab
Score 8.8 out of 10
Medium-sized Companies
GitLab
GitLab
Score 8.8 out of 10
GitLab
GitLab
Score 8.8 out of 10
Enterprises
GitLab
GitLab
Score 8.8 out of 10
GitLab
GitLab
Score 8.8 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
CircleCITeamCity
Likelihood to Recommend
8.0
(26 ratings)
10.0
(18 ratings)
Usability
10.0
(1 ratings)
-
(0 ratings)
Performance
7.8
(3 ratings)
9.3
(2 ratings)
Support Rating
6.9
(6 ratings)
-
(0 ratings)
User Testimonials
CircleCITeamCity
Likelihood to Recommend
CircleCI
CircleCI is perfect for a CI/CD pipeline for an app using a standard build process. It'll take more work for a complex build process, but should still be up to the task unless you need a lot of integrations with other tools. If you have a big team and can spare someone to focus full time on just the CI/CD tools, maybe something like Jenkins is better, but if you're just looking to get your app built, tested, and delivered without a huge amount of effort, CircleCI is probably your preferred tool.
Read full review
JetBrains
TeamCity is very quick and straightforward to get up and running. A new server and a handful of agents could be brought online in easily under an hour. The professional tier is completely free, full-featured, and offers a huge amount of growth potential. TeamCity does exceptionally well in a small-scale business or enterprise setting.
Read full review
Pros
CircleCI
  • Multiple builds can be run at the same time in parallel.
  • The CircleCI web interface (UI/UX) is very easy to understand and use.
  • Easy Configuration to learn and use. Just a single configuration YAML file.
  • Many integrations. We use the GItHub, Slack, and DataDog integrations.
Read full review
JetBrains
  • TeamCity provides a great integration with git, especially Bitbucket.
  • When a new code release (build) fails TeamCity has a great tool for investigation and troubleshooting.
  • TeamCity provides a user-friendly interface. While some technical knowledge is required to use TeamCity, the design helps simply things.
Read full review
Cons
CircleCI
  • The "phases" their config file uses to separate out options seem very arbitrary and are not very helpful for organizing your config file
  • No way that I know of to configure which version of MongoDB you use. You have to write your own shell script to download and start MongoDB if you want a specific version.
  • Hard to access build artifacts in the UI
Read full review
JetBrains
  • The customization is still fairly complex and is best managed by a dev support team. There is great flexibility, but with flexibility comes responsibility. It isn't always obvious to a developer how to make simple customizations.
  • Sometimes the process for dealing with errors in the process isn't obvious. Some paths to rerunning steps redo dependencies unnecessarily while other paths that don't are less obvious.
Read full review
Usability
CircleCI
CircleCI interface is awesome in that it is relatively modern and makes it clear exactly which parts of the engineering lifecycle you are in
Read full review
JetBrains
No answers on this topic
Performance
CircleCI
It's pretty snappy, even with using workflows with multiple steps and different docker images. I've seen builds take a long time if it's really involved, but from what I can tell, it's still at least on par if not faster than other build tools.
Read full review
JetBrains
TeamCity runs really well, even when sharing a small instance with other applications. The user interface adequately conveys important information without being overly bloated, and it is snappy. There isn't any significant overhead to build agents or unit test runners that we have measured.
Read full review
Support Rating
CircleCI
Unless you have a reasonably large account, you're going to be mainly stuck reading their documentation. Which has improved somewhat over the years but is still extremely limited compared to a platform like Digital Ocean who invested in the documentation and a community to ensure it's kept up to date. If you can't find your answer there, you can be stuck.
Read full review
JetBrains
No answers on this topic
Alternatives Considered
CircleCI
Circle was the first CI with simple setup, great documentation, and tight integration with GitHub. Using Jenkins was too much maintenance and overhead, TeamCity was limited in how we could customize it and run concurrent builds, TravisCI was not available for private repos when we switched.
Read full review
JetBrains
TeamCity is a great on-premise Continuous Integration tool. Visual Studio Team Services (VSTS) is a hosted SAAS application in Microsoft's Cloud. VSTS is a Source Code Repository, Build and Release System, and Agile Project Management Platform - whereas TeamCity is a Build and Release System only. TeamCity's interface is easier to use than VSTS, and neither have a great deployment pipeline solution. But VSTS's natural integration with Microsoft products, Microsoft's Cloud, Integration with Azure Active Directory, and free, private, Source Code repository - offer additional features and capabilities not available with Team City alone.
Read full review
Return on Investment
CircleCI
  • It has eased the burden of standardizing our testing and deployment, making onboarding new developers much faster, and having to fix deployment mistakes much less often.
  • It allows us to focus our process around the GitHub workflow, ignoring the details of whatever environment the thing we're working on is actually hosted in. This saves us time.
Read full review
JetBrains
  • TeamCity has greatly improved team efficiency by streamlining our production and pre-production pipelines. We moved to TeamCity after seeing other teams have more success with it than we had with other tools.
  • TeamCity has helped the reliability of our product by easily allowing us to integrate unit testing, as well as full integration testing. This was not possible with other tools given our corporate firewall.
  • TeamCity's ability to include Docker containers in the pipeline steps has been crucial in improving our efficiency and reliability.
Read full review
ScreenShots