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

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

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

There is nothing to dislike about LaunchDarkly. Review collected by and hosted on G2.com.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

AI features feel like an afterthought and somewhat unnecessary. Review collected by and hosted on G2.com.