No more typing reviews! Try our Samantha, our new voice AI agent.

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
6.4
Number of Reviews
13
Ranking in other categories
No ranking in other categories
TeamCity
Ranking in Build Automation
10th
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 April 2026, in the Build Automation category, the mindshare of AWS CodeBuild is 2.4%, up from 1.2% compared to the previous year. The mindshare of TeamCity is 5.8%, down from 7.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
AWS CodeBuild2.4%
TeamCity5.8%
Other91.8%
Build Automation
 

Featured Reviews

SomdipRoy - PeerSpot reviewer
Solution Architect at Skillnetinc
Has enabled automated deployments through continuous integration and supports multi-environment delivery
My recommendation for AWS CodeBuild to make it better for the next release would be something within AWS CodeBuild which can support the repository functions as well. It may not be as powerful as GitHub Actions, but it provides a very competitive price compared to GitHub Actions. GitHub Actions, if you want to use the YML CI/CD pipeline, gives a free tier of around three thousand hours per month. AWS CodeBuild is a little more expensive than that. However, if it supports the repository function as well along with it, then it will be a complete package. Everything would be in AWS, including the code versioning, code commit to the code infrastructure, to the code database, to the networking, and how the applications are accessed. Everything would be in one place, which would be very helpful. I believe AWS CodeBuild is a bit expensive because GitHub provides around three thousand minutes free, plus it has the free repository function as well. At the enterprise level, it charges maybe around nineteen dollars per user, though I do not remember exactly. In terms of AWS CodeBuild, I believe it is a bit expensive because it is providing only the deployment features. It is not providing the repository. In that comparison, I would say it is a little bit expensive.
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.

Quotes from Members

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

Pros

"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."
"The initial setup of CodeBuild is easy."
"AWS CodeBuild reduces wait time and optimizes workflows."
"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 solution provides good integrations."
"It works seamlessly with AWS Elastic Container Registry (ECR)."
"CodeBuild supports various platforms and coding."
"CodeBuild supports various platforms and coding, which offers an advantage."
"Continuous integration has reduced build failures and highlighted issues sooner."
"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."
"TeamCity is very useful due to the fact that it has a strong plug-in system."
"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 allows us to have self-sufficient development teams that can create their own builds and deployments."
"TeamCity is more structured and user-friendly than other vendors."
"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."
"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."
 

Cons

"While working on building images for multiple applications within a single script, I encountered an issue where looping functionality was not supported as expected."
"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."
"The front-end interface and the management are somewhat challenging, and there's a lot of space for improvement."
"We had integration issues with a tool called Octopus Deploy while using CodeBuild."
"They can further improve the integration of the Bitbucket for CodeBuild."
"One of the main challenges is that if the environment is not set up properly, it will result in issues such as image errors."
"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."
"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."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
"It'd be great to see future built-in support for Octopus Deploy."
"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."
"Their online documentation is fairly extensive, but sometimes you can end up navigating in circles to find answers."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
"Setting up build configurations involves too many steps, as the process is too much broken down."
 

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

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Media Company
10%
Manufacturing Company
10%
Computer Software Company
8%
Financial Services Firm
18%
Computer Software Company
12%
Comms Service Provider
9%
Marketing Services Firm
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise5
Large Enterprise2
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise4
Large Enterprise15
 

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?
The cost structure is affordable for most builds except macOS servers. Standard builds can utilize AWS EC2 servers for background operations. However, macOS or iOS builds require physical servers m...
What needs improvement with AWS CodeBuild?
My recommendation for AWS CodeBuild to make it better for the next release would be something within AWS CodeBuild which can support the repository functions as well. It may not be as powerful as G...
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: April 2026.
885,837 professionals have used our research since 2012.