AWS CodeBuild vs TeamCity comparison

Amazon Web Services (AWS) and JetBrains are both solutions in the Build Automation category. Amazon Web Services (AWS) is ranked #8 with an average rating of 8.2, while JetBrains is ranked #11 with an average rating of 6.8. Amazon Web Services (AWS) holds a 1.5% mindshare in BA, compared to JetBrains’s 7.2% mindshare. Additionally, 91% of Amazon Web Services (AWS) users are willing to recommend the solution, compared to 90% of JetBrains users who would recommend it.

AWS CodeBuild

Read 12 AWS CodeBuild reviews

548 Views
548 Comparison Views

91% willing to recommend

TeamCity

Read 28 TeamCity reviews

1,959 Views
1,959 Comparison Views

90% willing to recommend

AWS CodeBuild

TeamCity

Comparison Buyer's Guide

Download the report

Executive SummaryUpdated on Mar 5, 2025

TeamCity and AWS CodeBuild both compete in the CI/CD category. TeamCity appears to have the upper hand due to its flexibility in build configurations and extensive plugin functionality, whereas AWS CodeBuild excels with its seamless AWS integrations and cost-effective scalability.

Features: TeamCity offers cross-platform build support, detailed logging, and Octopus Deploy integration for automated deployments. AWS CodeBuild provides serverless operations, streamlined AWS service integration, and robust logging features with CloudWatch, facilitating easy troubleshooting.

Room for Improvement: TeamCity's setup can be complex, requiring better reporting, improved version control integration, and a more structured UI. AWS CodeBuild could enhance third-party integrations, offer more instance options, and improve environment setups. Notification features also need refinement for AWS CodeBuild.

Ease of Deployment and Customer Service: TeamCity offers deployment flexibility across private and public clouds but faces support challenges due to regional limitations. AWS CodeBuild is primarily deployed in public clouds, providing seamless AWS integration. AWS is commended for its responsive support, whereas TeamCity's documentation is helpful despite support timezone constraints.

Pricing and ROI: TeamCity provides a free tier with limited capacity but becomes costly for larger deployments, seen as an investment for robust operations. AWS CodeBuild's pricing is based on compute usage, ideal for pay-as-you-go models, but additional bundled AWS service costs can accumulate. Both tools offer different pricing strategies supporting continuous integration and deployment.

To learn more, read our detailed AWS CodeBuild vs. TeamCity Report (Updated: July 2025).

Buyer's Guide

AWS CodeBuild vs. TeamCity

July 2025

Download the complete report

Helped 865,164 peers since 2012

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

8th

Average Rating

8.2

Reviews Sentiment

6.3

Number of Reviews

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

Ranking in other categories

No ranking in other categories

Mindshare comparison

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

Build Automation

Featured Reviews

Mahadev Metre

DevOps Engineer at Paydoh

Integration with diverse environments boosts productivity and automation

AWS CodeBuild's support for a wide range of programming languages and build environments benefits development teams significantly in terms of productivity and ease of use. There are extensive libraries of code structures available, making it a universal pipeline. All programming languages I have worked with are supported in AWS CodeBuild, eliminating the need for alternative deployment services. The service supports iOS builds, Kotlin, Java, NodeJS, and ReactJS. AWS has made it accessible to all languages, allowing developers to simply open the console and trigger builds. AWS manages all the background server operations for building or deploying code. For standard builds such as ReactJS or Java, a Linux or Ubuntu server suffices. AWS provides its own operating system for these purposes. For builds requiring physical servers, such as Apple macOS server, AWS rents Mac minis specifically for iOS and SwiftUI builds. While this incurs higher charges, it demonstrates AWS's commitment to providing comprehensive solutions for all use cases.

Read full review

Almoeeni Fazal

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…

Read full review

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 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."

"AWS CodeBuild reduces wait time and optimizes workflows."

"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 solution provides good integrations."

"The integration is a good feature."

More AWS CodeBuild pros

"It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack."

"Time to deployment has been reduced in situations where we want to deploy to production or deploy breaking changes."

"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."

"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."

"VCS Trigger: Provides excellent source control support."

"One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."

More TeamCity pros

Cons

"One of the main challenges is that if the environment is not set up properly, it will result in issues such as image errors."

"While working on building images for multiple applications within a single script, I encountered an issue where looping functionality was not supported as expected."

"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."

"The deployment fails sometimes."

"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."

"We had integration issues with a tool called Octopus Deploy while using CodeBuild. AWS support helped us resolve it, however, it could be better."

"There have been times when CodeBuild has shown some instability, like bugs or breakdowns."

More AWS CodeBuild cons

"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."

"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."

"REST API support lacks many features in customization of builds, jobs, and settings."

"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."

"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."

"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."

"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."

More TeamCity cons

Pricing and Cost Advice

"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."

"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."

See which vendors are best for you

Use our free recommendation engine to learn which Build Automation solutions are best for your needs.

See recommendations

865,164 professionals have used our research since 2012.

Comparison Review

it_user184734

Systems Administrator at Facebook

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…

Read full review

Top Industries

By visitors reading reviews

Computer Software Company

16%

Media Company

11%

Financial Services Firm

11%

Manufacturing Company

10%

Financial Services Firm

21%

Computer Software Company

17%

Comms Service Provider

University

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).

See all answers

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...

See all answers

What needs improvement with AWS CodeBuild?

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 exten...

See all answers

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.

See all answers

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.

See all answers

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 ...

See all answers

Comparisons

GitHub Actions vs AWS CodeBuild

Compared 37% of the time

AWS CodePipeline vs AWS CodeBuild

Compared 23% of the time

GitLab vs AWS CodeBuild

Compared 22% of the time

Jenkins vs AWS CodeBuild

Compared 18% of the time

More AWS CodeBuild Competitors

GitLab vs TeamCity

Compared 40% of the time

GitHub Actions vs TeamCity

Compared 15% of the time

Harness vs TeamCity

Compared 13% of the time

Jenkins vs TeamCity

Compared 10% of the time

CircleCI vs TeamCity

Compared 8% of the time

More TeamCity Competitors

Product Reports

Buyer's Guide

AWS CodeBuild

August 2025

Download AWS CodeBuild product report

Buyer's Guide

TeamCity

July 2025

Download TeamCity product report

Also Known As

CodeBuild

No data available

Overview

AWS CodeBuild is a fully managed continuous integration service that compiles source code, runs tests, and produces software packages that are ready to deploy. With CodeBuild, you don’t need to provision, manage, and scale your own build servers. CodeBuild scales continuously and processes multiple builds concurrently, so your builds are not left waiting in a queue. You can get started quickly by using prepackaged build environments, or you can create custom build environments that use your own build tools. With CodeBuild, you are charged by the minute for the compute resources you use.

Amazon Web Services (AWS)

TeamCity is a Continuous Integration and Deployment server that provides out-of-the-box continuous unit testing, code quality analysis, and early reporting on build problems. A simple installation process lets you deploy TeamCity and start improving your release management practices in a matter of minutes. TeamCity supports Java, .NET and Ruby development and integrates perfectly with major IDEs, version control systems, and issue tracking systems.

JetBrains

Sample Customers

Expedia, Intuit, Royal Dutch Shell, Brooks Brothers

Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia

Buyer's Guide

AWS CodeBuild vs. TeamCity

July 2025

Free Report: AWS CodeBuild vs. TeamCity

Find out what your peers are saying about AWS CodeBuild vs. TeamCity and other solutions. Updated: July 2025.

DOWNLOAD NOW

865,164 professionals have used our research since 2012.

See our AWS CodeBuild vs. TeamCity report.

See our list of best Build Automation vendors.

We monitor all Build Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.