← Blog

Flagsmith vs LaunchDarkly: two dashboards, one choice

Flagsmith vs LaunchDarkly comes down to who runs the server and who meters the bill. Flagsmith is open source under a BSD-3-Clause license: clone it, run Django, Postgres, and the React admin yourself, or pay Flagsmith to host it. LaunchDarkly is closed-source SaaS: there is no server to run, and the usage meter is service connections plus client-side monthly active users (MAU).

Neither is missing a feature the other has outright. Both gate a flag behind an API, hosted or self-hosted, and both ship SDKs across a dozen-plus languages. This post compares pricing, hosting, SDK coverage, and governance, with numbers pulled from each vendor’s current pricing page, so you can work out which meter fits your traffic before picking one.

Key Takeaways

  • Flagsmith’s free tier covers 50,000 API requests a month and 1 team member. Its Start-Up tier is $40/month (annual) or $45/month (monthly) for 1 million requests and 3 seats.
  • LaunchDarkly’s Developer tier is free with 5 service connections and 1,000 client-side MAU included. Its Foundation tier adds $10/connection/month and $8.33 per 1,000 MAU past those limits, both on annual billing.
  • Flagsmith is open source (BSD-3-Clause) and self-hostable: run Django, Postgres, and the admin UI yourself, or pay for Flagsmith Cloud or Private Cloud. LaunchDarkly has no self-hosted option; only its SDKs are open source, under Apache 2.0.
  • Flagsmith ships 15+ SDKs, including Python, Java, Go, Ruby, PHP, .NET, Rust, and Elixir on the server. LaunchDarkly covers a comparable language spread plus the deeper enterprise governance layer: SCIM provisioning and required approvals on flag changes.
  • Both tools keep the flag’s state behind an API, not in your repo, so a change in either dashboard never shows up as a diff in a pull request.

Flagsmith vs LaunchDarkly: the core difference

Flagsmith started as an open-source, self-hostable flag server (it was originally called Bullet Train). That history still shows: the whole stack, Django API, Postgres database, React admin, is yours to run if you want it, and the source is on GitHub under a permissive license.

LaunchDarkly started as a hosted flag-management service and has stayed one. There is no self-hosted LaunchDarkly. You get an account on their infrastructure, and the bill tracks how many server environments connect and how many end users your client-side SDKs see in a month.

That split decides almost everything else in this comparison. Flagsmith’s pricing is a request count because the server is sitting behind your own API gateway or theirs. LaunchDarkly’s pricing is connections and MAU because the server is always theirs.

Flagsmith vs LaunchDarkly pricing

TierFlagsmithLaunchDarkly
Free$0/mo: 50K requests/mo, 100K users in experiments, 1 seatDeveloper: $0/mo, unlimited seats, 5 service connections, 1K client-side MAU
PaidStart-Up: $40/mo (annual) or $45/mo (monthly), 1M requests/mo, 3 seatsFoundation: $10/connection/mo (annual, 5 free) + $8.33/1K MAU (annual, 1K free)
Mid-tierScale-Up: $250/mo (annual) or $300/mo (monthly), 5M+ requests/mo, 5 seats (up to 20 at $50/seat/mo)(no mid-tier; Foundation scales with usage)
EnterpriseCustom: 5M+ requests, 20+ seats, LDAP + SCIMCustom: volume discounts, architecture mapping, security review

Flagsmith’s unit is the API request: every flag evaluation your server or client makes against the Flagsmith API counts against the monthly allotment, and seats are capped per tier (1 free, 3 on Start-Up, 5 on Scale-Up before the per-seat add-on kicks in). LaunchDarkly’s units are service connections, one per server-side SDK instance per environment, and client-side MAU, the number of distinct end users your browser or mobile SDKs serve in a month.

Run the math on a concrete case. A team with 10 server-side connections and 2,000 client-side MAU on LaunchDarkly’s Foundation tier pays 5 paid connections at $10 each ($50) plus 1,000 paid MAU at $8.33/1,000 ($8.33), about $58/month. The same team on Flagsmith, if their combined server and client requests stay under 1 million a month, fits the $40/month Start-Up tier with 3 seats included. A high-traffic consumer app burns through Flagsmith’s request allotment fast; a backend-heavy team with few end users keeps LaunchDarkly’s MAU meter low. Overage on Flagsmith runs about $50 per extra million requests, decreasing at volume; overage on LaunchDarkly is the $10/connection and $8.33/1,000-MAU rate repeated past the free tier.

Self-hosting: who can run their own server

Flagsmith can run entirely on your own infrastructure. The open-source repo is BSD-3-Clause licensed, and “self-host on-premises or in your own cloud” is one of Flagsmith’s three listed deployment options alongside Cloud and Private Cloud. Patching Django and backing up Postgres become your job, not Flagsmith’s, but so does every byte of the data.

LaunchDarkly has no self-hosted tier at any price. The Developer, Foundation, and Enterprise plans all run on LaunchDarkly’s infrastructure. If “no vendor runs my flag server” is a hard requirement, Flagsmith clears that bar and LaunchDarkly does not.

SDK and language coverage

Flagsmith ships SDKs across 15+ languages: Python, Java, .NET, Node.js, Ruby, PHP, Go, Rust, and Elixir on the server, plus JavaScript, React, Next.js, Flutter, React Native, Android/Kotlin, and iOS/Swift on the client. Server SDKs support local evaluation mode, caching the rule set so later flag checks skip the network call.

LaunchDarkly has the widest SDK matrix in the feature-flag category, covering a broader spread of backend and client languages, all published as open source under Apache 2.0 on github.com/launchdarkly. For either vendor, an open-source SDK means you can read exactly how a flag check resolves locally. Neither open-sources the service that serves the rules.

Governance and enterprise features

LaunchDarkly’s Enterprise tier adds SCIM provisioning, required approvals on flag changes, and architecture mapping plus a security review as part of onboarding, aimed at a classic enterprise-IT checklist. Flagsmith’s Scale-Up tier adds SAML/SSO and governance controls at $250/month (annual), and its Enterprise tier layers on LDAP and SCIM (listed as coming soon at time of writing).

If a required-approval workflow on every flag change is what your security review asks for, LaunchDarkly’s governance layer is the more direct match today. If self-hosting the whole stack, including the governance layer, is the actual requirement, Flagsmith is the one that lets you do that at all.

What neither tool fixes: the flag still lives behind an API

Self-hosted or SaaS, the flag’s current state lives in a database that your server or client code queries at runtime, not in your repo. A rule changed in Flagsmith’s admin UI or LaunchDarkly’s dashboard does not show up as a diff in a pull request. You find out it changed by checking an audit log, not by reading git blame. A coding agent working in your codebase cannot see either dashboard, so it has no way to know a flag exists before it deletes the branch behind it.

dif takes a different approach: every flag and experiment is a Markdown file in your repo, reviewed in a pull request, with the decision and the number written into the same file a coding agent can read on session start. It is a smaller bet than Flagsmith or LaunchDarkly: no admin UI, a JavaScript and TypeScript SDK instead of 15+ languages, and rollback is a merge and a deploy, not a toggle. If you want flags reviewed like code with nothing to self-host, that is the trade dif makes.

The open-source LaunchDarkly alternative and Flagsmith alternative posts both cover that tradeoff in full.

FAQ

Is Flagsmith cheaper than LaunchDarkly? It depends on your traffic shape and whether you self-host. Flagsmith’s Start-Up tier is $40/month for 1 million requests; self-hosting the open-source version drops the license cost to your own infrastructure bill. LaunchDarkly has no self-hosted option, and its Foundation tier meters $10 per service connection plus $8.33 per 1,000 client-side MAU past the free limits.

Can I self-host Flagsmith or LaunchDarkly? Flagsmith, yes. It is open source under a BSD-3-Clause license, and self-hosting on your own infrastructure is one of its three listed deployment options. LaunchDarkly, no. Every plan runs on LaunchDarkly’s hosted infrastructure.

Is Flagsmith actually open source? Yes. The core Flagsmith server, API, and admin UI are on GitHub under a BSD-3-Clause license. LaunchDarkly’s SDKs are open source under Apache 2.0, but its dashboard and evaluation service are closed and hosted only by LaunchDarkly.

Which has more SDK languages, Flagsmith or LaunchDarkly? LaunchDarkly. Flagsmith ships 15+ SDKs covering most common backend and client languages, including Python, Java, Go, Ruby, and Rust. LaunchDarkly’s matrix is the widest in the feature-flag category, so the exact gap depends on which backend language you need.

Does Flagsmith support A/B testing? Yes, starting on the Start-Up tier ($40/month annual). The free tier covers feature flags, environments, and segments but not A/B testing.

Is there an open-source alternative to both Flagsmith and LaunchDarkly? Yes. dif, GrowthBook, and Unleash are open-source options. dif is git-native: flags are Markdown files in your repo instead of rows in a database behind an admin API, so there is no server to self-host at all for the core flag workflow.

The bottom line

Flagsmith vs LaunchDarkly is a hosting decision first, and a pricing-model decision second. Flagsmith is open source and self-hostable, metered by API requests; LaunchDarkly is closed-source SaaS with no self-hosted option, metered by service connections and client-side MAU. Both publish broad SDK coverage, and both keep the flag’s live state in a database your code queries, not in your repo.

If self-hosting or the request-based free tier fits your traffic, Flagsmith is the more direct match. If you want the widest SDK matrix and a service you never operate yourself, LaunchDarkly is built for that. If you have read both pricing pages and still want the flag reviewed in a pull request instead of a dashboard, install the CLI and see the model directly:

npm install -g @dif.sh/cli
dif init

dif init scaffolds the dif/ directory and the agent files in about two minutes, no account required. The docs cover the full CLI and SDK workflow, and dif Cloud pricing has the flat-rate hosted option if you want analytics without running your own server.

Pricing and plan details are drawn from Flagsmith’s pricing page and LaunchDarkly’s pricing page, and SDK licensing is confirmed on github.com/flagsmith and github.com/launchdarkly, as of November 2026. Verify current pricing with each vendor, since tiers change.