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

AWS CodeBuild vs TeamCity comparison

 

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

AWS CodeBuild
Ranking in Build Automation
9th
Average Rating
8.2
Reviews Sentiment
7.7
Number of Reviews
11
Ranking in other categories
No ranking in other categories
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
 

Mindshare comparison

As of June 2025, in the Build Automation category, the mindshare of AWS CodeBuild is 1.2%, down from 1.5% compared to the previous year. The mindshare of TeamCity is 7.4%, up from 6.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

Munisaiteja Narravula - PeerSpot reviewer
Automated task handling with reliable logging but requires accurate environment setup
One of the main challenges is that if the environment is not set up properly, it will result in issues such as image errors. It's crucial to have accurate environment configurations to avoid such problems. During the build stage, we often face time issues that cause delays, which can be troublesome.
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…

Quotes from Members

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

Pros

"The integration is a good feature."
"The tool is used to build and test code. I find its biggest advantages are elasticity and reliability. We can easily assign as many computing resources as needed to build our code, which is much simpler than traditional methods that require server upgrades. It's a serverless tool, so it's very flexible and elastic."
"The integration with other AWS services has streamlined our workflow."
"The most important thing is that it's self-contained in an AWS account, and it's all linked to the customer's AWS account."
"One of the main features I value in CodeBuild compared to previous experiences, like using Jenkins, is its ability to handle tasks automatically with AWS, requiring only proper setup of the check file."
"It works seamlessly with AWS Elastic Container Registry (ECR)."
"The integration is a good feature."
"A valuable feature is the support for third-party repositories such as Bitbucket, GitLab, or GitHub."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"It's easy to move to a new release because of templates and meta-runners, and agent pooling."
"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."
"TeamCity is more structured and user-friendly than other vendors."
"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."
"One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."
"TeamCity is a very user-friendly tool."
"TeamCity is very useful due to the fact that it has a strong plug-in system."
 

Cons

"We had integration issues with a tool called Octopus Deploy while using CodeBuild. AWS support helped us resolve it, however, it could be better."
"Notifications could be added, or SNS integration could be included so that notifications can be received on every build, whether the build fails or succeeds."
"For improvement, I'd suggest more build instance-type options. There's a big jump from 15 gigabytes of RAM to 150, and I'd like something in between as the larger option is too expensive for our needs."
"While working on building images for multiple applications within a single script, I encountered an issue where looping functionality was not supported as expected."
"They can further improve the integration of the Bitbucket for CodeBuild."
"Multiple clients have faced issues with pricing. After migrating from Azure to EC2, they were unexpectedly charged 100,000 rupees because the pricing details were not clearly visible."
"There is no persistent storage or preservation of workspace between the builds."
"The front-end interface and the management are somewhat challenging, and there's a lot of space for improvement."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
"I would like to see an improvement where TeamCity alerts us via email or another medium if there are discrepancies between the code in the staging environment and what has been deployed to production, such as missing updates."
"The integration between other solutions and TeamCity could be smoother."
"REST API support lacks many features in customization of builds, jobs, and settings."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
"If there was more documentation that was easier to locate, it would be helpful for users."
"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."
 

Pricing and Cost Advice

"Despite the cost, it is worth the investment."
"AWS CodeBuild is free. We only pay for our code's compute resources during the build process. For example, if our code takes ten minutes to build, we only pay for those ten minutes of computing time. CodeDeploy and CodePipeline are free because they're serverless and don't require computing resources. CodeCommit has minimal costs for storing code."
"We pay a monthly licensing fee."
"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."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
859,579 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
18%
Financial Services Firm
13%
Media Company
10%
Manufacturing Company
10%
Financial Services Firm
24%
Computer Software Company
18%
Comms Service Provider
6%
Manufacturing Company
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about AWS CodeBuild?
It works seamlessly with AWS Elastic Container Registry (ECR).
What is your experience regarding pricing and costs for AWS CodeBuild?
Issues with pricing have been mentioned, especially for new clients who might not realize the cost implications initially, such as leaving servers on for too long and incurring unexpectedly high bi...
What needs improvement with AWS CodeBuild?
There is room for improvement in making AWS CodeBuild available on Windows servers in the Mumbai region. Multiple clients have faced issues with pricing. After migrating from Azure ( /products/micr...
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 different technologies.
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 ...
 

Comparisons

 

Also Known As

CodeBuild
No data available
 

Overview

 

Sample Customers

Expedia, Intuit, Royal Dutch Shell, Brooks Brothers
Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
Find out what your peers are saying about AWS CodeBuild vs. TeamCity and other solutions. Updated: June 2025.
859,579 professionals have used our research since 2012.