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.

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

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

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

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

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

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

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

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

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

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

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

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

I use LaunchDarkly for feature flags to manage visibility to users. I find it super user-friendly and, once set up, it's incredibly easy to manage customers and ensure everything works properly. I really like the integrations, particularly with Slack, as they help us stay updated on any changes and improve visibility as a team, making sure we're all on the same page. The initial setup was great and super easy. I definitely recommend it; it's super nice to have. Review collected by and hosted on G2.com.

Sometimes user management is a little bit hard. I guess it's the search functionality; I'll try to add customers, and because I'll search for them, it doesn't always work as expected. Review collected by and hosted on G2.com.