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

JRebel vs TeamCity comparison

 

Comparison Buyer's Guide

Executive Summary

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

JRebel
Ranking in Build Automation
30th
Average Rating
8.0
Number of Reviews
1
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 JRebel is 0.9%, up from 0.4% 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 (%)
TeamCity4.9%
JRebel0.9%
Other94.2%
Build Automation
 

Featured Reviews

it_user177786 - PeerSpot reviewer
Developer at a tech services company with 51-200 employees
Easy to configure, works well, has 'free' options (like Social)
Easy to configure, works well, has 'free' options (like Social) It gets the used time for redeploy in a development environment really fast and of course that's a good point. Development environment I had a little problem in redeploying applications using a specific…
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

"Easy to configure, works well, has 'free' options (like Social)."
"It is vital to our business to have quick and robust builds, and TeamCity is helping us to keep everything tidy and under control."
"Good visualization of builds Easy configuration Good integration with IDE and JetBrains products."
"TeamCity is a very user-friendly tool."
"TeamCity allows us to have self-sufficient development teams that can create their own builds and deployments."
"TeamCity is very useful due to the fact that it has a strong plug-in system."
"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."
"TeamCity is very stable, is easy to set up and maintain, and once everything is configured there is almost zero time needed to maintain it."
 

Cons

"I had a little problem in redeploying applications using a specific framework (reactor + spring) in a Maven multi-module project."
"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."
"Deployment functions need work."
"The integration between other solutions and TeamCity could be smoother."
"Net deployment needs improvement. Also, I'd like to see more NuGet/Octopus style features and Azure stuff."
"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."
"REST API support lacks many features in customization of builds, jobs, and settings."
"If there was more documentation that was easier to locate, it would be helpful for users."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
 

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.
908,877 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
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
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

ZeroTurnaround JRebel
No data available
 

Overview

 

Sample Customers

MS Learning & Consulting, NetworkedAssets, Vaadin Ltd, Heliocentris, Result Group
Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
Find out what your peers are saying about Jenkins, GitHub, GitLab and others in Build Automation. Updated: August 2026.
908,877 professionals have used our research since 2012.