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

IBM Rational Build Forge vs TeamCity comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive SummaryUpdated on Jun 3, 2026

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

IBM Rational Build Forge
Ranking in Build Automation
24th
Average Rating
9.0
Reviews Sentiment
7.5
Number of Reviews
2
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 September 2026, in the Build Automation category, the mindshare of IBM Rational Build Forge is 2.0%, up from 1.0% compared to the previous year. The mindshare of TeamCity is 4.8%, down from 6.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
TeamCity4.8%
IBM Rational Build Forge2.0%
Other93.2%
Build Automation
 

Featured Reviews

reviewer1538124 - PeerSpot reviewer
Devops and SAFe Specialist at a tech services company with 201-500 employees
Useful features, stable, easy to deploy, and works well
Its logging can be improved. When something goes wrong, it is not always very easy to find the problem. It is hard to identify whether the problem is because of low memory in the server or some configuration in Rational Build Forge. The error logs are not very detailed, and they should provide more information. It should also have more integration with third-party tools. It would be great to have more integration with third-party tools.
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

"I utilized the reporting features and a number of documents, as well as statuses."
"All features are useful; our customer doesn't have any complaints about the tool, and it works pretty well for what they want and what they need to do."
"Very good reporting features."
"It's easy to move to a new release because of templates and meta-runners, and agent pooling."
"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."
"TeamCity is more structured and user-friendly than other vendors."
"Time to deployment has been reduced and it has helped in preventing us from deploying breaking changes into production."
"Do it! Very easy to use and very stable."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"With Teamcity, our build/packaging process and the ensuing deployment via Octopus Deploy takes less than half an hour."
"It was simple and easy to use, with great features which are always customizable."
 

Cons

"Its logging can be improved. When something goes wrong, it is not always very easy to find the problem."
"Its logging can be improved. When something goes wrong, it is not always very easy to find the problem. It is hard to identify whether the problem is because of low memory in the server or some configuration in Rational Build Forge. The error logs are not very detailed, and they should provide more information. It should also have more integration with third-party tools. It would be great to have more integration with third-party tools."
"The solution could be more user friendly."
"Not user friendly for the layman."
"This product lacks real reporting for all the information it captures; we should be able to create reports or dashboards for management."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
"Occasionally issues deploying software using the tool due to configuration issues within the tool (mostly around powershell configuration)."
"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."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
"However, in TeamCity, the whole build is like a whole block, and there is no way to stop."
"The integration between other solutions and TeamCity could be smoother."
 

Pricing and Cost Advice

Information not available
"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.
914,805 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Financial Services Firm
15%
Computer Software Company
10%
Comms Service Provider
9%
Manufacturing Company
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise4
Large Enterprise15
 

Questions from the Community

Ask a question
Earn 20 points
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

 

Also Known As

Rational Build Forge
No data available
 

Overview

 

Sample Customers

Cars.com
Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
Find out what your peers are saying about IBM Rational Build Forge vs. TeamCity and other solutions. Updated: September 2026.
914,805 professionals have used our research since 2012.