flagsmith/flagsmith

Flagsmith is an open-source feature flag platform with remote config, experimentation, and self-hosted or cloud deployment options.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 9 minutes ago
Added to GitGenius on September 10th, 2026
Created on June 5th, 2018
Open Issues & Pull Requests: 706 (+0)
GitHub issues: Enabled
Number of forks: 565
Total Stargazers: 6,548 (+0)
Total Subscribers: 35 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 23.5 hours
Mean response time: 29.5 days
90th percentile: 77.0 days
Tracked items: 1,191

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 73% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "feature" is answered fastest, typically in under an hour, while "docs" waits about 8 days. 58% of tracked open issues have had no activity in three months. Only 9% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 488
New in 7 days: 11
Closed in 7 days: 9
Avg open age: 363 days
Stale 30+ days: 426
Stale 90+ days: 348

Recent activity

Opened in 7 days: 11
Closed in 7 days: 9
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • api (236)
  • front-end (233)
  • bug (192)
  • feature (65)
  • improvement (63)
  • tech-debt (48)
  • good first issue (41)
  • docs (30)

Detailed Description

Flagsmith is a feature flagging and remote configuration service that allows teams to control feature rollouts and configuration changes without redeploying code.

Feature flags let developers decouple feature releases from deployments, enabling gradual rollouts, A/B testing, and instant feature toggles in production. Flagsmith provides a centralized platform to manage these flags and remote configuration values across applications. Teams define flags in a dashboard, set targeting rules based on user attributes or segments, and applications query the service to determine which features are enabled for each user. The service supports multivariate testing, allowing different flag values to be returned based on conditions, and can be self-hosted or used through a managed cloud offering.

Flagsmith suits teams building applications where feature control and experimentation matter: those practicing continuous deployment who want to decouple releases from feature availability, teams running A/B tests, and organizations needing to manage configuration across multiple environments without code changes. Self-hosting appeals to teams with strict data residency requirements or those wanting to avoid external dependencies. The hosted version removes infrastructure overhead for teams comfortable with a managed service. Developers should evaluate whether their deployment workflow benefits from flag-driven feature control and whether the overhead of maintaining a flagging service justifies the operational flexibility it provides.

The project maintains active development across its core platform and SDKs. The codebase shows consistent updates to the Python backend and supporting client libraries. The team addresses issues and pull requests regularly, indicating responsive maintenance. Documentation is kept current alongside feature additions. The project demonstrates engagement with the open source community through participation in community initiatives and responsiveness to user contributions.