LaunchDarkly Reviews & Product Details

The peace of mind during production deployments is unmatched. Being able to decouple deployment from release means we ship code to production behind flags and verify in silence. If an unexpected latency spike or error occurs, flipping a flag acts as an instantaneous kill switch without triggering an emergency hotfix or rolling back an entire release pipeline. It completely changes deployment confidence. Review collected by and hosted on G2.com.

The pricing model can be surprisingly difficult to forecast as you scale, especially if you rely heavily on client-side feature flags. Because billing factors in Monthly Active Users (MAUs) and service connections, a sudden spike in traffic or expanding our client-side footprint can cause the bill to increase faster than expected. It’s definitely an enterprise-tier tool with an enterprise-tier price tag. Review collected by and hosted on G2.com.

LaunchDarkly gives our team the confidence to release often while keeping production stable. Staggered rollouts managed by LD flags help us control and mitigate any unwanted production downtimes. Simple to use and easy to navigate UI makes it easy to adapt. LaunchDarkly MCP and Slack automations is also an added advantage. Review collected by and hosted on G2.com.

There is Targeting rules can be confusing when many services share a flag. It’s hard to see why a flag gave a certain value. Old flags pile up - there should be feature to automate archival flags when not in use. The price can go up quickly as the team and usage grow. Review collected by and hosted on G2.com.

The biggest value is shipping risky fixes to production turned off, then turning them on for one customer at a time across our many environments. Rolling back is a toggle, not a redeploy, so we ship faster with less risk. The REST API is excellent. We script almost all flag work and built a daily Slack digest on it to catch stale or partly rolled-out flags. Flags have become our release process, and the ROI shows up in emergency rollbacks we never had to do. Review collected by and hosted on G2.com.

Targeting is easy to get wrong. Individual targets are stored apart from rules, and new rules default to the "user" context kind, which can silently match nothing. Stale-flag cleanup is left to us, so we built our own digest. It's also hard to see what flag value a long-running worker actually evaluated. Warnings on rules that can't match and built-in stale-flag tracking would help a lot. Review collected by and hosted on G2.com.

What I like most about LaunchDarkly is that it makes managing feature flags and rollouts really simple. I can easily control features for different environments or specific tenants without having to deploy the application again. The targeting rules are especially useful when we want to test something gradually or enable a feature for only a specific set of users. It makes feature rollouts safer and gives us more flexibility during development and testing. Review collected by and hosted on G2.com.

One thing I find a little challenging is that the number of options and settings can feel overwhelming at first, especially when setting up more complex targeting rules. It takes some time to understand all the available configurations. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

The audit trail is really useful whenever someone asks why a feature was enabled or when a change went live. Instead of piecing together the full timeline from scattered messages, I can quickly see what happened and when. I also appreciate that it gives me the breathing room to spot unexpected changes before they reach everyone, while still providing complete support and consistent performance. Review collected by and hosted on G2.com.

Sometimes I need more context about a flag’s business purpose. The technical names alone don’t tell me which financial reports or downstream metrics could be affected, and the UI could do a better job of surfacing that information so it’s easier to find when I need it. Review collected by and hosted on G2.com.

I like being able to release code and switch features on separately, because it gives us more control over when changes actually reach users. For example, we can decide whether a specific user or organisation should receive a different value.

Gradual rollouts also help us introduce features to a small group first, gather feedback, and build confidence before moving to a wider release.

Being able to switch a feature off quickly is particularly useful if something goes wrong, since it reduces the pressure to rush out another deployment just to undo a change.

Finally, having feature flags in one place makes it easier to see what’s enabled and to manage changes consistently across environments. Review collected by and hosted on G2.com.

I’d like to be able to create rule templates. For example, if I create a handful of flags to gate new features, I want to set up one reusable rule that enables them for my test user/shard/whatever, and then apply that same rule to all of those flags at the same time. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

I really like how seamless LaunchDarkly is to use. It connects very well with our AI systems, and its MCP integration is a game changer for connecting with coding agents like Claude, Codex, or even Cursor. The integration allows agents to make their own requests without needing to manually interact with the UI, which is both clean and functional. The ability to easily search for flags and filter by maintainers in the UI is something I appreciate a lot. Review collected by and hosted on G2.com.

One thing that's really hard to do is clean up flags that are no longer in use, like whether that be deleting them. I feel like you can't even find the delete button on the UI. Um, like I might accidentally create a LaunchDarkly flag that I'm like, hey, like I don't want it anymore and it's so hard to delete it or get rid of it. Uh, there's a lot of stale flags as well. So a way for us to easily recognize when flags are no longer being used, maybe like for a certain period of time, right? Maybe like for 60 days or something. If something hasn't been used, um, like maybe send a suggestion on should we deprecate this because I feel like we have a couple of flags that like are never used and sometimes agents pick up on them and um, it's not like up to date with the current system. Review collected by and hosted on G2.com.