4.4/5
G2 rating
621 reviews
Report
Should I Use LaunchDarkly?
Safely manage code and AI agents in production with feature flags, progressive delivery, automated rollback, and runtime control.
Depends
DependsBuy if you are a mid-size or large engineering org that needs progressive delivery and AI runtime control and can absorb five-figure annual contracts.
Enterprise-grade feature flags that shine at scale but price out small teams; free Developer tier, then $20k+/yr contracts.
Confidence: High
Yes
Free tier
Developer plan at $0/month
$20k+/yr
Typical enterprise cost
Usage-based, per Spendflo
$329M
Total funding
$3B valuation (2021)
Value for money
2
Users publicly balk at five-figure bills.
Ease of use
4
Reviewers consistently praise ease of use.
Feature depth
5
Market-leading flags, delivery, AI runtime control.
Security posture
4
Bug bounty, ISMS, trust page; 2025 outage disclosed.
Pros
Cons
Gotchas
- highUsage-based pricing can balloon fast; enterprise deals commonly run $20,000+ per year.⁵
- mediumPricing model moved away from seats — expect unpredictable bills as flag usage grows.
- mediumDeep SDK integration creates lock-in; one team publicly documented migrating to Statsig.12
- mediumService disruptions happen — a major one was publicly disclosed in October 2025.⁹
Best for
- Large engineering orgs
- Progressive delivery teams
- AI agent rollout control
- Teams needing flag governance
Not for
- Startups and small dev teams
- Anyone avoiding five-figure contracts
- Simple on/off toggle needs — use a config file
- Teams wanting predictable flat-rate billing
Companies that use it
- Paramount
- iPipeline
Pricing
Developer
$0/month
- Free plan for small teams
- Basic flagging
Enterprise
Not disclosed
- Usage-based billing
- SSO, support terms, governance
Security
Mature program: managed bug bounty, ISMS addendum, trust center; a disclosed 2025 outage and two dated ecosystem CVEs exist.
- CVE-2022-2097 in ld-relayVulnerability warning affecting the open-source self-hosted relay component.⁸
- CVE-2022-4259 in npm packageMalicious code reported in the launchdarkly npm package per Vulert database.
- October 20, 2025 service disruptionVendor publicly disclosed and explained a service disruption on its blog.⁹
What users say
Developers widely respect the product's polish and reliability but frequently push back on its cost and small-team fit.
“Why is Launch Darkly this expensive?”
“Honestly, Launchdarkly does what it sa…”
“We use LaunchDarkly currently. For a small team i…”
Alternatives
Compare LaunchDarkly with each alternative.
GrowthBook
Open-source flagging and experimentation with a free tier.
LaunchDarkly vs GrowthBookUnleash
Open-source alternative you can self-host cheaply.
LaunchDarkly vs UnleashConfigCat
Simpler, cheaper flag service for small teams.
LaunchDarkly vs ConfigCatStatsig
Modern alternative for experimentation at scale.
Full analysis
Based on 40+ public sources including G2, Gartner, Capterra, Reddit threads, vendor docs, and security databases.
Sources
review
- LaunchDarkly Reviews — Gartnergartner.comreview
- LaunchDarkly Reviews — AWS Marketplaceaws.amazon.comreview
review
- LaunchDarkly Pricing Guide — Spendflospendflo.comofficial
- LaunchDarkly Pricing 2026 — GrowthBookgrowthbook.ioofficial
- LaunchDarkly security trust pagelaunchdarkly.comsecurity
- ld-relay CVE-2022-2097 — GitHubgithub.comsecurity
- October 20 Service Disruption — LaunchDarklylaunchdarkly.comsecurity
news
- LaunchDarkly funding profile — PitchBookpitchbook.comnews
- Feature-flagging via LaunchDarkly, moved to Statsigc5r.medium.comreview
Rate this review
Anonymous. You can change your vote.
Loading votes…
Ask a follow-up
Ask if a use case fits. Answers stay inside this report and its sources.
Comments
One queue. No replies. Give a display name first. Limit: 7 comments per day.
No comments yet.