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
29th
Average Rating
8.0
Number of Reviews
1
Ranking in other categories
No ranking in other categories
TeamCity
Ranking in Build Automation
10th
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 June 2026, in the Build Automation category, the mindshare of JRebel is 1.0%, up from 0.3% compared to the previous year. The mindshare of TeamCity is 5.2%, down from 7.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
TeamCity5.2%
JRebel1.0%
Other93.8%
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)."
"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."
"The integration is a valuable feature."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"Do it! Very easy to use and very stable."
"TeamCity's GUI is nice."
"There is much online documentation for TeamCity, with certain learning materials such as videos."
"One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."
"TeamCity is a very user-friendly tool."
 

Cons

"I had a little problem in redeploying applications using a specific framework (reactor + spring) in a Maven multi-module project."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
"Setting up build configurations involves too many steps, as the process is too much broken down."
"However, in TeamCity, the whole build is like a whole block, and there is no way to stop."
"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."
"I need some more graphical design."
"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)."
"Deployment functions need work."
"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.
900,838 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Financial Services Firm
20%
Computer Software Company
11%
Comms Service Provider
7%
Manufacturing Company
6%
 

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, GitLab, GitHub and others in Build Automation. Updated: May 2026.
900,838 professionals have used our research since 2012.