Flagsmith Documentation
website·Indexed 36 days ago
https://docs.flagsmith.com/Documentation for Flagsmith, a feature flag management platform. Includes guides on client-side and server-side SDKs, Management and Flags APIs, OpenFeature providers, and self-hosting deployment options via Docker, Kubernetes, Helm, and various cloud providers. Covers feature versioning, A/B testing experimentation, and core concepts like segments and organizations.
What's inside Flagsmith
- Feature Health allows you to monitor observability metrics within Flagsmith. When a supported observability provider sends alert notifications, Flagsmith can mark specific features (and optionally environments) as 'unhealthy'. This provides teams with immediate visibility into feature regressions or failures to assist in quick response and decision-making.
Overview of self-hosting Flagsmith
Self-hosting Flagsmith allows organizations to run the complete platform within their own infrastructure. This provides full control over data sovereignty, custom integrations, security policies, and the ability to operate in offline environments with limited or no internet access.Overview of Flagsmith SCIM 2.0 capabilities
Flagsmith uses the SCIM 2.0 protocol to automate user and group provisioning from an identity provider (IdP). This allows for the creation of users before their first login, automatic deactivation/removal of users, and synchronization of group memberships. SCIM handles provisioning (who exists and their permissions), while SSO handles authentication (how they log in).
Supported Features:
- Creating, deleting, and updating users (via the
activeattribute). - Creating, updating, and deleting permission groups and their memberships.
- Filtering and pagination on
/Usersand/Groupsendpoints.
Unsupported Features:
- Profile sourcing,
/Me,/Bulk, sorting, and ETag concurrency control.
- Creating, deleting, and updating users (via the
Overview of Flagsmith Experimentation
Flagsmith Experimentation allows for end-to-end A/B testing by serving feature variations via multivariate flags, collecting application events into a managed data warehouse, and analyzing results using a built-in Bayesian statistics engine. Experiments are scoped to a specific environment. This feature is currently in beta for Enterprise plans.Overview of Flagsmith Release Pipelines
Release Pipelines automate the feature flag deployment process by defining a sequence of stages that flags progress through. They allow for automated rollouts to specific environments and audiences, reducing manual effort and risk by standardizing release protocols and providing visibility into flag progress. Note: This feature is currently in closed beta; contact support@flagsmith.com for access.Overview of Flagsmith Cohort Synchronisation
Cohort synchronisation allows you to target feature flags at groups of users defined outside of Flagsmith. These groups are imported as segments that can be used for feature overrides. This is particularly useful for targeting power users identified by analytics platforms or customer lists from a CRM.
Key constraints:
- Available only on paid plans.
- Synchronised segments are scoped to a single environment. If you need the same group in multiple environments, you must set up the segment separately for each.
- Membership is matched by identity identifier; the external source must use the same identifier value as your Flagsmith application.
- Membership is owned by the source; you cannot edit the rules of a synchronised segment within Flagsmith.
Overview of the Flagsmith Management API
The Flagsmith Management API allows developers to programmatically manage projects, environments, features, segments, and users. Any action available in the Flagsmith dashboard can be performed via this API. It is intended for automation, integrations, and custom workflows. Access is governed by the permissions of the API key or user making the request, meaning any organization member can use the API within their assigned RBAC scope.Overview of Flagsmith Edge Proxy
The Flagsmith Edge Proxy is a self-hosted service that runs an instance of the Flagsmith Engine close to your servers to provide low-latency feature flags. It functions as a lightweight Docker container that acts as a local cache and an API interface compatible with Flagsmith SDKs. It connects to the Flagsmith API (either the hostededge.api.flagsmith.comor a self-hosted instance) to retrieve environment flags and segment rules, reducing the number of polling requests made directly to the Core API.Overview of the Flagsmith MCP Server
The Flagsmith MCP Server allows AI assistants and agents (such as Claude Code, Claude Desktop, Cursor, and Codex) to programmatically manage feature flags, segments, multivariate options, and release workflows via the Model Context Protocol. It supports both remote (Streamable HTTP) connections and local subprocesses (stdio).Overview of Flagsmith OpenTelemetry events
The Flagsmith backend emits OpenTelemetry events that can be ingested into downstream observability systems or data warehouses via OTLP. These events provide visibility into system behavior, billing, cohort management, and experimentation.Stay notified about Flagsmith updates
To receive the latest updates and release notifications, you can use the following channels:
- GitHub: Watch the Flagsmith repository.
- Discord: Join the Discord community.
- Blog: Follow the Flagsmith blog for major announcements.
- Email: Subscribe to the official newsletter.
Monitor feature flag changes via the Flagsmith Slack Bot
Once the Slack integration is configured, the Flagsmith Bot automatically monitors the selected environments. It will post a message to the designated Slack channel detailing the changes whenever a flag is created, updated, or deleted.