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

AWS CodeBuild vs TeamCity 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

AWS CodeBuild
Ranking in Build Automation
10th
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
8th
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 November 2026, in the Build Automation category, the mindshare of AWS CodeBuild is 2.3%, up from 1.8% compared to the previous year. The mindshare of TeamCity is 4.9%, down from 6.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
TeamCity4.9%
AWS CodeBuild2.3%
Other92.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.
Almoeeni Fazal - PeerSpot reviewer
Python Django developer at Cielo WiGle Inc.
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 most important thing is that it's self-contained in an AWS account, and it's all linked to the customer's AWS account."
"The integration with other AWS services has streamlined our workflow."
"CodeBuild supports various platforms and coding, which offers an advantage."
"A valuable feature is the support for third-party repositories such as Bitbucket, GitLab, or GitHub."
"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 initial setup of CodeBuild is easy."
"AWS CodeBuild's support for popular languages and tools has enhanced my productivity; it supports the three most popular stacks that are in the world: the Python stack, the Node.js stack or framework, and the Java framework, along with other technology stacks such as Ruby on Rails."
"Scalability is a great feature with AWS CodeBuild, because after deploying applications the service automatically scales up and down according to our AWS needs using load balancing, which makes managing applications much easier without significant interruptions."
"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."
"It is very easy to use, and its speed is impressive, allowing the code to be ready for production in seconds."
"General ease of use, quick start up time, and the NUnit build runner are the most valuable features for us."
"The setup is extremely straightforward."
"TeamCity is a very user-friendly tool."
"There is much online documentation for TeamCity, with certain learning materials such as videos."
"Time to deployment has been reduced and it has helped in preventing us from deploying breaking changes into production."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
 

Cons

"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. AWS support helped us resolve it, however, it could be better."
"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."
"There is no persistent storage or preservation of workspace between the builds."
"They can further improve the integration of the Bitbucket for CodeBuild."
"There have been times when CodeBuild has shown some instability, like bugs or breakdowns."
"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."
"The servers used for macOS and iOS builds are limited in availability, operating only in US East 1 and East 2, and US West 1 and West 2. This geographical limitation causes latency issues and extended build times for regions such as India, impacting production efficiency."
"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."
"Net deployment needs improvement. Also, I'd like to see more NuGet/Octopus style features and Azure stuff."
"The UI for this solution could be improved. New users don't find it easy to navigate; they need some level of training to understand the ins and the outs."
"Occasionally issues deploying software using the tool due to configuration issues within the tool (mostly around powershell configuration)."
"If there was more documentation that was easier to locate, it would be helpful for users."
"This product lacks real reporting for all the information it captures; we should be able to create reports or dashboards for management."
"If TeamCity could create more out of the box solutions to make it more user friendly and create more use cases, that would be ideal."
"Deployment functions need work."
 

Pricing and Cost Advice

"We pay a monthly licensing fee."
"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."
"Despite the cost, it is worth the investment."
"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.
921,338 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
14%
Outsourcing Company
12%
Comms Service Provider
8%
Financial Services Firm
8%
Financial Services Firm
13%
Computer Software Company
10%
Comms Service Provider
9%
Manufacturing Company
8%
 

Company Size

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

Questions from the Community

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 is your primary use case for AWS CodeBuild?
My use of AWS CodeBuild is focused on the CI/CD part, which stands for continuous integration and continuous deployment. Basically, we write the code and then commit it into a repository, which cou...
Ask a question
Earn 20 points
 

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: November 2026.
921,338 professionals have used our research since 2012.