LaunchDarkly

My main use case for LaunchDarkly is to gate our new features behind the flags and to manage those flags via LaunchDarkly UI and portal and dashboard so that we can roll out different features properly tested on different environments and for different users and with different variations, with different configurations and settings.

One feature that we rolled out this way is a really big feature which was changing the product's whole flow and had to be rolled out to multiple markets, specifically to three different countries where our product is being used. Since it was a big feature, we had to get it behind the development first because it was in the development stage. We tested it out regularly with different variations, with different targetings, with different rule sets, using different LLMs and everything which was managed by LaunchDarkly. Then we launched it on staging, turning on the flag for staging to test it out there. When we rolled it into production, we selected a smaller customer country from the rules part for the launch to identify initial bugs or issues at a smaller customer base, eventually rolling it out and turning on the feature for bigger customers and bigger countries as well.

This is my main use case for LaunchDarkly; we create the flags there, manage them from there, and turn them on or off there. We have a whole dashboard where we can see who has made a recent change in the flag and what settings have been changed. If something breaks due to recent settings, we have an idea of what has been changed that caused it to not behave as required. Additionally, we have different variations, different rules in it, as well as a whole dashboard where we can look into it. It is really helpful to integrate it easily due to the flexibility that gives us confidence in LaunchDarkly.

LaunchDarkly has positively impacted my organization by providing flexibility and collaboration, as our company is divided into different squads. Every squad can collaborate on their flags, determining what needs to be turned on and for which squads, including variations and targetings.

I have witnessed improvements in collaboration through LaunchDarkly, as we have different variations for a flag that allows multiple squads to test different things simultaneously. Different squads use the same flag while testing various things, utilizing different variables, environments, variations, and targeting.

The best features LaunchDarkly offers include flexibility, a log about recent activities or who has done what, variations, targeting, and a single flag for different environments; these are the top most features that provide greater flexibility for LaunchDarkly.

Among those features, I rely on variations, the logs, and the rules the most; variations and the rules are particularly targeting the same thing, but these have significantly helped us.

I believe LaunchDarkly is working very well, but making it easier to integrate with code bases or providing an AI component that assists customers by understanding their code bases and supplying easy-to-integrate code snippets would be very helpful.

I have been using LaunchDarkly for almost around seven to eight months.

LaunchDarkly is stable.

Its scalability is good, as I mentioned previously, from the flexibility, scalability, and features points of view; it is good.

I have not felt a need to connect to customer support for anything, but I have heard from my other team members that customer support is great, really supportive, and collaborative. Their customer support success manager is in touch with us via emails, checking in about various matters, reviews, complaints, or anything else, which is great.

I previously used Flagsmith for our flags and feature flagging but switched to LaunchDarkly due to its superior features, including variations, flexibility, rules, targeting, and other options that were lacking in Flagsmith.

I advise others looking into using LaunchDarkly to go through the documentation thoroughly and select their use case since there are a lot of options available, but you do not need to go through each and every one. Just identify what relates to your use case because if you explore everything, it might become confusing, and you could struggle to switch to or effectively use LaunchDarkly. Focusing on your specific use case will help you find your solution in LaunchDarkly, and you might not have to use all of its features at once; you can use a part of it initially and later integrate additional features.

LaunchDarkly is working great, and I would encourage them to continue their excellent performance. They should aim to simplify things and avoid adding complex features that could complicate the product overall; keeping it simple and focused on use cases will keep it good. I am providing a review rating of nine for LaunchDarkly.

Private Cloud

Amazon Web Services (AWS)

What do you like best about the product?

I like LaunchDarkly's interface a lot because it's really simple and helpful, especially when creating a flag and targeting different environments. The flexibility it provides, like managing flags separately across development, staging, and production environments, is quite appealing. It's great that I don't have to create the same flag multiple times. The features like default rules, monitoring, and feedback within the same dashboard are really nice. The ability to have a JSON for different rules and the way it integrates with our product through SDK keys and environment variables is impressive. I also appreciate how flags are maintained, with options for descriptions, maintainers, and review processes to prevent mistakes.

What do you dislike about the product?

When I first started using LaunchDarkly, I faced some challenges, particularly with the initial setup and integration. For someone new, it can feel a bit difficult because I hadn't used LaunchDarkly before. I think it would be helpful to have a more detailed go-to guide or documentation to assist new users. While there might already be some resources, additional platform guidance would improve the initial experience. It would be great if there was an AI feature that could analyze code and guide users on where to place specific components, which would help simplify the integration process for beginners.

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

LaunchDarkly lets us test features safely, rolling them out gradually across environments to avoid bugs reaching customers. It provides flexibility and centralized flag management.

What do you like best about the product?

I really like how easy and fast it is to pick up flag changes with LaunchDarkly. It's straightforward to use with Claude and MCP, which makes creating and configuring new flags a breeze. Plus, I can easily identify fully rolled out flags that can be removed, all with the help of Claude. The initial setup was easy too.

What do you dislike about the product?

I'd like it to proactively recommend flags I can remove, or identify misconfigured flags, like backend-only flags with client access or temporary flags that should become permanent.

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

I use LaunchDarkly for safely rolling out changes to prod, experimenting, and swiftly reverting changes. It's fast and easy with Claude + MCP, letting me manage flags efficiently and identify unnecessary ones for removal.

What do you like best about the product?

Easy way to configure feature flags and configurations for multiple environments

What do you dislike about the product?

Interface that is hard to grasp, especially for the first timers

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

It helps me to easily setup feature flags, target different users, run A/B tests

What do you like best about the product?

I like the fingerprint feature most. In a very large team where flags are regularly updated, this feature allows you to immediately test-run a context to find out which variation it will receive.

What do you dislike about the product?

Switching environments requires you to click an icon first. The switching experience can be improved by allowing us to click the name of the current environment and a dropdown appears.

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

LaunchDarkly helps my software teams separate code deployment from feature release using feature flags. This allows us to easily run experiments and target specific groups of users before rolling out a feature globally.

What do you like best about the product?

I really like how incredibly easy it is to use LaunchDarkly with my coding agents to set up a flag and quickly connect everything. The process is so fast, and it's great that it only takes a couple of minutes. It’s also important for us because it solves a problem we have, acting as a sort of plug and play solution that's very quick to understand. Overall, LaunchDarkly is very valuable as it smoothly fits into our needs.

What do you dislike about the product?

I think that the overall user experience in the browser app is not as easy as it could be. There are probably better ways to make it more user-friendly so that people having their first contact with the app can easily understand how to change different environments and set up flags. It would be beneficial if the platform could utilize the new AI features more effectively. Moreover, I believe having a better MCP could eliminate the need for the UX entirely, making it so you only have to speak with an agent and use prompts, with everything being set up automatically. Also, using different kinds of toggles in the UI instead of drop-down lists might improve the experience.

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

LaunchDarkly allows me to regulate which clients receive different software versions. It's easy to set up feature flags and fast to implement, helping solve a bottleneck issue in our software.

What do you like best about the product?

It's easy to integrate, reliable, fast, and relatively good UI to visualize the feature flags. The CLI is very useful to pilot FF through ai agents.

What do you dislike about the product?

Launch Darkly offers a lot of features, which is great, but if you’re only using a subset of them, the pricing can feel relatively very expensive.

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

It helps us beta-test new features with a small segment of our audience, so we can gather feedback before opening them up to a larger audience.

What do you like best about the product?

As we develop our insurance claims categorization system for adjusters, doing full production releases frequently caused issues. LaunchDarkly's percentage-based progressive rollouts solved this by allowing me to roll out a new prompt or model update to just 5% or 10% of live claim extraction jobs rather than 100% at once. This is incredibly valuable. I also appreciate the in-memory flag evaluation, which ensures zero added network latency to our backend services because the Python SDK evaluates flag rules locally instead of making HTTP requests. The emergency kill switch is a major feature for me too; if an API starts failing, I can toggle the dashboard to instantly revert traffic back to our fallback logic without redeploying code. This makes handling issues seamless.

What do you dislike about the product?

There are a few things that could be improved in LaunchDarkly. Managing the lifecycle of feature flags requires strict engineering discipline. If developers don't clean up and archive old flags after a feature is fully rolled out, the dashboard becomes a confusing mess of stale toggles.

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

LaunchDarkly decouples deployment from feature release, letting us safely test and implement experimental logic by toggling features internally. It reduces operational risks by allowing quick model switches, minimizing downtime without redeployment. Progressive rollouts and kill switches make release management smoother and more flexible.

What do you like best about the product?

I find LaunchDarkly to be simple and easy to use, which is great. I also appreciate that it's very lightweight. The feature that allows for managing different environments to turn features on and off is particularly useful. Overall, I liked pretty much all aspects of it.

What do you dislike about the product?

Sometimes can be overwhelmed

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

LaunchDarkly helps me with testing and deployment of features using feature flags across different environments, and I find it simple, easy, and lightweight.

What do you like best about the product?

I like how LaunchDarkly makes feature releases less risky. We can roll out features gradually, test with specific users and quickly turn them off if something goes wrong without needing another deployment.

What do you dislike about the product?

It can feel a bit overwhelming at first, especially with a lot of feature flags across different environments. Keeping old flags cleaned up also takes some effort.

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

LaunchDarkly helps us release features safely without tying every change to a deployment. We can test with a small group, roll out gradually, and disable features quickly if issues come up.