LaunchDarkly

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.

What do you like best about the product?

LaunchDarkly is relatively easy to set up and has a straightforward learning curve compared to the other platforms we explored.

What do you dislike about the product?

So far, I haven't come across any major drawbacks, at least with the features I've worked with and explored.

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

Most of my exploration has been around feature flags and user lifecycle–based experiment setup.

My main use case for LaunchDarkly  is feature flagging and gradual rollouts. Instead of releasing a new feature to all users at once, we can first enable it for internal users, then for a small group of customers, and only later roll it out to everyone.

When we released a new feature, we first turned it on only for internal users. After that, we enabled it for a small percentage of real customers, which helped us test that feature in production without taking too much risk. If something went wrong, we could simply turn the flag off in LaunchDarkly  without doing a full rollback.

We use flags for gradual deploying and testing, then rolling out. For example, we enabled a feature, tested it in a specific environment, then turned off this flag.

The best feature LaunchDarkly offers is the flag that allows rollouts.

What I appreciate about LaunchDarkly is that the setup was easy, it had a clean user experience, and the control allowed us to manage the features without deploying them to everyone. We could deploy it gradually and then roll out easily. I particularly value the ability to click to turn the feature on and off.

LaunchDarkly has positively impacted my organization by reducing the risk of releasing new features because we did not have to expose everything to all users at the same time. It eventually resulted in faster releases and more confidence. It also saved engineering time because in some cases, we did not need to do a rollback or hot fixes; we could simply disable the feature flag. Additionally, it reduced the QA time since they could only test a specific area.

LaunchDarkly can be improved by managing old flags. We have an issue with old flags; it became very messy very fast and we need to be very disciplined about managing these flags. I also heard from the manager that it was very expensive when the usage grew.

Perhaps LaunchDarkly could mark old flags somehow or add a tag to these flags when they are not in use or have not been used for a long time. We found ourselves after a short period of time having too many flags.

I have been working in my current field for above ten years.

I used LaunchDarkly in my previous company for several months.

Overall, LaunchDarkly saved our engineering time and helped us manage features very smoothly, allowing us to gradually deploy and roll out.

My advice for others looking into using LaunchDarkly is to manage the flags carefully, as it can become messy very fast.

I believe LaunchDarkly is a very useful tool for teams wanting to release features quickly and safely; it gives a lot of control and helps reduce the risk around production releases. I would rate this product an eight out of ten.

Public Cloud

Amazon Web Services  (AWS )

What do you like best about the product?

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.

What do you dislike about the product?

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.

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

LaunchDarkly provides ease of maintenance and helps solve the risk of shipping code directly to all users at once. With feature flags, we can decouple deployment from release—code goes out, but features stay off until we’re ready. We can roll out to 1% of users, watch metrics, then either expand the rollout or kill it instantly without a redeploy. It also lets us run A/B experiments without engineering overhead each time, and it gives non-technical team members control over feature visibility. The result is faster releases, fewer incidents, and less pressure on every deploy. Overall, the system has a user-friendly UI.

What do you like best about the product?

LaunchDarkly is easy to understand while still being extremely comprehensive and flexible. I’ve used it at multiple workplaces, and I’m always happy to see it already in use as a service at an organization.

What do you dislike about the product?

Not much to complain about—any shortcomings I initially thought it had were overcome once I learned more about the product.

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

Segmented rollouts let us release features to specific user groups, using feature flags so we can quickly revert if needed. It also makes it easy to target particular user segments when a feature requires it.