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 May 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.4%, down from 7.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
TeamCity5.4%
JRebel1.0%
Other93.6%
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)."
"TeamCity's GUI is nice."
"Continuous integration has reduced build failures and highlighted issues sooner."
"It's easy to move to a new release because of templates and meta-runners, and agent pooling."
"The setup is extremely straightforward."
"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."
"I have not yet implemented the remote build feature, but this will be a big plus. We want to be able to build legacy products on a build agent without developers needing to have obsolete tool sets installed on their local PC."
"Do it! Very easy to use and very stable."
"The most valuable aspect of the solution is its easy configuration, and it also has multiple plugins that can be used especially for building .net applications."
 

Cons

"I had a little problem in redeploying applications using a specific framework (reactor + spring) in a Maven multi-module project."
"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."
"Setting up build configurations involves too many steps, as the process is too much broken down."
"REST API support lacks many features in customization of builds, jobs, and settings."
"However, in TeamCity, the whole build is like a whole block, and there is no way to stop."
"Deployment functions need work."
"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."
"The integration between other solutions and TeamCity could be smoother."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts."
 

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

Top Industries

By visitors reading reviews
No data available
Financial Services Firm
19%
Computer Software Company
12%
Comms Service Provider
9%
Marketing Services Firm
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 GitLab, Google, Jenkins and others in Build Automation. Updated: April 2026.
893,244 professionals have used our research since 2012.