Feature flag tools
Feature flag tools let engineers switch features on or off, roll them out to a slice of users, and roll them back without redeploying. This grid compares ten hosted and self-hosted tools, from open source servers to full experimentation platforms. The real trade-offs are how each one bills (per seat, per request, per user), whether you can run it yourself, and whether approvals, SSO, and A/B testing sit behind an enterprise plan.
Last updated
How to choose
Start with what you need the flags to do. If you only need on/off switches and gradual rollouts, nearly every tool here does it and price and hosting decide. If you want to measure the effect of a change, pick a tool with built-in experimentation or one that connects to your data warehouse.
Rule out deal-breakers
- Hosting: if data must stay on your own servers, check the self-hosting row. Open source editions often leave out SSO and approvals.
- Governance: regulated teams usually need approval workflows, SSO, and audit logs. These are frequently enterprise-only.
- Team size: per-seat pricing is predictable but grows with headcount; usage-based pricing grows with traffic.
Understand the full cost
Compare the free plan limits against your real traffic, then estimate a month on the paid plan, not just the starting price. Usage tools charge for requests, events, or monthly active users, so a traffic spike can move the bill. Enterprise tiers are usually quote-only.
Check the final choice
- Try the free tier with one real flag in production.
- Confirm an SDK exists for every language you ship.
- Ask how long approval and audit history are kept.
- Check what happens to flags if the vendor is down (local evaluation and caching).
Answer
Browse the table. Filter to what matters.
Use the filters below, then sign in if you want to shortlist and decide with friends.
Sign in to vote, hide services and features, and reorder.
Verified: hover a cell and click its green dot for the source Estimate: no cited source Not stated: the company doesn't publish it
| Feature | ⠿ | ⠿ | ⠿ | ⠿ | ⠿ | ⠿ | ⠿ | ⠿ | ⠿ | ⠿ |
|---|---|---|---|---|---|---|---|---|---|---|
|
⠿
Free hosted plan
|
|
|||||||||
|
⠿
Free plan limits
|
||||||||||
|
⠿
Pricing model
|
||||||||||
|
⠿
Entry paid price
|
||||||||||
|
⠿
No per seat charge
|
||||||||||
|
⠿
Open source
|
|
|
|
|
|
|||||
|
⠿
Self hosting
|
|
|
|
|
|
|||||
|
⠿
Built in experiments
|
|
|
||||||||
|
⠿
Approval workflows
|
|
|||||||||
|
⠿
SSO and SAML
|
|
|||||||||
|
⠿
Bundled analytics
|
|
|
|
|
|
|
Why these features matter
-
Free hosted plan
A free hosted plan lets you ship real flags to production without procurement or running a server; tools without one need a trial or your own infrastructure.
-
Free plan limits
The caps decide whether a real project fits for free or you hit a paywall at launch.
-
Pricing model
Per-seat bills follow headcount; usage bills follow traffic. Pick the one you can forecast.
-
Entry paid price ($/month)
Shows what it costs to move past the free tier, before usage overages and extra seats.
-
No per seat charge
Per-seat pricing makes bringing designers, product managers and support staff into the tool cost extra.
-
Open source
Open source means you can inspect it, avoid lock-in and fork it if the vendor changes course.
-
Self hosting
Keeps flag and user data inside your network, which regulated or privacy-conscious teams often require.
-
Built in experiments
Lets you measure whether a feature helped, not only roll it out.
-
Approval workflows
Approvals stop a single person from flipping a production flag, a common audit and change-control requirement.
-
SSO and SAML
Central login and offboarding is a baseline for company-wide rollout.
-
Bundled analytics
Bundled analytics saves buying and wiring a second tool, but can mean paying for what you do not use.
About the services
-
LaunchDarkly · LaunchDarkly
The best-known feature management platform, now also covering AI agent configs, experimentation, and observability. Usage-based billing with unlimited seats; approvals are on the pay-as-you-go plan but mandatory approvals, SSO and audit logs need Enterprise.
-
Statsig · Statsig
Experimentation, feature flags, product analytics and session replay in one usage-priced platform (now part of the Amplitude family). Generous free tier with unlimited seats; flat $150 Pro plan adds advanced experimentation and approvals.
-
GrowthBook · GrowthBook
Open source, warehouse-native feature flags and A/B testing, priced per seat rather than per user or request. Runs in the cloud or self-hosted; approvals and SSO are Enterprise.
-
Flagsmith · Flagsmith
Open source feature flags and remote config you can use in the cloud, in a private cloud, or on your own servers. Plans scale by API requests and team members.
-
Unleash · Unleash
Open source feature flag server with a paid Enterprise edition (hosted or self-hosted) that adds SSO, approvals and support. Flat $75 per seat, no charge for flag evaluations or end users.
-
PostHog · PostHog
All-in-one product analytics platform whose feature flags and experiments share one SDK and bill with analytics and session replay. Best when you already want PostHog's analytics; free monthly allowance renews every month.
-
ConfigCat · ConfigCat
Simple, flat-priced feature flag service with unlimited seats and users on every plan. Plans differ by flag count, environments and config download volume, not by headcount or audience size.
-
DevCycle · DevCycle
Developer-focused feature flags with OpenFeature-compatible SDKs and unlimited seats. Part of Dynatrace since early 2026; free up to 1,000 client-side MAUs, with the Business plan priced by MAU and requests.
-
Harness FME · Harness
Harness Feature Management and Experimentation (the former Split platform) with pipeline-gated approvals and built-in experimentation. A free plan can be enabled from a Harness account; paid plans are sold by quote.
-
Flipt · Flipt
Self-hosted, git-native feature flags: UI changes become reviewable git commits. Free open source edition; Pro is a flat $200 per month with no per-seat fees.
Suggest a change
Related comparisons
-
Translation management softwareTranslation management systems (TMS) keep a team's UI strings, documents and translations in one place, with translation memory, glossaries, machine and human translation, and integrations with code and design tools. The decision is how you are charged (words, strings or keys), what a free plan covers, and how much automation and security you need.
-
Incident management softwareIncident management software wakes the right person when something breaks, gives the team one place to run the response, and records what happened so it doesn't happen again. This grid compares eight tools on what most buyers decide on: what the first paid plan really costs, whether on-call paging is included or sold separately, how well incidents run inside Slack or Teams, and how far AI goes.
-
Status page softwareStatus page software gives your customers one trusted place to see whether your service is up, read incident updates, and subscribe to alerts. Some tools are stand-alone status pages, while others bundle uptime monitoring, on-call paging, or full incident response. The trade-offs are price model (flat plan, per user, or per component), how many subscribers and team members each plan allows, and whether monitoring and paging come with it.
-
API management platformsAPI management platforms sit in front of your APIs to handle authentication, rate limits, analytics, a developer portal, and increasingly AI and MCP traffic. This grid compares seven well-known options on what you can see before talking to sales: entry price, free access, how pricing works, where it can run, and which capabilities come built in.
-
CI/CD platformsCI/CD platforms build, test, and ship your code automatically every time you push a change. The real decision is whether to use the pipeline built into the place where your code already lives, or an independent service, and how you want to pay: per user, per build minute, or with your own servers.
-
Low-code platformsLow-code platforms let teams build business apps, internal tools and workflows with visual builders and a little code instead of full software projects. The real decision is between developer-friendly tools you can self-host and enterprise platforms sold on custom quotes.