LaunchDarkly - Pay As You Go Foundation logo

    LaunchDarkly - Pay As You Go Foundation

    LaunchDarkly allows you to manage feature flags, progressive delivery, experimentation, and AI agents for teams building on AWS. Pay as you go, billed through AWS. Start with a 30-day free trial.

    Ratings and reviews

    4.1
    24 ratings
    2 star
    1 star
    46%
    50%
    4%
    0%
    0%
    9 AWS reviews
    |
    15 external reviews
    External reviews are from PeerSpot .

    Filters

    Review type

    AWS Marketplace reviews
    External reviews
    Reviews (24)
    RaviPrakash1

    Feature flags have enabled controlled rollouts and have improved phased business validation

    Reviewed on Nov 11, 2026
    Review provided by PeerSpot

    What is our primary use case?

    My main use case for LaunchDarkly is managing the controlled rollout of capability in my in-house application named Escrow Navigator, a conversational assistant that helps the escrow team retrieve and interpret order information and documents. My use case includes enabling new document upload capability, introducing support for additional file formats, and allowing users to ask questions about newly uploaded documents without selecting them again. As a Lead Business Analyst, I define rollout requirements, document acceptance criteria, and coordinate validation with development, QA, and business stakeholders, focusing on feature behavior and release readiness rather than SDK implementation.

    LaunchDarkly helps us manage the rollout of new features by using feature flags and user tagging, which are the most valuable capabilities for our workflow. These capabilities allow us to make a capability available to a pilot group while other users continue with the existing experience. For example, when introducing questions about newly uploaded files, we can enable the capability for designated testers, allowing them to validate upload status, document processing, conversation association, and citation before we expand access. This gives us a practical way to gather feedback on a complete business workflow.

    How has it helped my organization?

    LaunchDarkly has positively impacted our organization by helping our team introduce new capabilities through controlled phase releases, making features available to selected users, gathering feedback, and validating business requirements before expanding access. This improves coordination between business development and QA teams and gives us greater control over release readiness. The main organizational benefit is increased confidence when introducing changes while limiting the number of users exposed to potential issues.

    We are currently tracking logs in Power BI to see how much feedback we are receiving, and negative feedback has recently been decreasing. We are more focused on UAT, allowing selected testers to validate newly uploaded questions, citation accuracy, and process status against defined acceptance criteria, which contributes to a greater impact on ROI in our project.

    We have seen great improvement in metrics such as token input and output, and latency has shown significant improvement, particularly in the production environment.

    What is most valuable?

    The best features LaunchDarkly offers include giving us more flexibility in controlling technical deployment with business readiness. A feature can be deployed while access remains limited to the user responsible for validating it. For Escrow Navigator, this supports phase validation for document upload and processing changes, allowing business users to review the experience while QA checks acceptance criteria before broader availability. The main benefit is better control over feature exposure and release coordination, although we have not formally qualified the financial benefit.

    The flexibility helps our team when rolling out features by enabling us to roll out a feature to a lower environment and disable it in a higher environment after some time, allowing us to manage features without conducting a major deployment.

    Regarding the feature flag, in the UI, if we have enabled a feature such as giving feedback, but we want to hide that feature, using LaunchDarkly, we can disable that flag, and it will reflect in the UI immediately. We also manage document upload and document review features via flags, with LaunchDarkly helping us by providing more flexibility in coordinating technical deployment.

    I use LaunchDarkly with GitHub. Our development team utilizes LaunchDarkly alongside GitHub, where GitHub manages our project source code and pull requests while LaunchDarkly controls the availability of features implemented behind flags. This allows teams to merge and deploy code, enabling capability for selected testers before a wider rollout. My role focuses on requirements and UAT validation while the development team handles technical integration.

    What needs improvement?

    From a business validation perspective, I would find a consolidated comparison of flag settings across environments helpful. Understanding differences in configuration and targeting when reviewing a feature in dev, UAT, and production is important, along with clear business descriptions, ownership information, and visibility into flags that are ready for retirement. This would make release review easier for stakeholders who do not work with technical configurations every day.

    If there are links to documentation available, that would be really helpful, especially from a knowledge transfer perspective.

    For how long have I used the solution?

    I have been using LaunchDarkly for around one to two years.

    What do I think about the stability of the solution?

    LaunchDarkly is currently stable, and we have not faced any issues with reliability or downtime.

    What do I think about the scalability of the solution?

    From our project perspective, LaunchDarkly has supported our feature management across environments and pilot user groups without accessibility issues. As usage grows, maintaining clear flag ownership, naming conventions, and cleanup practices becomes essential. I have not personally conducted load testing, and my assessment is based on business validation and release activities.

    How are customer service and support?

    We have not faced issues with customer support, as we have raised tickets and received solutions within the expected SLA timeframe. I also coordinate internally with the development and platform teams who handle any vendor escalations, leading to a good experience overall.

    I rate customer support an eight out of ten.

    Which solution did I use previously and why did I switch?

    Prior to LaunchDarkly, we used an in-house tool that managed feature availability through application configuration settings and coordinated deployments. This led to difficulties as enabling a feature for selected pilot users required additional deployment or configuration work. LaunchDarkly gives us a centralized way to manage feature availability and targeting, making phased rollout much easier to coordinate.

    We previously used an in-house tool for delegated feature management that managed feature availability. My assessment of LaunchDarkly focuses on its support for our requirements in controlled rollout, pilot testing, and business validation, as we no longer need multiple deployments across environments for managing feature access. LaunchDarkly enables us to disable features for users from its settings without the need for deployments.

    What was our ROI?

    We definitely see a return on investment, with operational values in easier pilot releases, more focused UAT, and greater control over feature availability, although we have not formally measured financial ROI or confirmed specific amounts saved. The benefits assessed could reduce release coordination efforts and rework, but supporting data is needed to translate them into concrete cost savings.

    What's my experience with pricing, setup cost, and licensing?

    From a BA perspective, I assess value through the flexibility it provides for controlling release and pilot testing. My role in setup revolves around defining rollout requirements, identifying pilot users, and validating the enabling and disabling of feature behavior in Escrow Navigator, as the development team manages technical integration and configuration.

    Which other solutions did I evaluate?

    Compared to our previous approach of managing features through application configuration and deployment, LaunchDarkly stands out by offering more flexibility for controlled release and pilot testing. For Escrow Navigator, its main value is enabling selected users to validate new capabilities before wider availability, fitting projects that need phased rollout and clear release governance, though I have not conducted a formal evaluation of competing platforms.

    What other advice do I have?

    I would rate LaunchDarkly an eight out of ten.

    I chose an eight because of the flexibility I have discussed earlier, along with the capability of supporting multiple environments, which I find good. However, since I am not sure about pricing, I do not give it a ten. In the future, when I have more understanding of pricing, I would definitely want to explore it and potentially change my rating.

    In terms of accuracy and reliability, I find LaunchDarkly's capabilities to be really good, as it supports governance and indirectly enables our application changes for certain testers to validate extra data and documents. While it would not directly improve dependence on document extraction or validation, any measured accuracy improvement that is considered ground truth is very helpful for us.

    Advice for others looking into using LaunchDarkly includes starting with a small pilot and a clear use case, such as enabling a new capability for selected users before a wider release. I recommend defining flag ownership, naming conventions, and cleanup responsibilities early, including both enabled and disabled behaviors in acceptance criteria during UAT, validating fallback behaviors, while keeping feature targeting separate from application security permissions. Finally, review pricing against expected user measures to assess value.

    Himanshu Roy

    Feature flags have reduced production incidents and support safe, gradual rollouts and A/B tests

    Reviewed on Nov 11, 2026
    Review from a verified AWS customer

    What is our primary use case?

    My main use case for LaunchDarkly is feature gating. Whenever I introduce a new feature, I put it behind a LaunchDarkly flag and then use it to release that feature percentage-wise. I release it for some percentage of people or some team members, then see if everything works fine, and then roll it out for 100% of the users. I also use it for A/B testing.

    A quick specific example of a feature I released using LaunchDarkly is the new cancellation flow, which was basically to reduce some churn. I didn't roll it out for all users; I first tested with only basic plan users. When I saw that it was working fine for them, I rolled it out for another plan, like the professional plan, and so on. Then I introduced it for the enterprise plan users, and then it was rolled out for all the other plan users.

    With AI coding tools helping my team ship code faster than ever, LaunchDarkly helps me maintain control once that code hits production by following a percentage-wise rollout strategy. I first roll out changes to a small percentage of users, then monitor them, and if everything works fine for them, I gradually increase the percentage.

    With LaunchDarkly, I use Sentry for error logging and monitoring whatever goes on with the changes, and it helps in observability and catching and figuring out the errors or any issues the users are facing.

    How has it helped my organization?

    LaunchDarkly has positively impacted my organization as I have been able to test things to a small percentage of users before rolling it out to a larger audience. If I have a bug in my production rollout, the blast radius is very small with this percentage rollout strategy, and if I find something, I can just quickly roll back that.

    From this approach, I can say that I have much less production incidents. In my four or five years here at my current company, I haven't seen any production issue where I have to roll out every change for all users because I catch it at an early stage as well because of LaunchDarkly, and that helps me improve my reliability metrics.

    What is most valuable?

    One of the best features that LaunchDarkly offers is that if I create a flag in one environment, such as beta, it is automatically created in other environments, in staging and production, and all I have to do is enable it in those environments whenever I want. Another feature I really appreciate is the simplicity of adding more conditions and making the flag more complex according to my use case. The interface is very straightforward, easy to understand, and intuitive.

    The automatic flag creation across environments helps my workflow because, as I mentioned before, if I create a flag and test some rollout strategy, I would like to test it on my beta environment first, then on stage, and then finally roll it out to the production environment. If this feature was not there, I would have to create this flag three times in a row. However, since LaunchDarkly provides this feature, I create the flag only once, and then it is replicated to all the other environments, and then I can just turn it on in the other environments without creating it from scratch. The UI is seamless to take care of all of these things.

    What needs improvement?

    One improvement that I think LaunchDarkly could make is that the search can be improved. Sometimes I find it complex to search for my feature flags or the feature flags created by other users.

    For how long have I used the solution?

    I have been using LaunchDarkly for three years.

    What do I think about the stability of the solution?

    LaunchDarkly is stable.

    What do I think about the scalability of the solution?

    LaunchDarkly's scalability is good because I have a large user base of approximately 40 million users, and it scales pretty reliably.

    Which solution did I use previously and why did I switch?

    Since my start at this company in 2022, my organization has been using LaunchDarkly only, so I don't have any context about what my company was using before LaunchDarkly. My organization didn't use any different solution before LaunchDarkly.

    What was our ROI?

    I can comment that the reliability improved a lot with using LaunchDarkly.

    What's my experience with pricing, setup cost, and licensing?

    My organization purchased LaunchDarkly and received the license.

    Which other solutions did I evaluate?

    My organization directly chose it without evaluating other options.

    What other advice do I have?

    On a scale of 1 to 10, I would rate LaunchDarkly a nine. I picked nine out of 10 because of the search feature I mentioned.

    LaunchDarkly is deployed in my organization as a public private cloud.

    I advise others looking into using LaunchDarkly to increase the reliability of their product by adopting a percentage-wise rollout strategy. You can also use A/B testing to figure out which features are liked more by the users, so it's a very good product to do all of these things.

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Amazon Web Services (AWS)
    Priyanshu Maurya

    Feature flags have enabled instant rollbacks and gradual cluster-based releases

    Reviewed on Nov 10, 2026
    Review from a verified AWS customer

    What is our primary use case?

    I use LaunchDarkly mainly for feature management and backend-related activities, such as when launching a new feature. I flag it behind a feature flag so that I can revert it whenever required, which provides instant rollback.

    For example, I used it in a migration where I had to migrate a service from one AWS stream to another stream. I put it behind a feature flag using LaunchDarkly, so that if something fails, I can revert it quickly without any PR or any merge using code or something similar.

    Using AI, I usually see faster code delivery, but there is a possibility that it can break in production. Everything is gated behind feature flags in LaunchDarkly, so it helps me a lot in preventing incidents.

    How has it helped my organization?

    LaunchDarkly has impacted my organization in a very positive manner. Earlier, I had to wait for a deployment which went step by step in case of any incident, but now it is quick, so the resolution is fast.

    Within five minutes, I can roll out in case of any incident. Earlier, it used to take two to three hours for a particular rollback, but now using LaunchDarkly, I can just turn off the feature flag and restart the service.

    What is most valuable?

    The features I like about LaunchDarkly are that I can roll using it by cluster by cluster and region by region. I have different types of tags that I can use for each feature flag, and I have a review system so that if someone tries to change a feature flag, then it needs to be reviewed so that others can also know about this. These options help me a lot.

    The feature that has made the biggest difference in my day-to-day work is the rollout feature cluster by cluster, where I can set to which cluster I have to roll out a feature, and then I can gradually increase using LaunchDarkly. This is quick and fast.

    There is also a feature where I can target LaunchDarkly feature flags by app level. For example, if I am migrating something, then I can put an app tag so that I can only target a particular app for a particular feature flag value.

    What needs improvement?

    I think the initialization of LaunchDarkly inside code can be made much easier because currently, every initialization calls the API.

    I need to call the API again and again whenever I need to see the update for a particular feature flag value. If that can be automatically implemented in the backend so that the feature flag value can be automatically fetched by the SDK, I could use it more effectively.

    For how long have I used the solution?

    I have been using LaunchDarkly for the last six months.

    What do I think about the stability of the solution?

    LaunchDarkly is stable.

    What do I think about the scalability of the solution?

    Regarding scalability, LaunchDarkly is quite stable and scalable, which helps me a lot.

    Which solution did I use previously and why did I switch?

    Before LaunchDarkly, I maintained a backend JSON file, and every time I needed to make a feature flag change, I created a PR for that, changing that JSON value. Then that JSON value is fetched again and again in the backend to read the latest value.

    I used to maintain a JSON file with embedded values for feature flags, which was time-consuming, so I switched to LaunchDarkly.

    What was our ROI?

    I save time with LaunchDarkly.

    Which other solutions did I evaluate?

    LaunchDarkly stands out as it is quicker in its approach and also cleaner, and I have different options, including a review system. These are all good things in LaunchDarkly.

    What other advice do I have?

    I chose nine out of ten because the initialization of LaunchDarkly requires me to call the API repeatedly to see updates for a particular feature flag value. If that could be implemented automatically in the backend, it would enhance the experience.

    My recommendation to others reading reviews on PeerSpot is to use LaunchDarkly as much as possible. Whenever they launch a new feature, they should put it behind a feature flag created in LaunchDarkly, and it can be the best option for that purpose. When they want to roll out gradually, cluster by cluster or cell by cell, then LaunchDarkly is also the best option for that.

    Which deployment model are you using for this solution?

    Public Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Amazon Web Services (AWS)
    Battula Ramesh

    Feature flags have improved safe rollouts and now support gradual testing across environments

    Reviewed on Nov 10, 2026
    Review provided by PeerSpot

    What is our primary use case?

    My main use case for LaunchDarkly is to manage feature flags, enable or disable features without deploying code, and safely test new features across different environments.

    I use feature flags in LaunchDarkly to control new features in different environments such as development, SIT, and UAT. First, I enable the features for testing, verify the functionalities, and fix any issues. Once everything is working properly, I gradually enable it for users, which helps reduce deployment risk.

    LaunchDarkly helps me improve release management, reduce risk, and quickly roll back features if issues occur, giving me better control over feature releases without the requirement for frequent deployments.

    LaunchDarkly helps me maintain control through feature flags and gradual rollouts once the code hits production.

    How has it helped my organization?

    LaunchDarkly has positively impacted my organization by making feature releases safer and more flexible, helping me reduce deployment risk, test new features with specific users, and quickly disable features if any issues occur. Overall, LaunchDarkly is improving my release management and development efficiency and effectiveness.

    I have seen improvements in release flexibility and testing efficiency.

    What is most valuable?

    The best features LaunchDarkly offers are enabling or disabling features without a deployment and enabling features for specific users or groups.

    Targeting specific users or groups helps my team validate a feature before rolling it out more broadly by allowing me to enable a feature for a specific user group first, collect feedback, and validate the functionalities. Once everything works as expected, I can gradually roll it out to all users and release features safely and confidently.

    I would also highlight the monitoring and analytics features of LaunchDarkly, which help me track feature performance, identify issues early, and make better decisions during releases. Overall, LaunchDarkly makes feature management easier, faster, and safer.

    What needs improvement?

    I think LaunchDarkly could be improved by making the user interface simpler, providing better reporting and analytics, and offering more detailed feature flag monitoring.

    I would suggest improving documentation, providing more practical examples, and making troubleshooting easier.

    For how long have I used the solution?

    I have been using LaunchDarkly for two months.

    Which solution did I use previously and why did I switch?

    Before LaunchDarkly, I mainly relied on traditional configuration-based feature management and a manual deployment process due to the limitations and difficulties I encountered.

    Which other solutions did I evaluate?

    LaunchDarkly stood out because of its easy-to-use feature flags, targeted rollouts, real-time updates, and environment management, and this flexibility along with the reduced release risk were the main reasons for choosing it.

    What other advice do I have?

    I rate LaunchDarkly an 8 out of 10. I give it an 8 because LaunchDarkly provides excellent features, flag management, safer releases, gradual rollouts, and flexibility.

    I think LaunchDarkly's AI capabilities should provide strong governance and security, with access control, data privacy, audit logs, and transparency being very important.

    Regarding reliability and accuracy, I think LaunchDarkly's AI capability improves productivity by providing safer and more accurate insights.

    LaunchDarkly is deployed as a public cloud-based SaaS solution in my organization, which I access through a web platform to manage feature flags across different deployment and testing environments.

    I use LaunchDarkly's cloud-hosted SaaS platform, although I'm not completely certain about the underlying cloud provider.

    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.

    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.

    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.

    Mandeep Bhangu

    Feature flags have enabled gradual rollouts and simple control of beta releases

    Reviewed on Sep 28, 2026
    Review provided by PeerSpot

    What is our primary use case?

    My use case for LaunchDarkly is for releasing features that we don't want to make available to customers immediately, or for beta testing. We put features behind feature flags and perform continuous deployment. Every week we deploy to production, but the whole feature is not available for clients, so we put it behind LaunchDarkly feature flags.

    I have not used LaunchDarkly to manage AI in production, models, prompts, or agents.

    What is most valuable?

    What I like most about LaunchDarkly is the ability to create segments easily. You don't have to create rules repeatedly. You just add your specific requirements into the segment and proceed from there without reworking the entire flag or rules.

    Over the period, I have seen measurable improvements in metrics such as evaluation scores when I implemented LaunchDarkly. They have made improvements, especially in enabling it globally and enabling it for a particular client, which makes a difference. Turning it off and turning it on was not a feature previously, but now it is much easier. If nothing is working, you can simply turn it off.

    What needs improvement?

    In the new UI where they have put production and related items next to each other, I find it is sometimes hard to determine if a feature flag is on in production or off. Looking for that specific information in the new UI was not pleasant for me.

    For how long have I used the solution?

    I have been working with LaunchDarkly for almost five or six years.

    What do I think about the stability of the solution?

    Regarding stability, it happened in four or five years of usage a couple of times that it was not syncing properly. Over the period, it got better.

    What do I think about the scalability of the solution?

    I would rate LaunchDarkly a seven in terms of scalability.

    Which solution did I use previously and why did I switch?

    I have not used anything similar to LaunchDarkly. We have been using this product for a long time.

    How was the initial setup?

    The initial setup was easy, and I was able to train my team. It took a couple of weeks and a couple of deployments for everyone to fully understand how to set it up for our company.

    What other advice do I have?

    I have been working in my current field overall for 15 or 16 years. The maintenance is taken care of by the team. I have not integrated any other tools with LaunchDarkly. I would give LaunchDarkly an overall rating of eight.

    FrankAlvarado

    Feature flags have transformed releases and now support flexible maintenance workflows

    Reviewed on Sep 28, 2026
    Review provided by PeerSpot

    What is our primary use case?

    Regarding my use cases for LaunchDarkly, I have tried to find more creative ways to use it, but it boils down to feature flagging features. I've attempted ways to implement more complex uses, but the business is resistant to doing much more than that. I want to do release gates and configurations. I've used it for gating a service. I had a GitHub action that would run on multiple workflows, and sometimes I needed to do maintenance. I set it up so that if I set the flag, it would enter maintenance mode and wouldn't run any other workflow actions, but it wouldn't fail, which is what I didn't want. This worked very well. I ended up getting rid of that service and everything, but other teams found this GitHub action using LaunchDarkly flags and found it useful. They have been using it for other things. This happens a lot with GitHub actions, since it's sometimes hard to go into everybody and tell them about maintenance. It's very easy to just use a feature flag where you can not fail them because then you'll get a lot of messages about it. Instead, you can tell them softly that the action didn't run because this is in maintenance mode. If they really need it, they can just wait. I set it up so I could also put a message saying we'll be back in two days or two hours, whatever. Essentially, it is mostly feature flags.

    What is most valuable?

    I love the stats and seeing how many times a flag got hit. All of that is handy. The feature flagging part is excellent, very fast, and very nice and intuitive.

    What needs improvement?

    When asked if there's anything LaunchDarkly can do better for me, I wish I could use it more and could give a more in-depth response. My main concern is that when I was trying the GitHub action functionality, what I was trying to use it for should have been something native and supported. I found that there were a lot of similar implementations done by DataDog, and it was confusing because I didn't know which one to use or fork off. I would say clean up some of the dev tooling in GitHub, especially for the GitHub action functionality. Maybe have a few that are very clear on what they do. Being able to run a GitHub action to check a feature flag is very handy. The last time I checked, it's not an explicitly supported thing, and I had to build the functionality myself. I understand LaunchDarkly is more focused on releases and live production functionality, but if they can also expand into dev tooling, I think that would be great.

    A feature flag should be very simple, should be true or false with a little description. If you want to do more fancy things with it, then you should be able to do an expanded view. Most of your main client base are developers and most of them can figure things out, but you'll be surprised at how many can't. The basic true or false Boolean feature flag UI should be very simple and very clear. Sometimes it feels like there's a lot going on and I just want a Boolean feature flag. If it's false, I want to switch to true. If it's true, I want to switch to false. Beyond that, I love the stats and seeing how many times it got hit, all of which is handy. When I'm setting a new flag, I remember the first time thinking this is way too much going on here. The basic functionality should be very simple, and if you want to get fancy, then show more options, but not from the start.

    Professionally, I have only used LaunchDarkly. For my personal projects, I have used PostHog. They make it slightly more simple, at least on the feature flag part. Maybe it's just the nature of the tool and it's a UX problem, or maybe it's because you have a bunch of developers creating things for developers so we don't care that much about the UX. It's just too much. You should be able to have a simple true or false option.

    I would say you are a little over-engineered, which makes it harder for developers. I've seen developers struggle, get annoyed by it, and just not use it as much. We kind of have to get to the point where we force them, telling them that every feature they release has to have a LaunchDarkly flag. Whereas it would be nicer if they would see the value right away and just create flags.

    For how long have I used the solution?

    In relation to how long I've been using LaunchDarkly overall in my career, I would say about four years.

    What do I think about the stability of the solution?

    Regarding stability of LaunchDarkly, I have no complaints. It's fast and works well.

    What do I think about the scalability of the solution?

    On the topic of scalability, we have used it across many applications in many different ways. Some of the front-end teams are using the client side instead of the server side. I've never heard any complaints about how scalable it is or how quick it is. If you understand how it works, you can set it up in a way that is not problematic. You can cache a lot of the responses and even create tests. LaunchDarkly offers handy documentation on how to set up testing for it.

    A feature flag should be very simple, true or false with a little description. If you want to do more fancy things with it, then you should be able to expand. I understand most of the main client base are developers and most of them can figure things out, but you'll be surprised. The basic true or false Boolean feature flag UI should be very simple and very clear. Sometimes it feels like there's a lot going on and I just want a Boolean feature flag. If it's false, I want to switch to true. If it's true, I want to switch to false. Beyond that, I love the stats and seeing how many times it got hit. When I'm setting a new flag, I remember the first time thinking this is way too much going on here. The basic functionality should be very simple, and if you want to get fancy, then show more options, but not from the start.

    Which solution did I use previously and why did I switch?

    When considering alternatives I've used compared to LaunchDarkly, we had a homemade solution before for feature flagging. It wasn't great and was a very custom thing. As far as an actual competitor, I don't think so. We had a homegrown product that worked okay, but it would break and was not very friendly to use. Documentation was poor. It was just a homegrown product. It was not a great experience. When we switched to LaunchDarkly, being a manager on my side of the organization, we did a lot of work trying to push it because we liked it so much. Now things are better and I think it has been adopted widely. As far as all the teams that I worked with, a lot of them use it.

    How was the initial setup?

    Concerning the initial deployment of LaunchDarkly, maybe because I wasn't too familiar with tools of that type, it was a little hard to get started. Once you got the hang of it and once it clicked what it's trying to do, it was pretty easy. It does feel like drinking from a fire hose sometimes with LaunchDarkly. I feel developers should be introduced to the feature flagging part first, which I feel most of them understand. I think you do a very good job at it, very fast, very nice, and very intuitive. Then start introducing the other functionality, because it does feel like you do a lot and it wasn't very clear. There were points where I was wondering if LaunchDarkly even does feature flagging the way I wanted to do it. A lot of developers get confused too. I've had to onboard a lot of developers to LaunchDarkly because being one of the early adopters in the company, at least on my side of the organization, my name got attached to it. A lot of people would come to me after seeing that I had worked on it before. I onboarded several teams, was an owner for some of the groups. They would come to me a lot, and once I got on a call with them, I would say, I know there's a lot going on here, but the one that you care about is the feature flagging. Then go through the docs and learn more about it. There are other things that you can do, but the main thing that most people reaching out to me needed was because their managers told them they needed to start using LaunchDarkly. They didn't have any idea how to start.

    Maybe there should be a more centralized way of implementing this and having centralized documentation on how to use the tool. It doesn't really change that much from team to team. Everybody kind of uses it the same way. Maybe there should be some kind of centralized effort to have centralized documentation that can help you get started. Here's how you request access to it, here's how you create flags. The whole way that the ownership is set up and who can allow access and the way the teams are named is very confusing. I felt we had a good thing and now it's kind of confusing and it has taken me a while to figure out what group I belong to and how I add people and how to get them access. LaunchDarkly in particular seems a little more difficult than the other tools that we use. Maybe the LDAP integration is not the greatest. Whoever implemented this in the company may have just done it poorly, but whoever implemented it should go through how they implemented it and maybe there's a better way to do it. This is very confusing right now with who gives access and who's the owner. That's why people still come to me years after I stopped being a daily user of it.

    I understand that LaunchDarkly may not have a solution for everything. We're trying to implement LaunchDarkly in some ECS instances to do feature flagging in ECS. The last time I checked, there wasn't a clear way of doing it. I managed to find a way though. There's always enough documentation. LaunchDarkly deserves credit for having good developer documentation. You cover a lot of cases and there are multiple ways to enable it. There are enough ways to make LaunchDarkly work in the multiple types of environments that I've had to make it work, and I've always found a way. It's not super hard. Whoever's implementing it depends on whether they know how to dig through developer documentation. LaunchDarkly provides enough information.

    What other advice do I have?

    On a scale from one to ten, I would rate LaunchDarkly as a nine overall. Now that I have used PostHog and I'm pretty sure their main focus is not feature flagging, but they do have it and it's pretty nice that it's part of their suite. You are a nine. You do almost everything that I need from you well. If I knew more about the pricing, I would give you a value ranking, but as far as a functionality ranking, you are a nine. You do almost everything pretty well and pretty fast. The UX is a little confusing. There are a lot of parts that feel over-engineered. I have learned that now that I have my side projects with users and they complain to me that things are not very simple looking. My main concern would be that you are a little over-engineered. It does make it a little harder for developers. I've seen developers struggle, get annoyed by it, and just not use it as much. We kind of have to force them, telling them that every feature they release has to have a LaunchDarkly flag. Whereas it would be nicer if they would see the value right away and just create flags without being forced. My overall rating for LaunchDarkly is a nine out of ten.

    Muhammad Ghaffar

    Feature flags have enabled controlled rollouts and support collaborative experimentation

    Reviewed on Sep 25, 2026
    Review from a verified AWS customer

    What is our primary use case?

    My main use case for LaunchDarkly is to gate our new features behind the flags and to manage those flags via LaunchDarkly UI and portal and dashboard so that we can roll out different features properly tested on different environments and for different users and with different variations, with different configurations and settings.

    One feature that we rolled out this way is a really big feature which was changing the product's whole flow and had to be rolled out to multiple markets, specifically to three different countries where our product is being used. Since it was a big feature, we had to get it behind the development first because it was in the development stage. We tested it out regularly with different variations, with different targetings, with different rule sets, using different LLMs and everything which was managed by LaunchDarkly. Then we launched it on staging, turning on the flag for staging to test it out there. When we rolled it into production, we selected a smaller customer country from the rules part for the launch to identify initial bugs or issues at a smaller customer base, eventually rolling it out and turning on the feature for bigger customers and bigger countries as well.

    This is my main use case for LaunchDarkly; we create the flags there, manage them from there, and turn them on or off there. We have a whole dashboard where we can see who has made a recent change in the flag and what settings have been changed. If something breaks due to recent settings, we have an idea of what has been changed that caused it to not behave as required. Additionally, we have different variations, different rules in it, as well as a whole dashboard where we can look into it. It is really helpful to integrate it easily due to the flexibility that gives us confidence in LaunchDarkly.

    How has it helped my organization?

    LaunchDarkly has positively impacted my organization by providing flexibility and collaboration, as our company is divided into different squads. Every squad can collaborate on their flags, determining what needs to be turned on and for which squads, including variations and targetings.

    I have witnessed improvements in collaboration through LaunchDarkly, as we have different variations for a flag that allows multiple squads to test different things simultaneously. Different squads use the same flag while testing various things, utilizing different variables, environments, variations, and targeting.

    What is most valuable?

    The best features LaunchDarkly offers include flexibility, a log about recent activities or who has done what, variations, targeting, and a single flag for different environments; these are the top most features that provide greater flexibility for LaunchDarkly.

    Among those features, I rely on variations, the logs, and the rules the most; variations and the rules are particularly targeting the same thing, but these have significantly helped us.

    What needs improvement?

    I believe LaunchDarkly is working very well, but making it easier to integrate with code bases or providing an AI component that assists customers by understanding their code bases and supplying easy-to-integrate code snippets would be very helpful.

    For how long have I used the solution?

    I have been using LaunchDarkly for almost around seven to eight months.

    What do I think about the stability of the solution?

    LaunchDarkly is stable.

    What do I think about the scalability of the solution?

    Its scalability is good, as I mentioned previously, from the flexibility, scalability, and features points of view; it is good.

    How are customer service and support?

    I have not felt a need to connect to customer support for anything, but I have heard from my other team members that customer support is great, really supportive, and collaborative. Their customer support success manager is in touch with us via emails, checking in about various matters, reviews, complaints, or anything else, which is great.

    Which solution did I use previously and why did I switch?

    I previously used Flagsmith for our flags and feature flagging but switched to LaunchDarkly due to its superior features, including variations, flexibility, rules, targeting, and other options that were lacking in Flagsmith.

    What other advice do I have?

    I advise others looking into using LaunchDarkly to go through the documentation thoroughly and select their use case since there are a lot of options available, but you do not need to go through each and every one. Just identify what relates to your use case because if you explore everything, it might become confusing, and you could struggle to switch to or effectively use LaunchDarkly. Focusing on your specific use case will help you find your solution in LaunchDarkly, and you might not have to use all of its features at once; you can use a part of it initially and later integrate additional features.

    LaunchDarkly is working great, and I would encourage them to continue their excellent performance. They should aim to simplify things and avoid adding complex features that could complicate the product overall; keeping it simple and focused on use cases will keep it good. I am providing a review rating of nine for LaunchDarkly.

    Which deployment model are you using for this solution?

    Private Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Amazon Web Services (AWS)