LaunchDarkly

I primarily use LaunchDarkly for rollouts, having flags, and putting my feature and code behind the flags.

I have multiple codes that I need to organize in different branches, and it is better to put those behind different flags so we can turn them on and off and test them in required environments.

I work with Java SDKs and Go SDKs to integrate LaunchDarkly, which really helps when dealing with a complex workflow and allows me to turn off a flag for a feature if it is not working well.

With LaunchDarkly, we are using a lot of AI to ship our bulk of code, which helps us keep new changes behind the flags until fully tested, enhancing our day-to-day usage.

We integrate monitoring tools like OpenSearch and Grafana with LaunchDarkly; these integrations are sufficient for our needs, and we use a common library built for across the organization to utilize LaunchDarkly flags and features.

I find LaunchDarkly very easy to use, with flags that work really well; it is very convenient and fast to toggle features on and off, and its integrations with different platforms and libraries are really good, making it overall perfect.

LaunchDarkly has positively impacted our organization by allowing us to confidently ship products across different environments, knowing we can easily turn off any feature that faces issues.

LaunchDarkly stands out due to its ease of use, deployability across environments, and the ability to easily toggle features, which are all beneficial qualities.

I did not particularly like the rule area; there are many things to add into the rule to enable it, and I think we could make it easier or more customizable at the organizational level.

If the rules could be a bit more user-friendly, it would be helpful.

I have been using LaunchDarkly for five to six months.

LaunchDarkly is stable.

SailPoint uses LaunchDarkly across a lot of employees, and we do not face many problems regarding scalability, so I think it is good and scalable.

I have not reached out to customer support for any reason, so I am not much aware of it.

Prior to LaunchDarkly, we used to organize our code via a Git branching strategy, which had its limitations and risks, making it not environment-friendly or customizable, issues that LaunchDarkly has helped solve.

I mentioned earlier how we previously used Git branching for multiple feature rollouts, which was complex and not very environment-friendly, making LaunchDarkly a better solution.

I cannot speak on money saved, but time saved is evident because we can ship products faster with more confidence, although I do not have metrics to quantify it.

Public Cloud

Amazon Web Services (AWS)

What do you like best about the product?

I use LaunchDarkly for turning on and off feature flags in demo environments. It solves the ability for me to manage lots of individual feature flags in different environments easily and at scale across the organization. I like that it's very easy and intuitive to use. Mostly, I can do things at scale quickly using only a couple of clicks. It effectively just saves me a lot of time, which would otherwise be spent managing these flags manually on an organizational level. Dealing with tens of environments at a time, it really saves a huge amount of time that could otherwise be spent on more valuable activities.

What do you dislike about the product?

I feel that maybe some training guides or user guides on how to actually use it could be useful, but nothing comes to mind for now.

What problems is the product solving and how is that benefiting you?

LaunchDarkly lets me manage multiple feature flags across environments easily and at scale, saving me lots of time I would otherwise spend managing them manually. It's easy and intuitive, allowing me to perform tasks quickly with just a few clicks.

What do you like best about the product?

What stands out most is its powerful feature flagging that lets us roll out new OTT platform features incrementally without risking full deployments. The granular audience targeting allows us to seamlessly run beta tests across specific viewer segments and instantly kill switches if performance drops.

What do you dislike about the product?

Managing a high volume of feature flags can get cluttered fast, and without strict team protocols, stale flags accumulate and add technical debt to the codebase. Additionally, the tier based pricing can get steep as active user contexts and subscriber event counts scale up across our OTT platforms.

What problems is the product solving and how is that benefiting you?

Launch darkly solves the high risk of platform downtime and broken user experiences by decoupling code deployments from feature releases. For our OTT platform, it allows us to safely test new video player features and UI updates with small viewer cohorts first, ensuring zero disruption to live streaming during major feature rollouts.

What do you like best about the product?

The ability to deploy code independently from feature releases. Feature flags give us the confidence to ship continuously without risk — we can roll out changes gradually, target specific segments, and instantly roll back if something goes wrong, all without a redeployment.

What do you dislike about the product?

Flag debt builds up quickly. It’s easy to create flags for a release and then never clean them up, and over time you end up with dozens of stale flags that nobody is confident are safe to remove. More robust built-in tooling to surface old flags, confirm whether they’re still in use, and help retire them would make a big difference.

What problems is the product solving and how is that benefiting you?

LaunchDarkly decouples our deployments from our releases, so engineers can merge and deploy code at any time without it immediately going “live” for users. This has significantly reduced our release risk: we can roll out changes gradually, catch issues early by exposing them to a small percentage of traffic, and instantly kill a feature if something breaks. It also takes the pressure off big-bang releases and gives the business more control over when features are visible and which users can see them.

What do you like best about the product?

easy to use UI. Is rarely down, which is essential for feature flags

What do you dislike about the product?

Searching across flags is not the best experience

What problems is the product solving and how is that benefiting you?

easy rollouts across environements, especially in an AI assisted coding world

What do you like best about the product?

The Contexts feature changed how we target. We went from basic user flags to targeting by company, subscription tier, and region, no application logic changes needed. Running 4-5 concurrent rollouts to different customer segments simultaneously would've taken 3 engineers and 4 months to build in-house. LD replaced that entirely. New engineers are shipping behind flags within their first week

What do you dislike about the product?

SDK versioning across 20+ microservices is a real headache, had 2 incidents this year from inconsistent flag evaluation caused by outdated SDK versions across teams.

What problems is the product solving and how is that benefiting you?

We run ~200 active flags in prod at any time. Kill switch response averages under 30 seconds when something goes wrong, that's not achievable with a homegrown solution at our scale. Saved us an estimated 12 engineer-months of build work.

What do you like best about the product?

I like LaunchDarkly because it makes it easy to release new features safely, manage feature rollouts, and quickly turn features on or off without deploying new code. Overall, it helps reduce risk and makes the software release process smoother and more controlled.

What do you dislike about the product?

It can be expensive for smaller teams, and some of the more advanced features take time to learn. Managing a large number of feature flags can also become difficult without proper organization.**

What problems is the product solving and how is that benefiting you?

LaunchDarkly helps me manage feature releases safely without having to deploy new code each time. It reduces release risk, speeds up deployments, makes testing easier, and lets me fix issues quickly by turning features on or off instantly.

What do you like best about the product?

It has MCP and works perfectly with my LLM. The UI / UX is also looks good

What do you dislike about the product?

Not specifically about LD, but the setup to get feature flag is so hard in my org. It's differnet in FE / BE

What problems is the product solving and how is that benefiting you?

Feature flagging release, changing threshold value for experimentation

What do you like best about the product?

LaunchDarkly has made it much safer to test new features in production by rolling them out to a small percentage of users first, rather than deploying changes to everyone at once. Being able to toggle features on or off instantly without redeploying code has sped up testing cycles significantly, especially when validating changes to trip flow or platform functionality before a full rollout. The targeting rules for controlling exactly who sees a given feature, whether by user segment or percentage, have made testing much more precise than relying on separate staging environments alone. The dashboard makes it easy to monitor flag status and adjust rollouts on the fly without needing a developer to make code changes for every adjustment.

What do you dislike about the product?

Managing a growing number of feature flags over time requires discipline to clean up ones that are no longer needed, otherwise the codebase accumulates unnecessary complexity. Pricing scales with usage and seats, which can get expensive as the number of flags and monthly active users grows. The initial setup for integrating flags cleanly into existing code took some restructuring, especially for parts of the codebase that weren't originally built with feature flagging in mind. Some of the more advanced targeting and experimentation features have a learning curve before getting full value out of them.

What problems is the product solving and how is that benefiting you?

LaunchDarkly has let us test new features on a small subset of real users before a full rollout, catching issues early without risking a broken experience for everyone on the platform. This has made deploying changes to core functionality, like trip flow updates, much safer, since we can instantly disable a feature if something goes wrong instead of needing an emergency rollback and redeploy.

What do you like best about the product?

This tool makes feature flag management incredibly straightforward, letting teams release, test, and roll back features without redeploying code. With real-time control over flags, progressive rollouts, experimentation capabilities, and robust SDK support, it helps reduce deployment risk while enabling faster, more confident software releases.

What do you dislike about the product?

The platform comes with a learning curve for teams that are new to feature flagging, particularly when setting up advanced targeting rules and managing multiple environments. In addition, some reporting and experimentation capabilities are limited to higher-tier plans, and the pricing can get expensive for organizations that need to manage a large number of feature flags.

What problems is the product solving and how is that benefiting you?

It separates feature releases from code deployments, so teams can test new functionality safely, roll it out gradually, and instantly disable problematic features without needing emergency deployments. This approach lowers release risk, supports more frequent deployments, speeds up product experimentation, and helps engineering teams ship new features with greater confidence and stability.