Flagsmith Self-Hosted
Feature management platform for targeted rollouts and remotely configured application behavior.
6 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
Flagsmith 2.292.0 request and authorization hardening
Flagsmith v2.292.0 adds SSRF allowlisting, corrects nested-write authorization scope, and updates a security dependency.
Scope: Upstream v2.292.0 release notes; no consolidated affected-version range is asserted.
Applicability depends on outbound request configuration, nested-resource writes, and the affected dependency.
Action: Upgrade to v2.292.0 or later, configure the SSRF allowlist, and retest nested writes.
Primary source · Reviewed 2026-11-18
What lands where
Supplied by
Vendor or project
Deploy the official Docker Compose environment and configure the dashboard/API, PostgreSQL and application SDK endpoints.
Runs in
Documented customer environment
Customer-operated dashboard and Django API with PostgreSQL persistence and optional processing services
- AWS: Customer cloud account
- Azure: Customer cloud account
- Google Cloud: Customer cloud account
- DigitalOcean: Boundary not confirmed
- AWS
- Azure
- Google Cloud
- DigitalOcean
Servers / containers
Operated by
Your team
Customer manages flag API availability, SDK endpoints, database, permissions, secrets, backups and upgrades.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Flagsmith self-hosted platform architecture ↗ · Source checked 2026-11-12
- Azure: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Flagsmith self-hosted platform architecture ↗ · Source checked 2026-11-12
- Google Cloud: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Flagsmith self-hosted platform architecture ↗ · Source checked 2026-11-12
- DigitalOcean: Boundary not confirmed · Customer-operated
Provider deployment is documented, but the reviewed evidence does not establish a more specific account or service boundary.
Flagsmith self-hosted platform architecture ↗ · Source checked 2026-11-12
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Deploy the official Docker Compose environment and configure the dashboard/API, PostgreSQL and application SDK endpoints. |
|---|---|
| Infrastructure | Servers / containers Customer-operated dashboard and Django API with PostgreSQL persistence and optional processing services. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support. |
| Licensing model | Open Source / Open Core BSD-3-Clause for upstream core functionality; supported Enterprise editions and commercial features have separate terms. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms. |
| License | BSD-3-Clause for upstream core functionality; supported Enterprise editions and commercial features have separate terms. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
6 of 12 fields researched (50%) · 6 documented · 0 unresolved. Evidence coverage is not a feature score.
- Single sign-on
Edition-dependentEvidence and scope for Single sign-on
The platform architecture identifies advanced authentication including Okta, LDAP, SAML and ADFS in Enterprise on-premises deployments. Confirm the licensed integration and protocol configuration for the chosen package.
Enterprise self-hosted/on-premises features · Source ↗ · Reviewed 2026-11-14
Edition-dependent · Editor reviewed.
- Security controls
DocumentedEvidence and scope for Security controls
Current advisory review: Flagsmith v2.292.0 adds SSRF allowlisting, corrects nested-write authorization scope, and updates a security dependency. Upgrade to v2.292.0 or later, configure the SSRF allowlist, and retest nested writes.
Upstream v2.292.0 release notes; no consolidated affected-version range is asserted. · Source ↗ · Reviewed 2026-11-18
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The official Docker guide downloads an upstream Compose environment for dashboard/API and supporting services. It is a local setup starting point; configure production secrets, network access, database persistence and edition requirements.
Upstream self-hosted deployment; not a provider support or production-readiness certification · Source ↗ · Deployment artifact ↗ (main (moving branch)) · Reviewed 2026-11-14
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The Kubernetes guide leaves resource requests/limits unset by default and recommends limits of 1 vCPU and 2 GB RAM per pod, subject to workload. PostgreSQL, evaluation/SSE traffic, replicas and any experimentation warehouse need separate capacity. These are pod limits, not a whole-host or HA minimum.
Official per-pod allocation guidance; database/warehouse and HA resources are separate · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
The published v2.292.0 core uses BSD 3-Clause terms. This does not include every Enterprise authentication, support or on-premises entitlement; choose the edition and agreement separately. Application/database hosting, SDK evaluation traffic, experimentation storage and operations have separate costs.
Published OSS core terms; commercial features and infrastructure are separate · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
Flagsmith v2.292.0 was published November 17, 2026. It adds SSRF allowlisting, corrects nested-write scope, adds organization audit-log UI, and updates dnspython for security.
Upstream Flagsmith self-hosted release · Source ↗ · Reviewed 2026-11-18
Documented · Editor reviewed.
Show all fields (6 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
The local Compose guide is an evaluation path requiring production hardening. Point SDKs to the self-hosted endpoint; experimentation can add warehouse and ingestion services with separate operational requirements. Flagsmith v2.291.0 fixes existing authentication tokens remaining valid after a password change or reset, an identities search that could bring down the database, a security update to oauthlib, and trust in compromised eMudhra certificate authorities. Self-hosted operators should upgrade so password changes invalidate existing dashboard tokens and the database-search safeguards are present. Flagsmith v2.292.0 adds SSRF allowlisting, scopes nested writes correctly, exposes organization audit logs, and updates dnspython for security. Review outbound destinations and nested-resource authorization after upgrading.
Community & maintenance
The project publishes frequent 2026 releases and a documented public development model. Its named Wistia case study describes production feature-flag adoption; the case study alone does not certify a self-hosted deployment boundary.
Category fit
- Feature management
- Feature flags, remote configuration, user targeting, segments and multivariate release control; advanced edition features are separate.
Compare within Feature management
- GrowthBook Self-HostedFeature flagging and experimentation platform with a self-operated application and SDKs.
- Railway
- Unleash Self-HostedFeature management and controlled application rollouts in your own environment.
- AWS
These products address related workflows; read their category-fit notes before comparing scope. See all of Feature management →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Official installation and runtime ↗docs.flagsmith.com
- Upstream project and capabilities ↗github.com
- Current upstream license ↗raw.githubusercontent.com
- Flagsmith v2.291.0 security and reliability fixes ↗github.com
- Password-change token revocation security issue ↗github.com
- Flagsmith v2.292.0 release ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Flagsmith self-hosted platform architecture ↗ · AWS, Azure, Google Cloud, DigitalOcean
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The vendor explicitly names AWS, Google Cloud, Azure and DigitalOcean for team-managed Docker or Kubernetes deployments. This is a self-hosted application compatibility statement, distinct from managed Flagsmith SaaS; configure the backing services, security and edition-specific entitlements.
- Flagsmith self-hosted platform architecture ↗ · AWS, Azure, Google Cloud, DigitalOcean
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Current releases ↗github.com
- Open-source development and core scope ↗www.flagsmith.com
- Named production adoption ↗www.flagsmith.com