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 (887)
Dmytro M.
Flexible, Low-Complexity Feature Flags and Rollouts That Just Work
Reviewed on Oct 08, 2026
Review provided by G2
What do you like best about the product?
Great, flexible, low cognitive complexity to understand tool for dynamic config, feature flags and rollout
What do you dislike about the product?
Nothing really from POV, never had a problem related to core functionality
What problems is the product solving and how is that benefiting you?
Feature flags, rollout features, shared dynamic config for apps can't develop app without these
Banking
Safely Releases New Features in Production Without Breaking the App
Reviewed on Oct 06, 2026
Review provided by G2
What do you like best about the product?
It’s very helpful for releasing new features in production without breaking the app.
What do you dislike about the product?
So far, I can’t think of anything that has annoyed me while using LaunchDarkly.
What problems is the product solving and how is that benefiting you?
Before using LaunchDarkly, I used to release new features directly in the application, which could sometimes cause breaks or even outages. Now I can easily prevent that from happening by simply enabling or disabling a flag.
Computer & Network Security
Very Stable and Agentic-Friendly—Works as Expected
Reviewed on Oct 04, 2026
Review provided by G2
What do you like best about the product?
It's very stable, agentic friendly, work as expected
What do you dislike about the product?
Actually nothing comes to my mind. I would say figuring out how to evaluate with the context is a bit confusing
What problems is the product solving and how is that benefiting you?
it helps rolling out features slowly
Information Technology and Services
Effortless Feature Rollouts and Quick Rollbacks with LaunchDarkly
Reviewed on Oct 02, 2026
Review provided by G2
What do you like best about the product?
What I like most about LaunchDarkly is how easy it makes feature releases and rollouts. Being able to control features without having to deploy new code is really useful, especially when testing something progressively or rolling it back quickly.
What do you dislike about the product?
Not much, honestly. It’s pretty useful and I haven’t really run into any major issues with it.
What problems is the product solving and how is that benefiting you?
It makes it easier to release and test features without having to deploy every time. We can roll things out gradually, turn features on or off, and reduce the risk of breaking things for everyone at once.
Stephen P.
Effortless Feature Management with LaunchDarkly
Reviewed on Oct 02, 2026
Review provided by G2
What do you like best about the product?
I love how LaunchDarkly is easy to use and super straightforward. It's great that you can just land in the UI and make sense of it right away, without needing to do any deep dives or extensive learning. This usability is really valuable for our small team of five engineers because we don't always have the time to learn complex tools. Being able to hop in and start efficiently with a SaaS product like LaunchDarkly is a huge benefit.
What do you dislike about the product?
I don't see another way around it, but the end of the feature flag life cycle can be a chore. I know Launch Darkly has tools to help identity stale flags in code, which is nice.
What problems is the product solving and how is that benefiting you?
LaunchDarkly lets us build features incrementally while deploying to production often. It's super straightforward, requiring no deep learning, which is great for our small team of five engineers to use efficiently. It's really valuable for getting started quickly.
Computer & Network Security
Clear, Comfortable UI Makes Flag Management Effortless
Reviewed on Oct 02, 2026
Review provided by G2
What do you like best about the product?
it's ui is very clear and comfortable. it's really easy to enable/disable flags
What do you dislike about the product?
had some degradation issues at one point, but the LaunchDarkly relay fixed it.
What problems is the product solving and how is that benefiting you?
easy flags switch
Giovanni Portogallo
Feature flags have simplified gradual rollouts and support safe checkout experiments in production
Reviewed on Sep 30, 2026
Review provided by PeerSpot
What is our primary use case?
My use cases for LaunchDarkly involve managing risk from new features such as AB testing and canary releases for features with gradual rollouts. This type of work is fundamentally about managing risk and testing new features.
I haven't used LaunchDarkly to manage any AI in production; the only thing I've used it for is feature flags for the most part.
What is most valuable?
What stands out to me about LaunchDarkly is that it's super easy to use. I appreciate that you can serve the feature at a percentage and that you can add users by email. For example, I used it in the past to do internal-only testing of the feature in production, which was very helpful.
From what I've seen, the management of feature flags in LaunchDarkly is pretty good. I don't have any other reference point to compare it to, but it's pretty simple to create a new flag and then edit the flag and increase or decrease traffic to that flag. I'm not an expert on feature testing, but for what I've used, it works for what I needed.
What needs improvement?
If LaunchDarkly goes down and you don't have it set up right, it could be a problem for you. I think that's a little bit on user error as well.
I would like some sort of a local instance to be available.
For how long have I used the solution?
I've been working with LaunchDarkly overall for at least a few years, probably around three years.
What do I think about the stability of the solution?
I've seen lagging, crashing, or downtime with LaunchDarkly. There was an outage, and that's what I was referring to. If there's ever an outage, I think you can define a default experience in your code, but I don't think we did that well. It might have reverted to an experience that we did not want the customers to see. For instance, my company developed a new version of our checkout page, and it was behind a LaunchDarkly flag, but it was serving 100% traffic to that flag. But when LaunchDarkly went down, it started using the prior checkout page, which is not as good of a page, which is why I'm saying that it's a problem if LaunchDarkly goes down.
What do I think about the scalability of the solution?
Regarding scalability, I think LaunchDarkly is pretty scalable. I've never had issues with it scaling.
Which solution did I use previously and why did I switch?
I've never actually used anything similar to LaunchDarkly, but I'm aware that there are competitors; however, LaunchDarkly is the only one that I've used.
How was the initial setup?
The initial deployment of LaunchDarkly was handled by a platform team that managed that initial setup, but as far as integrating it to my service, it's pretty easy to just create a LaunchDarkly client, much like any other type of client for any external software that you use, and then just go ahead and start using the flags.
What other advice do I have?
LaunchDarkly usually does not require any maintenance on my end. It's usually taken care of. The only time we have maintenance is if we're not using any flag anymore, or we make it a permanent feature instead of a feature flag; then we'd have to go into the code and clean it up to delete the flags and then delete it from LaunchDarkly. But in terms of maintenance outside of that, there isn't much required.
On a scale from 1 to 10, I would give LaunchDarkly an 8. I would definitely recommend it to another customer. It's always worked for me, except there have been outages here and there, but very rarely. I'd say it's pretty good for the most part.
Kirpalsinh R.
Emergency incident kill switches and SIEM-integrated deployment auditing
Reviewed on Sep 30, 2026
Review provided by G2
What do you like best about the product?
From a Security Operations Center (SOC) perspective, LaunchDarkly transforms how we handle active incident response and vulnerability containment. Typically, if a newly deployed feature is found to be actively exploited or leaking data, the SOC has to coordinate with engineering to initiate a full CI/CD pipeline rollback, which can take anywhere from 15 to 45 minutes. LaunchDarkly acts as an instantaneous emergency kill switch. We can immediately toggle off the vulnerable code path in milliseconds without deploying new code or restarting services. Furthermore, its native Data Export capabilities stream all feature flag evaluation and modification logs directly into our SIEM. This provides our security analysts with a definitive, real-time audit trail of exactly which developer toggled which feature in production, crucial for post-incident forensics.
What do you dislike about the product?
The platform easily facilitates the accumulation of stale feature flags, which inadvertently expands our application's attack surface. When developers forget to clean up old flags, it creates dormant code paths in production that could theoretically be exploited if an attacker manages to hijack an API key or manipulate client-side evaluations. Additionally, managing granular Role-Based Access Control (RBAC) across hundreds of microservices and thousands of flags is incredibly complex. Ensuring that junior developers don't have the permissions to toggle critical security or infrastructure flags in the production environment requires constant auditing and rigid policy enforcement.
What problems is the product solving and how is that benefiting you?
It drastically reduces our Mean Time To Contain (MTTC) during severe security incidents. Before integrating LaunchDarkly into our DevSecOps workflows, stopping a bleeding vulnerability required blocking IP ranges at the WAF or waiting for an emergency hotfix to compile and deploy. Now, our incident response playbooks include securely flipping LaunchDarkly kill switches, allowing us to instantly isolate vulnerable micro-features while keeping the rest of the application online and functional for users.
Pranjal E.
Safer releases, one customer at a time
Reviewed on Sep 29, 2026
Review provided by G2
What do you like best about the product?
The biggest value is shipping risky fixes to production turned off, then turning them on for one customer at a time across our many environments. Rolling back is a toggle, not a redeploy, so we ship faster with less risk. The REST API is excellent. We script almost all flag work and built a daily Slack digest on it to catch stale or partly rolled-out flags. Flags have become our release process, and the ROI shows up in emergency rollbacks we never had to do.
What do you dislike about the product?
Targeting is easy to get wrong. Individual targets are stored apart from rules, and new rules default to the "user" context kind, which can silently match nothing. Stale-flag cleanup is left to us, so we built our own digest. It's also hard to see what flag value a long-running worker actually evaluated. Warnings on rules that can't match and built-in stale-flag tracking would help a lot.
What problems is the product solving and how is that benefiting you?
It keeps a code fix separate from the decision to release it. We merge fixes to production turned off, turn them on for one customer to verify, then roll out everywhere. If something breaks, we turn the flag off instead of redeploying. We ship fixes faster, customer-specific issues can be tested safely in production, and bad releases have a much smaller impact.
Computer Software
Intuitive Feature Flags for Easy Testing and Key-Based Targeting
Reviewed on Sep 28, 2026
Review provided by G2
What do you like best about the product?
Easy to test out important software changes using flags. Interface is pretty intuitive and like having the option to decide based off different keys
What do you dislike about the product?
Would like more detail sometimes about exactly what was evaluated. What was sent to the LD client in order to give a particular evaluation and where it came from. The standard monitoring of number of false or true is ok, but sometimes if you are trying to debug it's not enough
What problems is the product solving and how is that benefiting you?
Reducing risk in critical software changes. Also, sometimes if we need to roll out a feature quickly and can't build the full flow for it in our system. It lets us roll it out for the required client