Try our new research platform with insights from 80,000+ expert users

JFrog Pipeline 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

JFrog Pipeline
Ranking in Build Automation
22nd
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 February 2026, in the Build Automation category, the mindshare of JFrog Pipeline is 2.2%, up from 1.1% compared to the previous year. The mindshare of TeamCity is 5.8%, down from 7.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Market Share Distribution
ProductMarket Share (%)
TeamCity5.8%
JFrog Pipeline2.2%
Other92.0%
Build Automation
 

Featured Reviews

Steve Buttler - PeerSpot reviewer
DevOps Lead at a tech company with 51-200 employees
Testing against multiple run times, versions, and environments is a plus point
We are using Shippable to automate our CI/CD, so we (and our developers) can focus on our core business.  Shippable has tremendously increased our product and features delivery by at least three times. The platform has some amazing features and the integration option makes it very simple to plug…
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

"The platform has some amazing features and the integration option makes it very simple to plug with any of our favorite tools."
"Testing against multiple run times, versions, and environments is a plus point with the additional pipelines making it more interesting to see what is happening across your development process in a single pane of glass."
"Good integration with IDE and JetBrains products."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."
"TeamCity is more structured and user-friendly than other vendors."
"It's easy to move to a new release because of templates and meta-runners, and agent pooling."
"TeamCity's GUI is nice."
"It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack."
"TeamCity is a very user-friendly tool."
 

Cons

"They could work on reducing the number of permissions required while using Bitbucket."
"If there was more documentation that was easier to locate, it would be helpful for users."
"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."
"REST API support lacks many features in customization of builds, jobs, and settings."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
"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."
"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."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
 

Pricing and Cost Advice

"The pricing is the cheapest compared to the other platforms out there."
"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."
"The licensing is on an annual basis."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
881,733 professionals have used our research since 2012.
 

Comparison Review

it_user184734 - PeerSpot reviewer
Systems Administrator at Facebook
Jan 22, 2015
I generally find TeamCity a lot more intuitive than Jenkins.
Moving to TeamCity from Jenkins At work, we’re slowly migrating from Jenkins to TeamCity in the hope of ending some of our recurring problems with continuous integration. My use of Jenkins prior to this job has been almost strictly on a personal basis, although I pretty much only use Travis…
 

Top Industries

By visitors reading reviews
Financial Services Firm
17%
Manufacturing Company
11%
Computer Software Company
6%
Educational Organization
6%
Financial Services Firm
18%
Computer Software Company
14%
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 do you like most about TeamCity?
One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies.
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 ...
 

Comparisons

 

Also Known As

Shippable
No data available
 

Overview

 

Sample Customers

SAP, Today Tix, Cisco, Lithium, Pushspring, Packet
Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
Find out what your peers are saying about GitLab, Google, GitHub and others in Build Automation. Updated: January 2026.
881,733 professionals have used our research since 2012.