LaunchDarkly logo

    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!

    Ratings and reviews

    4.5
    912 ratings
    7 AWS reviews
    |
    905 external reviews
    External reviews are from G2  and PeerSpot .

    Filters

    Review type

    AWS Marketplace reviews
    External reviews
    Reviews (912)
    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.
    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.
    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.

    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.
    Education Management

    Automated Monitoring, Progressive Rollouts, and an Incredibly Easy API

    Reviewed on Oct 20, 2026
    Review provided by G2
    What do you like best about the product?
    automated monitoring and progressive rollouts are great. I love the API as well, incredibly easy to use with AI
    What do you dislike about the product?
    I'd love for the targeting search field to better fuzzy match, and suggest facets better. When I search for a target, sometimes I'm not entirely sure what the exact client name is for example.
    What problems is the product solving and how is that benefiting you?
    It solves the gradual rollout for me, and letting the rest of the organization control features and risky changes as they roll.
    Consulting

    Straightforward, Easy-to-Navigate Interface That Simplifies Feature Search

    Reviewed on Oct 19, 2026
    Review provided by G2
    What do you like best about the product?
    I find LaunchDarkly’s interface really straightforward. It makes it easy to search for features and tickets across our organization, and overall the navigation feels simple and clear.
    What do you dislike about the product?
    There is a learning curve when you start onboarding onto the tool and learning where everything.
    What problems is the product solving and how is that benefiting you?
    LaunchDarkly is my go-to system when I want to understand the different experiences our customers are having. It makes it easier to talk with customers and get a clearer picture of their pain points.
    Jonathan Barson

    Feature flags have enabled cautious rollouts and have supported fast, coordinated launches

    Reviewed on Oct 16, 2026
    Review provided by PeerSpot

    What is our primary use case?

    Regarding my use cases, I am cautious about breaking customers in production, so I generally put LaunchDarkly flags on pretty much any feature that is going to be rolled out to production to slowly roll things out and ensure nothing is broken. Additionally, it is valuable for developing a new feature and then launching it all at once when it is ready to go, so I do both of those.

    I am not using LaunchDarkly to manage any AI in production, as other teams may be doing that. At the moment, my use of AI is limited to coding assistance, while other teams are integrating AI into the product.

    What is most valuable?

    What I appreciate most about LaunchDarkly is that it is very easy to use. I estimate I have around 30 flags, though I have not counted them recently. Finding the flags is straightforward; I search for the flag I need and then proceed with the setup for whatever I need to do. One useful aspect for my workflow is that whenever I set a flag or change something, I ask my coding LLM to confirm that everything is working as it should, whether it is to catch a typo or ensure I did not add the wrong merchant ID.

    What needs improvement?

    What I dislike about LaunchDarkly is the inability to quickly find all the flags I have currently running and their statuses. I want to know if they are rolled out partially, but I have to check externally by asking my coding agent about all my LaunchDarkly flags and their statuses. Recently, I forgot about a flag I rolled out to a couple of merchants, and I noticed I was not alone; several people had flags running for months with only one or two merchants enabled. A feature to alert me if a flag is underutilized or needs attention after a week of being rolled out would be beneficial.

    For how long have I used the solution?

    Overall, I have been working with LaunchDarkly for a couple of years, having used it at Instacart and currently at Thanks, but it was not utilized at Thomson Reuters. I have a couple of years of experience with it.

    What do I think about the scalability of the solution?

    I have not encountered any scalability issues with LaunchDarkly. I work for a mid-sized company with hundreds or thousands of users, and I have not run into scalability issues here. While my experience at Instacart might have been different, I was not using it as in-depth as I do now. I currently use LaunchDarkly on a daily basis.

    What other advice do I have?

    I have not integrated any other tools with LaunchDarkly; it stands by itself in my usage.

    Other than the server that checks the status whenever I request it, which saves me from going directly to LaunchDarkly, I do not have additional tools integrated.

    I would give LaunchDarkly a rating of nine out of ten because I never give out tens, as that implies no room for improvement, and everybody can improve. Overall, LaunchDarkly is good; it is easy to use, and I can see what is happening relatively quickly.

    Computer Software

    Vega Unreliable: Slow Trace Loading, Missing Data, and Hard-to-Find Sessions

    Reviewed on Oct 16, 2026
    Review provided by G2
    What do you like best about the product?
    In some cases, I’m able to view logged API responses. Searching for sessions is also pretty straightforward, especially if you already know the time and the user you’re trying to find.
    What do you dislike about the product?
    Vega hasn’t been working for me at all. If you don’t know exactly who you’re looking for and when, sessions are very hard to find. LaunchDarkly flags can also be difficult to track down, including the rules and where they’re being served from. Often I can find a session, but then there’s no information in the trace data, so it’s practically useless. On top of that, loading traces is very slow and hit-or-miss.
    What problems is the product solving and how is that benefiting you?
    I usually review session replays to see what the API calls contain and check whether anything looks off.