Feature Flags at Scale: LaunchDarkly, Unleash, Flagsmith, or Build It Yourself?
Four options, three tradeoffs that matter once flags are in every PR. Here is the actual cost and operational picture.
Why flags eat teams alive
Flags are easy to add and impossible to remove. Every team starts with “we'll clean them up” and ends with 2,000 flags nobody owns, 40% of which are always-on or always-off.
The tool choice matters less than the operational practice: you need flag lifecycle (creation → rollout → decision → cleanup), and you need it enforced by tooling, not convention.
LaunchDarkly
The premium commercial option. Multi-variant flags, percentage rollouts, audit logs, SDKs for every language, strong permissions. Cost scales with MAU + seats; at scale it is a line item worth its own review.
Strengths: reliability, feature depth, enterprise controls. Weaknesses: cost, and heavy SDKs in languages that matter to you (JS bundle size, in particular).
Unleash
Open-source, with a hosted tier. Feature parity with LaunchDarkly at the core (flags, rollouts, percentages). Self-hosting is straightforward; hosted is reasonably priced.
Strengths: open source, lighter SDKs, no per-MAU billing if self-hosted. Weaknesses: smaller community than LaunchDarkly, fewer integrations out of the box.
Flagsmith
Another open-source-first option, with the cleanest REST API of the three. Multi-environment support, segmentation, dynamic flag values.
Strengths: API ergonomics, straightforward self-host. Weaknesses: admin UI feels basic compared to LaunchDarkly, enterprise features are still being built out.
DIY
A hash table in Redis, a file in S3, a row in Postgres. Works well for <50 engineers, 1,2 environments, simple on/off flags.
Works badly as soon as you need percentage rollouts, audit logs, per-user targeting, or a non-engineer to flip a flag. Most teams overbuild this, then migrate.
Which one, at which scale
- Under 30 engineers: DIY or Unleash (community). You'll outgrow DIY at the next stage; the rewrite is usually two weeks.
- 30,200: Unleash (self-hosted) or Flagsmith. Ergonomics matter, audit logs matter, cost still matters.
- 200+: LaunchDarkly, or Unleash Enterprise if you want self-host. You will pay for the feature depth and it will be worth it.
The mistake is picking based on where you are today. Pick for where you'll be in 18 months, migrating flag systems mid-growth is the most painful rewrite in this list.
Flags are easy to add and impossible to remove.
The cleanup routine that actually works
Every flag gets a creator, an owner, and an expected lifetime at creation. Flags with lifetime 'forever' need a director's signature. Most flags are six weeks; a few are a quarter; almost none should be permanent.
Weekly, a job scans for flags that have been 100% rolled out or 0% rolled out for the full lifetime without being removed. It opens a ticket assigned to the owner.
Monthly, the platform team reviews flags that have no owner. If the original owner left the company, the flag is either adopted within 30 days or removed on sight.