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

GitHub Actions 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

GitHub Actions
Ranking in Build Automation
2nd
Average Rating
8.4
Reviews Sentiment
5.4
Number of Reviews
23
Ranking in other categories
No ranking in other categories
TeamCity
Ranking in Build Automation
12th
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 August 2026, in the Build Automation category, the mindshare of GitHub Actions is 7.0%, down from 11.5% compared to the previous year. The mindshare of TeamCity is 4.9%, down from 7.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
GitHub Actions7.0%
TeamCity4.9%
Other88.1%
Build Automation
 

Featured Reviews

Bharadwaj Deepak Mohapatra - PeerSpot reviewer
DevOps Engineer at ENTERPRISE SYSTEM SOLUTIONS LIMITED
Has supported repository management and demonstrates potential in workflow flexibility
While GitHub Actions offers a range of functionalities, it is newer compared to more established tools such as Jenkins and Azure DevOps. There is still room for improvement, especially in areas concerning deeper capabilities akin to those provided by Jenkins and Azure DevOps. Given the evolving nature of technology, there are potential improvements GitHub Actions can focus on, including enhancing support and reliability to match its competitors.
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

"The most valuable feature of GitHub Actions is the ability to automate various tasks, such as backups and deployments, to ease the development workflow."
"Creating workflows in YAML format is straightforward and easy to comprehend. This includes both understanding and writing workflows. Additionally, the downloading aspect for third-party instances can also be easily done. It's worth noting that vulnerability analysis and similar tasks should be part of our automation through data workflows. Furthermore, we can break down our processes step by step, starting from building, then moving on to analysis, testing, and finally deploying in production and the clear environment. All of these tasks can be efficiently managed within this platform."
"I have optimized job execution time by running test scripts in parallel and creating multiple pipelines; we've significantly reduced execution times. What could take 50 minutes can be cut down to just 8 to 10 minutes through these optimizations."
"It is user-friendly, with clear and organized processes, making it easy to navigate and work with."
"The product's most beneficial feature is the ability to create workflows within the solution."
"It saves a lot of time with GitHub Actions; especially, the whole process if done manually might cost us a lot, maybe a week or two weeks just for deployment, but now with automation, we automate the deployment effectively."
"The main benefit is collaboration. It allows us to easily collaborate with other developers, regardless of location. For example, we can collaborate with both our African and German colleagues seamlessly. It's platform-agnostic, so it is flexible and not tied to any OS, so we can work on Linux, Windows, web, and even Oracle applications. It's flexible, reliable, and overall an excellent tool for our needs."
"GitHub Actions is valuable for its ease of use and integration."
"It was simple and easy to use, with great features which are always customizable."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"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."
"There is much online documentation for TeamCity, with certain learning materials such as videos."
"General ease of use, quick start up time, and the NUnit build runner are the most valuable features for us."
"It's easy to move to a new release because of templates and meta-runners, and agent pooling."
"It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack."
"The setup is extremely straightforward."
 

Cons

"There is a part that detects outdated libraries. If that feature could be more intuitive and informative, that would be nice."
"The only issue I have faced is with authorization, particularly when configuring the GitHub token correctly."
"Sometimes incremental steps should be taken during deployment instead of trying to execute all tasks simultaneously, particularly when dealing with AWS EKS clusters and Helm charts."
"Sometimes it is quite complex to commit code from our local system to the GitHub repository; creating a folder in GitHub can be tedious."
"GitHub Actions lacks a feature for automating the build process for mobile applications."
"Improvements could be made in terms of time-saving capabilities and resolving potential complexities in centralized workflows."
"The UI could be better."
"The reporting capabilities are somewhat limited."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
"Setting up build configurations involves too many steps, as the process is too much broken down."
"I need some more graphical design."
"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."
"Features I would like to see in TeamCity: Allow for shared resource locks across multiple build configurations (i.e. deploy then run integration tests against the same environment)."
"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."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
"If there was more documentation that was easier to locate, it would be helpful for users."
 

Pricing and Cost Advice

"The product is slightly more expensive than some alternatives."
"The cost for GitHub Actions may be around $45 dollars per user."
"The tool's price is okay and reasonable."
"For our basic usage, we didn't have to pay."
"It's low-priced. Not high, but definitely low."
"Regarding cost, as an enterprise, we negotiate our license and expenses, so I can't provide a specific rating for that."
"It is free and open platform, so I would rate it 1 out of 10."
"Price-wise, GitHub Actions is okay. If I want to use the product's advanced features, then I need to pay the licensing charges for the solution."
"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.
908,877 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
20%
Manufacturing Company
8%
Comms Service Provider
7%
Outsourcing Company
6%
Financial Services Firm
17%
Computer Software Company
10%
Comms Service Provider
8%
Manufacturing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise4
Large Enterprise11
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise4
Large Enterprise15
 

Questions from the Community

What is your experience regarding pricing and costs for GitHub Actions?
I would rate pricing a seven, which leans toward the expensive side. However, there is still value for money, and that's why we continue using it.
What needs improvement with GitHub Actions?
While GitHub Actions offers a range of functionalities, it is newer compared to more established tools such as Jenkins and Azure DevOps. There is still room for improvement, especially in areas con...
What is your primary use case for GitHub Actions?
The main use case for GitHub Actions is maintaining enterprise repositories in private for security reasons, because we have multiple enterprise clients. We're using the premium GitHub service for ...
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 ...
What is your primary use case for TeamCity?
We use TeamCity for build configuration and pipeline creation, as well as for automation purposes. We provide working pipelines for different teams internally.
 

Comparisons

 

Overview

 

Sample Customers

Information Not Available
Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
Find out what your peers are saying about GitHub Actions vs. TeamCity and other solutions. Updated: August 2026.
908,877 professionals have used our research since 2012.