
# Feature management

Feature flags, rollout controls and application activation strategies.

Canonical page: https://launchinyourcloud.com/categories/feature-management/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


Feature flags, rollout controls and application activation strategies.

3 listings.


## Flagsmith Self-Hosted

Feature management platform for targeted rollouts and remotely configured application behavior.

- Listing: https://launchinyourcloud.com/directory/flagsmith/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: BSD-3-Clause for upstream core functionality; supported Enterprise editions and commercial features have separate terms.
- Licensing model: open-source
- Installation: Deploy the official Docker Compose environment and configure the dashboard/API, PostgreSQL and application SDK endpoints.
- Architecture: Customer-operated dashboard and Django API with PostgreSQL persistence and optional processing services
- Operations: Customer manages flag API availability, SDK endpoints, database, permissions, secrets, backups and upgrades.
- Product website: https://www.flagsmith.com/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

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.

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.


### Category fit

- feature-management: Feature flags, remote configuration, user targeting, segments and multivariate release control; advanced edition features are separate.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.flagsmith.com/flagsmith-concepts/platform-architecture (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.flagsmith.com/flagsmith-concepts/platform-architecture (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.flagsmith.com/flagsmith-concepts/platform-architecture (checked 2026-11-12). 

- digitalocean: Boundary not confirmed; Customer-operated; control plane: not-assessed. Source: https://docs.flagsmith.com/flagsmith-concepts/platform-architecture (checked 2026-11-12). 


### Cloud deployment evidence

- Flagsmith self-hosted platform architecture (aws, azure, gcp, digitalocean): https://docs.flagsmith.com/flagsmith-concepts/platform-architecture
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and 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.

Reviewed 2026-11-10.

- Current releases: https://github.com/Flagsmith/flagsmith/releases

- Open-source development and core scope: https://www.flagsmith.com/open-source

- Named production adoption: https://www.flagsmith.com/case-studies/wistia

### Sources

- Official installation and runtime: https://docs.flagsmith.com/deployment-self-hosting/hosting-guides/docker

- Upstream project and capabilities: https://github.com/Flagsmith/flagsmith

- Current upstream license: https://raw.githubusercontent.com/Flagsmith/flagsmith/main/LICENSE.md

- Flagsmith v2.291.0 security and reliability fixes: https://github.com/Flagsmith/flagsmith/releases/tag/v2.291.0

- Password-change token revocation security issue: https://github.com/Flagsmith/flagsmith/issues/8651

- Flagsmith v2.292.0 release: https://github.com/Flagsmith/flagsmith/releases/tag/v2.292.0

### Licensing sources

- https://raw.githubusercontent.com/Flagsmith/flagsmith/main/LICENSE.md

### Infrastructure sources

- https://docs.flagsmith.com/deployment-self-hosting/hosting-guides/docker


### Buyer diligence


Research coverage: 6/12 fields (50%); 6 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. 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. Scope: Enterprise self-hosted/on-premises features. Source: https://docs.flagsmith.com/flagsmith-concepts/platform-architecture (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. 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. Scope: Upstream v2.292.0 release notes; no consolidated affected-version range is asserted.. Source: https://github.com/Flagsmith/flagsmith/releases/tag/v2.292.0 (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. 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. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.flagsmith.com/deployment-self-hosting/hosting-guides/docker (reviewed 2026-11-14). Deployment artifact: https://raw.githubusercontent.com/Flagsmith/flagsmith/main/docker-compose.yml. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. 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. Scope: Official per-pod allocation guidance; database/warehouse and HA resources are separate. Source: https://docs.flagsmith.com/deployment-self-hosting/hosting-guides/kubernetes-openshift (reviewed 2026-11-20).

- License pricing: Documented. 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. Scope: Published OSS core terms; commercial features and infrastructure are separate. Source: https://github.com/Flagsmith/flagsmith/blob/v2.292.0/LICENSE.md (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. 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. Scope: Upstream Flagsmith self-hosted release. Source: https://github.com/Flagsmith/flagsmith/releases/tag/v2.292.0 (reviewed 2026-11-18).




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- Flagsmith 2.292.0 request and authorization hardening (security-advisory): 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. Conditions: 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. Source: https://github.com/Flagsmith/flagsmith/releases/tag/v2.292.0; reviewed 2026-11-18.




## GrowthBook Self-Hosted

Feature flagging and experimentation platform with a self-operated application and SDKs.

- Listing: https://launchinyourcloud.com/directory/growthbook/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT Expat for core code; specified enterprise directories use the GrowthBook Enterprise License.
- Licensing model: open-source
- Installation: Run the documented Docker Compose application and MongoDB-compatible database; configure production storage and credentials.
- Architecture: Customer-operated Next.js/Express application and statistics engine with MongoDB-compatible metadata storage
- Operations: Customer manages application availability, metadata database, SDK configuration, identity, data connections, backups and upgrades.
- Product website: https://www.growthbook.io/
- Source review: 2026-11-17; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-17

### Scope and qualifications

The bundled MongoDB service is a development/staging starting point. Warehouse connections, event tracking and managed database services can cross account boundaries; enterprise-only functionality is not included by the core license. GrowthBook v5.2.1 is a security patch release recommended for all self-hosted users. It updates zlib and multiple dependencies with known vulnerabilities and removes super-linear regular-expression backtracking.

MIT Expat for core code; specified enterprise directories use the GrowthBook Enterprise License. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated Next.js/Express application and statistics engine with MongoDB-compatible metadata storage. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support. Building the v5.2.1 image from source downloads zlib through github.com and release-assets.githubusercontent.com; environments with egress allowlists must permit both hosts.


### Category fit

- feature-management: Feature flags and experiment configuration with SDK-based feature evaluation and separately configured data-source analysis.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/growthbook (checked 2026-11-12). 


### Cloud deployment evidence

- GrowthBook community deployment template on Railway (railway): https://railway.com/deploy/growthbook
  This community template deploys the upstream growthbook/growthbook application image with MongoDB in a customer Railway project. Configure distinct frontend and API origins and preserve database/uploads. This is a community deployment path rather than a GrowthBook support commitment or GrowthBook Cloud subscription.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The upstream release history credits many named contributors, including first-time contributions across successive releases, and documents continued maintenance of self-hosted images.

Reviewed 2026-11-10.

- Release maintenance and contributor credits: https://github.com/growthbook/growthbook/releases

- Public upstream project: https://github.com/growthbook/growthbook

### Sources

- Official installation and runtime: https://docs.growthbook.io/self-host

- Upstream project and capabilities: https://github.com/growthbook/growthbook

- Current upstream license: https://raw.githubusercontent.com/growthbook/growthbook/main/LICENSE

- GrowthBook v5.2.1 security patch and build changes: https://github.com/growthbook/growthbook/releases/tag/v5.2.1

### Licensing sources

- https://raw.githubusercontent.com/growthbook/growthbook/main/LICENSE

### Infrastructure sources

- https://docs.growthbook.io/self-host

- https://github.com/growthbook/growthbook/releases/tag/v5.2.1


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. Enterprise SSO is documented for self-hosted GrowthBook through OIDC with named providers or a generic OIDC configuration. Set an active licence key and provider settings, and configure email-domain/account admission and role policy. Standard account login, experiment/SDK identities and SCIM are separate concerns. Scope: Licensed self-hosted Enterprise user login, distinct from Cloud account setup. Source: https://docs.growthbook.io/sso (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream Compose example includes the application and MongoDB with persistent volumes. It uses example credentials and moving images; replace credentials and select compatible pinned versions. Scope: Upstream example, not a hardened production configuration. Source: https://github.com/growthbook/growthbook/blob/main/docker-compose.yml (reviewed 2026-11-14). Deployment artifact: https://github.com/growthbook/growthbook/blob/main/docker-compose.yml. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The production guide recommends at least 1 vCPU/2 GB RAM per application instance and at least three instances for fault tolerance. MongoDB and optional separate stats/jobs workers need their own resources; its database example for 1,000 flags/experiments is not 1 TB of application data. Size experiment processing, warehouse queries, uploads and replicas separately. Scope: Current production application reference; database, stats engine and workload capacity remain separate. Source: https://docs.growthbook.io/self-host/production (reviewed 2026-11-20).

- License pricing: Documented. The v5.2.1 licence applies MIT terms to the core, with specified enterprise directories under the GrowthBook Enterprise License. Enterprise SSO on a self-hosted instance requires an active licence key. Hosted plans, self-hosted paid entitlements, infrastructure and support must be priced separately. Scope: Published core/Enterprise source boundary; no Cloud price transferred to self-hosted. Source: https://github.com/growthbook/growthbook/blob/v5.2.1/LICENSE (reviewed 2026-11-20). Supporting source: Self-hosted Enterprise SSO licence requirement — https://docs.growthbook.io/sso.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The reviewed upstream release is v5.2.1, published 2026-11-16. This is a dated release snapshot, not a support designation, a future cadence promise or approval to replace a provider package. Scope: Upstream growthbook/growthbook release record; commercial editions, LTS branches and provider packages can differ. Source: https://github.com/growthbook/growthbook/releases/tag/v5.2.1 (reviewed 2026-11-17).




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- GrowthBook self-hosted security patch (security-advisory): GrowthBook 5.2.1 updates vulnerable runtime dependencies and removes problematic regular-expression backtracking. Scope: Upstream self-hosted GrowthBook 5.2.1 patch over 5.2.0; not a promise about all commercial packaging. Conditions: The vendor recommends the update to self-hosted users. Source builds now fetch zlib through GitHub and its release-assets host. Action: Apply the compatible security patch and permit the documented download hosts when building behind an egress allowlist. Source: https://github.com/growthbook/growthbook/releases/tag/v5.2.1; reviewed 2026-11-17.




## Unleash Self-Hosted

Feature management and controlled application rollouts in your own environment.

- Listing: https://launchinyourcloud.com/directory/unleash/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0 Open Source; Enterprise features require separate commercial licensing
- Licensing model: open-source
- Installation: Official Docker/Compose deployment with PostgreSQL; choose the licensed edition.
- Architecture: Customer-operated feature-management service, database and SDK integrations
- Operations: Customer operates the service and database and manages SDK credentials, availability and upgrades.
- Product website: https://www.getunleash.io/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The self-hosted Open Source and Enterprise editions have different capabilities. Vendor-hosted Enterprise is a separate option. The installation guide documents version-check behavior and how to configure it; verify governance requirements against the selected edition.

AGPL-licensed Open Source is available alongside commercially licensed Enterprise capabilities. The entry covers both self-hosted edition choices.

The documented self-hosted runtime uses an application server or container with persistent state services. Hosted vendor editions are outside this listing.


### Category fit

- feature-management: Feature flags, activation strategies and controlled feature rollout using a self-hosted management service and SDKs.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.getunleash.io/blog/self-host-unleash-aws (checked 2026-11-12). 


### Cloud deployment evidence

- Unleash self-hosting in a customer AWS account (aws): https://www.getunleash.io/blog/self-host-unleash-aws
  The vendor describes self-hosting the full Unleash server in the customer AWS account, including ECS/Fargate, EC2, Elastic Beanstalk and EKS options. PostgreSQL, credentials, networking, backups and upgrades remain customer responsibilities; Unleash Cloud and Marketplace SaaS are separate options.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Self-hosted deployment and database: https://docs.getunleash.io/deploy/getting-started

- Feature platform and current open-source license: https://github.com/Unleash/unleash

### Licensing sources

- https://github.com/Unleash/unleash

- https://docs.getunleash.io/deploy/getting-started

### Infrastructure sources

- https://docs.getunleash.io/deploy/getting-started


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. The Enterprise SSO guide documents SAML 2.0 and OIDC, configured by an administrator with the selected IdP. Self-hosted Enterprise needs a valid licence key; core password login is a different path. Configure claim/account mapping and session policy; an IdP may not honor forced re-authentication requests identically. Scope: Current self-hosted Enterprise user login, including documented v8.3 session qualifications. Source: https://docs.getunleash.io/concepts/sso (reviewed 2026-11-20). Supporting source: Self-hosted Enterprise licence keys — https://docs.getunleash.io/deploy/license-keys.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream Compose file supplies Unleash and PostgreSQL but explicitly restricts that recipe to demo, development and learning. It is not a production deployment recommendation. Scope: Upstream development/demo Compose only. Source: https://github.com/Unleash/unleash/blob/main/docker-compose.yml (reviewed 2026-11-14). Deployment artifact: https://github.com/Unleash/unleash/blob/main/docker-compose.yml. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The configuration guide suggests 0.5–1 vCPU and 512 MiB–1 GiB for an application container, plus a PostgreSQL starting point of 1 vCPU, 1 GiB RAM and 5 GiB SSD. Flags, SDK request rate, replicas, storage and database availability determine the real footprint; these small component baselines do not size a 1 TB HA deployment. Scope: Current application/database starting allocations, not total production capacity. Source: https://docs.getunleash.io/deploy/configuring-unleash (reviewed 2026-11-20).

- License pricing: Documented. The reviewed v8.3.1 upstream core is AGPLv3, so older Apache-2.0 descriptions must not be applied to this release. Self-hosted Enterprise requires a separate licence key with seat-count/expiration enforcement. Hosted pricing, Enterprise entitlements, support and your PostgreSQL/application infrastructure are separate. Scope: Published application source licence and self-hosted Enterprise licensing. Source: https://github.com/Unleash/unleash/blob/v8.3.1/LICENSE (reviewed 2026-11-20). Supporting source: Self-hosted Enterprise licence-key and seat rules — https://docs.getunleash.io/deploy/license-keys.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v8.3.1, published 2026-10-29. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream Unleash/unleash release record; commercial editions and deployment packages may differ. Source: https://github.com/Unleash/unleash/releases/tag/v8.3.1 (reviewed 2026-11-14).






