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

LaunchDarkly vs TeamCity comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 5, 2025

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

LaunchDarkly
Ranking in Build Automation
12th
Average Rating
8.0
Reviews Sentiment
7.2
Number of Reviews
7
Ranking in other categories
No ranking in other categories
TeamCity
Ranking in Build Automation
9th
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 April 2025, in the Build Automation category, the mindshare of LaunchDarkly is 0.3%. The mindshare of TeamCity is 7.7%, up from 6.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

James Bayhylle - PeerSpot reviewer
Provides risk-free releases with control access and A/B testing
It allowed us to deploy faster. Despite having a rigorous code review process that slowed things down, once the code was reviewed, LaunchDarkly enabled safe deployments. If there was ever an issue, we could easily roll back a particular release by simply turning off the feature flag. When configuring and setting this up, begin with feature sets that are relatively small in scope. This helps build the necessary skills to leverage the product effectively while maintaining control over the blast radius, thus reducing risk to your customers and application in case of misconfiguration. As you gain more experience with the solution, it's crucial to have a process to manage feature flag sprawl, as mentioned earlier. Implementing a life cycle management system for your feature flags is essential. Overall, I rate the solution a nine out of ten because of its intuitiveness and ease of use.
Omakoji Idakwoji - PeerSpot reviewer
Build management system used to successfully create full request tests and run security scans
I find the TeamCity backend easily accessible. Users can login to the Linux servers that TeamCity is installed on and perform operations. Also I find the ability to template solutions using the meta runner a good feature as well as the user management feature. There is a display that shows which user made recent changes to a branch on GitHub, including the time the changes were made and the particular agent that ran the job. This is also a very useful feature. The metrics and audit available for projects, pipelines and jobs come in handy when debugging.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"It has really helped during the series of product lines and faster deployment and faster development."
"I appreciate that we can release any feature in production and maintain control over it."
"I like that it offers the ability to control the flags."
"From the development side, it allows us to manage multiple things."
"The initial setup is very easy."
"The setup is easy."
"The ability to turn off a flag is crucial when a task is not complete, especially if there is an error in a commit."
"Good integration with IDE and JetBrains products."
"The most valuable aspect of the solution is its easy configuration. It also has multiple plugins that can be used especially for building .net applications."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"It is very easy to use, and its speed is impressive, allowing the code to be ready for production in seconds."
"It's easy to move to a new release because of templates and meta-runners, and agent pooling."
"The integration is a valuable feature."
"TeamCity is very useful due to the fact that it has a strong plug-in system."
"One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."
 

Cons

"We need experience to use it, and the initial setup can be difficult. Also, sometimes it has breakdowns."
"I strongly believe they need to develop a strategy for handling situations where LaunchDarkly goes down."
"The feature where one feature flag is dependent on another could be explored more for our usage."
"Fetching information about multiple flags in a single action would be beneficial."
"Right now, no improvements are needed."
"When the system has an excessive number of feature flags, managing them can become cumbersome."
"I have used LaunchDarkly for around two and a half years and I haven't faced any issues with it."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
"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."
"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."
"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."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
 

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

Comparison Review

it_user184734 - PeerSpot reviewer
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
No data available
Financial Services Firm
25%
Computer Software Company
17%
Comms Service Provider
6%
Manufacturing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What needs improvement with LaunchDarkly?
We need experience to use it, and the initial setup can be difficult. Also, sometimes it has breakdowns. I would rate LaunchDarkly a seven out of ten.
What is your primary use case for LaunchDarkly?
We use LaunchDarkly for managing feature flags. It helps manage the keys to control what users view on our screens.
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

 

Overview

 

Sample Customers

Information Not Available
Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
Find out what your peers are saying about LaunchDarkly vs. TeamCity and other solutions. Updated: March 2025.
845,406 professionals have used our research since 2012.