LaunchDarkly can be improved by managing old flags. We have an issue with old flags; it became very messy very fast and we need to be very disciplined about managing these flags. I also heard from the manager that it was very expensive when the usage grew. Perhaps LaunchDarkly could mark old flags somehow or add a tag to these flags when they are not in use or have not been used for a long time. We found ourselves after a short period of time having too many flags.
I think LaunchDarkly's customer support can be improved as it is not responsive. I do not have anything else specific to add about needed improvements besides customer support.
Staff Software Engineer at a wholesaler/distributor with 10,001+ employees
Real User
Top 10
Oct 22, 2025
I wish we were using more targeting in our feature toggles and I wish we were using more feature toggles as well as feature toggle dependencies. Making one feature toggle or one set of feature toggles dependent on another one would allow us to turn them all on or turn them all off at one time. For improvements in LaunchDarkly, managing team members and access to those team members was challenging. We could add team members through Terraform and do it programmatically, and then modify it through the user interface. However, once we started modifying things through the interface, we weren't able to go back to using any configuration programmatically for the team members. It made it challenging to orchestrate team member management. The other aspect I wasn't particularly fond of was when they started adding AI to the interface and deployment interface. It reminded me of old school wizards when installing software and simplified the interface too much, removing some of the engineering control I preferred.
When the system has an excessive number of feature flags, managing them can become cumbersome. It would be helpful to have UI elements that make this easier, such as tracking feature flag usage, the duration that feature flags have been open, and generating reports. You need some experience to get used to it. There's a bit of a learning curve, but it is easier for people with a technical background,
LaunchDarkly currently lacks multi-region support. I strongly believe they need to develop a strategy for handling situations where LaunchDarkly goes down. They should have a backup URL and collaborate with other engineers to ensure availability. There should be a fail-over strategy in place. My understanding is that a multi-region real-time solution isn't available yet. Another future enhancement I envision is having the entire application property load through LaunchDarkly. This integration would be advantageous but needs to be designed to be very user-friendly and serviceable. I use a dashboard. I see some improvements happening, but it's a little bit cluttered. It even needs to be improved because certain kinds of levels of fields are added. So they need to make it very user-friendly, that kind of thing. So, LaunchDarkly really has to play around and make it very user-friendly. I expect certain behavior from the tool, but it gives me false results. I know I need to play around with all the properties, and then I can go to what it takes. It's not a tool that a non-technical person can use. Like, whoever is a non-technical person can also easily able to understand what they want to do; that kind of thing used to be taken as part of the dashboard (cloud dashboard), which is wherever we are enabled with your feature, like, so because If you go inside the plans, it has, like, a certain level of conditions and operations. So sometimes it works well, sometimes it doesn't work. So everyone has to understand. So, that needs to be very precise.
LaunchDarkly is the runtime control platform for the AI era. It includes two solutions: CodeControl and AgentControl. CodeControl helps teams ship AI-generated code safely with feature flags, progressive rollouts, observability, experimentation, and automatic recovery—so they can move fast without losing control. AgentControl helps teams manage AI agents in production by configuring prompts and models, monitoring behavior, and taking action in real time without redeploying. Together, they...
LaunchDarkly can be improved by managing old flags. We have an issue with old flags; it became very messy very fast and we need to be very disciplined about managing these flags. I also heard from the manager that it was very expensive when the usage grew. Perhaps LaunchDarkly could mark old flags somehow or add a tag to these flags when they are not in use or have not been used for a long time. We found ourselves after a short period of time having too many flags.
I think LaunchDarkly's customer support can be improved as it is not responsive. I do not have anything else specific to add about needed improvements besides customer support.
I wish we were using more targeting in our feature toggles and I wish we were using more feature toggles as well as feature toggle dependencies. Making one feature toggle or one set of feature toggles dependent on another one would allow us to turn them all on or turn them all off at one time. For improvements in LaunchDarkly, managing team members and access to those team members was challenging. We could add team members through Terraform and do it programmatically, and then modify it through the user interface. However, once we started modifying things through the interface, we weren't able to go back to using any configuration programmatically for the team members. It made it challenging to orchestrate team member management. The other aspect I wasn't particularly fond of was when they started adding AI to the interface and deployment interface. It reminded me of old school wizards when installing software and simplified the interface too much, removing some of the engineering control I preferred.
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.
As of now, I do not see much room for improvement. 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. It would be helpful to have UI elements that make this easier, such as tracking feature flag usage, the duration that feature flags have been open, and generating reports. You need some experience to get used to it. There's a bit of a learning curve, but it is easier for people with a technical background,
LaunchDarkly currently lacks multi-region support. I strongly believe they need to develop a strategy for handling situations where LaunchDarkly goes down. They should have a backup URL and collaborate with other engineers to ensure availability. There should be a fail-over strategy in place. My understanding is that a multi-region real-time solution isn't available yet. Another future enhancement I envision is having the entire application property load through LaunchDarkly. This integration would be advantageous but needs to be designed to be very user-friendly and serviceable. I use a dashboard. I see some improvements happening, but it's a little bit cluttered. It even needs to be improved because certain kinds of levels of fields are added. So they need to make it very user-friendly, that kind of thing. So, LaunchDarkly really has to play around and make it very user-friendly. I expect certain behavior from the tool, but it gives me false results. I know I need to play around with all the properties, and then I can go to what it takes. It's not a tool that a non-technical person can use. Like, whoever is a non-technical person can also easily able to understand what they want to do; that kind of thing used to be taken as part of the dashboard (cloud dashboard), which is wherever we are enabled with your feature, like, so because If you go inside the plans, it has, like, a certain level of conditions and operations. So sometimes it works well, sometimes it doesn't work. So everyone has to understand. So, that needs to be very precise.