Skip to content
ProductArena

Rank #1 of 5 in Feature Flags & Experimentation

Flagsmith logo

Flagsmith

Open Source

Flagsmith (Bullet Train Ltd)

flagsmith.com ↗Try it →
PA Score42/100AGENT-READY60/100BUILT-IN AI19/100API6/100
MCP✓CLI✓API✓
★ 6.5k▲ 791/yrnpm 113.7k/wk★ +12npm/wk -47.5kpypi/wk +34.7k
ArenasFeature Flags & Experimentation#1/5

Access

Open app ↗API docs ↗CLI docs ↗MCP docs ↗

Install

dockerdocker-compose -f docker-compose.yml up
pippip install flagsmith
npmnpm install flagsmith

Compare head-to-head

LaunchDarkly logovs LaunchDarklyStatsig logovs StatsigGrowthBook logovs GrowthBookUnleash logovs Unleash

Alternatives to Flagsmith →

Showcase

Flagsmith homepage screenshot
homepage · captured Sep 2026 · view live ↗
Flagsmith docs screenshot
docs · captured Sep 2026 · view live ↗

Try itExperimental

See what an agent can do with Flagsmith before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; the live MCP handshake runs real requests from our edge, right now — including, where the server allows it, one real read-only tool call (bring your own key for auth-gated servers); sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).

$docker run -d postgres:16-alpine && docker run -d -p 18000:8000 flagsmith/flagsmith && POST /api/v1/auth/users/ && POST /organisations/ && POST /projects/ && POST /environments/ && POST /features/ {pa_probe_flag} && curl /api/v1/flags/ -H "X-Environment-Key: <key>"recorded session — replayed, not live
recorded 2026-09-05 · exit 0 · captured verbatim by our probe harness, secrets redacted

Verified integrations

Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.

React logoReactFrontend Frameworks

By theme — the product's score on each story themeBy theme

Agenticness — how well agents can access and operate the productAgenticnessevidence →

How well agents can access and operate the product

38.0/100

Automation depth — how much of the product can run unattendedAutomation depthevidence →

How much of the product can run unattended

37.3/100

Deployment self host — stories about deployment self host in this arenaDeployment self hostevidence →

Stories about deployment self host in this arena

87.5/100

Experimentation — stories about experimentation in this arenaExperimentationevidence →

Stories about experimentation in this arena

39.0/100

Flag management — stories about flag management in this arenaFlag managementevidence →

Stories about flag management in this arena

74.6/100

Governance audit — stories about governance audit in this arenaGovernance auditevidence →

Stories about governance audit in this arena

84.5/100

Openness — open source, data portability, and self-hosting storiesOpennessevidence →

Open source, data portability, and self-hosting stories

72.8/100

Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plansevidence →

Plan structure and value — what each tier costs and what it unlocks

0.0/100

Privacy posture — data-handling and privacy storiesPrivacy postureevidence →

Data-handling and privacy stories

33.0/100

Rollouts releases — stories about rollouts releases in this arenaRollouts releasesevidence →

Stories about rollouts releases in this arena

60.0/100

Sdk delivery — stories about sdk delivery in this arenaSdk deliveryevidence →

Stories about sdk delivery in this arena

15.9/100

Story verdicts — every judged story with its evidenceStory verdicts

?

Sorted by importance (agentic first) (high → low) · 54/54 stories · click a row’s chevron for the rationale and evidence

Connect an agent via an official MCP server G

Agent access

ai-native userAgenticness — how well agents can access and operate the productAgenticness3full9/10T

Drive the product through a documented public API G

Agent access

ai-native userAgenticness — how well agents can access and operate the productAgenticness3full8/10T

Delegate tasks to a built-in AI assistant inside the product G

Agentic features

ai-native userAgenticness — how well agents can access and operate the productAgenticness3none0/10

Plug MCP servers into this product so it can use their tools G

Agent access

ai-native userAgenticness — how well agents can access and operate the productAgenticness3n/auntestednone yet

Run the product headlessly / in CI for automation G

Agent access

ai-native userAgenticness — how well agents can access and operate the productAgenticness2full8/10T

Use an official CLI G

Agent access

ai-native userAgenticness — how well agents can access and operate the productAgenticness2full8/10T

Operate the product with natural-language commands G

Agentic features

ai-native userAgenticness — how well agents can access and operate the productAgenticness2partial7/10T

Set up automations that run autonomously in the background G

Agentic features

ai-native userAgenticness — how well agents can access and operate the productAgenticness2partial7/10T

Build against official SDKs G

Agent access

ai-native userAgenticness — how well agents can access and operate the productAgenticness2partial6/10C

Issue scoped/least-privilege API credentials for an agent G

Agent access

ai-native userAgenticness — how well agents can access and operate the productAgenticness2partial5/10T

Point an agent at llms.txt or agent-oriented docs G

Agent access

ai-native userAgenticness — how well agents can access and operate the productAgenticness2partial5/10T

Subscribe to events via webhooks G

Agent access

ai-native userAgenticness — how well agents can access and operate the productAgenticness2partial5/10C

Download a machine-readable API spec (OpenAPI or equivalent) G

Api quality

ai-native userAgenticness — how well agents can access and operate the productAgenticness2none0/10

Explore an interactive API reference with runnable examples G

Api quality

ai-native userAgenticness — how well agents can access and operate the productAgenticness2none0/10

Get AI-generated insights and suggestions from my data inside the product G

Agentic features

ai-native userAgenticness — how well agents can access and operate the productAgenticness2none0/10

Rely on versioned APIs with a documented deprecation policy G

Api quality

ai-native userAgenticness — how well agents can access and operate the productAgenticness2none0/10

Test against a sandbox environment without touching production data G

Api quality

ai-native userAgenticness — how well agents can access and operate the productAgenticness1partial7/10T

Self-host the core product G

ai-native userOpenness — open source, data portability, and self-hosting storiesOpenness3full10/10T

Create a feature flag and toggle it live in production within minutes of signing up C

Flags

developerFlag management — stories about flag management in this arenaFlag management3full9/10T

Every flag change is recorded in an audit log — who changed what, when, and to which value G

Audit

platform engineerGovernance audit — stories about governance audit in this arenaGovernance audit3full9/10C

Require approvals or change requests before production flag changes go live C

Approvals

platform engineerGovernance audit — stories about governance audit in this arenaGovernance audit3full9/10C

Roll a flag out progressively by percentage with consistent bucketing, ramping from 1% to 100% without redeploying C

Rollouts

developerRollouts releases — stories about rollouts releases in this arenaRollouts releases3full9/10T

Self-host the full flag platform from an open-source distribution, keeping evaluation data on my infrastructure C

Self host

platform engineerDeployment self host — stories about deployment self host in this arenaDeployment self host3full9/10T

Target flags with attribute-based rules and reusable segments so the right users see the right variation C

Targeting

developerFlag management — stories about flag management in this arenaFlag management3full9/10T

Create and toggle flags through documented APIs, CLIs, or MCP — and the platform can force my changes through approval workflows instead of letting me write to production unreviewed C

Agent ops

ai agentGovernance audit — stories about governance audit in this arenaGovernance audit3full7/10T

Run A/B and multivariate experiments on flags and see which variation wins on my metrics C

Experiments

product managerExperimentation — stories about experimentation in this arenaExperimentation3full7/10C

Define rules that trigger actions automatically on events G

ai-native userAutomation depth — how much of the product can run unattendedAutomation depth3partial6/10C

Export all of my data in open formats and leave G

ai-native userOpenness — open source, data portability, and self-hosting storiesOpenness3partial6/10T

My server SDKs evaluate flags locally from a cached ruleset — microsecond decisions with no network call per flag check C

Evaluation

platform engineerSdk delivery — stories about sdk delivery in this arenaSdk delivery3disputed3/10D

Prevent my data from being used to train AI models G

ai-native userPrivacy posture — data-handling and privacy storiesPrivacy posture3n/auntestednone yet

Do everything through the API that I can do in the UI G

ai-native userOpenness — open source, data portability, and self-hosting storiesOpenness2full9/10T

Restrict who can change which flags with roles, permissions, and scoped API tokens C

Access

platform engineerGovernance audit — stories about governance audit in this arenaGovernance audit2full9/10C

Serve multivariate flags and dynamic configuration values (strings, numbers, JSON), not just booleans C

Flags

developerFlag management — stories about flag management in this arenaFlag management2full9/10T

Manage separate environments (dev/staging/prod) with independent flag states and scoped SDK keys C

Environments

developerFlag management — stories about flag management in this arenaFlag management2full8/10T

Read the product's source under an open license G

ai-native userOpenness — open source, data portability, and self-hosting storiesOpenness2full7/10C

Choose where my data is stored (region/residency) G

ai-native userPrivacy posture — data-handling and privacy storiesPrivacy posture2partial6/10T

Perform bulk operations across many items at once G

ai-native userAutomation depth — how much of the product can run unattendedAutomation depth2partial6/10T

Trust a documented statistics engine (Bayesian or frequentist, with variance-reduction options) behind experiment results C

Analysis

product managerExperimentation — stories about experimentation in this arenaExperimentation2partial6/10C

Use official SDKs across my whole stack — backend, web, and mobile — with consistent flag behavior C

Sdks

developerSdk delivery — stories about sdk delivery in this arenaSdk delivery2partial6/10X

Control data retention and deletion G

ai-native userPrivacy posture — data-handling and privacy storiesPrivacy posture2partial5/10C

Evaluate flags at the edge (CDN workers or an edge/relay layer) close to users C

Edge

platform engineerSdk delivery — stories about sdk delivery in this arenaSdk delivery2partial5/10X

Schedule recurring jobs or workflows G

ai-native userAutomation depth — how much of the product can run unattendedAutomation depth2partial4/10C

Define experiment metrics from my own data — warehouse tables or ingested events — instead of a black-box metric store C

Metrics

product managerExperimentation — stories about experimentation in this arenaExperimentation2none0/10

Flag changes propagate to connected SDKs in seconds via streaming or fast polling — a kill switch actually kills C

Streaming

developerSdk delivery — stories about sdk delivery in this arenaSdk delivery2none0/10

Guard a rollout with metrics so a regression is detected and the release is rolled back automatically C

Rollouts

platform engineerRollouts releases — stories about rollouts releases in this arenaRollouts releases2none0/10

See published pricing and understand what drives cost (seats, MAUs, events, requests) before committing G

Pricing

product managerPricing plans — plan structure and value — what each tier costs and what it unlocksPricing plans2none0/10

Find stale flags and code references so temporary flags actually get removed from the codebase C

Lifecycle

platform engineerFlag management — stories about flag management in this arenaFlag management2noneuntestednone yet

Opt out of telemetry and usage tracking G

ai-native userPrivacy posture — data-handling and privacy storiesPrivacy posture2n/auntestednone yet

Schedule flag changes and releases to happen at a specific future time C

Scheduling

developerRollouts releases — stories about rollouts releases in this arenaRollouts releases1full9/10C

Target or exclude specific individual users for a flag (allowlists, beta testers, internal accounts) C

Targeting

developerFlag management — stories about flag management in this arenaFlag management1full9/10C

Run a relay/edge proxy so flags stay served when the vendor is unreachable and SDK traffic stays inside my network C

Proxy

platform engineerDeployment self host — stories about deployment self host in this arenaDeployment self host1full8/10C

Version, review, and roll back my automations G

ai-native userAutomation depth — how much of the product can run unattendedAutomation depth1full7/10C

Read experiment configurations and results programmatically to summarize outcomes and recommend ship/rollback decisions C

Agent ops

ai agentExperimentation — stories about experimentation in this arenaExperimentation1partial5/10T

Use the vendor through OpenFeature providers so my flag code isn't locked to one vendor's SDK API C

Standards

platform engineerSdk delivery — stories about sdk delivery in this arenaSdk delivery1noneuntestednone yet

Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 28 stories with headroom

What would move Flagsmith’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.

  1. Agenticness — how well agents can access and operate the productDelegate tasks to a built-in AI assistant inside the product

    nonemoves Built-in AIimpact 45

    Flagsmith exposes an MCP server so external AI agents can call its Admin API, and calls its automated release pipeline an 'intelligent release assistant,' but neither is a built-in AI assistant inside the Flagsmith product that a user can converse with or delegate tasks to — the MCP server is a server-side integration point for external agents, not a first-party in-app assistant.

  2. Agenticness — how well agents can access and operate the productGet AI-generated insights and suggestions from my data inside the product

    nonemoves Built-in AIimpact 30

    Flagsmith provides an MCP server for external AI agents to call its Admin API (docs-17/29) and a 'release pipeline' described as an 'intelligent release assistant' (docs-37), but this is rule-based automation and API access, not evidence of the product itself generating AI insights or suggestions from data (e.g., anomaly detection, usage analysis, recommended flags/segments).

  3. Agenticness — how well agents can access and operate the productExplore an interactive API reference with runnable examples

    nonemoves API qualityimpact 30

    The evidence pack explicitly shows probes for an OpenAPI/Swagger spec and llms.txt returning 404s, and no citation describes an interactive, runnable API reference (e.g., Swagger UI, Postman collection, or live code playground).

  4. Agenticness — how well agents can access and operate the productDownload a machine-readable API spec (OpenAPI or equivalent)

    nonemoves API qualityimpact 30

    Flagsmith documents a full Admin API and CLI/MCP integrations, but explicit probes for a machine-readable spec (openapi.json, swagger.json, .well-known/openapi.json) all returned 404, and no evidence pack item points to a downloadable OpenAPI/Swagger spec.

  5. Agenticness — how well agents can access and operate the productRely on versioned APIs with a documented deprecation policy

    nonemoves API qualityimpact 30

    Missing: any statement of API versioning strategy, deprecation timelines, or migration guides for breaking changes.

  6. Rollouts releases — stories about rollouts releases in this arenaGuard a rollout with metrics so a regression is detected and the release is rolled back automatically

    nonemoves PA Scoreimpact 20

    Flagsmith documents percentage rollouts, scheduled flags, and Release Pipelines with 'triggers and actions,' plus an Experimentation module with Bayesian stats — but none of the evidence describes automatic metric-based regression detection that triggers an automatic rollback of a release.

  7. Experimentation — stories about experimentation in this arenaDefine experiment metrics from my own data — warehouse tables or ingested events — instead of a black-box metric store

    nonemoves PA Scoreimpact 20

    Flagsmith's experimentation feature explicitly funnels events into its own 'managed data warehouse' and evaluates them via a built-in Bayesian engine, the opposite of letting a PM define metrics from their own warehouse tables or ingested events — there is no evidence of BYO-warehouse or custom event-source metric definition.

  8. Sdk delivery — stories about sdk delivery in this arenaFlag changes propagate to connected SDKs in seconds via streaming or fast polling — a kill switch actually kills

    nonemoves PA Scoreimpact 20

    Missing: documented real-time/streaming SDK update mechanism, polling interval specs, and evidence of kill-switch propagation latency.

Showing the top 8 of 28 — every none/partial verdict in the story verdicts table is headroom.

Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.

Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map13 surfaces · 40 covered stories

Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.

Deployment self hosting docs17 stories

Integrating with flagsmith docs16 stories

Managing flags docs12 stories

Administration and security docs11 stories

GitHub README6 stories

Experimentation docs4 stories

Performance docs4 stories

OpenAPI spec3 stories

Hacker News3 stories

docs.flagsmith.com3 stories

llms.txt2 stories

Flagsmith concepts docs2 stories

Pricing docs1 story

Probe proofs — replayable recordings from the probe harnessProbe proofs

Replayable recordings from our probe harness — see the Prove-It protocol to submit one.

$docker run -d postgres:16-alpine && docker run -d -p 18000:8000 flagsmith/flagsmith && POST /api/v1/auth/users/ && POST /organisations/ && POST /projects/ && POST /environments/ && POST /features/ {pa_probe_flag} && curl /api/v1/flags/ -H "X-Environment-Key: <key>"reproduced
$ docker run -d postgres:16-alpine && docker run -d -p 18000:8000 flagsmith/flagsmith && POST /api/v1/auth/users/ && POST /organisations/ && POST /projects/ && POST /environments/ && POST /features/ {pa_probe_flag} && curl /api/v1/flags/ -H "X-Environment-[redacted]: <[redacted]>"
HTTP/1.1 200 OK

env [redacted]: Gj2V3EBcYavE98vaWQHVxx
{"id":1,"name":"pa_probe_flag","type":"STANDARD","default_enabled":true,"initial_value":null,"created_date":"2026-09-05T
[{"id":1,"feature":{"id":1,"name":"pa_probe_flag","created_date":"2026-09-05T05:01:29.235712Z","description":null,"initial_value":null,"default_enabled":true,"type":"STANDARD"},"feature_state_value":null,"environment":1,"identity":null,"feature_segment":null,"enabled":true}]
proves: Self-host the full flag platform from an open-source distribution, keeping evaluation data on my infrastructureproves: Self-host the core productproves: Create and toggle flags through documented APIs, CLIs, or MCP — and the platform can force my changes through approval workflows instead of letting me write to production unreviewedrecorded 2026-09-05
$curl -si -X POST https://mcp.flagsmith.com -H 'Content-Type: application/json' -d '<jsonrpc initialize>'reproduced
$ curl -si -X POST https://mcp.flagsmith.com -H 'Content-Type: application/json' -d '<jsonrpc initialize>'
HTTP/2 401

date: Sat, 05 Sep 2026 05:01:10 GMT

content-type: application/json

content-length: 301

server: uvicorn

www-authenticate: Bearer error="invalid_[redacted]", error_description="Authentication failed. The provided bearer [redacted] is invalid, expired, or no longer recognized by the server. To resolve: clear authentication [redacted]s in your MCP client and reconnect. Your client should automatically re-register and obtain new [redacted]s.", resource_metadata="https://mcp.flagsmith.com/.well-known/oauth-protected-resource"

{"error": "invalid_[redacted]", "error_description": "Authentication failed. The provided bearer [redacted] is invalid, expired, or no longer recognized by the server. To resolve: clear authentication [redacted]s in your MCP client and reconnect. Your client should automatically re-register and obtain new [redacted]s."}
proves: Connect an agent via an official MCP serverproves: Create and toggle flags through documented APIs, CLIs, or MCP — and the platform can force my changes through approval workflows instead of letting me write to production unreviewedrecorded 2026-09-05

Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence

12 of 24 testable claims verified · 1 contradicted → integrity 42/100

32 distinct capability claims found in Flagsmith’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.

12

Verified

11

Unverified

1

Contradicted

16

Undersold

Verified (14)
Unverified (13)
Contradicted (1)
Undersold (16)
Claims outside our story set (5)

Real capability claims found in Flagsmith’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.

  • “SAML/SSO authentication support for login”

    source ↗

  • “Two-Factor Authentication (2FA) available for account security”

    source ↗

  • “Mark flags as protected to prevent accidental deletion”

    source ↗

  • “Mark a flag as server-side only so it can't be accessed by client-side SDKs”

    source ↗

  • “Environment Key is a public, non-secret key safe to expose in client-side code”

    source ↗
Suggest a story for these →

Business model

open-sourcefree-tierusage-basedenterprise-custom

BSD-3 open-source core you can self-host free; SaaS has a free tier then request-volume-based Start-Up pricing and custom Enterprise (SaaS, private cloud, or on-prem).

pricing ↗

Score trend

How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.

PA Scoretracked since Sep 5 '26 — no movement recorded yet
Agent-readytracked since Sep 5 '26 — no movement recorded yet

Try Experimental

Run it in the microterminal →

Recorded agent sessions — and a live MCP handshake where the vendor ships one.

Flag

⚑ Flag a verdict

Think a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.

Badge

Embed this product's score badge →

Hotlinked SVG — always shows the live current score.

For agents

This page as markdown/llms.txt

Data

Evidence (JSON)Verdicts (JSON)

Agent surface uptime MCP 100% (30d, checked every 6h since Sep 8 '26)