← Blog

Unleash vs LaunchDarkly: open source against the incumbent

Unleash vs LaunchDarkly comes down to who runs the server and who owns the code. Unleash is open source: clone the repo, run it on your own infrastructure, and the core server code is yours to read. LaunchDarkly is closed-source SaaS: there is no server to run, because LaunchDarkly runs it for you, and the dashboard and evaluation service stay private.

That split sounds simple until you look at the license. Unleash’s core server moved from Apache 2.0 to AGPL-3.0 at v8.0.0 (the official Docker images stay Apache 2.0), which changes what “open source” obligates you to do if you modify and redistribute it. LaunchDarkly never offered that choice: only its SDKs are open source, and there is no self-hosted LaunchDarkly at any price. The numbers below are pulled from each vendor’s current pricing page and GitHub repo.

Key Takeaways

  • Unleash’s core server license changed from Apache 2.0 to AGPL-3.0 at v8.0.0. LaunchDarkly’s SDKs are Apache 2.0, but its dashboard and evaluation service are closed, with no self-hosted option at all.
  • Unleash OSS is free with unlimited seats, capped at 1 project, 2 environments, and 5,000 flags per instance. LaunchDarkly’s Developer tier is also free with unlimited seats, capped at 5 service connections and 1,000 client-side MAU.
  • Unleash’s Pay-As-You-Go plan is $75 per seat a month, no seat minimum on cloud but a 5-seat minimum self-hosted. LaunchDarkly’s Foundation tier meters $10 per service connection and $8.33 per 1,000 MAU, both on annual billing.
  • Unleash OSS Edge, the open-source edge-evaluation layer, reaches end-of-life December 31, 2026. The replacement, Enterprise Edge, is a paid feature requiring Unleash Enterprise v7.3 or later.
  • Unleash ships 15 official SDKs plus 15+ community ones; LaunchDarkly ships roughly 13 server-side and 12 client-side SDKs plus edge SDKs for Cloudflare, Fastly, Akamai, and Vercel. Neither stores the flag’s state in your repo.

Unleash vs LaunchDarkly: self-hosted server against SaaS

Unleash ships as a server you deploy: a backend, a PostgreSQL database, and a React admin UI where flags get created, targeted, and toggled. Run it on your own infrastructure or pay Unleash to run it in their cloud. Either way, the code that evaluates a flag is code you can read, because the repository is public.

LaunchDarkly has never shipped a self-hosted option. Every tier, Developer, Foundation, or Enterprise, runs on LaunchDarkly’s infrastructure. You get an account, not a deployment. The SDKs that talk to that service are open source, but the service itself, the rule engine and the dashboard, is not.

If “no vendor runs my flag server” is a hard requirement, that decides the comparison before pricing enters the picture. Unleash clears that bar. LaunchDarkly does not, and does not claim to.

Licensing: AGPL-3.0 against a closed dashboard

Most comparison posts skip this, but it decides what you are allowed to do with the code. Unleash’s main repository, Unleash/unleash on GitHub, carries an AGPL-3.0 license as of this writing. AGPL’s network clause means that if you modify Unleash and run the modified version as a service other people use over a network, you owe them the source of your changes, not just a copy if you ship it. That is a meaningfully stronger copyleft than the Apache 2.0 license Unleash used before v8.0.0, and it is worth a legal read before you fork and extend the server for internal use.

LaunchDarkly’s position is simpler because there is less to license: the SDKs that run inside your application are Apache 2.0, a permissive license with no network clause. The dashboard and evaluation engine are not open source at all, so there is nothing to fork. You are licensed to use the service, not to read or modify what runs it.

Neither model is wrong. Unleash’s AGPL-3.0 buys real transparency and a real self-hosting option, with a license term a legal team should read before you fork the server. LaunchDarkly’s closed core means one fewer license to evaluate, and one fewer thing you can ever run yourself.

Unleash vs LaunchDarkly pricing

TierUnleashLaunchDarkly
FreeOSS self-hosted: $0, unlimited seats, capped at 1 project, 2 environments, 5,000 flagsDeveloper: $0/mo, unlimited seats, 5 service connections, 1,000 client-side MAU
PaidPay-As-You-Go: $75/seat/mo, no seat minimum on cloud, 5-seat minimum self-hosted; unlimited flags, projects, environments; 53M API requests/mo included, then $5/millionFoundation: $10/connection/mo (annual) + $8.33/1K MAU (annual), both with a small free allowance
EnterpriseCustom, invoiced annually; SSO, SCIM, RBAC, change approvals, support SLACustom; SSO/SAML, SCIM, custom RBAC, PII redaction, audit logging, architecture review

Run a concrete case. A 10-person team on Unleash’s cloud Pay-As-You-Go plan pays $750 a month flat, no matter how many flags or environments they add, since there’s no seat minimum on cloud and the caps that apply to OSS disappear once you pay. The same team on LaunchDarkly’s Foundation tier pays for connections and MAU, not seats: 10 service connections and 2,000 client-side MAU runs about $58 a month on annual billing, a fraction of Unleash’s per-seat number, right up until MAU or connection count climbs.

That is the real tradeoff in the pricing. Unleash charges per seat, so the bill is predictable per head count and indifferent to traffic. LaunchDarkly charges per connection and per MAU, so a small team with heavy traffic can pay more than its seat count would suggest, and a large team with light usage can pay less than Unleash’s per-seat floor.

SDK and language coverage

Unleash’s own GitHub repo lists 15 official SDKs: Go, Java, Node.js, PHP, Python, Ruby, Rust, and .NET on the server, plus Android, Flutter, iOS, JavaScript, React, Svelte, and Vue on the client, with 15 or more community-maintained SDKs beyond that. Unleash’s pricing page rounds this up to “25+ SDKs for your favorite language or framework.”

LaunchDarkly’s matrix covers roughly 13 server-side languages and 12 client-side platforms, plus edge SDKs for Cloudflare, Fastly, Akamai, and Vercel that evaluate a flag at the CDN layer instead of in your app or your backend. LaunchDarkly’s SDKs are open source under Apache 2.0 on github.com/launchdarkly.

Both lists are wide enough that language coverage rarely decides this comparison on its own. The edge SDKs are the exception: if you need a flag evaluated at a CDN edge node before a request reaches your origin, LaunchDarkly has a shipped answer and Unleash’s roadmap does not list an equivalent today.

Governance, kill switches, and Unleash Edge’s end-of-life

LaunchDarkly’s Enterprise tier is built around a procurement checklist: SSO/SAML, SCIM provisioning, custom RBAC, PII redaction, audit logging, and an architecture-mapping review as part of onboarding. Unleash Enterprise covers the same ground (SSO, SCIM, granular RBAC, change-request approvals, a support SLA), gated behind the same kind of custom contract.

Both tools give an admin a sub-second kill switch: toggle the flag in the UI, and the next SDK poll or streamed update turns it off in production. Neither waits on a build or a deploy.

The date to track is Unleash Edge. The open-source edge-evaluation layer reaches end-of-life on December 31, 2026, with Enterprise Edge, a paid feature requiring Unleash Enterprise v7.3 or later, as the replacement. A team relying on OSS Edge for low-latency evaluation needs a 2026 plan, not a 2027 one.

LaunchDarkly’s newest feature, Release Autopilot, ships code an agent writes and rolls it back automatically if it breaks, free across all tiers until February 1, 2027. LaunchDarkly and Unleash are both now reaching for the same agent-assisted workflow dif was built around from the start. Whether a dashboard behind a login can give an agent that context safely is a separate question.

What neither tool fixes: the flag still lives outside your repo

Self-hosted or SaaS, the flag’s live state sits in a database your server or client code queries at runtime, not in your repo. A rule changed in Unleash’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 reads on session start. It is a smaller bet than either tool here: no admin UI, a JavaScript and TypeScript SDK instead of 15 or 25-plus languages, and rollback is a merge and a deploy, not a toggle. If you want the flag reviewed like code with nothing to self-host and nothing to license, that is the trade dif makes.

The Unleash alternative and open-source LaunchDarkly alternative posts both cover that tradeoff against each tool individually.

FAQ

Is Unleash open source? Yes. The core server repository is licensed AGPL-3.0 as of v8.0.0 (it was Apache 2.0 before that; the official Docker images still ship under Apache 2.0). The free self-hosted tier caps at 1 project, 2 environments, and 5,000 flags per instance.

Is LaunchDarkly open source? Only the SDKs, under Apache 2.0. The dashboard and the service that evaluates and stores flag rules are closed source, and there is no self-hosted LaunchDarkly at any price.

How much does Unleash cost compared to LaunchDarkly? Unleash’s Pay-As-You-Go cloud plan is $75 per seat a month with no seat minimum (self-hosted paid plans carry a 5-seat minimum), and it includes unlimited flags, projects, and environments. LaunchDarkly’s Foundation tier meters $10 per service connection and $8.33 per 1,000 client-side MAU, both on annual billing, after a free allowance of 5 connections and 1,000 MAU.

Can I self-host Unleash or LaunchDarkly? Unleash, yes, that is the core of its model. LaunchDarkly, no. Every LaunchDarkly tier runs on LaunchDarkly’s own infrastructure.

What happens to Unleash Edge in 2026? Unleash OSS Edge, the open-source edge-evaluation layer, reaches end-of-life on December 31, 2026. Enterprise Edge, a paid feature requiring Unleash Enterprise v7.3 or later, is the replacement Unleash recommends migrating to.

Is there an open-source alternative to both Unleash and LaunchDarkly? Yes. dif, GrowthBook, and Flagsmith are open-source options. dif is git-native: flags and experiments are Markdown files reviewed in pull requests, instead of rows in a database behind an admin UI for either tool here.

The bottom line

Unleash vs LaunchDarkly is a licensing and hosting decision first, and a pricing decision second. Unleash is AGPL-3.0, self-hostable, and priced per seat; LaunchDarkly is closed-source SaaS with no self-hosted option, priced per connection and per MAU. Both give you a sub-second kill switch and a real SDK matrix, and both keep the flag’s live state in a database your code queries, not in your repo.

If self-hosting or a flat per-seat bill fits your team, Unleash is the more direct match, with the AGPL-3.0 terms worth a legal read first. If you want the widest edge-evaluation story and never want to run the server yourself, LaunchDarkly is built for that, at a usage-based price that tracks your traffic. If you have read both pricing pages and still want the flag reviewed in a pull request instead of either 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 workflow, and dif Cloud pricing has the flat-rate hosted option if you want analytics without running a server at all.

Pricing and licensing facts are drawn from Unleash’s pricing page and LaunchDarkly’s pricing page, with license terms confirmed on github.com/Unleash/unleash and github.com/launchdarkly, as of November 2026. Verify current pricing and licensing with each vendor, since both change terms.