LaunchDarkly

What do you like best about the product?

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 the product?

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 the product 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.

What do you like best about the product?

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.

What do you dislike about the product?

Pricing gets a bit steep as you add more seats, and the dashboard navigation could be more streamlined. Nothing major though.

What problems is the product solving and how is that benefiting you?

Payroll is a zero-tolerance domain, mistakes are immediately visible to end users. LD lets us A/B test payroll flow changes on a controlled subset of companies first, catch issues early, and roll back instantly if needed.

What do you like best about the product?

The biggest unlock for our team was making it quick and easy for developers, CS, and leadership to see exactly which features each customer has turned on.

What do you dislike about the product?

No downsides so far. It’s quick and easy to turn feature flags on and off for individual customers, which makes managing rollouts really straightforward.

What problems is the product solving and how is that benefiting you?

We run a multi-tenant system, which can quickly turn into a logistical nightmare when it comes to feature flagging. LaunchDarkly makes it straightforward to run A/B tests and clearly see exactly who has which features turned on.

What do you like best about the product?

I really like how it manages feature flags. Having one centralized place to control them is very convenient and makes the whole process feel more organized.

What do you dislike about the product?

It can feel pretty overwhelming for newbies at first.

What problems is the product solving and how is that benefiting you?

LaunchDarkly is helping us solve our problem with feature flag management, and it does that quite well. we used to have lots of feature flags littered all over our products that were difficult to keep track of. Now with LaunchDarkly, that problem is a thing of the past.

What do you like best about the product?

Easy feature flagging platform to control rollout of features

What do you dislike about the product?

Doesn't work for other purposes that well such as a/b testing

What problems is the product solving and how is that benefiting you?

Controlling rollouts of code, easier to manage and maintain

What do you like best about the product?

Comfortable for flag management per environment

What do you dislike about the product?

The UI is not straightforward when trying to add a new flag

What problems is the product solving and how is that benefiting you?

different environment and container flags management in one place

What do you like best about the product?

What I like most about LaunchDarkly is being able to control feature releases without needing new deployments. It gives us the confidence to roll out features gradually, test changes with specific user groups, and quickly disable a feature if any issues come up. Overall, the platform is reliable and easy to use, and it has become an essential part of our release process. It’s helped us reduce deployment risk, improve operational stability, and move faster as a team.

What do you dislike about the product?

Nothing as such, the installation and setup are very easy. So no complaints

What problems is the product solving and how is that benefiting you?

It is solving the problem of AB testing. We can now test features way faster with LD.

What do you like best about the product?

The biggest win for our team has been the UI/UX, it's genuinely intuitive. Our non-technical stakeholders can toggle flags without bugging engineers. The integrations with our Datadog pipeline and Slack for notifications have made rollouts smoother. Performance-wise, the SDK latency is negligible even with hundreds of flags in production. Plus, the support team answered our oncall questions at 2 AM, that matters when you're rolling out to millions of users.

What do you dislike about the product?

The onboarding documentation is comprehensive but requires time investment to fully understand best practices around flag cleanup and cost optimization. The AI-powered insights are helpful for identifying anomalies, though they're fairly straightforward and don't offer advanced recommendations. A few integrations we wanted to use required custom webhook implementations, which added some development overhead.

What problems is the product solving and how is that benefiting you?

We needed safer deployments without full rollbacks. Now we roll out features to 1% → 10% → 100% with real-time kill switches. It's cut our incident response time by 30%. The performance impact is zero, so we're not choosing between safety and speed. It's also letting us do canary releases and A/B tests in production confidently, basically, we've moved from nerve-wrecking to confidence deployments.

What do you like best about the product?

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.

What do you dislike about the product?

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.

What problems is the product solving and how is that benefiting you?

The big one for me is that it's closed the gap between when something is built and when we actually feel confident putting it in front of customers. That used to be a stressful handoff, lots of back and forth, timing pressure, hoping nothing breaks. Now the flag is already in prod, we control the switch, and we can move at our own pace. I'll typically start with a small beta, maybe 10 or 15 customers, get some signal, and then expand from there. It also makes cross-team coordination easier. I can tell customer success exactly what's going out and when, without waiting on release notes or a deploy window. It's made the whole release process feel a lot less chaotic honestly. Less firefighting, more intentional shipping.

What do you like best about the product?

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 the product?

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 the product 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.