Flipt vs Flagsmith
Both are alternatives to LaunchDarkly. Here's how they stack up — verified facts, no spin.
Also searched as Flagsmith vs Flipt — same comparison, one verdict.
Flipt and Flagsmith are closely matched on ownership (93 vs 90) — this one comes down to pricing and to which trade-offs below you can live with.
Flipt
Flags defined in Git, evaluated by one Go binary.
Flipt takes a GitOps approach: flag definitions live in your repository as files, get reviewed in pull requests like any other change, and are evaluated by a single Go binary that can run entirely offline with no external dependency. For a platform team that already runs everything through Git, this makes flags an ordinary part of the deployment pipeline rather than a separate control plane somebody has to remember to check. GPL-3.0 with about 4.9k stars. The trade is deliberate: no polished dashboard for product managers, because the source of truth is a file.
Flagsmith
BSD-licensed flags with remote config, and no copyleft to reason about.
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.
Side by side
10 points of comparison, every one read from a verified field. Green marks the side that wins a row outright. A dash means we do not hold that fact — never that it is zero.
| Flipt | Flagsmith | |
|---|---|---|
| Sovereignty ScoreOur transparent 0–100 composite for data ownership and exit cost. | 93 | 90 |
| Open source | Yes | Yes |
| Self-hostable | Yes | Yes |
| Local-first data | Yes | Yes |
| License | GPL-3.0 | BSD-3-Clause (open core; paid hosted and enterprise tiers) |
| Pricing | Free and open source. One binary on hardware you already have. | Open source free and self-hostable. Hosted plans have a free tier and paid tiers above it. |
| RAM to run it wellThe figure that actually matters, not the vendor's minimum. | — | 4 GB |
| Realistic running costWhat the box costs each month if you run it yourself. | — | $24–40/mo plus PostgreSQL, against LaunchDarkly pricing that scales per seat and per monthly active user |
| Setup timeHonest first-install estimate, not the marketing quickstart. | — | 2 hours |
| Ongoing maintenanceThe part nobody budgets for. | — | Low to moderate. |
Flipt edges it on the Sovereignty Score, but the right pick depends on the trade-offs below.
Weighing both against staying on LaunchDarkly? Is LaunchDarkly free? What it actually costs →
Flipt
Strengths
- +Flag definitions live in Git — reviewed, versioned and audited like code
- +Single Go binary, runs air-gapped with no external calls
- +Fits a GitOps workflow with no extra machinery
- +GPL-3.0 with no enterprise carve-out
Trade-offs
- −Smallest project here — a real bus-factor consideration
- −No dashboard a non-engineer will happily use
- −Git-based workflow means non-technical staff cannot flip a flag
- −No experimentation or statistics
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
Trade-offs
- −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
Which one fits you
The trade-offs above, turned into a decision. Find the line that describes your team.
Choose Flipt
if a lower exit cost matters more to you than any single feature, and flag definitions live in Git — reviewed, versioned and audited like code.
Choose Flagsmith
if bSD-3-Clause — the most permissive licence here, no copyleft to interpret.
Neither, yet
if both carry a real cost you should weigh first — smallest project here — a real bus-factor consideration, and smaller community than Unleash and fewer third-party integrations. If either of those is a dealbreaker for your team, the shortlist is wrong rather than the choice.
What it takes to run these yourself
Real requirements and honest running costs, not the vendor quickstart.
Flipt vs Flagsmith — common questions
Is Flipt a better fit than Flagsmith for feature flags & experimentation?
It depends on what you are optimising for, and the honest split is this: Flipt scores 93 to Flagsmith's 90 on data ownership and exit cost, so it is the safer choice if you care about being able to leave. Flagsmith earns its place on a different axis — bSD-3-Clause — the most permissive licence here, no copyleft to interpret. Neither is a wrong answer for every team; the table above is the actual comparison.
What happens if we want to switch later?
Flipt keeps its data local or in open formats, so leaving is an export rather than a negotiation. Flagsmith is still self-hostable, so the files stay on your server either way — but it is not local-first by design, so check what its export produces before you rely on it.
Can I self-host Flipt or Flagsmith?
Both can be self-hosted. The difference is what it costs you in time rather than whether it is possible — see the setup and maintenance rows above.
Are Flipt and Flagsmith both alternatives to LaunchDarkly?
Yes — both appear in our LaunchDarkly comparison, which is why they are worth putting side by side. People usually arrive here already having decided to move off LaunchDarkly and now choosing between the two replacements, which is a narrower and much easier question.
Related alternative guides
Facts verified 2026-07-31. Licenses and pricing change — spotted something out of date? That's a correction we want.