LaunchDarkly → Flagsmith
What it saves, what actually moves, what you rebuild — and the thing that catches people.
What it costs, and what it saves
Same LaunchDarkly baseline. Flagsmith self-hosted is free under BSD-3-Clause with no per-MAU meter at all.
Moves cleanly
Nothing automatically, but Flagsmith's environment and project model maps closely enough that the mental translation is quick.
You rebuild
Flags, environments and SDK integration.
What LaunchDarkly costs you today
LaunchDarkly moved off per-seat pricing and now bills on a dual meter: roughly $10 per service connection plus about $8.33 per 1,000 client-side monthly active users. Seats are unlimited on every tier, which is a genuine improvement — but the meters mean a consumer app with a large user base can pay substantially more than it did before, while a small team with many microservices pays on connections. There is a free tier for small use. Figures checked 2026-07-31; this pricing changed recently, so confirm against LaunchDarkly's current page before modelling it.
What actually holds you in
Moderate, and falling fast because of OpenFeature. Historically the hook was the SDK: flags evaluated through LaunchDarkly's client meant swapping vendors meant touching every call site. OpenFeature — a CNCF standard with provider implementations for most of this category, LaunchDarkly included — makes the evaluation API vendor-neutral, so the switch becomes a provider swap at startup. What still does not move is everything around the flags: targeting rules, segment definitions, experiment history and the audit trail, none of which export in a form another platform ingests.
What you are moving to
Flagsmith covers feature flags, remote configuration and A/B testing under BSD-3-Clause — the most permissive licence in this comparison, which removes the legal reading that AGPL requires. It self-hosts on Docker or Kubernetes, supports multiple environments and organisations natively, and its edge API keeps evaluation latency low without you building a caching layer. Around 6.5k stars. Its remote-config support is the underrated part: shipping a configuration value to clients without a release is the same mechanism as a flag, and having both in one tool removes a category of bespoke plumbing.
Open source free and self-hostable. Hosted plans have a free tier and paid tiers above it.
Flagsmith strengths
- BSD-3-Clause — the most permissive licence here, no copyleft to interpret
- Feature flags and remote config in one product
- Multi-environment and multi-organisation support built in, not bolted on
- Edge API keeps evaluation fast without custom caching
What you give up
- Smaller community than Unleash and fewer third-party integrations
- Experimentation is basic next to LaunchDarkly
- Advanced features are reserved for the paid tiers
- Self-hosted deployment needs Postgres and some tuning at scale
The migration, step by step
- 1Adopt OpenFeature first, for the same reason as above
- 2Deploy Flagsmith on Docker with Postgres
- 3Mirror your LaunchDarkly environments — Flagsmith's are first-class, not an add-on
- 4Recreate flags and remote config values together; Flagsmith handles both
- 5Point the edge API at your own domain if evaluation latency matters
The gotcha
Flagsmith's BSD licence is the reason to choose it over Unleash's AGPL, and that only matters if you intend to modify it. If you do not, pick on features instead and the answer is usually Unleash.
When to stay on LaunchDarkly
You need experimentation or approval workflows.
Other ways off LaunchDarkly
More Layer 3 migrations
Figures verified 2026-07-31 against vendor pricing pages. Prices change and migrations differ by estate — treat the cost delta as a starting model, not a quote. Rankings and recommendations here are merit-only; affiliate income never changes a verdict. See our methodology.