Flagsmith
Feature flag platform meets developers where they already work — Backstage, GitHub, Sentry — while adding governance for larger teams.
◆Recent moves
- 3mo ago
Backstage Plugin
First-party Backstage plugin surfaces flag tables, entity-overview summaries, and usage charts inside the developer portal. Continues the recurring move to show Flagsmith data where developers already are — Backstage joins GitHub references and Sentry as native integration surfaces.
View source ↗ - 4mo ago
GitHub Code References
A GitHub Action scans repos inside the customer's own runner and pushes flag references to Flagsmith — source code never leaves the customer environment. Closes the where-is-this-flag-used question without forcing teams to hand source over to a SaaS. Privacy-conscious framing fits the enterprise lean.
View source ↗ - 8mo ago
Change Requests for Segments
Segment edits can now require team approval, mirroring the existing feature-change-request flow. Governance feature targeting larger teams that already gate features but had a hole around segment changes.
View source ↗ - 10mo ago
User Segmentation Improvements
Three additions to segmentation: percentage-based rollout across tenants, companies, or device types; per-environment restriction of segment evaluation; and pre-defined keys as traits. Real depth for multi-tenant SaaS customers running staged rollouts.
View source ↗ - 0y ago
Sentry Integration
Native Sentry integration tracks feature-flag changes alongside error events — letting teams correlate a flag toggle with an error spike. Same theme as the later Backstage plugin: bring Flagsmith into surfaces developers already monitor.
View source ↗ - 0y ago
Environment Metrics
New Environment Metrics summary surfaces feature, segment, and override counts on the environment dashboard. Modest but answers the what-is-actually-happening-in-this-environment question without scripting a query.
View source ↗