--- title: LaunchDarkly Reviews meta\_title: 'LaunchDarkly Reviews 2026: Details, Pricing, & Features | G2' meta\_description: Filter 812 reviews by the users' company size, role or industry to find out how LaunchDarkly works for a business like yours. aggregate\_rating: rating\_value: 4.5 review\_count: 812 scale: '5' date\_modified: '2026-08-10' parent\_category: name: Development url: https://www.g2.com/categories/development ---

# LaunchDarkly Reviews & Product Details

Visit Website

Founded in 2014 and headquartered in Oakland, California, LaunchDarkly serves over thousands of enterprises, including a quarter of the Fortune 500. LaunchDarkly is the runtime control platform for the AI era, trusted by software teams to control AI-generated code and AI agents in production at any scale. The LaunchDarkly platform delivers runtime control through two solutions: CodeControl and AgentControl. CodeControl helps teams ship AI-generated code confidently. With CodeControl, teams can observe production behavior, make changes in real time, and limit exposure based on actual impact. Through a combination of industry-leading feature flags, progressive rollouts, real-time observability, experimentation, and automatic recovery, LaunchDarkly gives organizations the ability to move at AI speed without giving up control. AgentControl helps teams keep AI agents in check in production, blocking bad behavior and steering responses in real time. Teams can configure prompts and models before launch, monitor and observe live performance and behavior, and automatically take action—without redeploying. When agents make curious decisions, or when small prompt or model changes cause big issues, AgentControl detects and corrects them as they happen. With runtime control across code and agents, LaunchDarkly helps enable teams to ship AI-built software with confidence, govern agent behavior in production, optimize AI performance and cost, build self-healing systems, and experiment continuously. The result is faster release velocity, lower production risk, and the ability to continuously adapt software and AI systems without slowing down to stay safer.

* * *

Product Website
LaunchDarkly
Seller
[LaunchDarkly](https://www.g2.com/sellers/launchdarkly)
Discussions
[LaunchDarkly Community](https://www.g2.com/products/launchdarkly/discuss)
Languages Supported

English

Solution Type

All-in-One

Overview by
Emily Coleman

Show More

## Pricing

Pricing provided by LaunchDarkly.

### Developer

$0.00

[
View More Pricing Information
](https://www.g2.com/products/launchdarkly/pricing)

## LaunchDarkly Integrations
(33)

What do users say about integrations?

Verified by LaunchDarkly

[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

Amazon Elastic Kubernetes Service (Amazon EKS)

](https://www.g2.com/products/amazon-elastic-kubernetes-service-amazon-eks/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

Amazon Kinesis Data Streams

](https://www.g2.com/products/aws-amazon-kinesis-data-streams/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

AWS Cloud9

](https://www.g2.com/products/aws-cloud9/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

AWS CloudTrail

](https://www.g2.com/products/aws-cloudtrail/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

AWS Lambda

](https://www.g2.com/products/aws-lambda/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

Azure Kubernetes Service (AKS)

](https://www.g2.com/products/azure-kubernetes-service-aks/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

BambooHR

](https://www.g2.com/products/bamboohr/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

Bitbucket

](https://www.g2.com/products/bitbucket/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

Claude

](https://www.g2.com/products/claude-2025-12-11/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

Claude Code

](https://www.g2.com/products/anthropic-claude-code/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

Confluence

](https://www.g2.com/products/confluence/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

Cursor

](https://www.g2.com/products/cursor/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

Datadog

](https://www.g2.com/products/datadog/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

Dynatrace

](https://www.g2.com/products/dynatrace/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

Express.js

](https://www.g2.com/products/express-js/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

GitHub

](https://www.g2.com/products/github/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

Google Kubernetes Engine (GKE)

](https://www.g2.com/products/google-kubernetes-engine-gke/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

Grafana Labs

](https://www.g2.com/products/grafana-labs/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

Honeycomb

](https://www.g2.com/products/honeycomb/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

Internal

](https://www.g2.com/products/internal/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

Jenkins

](https://www.g2.com/products/jenkins/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

Jira

](https://www.g2.com/products/jira/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

Linear

](https://www.g2.com/products/linear/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

MTECH Systems

](https://www.g2.com/products/mtech-systems/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

Next.js

](https://www.g2.com/products/next-js/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

Node.js

](https://www.g2.com/products/node-js/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

Procore

](https://www.g2.com/products/procore/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

Python

](https://www.g2.com/products/python/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

React Native

](https://www.g2.com/products/react-native/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

Slack

](https://www.g2.com/products/slack/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

Slack Connector for Jira

](https://www.g2.com/products/slack-connector-for-jira/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

Snowflake

](https://www.g2.com/products/snowflake/reviews)[

 ![Product Avatar Image](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Product Avatar Image")

TouchBistro Restaurant POS

](https://www.g2.com/products/touchbistro-restaurant-pos/reviews)

Show More

 ![Muhammed A.](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Muhammed A.")
MA

Muhammed A.

Technical Project Manager 

Information Technology and Services

Mid-Market (51-1000 emp.)

8/5/2026

"Safer Production Rollouts with Instant Feature Toggles and Precise Targeting"

4.5/5

What do you like best about LaunchDarkly?

LaunchDarkly has made it much safer to test new features in production by rolling them out to a small percentage of users first, rather than deploying changes to everyone at once. Being able to toggle features on or off instantly without redeploying code has sped up testing cycles significantly, especially when validating changes to trip flow or platform functionality before a full rollout. The targeting rules for controlling exactly who sees a given feature, whether by user segment or percentage, have made testing much more precise than relying on separate staging environments alone. The dashboard makes it easy to monitor flag status and adjust rollouts on the fly without needing a developer to make code changes for every adjustment. Review collected by and hosted on G2.com.

What do you dislike about LaunchDarkly?

Managing a growing number of feature flags over time requires discipline to clean up ones that are no longer needed, otherwise the codebase accumulates unnecessary complexity. Pricing scales with usage and seats, which can get expensive as the number of flags and monthly active users grows. The initial setup for integrating flags cleanly into existing code took some restructuring, especially for parts of the codebase that weren't originally built with feature flagging in mind. Some of the more advanced targeting and experimentation features have a learning curve before getting full value out of them. Review collected by and hosted on G2.com.

What problems is LaunchDarkly solving and how is that benefiting you?

LaunchDarkly has let us test new features on a small subset of real users before a full rollout, catching issues early without risking a broken experience for everyone on the platform. This has made deploying changes to core functionality, like trip flow updates, much safer, since we can instantly disable a feature if something goes wrong instead of needing an emergency rollback and redeploy. Review collected by and hosted on G2.com.

Show More

Response from Micaela Durkin of LaunchDarkly

[Editedit](https://www.g2.com/survey_responses/launchdarkly-review-13211989/official_response/edit)

Thank you for sharing such thoughtful feedback! We’re so glad LaunchDarkly has helped you roll out trip flow and platform changes more safely while reducing the need for emergency redeployments. For managing flag debt, we have a great guide to reducing technical debt from feature flags which offers best practices for flag cleanup and lifecycle management. I've shared the link below if it's helpful!

[See how LaunchDarkly improved](https://launchdarkly.com/docs/guides/flags/technical-debt)

Our network of Icons are G2 members who are recognized for their outstanding contributions and commitment to helping others through their expertise.G2 IconCurrent UserValidated ReviewerIncentivizedSource: G2 invite

 ![Johanna B.](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Johanna B.")
JB

Johanna B.

Team Lead, Customer Support

Mid-Market (51-1000 emp.)

7/27/2026

"Quick No-Code Changes using LaunchDarkly"

4.5/5

What do you like best about LaunchDarkly?

It's incredibly easy and straight-forward to use, even from a no/low-code perspective. I like how quickly it enables us to make changes in our platform. Review collected by and hosted on G2.com.

What do you dislike about LaunchDarkly?

When working within specific Flags in LaunchDarkly, I wish there was a way to bulk add or bulk remove targets. I've spent quite a bit of time adding a Flag for about 20 targets, which I feel like could be sped up. Review collected by and hosted on G2.com.

What problems is LaunchDarkly solving and how is that benefiting you?

For me specifically, leading our support team, I'm able to use it to activate a variety of banners across our platform, especially for notices and updates that need to go out in a timely manner. This allows us to get broader reach than spending out a mass email and tracking the emails down. We've been able to integrate with Claude projects as well, and are hoping to add additional automates to make it even faster and easier to use. Review collected by and hosted on G2.com.

Show More

Response from Micaela Durkin of LaunchDarkly

[Editedit](https://www.g2.com/survey_responses/launchdarkly-review-13171945/official_response/edit)

Thank you for sharing this, I love hearing your perspective from support and using LaunchDarkly for banner rollouts. It's great to hear how much easier it's made reaching your users compared to mass emails. On the target front, we actually do offer bulk editing within a flag's targeting tab, so you can add, remove, or replace multiple targets at once instead of one by one, I've shared the docs below if this is what you're looking for and is useful for your workflow!

[See how LaunchDarkly improved](https://launchdarkly.com/docs/home/flags/bulk-targeting)

Current UserValidated ReviewerIncentivizedSource: Seller invite

 ![Raj K.](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Raj K.")
RK

Raj K.

Senior Software Engineer

Mid-Market (51-1000 emp.)

7/9/2026

"Fantastic SDK Integrations and a Unified Workflow for Safe Deployments & Experimentation"

4.5/5

What do you like best about LaunchDarkly?

The SDK integrations are fantastic. LaunchDarkly collapsed two major headaches—safe deployments and structured experimentation—into a single, unified workflow. The compounding time savings and the confidence it gives our engineering and on-call teams are immense.

The context tracking and intuitive UI make it easy to manage who sees what. The ability to run A/B tests and progressively roll out new UI elements to specific user segments without engineering intervention is brilliant Review collected by and hosted on G2.com.

What do you dislike about LaunchDarkly?

There is definitely a learning curve for new team members when it comes to organizing and cleaning up flags. Once a project scales, managing multiple flags can become cluttered and performance could degrade if you don't stay on top of deprecation and maintenance Review collected by and hosted on G2.com.

What problems is LaunchDarkly solving and how is that benefiting you?

We primarily use it for continuous delivery and targeted rollouts. It allows us to test changes on small segments of real traffic before rolling them out widely. Rollbacks have become a simple toggle flip instead of a stressful, emergency fire drill Review collected by and hosted on G2.com.

Show More

Response from Micaela Durkin of LaunchDarkly

[Editedit](https://www.g2.com/survey_responses/launchdarkly-review-13086481/official_response/edit)

Thanks so much for sharing this we love hearing that rollbacks went from "fire drill" to a "simple toggle flip"! We're glad the SDKs and context targeting are helping your team ship confidently and experiment without engineering bottlenecks. LaunchDarkly Academy is a great resource for onboarding new team members which I've linked below, and we're also continuing to invest in making flag organization and cleanup more intuitive as projects grow.

[See how LaunchDarkly improved](https://academy.launchdarkly.com/)

Current UserValidated ReviewerIncentivizedSource: G2 invite

SP

Shruti P.

senior engineer

Mid-Market (51-1000 emp.)

6/29/2026

"Smarter Experimentation Nudges and Powerful Context Targeting"

4.5/5

What do you like best about LaunchDarkly?

Smarter experimentation features where it helps you identify which flags are worth A/B testing based on traffic patterns. As someone still learning the ropes, having the tool nudge me toward "hey, this flag has enough traffic to run a meaningful experiment" is genuinely helpful, I don't have to figure that out from scratch.

LD moved from Users to Contexts, meaning you can now target not just by user but by organization, device, session, or any custom entity. As a junior eng, this unlocked a lot for me. Review collected by and hosted on G2.com.

What do you dislike about LaunchDarkly?

the flag cleanup and archiving experience isn't great, stale flags pile up fast and there's no strong nudge to deprecate them. I've also hit moments where the dashboard felt slightly slow when loading large flag lists. Nothing that's blocked me, but there's room to tighten the performance and make flag hygiene easier. Review collected by and hosted on G2.com.

What problems is LaunchDarkly solving and how is that benefiting you?

The GitHub integration has been especially useful, I can see which flags are tied to open PRs and make sure nothing accidentally goes live before it's reviewed. It's made me a lot more confident shipping as a engineer. Review collected by and hosted on G2.com.

Show More

Response from Micaela Durkin of LaunchDarkly

[Editedit](https://www.g2.com/survey_responses/launchdarkly-review-13041707/official_response/edit)

Thank you for the thoughtful review! We’re so glad our experimentation insights, Contexts model, and GitHub integration are helping you ship with more confidence as you grow in your role. We also appreciate the candid feedback on flag cleanup and dashboard performance, and we’re continuing to improve both with feedback like this.

Current UserValidated ReviewerIncentivizedSource: Seller invite

 ![MOKSHI J.](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "MOKSHI J.")
MJ

MOKSHI J.

Senior Software Engineer

Mid-Market (51-1000 emp.)

8/7/2026

"Contexts Transformed Our Targeting and Rollouts"

4.5/5

What do you like best about LaunchDarkly?

The Contexts feature changed how we target. We went from basic user flags to targeting by company, subscription tier, and region, no application logic changes needed. Running 4-5 concurrent rollouts to different customer segments simultaneously would've taken 3 engineers and 4 months to build in-house. LD replaced that entirely. New engineers are shipping behind flags within their first week Review collected by and hosted on G2.com.

What do you dislike about LaunchDarkly?

SDK versioning across 20+ microservices is a real headache, had 2 incidents this year from inconsistent flag evaluation caused by outdated SDK versions across teams. Review collected by and hosted on G2.com.

What problems is LaunchDarkly solving and how is that benefiting you?

We run ~200 active flags in prod at any time. Kill switch response averages under 30 seconds when something goes wrong, that's not achievable with a homegrown solution at our scale. Saved us an estimated 12 engineer-months of build work. Review collected by and hosted on G2.com.

Show More

Response from Micaela Durkin of LaunchDarkly

[Editedit](https://www.g2.com/survey_responses/launchdarkly-review-13224474/official_response/edit)

Thank you for highlighting how Contexts have helped your team run more sophisticated rollouts and respond quickly when issues arise! It's also amazing to hear how using LaunchDarkly has translated to real engineering time saved. To your point on SDK versioning, we provide in-product SDK version notifications based on the SDKs used in each environment, along with guidance for updating and migrating, and I've linked the documentation below if it's helpful!

[See how LaunchDarkly improved](https://launchdarkly.com/docs/sdk/concepts/version-notifications)

Current UserValidated ReviewerIncentivizedSource: Seller invite

 ![RAJNIKANT J.](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "RAJNIKANT J.")
RJ

RAJNIKANT J.

Senior Software Engineer

Mid-Market (51-1000 emp.)

7/7/2026

"Controlled Rollouts That Help Us Catch Issues Early"

5/5

What do you like best about LaunchDarkly?

We use it for region specific rollout and for private beta release. Once we had a situation where a new dashboard feature caused confusion for a specific customer segment - we caught it at 8% rollout and pulled back before it became a support escalation. That kind of controlled exposure is genuinely hard to replicate otherwise. Review collected by and hosted on G2.com.

What do you dislike about LaunchDarkly?

It would be helpful if we could schedule when an approved flag should be applied. I’d also like a clean way to share a rollout summary with the customer success team without having to give them full dashboard access. Review collected by and hosted on G2.com.

What problems is LaunchDarkly solving and how is that benefiting you?

We now do account-level targeting for every major feature, specific customers get early access, give feedback, and we iterate before general availability. Our GA timelines have tightened by about 30% because we're not doing big reveal launches anymore, just gradual confident expansions. Review collected by and hosted on G2.com.

Show More

Response from Micaela Durkin of LaunchDarkly

[Editedit](https://www.g2.com/survey_responses/launchdarkly-review-13074602/official_response/edit)

Thank you so so much for the detailed feedback! We love hearing how percentage rollouts helped you catch that dashboard issue at 8% before it escalated, and that gradual rollouts have tightened your GA timelines by 30%. We hear you on wanting scheduled flag changes and an easier way to share rollout summaries, and we'd love to pass this along to our product team. Thanks for being a LaunchDarkly customer!

Current UserValidated ReviewerIncentivizedSource: Seller invite

 ![James L.](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "James L.")
JL

James L.

IT Specialist

Small-Business (50 or fewer emp.)

6/8/2026

"Clear Customer Journey Visibility with Powerful Filters and a Polished UI"

4.5/5

What do you like best about LaunchDarkly?

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. Review collected by and hosted on G2.com.

What do you dislike about LaunchDarkly?

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. Review collected by and hosted on G2.com.

What problems is LaunchDarkly 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. Review collected by and hosted on G2.com.

Show More

Response from Micaela Durkin of LaunchDarkly

[Editedit](https://www.g2.com/survey_responses/launchdarkly-review-12931617/official_response/edit)

Thank you so much for the thoughtful review! We’re glad LaunchDarkly is helping your team quickly investigate customer journey issues and find patterns across sessions. We also appreciate the candid feedback on session sharing and dashboard flexibility, and we’re sharing it with our product team as we continue improving how teams collaborate and work with their data.

Current UserValidated ReviewerIncentivizedSource: Seller invite

 ![Parth M.](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Parth M.")
PM

Parth M.

Senior Backend Engineer

Mid-Market (51-1000 emp.)

5/26/2026

"Operational agility at scale — deploys replaced by toggles"

4.5/5

What do you like best about LaunchDarkly?

UI / UX

Intuitive flag management: toggling, targeting rules by account/region, and scheduled rollouts work out of the box

Strong visibility — see active flags, their targets, and last-modified status at a glance

At 100+ flags across services, the UI gets noisy; we rely on naming conventions (rollout-\*, enable-\*, configure-\*) and project organization to stay navigable

Filtering and search are functional but underpowered for teams at our scale

Integrations

Clean integration with our Java backend via the Server SDK

Built a centralized wrapper service that all modules consume — no service talks to LD directly

DynamoDB persistent store ensures flags survive SDK restarts without re-fetching from LD cloud (critical for production reliability)

CI workflow auto-syncs code references on every push, keeping the LD dashboard aware of where each flag is actually used

Local development runs against a containerized LD dev server or plain YAML files — no live LD connection required

Performance

Core to how we operate our large-scale monorepo for real-time event ingestion and multi-channel engagement

128+ feature flags embedded across 229 files in the core pipeline

Shifted our workflow from "change code and deploy" to "toggle and observe"

For a platform processing millions of events in real time, this directly reduces incident blast radius and dropped events

Pricing / ROI

Each skipped config-change deploy saves 30–60 minutes of engineer time

~25 flag changes/month = 12–25 engineering hours saved on deploys alone

Runtime tuning (thread pools, processing limits, retry intervals) dropped from 2–4 hours per iteration to ~5 minutes

Incident math is the clincher: one kill-switch save of 30 minutes downtime on the real-time pipeline justifies the annual cost

Pricing scales with seats and flag evaluations — expensive at enterprise scale, but cheaper than the alternative (more deploys, longer incidents, slower rollouts)

Support / Onboarding

Low-friction onboarding thanks to our wrapper layer — engineers learn our internal API, not the LD SDK

Official LD documentation and SDK docs are solid

File-based mode for tests and a local dev server let new developers work with flags from day one without LD credentials

Upfront investment went into defining our targeting context model (infrastructure, account, custom attributes) — self-sustaining once established

AI / Intelligence

LLM Gateway uses a JSON flag to dynamically route accounts across AI model providers, with built-in regional compliance validation

A background worker polls a flag every minute to add/remove accounts from historic processing workflows

Flags control file-size limits per content type in our AI tooling layer

Net effect: a control plane for inherently experimental AI features — model swaps, threshold tuning, per-account gating — without code deploys Review collected by and hosted on G2.com.

What do you dislike about LaunchDarkly?

UI / UX

While lifecycle stages and archival suggestions exist, once you get to 100+ flags the dashboard still lacks service- or team-based grouping. Naming conventions end up being the main organizational tool. Native folders or tag-based grouping by service would lower cognitive overhead.

The targeting rule builder becomes unwieldy with complex, multi-context rules (infrastructure + account + custom attributes). Managing nested conditions is cumbersome for power users.

Flag search and filtering are fine at small-to-mid scale, but at enterprise flag volumes, bulk operations and cross-project visibility feel limited.

Integrations

The DynamoDB persistent store has a hard 400KB per-item limit. Flags that exceed this are silently skipped with only an ERROR log, with no proactive alerting or dashboard visibility.

On cold start with a persistent store, the SDK serves last-known (potentially stale) flag data and is technically “not initialized” until streaming reconnects. For kill switches or processing limits, that stale-default window is operationally risky.

Local-to-production flag parity is still a manual discipline. File-based local configs can drift from production state and create environment mismatches.

Performance

Streaming connections can drop in containerized environments behind load balancers due to network timeouts. The SDK does auto-reconnect and exposes status listeners (DataSourceStatusProvider), but the reconnection window still creates brief stale-flag exposure under load.

For high-throughput services evaluating flags on every request, evaluation overhead compounds. The SDK doesn’t provide built-in per-flag evaluation latency metrics, so teams have to instrument this themselves.

Cold-start hydration from DynamoDB is slower than in-memory. During this window, flags fall back to coded defaults, which can cause unexpected behavior for critical operational flags.

Pricing / ROI

~~Seat-based pricing doesn't differentiate roles~~ — corrected: LD now offers unlimited seats on Developer and Foundation tiers. However, usage-based pricing (service connections, MAUs) can be hard to predict for high-throughput platforms. Better cost-forecasting tools within LD would help.

Enterprise and Guardian tier pricing is fully custom with no published benchmarks, which makes it difficult to budget or compare without a sales conversation.

Evaluation volume costs are opaque at scale. There’s no self-serve way to model, “If we add X more flags across Y services, what’s the cost impact?”

Support / Onboarding

Documentation covers the basics well, but advanced patterns (multi-context targeting design, persistent store tuning, high-throughput optimization) are scattered across blog posts, support articles, and GitHub issues instead of being consolidated in one place.

For production incidents involving SDK streaming behavior or cache inconsistencies, troubleshooting requires correlating SDK status listeners, DynamoDB state, and network logs. A unified diagnostics view would speed resolution.

There are no published reference architectures for high-throughput event platforms. Teams designing targeting context models at scale are largely self-guided.

AI / Intelligence

LD launched AI Experiments, AI Versioning, and AI Configs (GA May 2025) — a significant step forward. However, compliance-aware model routing (ensuring data doesn’t flow to disallowed regions) is still custom logic that teams must build themselves.

Feedback-loop-driven flag decisions (tying flag choices to downstream quality metrics automatically) aren’t natively supported. Experimentation still requires manual metric setup rather than closed-loop optimization.

For teams already managing AI features via plain JSON flags (model overrides, prompt configs), the migration path to the new AI Configs feature isn’t well documented. Review collected by and hosted on G2.com.

What problems is LaunchDarkly solving and how is that benefiting you?

Before LaunchDarkly, every configuration change or feature toggle required a full deploy cycle—30–60 minutes minimum in a large monorepo. Incident response meant writing a fix, getting it reviewed, building, and deploying, which easily took 1–4 hours while the issue continued impacting users. Rollouts were all-or-nothing, and per-customer feature management often meant hardcoded account lists living in the code.

Since adopting LaunchDarkly, incident response has gone from hours to seconds. Kill-switch flags let us disable a broken feature immediately instead of waiting for a full deploy. For a real-time event pipeline, that difference can prevent significant data loss during outages.

We can also tune configuration without deploys. Thread pools, processing limits, and retry intervals are now managed via flags. A tuning cycle that used to take 2–4 hours per iteration (change → deploy → observe) now takes about 5 minutes.

Progressive rollouts have replaced the old all-or-nothing approach. We can ship to 1% of accounts first, and if a bug is caught at 5% rollout, it affects 20x fewer users—dramatically reducing support escalations.

Per-customer targeting no longer requires code changes. Enabling features for specific accounts used to mean a PR plus a deploy; now it’s just a flag rule change, saving dozens of engineering hours across 30+ account-targeted flags.

Finally, teams can ship more independently. Code can merge behind disabled flags, and PMs can toggle features when they’re ready. That has eliminated long-lived branches, reduced merge conflicts, and removed a lot of release-day coordination across teams. Review collected by and hosted on G2.com.

Show More

Response from Micaela Durkin of LaunchDarkly

[Editedit](https://www.g2.com/survey_responses/launchdarkly-review-12870973/official_response/edit)

Thank you for the detailed review! We’re glad LaunchDarkly is helping your team manage rollouts, operational tuning, and AI-driven workflows with more speed, control, and less risk in a high-throughput environment. We also appreciate the candid feedback—this helps shape where we continue to invest. We’re also expanding this area with AgentControl, which helps teams govern AI agents in production, continuously evaluate prompts and models, and respond to drift or performance issues without redeploying. I've linked the documentation below!

[See how LaunchDarkly improved](https://launchdarkly.com/docs/home/agentcontrol)

Current UserValidated ReviewerIncentivizedSource: Seller invite

 ![Shubham C.](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Shubham C.")
SC

Shubham C.

Senior Frontend Engineer

Mid-Market (51-1000 emp.)

5/26/2026

"Intuitive UI, Powerful Integrations, and Low-Latency Feature Flagging"

4.5/5

What do you like best about LaunchDarkly?

The UI is genuinely well thought out. Managing flags, setting up targeting rules, and navigating environments never feels overwhelming — everything is where you'd expect it to be. For a tool that can get complex quickly, it stays remarkably approachable even as your flag count grows.

The integrations are where it really shines for day-to-day engineering work. It plugs into pretty much everything — your CI/CD pipeline, Slack, DataDog, Jira — so flag activity doesn't live in isolation. You get context right where you already work, which makes it much easier to correlate a rollout with a spike in errors or a support ticket.

And performance-wise, the SDKs are built with latency in mind. Flag evaluations happen locally after the initial sync, so you're not making a network call every time a flag is checked. For a frontend-heavy application where you might be evaluating flags on every render or route change, that matters a lot. The streaming updates also mean flag changes propagate almost instantly without you having to poll or refresh anything. Review collected by and hosted on G2.com.

What do you dislike about LaunchDarkly?

The onboarding process for this tool is very confusing, especially for something that is supposed to be simple to use and meant to help others simplify processes. Sure, adding the SDK is simple. But the trick is figuring out how to appropriately set up and organize your environments, your projects, and your contexts. This process is tricky to say the least, and it fails to cover the why in the explanation of the architecture, if it covers it at all. Support is available, but it is more of a last resort, as help is only given slowly and at great length when asked.

Their AI is impressive but still has more room for development and improvement. They talk a lot about data driven rollouts, but the only data when using the platform is very base data, which is rather disappointing. For a platform that holds so much behavioral data, it seems like a large miss to not have the platform offer suggestions for smarter data based decisions. Suggestions like setting automatic thresholds for rollout based on historical data or flagging outdated rolling data are all things the platform could be doing and are not. Review collected by and hosted on G2.com.

What problems is LaunchDarkly solving and how is that benefiting you?

Before LaunchDarkly, every production release was an all-or-nothing event. If something broke, we were either rolling back the entire deployment or pushing a hotfix under pressure. Over time, that made our team risk-averse — we'd delay shipping, over-bundle changes, and still dread release day. On top of that, any kind of A/B testing was a separate, heavyweight process that required coordinating with the data team, setting up custom tooling, and waiting weeks before we had anything conclusive.

We struggled with both the all-or-nothing nature of deployments and the lack of a lightweight experimentation workflow, but now we can decouple releases from deployments and run A/B tests directly within the same flag infrastructure. This has resulted in two compounding benefits — faster, safer rollouts and data-backed feature decisions without needing a separate experimentation platform.

On the deployment side, catching critical issues now happens within the first hour of a limited rollout rather than days later. Incident response time has dropped from a stressful 2–3-hour process to under 15 minutes in most cases. On the experimentation side, we've gone from running maybe one or two A/B tests a quarter to running them continuously — testing copy changes, UI variations, and new feature flows with real user segments without any additional infrastructure overhead.

The biggest shift is cultural. The team no longer treats releasing as a risky event or experimentation as a big project. Both are now just part of how we ship.

LaunchDarkly collapsed two separate problems — safe deployments and structured experimentation — into a single workflow, and the compounded time savings and confidence gains have been significant. Review collected by and hosted on G2.com.

Show More

Response from Micaela Durkin of LaunchDarkly

[Editedit](https://www.g2.com/survey_responses/launchdarkly-review-12870341/official_response/edit)

Thank you for sharing such a thoughtful review! We’re so glad LaunchDarkly is helping your team ship more safely and experiment with confidence. We also appreciate the candid feedback on onboarding, and for anyone getting started, LaunchDarkly Academy offers great guided training and resources to help teams ramp up faster. I included the link below.

[See how LaunchDarkly improved](https://academy.launchdarkly.com/)

Current UserValidated ReviewerIncentivizedSource: Seller invite

 ![Yashdeep S.](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Yashdeep S.")
YS

Yashdeep S.

Staff Engineer DevOps

Mid-Market (51-1000 emp.)

5/22/2026

"Precise Feature Rollouts and Instant Kill Switches with LaunchDarkly"

5/5

What do you like best about LaunchDarkly?

LaunchDarkly gives us precise control over feature rollouts without requiring new deployments. The per-account targeting rules are especially valuable for enterprise software — we can enable beta features for specific customers, run gradual rollouts, and kill-switch anything gone wrong instantly. The audit trail also helps during incidents: we can quickly see if a recent flag change correlates with a problem. Review collected by and hosted on G2.com.

What do you dislike about LaunchDarkly?

The main friction point is flag hygiene — LaunchDarkly makes it easy to create flags but doesn't enforce a lifecycle. Stale flags accumulate and become invisible tech debt. Pricing can also be a concern at scale, especially for high-MAU B2C products. We'd love better built-in tooling for flag retirement workflows and technical debt tracking Review collected by and hosted on G2.com.

What problems is LaunchDarkly solving and how is that benefiting you?

LaunchDarkly solves the core problem of separating code deployment from feature release. For a multi-tenant B2B platform, this is essential — we can ship code continuously and control exactly which accounts see which features. It's also eliminated an entire class of hotfix deploys: production issues caused by a new feature are now resolved in seconds by toggling a flag rather than going through a full release cycle. The visibility it gives to non-engineering teams (support, TAMs) has also reduced internal back-and-forth on 'is feature X enabled for customer Y. Review collected by and hosted on G2.com.

Show More

5/26/2026
Current UserValidated ReviewerIncentivizedSource: Seller invite

## Questions about LaunchDarkly? Ask real users or explore answers from the community

Get practical answers, real workflows, and honest pros and cons from the G2 community or share your insights.

[
Ask about LaunchDarkly
](https://www.g2.com/products/launchdarkly/discussions/new)

GU

Guest User
•
Last activity over 2 years ago

How do I use LaunchDarkly?

0 Upvotes

1

[
Join the conversation
](https://www.g2.com/discussions/how-do-i-use-launchdarkly)

GU

Guest User
•
Last activity over 2 years ago

What is LaunchDarkly used for?

0 Upvotes

1

[
Join the conversation
](https://www.g2.com/discussions/what-is-launchdarkly-used-for)

[
View all Discussions
](https://www.g2.com/products/launchdarkly/discuss)

## Pricing Options

Pricing provided by LaunchDarkly.

### Developer

$0.00

### Foundation

$12.00

Per Month

### Enterprise

Contact Us

[
View More Pricing Information
](https://www.g2.com/products/launchdarkly/pricing)

LaunchDarkly Comparisons

 ![Product Avatar Image](https://images.g2crowd.com/uploads/product/image/small_square/small_square_c73a6cc10ab731dbf2a60faddcd17402/optimizely-web-experimentation.png "Product Avatar Image")

Optimizely Web Experimentation

4.2/5(411)

[
Compare Now
](https://www.g2.com/compare/launchdarkly-vs-optimizely-web-experimentation)

 ![Product Avatar Image](https://images.g2crowd.com/uploads/product/image/small_square/small_square_b4891cf5174ea2e62915eea6047768f5/unleash.png "Product Avatar Image")

Unleash

4.7/5(134)

[
Compare Now
](https://www.g2.com/compare/launchdarkly-vs-unleash)

 ![Product Avatar Image](https://images.g2crowd.com/uploads/product/image/small_square/small_square_24d73c218b91bf58ac8c262bc79b8f39/configcat.jpg "Product Avatar Image")

ConfigCat

4.6/5(40)

[
Compare Now
](https://www.g2.com/compare/configcat-vs-launchdarkly)

##### 
##### LaunchDarkly Features

Functionality

Deployment-Ready Staging

Integration

Extensible

Management

Processes and Workflow

Reporting

Automation

Analytics

Reporting and Analytics

Experimental Design

Multivariate testing capacities

Split Testing

[
View More Features
](https://www.g2.com/products/launchdarkly/features)

## Top-Rated Alternatives

[

 ![PostHog](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "PostHog")

PostHog

4.5/5(1,054)

](https://www.g2.com/products/posthog/reviews)

[

 ![Statsig](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Statsig")

Statsig

4.7/5(347)

](https://www.g2.com/products/statsig/reviews)

[

 ![Optimizely Web Experimentation](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Optimizely Web Experimentation")

Optimizely Web Experimentation

4.2/5(411)

](https://www.g2.com/products/optimizely-web-experimentation/reviews)

[
View All Alternatives
](https://www.g2.com/products/launchdarkly/competitors/alternatives)

##### Categories on G2

[Bug Tracking](https://www.g2.com/categories/bug-tracking)[Mobile App Analytics](https://www.g2.com/categories/mobile-app-analytics)[Product Analytics](https://www.g2.com/categories/product-analytics)

[Bug Tracking](https://www.g2.com/categories/bug-tracking)[Mobile App Analytics](https://www.g2.com/categories/mobile-app-analytics)[Product Analytics](https://www.g2.com/categories/product-analytics)[AI Orchestration](https://www.g2.com/categories/ai-orchestration)[A/B Testing](https://www.g2.com/categories/a-b-testing-tools)[Session Replay](https://www.g2.com/categories/session-replay)[Application Performance Monitoring (APM)](https://www.g2.com/categories/application-performance-monitoring-apm)[Observability Software](https://www.g2.com/categories/observability-software)[Continuous Delivery](https://www.g2.com/categories/continuous-delivery-tools)[Log Monitoring](https://www.g2.com/categories/log-monitoring)[Feature Management](https://www.g2.com/categories/feature-management)[Large Language Model Operationalization (LLMOps)](https://www.g2.com/categories/large-language-model-operationalization-llmops)[Prompt Management Tools](https://www.g2.com/categories/prompt-management-tools)

[Show MoreShow Less](javascript:void(0);)

##### Explore More

[Top-rated tools for certification and compliance assessments](https://www.g2.com/discussions/top-rated-tools-for-certification-and-compliance-assessments)[Is Alteryx designed to support non-technical users like business analysts, operations teams, and marketers who need self-service analytics?](https://www.g2.com/discussions/is-alteryx-designed-to-support-non-technical-users-like-business-analysts-operations-teams-and-marketers-who-need-self-service-analytics)[Which cloud security monitoring platforms work best for a fintech or healthcare company that has strict regulatory requirements around cloud data and audit trails?](https://www.g2.com/discussions/which-cloud-security-monitoring-platforms-work-best-for-a-fintech-or-healthcare-company-that-has-strict-regulatory-requirements-around-cloud-data-and-audit-trails)

[Which CCM platform is the most user-friendly for startups](https://www.g2.com/discussions/which-ccm-platform-is-the-most-user-friendly-for-startups)[What are some recruiting and interview scheduling software with AI-powered candidate screening for field sales software hiring?](https://www.g2.com/discussions/what-are-some-recruiting-and-interview-scheduling-software-with-ai-powered-candidate-screening-for-field-sales-software-hiring)[Pros and Cons Details](https://www.g2.com/products/launchdarkly/reviews?qs=pros-and-cons)

[Show MoreShow Less](javascript:void(0);)