LaunchDarkly → Unleash
What it saves, what actually moves, what you rebuild — and the thing that catches people.
What it costs, and what it saves
LaunchDarkly bills roughly $10 per service connection plus about $8.33 per 1,000 client-side MAU. A consumer app with 200,000 MAU pays roughly $1,700/month. Unleash self-hosted is a server and a database.
Moves cleanly
The concepts — flags, segments, gradual rollouts all exist in both. Nothing transfers automatically.
You rebuild
Flag definitions, targeting rules and every SDK call site, unless you adopt OpenFeature first.
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
Unleash is the closest open equivalent to LaunchDarkly: gradual rollouts, user targeting, segments, environments, custom activation strategies and a genuinely good admin UI. Its architecture is the detail that matters most in production — SDKs evaluate flags locally from a cached configuration, so an outage of the Unleash server does not take your application down with it, which is not true of every platform in this category. AGPL-3.0 with around 13.7k stars, self-hostable with Docker, and an enterprise tier for organisations that want support and advanced governance. Note the licence: AGPL is strong copyleft, which matters if you intend to modify it and offer it as a service.
Open-source server free and self-hostable. Hosted and enterprise tiers are paid.
Unleash strengths
- Closest feature parity with LaunchDarkly of anything open
- Local SDK evaluation — your app survives an outage of the flag service
- Mature, with a decade of production use behind it
- Strong Kubernetes and Docker deployment story
What you give up
- AGPL-3.0 is strong copyleft — read it before you modify and redistribute
- Some governance and advanced features sit in the paid enterprise tier
- No experimentation engine on the level of LaunchDarkly's
- Self-hosting means running a server and a database you now own
The migration, step by step
- 1Adopt OpenFeature BEFORE migrating — it makes the vendor a one-line provider swap and LaunchDarkly ships a provider, so this step is free
- 2Deploy Unleash with Postgres
- 3Recreate flags, starting with the ones actually evaluated in the last 30 days
- 4Swap the OpenFeature provider from LaunchDarkly to Unleash
- 5Delete the dead flags rather than porting them — most estates are half dead
The gotcha
Skipping the OpenFeature step turns a provider swap into touching every call site. It is the single highest-leverage move in this migration and it is invisible until you have skipped it.
When to stay on LaunchDarkly
You run real experiments — LaunchDarkly's statistics engine is ahead of anything open.
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.