--- title: LaunchDarkly Reviews meta_title: 'LaunchDarkly Reviews 2026: Details, Pricing, & Features | G2' meta_description: Filter 850 reviews by the users' company size, role or industry to find out how LaunchDarkly works for a business like yours. aggregate_rating: rating_value: 4.5 review_count: 850 scale: '5' date_modified: '2026-09-01' parent_category: name: Development url: https://www.g2.com/categories/development --- # LaunchDarkly Reviews **Vendor:** LaunchDarkly **Category:** [Feature Management Software](https://www.g2.com/categories/feature-management) **Average Rating:** 4.5/5.0 **Total Reviews:** 850 **AI Verified:** At least 10 G2 reviewers have confirmed using this product's AI features and functionality. ## About LaunchDarkly Founded in 2014 and headquartered in Oakland, California, LaunchDarkly serves over thousands of enterprises, including a quarter of the Fortune 500. LaunchDarkly is the runtime control platform for the AI era, trusted by software teams to control AI-generated code and AI agents in production at any scale. The LaunchDarkly platform delivers runtime control through two solutions: CodeControl and AgentControl. CodeControl helps teams ship AI-generated code confidently. With CodeControl, teams can observe production behavior, make changes in real time, and limit exposure based on actual impact. Through a combination of industry-leading feature flags, progressive rollouts, real-time observability, experimentation, and automatic recovery, LaunchDarkly gives organizations the ability to move at AI speed without giving up control. AgentControl helps teams keep AI agents in check in production, blocking bad behavior and steering responses in real time. Teams can configure prompts and models before launch, monitor and observe live performance and behavior, and automatically take action—without redeploying. When agents make curious decisions, or when small prompt or model changes cause big issues, AgentControl detects and corrects them as they happen. With runtime control across code and agents, LaunchDarkly helps enable teams to ship AI-built software with confidence, govern agent behavior in production, optimize AI performance and cost, build self-healing systems, and experiment continuously. The result is faster release velocity, lower production risk, and the ability to continuously adapt software and AI systems without slowing down to stay safer. ## LaunchDarkly Pros & Cons Pros and Cons are compiled from review feedback and grouped into themes to provide an easy-to-understand summary of user reviews. **What users like:** - Users appreciate the **ease of use** of LaunchDarkly, finding setup and configuration straightforward and intuitive. (211 reviews) - Users appreciate the **ease of use for feature flags** , enabling fast toggling and effective configuration without technical barriers. (174 reviews) - Users appreciate the **flexibility and user-friendly design** of LaunchDarkly, enhancing feature flag management for all team members. (116 reviews) - Users find the **easy setup** of LaunchDarkly to be smooth and facilitating the integration process seamlessly. (93 reviews) - Users commend LaunchDarkly for its **ease of implementation** , allowing seamless integration and efficient feature management. (74 reviews) - Users appreciate the **user-friendly interface** of LaunchDarkly, making it accessible for non-technical team members. (65 reviews) - Rollout Management (64 reviews) - Control (63 reviews) - Users praise the **easy integrations** of LaunchDarkly, enabling seamless connections with existing tools for enhanced efficiency. (61 reviews) - Users praise the **seamless integrations** of LaunchDarkly, enhancing flexibility and streamlining operations across teams. (60 reviews) **What users dislike:** - Users note that **feature flags issues** create confusion, making it hard to manage percentages and track logs effectively. (62 reviews) - Users feel that the **manual process for handling holdout groups** adds complexity to their management experience. (47 reviews) - Users express frustration over the **missing features** in LaunchDarkly, particularly regarding crypto-signature support and flag management. (45 reviews) - Users express frustration over the **limited features** in LaunchDarkly, particularly regarding crypto-signature support and integration capabilities. (40 reviews) - Users find the **complex features** of LaunchDarkly clumsy, especially regarding environment management and configuration handling. (35 reviews) - Users find the **interface confusing** , leading to a steep learning curve for effective flag configuration. (34 reviews) - Confusion (33 reviews) - Limitations (33 reviews) - Complexity (32 reviews) - Users express concerns over the **poor UI** , which can be frustrating and disrupt workflow during usage. (32 reviews) ## LaunchDarkly Reviews ### 1. Safer Production Rollouts with Instant Feature Toggles and Precise Targeting **Rating:** 4.5/5.0 stars **Reviewed by:** Muhammed A. | Technical Project Manager , Information Technology and Services, Mid-Market (51-1000 emp.) **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** Validated through LinkedIn **Incentivized:** This reviewer was offered a nominal gift card as thank you for completing this review. **Source: G2 invite:** Invitation from G2. This reviewer was offered a nominal gift card as thank you for completing this review. **G2 Icon:** Our network of Icons are G2 members who are recognized for their outstanding contributions and commitment to helping others through their expertise. **Reviewed Date:** August 05, 2026 **What do you like best about LaunchDarkly?** LaunchDarkly has made it much safer to test new features in production by rolling them out to a small percentage of users first, rather than deploying changes to everyone at once. Being able to toggle features on or off instantly without redeploying code has sped up testing cycles significantly, especially when validating changes to trip flow or platform functionality before a full rollout. The targeting rules for controlling exactly who sees a given feature, whether by user segment or percentage, have made testing much more precise than relying on separate staging environments alone. The dashboard makes it easy to monitor flag status and adjust rollouts on the fly without needing a developer to make code changes for every adjustment. **What do you dislike about LaunchDarkly?** Managing a growing number of feature flags over time requires discipline to clean up ones that are no longer needed, otherwise the codebase accumulates unnecessary complexity. Pricing scales with usage and seats, which can get expensive as the number of flags and monthly active users grows. The initial setup for integrating flags cleanly into existing code took some restructuring, especially for parts of the codebase that weren't originally built with feature flagging in mind. Some of the more advanced targeting and experimentation features have a learning curve before getting full value out of them. **What problems is LaunchDarkly solving and how is that benefiting you?** LaunchDarkly has let us test new features on a small subset of real users before a full rollout, catching issues early without risking a broken experience for everyone on the platform. This has made deploying changes to core functionality, like trip flow updates, much safer, since we can instantly disable a feature if something goes wrong instead of needing an emergency rollback and redeploy. **Official Response from Micaela Durkin:** > Thank you for sharing such thoughtful feedback! We’re so glad LaunchDarkly has helped you roll out trip flow and platform changes more safely while reducing the need for emergency redeployments. For managing flag debt, we have a great guide to reducing technical debt from feature flags which offers best practices for flag cleanup and lifecycle management. I've shared the link below if it's helpful! ### 2. Powerful Feature Flag Platform with a Learning Curve **Rating:** 4.0/5.0 stars **Reviewed by:** Jeni J. | Software Dev , Ai Agents Builder, Information Technology and Services, Mid-Market (51-1000 emp.) **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** Validated through LinkedIn **Incentivized:** This reviewer was offered a nominal gift card as thank you for completing this review. **Source: G2 invite:** Invitation from G2. This reviewer was offered a nominal gift card as thank you for completing this review. **G2 Icon:** Our network of Icons are G2 members who are recognized for their outstanding contributions and commitment to helping others through their expertise. **Reviewed Date:** July 30, 2026 At G2, we prefer fresh reviews and we like to follow up with reviewers. They may not have updated their review text, but have updated their review. **What do you like best about LaunchDarkly?** I love the confidence LaunchDarkly gives me when releasing new features. Feature flags, gradual rollouts, and instant rollbacks let me deploy code independently of releases, reducing risk and making experimentation much easier. The platform offers an excellent developer experience with strong integrations into CI/CD workflows. Its newer AI-focused capabilities help teams manage AI-powered features more confidently in production. I also appreciate how AI Configs allow me to treat prompts, model selection, and AI parameters like feature flags, making it safer to iterate on AI features in production. Additionally, the initial setup of LaunchDarkly was very easy. **What do you dislike about LaunchDarkly?** LaunchDarkly can feel expensive for smaller teams or startups that only need basic feature flagging. The interface is packed with powerful capabilities, but it takes time to fully understand advanced concepts like experimentation, governance, and AI Configs, so more guided onboarding would help. I'd also like to see deeper built-in analytics and reporting that make it easier to measure the business impact of feature rollouts and AI configuration changes without relying on external tools. **What problems is LaunchDarkly solving and how is that benefiting you?** I use LaunchDarkly to manage feature flags and perform safe rollouts without redeployment. It enables precise testing and quick disabling of issues, reducing risk. Its excellent developer experience and AI Configs enhance confidence in deploying new features and AI elements securely. **Official Response from Micaela Durkin:** > Thank you for taking the time and leaving such a thoughtful review! We love that LaunchDarkly is helping you release safely and iterate on AI-powered features with confidence. For onboarding, the LaunchDarkly Academy resources as well as documentation can help teams ramp faster and get more guidance on rollout and experimentation best practices. ### 3. Flexible Feature Blocking Makes Customer Experiences Easy to Tailor **Rating:** 5.0/5.0 stars **Reviewed by:** Anthony B. | Senior Software Engineer, Health, Wellness and Fitness, Small-Business (50 or fewer emp.) **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** Validated through Google using a business email account **Incentivized:** This reviewer was offered a nominal gift card as thank you for completing this review. **Source: G2 invite:** Invitation from G2. This reviewer was offered a nominal gift card as thank you for completing this review. **Reviewed Date:** August 28, 2026 **What do you like best about LaunchDarkly?** I like that you can block features at two levels, app-wise or customer-wise, which has made it easy to create bespoke experiences for our customers. **What do you dislike about LaunchDarkly?** While LaunchDarkly is powerful, the pricing model can scale up quickly as monthly active users increase. Additionally, managing flag lifecycle hygiene requires continuous effort to prevent technical debt from stale flags in the codebase, and the UI has a bit of a learning curve for non-technical users. **What problems is LaunchDarkly solving and how is that benefiting you?** We previously struggled with high-risk software deployments that required complex rollbacks whenever issues arose. LaunchDarkly allowed us to separate code deployments from feature releases, enabling us to test new features safely in production with specific user groups. We can now perform gradual percentage rollouts and instantly kill buggy features with a single toggle, which has significantly reduced deployment anxiety and shortened our release cycles. **Official Response from Micaela Durkin:** > Thank you for sharing this! We love to hear that targeting at both the app and customer level has helped you build tailored experiences, and that separating deployments from releases has cut down on deployment anxiety and shortened your release cycles. We also hear you on flag hygiene and the learning curve for non-technical users, and we'll be sure to pass that along to our product team. In the meantime, I linked to a guide in our docs that provides some best practices for reducing tech debt. ### 4. Effortless Feature Management and Integration **Rating:** 4.0/5.0 stars **Reviewed by:** SARAYU B. | Software Engineer, Mid-Market (51-1000 emp.) **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** Validated through LinkedIn **Incentivized:** This reviewer was offered a nominal gift card as thank you for completing this review. **Source: G2 invite:** Invitation from G2. This reviewer was offered a nominal gift card as thank you for completing this review. **G2 Icon:** Our network of Icons are G2 members who are recognized for their outstanding contributions and commitment to helping others through their expertise. **Reviewed Date:** July 25, 2026 **What do you like best about LaunchDarkly?** I find LaunchDarkly incredibly valuable for shadow launching features in our web application, especially because it allows feature flags to be set at different hierarchies. Also, it enables to quickly turn off a feature during any release if any issues are encountered at the last minute without a need to rever back any code Or any additional work. The ability to enable a feature for certain users while it's disabled for others is a great way to conduct load testing and infra-level testing, helping us identify and resolve bugs early, thus improving customer satisfaction. I really like the ease of setup and how even a layman can understand and set it up easily. The customizability of the payload structure is a standout feature, as it lets us tailor the naming and organization to our needs. Integration with any tech stack is seamless, making it maintainable and valuable during releases and integration tests. I also appreciate the comprehensive documentation, which makes setup straightforward. **What do you dislike about LaunchDarkly?** I really like everything about it, but one thing that I can say it can improve is the introduction of AI of some kind to help in writing the given scripts (payload in this case) when given a requirement. **What problems is LaunchDarkly solving and how is that benefiting you?** I use LaunchDarkly for shadow launching features, enabling early bug detection and load testing, boosting customer satisfaction and ensuring smooth releases without sharing features with end users prematurely. **Official Response from Micaela Durkin:** > Thank you so much for the detailed feedback. It's great to hear how much value you're getting from flag hierarchies and targeted rollouts for load testing. On the AI front, LaunchDarkly actually already has some AI-assisted capabilities in the product, including AI-assisted experiment creation and AI-assisted onboarding for SDK setup, and we're continuing to expand AI-assisted workflows more broadly. We'd love to hear more about the specific payload generation use case you have in mind, so please feel free to reach out to our team directly to dig into it further. ### 5. Quick No-Code Changes using LaunchDarkly **Rating:** 4.5/5.0 stars **Reviewed by:** Johanna B. | Team Lead, Customer Support, Mid-Market (51-1000 emp.) **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** Validated through a business email account **Incentivized:** This reviewer was offered a nominal incentive as thanks for completing this review. **Source: Seller invite:** Invitation from a seller or affiliate. This reviewer was offered a nominal incentive as thanks for completing this review. **Reviewed Date:** July 27, 2026 **What do you like best about LaunchDarkly?** It's incredibly easy and straight-forward to use, even from a no/low-code perspective. I like how quickly it enables us to make changes in our platform. **What do you dislike about LaunchDarkly?** When working within specific Flags in LaunchDarkly, I wish there was a way to bulk add or bulk remove targets. I've spent quite a bit of time adding a Flag for about 20 targets, which I feel like could be sped up. **What problems is LaunchDarkly solving and how is that benefiting you?** For me specifically, leading our support team, I'm able to use it to activate a variety of banners across our platform, especially for notices and updates that need to go out in a timely manner. This allows us to get broader reach than spending out a mass email and tracking the emails down. We've been able to integrate with Claude projects as well, and are hoping to add additional automates to make it even faster and easier to use. **Official Response from Micaela Durkin:** > Thank you for sharing this, I love hearing your perspective from support and using LaunchDarkly for banner rollouts. It's great to hear how much easier it's made reaching your users compared to mass emails. On the target front, we actually do offer bulk editing within a flag's targeting tab, so you can add, remove, or replace multiple targets at once instead of one by one, I've shared the docs below if this is what you're looking for and is useful for your workflow! ### 6. Fantastic SDK Integrations and a Unified Workflow for Safe Deployments & Experimentation **Rating:** 4.5/5.0 stars **Reviewed by:** Raj K. | Senior Software Engineer, Mid-Market (51-1000 emp.) **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** Validated through Google using a business email account **Incentivized:** This reviewer was offered a nominal gift card as thank you for completing this review. **Source: G2 invite:** Invitation from G2. This reviewer was offered a nominal gift card as thank you for completing this review. **Reviewed Date:** July 09, 2026 **What do you like best about LaunchDarkly?** The SDK integrations are fantastic. LaunchDarkly collapsed two major headaches—safe deployments and structured experimentation—into a single, unified workflow. The compounding time savings and the confidence it gives our engineering and on-call teams are immense. The context tracking and intuitive UI make it easy to manage who sees what. The ability to run A/B tests and progressively roll out new UI elements to specific user segments without engineering intervention is brilliant **What do you dislike about LaunchDarkly?** There is definitely a learning curve for new team members when it comes to organizing and cleaning up flags. Once a project scales, managing multiple flags can become cluttered and performance could degrade if you don't stay on top of deprecation and maintenance **What problems is LaunchDarkly solving and how is that benefiting you?** We primarily use it for continuous delivery and targeted rollouts. It allows us to test changes on small segments of real traffic before rolling them out widely. Rollbacks have become a simple toggle flip instead of a stressful, emergency fire drill **Official Response from Micaela Durkin:** > Thanks so much for sharing this we love hearing that rollbacks went from "fire drill" to a "simple toggle flip"! We're glad the SDKs and context targeting are helping your team ship confidently and experiment without engineering bottlenecks. LaunchDarkly Academy is a great resource for onboarding new team members which I've linked below, and we're also continuing to invest in making flag organization and cleanup more intuitive as projects grow. ### 7. Smarter Experimentation Nudges and Powerful Context Targeting **Rating:** 4.5/5.0 stars **Reviewed by:** Shruti P. | senior engineer, Mid-Market (51-1000 emp.) **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** This review contains authentic analysis and has been reviewed by our team **Incentivized:** This reviewer was offered a nominal incentive as thanks for completing this review. **Source: Seller invite:** Invitation from a seller or affiliate. This reviewer was offered a nominal incentive as thanks for completing this review. **Reviewed Date:** June 29, 2026 **What do you like best about LaunchDarkly?** Smarter experimentation features where it helps you identify which flags are worth A/B testing based on traffic patterns. As someone still learning the ropes, having the tool nudge me toward "hey, this flag has enough traffic to run a meaningful experiment" is genuinely helpful, I don't have to figure that out from scratch. LD moved from Users to Contexts, meaning you can now target not just by user but by organization, device, session, or any custom entity. As a junior eng, this unlocked a lot for me. **What do you dislike about LaunchDarkly?** the flag cleanup and archiving experience isn't great, stale flags pile up fast and there's no strong nudge to deprecate them. I've also hit moments where the dashboard felt slightly slow when loading large flag lists. Nothing that's blocked me, but there's room to tighten the performance and make flag hygiene easier. **What problems is LaunchDarkly solving and how is that benefiting you?** The GitHub integration has been especially useful, I can see which flags are tied to open PRs and make sure nothing accidentally goes live before it's reviewed. It's made me a lot more confident shipping as a engineer. **Official Response from Micaela Durkin:** > Thank you for the thoughtful review! We’re so glad our experimentation insights, Contexts model, and GitHub integration are helping you ship with more confidence as you grow in your role. We also appreciate the candid feedback on flag cleanup and dashboard performance, and we’re continuing to improve both with feedback like this. ### 8. Feature Releases Feel Much Less Risky **Rating:** 5.0/5.0 stars **Reviewed by:** Kritika M. | Senior Software Engineer, Mid-Market (51-1000 emp.) **Validated Reviewer:** Validated through LinkedIn **Incentivized:** This reviewer was offered a nominal gift card as thank you for completing this review. **Source: G2 invite:** Invitation from G2. This reviewer was offered a nominal gift card as thank you for completing this review. **Reviewed Date:** September 01, 2026 **What do you like best about LaunchDarkly?** For me though, the biggest benefit of feature releases is that you can ship code without having to release that feature to everyone at the same time. We’ve used flags in cases where the feature was technically ready but we wanted to test with a smaller percentage of our users. It also comes in handy if something isn’t behaving how you expect in production. With feature flags you can simply turn off the feature without having to do another deployment. We have avoided a few panicked midnight releases because of that. **What do you dislike about LaunchDarkly?** The biggest downside once you start using feature flags a lot is that you have to stay organized. Dead flags can linger longer than they should, especially if noones responsible for cleaning up old flags. Another pitfall I’ve experienced is when targeting rules get more complex than you originally anticipate. Feature flags as a product are awesome, but you have to have some discipline with naming and deleting temporary flags. **What problems is LaunchDarkly solving and how is that benefiting you?** Essentially feature releases remove the risk of releasing new functionality. We can roll out a feature gradually, observe how it behaves, and then increase exposure when we are ready. I don’t worry quite so much about whether a minor issue will cause us to do an emergency rollback, and I can easily test functionality with certain users. **Official Response from Micaela Durkin:** > We love to hear this kind of feedback! It's also great to hear how flags have helped you avoid those midnight emergency releases. You're spot on that flag hygiene and targeting complexity take real discipline as usage grows, and we appreciate you being so candid about that tradeoff alongside the wins. Here is one of our best practice guides on reducing technical debt: ### 9. Contexts Transformed Our Targeting and Rollouts **Rating:** 4.5/5.0 stars **Reviewed by:** MOKSHI J. | Senior Software Engineer, Mid-Market (51-1000 emp.) **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** This review contains authentic analysis and has been reviewed by our team **Incentivized:** This reviewer was offered a nominal incentive as thanks for completing this review. **Source: Seller invite:** Invitation from a seller or affiliate. This reviewer was offered a nominal incentive as thanks for completing this review. **Reviewed Date:** August 07, 2026 **What do you like best about LaunchDarkly?** The Contexts feature changed how we target. We went from basic user flags to targeting by company, subscription tier, and region, no application logic changes needed. Running 4-5 concurrent rollouts to different customer segments simultaneously would've taken 3 engineers and 4 months to build in-house. LD replaced that entirely. New engineers are shipping behind flags within their first week **What do you dislike about LaunchDarkly?** SDK versioning across 20+ microservices is a real headache, had 2 incidents this year from inconsistent flag evaluation caused by outdated SDK versions across teams. **What problems is LaunchDarkly solving and how is that benefiting you?** We run ~200 active flags in prod at any time. Kill switch response averages under 30 seconds when something goes wrong, that's not achievable with a homegrown solution at our scale. Saved us an estimated 12 engineer-months of build work. **Official Response from Micaela Durkin:** > Thank you for highlighting how Contexts have helped your team run more sophisticated rollouts and respond quickly when issues arise! It's also amazing to hear how using LaunchDarkly has translated to real engineering time saved. To your point on SDK versioning, we provide in-product SDK version notifications based on the SDKs used in each environment, along with guidance for updating and migrating, and I've linked the documentation below if it's helpful! ### 10. Decouples code deployment from feature release with fine-grained control **Rating:** 5.0/5.0 stars **Reviewed by:** Yogesh S. | Software Engineer, Mid-Market (51-1000 emp.) **Validated Reviewer:** Validated through LinkedIn **Incentivized:** This reviewer was offered a nominal gift card as thank you for completing this review. **Source: G2 invite:** Invitation from G2. This reviewer was offered a nominal gift card as thank you for completing this review. **Reviewed Date:** August 30, 2026 **What do you like best about LaunchDarkly?** Decoupling deployment from release is a game-changer for maintaining a fast, trunk-based development workflow. LaunchDarkly makes implementing feature flags and gradual percentage rollouts seamless across multiple environments. The SDKs are well-documented and simple to integrate into both frontend frameworks and backend services. The real-time streaming architecture ensures that flag updates propagate across services in milliseconds without needing to redeploy code or restart servers. Having granular targeting rules based on custom user attributes enables running canary releases and dark launches effortlessly, while the instant kill-switch capability gives the engineering team complete confidence to push changes directly into production. **What do you dislike about LaunchDarkly?** Technical debt management can become challenging if the team does not enforce strict flag lifecycle governance; stale flags accumulate quickly in the codebase if not actively cleaned up. The pricing model can also scale up significantly based on Monthly Active Users (MAU) or client-side evaluations, which requires careful planning for high-traffic public-facing apps. Additionally, managing complex flag prerequisites and interdependent rules across multiple microservices can lead to an overwhelming UI view that takes time to audit. **What problems is LaunchDarkly solving and how is that benefiting you?** It completely eliminates high-stress, all-or-nothing release days. Instead of managing long-lived feature branches and painful merge conflicts, code is merged continuously behind flags. If a new service or database migration introduces unexpected latency or errors, turning off the flag instantly reverts the behavior for affected users without requiring an emergency rollback or hotfix deployment. This drastically reduces the blast radius of new releases, shortens our delivery cycles, and allows for safe testing in live production environments. **Official Response from Micaela Durkin:** > Wow, thank you for taking the time to leave such a detailed review! It's great to hear that decoupling deployment from release has transformed your workflows, and that your engineering team now has the confidence to ship straight to production. We also appreciate the feedback on flag governance and managing complex dependencies across microservices, and we'll be sure to pass that along to our product team. For flag cleanup and reducing tech debt, check out Vega, our new AI agent that can identify stale flags and open a pull request to remove them from your code automatically. I've linked the docs below! ### 11. Feature Management with Granular Release Control **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Small-Business (50 or fewer emp.) This reviewer's identity has been verified by our review moderation team. They have asked not to show their name, job title, or picture. **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** Validated through a business email account **Incentivized:** This reviewer was offered a nominal incentive as thanks for completing this review. **Source: Seller invite:** Invitation from a seller or affiliate. This reviewer was offered a nominal incentive as thanks for completing this review. **Reviewed Date:** August 29, 2026 **What do you like best about LaunchDarkly?** LaunchDarkly is widely considered the industry standard for feature management and progressive delivery. It excels at decoupling code deployments from feature releases, giving engineering teams granular control over how and when new features reach users. **What do you dislike about LaunchDarkly?** While the UI is generally clean, the platform's depth can feel overwhelming to non-technical users or beginners who just need simple toggle management. **What problems is LaunchDarkly solving and how is that benefiting you?** - Granular Targeting & Progressive Rollouts: LaunchDarkly allows you to roll out features to specific user segments, beta testers, or a percentage of your audience. This minimizes the blast radius of bugs and lets teams catch issues early before a full-scale release. - The "Instant Kill Switch": One of its most praised capabilities is the ability to instantly disable a problematic feature in production without rolling back the entire deployment or writing new code. - Beyond Simple Toggles: It handles complex use cases, such as A/B testing different LLMs (routing requests to different models in specific proportions) or targeted experimentation. **Official Response from Micaela Durkin:** > Thank you so much for sharing your experience, and it's great to hear the platform is supporting more advanced use cases like progressive rollouts and A/B testing across LLM routing. We appreciate you calling our the learning curve for non-technical users. For newer or less technical team members, our LaunchDarkly Academy can be a helpful resource for getting up to speed on the platform at their own pace and I've linked it below: ### 12. LaunchDarkly helps make feature releases safer and easier. **Rating:** 4.5/5.0 stars **Reviewed by:** Kinjal K. | Associate Product Manager, Enterprise (> 1000 emp.) **Validated Reviewer:** Validated through LinkedIn **Incentivized:** This reviewer was offered a nominal gift card as thank you for completing this review. **Source: G2 invite:** Invitation from G2. This reviewer was offered a nominal gift card as thank you for completing this review. **Reviewed Date:** August 24, 2026 **What do you like best about LaunchDarkly?** What I like most about LaunchDarkly is the complete control it offers over when a feature is released. As a PM, I prefer rolling out features gradually in collaboration with the engineering team, rather than releasing something to all users at once. Using feature flags is very straightforward, and the ability to test features with specific users before a full rollout is highly beneficial. It also facilitates coordination between product and engineering teams regarding releases, as it allows you to decouple deployment from the actual release. **What do you dislike about LaunchDarkly?** Setting it up and understanding all the options initially requires some time and a learning curve. Additionally, team members who haven't worked with feature flagging before may need some time to get used to it. **What problems is LaunchDarkly solving and how is that benefiting you?** LaunchDarkly enables safer feature releases by allowing you to roll out features to users gradually. If something goes wrong, you have the ability to instantly turn off the feature. You can also use Launch Darkly to test features with specific customers and manage distinct experiences for different user segments. This simplifies the coordination of releases between product and engineering teams. **Official Response from Micaela Durkin:** > Thank you for sharing! It's great to hear that gradual rollouts and testing with specific users have made coordination between your product and engineering teams so much smoother. The learning curve you mentioned is fair, and we'd recommend pointing new team members to the LaunchDarkly Academy to help them get up to speed faster. ### 13. Clear Customer Journey Visibility with Powerful Filters and a Polished UI **Rating:** 4.5/5.0 stars **Reviewed by:** James L. | IT Specialist, Small-Business (50 or fewer emp.) **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** Validated through LinkedIn **Incentivized:** This reviewer was offered a nominal incentive as thanks for completing this review. **Source: Seller invite:** Invitation from a seller or affiliate. This reviewer was offered a nominal incentive as thanks for completing this review. **Reviewed Date:** June 08, 2026 **What do you like best about LaunchDarkly?** I can view all aspects of the events in a customer’s journey. This is especially helpful when I need to find specific moments around an issue by using filters, such as the name of a button the user clicked. From there, it’s easy to extend the search to other customer journeys and see whether they encountered the same issue as well. Overall, this is straightforward to do because the UI is very well presented. **What do you dislike about LaunchDarkly?** It’s unfortunate that we’ve lost the ability to share individual session captures with external users. There are times when we want to provide customers with evidence of an issue or of a user’s actions, but in Launch Darkly this isn’t possible. We hoped we could work around it by adding customers as users on the platform with custom access levels. However, that also isn’t possible with Launch Darkly, which seems to offer an all-or-nothing level of sharing when it comes to sessions. This is disappointing, especially because it’s something we were very used to when using Highlight.io. Additionally while the Dashboards are fine, we would prefer this data to be exported to Grafana where we would be able to use their panels to display and transform the data as we would like. We are working on this ourselves at the moment. **What problems is LaunchDarkly solving and how is that benefiting you?** Speaking from the position of the support team, Launch Darkly allows a singular platform that we can use to troubleshoot the customer and end user journey issues. It also provides the tools for our developers to enhance the level that we can do this via custom fields. It's integration with Linear makes it easy for Issues to be raised linked to the journey and the Dashboards allow a holistic view across the front end so we can be proactive with bug investigation and fixes. **Official Response from Micaela Durkin:** > Thank you so much for the thoughtful review! We’re glad LaunchDarkly is helping your team quickly investigate customer journey issues and find patterns across sessions. We also appreciate the candid feedback on session sharing and dashboard flexibility, and we’re sharing it with our product team as we continue improving how teams collaborate and work with their data. ### 14. This makes controlling feature rollouts much easier. **Rating:** 4.5/5.0 stars **Reviewed by:** Seema S. | Product Manager, Mid-Market (51-1000 emp.) **Validated Reviewer:** Validated through LinkedIn **Incentivized:** This reviewer was offered a nominal gift card as thank you for completing this review. **Source: G2 invite:** Invitation from G2. This reviewer was offered a nominal gift card as thank you for completing this review. **Reviewed Date:** August 23, 2026 **What do you like best about LaunchDarkly?** Split makes it easy to control who can use specific features. The best part for me is that we can release a feature without making it available to every user immediately. We can enable it first for internal users or a small group of users. After gathering feedback, we can gradually roll it out to more people. As a product manager, this is incredibly beneficial because I don't have to wait for another deployment just to change access settings. It also helps maintain alignment between the product, developer, and QA teams. **What do you dislike about LaunchDarkly?** When you have a large number of feature flags, the dashboard can start to look cluttered. Also, teams need to ensure they properly remove old flags. **What problems is LaunchDarkly solving and how is that benefiting you?** This helps mitigate risks associated with new releases. We use it to control who sees new features. It allows us to test features with specific users and instantly disable them if something goes wrong. **Official Response from Micaela Durkin:** > Thanks for the detailed feedback! It's great to hear LaunchDarkly has helped keep your internal teams aligned while reducing the risk tied to new launches. We also hear you on dashboard clutter as flag volume grows, and we appreciate you flagging the importance of cleaning up old flags, I've shared the link to some of our best practices for reducing tech debt below! ### 15. Simple Yet Pricey Feature Flag Management **Rating:** 4.0/5.0 stars **Reviewed by:** Abhishek S. | Senior Product Manager, Computer Software, Mid-Market (51-1000 emp.) **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** Validated through LinkedIn **Incentivized:** This reviewer was offered a nominal gift card as thank you for completing this review. **Source: G2 invite:** Invitation from G2. This reviewer was offered a nominal gift card as thank you for completing this review. **G2 Icon:** Our network of Icons are G2 members who are recognized for their outstanding contributions and commitment to helping others through their expertise. **Reviewed Date:** July 21, 2026 At G2, we prefer fresh reviews and we like to follow up with reviewers. They may not have updated their review text, but have updated their review. **What do you like best about LaunchDarkly?** I find LaunchDarkly gets the work done as a simple but very focused product. No one inside the company ever gets confused about how to operate LaunchDarkly. It’s very simple to operate since it does one thing. **What do you dislike about LaunchDarkly?** It's expensive for the stuff it does. Fixed pricing would help because right now it’s usage-based, which sometimes makes it very expensive. Also, over time, the ease of use makes the environment complicated because there are way too many feature flags, which leads to no team member fully understanding what each flag does. It requires deep exploration every time. **What problems is LaunchDarkly solving and how is that benefiting you?** I use LaunchDarkly for feature flag management, which helps gate features for different customers and environments. It's simple to operate, so no one gets confused, making it an efficient and focused product. **Official Response from Micaela Durkin:** > We really appreciate you taking the time to share your feedback! It's great to know that the simplicity of LaunchDarkly has made feature flag management easy for your whole team to pick up, especially for gating features across different customers and environments. We also hear you on flag sprawl becoming harder to track over time. I've shared some documentation below on naming conventions which can help as you scale. If you'd ever like to talk through your experience in more depth, we'd welcome the conversation. ### 16. Intuitive UI and Robust Feature Flagging with Minor MCP Challenges **Rating:** 4.5/5.0 stars **Reviewed by:** Tarun E. | Co-founder and CTO, Mid-Market (51-1000 emp.) **Validated Reviewer:** Validated through Google One Tap using a business email account **Incentivized:** This reviewer was offered a nominal gift card as thank you for completing this review. **Source: G2 invite:** Invitation from G2. This reviewer was offered a nominal gift card as thank you for completing this review. **Reviewed Date:** August 16, 2026 **What do you like best about LaunchDarkly?** I use LaunchDarkly mainly for feature flags, and it's great because I can enable features without code deployment and serve variations based on users, organizations, locales, countries, regions, etc. The UI is very intuitive and easy to work with, which I really appreciate. The reporting feature is very comprehensive, showing a lot of stats and metrics. It's also super easy to understand what percentage of the audience has been served what variations. Plus, LaunchDarkly has an SDK that integrates very well with our application, making it all seamless. The initial setup was very easy too. **What do you dislike about LaunchDarkly?** I find MCP does not support team users well, and it wasn't easy for me to use LaunchDarkly's MCP with Claude Code due to the enterprise settings. I also find the access control complex. **What problems is LaunchDarkly solving and how is that benefiting you?** I use LaunchDarkly to enable features without code deployment and serve variations based on user and other factors. Its intuitive UI and comprehensive reporting make it easy to understand audience reach. **Official Response from Micaela Durkin:** > Thank you for sharing such a detailed review! It's great to hear the intuitive UI, comprehensive reporting, and seamless SDK integration have made feature flag management easier for your team. We also appreciate you flagging the MCP and access control challenges with enterprise settings, and we'll be sure to pass that feedback along to our product team. ### 17. Safer, Faster Releases with Flags, Targeting, and Real-Time Updates **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Logistics and Supply Chain | Mid-Market (51-1000 emp.) This reviewer's identity has been verified by our review moderation team. They have asked not to show their name, job title, or picture. **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** Validated through a business email account **Incentivized:** This reviewer was offered a nominal incentive as thanks for completing this review. **Source: Seller invite:** Invitation from a seller or affiliate. This reviewer was offered a nominal incentive as thanks for completing this review. **Reviewed Date:** August 13, 2026 **What do you like best about LaunchDarkly?** The thing that changed how we ship is being able to deploy and release separately. We put a whole customer-facing chat widget into production completely dark behind a flag that defaulted to off, merging it changed nothing for real users, which meant the code stopped rotting on a branch while we waited on a product decision. Custom context attributes are the other big one: we pass country, partner type and access level into the context, so we can roll a feature out to one country or one partner segment without touching code. Targeting changes take effect in the running app in seconds via the streaming connection, no redeploy. JSON flags carrying config payloads (not just booleans) have also saved us a couple of releases. **What do you dislike about LaunchDarkly?** Client-side initialization is the rough edge. bootstrap: 'localStorage' doesn't reliably hand you every flag before first render, so we ended up hand-rolling our own flag cache in localStorage on one app to avoid UI flicker on load — that's a known, long-standing SDK issue and it should really be solved in the SDK. In our Nuxt app we also had to write a retry loop that polls for client readiness because the LD client isn't guaranteed to be up when a component first asks for a flag; a first-class "await ready then subscribe" primitive would remove a lot of fragile glue. Flag cleanup is also on us - nothing nudges you when a flag has been at 100% for six months, so stale flags accumulate. **What problems is LaunchDarkly solving and how is that benefiting you?** Two things. First, decoupling deploy from release: risky work merges early and ships dark, so we're not sitting on long-lived branches waiting for a sign-off. Second, progressive migration. We're moving users off a legacy Angular portal onto a new one, and a flag decides per user whether they get redirected — which turns a scary big-bang cutover into something we can ramp and instantly roll back. We operate across six countries, so per-country rollout of region-specific forms and features is the other daily benefit, enable in one market, watch it, then widen. **Official Response from Micaela Durkin:** > Thank you for such a detailed review! It's great to hear that decoupling deploy and release, custom context targeting by country and partner segment, and JSON flags have changed how your team ships, and the Angular portal migration sounds like a perfect use case for that kind of controlled rollout. On the client-side initialization timing you ran into with the Nuxt app, we just published a pre-release of our Vue client SDK that addresses the localStorage bootstrap issue you described, so we'd love for you to give it a try and let us know how it holds up. We appreciate you sharing this level of detail and will make sure the team sees your note on flag cleanup as well. [!CAUTION] This SDK is in pre-release and not subject to backwards compatibility guarantees. The API may change based on feedback.*** ### 18. Safe and fast progressive deployments with LaunchDarkly **Rating:** 5.0/5.0 stars **Reviewed by:** Damián Y. | Presales, Information Technology and Services, Small-Business (50 or fewer emp.) **Validated Reviewer:** Validated through a business email account **Incentivized:** This reviewer was offered a nominal gift card as thank you for completing this review. **Source: G2 invite:** Invitation from G2. This reviewer was offered a nominal gift card as thank you for completing this review. **AI Translated:** This review has been translated from Spanish; Castilian using AI. **Reviewed Date:** August 11, 2026 **What do you like best about LaunchDarkly?** What I like most about LaunchDarkly is that it allows separating the deployment from the release of a feature. We can publish code and enable it gradually by users, segments, or percentages, and also disable it immediately if a problem arises. Its interface is clear, the SDKs and integrations with CI/CD processes facilitate implementation, and the performance is stable even in progressive deployments. This reduces risk, avoids complete rollbacks, and accelerates delivery, generating a good return on investment. The documentation and initial support help overcome the learning curve. I also value the intelligent segmentation and A/B testing, because they allow making decisions based on real results. **What do you dislike about LaunchDarkly?** What I like the least is that the interface can become complex when managing many flags, especially because obsolete ones accumulate if there is no cleanup process. The initial setup also requires expertise, and some integrations or SDKs offer different levels of logging and diagnostics. Although performance is usually stable, relying on an external service requires designing backup mechanisms in case of connectivity issues. The price increases rapidly depending on usage, which can affect ROI in large organizations. I would also improve the integrated analytics by incorporating intelligent recommendations to detect unused flags, risks, and optimization opportunities. A more practical onboarding guide would help reduce the learning curve. **What problems is LaunchDarkly solving and how is that benefiting you?** Before, each release depended on a new deployment, and any failure could force us to do a complete rollback. With LaunchDarkly, on the other hand, we can release the code with the functionality turned off, validate it first with internal users, and then enable it progressively by segments. If a problem arises, we disable it in seconds, without needing to restart the application. This reduces interruptions, speeds up deliveries, and decreases operational work, which translates into a better ROI. Additionally, the integrations with CI/CD and its SDKs help automate the flow, while the interface, documentation, and support make management easier. Finally, A/B testing and segmentation allow us to evaluate real results before extending a feature to all users. **Official Response from Micaela Durkin:** > Thank you for such a detailed and thoughtful review! We're so glad to hear that separating deployment from release has changed how your team manages risk, and that the CI/CD integrations, SDKs, and A/B testing capabilities have made real-time, data-driven decisions possible for your releases. Your point about flag cleanup and onboarding is well taken, and we'd love to share some resources on flag lifecycle management that other customers have found helpful for keeping things organized as usage scales. We appreciate your partnership and the confidence you've placed in LaunchDarkly. ### 19. Effortlessly Manages Feature Flags Across Environments **Rating:** 4.0/5.0 stars **Reviewed by:** AYUSH P. | Software engineer, Mid-Market (51-1000 emp.) **Validated Reviewer:** Validated through LinkedIn **Incentivized:** This reviewer was offered a nominal incentive as thanks for completing this review. **Source: Seller invite:** Invitation from a seller or affiliate. This reviewer was offered a nominal incentive as thanks for completing this review. **Reviewed Date:** August 11, 2026 **What do you like best about LaunchDarkly?** I have been using LaunchDarkly for our main server to maintain client customizations and business logic. It's really intuitive and flexible, allowing me to easily maintain and update the flags without changing code and going to the database. The best thing about LaunchDarkly is the ability to manage different environments like production, pre-production, and development without creating a flag separately in each environment. It helps me route users to dedicated databases and switch users under one client to a different region, and any client customization is directly served from LaunchDarkly. The initial setup was very easy; we just asked our IT team to get access and simply started adding flags. **What do you dislike about LaunchDarkly?** I find it could be a bit easier to create and delete through the SDK. **What problems is LaunchDarkly solving and how is that benefiting you?** I use LaunchDarkly to easily maintain and update flags without changing code, manage different environments effortlessly, and route users to the right databases. It's intuitive and flexible, handling client customizations effectively. **Official Response from Micaela Durkin:** > Thank you for sharing how LaunchDarkly is powering your client customizations and multi-region routing, that kind of flexibility across environments without duplicating flags is exactly what we're going for! ### 20. Instant Rollbacks and Peace of Mind During Releases **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Human Resources | Mid-Market (51-1000 emp.) This reviewer's identity has been verified by our review moderation team. They have asked not to show their name, job title, or picture. **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** This review contains authentic analysis and has been reviewed by our team **Incentivized:** This reviewer was offered a nominal incentive as thanks for completing this review. **Source: Seller invite:** Invitation from a seller or affiliate. This reviewer was offered a nominal incentive as thanks for completing this review. **Reviewed Date:** August 10, 2026 **What do you like best about LaunchDarkly?** The instant rollback is what sold me on it honestly. We had a situation where something went wrong in production and instead of scrambling to revert a deployment and wait for a pipeline to run, we just turned the flag off and it was done in seconds. That alone is worth it. The peace of mind during releases is just different when you know you can kill something instantly without touching the codebase or waiting on CI. **What do you dislike about LaunchDarkly?** Pricing creeps up on you fast. When you're starting out it feels reasonable but as the team grows and you start adding more flags and more users it gets expensive pretty quickly. For smaller teams or early stage companies it might be hard to justify the cost compared to rolling something simpler yourself. Worth it if you're at scale but the jump in pricing can catch you off guard. **What problems is LaunchDarkly solving and how is that benefiting you?** It basically decoupled our deploys from our releases which is a bigger deal than it sounds. We can ship code to production whenever it's ready and then decide separately when to actually turn it on for users. No more coordinating releases with specific deploy windows or stressing about rolling back a bad deploy. The team ships with a lot more confidence now knowing there's always a quick way out if something goes sideways. ### 21. Operational agility at scale — deploys replaced by toggles **Rating:** 4.5/5.0 stars **Reviewed by:** Parth M. | Senior Backend Engineer, Mid-Market (51-1000 emp.) **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** Validated through a business email account **Incentivized:** This reviewer was offered a nominal incentive as thanks for completing this review. **Source: Seller invite:** Invitation from a seller or affiliate. This reviewer was offered a nominal incentive as thanks for completing this review. **Reviewed Date:** May 26, 2026 **What do you like best about LaunchDarkly?** UI / UX Intuitive flag management: toggling, targeting rules by account/region, and scheduled rollouts work out of the box Strong visibility — see active flags, their targets, and last-modified status at a glance At 100+ flags across services, the UI gets noisy; we rely on naming conventions (rollout-*, enable-*, configure-*) and project organization to stay navigable Filtering and search are functional but underpowered for teams at our scale Integrations Clean integration with our Java backend via the Server SDK Built a centralized wrapper service that all modules consume — no service talks to LD directly DynamoDB persistent store ensures flags survive SDK restarts without re-fetching from LD cloud (critical for production reliability) CI workflow auto-syncs code references on every push, keeping the LD dashboard aware of where each flag is actually used Local development runs against a containerized LD dev server or plain YAML files — no live LD connection required Performance Core to how we operate our large-scale monorepo for real-time event ingestion and multi-channel engagement 128+ feature flags embedded across 229 files in the core pipeline Shifted our workflow from "change code and deploy" to "toggle and observe" For a platform processing millions of events in real time, this directly reduces incident blast radius and dropped events Pricing / ROI Each skipped config-change deploy saves 30–60 minutes of engineer time ~25 flag changes/month = 12–25 engineering hours saved on deploys alone Runtime tuning (thread pools, processing limits, retry intervals) dropped from 2–4 hours per iteration to ~5 minutes Incident math is the clincher: one kill-switch save of 30 minutes downtime on the real-time pipeline justifies the annual cost Pricing scales with seats and flag evaluations — expensive at enterprise scale, but cheaper than the alternative (more deploys, longer incidents, slower rollouts) Support / Onboarding Low-friction onboarding thanks to our wrapper layer — engineers learn our internal API, not the LD SDK Official LD documentation and SDK docs are solid File-based mode for tests and a local dev server let new developers work with flags from day one without LD credentials Upfront investment went into defining our targeting context model (infrastructure, account, custom attributes) — self-sustaining once established AI / Intelligence LLM Gateway uses a JSON flag to dynamically route accounts across AI model providers, with built-in regional compliance validation A background worker polls a flag every minute to add/remove accounts from historic processing workflows Flags control file-size limits per content type in our AI tooling layer Net effect: a control plane for inherently experimental AI features — model swaps, threshold tuning, per-account gating — without code deploys **What do you dislike about LaunchDarkly?** UI / UX While lifecycle stages and archival suggestions exist, once you get to 100+ flags the dashboard still lacks service- or team-based grouping. Naming conventions end up being the main organizational tool. Native folders or tag-based grouping by service would lower cognitive overhead. The targeting rule builder becomes unwieldy with complex, multi-context rules (infrastructure + account + custom attributes). Managing nested conditions is cumbersome for power users. Flag search and filtering are fine at small-to-mid scale, but at enterprise flag volumes, bulk operations and cross-project visibility feel limited. Integrations The DynamoDB persistent store has a hard 400KB per-item limit. Flags that exceed this are silently skipped with only an ERROR log, with no proactive alerting or dashboard visibility. On cold start with a persistent store, the SDK serves last-known (potentially stale) flag data and is technically “not initialized” until streaming reconnects. For kill switches or processing limits, that stale-default window is operationally risky. Local-to-production flag parity is still a manual discipline. File-based local configs can drift from production state and create environment mismatches. Performance Streaming connections can drop in containerized environments behind load balancers due to network timeouts. The SDK does auto-reconnect and exposes status listeners (DataSourceStatusProvider), but the reconnection window still creates brief stale-flag exposure under load. For high-throughput services evaluating flags on every request, evaluation overhead compounds. The SDK doesn’t provide built-in per-flag evaluation latency metrics, so teams have to instrument this themselves. Cold-start hydration from DynamoDB is slower than in-memory. During this window, flags fall back to coded defaults, which can cause unexpected behavior for critical operational flags. Pricing / ROI ~~Seat-based pricing doesn't differentiate roles~~ — corrected: LD now offers unlimited seats on Developer and Foundation tiers. However, usage-based pricing (service connections, MAUs) can be hard to predict for high-throughput platforms. Better cost-forecasting tools within LD would help. Enterprise and Guardian tier pricing is fully custom with no published benchmarks, which makes it difficult to budget or compare without a sales conversation. Evaluation volume costs are opaque at scale. There’s no self-serve way to model, “If we add X more flags across Y services, what’s the cost impact?” Support / Onboarding Documentation covers the basics well, but advanced patterns (multi-context targeting design, persistent store tuning, high-throughput optimization) are scattered across blog posts, support articles, and GitHub issues instead of being consolidated in one place. For production incidents involving SDK streaming behavior or cache inconsistencies, troubleshooting requires correlating SDK status listeners, DynamoDB state, and network logs. A unified diagnostics view would speed resolution. There are no published reference architectures for high-throughput event platforms. Teams designing targeting context models at scale are largely self-guided. AI / Intelligence LD launched AI Experiments, AI Versioning, and AI Configs (GA May 2025) — a significant step forward. However, compliance-aware model routing (ensuring data doesn’t flow to disallowed regions) is still custom logic that teams must build themselves. Feedback-loop-driven flag decisions (tying flag choices to downstream quality metrics automatically) aren’t natively supported. Experimentation still requires manual metric setup rather than closed-loop optimization. For teams already managing AI features via plain JSON flags (model overrides, prompt configs), the migration path to the new AI Configs feature isn’t well documented. **What problems is LaunchDarkly solving and how is that benefiting you?** Before LaunchDarkly, every configuration change or feature toggle required a full deploy cycle—30–60 minutes minimum in a large monorepo. Incident response meant writing a fix, getting it reviewed, building, and deploying, which easily took 1–4 hours while the issue continued impacting users. Rollouts were all-or-nothing, and per-customer feature management often meant hardcoded account lists living in the code. Since adopting LaunchDarkly, incident response has gone from hours to seconds. Kill-switch flags let us disable a broken feature immediately instead of waiting for a full deploy. For a real-time event pipeline, that difference can prevent significant data loss during outages. We can also tune configuration without deploys. Thread pools, processing limits, and retry intervals are now managed via flags. A tuning cycle that used to take 2–4 hours per iteration (change → deploy → observe) now takes about 5 minutes. Progressive rollouts have replaced the old all-or-nothing approach. We can ship to 1% of accounts first, and if a bug is caught at 5% rollout, it affects 20x fewer users—dramatically reducing support escalations. Per-customer targeting no longer requires code changes. Enabling features for specific accounts used to mean a PR plus a deploy; now it’s just a flag rule change, saving dozens of engineering hours across 30+ account-targeted flags. Finally, teams can ship more independently. Code can merge behind disabled flags, and PMs can toggle features when they’re ready. That has eliminated long-lived branches, reduced merge conflicts, and removed a lot of release-day coordination across teams. **Official Response from Micaela Durkin:** > Thank you for the detailed review! We’re glad LaunchDarkly is helping your team manage rollouts, operational tuning, and AI-driven workflows with more speed, control, and less risk in a high-throughput environment. We also appreciate the candid feedback—this helps shape where we continue to invest. We’re also expanding this area with AgentControl, which helps teams govern AI agents in production, continuously evaluate prompts and models, and respond to drift or performance issues without redeploying. I've linked the documentation below! ### 22. Intuitive UI, Powerful Integrations, and Low-Latency Feature Flagging **Rating:** 4.5/5.0 stars **Reviewed by:** Shubham C. | Senior Frontend Engineer, Mid-Market (51-1000 emp.) **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** Validated through a business email account **Incentivized:** This reviewer was offered a nominal incentive as thanks for completing this review. **Source: Seller invite:** Invitation from a seller or affiliate. This reviewer was offered a nominal incentive as thanks for completing this review. **Reviewed Date:** May 26, 2026 **What do you like best about LaunchDarkly?** The UI is genuinely well thought out. Managing flags, setting up targeting rules, and navigating environments never feels overwhelming — everything is where you'd expect it to be. For a tool that can get complex quickly, it stays remarkably approachable even as your flag count grows. The integrations are where it really shines for day-to-day engineering work. It plugs into pretty much everything — your CI/CD pipeline, Slack, DataDog, Jira — so flag activity doesn't live in isolation. You get context right where you already work, which makes it much easier to correlate a rollout with a spike in errors or a support ticket. And performance-wise, the SDKs are built with latency in mind. Flag evaluations happen locally after the initial sync, so you're not making a network call every time a flag is checked. For a frontend-heavy application where you might be evaluating flags on every render or route change, that matters a lot. The streaming updates also mean flag changes propagate almost instantly without you having to poll or refresh anything. **What do you dislike about LaunchDarkly?** The onboarding process for this tool is very confusing, especially for something that is supposed to be simple to use and meant to help others simplify processes. Sure, adding the SDK is simple. But the trick is figuring out how to appropriately set up and organize your environments, your projects, and your contexts. This process is tricky to say the least, and it fails to cover the why in the explanation of the architecture, if it covers it at all. Support is available, but it is more of a last resort, as help is only given slowly and at great length when asked. Their AI is impressive but still has more room for development and improvement. They talk a lot about data driven rollouts, but the only data when using the platform is very base data, which is rather disappointing. For a platform that holds so much behavioral data, it seems like a large miss to not have the platform offer suggestions for smarter data based decisions. Suggestions like setting automatic thresholds for rollout based on historical data or flagging outdated rolling data are all things the platform could be doing and are not. **What problems is LaunchDarkly solving and how is that benefiting you?** Before LaunchDarkly, every production release was an all-or-nothing event. If something broke, we were either rolling back the entire deployment or pushing a hotfix under pressure. Over time, that made our team risk-averse — we'd delay shipping, over-bundle changes, and still dread release day. On top of that, any kind of A/B testing was a separate, heavyweight process that required coordinating with the data team, setting up custom tooling, and waiting weeks before we had anything conclusive. We struggled with both the all-or-nothing nature of deployments and the lack of a lightweight experimentation workflow, but now we can decouple releases from deployments and run A/B tests directly within the same flag infrastructure. This has resulted in two compounding benefits — faster, safer rollouts and data-backed feature decisions without needing a separate experimentation platform. On the deployment side, catching critical issues now happens within the first hour of a limited rollout rather than days later. Incident response time has dropped from a stressful 2–3-hour process to under 15 minutes in most cases. On the experimentation side, we've gone from running maybe one or two A/B tests a quarter to running them continuously — testing copy changes, UI variations, and new feature flows with real user segments without any additional infrastructure overhead. The biggest shift is cultural. The team no longer treats releasing as a risky event or experimentation as a big project. Both are now just part of how we ship. LaunchDarkly collapsed two separate problems — safe deployments and structured experimentation — into a single workflow, and the compounded time savings and confidence gains have been significant. **Official Response from Micaela Durkin:** > Thank you for sharing such a thoughtful review! We’re so glad LaunchDarkly is helping your team ship more safely and experiment with confidence. We also appreciate the candid feedback on onboarding, and for anyone getting started, LaunchDarkly Academy offers great guided training and resources to help teams ramp up faster. I included the link below. ### 23. Precise Feature Rollouts and Instant Kill Switches with LaunchDarkly **Rating:** 5.0/5.0 stars **Reviewed by:** Yashdeep S. | Staff Engineer DevOps, Mid-Market (51-1000 emp.) **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** Validated through LinkedIn **Incentivized:** This reviewer was offered a nominal incentive as thanks for completing this review. **Source: Seller invite:** Invitation from a seller or affiliate. This reviewer was offered a nominal incentive as thanks for completing this review. **Reviewed Date:** May 22, 2026 At G2, we prefer fresh reviews and we like to follow up with reviewers. They may not have updated their review text, but have updated their review. **What do you like best about LaunchDarkly?** LaunchDarkly gives us precise control over feature rollouts without requiring new deployments. The per-account targeting rules are especially valuable for enterprise software — we can enable beta features for specific customers, run gradual rollouts, and kill-switch anything gone wrong instantly. The audit trail also helps during incidents: we can quickly see if a recent flag change correlates with a problem. **What do you dislike about LaunchDarkly?** The main friction point is flag hygiene — LaunchDarkly makes it easy to create flags but doesn't enforce a lifecycle. Stale flags accumulate and become invisible tech debt. Pricing can also be a concern at scale, especially for high-MAU B2C products. We'd love better built-in tooling for flag retirement workflows and technical debt tracking **What problems is LaunchDarkly solving and how is that benefiting you?** LaunchDarkly solves the core problem of separating code deployment from feature release. For a multi-tenant B2B platform, this is essential — we can ship code continuously and control exactly which accounts see which features. It's also eliminated an entire class of hotfix deploys: production issues caused by a new feature are now resolved in seconds by toggling a flag rather than going through a full release cycle. The visibility it gives to non-engineering teams (support, TAMs) has also reduced internal back-and-forth on 'is feature X enabled for customer Y. ### 24. Better Control Deploying Features . **Rating:** 4.5/5.0 stars **Reviewed by:** Mohini G. | Information Technology Infrastructure Manager, Enterprise (> 1000 emp.) **Validated Reviewer:** Validated through LinkedIn **Incentivized:** This reviewer was offered a nominal gift card as thank you for completing this review. **Source: G2 invite:** Invitation from G2. This reviewer was offered a nominal gift card as thank you for completing this review. **Reviewed Date:** August 24, 2026 **What do you like best about LaunchDarkly?** LaunchDarkly allows for controlled releases of features. I enjoy having control of features through feature flags. They allow us to turn features on and off and even test features without having to deploy. Rollout controls and targeting options are extremely helpful when deploying features gradually. Also allows for better development and operations collaboration by having more visibility of what features are turned on per environment. **What do you dislike about LaunchDarkly?** The only issue I’ve encountered is when you start to accumulate a lot of feature flags. There would need to be proper policy around reviewing/removing old flags. **What problems is LaunchDarkly solving and how is that benefiting you?** Less risk when releasing features. With LaunchDarkly we have the ability to gradually roll out features. Instead of pushing changes to everyone we can monitor and fix issues along the way. This allows teams to feel confident about deployments, increase stability and get features shipped quicker with better control of production. **Official Response from Micaela Durkin:** > Thank you so much for the thoughtful feedback and for highlighting how controlled releases and targeting have helped your dev and ops teams collaborate more effectively. Your point about flag accumulation is a common one, and we have a guide on reducing technical debt from feature flags that covers best practices for reviewing and archiving old flags ### 25. Review **Rating:** 4.0/5.0 stars **Reviewed by:** Facundo D. | Arquitecto de software, Mid-Market (51-1000 emp.) **Validated Reviewer:** Validated through a business email account added to their profile **Incentivized:** This reviewer was offered a nominal incentive as thanks for completing this review. **Source: Seller invite:** Invitation from a seller or affiliate. This reviewer was offered a nominal incentive as thanks for completing this review. **AI Translated:** This review has been translated from Spanish; Castilian using AI. **Reviewed Date:** August 28, 2026 ### 26. LaunchDarkly Makes Staggered Deployments Fast, Smooth, and Easy **Rating:** 4.5/5.0 stars **Reviewed by:** Vishvaas J. | Associate Director, Mid-Market (51-1000 emp.) **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** Validated through a business email account **Incentivized:** This reviewer was offered a nominal incentive as thanks for completing this review. **Source: Seller invite:** Invitation from a seller or affiliate. This reviewer was offered a nominal incentive as thanks for completing this review. **Reviewed Date:** May 22, 2026 At G2, we prefer fresh reviews and we like to follow up with reviewers. They may not have updated their review text, but have updated their review. **What do you like best about LaunchDarkly?** LaunchDarkly enables staggered deployments and helps our teams release features faster. Its integrations with our Slack channels make it easy to approve and apply changes without friction. The UX is intuitive and straightforward to understand, so it doesn’t take long to get comfortable using it. Performance and uptime have never been an issue for us with LaunchDarkly, and rollouts have been consistently smooth. Pricing feels reasonable given the feature set and how easy it is to manage deployments. LaunchDarkly support is also prompt, responding quickly and helping resolve issues efficiently. We haven’t used any AI features yet, but the core functionality has been genuinely useful. **What do you dislike about LaunchDarkly?** There is nothing to dislike about LaunchDarkly. **What problems is LaunchDarkly solving and how is that benefiting you?** We are able to have staggered deplyoments, alpha and beta rollouts and customer directed feature rollouts with Launchdarkly. We are also able to help developers by controlling detailed logging via launchdarkly, which has been really helpful for monitoring and alerting. **Official Response from Micaela Durkin:** > Thank you for leaving us such a thoughtful review! We're so glad to hear staggered deployments and rollouts have been smooth, and that the Slack integration and support experience have been working well for you too. Now is actually a great time to explore our AI features since we just launched AgentControl! Agent behavior shifts in production without warning and AgentControl helps keep agents on track, blocking bad behavior and steering responses in real time. Check it out. Thanks again for the kind words! ### 27. Reliable Feature Flag Platform for Safe Deploymentst and Confident Rollouts **Rating:** 4.5/5.0 stars **Reviewed by:** Harshita T. | Data scientist, Mid-Market (51-1000 emp.) **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** This review contains authentic analysis and has been reviewed by our team **Incentivized:** This reviewer was offered a nominal incentive as thanks for completing this review. **Source: Seller invite:** Invitation from a seller or affiliate. This reviewer was offered a nominal incentive as thanks for completing this review. **Reviewed Date:** May 24, 2026 **What do you like best about LaunchDarkly?** What I like most about LaunchDarkly is how straightforward it makes feature flag management and controlled rollouts. It lets teams release features gradually, test safely in production, and quickly roll back changes when needed—all without redeploying code. The dashboard feels intuitive, the integrations with CI/CD workflows are smooth, and the targeting rules provide a lot of flexibility for experimentation and user segmentation. Overall, it helps reduce deployment risk and boosts release confidence for both engineering and product teams. **What do you dislike about LaunchDarkly?** While LaunchDarkly is a very powerful platform, there are a few areas that could be improved. The pricing structure can be challenging for smaller organizations as feature usage grows, and some advanced capabilities take time to fully understand and use effectively. It offers a wide range of configuration options, but the UI can occasionally feel overly complex, especially when managing a large number of feature flags. Stronger onboarding guidance, simpler navigation, and more built-in analytics would make the overall experience even better. **What problems is LaunchDarkly solving and how is that benefiting you?** LaunchDarkly has helped us address the risks of software deployments and the lack of fine-grained release control. Before we started using it, shipping new features often meant deploying to everyone at once, which raised the chance of production issues and made rollbacks slow and painful. Now we can roll out changes gradually to specific user segments, run experiments more safely, and turn off problematic features immediately without redeploying the application. As a result, we feel more confident during deployments, face less risk of downtime, and have been able to speed up our release cycle significantly. Its integrations with our CI/CD pipelines and monitoring tools have also made it easier for engineering and product teams to stay aligned and collaborate. Overall, it’s enabled faster innovation while maintaining stronger stability and a better user experience. **Official Response from Micaela Durkin:** > We really appreciate you taking the time to leave us a review! Reducing deployment risk while giving teams the confidence to ship faster — that's the goal. Really glad it's working so well for your team. On the learning curve for advanced features, LaunchDarkly Academy is a great resource for getting new team members up to speed. It has self-guided courses, hands-on workshops, and certifications. Thanks again for the thoughtful review! ### 28. Confident Continuous Delivery with Feature Flags and Instant Rollbacks **Rating:** 5.0/5.0 stars **Reviewed by:** Brauny N. | Site Reliability Analyst, Enterprise (> 1000 emp.) **Validated Reviewer:** Validated through Google using a business email account **Incentivized:** This reviewer was offered a nominal gift card as thank you for completing this review. **Source: G2 invite:** Invitation from G2. This reviewer was offered a nominal gift card as thank you for completing this review. **Reviewed Date:** August 07, 2026 **What do you like best about LaunchDarkly?** The ability to deploy code independently from feature releases. Feature flags give us the confidence to ship continuously without risk — we can roll out changes gradually, target specific segments, and instantly roll back if something goes wrong, all without a redeployment. **What do you dislike about LaunchDarkly?** Flag debt builds up quickly. It’s easy to create flags for a release and then never clean them up, and over time you end up with dozens of stale flags that nobody is confident are safe to remove. More robust built-in tooling to surface old flags, confirm whether they’re still in use, and help retire them would make a big difference. **What problems is LaunchDarkly solving and how is that benefiting you?** LaunchDarkly decouples our deployments from our releases, so engineers can merge and deploy code at any time without it immediately going “live” for users. This has significantly reduced our release risk: we can roll out changes gradually, catch issues early by exposing them to a small percentage of traffic, and instantly kill a feature if something breaks. It also takes the pressure off big-bang releases and gives the business more control over when features are visible and which users can see them. **Official Response from Micaela Durkin:** > Thank you for sharing how LaunchDarkly helps your team decouple deployments from releases, roll out changes safely, and reduce release risk! We also appreciate your candid feedback on flag debt, if it's helpful, I've shared some of our best practice guides below. ### 29. The tool that made Friday deployments feel safe with Gradual rollouts and A/B testing **Rating:** 5.0/5.0 stars **Reviewed by:** Prayush J. | Senior Software Developer, Mid-Market (51-1000 emp.) **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** Validated through Google using a business email account **Incentivized:** This reviewer was offered a nominal incentive as thanks for completing this review. **Source: Seller invite:** Invitation from a seller or affiliate. This reviewer was offered a nominal incentive as thanks for completing this review. **Reviewed Date:** May 22, 2026 **What do you like best about LaunchDarkly?** The integration was straightforward we plugged it into our existing setup without major friction. Their documentation covers most common use cases well enough that we rarely needed to raise a support ticket. Gradual rollouts and flexible targeting rules make A/B testing and experimentation seamless, no extra infrastructure needed. The UI is clean and intuitive; creating and managing flags takes seconds, and the targeting rules editor is easy to navigate even for non-engineers and Product Managers on the team. Performance has been solid, flag evaluations are fast and we haven't seen any noticeable latency impact on our services. What I like most is the deploy-release decoupling. Code ships behind a flag and gets enabled for a specific user, a percentage of traffic, or a whole segment, no redeploy needed. Rollbacks become a toggle instead of a fire drill. **What do you dislike about LaunchDarkly?** Pricing can feel steep for smaller teams, and at lower usage tiers it’s harder to justify the ROI. My main pain point right now is enforcing rules around describing exactly how a given FF works, so that the documentation stays consistent and clear. **What problems is LaunchDarkly solving and how is that benefiting you?** The biggest benefit is that releases have stopped being scary. Engineers ship more often, on-call is quieter, and product can run real experiments instead of guessing. For teams operating across multiple regions and customer segments, targeted flag evaluation makes it easier to ensure the right features reach the right users without needing separate deployments. Overall, it’s improved our confidence in releases, reduced MTTR, and given both product and engineering more autonomy and control over how features are delivered. **Official Response from Micaela Durkin:** > Releases stopped being scary! Love hearing that your whole team, engineers and PMs alike, can work confidently in LaunchDarkly. On flag documentation, that's fair feedback. Flag descriptions and naming conventions can go a long way, our flag conventions guide has some good patterns for keeping things consistent across teams. Thank you so much for the thorough review! ### 30. Stress-Free Deployments with Instant Feature Toggles **Rating:** 5.0/5.0 stars **Reviewed by:** Yashdeep S. | Senior Devops Engineer, Mid-Market (51-1000 emp.) **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** Validated through a business email account **Incentivized:** This reviewer was offered a nominal incentive as thanks for completing this review. **Source: Seller invite:** Invitation from a seller or affiliate. This reviewer was offered a nominal incentive as thanks for completing this review. **Reviewed Date:** May 22, 2026 **What do you like best about LaunchDarkly?** It takes the stress out of production deployments. If a new feature starts throwing 500 errors or leaking memory in production at 3:00 AM, nobody has to panic, scramble to roll back a deployment, or rush an emergency hotfix through CI/CD. You just flip the toggle in the UI, the feature disappears instantly for users, and the team can debug it safely the next morning. **What do you dislike about LaunchDarkly?** This is the single biggest headache. LaunchDarkly makes it so easy to create a feature flag that people create them for everything. But once a feature is 100% rolled out and stable, teams often forget to go back into the code to remove the if/else logic and delete the flag from the dashboard. **What problems is LaunchDarkly solving and how is that benefiting you?** It separates infrastructure deployment from feature release. You can deploy the code directly to your ECS Fargate or EKS clusters behind a flag. The code sits dormant, processing nothing. You then use LaunchDarkly to dynamically open the valve—routing just 0.5% of incoming tracking events or push payloads through the new code path. If the connection pools hold and latencies spike by 0ms, you scale it up. If things go sideways, you don't roll back the containers; you flip the toggle and drop traffic back to 0% in milliseconds. **Official Response from Micaela Durkin:** > Thank you for the kind words! We love to hear that we've given you your nights and weekends back. Flag sprawl is a pain we hear about often. Our flag hygiene docs are a great resource, which I've linked below. Also, if you use GitHub check out Vega, our AI agent that automates flag cleanup. It checks staleness, verifies safety, and opens a PR to remove the code for you. Thank you again for the detailed review! ### 31. Safer Feature Releases and Smooth Rollouts with LaunchDarkly **Rating:** 4.5/5.0 stars **Reviewed by:** LOKESH G. | Engineer.SGB TCS-FS CORE BANKING,Production, Information Technology and Services, Enterprise (> 1000 emp.) **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** Validated through LinkedIn **Incentivized:** This reviewer was offered a nominal gift card as thank you for completing this review. **Source: G2 invite:** Invitation from G2. This reviewer was offered a nominal gift card as thank you for completing this review. **G2 Icon:** Our network of Icons are G2 members who are recognized for their outstanding contributions and commitment to helping others through their expertise. **Reviewed Date:** August 05, 2026 **What do you like best about LaunchDarkly?** I like LaunchDarkly because it makes it easy to release new features safely, manage feature rollouts, and quickly turn features on or off without deploying new code. Overall, it helps reduce risk and makes the software release process smoother and more controlled. **What do you dislike about LaunchDarkly?** It can be expensive for smaller teams, and some of the more advanced features take time to learn. Managing a large number of feature flags can also become difficult without proper organization.** **What problems is LaunchDarkly solving and how is that benefiting you?** LaunchDarkly helps me manage feature releases safely without having to deploy new code each time. It reduces release risk, speeds up deployments, makes testing easier, and lets me fix issues quickly by turning features on or off instantly. **Official Response from Micaela Durkin:** > We love to hear it! It's great to know LaunchDarkly helps you release features safely, reduce risk, and move faster without redeploying code. We also appreciate your feedback and using tags to categorize and filter flags can help keep everything organized. You can learn more in our Tags documentation which I added below if it's helpful. ### 32. Safer, More Controlled Releases with LaunchDarkly Feature Flags **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Oil & Energy | Mid-Market (51-1000 emp.) This reviewer's identity has been verified by our review moderation team. They have asked not to show their name, job title, or picture. **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** Validated through a business email account **Incentivized:** This reviewer was offered a nominal gift card as thank you for completing this review. **Source: G2 invite:** Invitation from G2. This reviewer was offered a nominal gift card as thank you for completing this review. **G2 Icon:** Our network of Icons are G2 members who are recognized for their outstanding contributions and commitment to helping others through their expertise. **Reviewed Date:** August 03, 2026 **What do you like best about LaunchDarkly?** What I like most about this LaunchDarkly platform is its ability to separate feature releases from the core deployments, and its feature flags allow our team to release new functionality gradually, and their test changes with specific user segments can be rolled back instantly if the issue keeps arising, even without requiring any new deployment. Their platform also integrates well with our CD pipelines, which provides excellent targeting capabilities and makes software releases much safer and more controlled. Overall, this has significantly improved our deployment confidence and reduced our operational risk. **What do you dislike about LaunchDarkly?** This platform offers many advanced capabilities, so there is also a complex learning curve for teams who are adapting to their feature flag management for the first time, and their onboarding is also a bit complicated, which should be made easier at this point. Managing a large number of feature flags along with good governance is a bit of a hectic task to avoid accumulating technical debt. Additionally, some of their enterprise capabilities are available only on higher pricing tyres which may be expensive for a bit too small organisations. **What problems is LaunchDarkly solving and how is that benefiting you?** This platform solves the challenge of deploying software safely, even without exposing every new feature to all users immediately, where we can release features incrementally, conduct AB testing and enable data programs to quickly disable problematic functionality if required. This has also reduced the deployment risk and improved the release velocity by minimising the downtime and allows our team to deliver updates more frequently with higher confidence. **Official Response from Micaela Durkin:** > Thank you for sharing this! We love that LaunchDarkly has helped your team release more safely and with greater confidence, and we also appreciate your candid input on the learning curve and flag governance at scale. To help teams ramp faster, we offer LaunchDarkly Academy for onboarding and self-guided learning, which teams find really useful as they get started! ### 33. LaunchDarkly Makes Safer, More Controlled Feature Rollouts Easy **Rating:** 5.0/5.0 stars **Reviewed by:** Yadidya P. | software Engineer, Mid-Market (51-1000 emp.) **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** Validated through Google One Tap using a business email account **Incentivized:** This reviewer was offered a nominal incentive as thanks for completing this review. **Source: Seller invite:** Invitation from a seller or affiliate. This reviewer was offered a nominal incentive as thanks for completing this review. **Reviewed Date:** May 19, 2026 **What do you like best about LaunchDarkly?** That's a fun question! I don’t have personal preferences or firsthand experiences with tools, but I can share what developers and teams commonly appreciate about LaunchDarkly. It’s widely regarded as one of the more mature, full-featured feature flag management platforms. Teams often value how it helps decouple deployments from releases: you can ship code whenever you’re ready and then use flags to control who actually sees a feature. That approach tends to make rollouts, A/B testing, and kill switches feel much safer and easier to manage. People also frequently point to the granular targeting and segmentation options, along with real-time flag evaluation and minimal latency, as standout strengths. **What do you dislike about LaunchDarkly?** I don't disTheir pricing is per-seat and scales with the number of monthly active users (MAUs) your application serves, which can add up quickly as you grow. The free tier is quite limited, and once you need features like advanced targeting, experimentation, or audit logs, you're looking at their Pro or Enterprise plans which can get costly. **What problems is LaunchDarkly solving and how is that benefiting you?** Sure! Here’s a positive take: LaunchDarkly is a game-changer for teams that want to ship with confidence. It enables gradual feature releases, so instead of a nerve-wracking big-bang launch, you get a smooth, controlled rollout where you can monitor what’s happening in real time. Teams appreciate being able to toggle features on or off instantly, experiment safely with different user segments, and move quickly without breaking things. Developers can merge code daily with less anxiety, product managers can test ideas with real users earlier, and everyone sleeps better at night knowing there’s always a fast “off switch” if something goes wrong. The UI is clean, intuitive, and well organized, so even non-technical team members can navigate it comfortably. The dashboard also provides a clear at-a-glance view of your flags, their statuses, and your environments. **Official Response from Micaela Durkin:** > Thank you for the kind words! Safer rollouts and that "off switch" peace of mind are exactly what we're built for. Really glad the platform is working well for your team! ### 34. Empowers Safe, Controlled Feature Releases **Rating:** 4.5/5.0 stars **Reviewed by:** Krishna S. | Mid-Market (51-1000 emp.) **Validated Reviewer:** Validated through a business email account **Incentivized:** This reviewer was offered a nominal incentive as thanks for completing this review. **Source: Seller invite:** Invitation from a seller or affiliate. This reviewer was offered a nominal incentive as thanks for completing this review. **Reviewed Date:** August 03, 2026 **What do you like best about LaunchDarkly?** I use LaunchDarkly to manage feature flags, which lets us release features safely without redeploying the application. I appreciate its ability to handle gradual rollouts and provide customer-specific access. What I like most is the ability to instantly enable and disable features in production without any code deployment. This makes it possible for us to deploy code to production with confidence because we can gradually roll out features to specific users or a small percentage of traffic and instantly disable a feature if an issue occurs. This reduces release risk significantly and makes production deployments much safer. It's very easy to integrate, which is another plus. **What do you dislike about LaunchDarkly?** I feel a reminder feature which we can set up for cleaning the feature flag is needed. We add so many feature flags to LaunchDarkly, and we plan to clean the old feature flag after some time. So a reminder feature would help after these many days, we will remove the flag. **What problems is LaunchDarkly solving and how is that benefiting you?** I use LaunchDarkly to safely release, test, and instantly disable features in production without redeploying. It allows gradual rollouts and quick rollbacks, reducing deployment risk and giving better control over feature releases, making production deployments safer. **Official Response from Micaela Durkin:** > Thank you so much for sharing! It's great to hear LaunchDarkly is helping your team ship with more confidence and reduce risk. On the flag cleanup reminder, we actually do have some options for this today, like Slack notifications when a flag becomes ready to remove, a stale flags dashboard for reviewing and sorting by age, and Vega, our AI agent that can automate the cleanup PR itself, definitely worth checking out if this is a priority for your team! ### 35. Effortless Feature Flag Management with Minor Downtime Issues **Rating:** 4.5/5.0 stars **Reviewed by:** Adam S. | Backend Team Lead, Small-Business (50 or fewer emp.) **Validated Reviewer:** Validated through a business email account **Incentivized:** This reviewer was offered a nominal incentive as thanks for completing this review. **Source: Seller invite:** Invitation from a seller or affiliate. This reviewer was offered a nominal incentive as thanks for completing this review. **Reviewed Date:** August 04, 2026 **What do you like best about LaunchDarkly?** I appreciate the ease of variation configuration in LaunchDarkly, which allows me to use a lot of data from the invocation point to decide on the variation. This makes it easy to test or guard specific logic changes in the code depending on the service, client, or percentage. I find it valuable for gradual rollouts and implementing kill switches without the need for code deployment, as well as testing different approaches without constantly having to change the code. **What do you dislike about LaunchDarkly?** We recently had a downtime and it was not very clear when it ended. It also didn't start working without resetting the services. Although it was communicated, we would like a constant push for as high uptime as possible. **What problems is LaunchDarkly solving and how is that benefiting you?** I use LaunchDarkly for feature flags, allowing gradual rollouts and testing different approaches without redeploying code. It offers kill switches and client-based variability, making it easy to test or safeguard logic changes. **Official Response from Micaela Durkin:** > Thank you so much for the kind words on variation configuration, gradual rollouts, and kill switches! We're glad those are helping you test and guard logic changes without redeploys! We're very sorry the recent downtime wasn't clearly communicated with you when it ended and required a service reset to recover. We take uptime very seriously, and are continuing to invest in clearer incident communication and faster recovery. You can always refer to our status page as well as our resilient architecture guide, which covers configuration patterns that help SDKs recover more gracefully during any connectivity disruptions. ### 36. Powerful Feature Flagging for Safe, Incremental OTT Rollouts **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Computer Software | Mid-Market (51-1000 emp.) This reviewer's identity has been verified by our review moderation team. They have asked not to show their name, job title, or picture. **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** Validated through a business email account **Incentivized:** This reviewer was offered a nominal gift card as thank you for completing this review. **Source: G2 invite:** Invitation from G2. This reviewer was offered a nominal gift card as thank you for completing this review. **Reviewed Date:** August 09, 2026 **What do you like best about LaunchDarkly?** What stands out most is its powerful feature flagging that lets us roll out new OTT platform features incrementally without risking full deployments. The granular audience targeting allows us to seamlessly run beta tests across specific viewer segments and instantly kill switches if performance drops. **What do you dislike about LaunchDarkly?** Managing a high volume of feature flags can get cluttered fast, and without strict team protocols, stale flags accumulate and add technical debt to the codebase. Additionally, the tier based pricing can get steep as active user contexts and subscriber event counts scale up across our OTT platforms. **What problems is LaunchDarkly solving and how is that benefiting you?** Launch darkly solves the high risk of platform downtime and broken user experiences by decoupling code deployments from feature releases. For our OTT platform, it allows us to safely test new video player features and UI updates with small viewer cohorts first, ensuring zero disruption to live streaming during major feature rollouts. **Official Response from Micaela Durkin:** > Thank you so much for sharing such detailed feedback, especially on how feature flagging and audience targeting have made incremental rollouts and beta testing safer for your OTT platform during live streaming! We hear you on flag management at scale, I've shared a link to our best practices below on flag debt. ### 37. Effortless Controlled Rollouts with Flexible Feature Flags **Rating:** 5.0/5.0 stars **Reviewed by:** Jay L. | Senior Software Engineer, Mid-Market (51-1000 emp.) **Validated Reviewer:** Validated through LinkedIn **Incentivized:** This reviewer was offered a nominal incentive as thanks for completing this review. **Source: Seller invite:** Invitation from a seller or affiliate. This reviewer was offered a nominal incentive as thanks for completing this review. **Reviewed Date:** August 04, 2026 **What do you like best about LaunchDarkly?** What I like best is how easy it is to do controlled rollouts without shipping separate builds. Being able to target by environment/tenant, gate risky changes behind flags, and then cleanly turn features on (or keep them off) in production/dev environments. **What do you dislike about LaunchDarkly?** I have to set up a full rule, but I’d like to keep it simple. I want to be able to choose orgs from a dropdown and disable the flags. **What problems is LaunchDarkly solving and how is that benefiting you?** LaunchDarkly helps us separate deployment from release. We can ship code, validate it in lower environments, and then gradually enable it by tenant or environment without needing another deploy. This reduces the blast radius for risky changes, makes rollbacks as simple as flipping a flag, and lets us run experiments or phased rollouts without maintaining long-lived branches. For us, that translates into faster delivery with more confidence, and fewer emergency hotfixes when something misbehaves in production. **Official Response from Micaela Durkin:** > Thank you for the thoughtful review! We're glad LaunchDarkly is helping your team separate deployment from release and reduce risk in production! For org-level toggling without building a full rule, our individual targeting feature lets you search and select a context (like an org) directly and set its variation, please let us know if this is helpful! ### 38. Detailed Feature Flag Rules and a Clear UX Across Environments **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Computer Software | Enterprise (> 1000 emp.) This reviewer's identity has been verified by our review moderation team. They have asked not to show their name, job title, or picture. **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** Validated through a business email account **Incentivized:** This reviewer was offered a nominal incentive as thanks for completing this review. **Source: Seller invite:** Invitation from a seller or affiliate. This reviewer was offered a nominal incentive as thanks for completing this review. **Reviewed Date:** July 27, 2026 **What do you like best about LaunchDarkly?** We used to reinvent the wheel at my previous company by building our own system to handle feature flags. There was really no reason to do that—just use LD instead. What I especially like is how detailed you can get when defining the rules that the flags are evaluated against. It is also wonderful to have different environment where you can define your flags (prod VS non-prod environemnt), and the easy-to-understand UX allows you to easily accomplish your task **What do you dislike about LaunchDarkly?** in my perosnal opinion, the biggest drawback is about the complexity that comes when we need to manage a large number of feature flags. Without good processes, we can have a growing number of stale flags that can accumulate, with increased maintenance overhead **What problems is LaunchDarkly solving and how is that benefiting you?** Our main use case is to define new flags so we can control a feature that’s still under development, and make sure customers only see it once it’s fully completed. Another use case is for features that should be available only to a subset of customers; with LD, we can easily control which customers the feature is available to. **Official Response from Micaela Durkin:** > Thank you so much for such a thoughtful review. We love to hear how much detail and flexibility you're able to get with rule targeting, and how the environment setup and overall UX have made it easier to manage your rollout process compared to building something in house. You raise a fair point about the overhead that comes with managing a large volume of flags. We have some guidance on flag health and cleanup that your team might find useful which I've shared below: ### 39. Rock-Solid Reliability for Feature Rollouts and Instant Flag Updates **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Mid-Market (51-1000 emp.) This reviewer's identity has been verified by our review moderation team. They have asked not to show their name, job title, or picture. **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** Validated through a business email account **Incentivized:** This reviewer was offered a nominal incentive as thanks for completing this review. **Source: Seller invite:** Invitation from a seller or affiliate. This reviewer was offered a nominal incentive as thanks for completing this review. **Reviewed Date:** August 26, 2026 **What do you like best about LaunchDarkly?** It's reliable! We depend heavily on LD for feature rollouts, operational toggles, split testing, etc., across multiple apps, and I've never had to think twice about whether I can count on the system to work. In terms of LD's specific features, I love its DD integration, its flag history, its SSE approach so client changes propagate instantly, and session replay for investigating user bug reports. **What do you dislike about LaunchDarkly?** I haven't been a huge fan of the UI updates in the past year or two. The configurable tag/bubble-looking presentation for selecting which environments are shown atop the flag page is particularly unintuitive. **What problems is LaunchDarkly solving and how is that benefiting you?** Feature rollouts are pretty much frictionless, and we can target the rollouts by so many different attributes. We build entire GTM strategies around this capability. Secondarily, features like session replay are helping us during incident investigations. **Official Response from Micaela Durkin:** > Thank you for the detailed feedback! It's great to hear the Datadog integration, flag history, SSE propagation, and session replay are all pulling their weight, especially during incident investigations. We also appreciate your feedback on the environment selector UI, and we'll pass that along to our product team as we keep refining the experience. ### 40. LaunchDarkly Streamlines Feature Releases. **Rating:** 4.5/5.0 stars **Reviewed by:** Sagar L. | Team Specialist, Enterprise (> 1000 emp.) **Validated Reviewer:** Validated through LinkedIn **Incentivized:** This reviewer was offered a nominal gift card as thank you for completing this review. **Source: G2 invite:** Invitation from G2. This reviewer was offered a nominal gift card as thank you for completing this review. **Reviewed Date:** September 01, 2026 **What do you like best about LaunchDarkly?** I really appreciate how LaunchDarkly gives our teams control when we release features. Instead of simply switching a change on for every user at once, we have the option to gradually roll out features to specific test groups or instantly disable them completely if something goes wrong. Feature flags have greatly simplified communication between our developer, support, and operations teams. **What do you dislike about LaunchDarkly?** Feature flags can quickly become unmanageable when multiple teams create them without a naming convention or a strategy for removing them. **What problems is LaunchDarkly solving and how is that benefiting you?** LaunchDarkly reduces release risk by decoupling code deployment from feature releases, allowing you to show new features to select users and respond quickly if a feature needs to be rolled back. Streamline your release process, minimize disruptions for your users, and provide your support team with greater visibility during releases. **Official Response from Micaela Durkin:** > Thank you for sharing! We're glad the gradual rollout and instant rollback controls have given your team confidence in the release process and improved communication across development, support, and operations. Flag hygiene as usage scales is a common challenge, and we appreciate you flagging it as an area where more guidance around naming conventions and cleanup would help. Here is one of our guides with best practices for flag debt. ### 41. Game-Changer for Safe Rollouts and Stress-Free Releases **Rating:** 4.0/5.0 stars **Reviewed by:** Gauri S. | Analyst, Enterprise (> 1000 emp.) **Validated Reviewer:** Validated through LinkedIn **Incentivized:** This reviewer was offered a nominal gift card as thank you for completing this review. **Source: G2 invite:** Invitation from G2. This reviewer was offered a nominal gift card as thank you for completing this review. **Reviewed Date:** June 28, 2026 At G2, we prefer fresh reviews and we like to follow up with reviewers. They may not have updated their review text, but have updated their review. **What do you like best about LaunchDarkly?** The best part is the ability to toggle features in production without a full redeploy—it’s an absolute game-changer. Being able to run safe, targeted rollouts, or instantly “kill” a buggy feature without sweating through a hotfix, has taken a huge amount of stress out of our release cycles. What used to feel like high-risk deployments now becomes a non-event. Bottom line: if you want to ship faster with real peace of mind, this is an essential tool. The level of control over user targeting, plus the audit logs, makes it worth the investment on its own. **What do you dislike about LaunchDarkly?** The main downsides to LaunchDarkly are its high price point, which scales rapidly as your team grows, and the significant learning curve involved in mastering its complex configuration. Additionally, it requires strict internal discipline to manage "flag debt"—if your team doesn't proactively clean up retired flags, your codebase can quickly become cluttered, eventually turning a powerful tool into a source of technical maintenance and operational noise. **What problems is LaunchDarkly solving and how is that benefiting you?** LaunchDarkly solves the "deployment risk" problem by decoupling code releases from feature activation. It benefits me by allowing for instant kill-switches for bugs, targeted rollouts to specific user segments, and the ability to test in production, which eliminates the stress of "all-or-nothing" releases and significantly accelerates development velocity. **Official Response from Micaela Durkin:** > Thank you for leaving such a thoughtful review! We’re so glad LaunchDarkly has helped your team reduce deployment risk with targeted rollouts, instant kill switches, and more peace of mind in production. We also appreciate the candid feedback on flag debt, and we’ve shared our docs below with best practices for improving flag hygiene. ### 42. Streamlined Deployments with Feature Flags and Staged Rollouts **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Small-Business (50 or fewer emp.) This reviewer's identity has been verified by our review moderation team. They have asked not to show their name, job title, or picture. **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** Validated through LinkedIn **Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate. **Reviewed Date:** August 20, 2026 **What do you like best about LaunchDarkly?** One of the biggest improvements to my workflow is the ability to separate deployment from release, easily create and maintain feature flags, and do a staged rollout. **What do you dislike about LaunchDarkly?** The main downside is that LaunchDarkly can feel a little complex, especially when you're managing a large number of feature flags across multiple environments. It also requires discipline to clean up old or unused flags; otherwise, they can accumulate and make it harder to understand which flags are still relevant. **What problems is LaunchDarkly solving and how is that benefiting you?** LD benefits us by reducing deployment risk and giving the team more control over production releases. If something goes wrong, we can quickly disable a feature without rolling back the entire application. It also allows us to test features with specific users or groups before making them available to everyone, which gives us more confidence when shipping changes. **Official Response from Micaela Durkin:** > Thanks for sharing how separating deploy from release and staged rollouts have given your team more control and confidence when shipping changes! On the flag cleanup point, I'd love to introduce you to Vega, our new AI-powered cleanup agent, which can help identify and remove stale flags automatically so they're easier to manage across environments. ### 43. Peace of Mind for Confident Feature Releases with LaunchDarkly **Rating:** 4.0/5.0 stars **Reviewed by:** Jay K. | Software Developer, Mid-Market (51-1000 emp.) **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** Validated through a business email account **Incentivized:** This reviewer was offered a nominal incentive as thanks for completing this review. **Source: Seller invite:** Invitation from a seller or affiliate. This reviewer was offered a nominal incentive as thanks for completing this review. **Reviewed Date:** May 15, 2026 **What do you like best about LaunchDarkly?** We use LaunchDarkly to more confidently release new features. By feature flagging new features/logic, we can enable features for a subset of users/accounts before a full release; this gives us the confidence that 1. features can we rolled back at the flip of a switch if any issues arise and 2. that features have been tested in a production environment before making them visible to all users. LaunchDarkly's UX is simple and allows us to quickly enable features for specific users/accounts and easily track how the feature flags have been evaluating in a given environment. LaunchDarkly gives us peace of mind every time we release a new feature. **What do you dislike about LaunchDarkly?** AI features feel like an afterthought and somewhat unnecessary. **What problems is LaunchDarkly solving and how is that benefiting you?** Controlled rollout of new features, giving us peace of mind that we can instantly rollback anything broken and fully test new features before they're enabled for all users. **Official Response from Micaela Durkin:** > Thank you for taking the time to share your thoughts and feedback! Peace of mind at every release is exactly what we're here for, so this really means a lot. On the AI front, we hear you, and we think you'll be excited about what we have coming very soon. Stay tuned! ### 44. Centralized Feature Management with easy Rollouts and Rollbacks **Rating:** 5.0/5.0 stars **Reviewed by:** Dwitesh S. | Custom Software Engineering Specialist, Enterprise (> 1000 emp.) **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** Validated through a business email account **Incentivized:** This reviewer was offered a nominal gift card as thank you for completing this review. **Source: G2 invite:** Invitation from G2. This reviewer was offered a nominal gift card as thank you for completing this review. **Reviewed Date:** July 08, 2026 **What do you like best about LaunchDarkly?** LaunchDarkly provided centralised feature management. It also decouples code deployment from feature release. This enables rolling out new features through canary launches and also rolling back buggy features without an extra deployment. **What do you dislike about LaunchDarkly?** To be honest, there aren't a lot of cons when it comes to LaunchDarkly. Probably, cost can be a factor for small-scale teams. Also, technical debt (i.e., ownership of flags) in large-scale teams can be problematic but this can be made easier through careful planning **What problems is LaunchDarkly solving and how is that benefiting you?** The most important benefit we have observed so far is ease of high-risk feature releases coupled with quick rollbacks (if necessary). Delivery cycle is made smoother through the canary launch strategy. Production versions are stable and downtime can be minimised **Official Response from Micaela Durkin:** > Thank you for the great review! We love to hear that LaunchDarkly's decoupling of deployment from release has made canary launches and instant rollbacks such a smooth part of your delivery cycle, with the stability and reduced downtime to show for it. Thanks for sharing your experience! ### 45. Feature Flags That Boost Release Velocity and Enable Confident Rollouts **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Enterprise (> 1000 emp.) This reviewer's identity has been verified by our review moderation team. They have asked not to show their name, job title, or picture. **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** Validated through LinkedIn **Incentivized:** This reviewer was offered a nominal incentive as thanks for completing this review. **Source: Seller invite:** Invitation from a seller or affiliate. This reviewer was offered a nominal incentive as thanks for completing this review. **Reviewed Date:** July 16, 2026 **What do you like best about LaunchDarkly?** The feature flag capabilities have been incredibly valuable for our team. They solve a wide range of business use cases by allowing us to control feature rollouts with precision, without requiring new deployments for every change. This has significantly improved our release velocity, enabling us to ship code more frequently while minimizing risk. One of the biggest advantages is the ability to gradually roll out new features to specific user segments, perform A/B testing, and quickly disable problematic features if issues arise in production. This has given our team much greater confidence in releasing changes and experimenting with new ideas. Overall, feature flags have streamlined our development and deployment workflow, reduced operational risk, and made it much easier to validate new features with real users before a full-scale rollout. They have become an essential part of our release strategy, helping us deliver value to customers faster while maintaining stability and reliability. **What do you dislike about LaunchDarkly?** Sometimes the support is not great especially during the times when the platform is down and offlate we are seeing a lot of cases where our company are seeing unreliable results **What problems is LaunchDarkly solving and how is that benefiting you?** LaunchDarkly has solved several challenges that we previously faced around feature releases, testing, and risk management. Before adopting feature flags, releasing new functionality often meant coupling deployments directly with feature launches, making it difficult to test changes in production or quickly respond if something went wrong. With LaunchDarkly, we can decouple deployments from feature releases, giving us much greater control over how and when new functionality is exposed to users. We can gradually roll out features to specific customer segments, perform A/B testing, validate new functionality with a limited audience, and instantly disable or roll back a feature without requiring a new deployment. This has significantly reduced the operational risk associated with releases. The platform has also increased our development and release velocity. Our engineering teams can merge and deploy code more frequently without waiting for a coordinated product launch, while product and business teams have the flexibility to control feature availability independently. This has streamlined collaboration across teams and shortened the time it takes to deliver value to customers. Overall, LaunchDarkly has become a key part of our release strategy. It has improved the reliability of our deployments, enabled faster experimentation and data-driven decision-making, reduced the impact of potential production issues, and allowed us to deliver new features to customers with greater confidence and agility. **Official Response from Micaela Durkin:** > Thank you for sharing such a detailed and thoughtful review. It's nice to hear how much of an impact decoupling deployments from releases has had on your team's speed and confidence, especially with gradual rollouts and A/B testing becoming core parts of your release strategy. We also hear you on the support experience and we take that seriously. We'd like to connect to understand what happened and make sure it gets addressed, so please reach out to me (mdurkin@launchdarkly.com) or our support channel so we can better help! ### 46. Flexible, Reliable Feature Flags for Confident Anytime Releases **Rating:** 4.0/5.0 stars **Reviewed by:** Anish M. | Member Of Technical Staff - Software Development (AI), Enterprise (> 1000 emp.) **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** Validated through LinkedIn **Incentivized:** This reviewer was offered a nominal gift card as thank you for completing this review. **Source: G2 invite:** Invitation from G2. This reviewer was offered a nominal gift card as thank you for completing this review. **Reviewed Date:** April 28, 2026 At G2, we prefer fresh reviews and we like to follow up with reviewers. They may not have updated their review text, but have updated their review. **What do you like best about LaunchDarkly?** The biggest advantage of LaunchDarkly is the way wherein it's ability to separate deployment and release in a real prod environment. We use it in our stack (Node.js backend + React frontend in most cases) to control feature rollouts without redeploys. We can turn on features for internal users first, then for certain customers all e and finally roll out in percentage based releases. This has made biweekly releases a lot safer, especially for high impact changes. The integration of the SDK was simple and once implemented it became a core part of our release workflow. It also gives product and QA teams control over feature exposure without relying on engineering, which increases overall velocity. **What do you dislike about LaunchDarkly?** Feature flag management can become or becomes a problem if not managed as per best practices. In our case, stale flags started piling up after multiple releases, and without strict cleanup which we have every quarter helps us fix this Pricing is another concern, it scales quickly as usage grows. During renewal, we didn’t receive the same level of discount that was initially discussed during onboarding, which made cost planning a bit more harder. **What problems is LaunchDarkly solving and how is that benefiting you?** In reality, when we ship a feature, we start it with a disabled feature flag. First, we activate it for our beta users or certain customers through the means of domain targeting, then slowly roll it out to others users periodically all users in production. We are also dependent on feature flags as kill switches. For instance, in the case where we observe any latency or error issues due to some downstream API or new business logic that we have introduced, we do not need to apply a hotfix but just disable the flag through the dashboard. We also use segmentation rules (user attributes, environments) to test features with specific cohorts before a full rollout **Official Response from Micaela Durkin:** > Thank you for sharing how LaunchDarkly fits into your Node.js and React workflow! We’re so glad to hear that controlled rollouts, kill switches, and separating deployment from release have made your releases safer and more efficient while empowering your product and QA teams. We also appreciate your note on flag management and agree that consistent cleanup is the key to maintaining a healthy system over time. ### 47. Highly Controllable Progressive Delivery for Precise Rollouts and Experiments **Rating:** 5.0/5.0 stars **Reviewed by:** Nirmal K. | Manager, E-Learning, Small-Business (50 or fewer emp.) **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** Validated through LinkedIn **Incentivized:** This reviewer was offered a nominal gift card as thank you for completing this review. **Source: G2 invite:** Invitation from G2. This reviewer was offered a nominal gift card as thank you for completing this review. **G2 Icon:** Our network of Icons are G2 members who are recognized for their outstanding contributions and commitment to helping others through their expertise. **Reviewed Date:** August 11, 2026 **What do you like best about LaunchDarkly?** It excels at progressive delivery. You can easily roll out a new feature to exactly 5% of your users, exclusively to your internal QA team, or specifically to beta testers in a certain geography, making A/B testing and canary releases highly controllable. **What do you dislike about LaunchDarkly?** While creating a simple "on/off" switch is very intuitive, setting up complex rule-based targeting, utilizing the newer "contexts" model, and running statistically significant experiments involves a steep learning curve. **What problems is LaunchDarkly solving and how is that benefiting you?** LaunchDarkly has recently expanded into AI configs, allowing teams to use feature flags to route traffic between different LLMs, A/B test AI prompts, and monitor AI feature rollouts. **Official Response from Micaela Durkin:** > Thank you for sharing how you're using progressive delivery to control rollouts down to specific user segments and geographies, it's great to hear that level of precision is making releases and A/B testing so manageable. We hear you on the learning curve with contexts and rule-based targeting, and we'd encourage you to check out LaunchDarkly Academy, it has some great resources for getting more comfortable with those advanced features. ### 48. Effortless Feature Rollouts with LaunchDarkly **Rating:** 4.5/5.0 stars **Reviewed by:** Dheeraj V. | Mid-Market (51-1000 emp.) **Validated Reviewer:** Validated through Google using a business email account **Incentivized:** This reviewer was offered a nominal incentive as thanks for completing this review. **Source: Seller invite:** Invitation from a seller or affiliate. This reviewer was offered a nominal incentive as thanks for completing this review. **Reviewed Date:** July 14, 2026 **What do you like best about LaunchDarkly?** I use LaunchDarkly for safeguarding new features and cohort-based rollouts. It makes rolling out features super easy, and I appreciate that the UI is very clean and user-friendly. The bulk updates via JSON make it much more customizable, and I don't have to manage environments in helm files or local files, which would later require code merges and deployments. LaunchDarkly provides a make checker flow that makes it easy for me to add my counterparts in the loop when releasing features for a new cohort. The other person can approve and apply the changes I raised for review. It was really easy and quick to set up too. I definitely find it way better than the Harness feature flag service. **What do you dislike about LaunchDarkly?** One thing I think can be improved is the UI placement for adding a new rule. It does take some time to understand how to add a new rule. I think if an AI agent were there to create rules or update the flags, it would be the best, as I could pair up with an LD agent to create the rules and send them to me for approval. Makes life a whole lot easier. **What problems is LaunchDarkly solving and how is that benefiting you?** I use LaunchDarkly for safeguarding new features and cohort-based rollouts. It makes feature management simple, with an easy UI and customizable bulk updates. I avoid managing environments in helm or local files. Approvals and changes are streamlined, improving feature release coordination. **Official Response from Micaela Durkin:** > Thank you for the detailed rundown! It's great to hear cohort based rollouts, bulk JSON updates, and the approval workflows have made release coordination so much smoother, and that it's outperforming Harness for your team. We do have an AI agent called Vega in the product today, though right now it's focused on flag cleanup rather than rule creation, and I'll be sure to share your feedback on extending that to rule building with our product team. ### 49. LaunchDarkly: Reliable Yet Needs Better API Management **Rating:** 3.5/5.0 stars **Reviewed by:** Verified User in Computer Software | Mid-Market (51-1000 emp.) This reviewer's identity has been verified by our review moderation team. They have asked not to show their name, job title, or picture. **Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user. **Validated Reviewer:** Validated through a business email account **Incentivized:** This reviewer was offered a nominal incentive as thanks for completing this review. **Source: G2 invite on behalf of seller:** Invitation from G2 on behalf of a seller or affiliate. This reviewer was offered a nominal incentive as thanks for completing this review. **Reviewed Date:** April 29, 2024 At G2, we prefer fresh reviews and we like to follow up with reviewers. They may not have updated their review text, but have updated their review. **What do you like best about LaunchDarkly?** I like most about LaunchDarkly is how instant it is. It's pretty highly reliable, and even though we just had an issue yesterday, it's the first we've had this year so far. When we make a change to a feature flag, it gets updated on our back end or for whatever service is consuming it very quickly. For the most part, we don't have to worry about if the flag change got applied because there's a nice UI that shows how many flag evaluations and their results have happened. It's a good way of knowing if our flag is being hit correctly. There's even something about detecting when a flag is stale, like an auto detector of stale flags, which I think is pretty cool, and we're thinking of using it. Additionally, if you add some hook to your CI, LaunchDarkly can tell you where flag evaluations are happening inside your repo, which helps us evaluate whether a flag is stale or not. This is useful for us as it helps make LaunchDarkly faster to start up and more reliable since it doesn't have to pull so much data. **What do you dislike about LaunchDarkly?** I think the security aspect is okay-ish, but I don't like how we can only have one SDK key per project. I really don't like that. That means we have one API key for the whole company for our environment. We can't really have every team with their own API key, scoped to only read certain flags. It's just one huge shared environment, and I think that's not how it should be implemented. We should have more access control on reading these flags, especially because people tend to put configuration data on LaunchDarkly. **What problems is LaunchDarkly solving and how is that benefiting you?** LaunchDarkly solves config management and feature deployment, letting us enable features for specific customers or clusters. It allows on-the-fly configurations without redeployments, and everything updates instantly, making our processes smooth and reliable. **Official Response from Micaela Durkin:** > Thank you for taking the time to share such detailed feedback with us. It's great to know the speed and reliability of flag evaluations have held up well for you, and that the stale flag detection and CI integration are proving useful for keeping things lean. We also appreciate you flagging the SDK key and access control setup. And I have great news, we now support multiple SDK keys per environment, which lets you isolate access across teams and set expiration dates for key rotation. It's available on our Enterprise plan tier. That said, I hear you that it's not quite the same as fine-grained, per-flag read scoping, and that kind of detail helps us understand how teams are actually using LaunchDarkly day to day and where we can improve. I'll be sure to share this with our product team. ### 50. Feature-Rich, Reliable, and Developer-Friendly **Rating:** 4.5/5.0 stars **Reviewed by:** William C. | OSS Contributor, Enterprise (> 1000 emp.) **Validated Reviewer:** Validated through LinkedIn **Incentivized:** This reviewer was offered a nominal incentive as thanks for completing this review. **Source: Seller invite:** Invitation from a seller or affiliate. This reviewer was offered a nominal incentive as thanks for completing this review. **Reviewed Date:** July 09, 2026 **What do you like best about LaunchDarkly?** I really appreciate LaunchDarkly's good design and developer experience. It's easy to find things and there's limited friction, which makes it well thought out. The interfaces for customization are good too. I mainly use it to ship software fast with quick rollbacks and to control runtime configs, and it handles feature-rich flag management really well with its rules and very good access controls. I find the flag evaluation metrics crucial for safe offboarding, and the guarded releases feature is pretty cool. The access controls at the resource level are amazing, and the initial setup was very easy, thanks to their minimal SDK. **What do you dislike about LaunchDarkly?** I wish LaunchDarkly had some state persistence managed by them. Having to construct complex user contexts is hard to do and requires a lot of engineering effort. Would love to leverage LaunchDarkly's infrastructure more for that. **What problems is LaunchDarkly solving and how is that benefiting you?** I use LaunchDarkly to ship software fast with quick rollbacks, control runtime configs, and manage feature flags with rules and metrics. It offers great access controls and auto rollbacks, making releases safer and allowing reliable targeting and flag metrics. ## LaunchDarkly Discussions - [What is LaunchDarkly used for?](https://www.g2.com/discussions/what-is-launchdarkly-used-for) - 1 comment - [How do I use LaunchDarkly?](https://www.g2.com/discussions/how-do-i-use-launchdarkly) - 1 comment - [View LaunchDarkly pricing details and edition comparison](https://www.g2.com/products/launchdarkly/reviews?section=pricing&secure%5Bexpires_at%5D=2026-09-02+02%3A52%3A19+-0500&secure%5Bsession_id%5D=2e01793c-febd-44ab-94b3-7fa6bd809300&secure%5Btoken%5D=edd78d531020276aec9e4284fdb7b558cdae04a1282bb1acb4c75d5c61b7d1be&format=llm_user) ## LaunchDarkly Features **Additional Functionality** - Tagging - Natural Language Processing - Data Extraction - Multi-Language - Predictive Analytics - Drag & Drop - Speech Recognition - Reporting/Analytics - Data Storage Management - Virtual Personal Assistant (VPA) - AI Copilot - Customer Segmentation - Collaboration Tools - Data Import/Export - Generative AI - For eCommerce - Role-Based Permissions - Customizable Branding - Search/Filter - Monitoring - Document Management - API - Data Visualization - Trend Analysis - Machine Learning - Access Controls/Permissions - Alerts/Escalation - Performance Metrics - Real-Time Data - Third-Party Integrations - Mobile App - Multiple Data Sources - For Sales Teams/Organizations - Sentiment Analysis - Activity Dashboard - Chatbot - Workflow Automation **Additional Functionality** - Code Generation - Text to Image - Generative AI - API - Natural Language Processing - Virtual Characters and Avatars - Content Generation - Personalization and Recommendation - Conditional Generation - Transformer Model - Automated Image & Video Editing - Interactive and Co-Creative Systems - Text Summarization - Data Augmentation - Variation Autoencoder Models - Adversarial Training - Transfer Learning and Fine-tuning - Simulation and Scenario Generation - Creative Design - AI Copilot - Prompt Engineering - Foundation Model **User Identification** - Demographics - User Segmentation - Geolocation - Predictive Analytics **User Behavior** - Click Tracking - Mouse Movement - Frustration Tracking **Product Analytics** - Account-Level Analytics - User-Level Analytics - Segmentation - Funnels - Multi-Product Analytics - Integrations - Usage Tracking/Analytics **Functionality** - Deployment-Ready Staging - Integration - Extensible **Bug Reporting** - User Reports & Feedback - Tester Reports & Feedback - Team Reports & Comments **Visibility** - Dashboards and Visualizations - Alerts and Notifications - Reporting **Management** - Flag Management - Rollout & Rollback Control - Monitoring **Monitoring** - Performance Baselines - Performance Analysis - Transaction Monitoring - AI/ML Assistance - Multi-System Monitoring - Generative AI - Container Monitoring **Computing** - Generative AI **Prompt Engineering - Large Language Model Operationalization (LLMOps) ** - Prompt Optimization Tools **Telemetry Collection & Ingestion - Observability** - Multi-Telemetry Ingestion - OpenTelemetry Support **Prompt Management - Prompt Management Tools** - Change tracking - Prompt Behaviour Feedback **Workflow Design & Integration - AI Orchestration** - Dependency Management - Workflow Coordination - Multi-Provider API Connectivity - Multi-Step Workflow Creation - Enterprise System Integration - Real-Time Data Pipelines **Agentic AI - Observability Software** - Autonomous Task Execution - Multi-step Planning - Cross-system Integration - Adaptive Learning - Natural Language Interaction - Proactive Assistance - Decision Making - AI/Machine Learning - Third-Party Integrations **Tracking & Reporting** - Custom Event Tracking - Real-Time Insights - Attribution - Activity Dashboard - User Path Tracking - User Activity History - Multi-Channel Attribution - In-App Events Tracking **A/B Testing ** - Error and Bug Tracking - Split URL Testing - Data Analysis - Notes **Management** - Processes and Workflow - Reporting - Automation **Bug Monitoring** - Bug History - Data Retention **Monitoring and Management** - Automation - Performance Baseline - Real-Time Monitoring **Functionality** - Multi-Environment Control - Feature Testing - Low-Code Interface **Response** - Dashboards and Visualization - Incident Alerting - Root Cause Analysis (RCA) - Trend Analysis - Data Visualization **Experimental Design** - Multivariate testing capacities - Split Testing - Mobile Testing - AI Assisted Testing - AI Generated Variations - Multivariate Testing **Model Garden - Large Language Model Operationalization (LLMOps)** - Model Comparison Dashboard **Visualization & Dashboards - Observability** - Unified Dashboard - Trace Visualization - Activity Dashboard **Agentic AI - Product Analytics** - Cross-system Integration - Adaptive Learning - Machine Learning **Performance Analytics - Prompt Management Tools** - Lower Latency - Token Usage - Cost Control **Performance Optimization & Analytics - AI Orchestration** - Workflow Performance Dashboards - Workflow Reporting - Resource Utilization Monitoring - Computational Resource Management - Dynamic Scaling - Component Monitoring **Metrics** - Engagement - Retention - Return - Conversions - Engagement Tracking - Uninstall Tracking - Conversion Tracking - Location Tracking - ROI Tracking - Retention Tracking - Visitor Tracking - Behavior Tracking - Revenue Tracking **Visitor Information** - User Identification - Search Box **Analytics** - Reporting and Analytics - Visual Analytics **Correlation & Root Cause Analysis - Observability** - Cross-Telemetry Correlation - Root Cause Detection - Intelligent Alerting **Agentic AI - Bug Tracking** - Adaptive Learning - Natural Language Interaction - Proactive Assistance - Assignment Management - Prioritization **Agentic AI - Continuous Delivery** - Autonomous Task Execution - Cross-system Integration - Adaptive Learning - Natural Language Interaction - Proactive Assistance **Model Benchmarking and Comparison - Prompt Management Tools** - Strategic Model Selection **Governance & Compliance Controls - AI Orchestration** - Regulatory Compliance - Governance Policy Enforcement - Role-Based Access Control - Audit Trail Management - Security Protocols **Agentic AI - Application Performance Monitoring (APM)** - Autonomous Task Execution - Adaptive Learning - Proactive Assistance - Decision Making - Third-Party Integrations **Agentic AI - Log Monitoring** - Natural Language Interaction **Behavioral Analytics - Product Analytics** - Multi-Product Analytics - User level Analytics - Account level Analytics - Segmentation - Funnels **Additional Functionality** - API - Audit Trail - Drag & Drop - Projections - Charting - Ticket Management - Monitoring - Status Tracking - Progress Tracking - Workflow Management - Project Time Tracking - Issue Tracking - Configurable Workflow - Collaboration Tools - Agile Methodologies - Customizable Fields - Backlog Management - Real-Time Updates - Single Sign On - Generative AI - Task Scheduling - Activity Tracking - Activity Dashboard - Task Management - Project Management - Project Planning - Feedback Management - Code Repository Integration - Reporting & Statistics - Email Management - Knowledge Base Management - Multiple Projects - Tagging - AI Copilot - File Management - Issue Management - Task Planning - Data Visualization - Bug/Issue Capture - Bug Tracking - Alerts/Notifications - Commenting/Notes - @mentions - Third-Party Integrations - Customizable Templates - Task Progress Tracking - Real-Time Notifications - Access Controls/Permissions **Additional Functionality** - Alerts/Notifications - Surveys & Feedback - Mobile Access - Customizable Templates - Workflow Management - Customizable Reports - Visual Editor - Conversion Rate Optimization - Access Controls/Permissions - Campaign Segmentation - Widgets - Activity Dashboard - Funnel Analysis - Drag & Drop - API - Content Management - Behavior Tracking - Landing Pages/Web Forms - Engagement Tracking - Geotargeting - AI Copilot - Monitoring - Conversion Tracking - Customizable Branding - Real-Time Data - Assessment Management - Search/Filter - Data Visualization - Statistical Analysis **Additional Functionality** - Monitoring - Push Notifications - Access Controls/Permissions - Campaign Management - Data Modeling - Funnel Analysis - For Marketers - Single Sign On - Workflow Management - Customer Experience Management - Trend Analysis - Mobile Access - Third-Party Integrations - Alerts/Escalation - Data Import/Export - Collaboration Tools - Session Recording - Data Visualization - Root Cause Analysis - Drag & Drop - Performance Metrics - Generative AI - Cohort Analysis - Issue Management - Compliance Management - Heatmaps - Customizable Branding - Search/Filter - AI Copilot - Event Triggered Actions - API - Reporting/Analytics - A/B Testing **Application Development - Large Language Model Operationalization (LLMOps) ** - SDK & API Integrations **Scalability & Ecosystem Integration - Observability** - Kubernetes Monitoring - Hybrid/Multi-Cloud Support - Real-Time Monitoring - Network Monitoring - Container Monitoring - Activity Monitoring **Agentic AI - Session Replay** - Cross-system Integration **Agentic AI - A/B Testing** - Autonomous Task Execution - Cross-system Integration - Adaptive Learning - Proactive Assistance - Audience Targeting - Third-Party Integrations **Production-ready Deployment Tools - Prompt Management Tools** - CI/CD Integration **Platform Infrastructure - Product Analytics** - Cross System integrations - Alerts - Integrations **Model Deployment - Large Language Model Operationalization (LLMOps) ** - One-Click Deployment **AI Features - Observability** - Predictive Insights - Generative AI - AI Anomaly Detection **Prompt Performance - Prompt Management Tools** - Real-time Visibility **AI driven optimization - Product Analytics** - User scoring - Adaptive learning - Automated insights - Autonomous task execution **Additional Functionality** - Vulnerability Management - Load Balancing - Asset Discovery - AI Copilot - Real-Time Data - Incident Reporting - Real-Time Analytics - Threat Response - Threat Intelligence - Performance Metrics - Alerts/Notifications - Compliance Management - Workflow Management - Configuration Management - Issue Tracking - Reporting & Statistics - Log Management - Troubleshooting - Incident Management - Root Cause Analysis - Prioritization - Key Performance Indicators **Additional Functionality** - Conversion Tracking - Funnel Analysis - Product Data Management - Engagement Tracking - Alerts/Notifications - Cohort Analysis - Session Recording - AI Copilot - Data Visualization - Customer Journey Mapping - Generative AI - Interactive Reports - A/B Testing **Model Monitoring - Large Language Model Operationalization (LLMOps)** - Real-Time Performance Metrics **Security - Large Language Model Operationalization (LLMOps)** - Access Control Management **Performance** - Real User Monitoring (RUM) - Performance Metrics **Functionality** - Load Balancing - Cloud Observability - Server Monitoring **Additional Functionality** - Real-Time Data - Email Alerts - Bottleneck Identification - API - Uptime Reporting - Resource Management - Dashboard Creation - Data Import/Export - Baseline Manager - Issue Tracking - Drag & Drop - Reporting/Analytics - Alerts/Notifications - Prioritization - Collaboration Tools - Real-Time Reporting - Application Management - SSL Security - Incident Management - Access Controls/Permissions - Status Tracking - Audit Management - Customizable Reports - Diagnostic Tools - Single Sign On - Workflow Management - AI Copilot - Activity Tracking - Event Logs ## Top LaunchDarkly Alternatives - [PostHog](https://www.g2.com/products/posthog/reviews) - 4.5/5.0 (1,046 reviews) - [Statsig](https://www.g2.com/products/statsig/reviews) - 4.7/5.0 (346 reviews) - [Optimizely Web Experimentation](https://www.g2.com/products/optimizely-web-experimentation/reviews) - 4.2/5.0 (401 reviews)