LaunchDarkly is hired to let engineering teams switch features on and off for chosen users without deploying code. It also lists experimentation, observability and AI agent controls on its site. This page covers the feature flag job, which is the part most teams hire it for: published prices, the open-source options, and a procedure for moving without surprising customers.
Once SDK calls are woven through the code, the flag service is part of the application. Flags added for one release are still there years later, and nobody remembers which are safe to delete.
The tool is rarely the hard part of leaving. The hard part is knowing which flags are alive, which is why the first step is a flag inventory.
Only alternatives we have checked. An open-source project is listed with the license its repository reports, on the date shown; one whose license could not be read as a single standard id is not offered as open source. Read the license guide before running any of them.
| Alternative | Kind | License | Read from |
|---|---|---|---|
| Unleash | Open source | AGPL-3.0 | Unleash repositoryChecked Oct 25, 2026 |
| Flagsmith | Open source | BSD-3-Clause | Flagsmith repositoryChecked Oct 25, 2026 |
Each feature below is what the product's own page or README says, linked to where we read it on the date shown. Pros and cons are limited to what those pages state and to what the path itself changes. We do not rank products on quality.
| Plan | Price as published | Includes | Read from |
|---|---|---|---|
| LaunchDarkly Developer | $0 | Unlimited seats, unlimited feature flags, 1K client-side MAU per month, 5 service connections | LaunchDarkly pricingChecked Oct 25, 2026 |
| LaunchDarkly Foundation, service connections | $10 per service connection per month | Pay as you go, billed yearly after a 14-day trial; 5 service connections included, no platform or seat fees | LaunchDarkly pricingChecked Oct 25, 2026 |
| LaunchDarkly Foundation, client-side MAU | $8.33 per 1K MAU per month (comparison table shows $10) | Client-side monthly active users on the pay-as-you-go plan | LaunchDarkly pricingChecked Oct 25, 2026 |
| LaunchDarkly Enterprise | Custom | Adds advanced user targeting, custom roles, workflows and approvals, SCIM | LaunchDarkly pricingChecked Oct 25, 2026 |
Prices as printed on LaunchDarkly's page on the checked date. The Foundation plan is usage-based, so the bill depends on service connections and client-side monthly active users. The page prints two different client-side MAU rates, $8.33 and $10 per 1,000, and does not explain the difference.
A feature flag service is read by your running code. That makes it infrastructure, and the work of replacing it is mostly engineering: swapping SDK calls and proving the flags evaluate the same way. The price comparison matters less than that effort.
Check the pricing model against your own usage. LaunchDarkly prices on the page by service connections and client-side monthly active users, so the cost follows how your apps are shaped, not just how many people use the dashboard.
Samples are made up and are not LaunchDarkly's prices. Type in the figures from your own invoice or order form.
The honest yearly cost of running open-source software yourself, set against the bill it replaces, with the seat count where it stops paying.
Paid seats against seats in use: what the idle ones cost a year, and what you save by right-sizing at renewal.
Arithmetic only, not tax, accounting or legal advice. Check the figures against your own order form.
In outline:
List every flag, which services read it, its rules, and whether it is a temporary release switch or permanent configuration. Remove the dead ones before moving anything.
Stand up the new service, recreate a few low-risk flags, and wrap the SDK calls behind one small function so switching providers touches one place.
Run both services for one application and compare what each returns for the same users, in every environment.
Move services one at a time, lowest risk first, and keep the old flag values frozen as the reference.
Revoke the old SDK keys, keep an export, then end the plan inside the contract's notice window.
Run the vendor report for QuickBooks Online or Xero, then open the free audit.
General information, not legal advice. See cancelling without penalties. Last reviewed Oct 25, 2026. Product names belong to their owners and are used only to identify them.
Send us the export and see which lines are worth a second look. A connected version is planned. LaunchDarkly is one of the lines worth a look.
Worked example. Type over it.
Result
| Self-hosting, per year | Amount |
|---|---|
| Hosting, backups, tooling | 720.00 |
| Admin and restore-test time | 2,640.00 |
| Total | 3,360.00 |
| One-off set-up (not in the yearly total) | 1,200.00 |
The saving holds only if the time is real. Price the admin hours at what that person's time costs the company, not at zero.
Worked example. Type over it.
Result
“In use” is your call: last sign-in in the past 30 or 90 days from the vendor's admin report. A seat for someone on leave is not idle.