Skip to content
ProductArena

Rank #4 of 5 in Feature Flags & Experimentation

LaunchDarkly logo

LaunchDarkly

LaunchDarkly (Catamorphic Co.) · commercial

launchdarkly.com ↗Try it →
PA Score32/100AGENT-READY66/100BUILT-IN AI22/100API10/100
MCP✓CLI✓API✓
npm 1.8M/wknpm/wk -803.5k
ArenasFeature Flags & Experimentation#4/5

Access

Open app ↗API docs ↗CLI docs ↗MCP docs ↗

Install

brewbrew tap launchdarkly/homebrew-tap && brew install ldcli
npmnpm install @launchdarkly/node-server-sdk
mcpnpx -y @launchdarkly/mcp-server start

Compare head-to-head

Statsig logovs StatsigGrowthBook logovs GrowthBookFlagsmith logovs FlagsmithUnleash logovs Unleash

Alternatives to LaunchDarkly →

Showcase

LaunchDarkly homepage screenshot
homepage · captured Sep 2026 · view live ↗
LaunchDarkly docs screenshot
docs · captured Sep 2026 · view live ↗

Try itExperimental

See what an agent can do with LaunchDarkly before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).

$ldcli --version # installed via `brew tap launchdarkly/homebrew-tap && brew install ldcli`recorded session — replayed, not live
recorded 2026-09-05 · exit 0 · captured verbatim by our probe harness, secrets redacted

Verified integrations

Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.

Sentry logoSentryObservability & MonitoringSlack logoSlackTeam Chat

By theme — the product's score on each story themeBy theme

Agenticness — how well agents can access and operate the productAgenticnessevidence →

How well agents can access and operate the product

43.0/100

Automation depth — how much of the product can run unattendedAutomation depthevidence →

How much of the product can run unattended

37.5/100

Deployment self host — stories about deployment self host in this arenaDeployment self hostevidence →

Stories about deployment self host in this arena

20.0/100

Experimentation — stories about experimentation in this arenaExperimentationevidence →

Stories about experimentation in this arena

42.8/100

Flag management — stories about flag management in this arenaFlag managementevidence →

Stories about flag management in this arena

68.0/100

Governance audit — stories about governance audit in this arenaGovernance auditevidence →

Stories about governance audit in this arena

65.3/100

Openness — open source, data portability, and self-hosting storiesOpennessevidence →

Open source, data portability, and self-hosting stories

6.0/100

Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plansevidence →

Plan structure and value — what each tier costs and what it unlocks

36.0/100

Privacy posture — data-handling and privacy storiesPrivacy postureevidence →

Data-handling and privacy stories

0.0/100

Rollouts releases — stories about rollouts releases in this arenaRollouts releasesevidence →

Stories about rollouts releases in this arena

72.0/100

Sdk delivery — stories about sdk delivery in this arenaSdk deliveryevidence →

Stories about sdk delivery in this arena

64.8/100

Story verdicts — every judged story with its evidenceStory verdicts

?

Sorted by importance (agentic first) (high → low) · 54/54 stories · click a row’s chevron for the rationale and evidence

Connect an agent via an official MCP server G

Agent access

ai-native userAgenticness — how well agents can access and operate the productAgenticness3full9/10T

Drive the product through a documented public API G

Agent access

ai-native userAgenticness — how well agents can access and operate the productAgenticness3full7/10T

Delegate tasks to a built-in AI assistant inside the product G

Agentic features

ai-native userAgenticness — how well agents can access and operate the productAgenticness3none0/10

Plug MCP servers into this product so it can use their tools G

Agent access

ai-native userAgenticness — how well agents can access and operate the productAgenticness3n/auntestednone yet

Use an official CLI G

Agent access

ai-native userAgenticness — how well agents can access and operate the productAgenticness2full9/10T

Build against official SDKs G

Agent access

ai-native userAgenticness — how well agents can access and operate the productAgenticness2full8/10T

Subscribe to events via webhooks G

Agent access

ai-native userAgenticness — how well agents can access and operate the productAgenticness2full8/10C

Operate the product with natural-language commands G

Agentic features

ai-native userAgenticness — how well agents can access and operate the productAgenticness2full7/10T

Run the product headlessly / in CI for automation G

Agent access

ai-native userAgenticness — how well agents can access and operate the productAgenticness2full7/10T

Issue scoped/least-privilege API credentials for an agent G

Agent access

ai-native userAgenticness — how well agents can access and operate the productAgenticness2partial6/10T

Set up automations that run autonomously in the background G

Agentic features

ai-native userAgenticness — how well agents can access and operate the productAgenticness2partial5/10T

Download a machine-readable API spec (OpenAPI or equivalent) G

Api quality

ai-native userAgenticness — how well agents can access and operate the productAgenticness2none0/10

Explore an interactive API reference with runnable examples G

Api quality

ai-native userAgenticness — how well agents can access and operate the productAgenticness2none0/10

Get AI-generated insights and suggestions from my data inside the product G

Agentic features

ai-native userAgenticness — how well agents can access and operate the productAgenticness2none0/10

Point an agent at llms.txt or agent-oriented docs G

Agent access

ai-native userAgenticness — how well agents can access and operate the productAgenticness2none0/10

Rely on versioned APIs with a documented deprecation policy G

Api quality

ai-native userAgenticness — how well agents can access and operate the productAgenticness2none0/10

Test against a sandbox environment without touching production data G

Api quality

ai-native userAgenticness — how well agents can access and operate the productAgenticness1full7/10C

Roll a flag out progressively by percentage with consistent bucketing, ramping from 1% to 100% without redeploying C

Rollouts

developerRollouts releases — stories about rollouts releases in this arenaRollouts releases3full9/10X

Target flags with attribute-based rules and reusable segments so the right users see the right variation C

Targeting

developerFlag management — stories about flag management in this arenaFlag management3full9/10X

Require approvals or change requests before production flag changes go live C

Approvals

platform engineerGovernance audit — stories about governance audit in this arenaGovernance audit3full8/10C

Run A/B and multivariate experiments on flags and see which variation wins on my metrics C

Experiments

product managerExperimentation — stories about experimentation in this arenaExperimentation3full8/10X

Create a feature flag and toggle it live in production within minutes of signing up C

Flags

developerFlag management — stories about flag management in this arenaFlag management3full7/10X

Create and toggle flags through documented APIs, CLIs, or MCP — and the platform can force my changes through approval workflows instead of letting me write to production unreviewed C

Agent ops

ai agentGovernance audit — stories about governance audit in this arenaGovernance audit3full7/10T

Define rules that trigger actions automatically on events G

ai-native userAutomation depth — how much of the product can run unattendedAutomation depth3full7/10C

Every flag change is recorded in an audit log — who changed what, when, and to which value G

Audit

platform engineerGovernance audit — stories about governance audit in this arenaGovernance audit3partial6/10X

My server SDKs evaluate flags locally from a cached ruleset — microsecond decisions with no network call per flag check C

Evaluation

platform engineerSdk delivery — stories about sdk delivery in this arenaSdk delivery3partial6/10X

Export all of my data in open formats and leave G

ai-native userOpenness — open source, data portability, and self-hosting storiesOpenness3none0/10

Self-host the core product G

ai-native userOpenness — open source, data portability, and self-hosting storiesOpenness3none0/10

Self-host the full flag platform from an open-source distribution, keeping evaluation data on my infrastructure C

Self host

platform engineerDeployment self host — stories about deployment self host in this arenaDeployment self host3none0/10

Prevent my data from being used to train AI models G

ai-native userPrivacy posture — data-handling and privacy storiesPrivacy posture3n/auntestednone yet

Manage separate environments (dev/staging/prod) with independent flag states and scoped SDK keys C

Environments

developerFlag management — stories about flag management in this arenaFlag management2full9/10X

Evaluate flags at the edge (CDN workers or an edge/relay layer) close to users C

Edge

platform engineerSdk delivery — stories about sdk delivery in this arenaSdk delivery2full8/10X

Restrict who can change which flags with roles, permissions, and scoped API tokens C

Access

platform engineerGovernance audit — stories about governance audit in this arenaGovernance audit2full8/10C

Use official SDKs across my whole stack — backend, web, and mobile — with consistent flag behavior C

Sdks

developerSdk delivery — stories about sdk delivery in this arenaSdk delivery2full8/10X

Flag changes propagate to connected SDKs in seconds via streaming or fast polling — a kill switch actually kills C

Streaming

developerSdk delivery — stories about sdk delivery in this arenaSdk delivery2full7/10X

Find stale flags and code references so temporary flags actually get removed from the codebase C

Lifecycle

platform engineerFlag management — stories about flag management in this arenaFlag management2partial6/10X

Guard a rollout with metrics so a regression is detected and the release is rolled back automatically C

Rollouts

platform engineerRollouts releases — stories about rollouts releases in this arenaRollouts releases2partial6/10C

See published pricing and understand what drives cost (seats, MAUs, events, requests) before committing G

Pricing

product managerPricing plans — plan structure and value — what each tier costs and what it unlocksPricing plans2partial6/10X

Serve multivariate flags and dynamic configuration values (strings, numbers, JSON), not just booleans C

Flags

developerFlag management — stories about flag management in this arenaFlag management2partial6/10X

Trust a documented statistics engine (Bayesian or frequentist, with variance-reduction options) behind experiment results C

Analysis

product managerExperimentation — stories about experimentation in this arenaExperimentation2partial6/10C

Do everything through the API that I can do in the UI G

ai-native userOpenness — open source, data portability, and self-hosting storiesOpenness2partial5/10T

Perform bulk operations across many items at once G

ai-native userAutomation depth — how much of the product can run unattendedAutomation depth2partial5/10T

Choose where my data is stored (region/residency) G

ai-native userPrivacy posture — data-handling and privacy storiesPrivacy posture2none0/10

Define experiment metrics from my own data — warehouse tables or ingested events — instead of a black-box metric store C

Metrics

product managerExperimentation — stories about experimentation in this arenaExperimentation2none0/10

Read the product's source under an open license G

ai-native userOpenness — open source, data portability, and self-hosting storiesOpenness2none0/10

Schedule recurring jobs or workflows G

ai-native userAutomation depth — how much of the product can run unattendedAutomation depth2none0/10

Control data retention and deletion G

ai-native userPrivacy posture — data-handling and privacy storiesPrivacy posture2noneuntestednone yet

Opt out of telemetry and usage tracking G

ai-native userPrivacy posture — data-handling and privacy storiesPrivacy posture2noneuntestednone yet

Schedule flag changes and releases to happen at a specific future time C

Scheduling

developerRollouts releases — stories about rollouts releases in this arenaRollouts releases1full9/10C

Run a relay/edge proxy so flags stay served when the vendor is unreachable and SDK traffic stays inside my network C

Proxy

platform engineerDeployment self host — stories about deployment self host in this arenaDeployment self host1full8/10X

Target or exclude specific individual users for a flag (allowlists, beta testers, internal accounts) C

Targeting

developerFlag management — stories about flag management in this arenaFlag management1full8/10X

Use the vendor through OpenFeature providers so my flag code isn't locked to one vendor's SDK API C

Standards

platform engineerSdk delivery — stories about sdk delivery in this arenaSdk delivery1full8/10C

Read experiment configurations and results programmatically to summarize outcomes and recommend ship/rollback decisions C

Agent ops

ai agentExperimentation — stories about experimentation in this arenaExperimentation1partial5/10T

Version, review, and roll back my automations G

ai-native userAutomation depth — how much of the product can run unattendedAutomation depth1partial5/10C

Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 28 stories with headroom

What would move LaunchDarkly’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.

  1. Agenticness — how well agents can access and operate the productDelegate tasks to a built-in AI assistant inside the product

    nonemoves Built-in AIimpact 45

    LaunchDarkly's evidence shows AI-related feature-flag tooling (AI Runs, LLM evaluation flags) and an MCP server that lets external AI agents call into LaunchDarkly as a tool provider, but there is no evidence of a built-in AI assistant inside the product itself that a user can delegate tasks to.

  2. Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave

    nonemoves PA Scoreimpact 30

    LaunchDarkly offers API access tokens and a CLI (ldcli) that could programmatically read flag/segment configurations, but no evidence pack item documents a dedicated bulk data-export feature, an open-format export tool, or a stated data-portability/exit policy for account data.

  3. Openness — open source, data portability, and self-hosting storiesSelf-host the core product

    nonemoves PA Scoreimpact 30

    LaunchDarkly is a hosted SaaS platform; the only self-hostable component is the Relay Proxy, a caching/streaming layer that still depends on the LaunchDarkly SaaS control plane for flag configuration, not the core product itself.

  4. Deployment self host — stories about deployment self host in this arenaSelf-host the full flag platform from an open-source distribution, keeping evaluation data on my infrastructure

    nonemoves PA Scoreimpact 30

    LaunchDarkly's evidence only describes an open-source Relay Proxy that caches/streams flag data from the LaunchDarkly cloud for resiliency and low latency, not a full self-hostable flag-management platform; the control plane, rules engine, and dashboard remain SaaS-hosted, and community comments explicitly flag this as a third-party critical-path dependency rather than a self-hosted deployment (launchdarkly-docs-13, launchdarkly-comm-2, launchdarkly-comm-6).

  5. Agenticness — how well agents can access and operate the productPoint an agent at llms.txt or agent-oriented docs

    nonemoves agent-readyimpact 30

    Direct probes show llms.txt and docs.md both return 404, and no evidence of any agent-oriented documentation endpoint; while LaunchDarkly ships an MCP server and CLI, these do not satisfy the specific 'llms.txt or agent-oriented docs' story.

  6. Agenticness — how well agents can access and operate the productGet AI-generated insights and suggestions from my data inside the product

    nonemoves Built-in AIimpact 30

    The evidence shows LaunchDarkly's AI-related features (AI Configs, 'AI Runs', LLM-as-judge evals) are about managing and evaluating AI/LLM application behavior via flags, not about the product itself surfacing AI-generated insights or suggestions from a user's flag/experiment/metrics data.

  7. Agenticness — how well agents can access and operate the productExplore an interactive API reference with runnable examples

    nonemoves API qualityimpact 30

    The evidence pack shows only static docs pages and confirms no OpenAPI/swagger spec discoverable (probe-3 all 404s) and no llms.txt/docs.md; nothing indicates an interactive, runnable API reference/playground exists.

  8. Agenticness — how well agents can access and operate the productDownload a machine-readable API spec (OpenAPI or equivalent)

    nonemoves API qualityimpact 30

    The evidence pack shows explicit probes for an OpenAPI/swagger spec at LaunchDarkly's standard candidate paths all returning 404, and no other citation surfaces a downloadable machine-readable API spec (only human-readable API access token docs are referenced).

Showing the top 8 of 28 — every none/partial verdict in the story verdicts table is headroom.

Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.

Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map4 surfaces · 37 covered stories

Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.

docs36 stories

Hacker News15 stories

Pricing docs7 stories

OpenAPI spec2 stories

Probe proofs — replayable recordings from the probe harnessProbe proofs

Replayable recordings from our probe harness — see the Prove-It protocol to submit one.

$ldcli --version # installed via `brew tap launchdarkly/homebrew-tap && brew install ldcli`reproduced
$ ldcli --version  # installed via `brew tap launchdarkly/homebrew-tap && brew install ldcli`
ldcli version 3.11.0
proves: Use an official CLIrecorded 2026-09-05
$curl -si -X POST https://mcp.launchdarkly.com/mcp/launchdarkly -H 'Content-Type: application/json' -d '<jsonrpc initialize>'reproduced
$ curl -si -X POST https://mcp.launchdarkly.com/mcp/launchdarkly -H 'Content-Type: application/json' -d '<jsonrpc initialize>'
HTTP/2 401

date: Sat, 05 Sep 2026 05:00:59 GMT

content-type: application/json

content-length: 81

access-control-allow-credentials: true

access-control-allow-headers: Accept, Content-Type, Content-Length, Accept-Encoding, Authorization, User-Agent, Gram-Session, Gram-Project, Gram-[redacted], Gram-[redacted], idempotency-[redacted], Gram-Admin-Override, Gram-Chat-ID, Gram-Assistant-ID, Gram-Chat-Session, MCP-Protocol-Version, Mcp-Method, Mcp-Name, Mcp-Session-Id, X-Gram-Scope-Override, X-Gram-Source

access-control-allow-methods: POST, GET, OPTIONS, PUT, DELETE

access-control-allow-origin: https://app.getgram.ai

access-control-expose-headers: Accept, Content-Type, Content-Length, Accept-Encoding, x-trace-id, Gram-Session, Gram-Chat-ID, Gram-Chat-Session, Mcp-Session-Id

mcp-session-id: e95fa55c-7f4e-422f-9a5d-3efe7d34cffc

www-authenticate: Bearer resource_metadata="https://mcp.launchdarkly.com/.well-known/oauth-protected-resource/mcp/launchdarkly"

x-request-id: f8e7c64866e956b96616ddf413214425

x-trace-id: 0cee9fca19143252ada73ae6e3c75694

strict-transport-security: max-age=31536000; includeSubDomains

content-security-policy: base-uri 'none'; connect-src 'self' https://api.github.com https://metrics.speakeasy.com https://browser-intake-datadoghq.com https://*.usepylon.com wss://*.pusher.com https://*.pusher.com https://*.posthog.com https://chat.speakeasy.com https://chat.dev.speakeasy.com https://app.getgram.ai https://dev.getgram.ai https://cdn.prod.getgram.ai https://cdn.dev.getgram.ai https://app.cal.com https://storage.googleapis.com https://*.clairedefermat.com; default-src 'self'; font-src 'self' https://*.getgram.ai https://fonts.googleapis.com https://fonts.gstatic.com https://*.usepylon.com https://*.posthog.com; frame-ancestors 'self'; frame-src 'self' https://polar.sh https://*.polar.sh https://app.svix.com https://app.cal.com https://cal.com; img-src 'self' blob: https: android-webview-video-poster: data:; media-src 'self' https://*.posthog.com; object-src 'none'; script-src 'self' 'wasm-unsafe-eval' https://www.datadoghq-browser-agent.com https://metrics.speakeasy.com https://widget.usepylon.com https://*.posthog.com https://*.getgram.ai https://app.cal.com https://*.clairedefermat.com; style-src 'self' 'unsafe-inline' https://*.getgram.ai https://fonts.googleapis.com https://*.usepylon.com https://*.posthog.com; worker-src 'self' blob:; report-to browser-intake-datadoghq

permissions-policy: fullscreen=(), compute-pressure=(), camera=(), microphone=(self), geolocation=(), accelerometer=(), bluetooth=(), gyroscope=(), payment=(), usb=(), midi=(), magnetometer=()

referrer-policy: strict-origin-when-cross-origin

reporting-endpoints: browser-intake-datadoghq="https://browser-intake-datadoghq.com/api/v2/logs?dd-[redacted]

x-content-type-options: nosniff

x-frame-options: deny

x-xss-protection: 1; mode=block

{"error":{"code":-32001,"message":"unauthorized access"},"id":1,"jsonrpc":"2.0"}
proves: Connect an agent via an official MCP serverrecorded 2026-09-05
$echo '<jsonrpc initialize>' | npx -y @launchdarkly/mcp-server start --transport stdioreproduced
$ echo '<jsonrpc initialize>' | npx -y @launchdarkly/mcp-server start --transport stdio
\|/{"result":{"protocolVersion":"2025-06-18","capabilities":{"tools":{"listChanged":true}},"serverInfo":{"name":"LaunchDarkly","version":"0.6.2"}},"jsonrpc":"2.0","id":1}
\
proves: Connect an agent via an official MCP serverproves: Create and toggle flags through documented APIs, CLIs, or MCP — and the platform can force my changes through approval workflows instead of letting me write to production unreviewedrecorded 2026-09-05

Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence

15 of 23 testable claims verified · 1 contradicted → integrity 57/100

33 distinct capability claims found in LaunchDarkly’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.

15

Verified

7

Unverified

1

Contradicted

15

Undersold

Verified (21)
Unverified (8)
Contradicted (1)
Undersold (15)
Claims outside our story set (3)

Real capability claims found in LaunchDarkly’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.

  • “Preview/test the impact of targeting rule changes before applying them”

    source ↗

  • “Configure, evaluate, roll out, and observe AI models end-to-end within the platform”

    source ↗

  • “Generates an 'AI Run' record when tracking an LLM request or running an online LLM-as-a-judge eval”

    source ↗
Suggest a story for these →

Business model

free-tiersubscription-per-seatusage-basedenterprise-custom

Developer free tier, then per-seat Foundation plans with usage-based add-ons (service connections, experimentation keys, data export) and custom Enterprise/Guardian tiers.

pricing ↗

Score trend

How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.

PA Score23 (Sep 5 '26)32 (Sep 5 '26)
Agent-ready47 (Sep 5 '26)66 (Sep 5 '26)

Try Experimental

Run it in the microterminal →

Recorded agent sessions — and a live MCP handshake where the vendor ships one.

Flag

⚑ Flag a verdict

Think a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.

Badge

Embed this product's score badge →

Hotlinked SVG — always shows the live current score.

For agents

This page as markdown/llms.txt

Data

Evidence (JSON)Verdicts (JSON)

Agent surface uptime MCP 100% (30d, checked every 6h since Sep 8 '26)