Feature management on Azure
Feature flags, rollout controls and application activation strategies.
1 documented option on Microsoft Azure. Provider coverage reflects reviewed evidence, not an exhaustive compatibility claim.
Read this page as JSON or Markdown.
| Listing | Documented clouds | Deployment and infrastructure | Licensing | Installation | Operations and limitations |
|---|---|---|---|---|---|
| Flagsmith Self-Hosted | AWS, Azure, Google Cloud, DigitalOcean | Customer-operated Servers / containers | Open Source / Open Core BSD-3-Clause for upstream core functionality; supported Enterprise editions and commercial features have separate terms. | Deploy the official Docker Compose environment and configure the dashboard/API, PostgreSQL and application SDK endpoints. | Customer manages flag API availability, SDK endpoints, database, permissions, secrets, backups and upgrades.Scope and evidenceThe 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.
Cloud evidence reviewed 2026-11-12 |
Deployment evidence and category fit
Flagsmith Self-Hosted
Feature flags, remote configuration, user targeting, segments and multivariate release control; advanced edition features are separate.
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.
- Flagsmith self-hosted platform architecture ↗
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.
Cloud evidence reviewed 2026-11-12. Full listing and qualifications
Deployment and procurement checks
- Private offers
- Microsoft Marketplace private offers negotiate product pricing and terms. Confirm the exact offer, billing scope and benefit eligibility rather than assuming all purchases count toward a commitment. Provider source ↗ · Reviewed 2026-11-14
- Private connectivity
- Azure Private Link uses private endpoints in a virtual network for supported Azure and partner services. Check application support, DNS and service availability. Provider source ↗ · Reviewed 2026-11-14
- Cross-tenant operations
- Azure Lighthouse supports delegated management with customer-controlled scopes and actions. Agree the roles, audit requirements and revocation plan for the selected vendor. Provider source ↗ · Reviewed 2026-11-14
- Government environments
- Azure Government uses isolated US datacenters and networks. Commercial Azure documentation alone does not establish a product path or compliance in Government. Provider source ↗ · Reviewed 2026-11-14
For every provider, confirm marketplace/private-offer terms, commitment eligibility, regional service availability, private connectivity and any vendor access against your selected deployment. Provider capabilities do not automatically establish application support.
Plan this deployment
Account boundary: Subscription and resource group. Access: Microsoft Entra identities and Azure RBAC. Network: Virtual Network (VNet).
Provider documentation ↗ · Guidance reviewed 2026-11-10. Confirm the application edition, region, support access, backup locations and operating responsibilities before choosing.
Compare this category across clouds · Search these listings · Compare 2–4 listings