LaunchDarkly

What do you like best about the product?

What I like best about LaunchDarkly is how it makes feature flag management and progressive software delivery incredibly simple and reliable. It allows teams to release features safely by decoupling deployments from releases, enabling gradual rollouts, A/B testing, targeted user segmentation, and instant feature rollbacks without redeploying code. I also appreciate its intuitive dashboard, robust SDK support, real-time flag updates, and seamless integrations with CI/CD pipelines and observability tools. Overall, LaunchDarkly reduces deployment risk, accelerates software releases, and gives engineering teams much greater control over feature delivery in production.

What do you dislike about the product?

One area where LaunchDarkly could improve is offering simpler pricing and more intuitive management for organizations with a large number of feature flags and environments. While the platform is extremely powerful, maintaining hundreds of flags over time can become complex without strong governance. I'd also like to see richer built-in analytics, more customizable dashboards, and additional automation for flag lifecycle management. Overall, the experience has been very positive, but improved cost transparency, enhanced reporting, and stronger flag management capabilities would make LaunchDarkly even more valuable for engineering teams.

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

LaunchDarkly solves the challenge of releasing software safely by separating feature releases from code deployments through feature flags. Instead of deploying code directly to all users, teams can gradually roll out features, target specific user segments, run experiments, and instantly disable problematic features without redeploying applications. This reduces deployment risk, minimizes downtime, accelerates release cycles, and gives engineering teams greater control over production changes. As a result, it has streamlined software delivery, improved release confidence, enabled continuous deployment, and allowed us to ship new features faster with significantly lower operational risk.

What do you like best about the product?

Ability to release a new features to clients and if there an issue in a new feature you can quickly revert your changes, you can target particular users to release a new feature

What do you dislike about the product?

So far, so good, didn't find anything to dislike

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

I can work within a new feature independently and not bother other users with my uncompleted changes, the new changes will be available only for me

What do you like best about the product?

I use LaunchDarkly mainly for feature flags, and it's great because I can enable features without code deployment and serve variations based on users, organizations, locales, countries, regions, etc. The UI is very intuitive and easy to work with, which I really appreciate. The reporting feature is very comprehensive, showing a lot of stats and metrics. It's also super easy to understand what percentage of the audience has been served what variations. Plus, LaunchDarkly has an SDK that integrates very well with our application, making it all seamless. The initial setup was very easy too.

What do you dislike about the product?

I find MCP does not support team users well, and it wasn't easy for me to use LaunchDarkly's MCP with Claude Code due to the enterprise settings. I also find the access control complex.

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

I use LaunchDarkly to enable features without code deployment and serve variations based on user and other factors. Its intuitive UI and comprehensive reporting make it easy to understand audience reach.

What do you like best about the product?

The customizable rules, and the evaluation history chart.

What do you dislike about the product?

the initialization takes time in the code

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

release in confidence and release control

What do you like best about the product?

makes rolling out features pretty easy without having to build your own infra

What do you dislike about the product?

cost structure pretty confusing and requires you to reinvent a lot of things to make it work cleanly

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

making feature rollouts easy without having to think

What do you like best about the product?

The thing that changed how we ship is being able to deploy and release separately. We put a whole customer-facing chat widget into production completely dark behind a flag that defaulted to off, merging it changed nothing for real users, which meant the code stopped rotting on a branch while we waited on a product decision. Custom context attributes are the other big one: we pass country, partner type and access level into the context, so we can roll a feature out to one country or one partner segment without touching code. Targeting changes take effect in the running app in seconds via the streaming connection, no redeploy. JSON flags carrying config payloads (not just booleans) have also saved us a couple of releases.

What do you dislike about the product?

Client-side initialization is the rough edge. bootstrap: 'localStorage' doesn't reliably hand you every flag before first render, so we ended up hand-rolling our own flag cache in localStorage on one app to avoid UI flicker on load — that's a known, long-standing SDK issue and it should really be solved in the SDK. In our Nuxt app we also had to write a retry loop that polls for client readiness because the LD client isn't guaranteed to be up when a component first asks for a flag; a first-class "await ready then subscribe" primitive would remove a lot of fragile glue. Flag cleanup is also on us - nothing nudges you when a flag has been at 100% for six months, so stale flags accumulate.

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

Two things. First, decoupling deploy from release: risky work merges early and ships dark, so we're not sitting on long-lived branches waiting for a sign-off. Second, progressive migration. We're moving users off a legacy Angular portal onto a new one, and a flag decides per user whether they get redirected — which turns a scary big-bang cutover into something we can ramp and instantly roll back. We operate across six countries, so per-country rollout of region-specific forms and features is the other daily benefit, enable in one market, watch it, then widen.

What do you like best about the product?

It makes feature releases easy to control and manage. Feature flags let us roll out changes gradually, in phases or steps. Being able to test features for specific users or email IDs also makes it a flexible option.

What do you dislike about the product?

I don't think there is anything which i dislike, but there are some manageable trade offs given the flexibility the platform provides.

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

The first issue that launchdarkly has resolved is rolling out the functionalities in phases or partially for particular users or for different environments without changing the code again and again..

What do you like best about the product?

What I like most about LaunchDarkly is that it allows separating the deployment from the release of a feature. We can publish code and enable it gradually by users, segments, or percentages, and also disable it immediately if a problem arises. Its interface is clear, the SDKs and integrations with CI/CD processes facilitate implementation, and the performance is stable even in progressive deployments. This reduces risk, avoids complete rollbacks, and accelerates delivery, generating a good return on investment. The documentation and initial support help overcome the learning curve. I also value the intelligent segmentation and A/B testing, because they allow making decisions based on real results.

What do you dislike about the product?

What I like the least is that the interface can become complex when managing many flags, especially because obsolete ones accumulate if there is no cleanup process. The initial setup also requires expertise, and some integrations or SDKs offer different levels of logging and diagnostics. Although performance is usually stable, relying on an external service requires designing backup mechanisms in case of connectivity issues. The price increases rapidly depending on usage, which can affect ROI in large organizations. I would also improve the integrated analytics by incorporating intelligent recommendations to detect unused flags, risks, and optimization opportunities. A more practical onboarding guide would help reduce the learning curve.

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

Before, each release depended on a new deployment, and any failure could force us to do a complete rollback. With LaunchDarkly, on the other hand, we can release the code with the functionality turned off, validate it first with internal users, and then enable it progressively by segments. If a problem arises, we disable it in seconds, without needing to restart the application. This reduces interruptions, speeds up deliveries, and decreases operational work, which translates into a better ROI. Additionally, the integrations with CI/CD and its SDKs help automate the flow, while the interface, documentation, and support make management easier. Finally, A/B testing and segmentation allow us to evaluate real results before extending a feature to all users.

What do you like best about the product?

Easy to use, very clear how to find and selectively activate feature flags.

What do you dislike about the product?

No major issues come to mind. I am able to do the work I need to do in it.

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

It's helping me selectively activate features in environments for customers.

What do you like best about the product?

I have been using LaunchDarkly for our main server to maintain client customizations and business logic. It's really intuitive and flexible, allowing me to easily maintain and update the flags without changing code and going to the database. The best thing about LaunchDarkly is the ability to manage different environments like production, pre-production, and development without creating a flag separately in each environment. It helps me route users to dedicated databases and switch users under one client to a different region, and any client customization is directly served from LaunchDarkly. The initial setup was very easy; we just asked our IT team to get access and simply started adding flags.

What do you dislike about the product?

I find it could be a bit easier to create and delete through the SDK.

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

I use LaunchDarkly to easily maintain and update flags without changing code, manage different environments effortlessly, and route users to the right databases. It's intuitive and flexible, handling client customizations effectively.