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
11th
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 2025, in the Build Automation category, the mindshare of LaunchDarkly is 0.4%, up from 0.0% compared to the previous year. The mindshare of TeamCity is 7.4%, up from 6.7% 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.
Almoeeni Fazal - PeerSpot reviewer
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…

Quotes from Members

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

Pros

"The ability to turn off a flag is crucial when a task is not complete, especially if there is an error in a commit."
"The initial setup is very easy."
"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."
"From the development side, it allows us to manage multiple things."
"The setup is easy."
"I like that it offers the ability to control the flags."
"It is very easy to use, and its speed is impressive, allowing the code to be ready for production in seconds."
"Time to deployment has been reduced in situations where we want to deploy to production or deploy breaking changes."
"It's easy to move to a new release because of templates and meta-runners, and agent pooling."
"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."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"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's GUI is nice."
"VCS Trigger: Provides excellent source control support."
 

Cons

"I have used LaunchDarkly for around two and a half years and I haven't faced any issues with it."
"We need experience to use it, and the initial setup can be difficult. Also, sometimes it has breakdowns."
"Fetching information about multiple flags in a single action would be beneficial."
"Right now, no improvements are needed."
"The feature where one feature flag is dependent on another could be explored more for our usage."
"When the system has an excessive number of feature flags, managing them can become cumbersome."
"I strongly believe they need to develop a strategy for handling situations where LaunchDarkly goes down."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
"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."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
"I need some more graphical design."
"If there was more documentation that was easier to locate, it would be helpful for users."
"The integration between other solutions and TeamCity could be smoother."
 

Pricing and Cost Advice

Information not available
"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.
857,162 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
24%
Computer Software Company
18%
Comms Service Provider
6%
Manufacturing Company
5%
 

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: June 2025.
857,162 professionals have used our research since 2012.