JFrog Pipeline vs TeamCity comparison

JFrog and JetBrains are both solutions in the Build Automation category. JFrog is ranked #23, while JetBrains is ranked #11 with an average rating of 6.8. JFrog holds a 1.3% mindshare in BA, compared to JetBrains’s 7.3% mindshare. Additionally, 100% of JFrog users are willing to recommend the solution, compared to 90% of JetBrains users who would recommend it.

JFrog Pipeline

Read 1 JFrog Pipeline review

407 Views
289 Comparison Views

100% willing to recommend

TeamCity

Read 28 TeamCity reviews

2,025 Views
1,064 Comparison Views

90% willing to recommend

JFrog Pipeline

TeamCity

Comparison Buyer's Guide

Download the report

Executive Summary

We performed a comparison between JFrog Pipeline and TeamCity based on real PeerSpot user reviews.

Find out what your peers are saying about GitLab, Google, Jenkins and others in Build Automation.

To learn more, read our detailed Build Automation Report (Updated: June 2025).

Buyer's Guide

Build Automation

June 2025

Download the complete report

Helped 860,592 peers since 2012

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

23rd

Average Rating

8.0

Number of Reviews

Ranking in other categories

No ranking in other categories

TeamCity

Ranking in Build Automation

11th

Average Rating

8.2

Reviews Sentiment

7.7

Number of Reviews

Ranking in other categories

No ranking in other categories

Mindshare comparison

As of July 2025, in the Build Automation category, the mindshare of JFrog Pipeline is 1.3%, up from 1.1% compared to the previous year. The mindshare of TeamCity is 7.3%, up from 6.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.

Build Automation

Featured Reviews

Steve Buttler

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…

Read full review

Almoeeni Fazal

Python Django developer at Cielo WiGle Inc.

Impressive pipeline efficiency with helpful support and a fairly straightforward setup

We use TeamCity for the CI/CD pipeline. It is used for deploying code from the desktop to the production environment. We push our code to GitHub, which then creates a pipeline to a server using AWS, deploying automatically without errors or conflicts in GitHub branches. We also use TeamCity's…

Read full review

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."

"TeamCity is more structured and user-friendly than other vendors."

"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."

"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."

"It is very easy to use, and its speed is impressive, allowing the code to be ready for production in seconds."

"It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack."

"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."

"One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."

More TeamCity pros

Cons

"They could work on reducing the number of permissions required while using Bitbucket."

"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."

"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 upgrade process could be smoother. Upgrading major versions can often cause some pain."

"The UI for this solution could be improved. New users don't find it easy to navigate. The need some level of training to understand the ins and the outs."

"It will benefit this solution if they keep up to date with other CI/CD systems out there."

"REST API support lacks many features in customization of builds, jobs, and settings."

"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."

"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."

More TeamCity cons

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."

See which vendors are best for you

Use our free recommendation engine to learn which Build Automation solutions are best for your needs.

See recommendations

860,592 professionals have used our research since 2012.

Comparison Review

it_user184734

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…

Read full review

Top Industries

By visitors reading reviews

Financial Services Firm

20%

Computer Software Company

13%

Manufacturing Company

Comms Service Provider

Financial Services Firm

24%

Computer Software Company

18%

Comms Service Provider

Manufacturing Company

Company Size

By reviewers

Large Enterprise

Midsize Enterprise

Small Business

No data available

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.

See all answers

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.

See all answers

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 ...

See all answers

Comparisons

Jenkins vs JFrog Pipeline

Compared 69% of the time

GitHub Actions vs JFrog Pipeline

Compared 18% of the time

Buildkite vs JFrog Pipeline

Compared 13% of the time

More JFrog Pipeline Competitors

GitLab vs TeamCity

Compared 41% of the time

Harness vs TeamCity

Compared 14% of the time

GitHub Actions vs TeamCity

Compared 14% of the time

Jenkins vs TeamCity

Compared 10% of the time

CircleCI vs TeamCity

Compared 7% of the time

More TeamCity Competitors

Product Reports

Buyer's Guide

Build Automation

June 2025

Download JFrog Pipeline product report

Buyer's Guide

TeamCity

June 2025

Download TeamCity product report

Also Known As

Shippable

No data available

Overview

JFrog Pipelines empowers software teams to ship updates faster by automating DevOps processes in a continuously streamlined and secure way across all their teams and tools. Encompassing continuous integration (CI), continuous delivery (CD), infrastructure and more, it automates everything from code to production. Pipelines is natively integrated with the JFrog Platform and is available with both cloud (software-as-a-service) and on-prem subscriptions.

JFrog

TeamCity is a Continuous Integration and Deployment server that provides out-of-the-box continuous unit testing, code quality analysis, and early reporting on build problems. A simple installation process lets you deploy TeamCity and start improving your release management practices in a matter of minutes. TeamCity supports Java, .NET and Ruby development and integrates perfectly with major IDEs, version control systems, and issue tracking systems.

JetBrains

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, Jenkins and others in Build Automation. Updated: June 2025.

DOWNLOAD NOW

860,592 professionals have used our research since 2012.

See our list of best Build Automation vendors.

We monitor all Build Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.