● Beta — KubeEra is in active development. Profiles are live; AI-perception measurement is rolling out.
F

Flagsmith

Observability
Open source · BSD-3-Clause

Flagsmith is an open-source feature flag and remote config management platform. It lets engineering teams toggle features, run A/B tests, manage environment-specific config, and control rollout percentages without redeploying code.

updated 2026-07-01

What it is

Flagsmith is an open-source feature flag and remote config management platform. It lets engineering teams toggle features, run A/B tests, manage environment-specific config, and control rollout percentages without redeploying code. It ships SDKs for most major languages/frameworks and supports both a hosted SaaS version and full self-hosting. The core API and management service are written in Python (Django), with a separate Go-based edge proxy for low-latency flag evaluation at scale.

Note: it's categorized here under Observability and Analysis, but that's a loose fit — Flagsmith is fundamentally a feature management / progressive delivery tool, not a metrics or tracing system. Its "observability" angle is limited to flag change audit logs and basic usage analytics.

Who builds it and why

Flagsmith is built by Flagsmith Ltd, a company that sells hosted and enterprise self-hosted tiers on top of the open-source core — the standard open-core model. Founding details aren't publicly available in the data here, but the project has been actively maintained for years with a real commercial entity behind it, not a side project. 140 contributors and a steady release cadence (currently v2.251.0) indicate ongoing investment rather than a dormant OSS dump.

Production readiness signal

  • 6,430 GitHub stars — moderate adoption, smaller than LaunchDarkly-scale mindshare but a real, established user base.
  • Last commit 2026-07-01 — actively maintained, not abandoned.
  • 140 contributors — healthy for a project of this size; not a single-maintainer risk.
  • BSD-3-Clause license — permissive, no copyleft concerns for commercial use.
  • v2.251.0 — high version numbers suggest frequent incremental releases (common with CI/CD-driven semantic-ish versioning), which is generally a good sign for iteration speed but means you should pin versions and read changelogs before upgrading in production.
  • No CNCF maturity level — this isn't a CNCF project, so don't expect that governance/security bar. Evaluate it on its own merits.

Self-hosting Flagsmith means you own the uptime of a Postgres-backed Django service plus optional Go proxy — treat it like any other stateful internal service requiring monitoring, backups, and upgrade discipline.

Who should use this

  • Teams that want feature flags and remote config without vendor lock-in and are comfortable self-hosting.
  • Organizations with data residency or compliance requirements that rule out SaaS-only flag providers.
  • Python/Django-shops that want a stack they can debug and extend in-house.
  • Teams needing multi-environment, multi-project flag management with role-based access control at a lower price point than enterprise incumbents.

Who should NOT use this

  • Teams wanting a fully managed, zero-ops experience with deep enterprise SLAs — LaunchDarkly's SaaS maturity and support org are more built out.
  • Shops already deep in a cloud provider's native flagging (AWS AppConfig, Azure App Configuration) where adding another system increases operational surface area for marginal gain.
  • Anyone expecting true observability/tracing capability — this is not a substitute for Prometheus, Grafana, or an APM tool, despite the category label here.
  • Small teams with a handful of flags and no rollout complexity — a simple env-var or config-file approach is less operational overhead than running a flag service.
  • Teams unwilling to operate/patch a self-hosted Postgres + Django + Go stack if they choose self-host over SaaS.

Alternatives

  • LaunchDarkly — the enterprise incumbent, mature SaaS, deeper analytics and experimentation, but closed-source and pricier at scale.
  • Unleash — another open-source feature flag platform, similar open-core model, Node/Java-based, comparable self-hosting story.
  • AWS AppConfig / Azure App Configuration — cloud-native managed config services, good fit if you're already all-in on one cloud and don't need cross-cloud portability.

Pricing

Core Flagsmith is fully open source (BSD-3-Clause) and free to self-host with no feature gating on the base flagging/config functionality. Flagsmith Ltd sells a hosted SaaS tier and an enterprise self-hosted tier with SSO, advanced permissions, and support SLAs — exact pricing not publicly available in the data provided; check flagsmith.com for current tiers.

Frequently asked

What is Flagsmith?+
Flagsmith is an open-source feature flag and remote config management platform. It lets engineering teams toggle features, run A/B tests, manage environment-specific config, and control rollout percentages without redeploying code.
Who builds Flagsmith?+
Flagsmith is built by Flagsmith Ltd, a company that sells hosted and enterprise self-hosted tiers on top of the open-source core — the standard open-core model.
Is Flagsmith production ready?+
6,430 GitHub stars — moderate adoption, smaller than LaunchDarkly-scale mindshare but a real, established user base. Last commit 2026-07-01 — actively maintained, not abandoned. 140 contributors — healthy for a project of this size; not a single-maintainer risk.
Who should use Flagsmith?+
Teams that want feature flags and remote config without vendor lock-in and are comfortable self-hosting. Organizations with data residency or compliance requirements that rule out SaaS-only flag providers. Python/Django-shops that want a stack they can debug and extend in-house.
Who should not use Flagsmith?+
Teams wanting a fully managed, zero-ops experience with deep enterprise SLAs — LaunchDarkly's SaaS maturity and support org are more built out.
What are the alternatives to Flagsmith?+
LaunchDarkly — the enterprise incumbent, mature SaaS, deeper analytics and experimentation, but closed-source and pricier at scale. Unleash — another open-source feature flag platform, similar open-core model, Node/Java-based, comparable self-hosting story.
How much does Flagsmith cost?+
Core Flagsmith is fully open source (BSD-3-Clause) and free to self-host with no feature gating on the base flagging/config functionality.