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)."
"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."
"I spend less time scripting to get a build working and more time configuring TeamCity through its web-based front end."
"VCS Trigger: Provides excellent source control support."
"It's easy to move to a new release because of templates and meta-runners, and agent pooling."
"TeamCity allows us to have self-sufficient development teams that can create their own builds and deployments."
"When we discovered TeamCity, it totally speeded up our workflow."
"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 integration is a valuable feature."
 

Cons

"I had a little problem in redeploying applications using a specific framework (reactor + spring) in a Maven multi-module project."
"We would like to see better integration with other version controls, since we encountered difficulty when this was first attempted."
"More build runners and more options are needed, although I have no worries they keep improving."
"There have been times when making copies of a project has caused major stability issues, especially when you have nested project structure based off of different build configuration templates."
"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."
"It'd be great to see future built-in support for Octopus Deploy."
"REST API support lacks many features in customization of builds, jobs, and settings."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
 

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.