Honestly, the thing that's made the biggest difference for me is just being able to control who sees what without having to rope in an engineer every single time. We're juggling a lot of moving parts —HR, IT, payroll—and before LD, getting a feature in front of a specific set of customers meant coordinating deploys, syncing across teams, the whole thing. Now I can target a specific customer segment, set a rollout percentage, and go. The experimentation piece has also been really useful, I use it to gut-check whether something is actually working before we fully commit. And the audit log sounds boring but I reference it more than I expected to. Stakeholders ask "why did this change" and I can just show them. That alone has saved a few awkward conversations. Review collected by and hosted on G2.com.

Nothing major honestly. If I had to nitpick, the initial setup and the whole projects/environments structure takes a little getting used to, new people on the team sometimes need a bit of hand-holding at first. But once it clicks it's fine. More of a onboarding thing than an actual issue with the product. Overall it's been pretty smooth for us. Review collected by and hosted on G2.com.

The dashboard is clean and intuitive enough for PMs to manage rollouts without needing dev help. Flag targeting and the segment builder are powerful, although complex rule sets can get cluttered and harder to scan. Integration with our existing system was straightforward, and the SDK coverage spans every major language we use. Flag evaluation is effectively near-zero latency on the client side, propagation is sub-second, and we haven’t seen any measurable overhead in the app.

Pricing feels acceptable for what you get. I haven’t fully explored the AI features yet, so I’m holding off on judging those for now. Overall, it’s a strong choice for teams that ship continuously, but budget-conscious orgs or teams with a low release cadence should compare alternatives first. Review collected by and hosted on G2.com.

It’s unable to handle complex rules. The product itself seems like it was designed for non-dev users in the first place, but in real-life environments you often need to deal with more complex situations; otherwise, we’re not able to cover the majority of the system.

It’s also important to point out a major issue with segment integration with the backend system: there’s a bug where it can’t retrieve the correct value while segment targeting is being processed. Although we tried to contact LaunchDarkly support, the problem seems to remain unresolved. Review collected by and hosted on G2.com.

The ability to run A/B tests on specific user segments without a deployment has been huge for our team. Since we work on HR & Payroll, where changes to payroll calculations or tax logic are high stakes, being able to gradually test on a small set of companies before rolling out broadly is a lifesaver. Integrations with Slack and Datadog keep the team in the loop without any extra effort, and the AI-assisted flag cleanup suggestions are a nice bonus. Review collected by and hosted on G2.com.

Pricing gets a bit steep as you add more seats, and the dashboard navigation could be more streamlined. Nothing major though. Review collected by and hosted on G2.com.

What makes LaunchDarkly truly stand out is how effectively it decouples code deployment from feature release, turning high-stakes launches into controlled, low-drama events. Engineers can ship code to production quietly behind a flag, then roll it out with fine-grained percentage controls, run beta tests for specific user segments, and use instant “kill switches” to isolate bugs in milliseconds without needing a full rollback. By shifting day-to-day release control into a visual dashboard, it also empowers product and marketing teams to decide when a feature actually goes live. That, in turn, reduces developer stress and helps keep overall system stability high. Review collected by and hosted on G2.com.

While LaunchDarkly is widely seen as an industry leader in feature management, teams often encounter a few recurring pain points during adoption. The most common critiques tend to fall into two areas: technical debt and cost.

Because it’s so easy to create flags, organizations can quickly accumulate “flag debt,” where dead or obsolete toggles stay buried in the codebase. Over time, this adds clutter and can introduce logic bugs if flags aren’t actively tracked and cleaned up. On the cost side, the pricing model—scaling with Monthly Active Users (MAUs) and seat counts—can become prohibitively expensive for high-traffic consumer apps or fast-growing startups.

Finally, some teams mention a modest learning curve when managing more complex targeting rules, along with the operational dependency this creates. If the platform experiences latency or downtime, it can affect how quickly an application resolves its runtime configuration. Review collected by and hosted on G2.com.

I use LaunchDarkly to make production deployments much safer by enabling features only for internal users at first and then gradually rolling them out to larger percentages of customers. I really like how easy it makes progressive rollouts and targeting, allowing me to enable features for specific users, teams, or percentages of traffic directly from the dashboard, which gives a lot of confidence when deploying changes. The targeting capabilities are especially useful because I can enable features based on attributes like customer creation date, subscription type, or specific workspaces. The initial setup was pretty straightforward, with the SDKs and docs making it easy to get started. Review collected by and hosted on G2.com.

One thing that could be improved is the pricing model, it can become pretty expensive as usage grows. It would be great to have more flexible pricing tiers for growing engineering teams. Review collected by and hosted on G2.com.

As a PM, LaunchDarkly has become essential for how we ship features, especially when we need to enable something for a specific customer without any engineering involvement, whether it's in Private Beta or not yet available to general customers. LD gives us the ability to create targeted segments, so I can roll out to specific customer cohorts by region, or our private beta group, all without a separate build or engineering involvement.

The UI is clean and smooth, and our engineering team found the support very responsive during integration. We haven’t used any AI Intelligence features yet, but the core functionality has been genuinely useful. Review collected by and hosted on G2.com.

To be honest, I have no major complaints on the functionality side, it has solved every scenario that we had. So, no complaints - great work, and great team. Review collected by and hosted on G2.com.

I really like how LaunchDarkly separates deployments from feature releases. It lets us ship code whenever we want and decide later who gets access to a feature. That flexibility has made testing and releasing changes much smoother for our team Review collected by and hosted on G2.com.

Sometimes it takes a few clicks to find specific flags or settings, especially when managing a large number of feature flags. Better navigation and organization would make the experience smoother. Review collected by and hosted on G2.com.

LaunchDarkly has become an integral part of our feature delivery workflow at CleverTap. By decoupling deployments from releases, it gives our engineering teams the confidence to ship code with far less risk. Having feature flags, gradual rollouts, kill switches, and A/B testing all in one place significantly reduces coordination overhead across teams. The targeting rules and segmentation are powerful yet still intuitive to use, and real-time flag evaluation with minimal latency means we don’t have to compromise on performance. Overall, it has made our release process faster, safer, and much more controlled. Review collected by and hosted on G2.com.

Pricing can be steep, and as usage scales it becomes a noticeable line item for larger engineering organizations. The dashboard UI is feature-rich, but it can feel overwhelming for new team members when they’re onboarding to the platform. Flag hygiene and lifecycle management—especially archiving stale flags—also require deliberate effort and discipline, since there isn’t strong enforcement out of the box. In addition, the audit log and reporting could be more granular; deeper visibility into flag evaluation history and the impact of changes would be valuable for compliance and debugging. Review collected by and hosted on G2.com.

The ability to toggle features independently without a new deploy has been a game changer for how I work. Being able to test in staging and production separately, then roll out to specific users or orgs before a wider release, gives me a level of control and confidence that has meaningfully sped up how I ship and validate new features. Review collected by and hosted on G2.com.

Managing multiple flags across several projects can get cluttered over time. A cleaner way to archive or organize older flags would make it easier to keep things tidy at scale. Review collected by and hosted on G2.com.

I find LaunchDarkly very easy to set up and use. It works very well in the app and isn't complicated at all. We just put the hooks in the code and use it out of the box, allowing us to target users and specific stores easily. Our team of about 20 people finds it really helpful, and the ease of setup makes it valuable to our workflow. Review collected by and hosted on G2.com.

Once we had an incident that it wasn't working well, but it was very quickly resolved. I think having more predefined sets of groupings detecting their requests and allowing you to choose which context to use would be very helpful. Sometimes you want to enable feature flags for specific stores, so it would be very helpful if those stores were readily available as dropdown options to choose from there. Review collected by and hosted on G2.com.