Share your experience using Plutora

My use cases for LaunchDarkly involve managing risk from new features such as AB testing and canary releases for features with gradual rollouts. This type of work is fundamentally about managing risk and testing new features.

I haven't used LaunchDarkly to manage any AI in production; the only thing I've used it for is feature flags for the most part.

What stands out to me about LaunchDarkly is that it's super easy to use. I appreciate that you can serve the feature at a percentage and that you can add users by email. For example, I used it in the past to do internal-only testing of the feature in production, which was very helpful.

From what I've seen, the management of feature flags in LaunchDarkly is pretty good. I don't have any other reference point to compare it to, but it's pretty simple to create a new flag and then edit the flag and increase or decrease traffic to that flag. I'm not an expert on feature testing, but for what I've used, it works for what I needed.

If LaunchDarkly goes down and you don't have it set up right, it could be a problem for you. I think that's a little bit on user error as well.

I would like some sort of a local instance to be available.

I've been working with LaunchDarkly overall for at least a few years, probably around three years.

I've seen lagging, crashing, or downtime with LaunchDarkly. There was an outage, and that's what I was referring to. If there's ever an outage, I think you can define a default experience in your code, but I don't think we did that well. It might have reverted to an experience that we did not want the customers to see. For instance, my company developed a new version of our checkout page, and it was behind a LaunchDarkly flag, but it was serving 100% traffic to that flag. But when LaunchDarkly went down, it started using the prior checkout page, which is not as good of a page, which is why I'm saying that it's a problem if LaunchDarkly goes down.

Regarding scalability, I think LaunchDarkly is pretty scalable. I've never had issues with it scaling.

I've never actually used anything similar to LaunchDarkly, but I'm aware that there are competitors; however, LaunchDarkly is the only one that I've used.

The initial deployment of LaunchDarkly was handled by a platform team that managed that initial setup, but as far as integrating it to my service, it's pretty easy to just create a LaunchDarkly client, much like any other type of client for any external software that you use, and then just go ahead and start using the flags.

LaunchDarkly usually does not require any maintenance on my end. It's usually taken care of. The only time we have maintenance is if we're not using any flag anymore, or we make it a permanent feature instead of a feature flag; then we'd have to go into the code and clean it up to delete the flags and then delete it from LaunchDarkly. But in terms of maintenance outside of that, there isn't much required.

On a scale from 1 to 10, I would give LaunchDarkly an 8. I would definitely recommend it to another customer. It's always worked for me, except there have been outages here and there, but very rarely. I'd say it's pretty good for the most part.

My use case for LaunchDarkly is for releasing features that we don't want to make available to customers immediately, or for beta testing. We put features behind feature flags and perform continuous deployment. Every week we deploy to production, but the whole feature is not available for clients, so we put it behind LaunchDarkly feature flags.

I have not used LaunchDarkly to manage AI in production, models, prompts, or agents.

What I like most about LaunchDarkly is the ability to create segments easily. You don't have to create rules repeatedly. You just add your specific requirements into the segment and proceed from there without reworking the entire flag or rules.

Over the period, I have seen measurable improvements in metrics such as evaluation scores when I implemented LaunchDarkly. They have made improvements, especially in enabling it globally and enabling it for a particular client, which makes a difference. Turning it off and turning it on was not a feature previously, but now it is much easier. If nothing is working, you can simply turn it off.

In the new UI where they have put production and related items next to each other, I find it is sometimes hard to determine if a feature flag is on in production or off. Looking for that specific information in the new UI was not pleasant for me.

I have been working with LaunchDarkly for almost five or six years.

Regarding stability, it happened in four or five years of usage a couple of times that it was not syncing properly. Over the period, it got better.

I would rate LaunchDarkly a seven in terms of scalability.

I have not used anything similar to LaunchDarkly. We have been using this product for a long time.

The initial setup was easy, and I was able to train my team. It took a couple of weeks and a couple of deployments for everyone to fully understand how to set it up for our company.

I have been working in my current field overall for 15 or 16 years. The maintenance is taken care of by the team. I have not integrated any other tools with LaunchDarkly. I would give LaunchDarkly an overall rating of eight.