- LaunchDarkly alternatives at a glance
- Ten feature flag and experimentation tools
- Two well-known flag tools now belong to bigger companies
- Open source and self-hosted, or a hosted suite?
- What to check before you migrate your flags
- My plain advice on choosing a LaunchDarkly replacement
- Frequently asked questions
The main LaunchDarkly alternatives split three ways: open source feature flag tools you can self-host, hosted flag services you can sign up for and use straight away, and experimentation suites that tie every flag to an A/B test. Decide whether you need flags alone or flags plus experiments, then compare the ten tools below.
Teams usually start looking past LaunchDarkly for one of three reasons: they want to host flags themselves, they want flags and experiments in one place, or they want a simpler service with fewer moving parts. Each of those points to a different tool.
The ten below are listed alphabetically and in no particular order, and every description comes from each vendor's own website, read as of Oct 2026. If experiments are the bigger goal, my roundup of A/B testing tools covers the marketing side.
LaunchDarkly alternatives at a glance
I checked the free plan column on each vendor's own website, as of Oct 2026. Yes means the page names a free plan, a free version or an open source edition. Trial only means it names a time-limited free trial. Not stated means the page I read named neither, so check the vendor's own site before you sign up.
| Tool | Type | Good for | Free plan |
|---|---|---|---|
| ConfigCat | Hosted feature flag service | Simple on and off flags with unlimited seats | Yes |
| Eppo | Experimentation platform, now Datadog | Experiments with flags for rollouts and kill switches | Not stated |
| Flagship | Experimentation and rollouts | Experiments, personalisation and feature rollouts together | Not stated |
| Flagsmith | Open source flag service | Cloud, self-hosted or private cloud feature flags | Yes |
| GrowthBook | Warehouse-native experimentation | Experiments, flags and product analytics on your own data | Not stated |
| Harness | Feature management in a delivery platform | Flags and experiments inside a wider delivery platform | Not stated |
| Optimizely | Feature management and experimentation | Teams that treat every release as an experiment | Not stated |
| Split | Enterprise feature management | Flag targeting at enterprise scale, with experiments | Not stated |
| Statsig | Product development platform | Flags, experiments and analytics tied to product data | Yes |
| Unleash | Open source feature management | Self-hosted flags for large organisations | Yes |
Ten feature flag and experimentation tools
ConfigCat
Best for: Teams that want a cross-platform flag service with unlimited seats and open source SDKs, and a forever free plan named on its home page.
Eppo
Best for: Data teams that want fast feature flags for A/B tests, feature gates, controlled rollouts and kill switches, now sold as Datadog Experiments.
Flagship
Best for: Product and marketing teams that want experiments, personalisation, search adjustments and feature rollouts managed from one digital experience suite.
Flagsmith
Best for: Engineering teams moving off an in-house flag system who want an open source service they can run in the cloud, self-hosted or in a private cloud.
GrowthBook
Best for: Product teams that want experimentation, feature flags and product analytics running on their own data warehouse, from a vendor citing 4,000+ companies as users.
Harness
Best for: Engineering teams already on a software delivery platform that want flags, experimentation and runtime configuration in the same place.
Optimizely
Best for: Organisations that want safe rollouts and experiments managed from the AI tools they already use, where each new feature can be switched on for testing.
Split
Best for: Enterprises that want to create, target and manage feature flags at scale, and measure whether each change makes things better or worse.
Statsig
Best for: Startups that want flags linked directly to product data, plus experiments computed in their warehouse, with what the vendor calls the most generous free tier.
Unleash
Best for: Large organisations that want to host flags on their own infrastructure, built on what the vendor calls the world's largest open source feature flag project.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Two well-known flag tools now belong to bigger companies
This is the part most comparison posts miss. Split's home page now says it's part of Harness, and the Eppo page is now titled Datadog Experiments, with a banner saying Datadog acquired the company. Flagship sits on Wingify's digital experience page, which says AB Tasty and VWO have united. Even LaunchDarkly's own title has moved on, to Runtime Control for AI-Era Software.
None of that makes them poor choices. It does mean a new owner sets the roadmap, so ask what's changing before you sign a long contract.
Open source and self-hosted, or a hosted suite?
- Open source, self-hosted. You run the flag service on your own infrastructure and keep evaluation data in-house. Two tools here lead with open source on their home pages.
- Hosted flag services. Sign up, add an SDK and start flipping flags. These suit smaller teams who want flags without running another service.
- Experimentation suites. Every flag can become a test, with results computed against your product or warehouse data. Choose this if experiments, not releases, are the main job.
What to check before you migrate your flags
- How many flags do you have live? Export the list first and delete the stale ones before you move anything.
- Which SDKs do you need? Check every language and platform you ship on, including mobile and edge.
- Where should evaluation happen? Self-hosting keeps user data inside your network, while hosted services are quicker to start.
- Do you need experiments now or later? A full suite for flags alone adds complexity you may not use.
- Who needs access? Some services limit seats, while one here says its seats are unlimited.
Flags work best when you can see what users do after a release, so it's worth pairing them with one of the product analytics tools I've rounded up.
Do you make a feature flag or experimentation tool? Tool makers can ask to be considered for a featured place on this list.
My plain advice on choosing a LaunchDarkly replacement
Decide first whether you want to run the service yourself. If you do, start with the open source options and spin one up in a test environment in an afternoon. If you don't, choose a hosted service that covers your SDKs and try it on one low-risk flag before you migrate the rest. Only reach for a full experimentation suite when your team already runs tests every week.
If you're tidying the wider toolkit at the same time, my list of developer productivity tools is a sensible next read.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
What is a feature flag?
A feature flag is a switch in your code that turns a feature on or off without a new deployment, so you can release to a few users first, roll back fast or run an experiment.
Is there an open source alternative to LaunchDarkly?
Yes. Two tools on this list lead with open source on their home pages and can be self-hosted, as of Oct 2026. The free plan column shows which ones.
Have any LaunchDarkly alternatives been bought?
Yes. Two of the better-known names on this list now belong to bigger companies, one to a software delivery platform and one to a monitoring company, as of Oct 2026. Both still sell flags and experiments.
Do I need experimentation as well as feature flags?
Not always. Flags on their own handle safe releases and kill switches. Add experimentation when you want to measure whether a change improves a metric, not just whether it breaks anything.
How hard is it to migrate from LaunchDarkly?
The code change is usually small, since most tools use similar SDK calls. The work is in recreating targeting rules and segments, so move a few low-risk flags first.


