
# Feature management on Google Cloud

Compare documented Feature management deployments on Google Cloud, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/gcp/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.


## Provider guidance

- Account boundary: Google Cloud project
- Provider group: cloud-infrastructure
- Provider classification: Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Source: https://docs.cloud.google.com/resource-manager/docs/creating-managing-projects (checked 2026-11-20).
- Network: VPC network
- Identity and access: IAM policies and service accounts
- Installation guidance: Terraform, optionally using Infrastructure Manager for resource provisioning; deploy the application separately.
- Guidance source: https://docs.cloud.google.com/infrastructure-manager/docs/overview
- Guidance reviewed: 2026-11-10


### Private offers

Cloud Marketplace vendors can negotiate a private offer for a specified Cloud Billing account. Check duration, renewal terms and commitment treatment in the actual agreement.
Source: https://docs.cloud.google.com/marketplace/docs/offers/discover-private-offers (reviewed 2026-11-14).

### Private connectivity

Private Service Connect connects VPC consumers to supported managed or producer services. Confirm the actual product endpoint and network/DNS architecture.
Source: https://docs.cloud.google.com/vpc/docs/private-service-connect (reviewed 2026-11-14).

### External workload access

Workload Identity Federation can grant external workloads scoped Google Cloud access without long-lived service-account keys. Validate the trust configuration and exact roles.
Source: https://docs.cloud.google.com/iam/docs/workload-identity-federation (reviewed 2026-11-14).

### Regulated environments

Assured Workloads applies control packages for residency and access boundaries. Confirm supported services, regions and the product deployment; it is not automatic product certification.
Source: https://docs.cloud.google.com/assured-workloads/docs/overview (reviewed 2026-11-14).

The listings below have evidence for Google Cloud. Read each cloud evidence note for the applicable package, edition and support qualifications.

1 listing.


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



