Sold by
LaunchDarkly
Accelerate innovation at AI scale by using LaunchDarkly for your front-end and back-end feature releases on AWS, including AI applications using Amazon Bedrock and AgentCore!
Reviews (917)
nethra k.
Easy-to-Use Feature Flags with Flexible Audience Scaling
Reviewed on Oct 26, 2026
Review provided by G2
What do you like best about the product?
I like LaunchDarkly’s ease of use and scaling options. I can scale a feature to different target segments, and the initial setup was pretty easy.
What do you dislike about the product?
ease of use
What problems is the product solving and how is that benefiting you?
I use LaunchDarkly to turn features on and off and run A/B tests.
Anonymous
Flexible Rollouts, but A/B Testing Needs Better Guidance
Reviewed on Oct 21, 2026
Review provided by G2
What do you like best about the product?
I use LaunchDarkly to feature-flag new features so we can test them before rollout and roll them out incrementally. I like having temporary flags for feature rollouts and more permanent flags for client customizations. I also like the different rollout options, such as rolling out by a percentage or by a number of companies, since the right option depends on the feature. I can roll things out carefully, test features, and gate them to specific clients. My personal setup when I first logged in was pretty easy.
What do you dislike about the product?
I’ve been trying to learn how to better A/B test features in LaunchDarkly, but I don’t feel properly trained and haven’t found a successful method yet. Our organization’s setup also makes it hard to distinguish between users and make sure the traffic split is exactly the percentage we want. More in-app education, like a help article or demo video when I open a new area or use a new feature, would make it easier to learn. It may already exist somewhere, but it would be easier if it were right there.
What problems is the product solving and how is that benefiting you?
I use LaunchDarkly to better test features, gate them to specific clients, and roll them out incrementally by percentage or number of companies to avoid rollout problems. Temporary flags help with feature rollouts, and permanent flags are useful for client customizations.
Computer Software
Super Helpful for Feature Rollouts
Reviewed on Oct 21, 2026
Review provided by G2
What do you like best about the product?
Super helpful for rollout of new features and for doing production evals by splitting traffic down different routes.
What do you dislike about the product?
As an engineer, there isn't much I dislike. The only negative experience I've had was the LD outage about 2 months ago.
What problems is the product solving and how is that benefiting you?
Solving issues with rollout when working on new features.
Shubham singh C.
LaunchDarkly Makes Progressive Delivery in Salesforce Predictable and Low-Drama
Reviewed on Oct 21, 2026
Review provided by G2
What do you like best about the product?
What stands out most is how cleanly LaunchDarkly shifts our release strategy from high-risk, all-at-once deployments to controlled, progressive delivery. In an enterprise Salesforce environment, production deployments are usually rigid: they demand tight maintenance windows, extensive pre-deployment testing, and complicated rollback pipelines if something goes wrong. LaunchDarkly helps by fully decoupling the physical code deployment from the business activation.
By wrapping new Lightning Web Components and backend integrations behind LaunchDarkly flags, we can merge production-ready code into our main branch days ahead of time without immediately exposing it to users. From there, we can activate features progressively, validate performance in real, live conditions, and fall back on an instant kill switch if needed. That separation between shipping code and turning it on transforms high-stress release cycles into predictable, low-drama rollouts.
By wrapping new Lightning Web Components and backend integrations behind LaunchDarkly flags, we can merge production-ready code into our main branch days ahead of time without immediately exposing it to users. From there, we can activate features progressively, validate performance in real, live conditions, and fall back on an instant kill switch if needed. That separation between shipping code and turning it on transforms high-stress release cycles into predictable, low-drama rollouts.
What do you dislike about the product?
The platform demands strict operational hygiene around feature-flag lifecycle governance. Because creating a toggle is so effortless, stale flags can quickly pile up in both your codebase and the LaunchDarkly workspace if the engineering team doesn’t consistently build cleanup tasks into the sprint cycle. When abandoned toggles are left behind, they create technical debt and lead to unnecessary conditional branching throughout component code. In addition, setting up granular user-targeting rules—especially when they rely on nested contextual attributes—takes deliberate planning and a solid understanding of how your context structures are defined and used.
What problems is the product solving and how is that benefiting you?
It takes the stress out of “big bang” releases where everyone gets hit with a major change all at once.
In the past, rolling out a large update—like our new checkout screen and real-time tax calculation—meant pushing it to every sales rep on day one. If some weird edge-case bug showed up, our only option was an emergency hotfix deployment. That usually led to at least an hour of scrambling while the sales team was stuck dealing with broken screens.
With LaunchDarkly, we can do small canary rollouts directly on our Salesforce pages. We enable the new interface for just 5–10% of our super-users first, watch how it behaves under real-world usage, and keep everyone else on the standard, working screen. Best of all, if the backend slows down or something breaks, we can flip the switch back to the old screen in a second—without redeploying code or disrupting the business.
In the past, rolling out a large update—like our new checkout screen and real-time tax calculation—meant pushing it to every sales rep on day one. If some weird edge-case bug showed up, our only option was an emergency hotfix deployment. That usually led to at least an hour of scrambling while the sales team was stuck dealing with broken screens.
With LaunchDarkly, we can do small canary rollouts directly on our Salesforce pages. We enable the new interface for just 5–10% of our super-users first, watch how it behaves under real-world usage, and keep everyone else on the standard, working screen. Best of all, if the backend slows down or something breaks, we can flip the switch back to the old screen in a second—without redeploying code or disrupting the business.
Computer Software
Clean, Easy-to-Integrate Feature Flags, But Needs more flag cleanup features.
Reviewed on Oct 21, 2026
Review provided by G2
What do you like best about the product?
I like having control over how we roll out features gradually, especially for test teams. LaunchDarkly gives me visibility into how launches are doing, including evaluations and which users are on each feature flag or version. The interface is super easy to use and clean, integrating it with our code is super easy, and the SDKs are really well designed. It saves us time when we manage these things. Having an MCP is pretty useful, and maintaining the setup has been pretty seamless.
What do you dislike about the product?
My biggest concern with LaunchDarkly is planning for when it's offline. During the recent outage we had a lot of flags falling back to bad defaults, so a lot of features were turned off. It would be great to have more features that could highlight this and alert us for flags that should be removed or phased out.
What problems is the product solving and how is that benefiting you?
I use LaunchDarkly to control how we roll features out and see how launches are doing, including evaluations and how many users are on each feature flag or version.
Himanshu R.
Simple Feature Flag Creation Across All Environments
Reviewed on Oct 21, 2026
Review provided by G2
What do you like best about the product?
The simplicity and ease of creating flag in one environment and get it for all the environments without configuring it again for each one.
What do you dislike about the product?
Sometimes it is difficult to search for the exact flag I am looking for.
What problems is the product solving and how is that benefiting you?
Controlling which users see what change after a release so that we can limit the blast radius.
Anonymous
Easy Configuration Management, but a Surprisingly Low Recommendation Score
Reviewed on Oct 20, 2026
Review provided by G2
What do you like best about the product?
I’ve had a really nice time using LaunchDarkly. The interface and user experience are easy to use, and everything works well with good uptime. I like the configuration manager because it’s easy to use and helps me do that part of my job. I can manage configurations and choose what goes out to each of our clients. The initial setup was easy, and I haven’t had any issues with it.
What do you dislike about the product?
Nothing
What problems is the product solving and how is that benefiting you?
I use LaunchDarkly to manage configurations and choose which configuration or product version goes out to each client.
Luis Bravo
Feature flags and AI prompts have enabled rapid config changes and faster experimentation
Reviewed on Oct 20, 2026
Review provided by PeerSpot
What is our primary use case?
I use LaunchDarkly for feature flags to turn on and off features that we deploy into production. I have also used LaunchDarkly to manage AI in production. We're using it for AI config, which are basically the prompts. So we are using it for flags and we also use it for the prompts, to store the prompts.
How has it helped my organization?
LaunchDarkly has helped me solve the challenge of iterating quickly on prompts and instructions. Having the instructions and prompts in LaunchDarkly makes it fast to iterate and just like flags, I can go into a UI and make the change, rather than having to deploy code, because the CI workflows tend to be a lot slower. We ended up wanting to have the instructions as code anyway, so we had to work on a specific pipeline to be able to still store that from our side as code and also publish it to LaunchDarkly. The main advantage is the same as the flag's flexibility—basically being able to change it quickly without having to actually wait for a PR to be merged and something to be deployed.
What is most valuable?
LaunchDarkly works well and it's nice to have the control of a feature flag as a whole. It's very handy. The only thing that I would like is a more structured way to visualize the flags, especially when you end up having too many flags and there is some hierarchy. The UI and the way that it is presented is very flat. When you end up having structures and dependencies on flags, there is no dashboard that would give you exactly what you want, especially when you're working on a particular project. Because the way that we have in our organization is that we have multiple products, multiple features and multiple teams that are working on features. You end up having a lot of different flags that are presented in a flat manner, and you may have a main one that when it is turned on, the child ones are evaluated based on it, and you may have many depths on that relationship. If there were a dashboard or a certain view that would make that structure apparent and very obvious, it would be useful.
Also, because you have different values depending on whichever environment that you're interested in, you have to actually dig into what are the relevant flags and then go to a particular environment that you are focused on. If there would be some sort of dashboard that would give you all of that as a whole, not individually by flag, but as a whole structure is constructed and your interest checked on, it would be handy from the flag side.
What needs improvement?
I would like to see all of the flags and their relationships and I would like to see a tree type view. As a developer, I may be working on a particular piece from a particular team. If I'm able to just group them the right way based on the hierarchy of the flag and just select the particular feature that I'm working on and only see that and see all of the hierarchy, and also see all of the values based on the environment that I am interested in at a glance, would be very handy and that would save a lot of time.
For how long have I used the solution?
I have been using LaunchDarkly for maybe six months overall. I have been working in my current field for seventeen years.
What do I think about the stability of the solution?
There was one time that there was an outage, and we had to act on it because the default that we were getting actually ended up breaking some other feature.
What do I think about the scalability of the solution?
I am not aware of any performance issues, but I am aware of one time that there was an outage and we had to act on it to fix it.
How are customer service and support?
We have a thread in Slack where we are raising issues directly to LaunchDarkly support. I'm not really involved in that, but I do know that this thread exists.
Which solution did I use previously and why did I switch?
I have used an in-house solution previously. Comparing to that, LaunchDarkly is very feature rich, but it's basically because we were doing it ourselves. We are also using LaunchDarkly for AI configuration and that also seems intuitive, but it also ends up suffering from the same symptom of having everything be very flat. We have been having issues with certain variations of AI config being too large. There is a certain limit that LaunchDarkly imposes on how much you're able to post as a variation for an AI config. We have been having a lot of issues with that recently. We did a migration from the in-house solution to LaunchDarkly.
How was the initial setup?
I didn't actually do the platform part, but from my point of view, I was just moving existing flags to be in LaunchDarkly flags. I didn't do any work regarding that, but because it was already taken care of, I was just using the flags.
What about the implementation team?
There's a platform team that is taking care of the maintenance side, so it doesn't require maintenance on my end.
What was our ROI?
I wouldn't be in the position to actually compare metrics, but LaunchDarkly seems to be pretty performant. The client in the browser gets the events fairly quickly.
What other advice do I have?
I give LaunchDarkly a rating of eight out of ten overall for everything.
Dhiman S.
Reliable Feature Flags, but Flag Sprawl Drives Costs
Reviewed on Oct 20, 2026
Review provided by G2
What do you like best about the product?
I love the experience and smart features like the default fallback in the SDKs. I don’t need to worry about caching, and I get guaranteed SLAs. It frees me to focus on solving my business problem instead of worrying about whether feature flags or configuration will scale. I also use feature flags for rollouts and rollbacks without deployment.
What do you dislike about the product?
As our team and features scale, there isn’t enough emphasis on cleaning up feature flags or maintaining flag hygiene. Since LaunchDarkly charges based on the number of flags, costs keep growing, and we end up jailing teams that have more than a set number of flags.
What problems is the product solving and how is that benefiting you?
I use LaunchDarkly for feature flags, rollouts, and rollbacks without deployment.
Oren B.
Simple, Reliable Feature Rollouts with Flexible Controls
Reviewed on Oct 20, 2026
Review provided by G2
What do you like best about the product?
I like that LaunchDarkly is modular but simple enough to use, scalable, and reliable. It’s configurable for tests, gradual rollouts, releases to specific customers, and internal testing without complex setup. Once it’s integrated, it works as part of my app. The initial setup was easy enough and a one-time effort.
What do you dislike about the product?
Nothing, all is great
What problems is the product solving and how is that benefiting you?
I use LaunchDarkly for control and governance, and to make the rollout process more reliable and resilient.