LaunchDarkly
LaunchDarklyExternal reviews
727 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Effortless Feature Management with Room for UI Improvement
What do you like best about the product?
I use LaunchDarkly for managing feature flags on a Next.js app. I appreciate being able to have different configurations for different environments and being able to change them on the fly without redeploying code. It is very easy to use and updates very fast. I like the granularity of the rules, which is valuable for launching new features in a limited way. Also, we have a Slack integration for changes, which is handy.
What do you dislike about the product?
I feel like there could be a better UI for changing JSON responses. For example, having a UI where you can add or remove fields without directly editing the JSON, sort them automatically, etc.
What problems is the product solving and how is that benefiting you?
I use LaunchDarkly to manage feature flags on a Next.js app. It solves the problem of updating configurations across different environments on the fly without redeploying code. I like its ease of use, fast updates, and the granular control for targeted feature launches.
LaunchDarkly Makes Safer, More Controlled Feature Rollouts Easy
What do you like best about the product?
That's a fun question! I don’t have personal preferences or firsthand experiences with tools, but I can share what developers and teams commonly appreciate about LaunchDarkly.
It’s widely regarded as one of the more mature, full-featured feature flag management platforms. Teams often value how it helps decouple deployments from releases: you can ship code whenever you’re ready and then use flags to control who actually sees a feature. That approach tends to make rollouts, A/B testing, and kill switches feel much safer and easier to manage. People also frequently point to the granular targeting and segmentation options, along with real-time flag evaluation and minimal latency, as standout strengths.
It’s widely regarded as one of the more mature, full-featured feature flag management platforms. Teams often value how it helps decouple deployments from releases: you can ship code whenever you’re ready and then use flags to control who actually sees a feature. That approach tends to make rollouts, A/B testing, and kill switches feel much safer and easier to manage. People also frequently point to the granular targeting and segmentation options, along with real-time flag evaluation and minimal latency, as standout strengths.
What do you dislike about the product?
I don't disTheir pricing is per-seat and scales with the number of monthly active users (MAUs) your application serves, which can add up quickly as you grow. The free tier is quite limited, and once you need features like advanced targeting, experimentation, or audit logs, you're looking at their Pro or Enterprise plans which can get costly.
What problems is the product solving and how is that benefiting you?
Sure! Here’s a positive take:
LaunchDarkly is a game-changer for teams that want to ship with confidence. It enables gradual feature releases, so instead of a nerve-wracking big-bang launch, you get a smooth, controlled rollout where you can monitor what’s happening in real time.
Teams appreciate being able to toggle features on or off instantly, experiment safely with different user segments, and move quickly without breaking things. Developers can merge code daily with less anxiety, product managers can test ideas with real users earlier, and everyone sleeps better at night knowing there’s always a fast “off switch” if something goes wrong. The UI is clean, intuitive, and well organized, so even non-technical team members can navigate it comfortably. The dashboard also provides a clear at-a-glance view of your flags, their statuses, and your environments.
LaunchDarkly is a game-changer for teams that want to ship with confidence. It enables gradual feature releases, so instead of a nerve-wracking big-bang launch, you get a smooth, controlled rollout where you can monitor what’s happening in real time.
Teams appreciate being able to toggle features on or off instantly, experiment safely with different user segments, and move quickly without breaking things. Developers can merge code daily with less anxiety, product managers can test ideas with real users earlier, and everyone sleeps better at night knowing there’s always a fast “off switch” if something goes wrong. The UI is clean, intuitive, and well organized, so even non-technical team members can navigate it comfortably. The dashboard also provides a clear at-a-glance view of your flags, their statuses, and your environments.
Effortless Flagged Releases and Instant Rollbacks—No Redeploy Needed
What do you like best about the product?
What I like best is that it decouples deploy from release. Code can ship behind a flag and get turned on for a specific user, a percentage of traffic, or a whole segment — no redeploy needed. Rollbacks become a toggle instead of a fire drill, and risky changes can be tested on real traffic in tiny slices before going wide.
What do you dislike about the product?
Honestly, the pricing. It's priced per seat and per MAU, so the second other teams catch on and want in, the bill jumps in a way that's hard to defend to finance
What problems is the product solving and how is that benefiting you?
The benefit is mostly that releases stopped being scary. Engineers ship more often, on-call is quieter, and product can actually run real experiments instead of guessing.
Easy Access and Permission Control, but Search and Favorites Need Work
What do you like best about the product?
Easy to access for everyone. Managing permissions.
What do you dislike about the product?
NO favorites can be set. Difficult to search. lack of access to team based
What problems is the product solving and how is that benefiting you?
Sending traffic based on the conditions and thats the only usecase I know
Game-Changing Feature Toggles for Confident, Faster Rollouts
What do you like best about the product?
The ability to toggle features independently without a new deploy has been a game changer for how I work. Being able to test in staging and production separately, then roll out to specific users or orgs before a wider release, gives me a level of control and confidence that has meaningfully sped up how I ship and validate new features.
What do you dislike about the product?
Managing multiple flags across several projects can get cluttered over time. A cleaner way to archive or organize older flags would make it easier to keep things tidy at scale.
What problems is the product solving and how is that benefiting you?
It gives me a safe and controlled way to ship experimental features without risk to production. Being able to feature flag new builds means I can put things in front of internal users for testing, gather feedback, and iterate without waiting on full deployment cycles. For the kind of AI-forward prototyping I have been doing, that speed and flexibility has been critical.
LaunchDarkly: Reliable, High-Performance Feature Flags with Generous Pricing
What do you like best about the product?
It does what it says it does, and does it well. It's easy to add new flags. It's easy to configure how the flags are calculated, add custom test groups, percentage rollouts, etc. Performance is great, I've never seen the service down. Pricing is generous. In this age of build vs buy, LaunchDarkly is still a a Good Buy.
What do you dislike about the product?
Sometimes the UX is frustrating. Hard to remember where to go to do what i want.
What problems is the product solving and how is that benefiting you?
We need to roll out features slowly before turning them on to the full audience. This solves that, and does it very well.
Clean Release Control with Powerful Flags and a Reliable Kill Switch
What do you like best about the product?
What I like most about LaunchDarkly is how cleanly it decouples deployment from release. We can ship code to production behind a flag and then roll it out gradually—to internal users first, then a small percentage of customers, and finally everyone—without any redeploys. The targeting rules (by user attribute, segment, or environment) are powerful yet still straightforward to configure in the dashboard, so even non-engineers like PMs and support can flip flags safely.
The kill-switch capability has saved us more than once: when something misbehaves in production, we can simply toggle the flag off instead of rushing a hotfix or doing a rollback. The SDKs for all the major languages we use have been reliable, and flag changes propagate to clients in near real time.
The kill-switch capability has saved us more than once: when something misbehaves in production, we can simply toggle the flag off instead of rushing a hotfix or doing a rollback. The SDKs for all the major languages we use have been reliable, and flag changes propagate to clients in near real time.
What do you dislike about the product?
Pricing can get steep as you scale. Adding seats and unlocking certain features (like experimentation and advanced analytics) often nudges you toward an enterprise plan, which can be tough to justify for smaller teams. The UI also comes with a real learning curve: given the depth of features across projects, environments, segments, and targeting rules, new team members usually need some time before they feel comfortable navigating everything.
What problems is the product solving and how is that benefiting you?
LaunchDarkly solves the core problem of releases being risky, all-or-nothing events. By decoupling deployment from release, we can merge and deploy code continuously while keeping new features hidden behind flags until they're ready. This has dramatically reduced the stress around shipping — there's no more bundling features into big releases or scheduling late-night deploys.
The targeting and gradual rollout capabilities let us release to internal users, then beta customers, then a small percentage of production traffic before going 100%. If something breaks, we flip the flag off instantly instead of rolling back or hot-fixing. This has cut our incident recovery time significantly and given engineers the confidence to ship more often.
It's also empowered non-engineering teams — PMs control beta access, support can toggle entitlements, and marketing can time feature launches to campaigns without needing engineering involvement for every change.
The targeting and gradual rollout capabilities let us release to internal users, then beta customers, then a small percentage of production traffic before going 100%. If something breaks, we flip the flag off instantly instead of rolling back or hot-fixing. This has cut our incident recovery time significantly and given engineers the confidence to ship more often.
It's also empowered non-engineering teams — PMs control beta access, support can toggle entitlements, and marketing can time feature launches to campaigns without needing engineering involvement for every change.
Peace of Mind for Confident Feature Releases with LaunchDarkly
What do you like best about the product?
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.
What do you dislike about the product?
AI features feel like an afterthought and somewhat unnecessary.
What problems is the product solving and how is that benefiting you?
Controlled rollout of new features, giving us peace of mind that we can instantly rollback anything broken and fully test new features before they're enabled for all users.
Fast and AI-Compatible With a Snappy UI
What do you like best about the product?
I like that LaunchDarkly is fast and works well with AI. The Slackbot makes it easy to open tickets from Slack conversations, and the snappy UI makes it effective to work with the product. Additionally, the initial setup was easy.
What do you dislike about the product?
not much
What problems is the product solving and how is that benefiting you?
LaunchDarkly is fast and integrates well with AI. The Slackbot feature allows easy ticket creation from Slack, and its snappy UI enhances productivity.
Great Features, but Integration Needs Improvement
What do you like best about the product?
One thing I like about LaunchDarkly is the ability to let certain customers use certain features while others do not.
What do you dislike about the product?
One of the major issues is that we're adding a lot of flags for many different companies and projects, but we have no way of integrating the company IDs and the project IDs with LaunchDarkly. So we kinda have to find them and manually add them. It would be better if we could select the LaunchDarkly flags with checkboxes and then automatically pick a company or project, enabling or sending it for approval instead of doing everything manually. The process is very manual at the moment, making it tedious, which affects how likely I would recommend it.
What problems is the product solving and how is that benefiting you?
I use LaunchDarkly to add features to specific customers and projects for testing, ensuring most customers aren't affected during trials.
showing 1 - 10