LaunchDarkly

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 really like the UI interface of LaunchDarkly, especially the dark mode and the cool contrast between colors. It's very visible and apparent when switching from staging to production to beta. I appreciate how easy it is to toggle features on and off, even when something is live in production. The API is very easy to configure, making it simple to add new flags or segments. The ease of access stands out as well, allowing people who are not very tech-savvy, like designers and ML folks, to use it seamlessly.

What do you dislike about the product?

I find it a bit hard to work with the API access on LaunchDarkly. I would prefer if it were easier to work off with my agent and let Claude handle most of the toggling and adding segments. The ease of accessing the API could be improved.

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

LaunchDarkly helps me segregate users and enable features easily with toggles. The UI is intuitive, making it simple for non-tech savvy users, while the API helps in managing flags and segments efficiently.

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 like how easy it is to manage feature flags and control rollouts safely.

What do you dislike about the product?

The UI can feel a bit overwhelming when managing many flags and environments.

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

LaunchDarkly solves the challenge of safely releasing features and managing them across environments. It gives me better control over rollouts, reduces deployment risk, and lets me enable or disable features without redeploying.