
# Content management & CMS on Google Cloud

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

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

7 listings.


## Confluence Data Center

Commercial self-managed Confluence edition for enterprise collaboration and knowledge management. New Data Center subscriptions are restricted to eligible existing Atlassian customers.

- Listing: https://launchinyourcloud.com/directory/confluence-data-center/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Atlassian Data Center term license for eligible existing customers; new-customer sales ended March 30, 2026. Affected subscriptions expire March 28, 2029.
- Licensing model: commercial-only
- Installation: Official Atlassian Helm chart on Amazon EKS, Azure AKS or Google GKE, or package-based single-node and clustered installation
- Architecture: Single-node or clustered Confluence and optional Synchrony services with an external database, load balancer, shared home and local indexes
- Operations: Customer manages Kubernetes or hosts, the database, shared and local storage, Synchrony, load balancing, networking, TLS, identity, Marketplace apps, backups, monitoring and upgrades.
- Product website: https://www.atlassian.com/software/confluence/enterprise
- Source review: 2026-11-18; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers Confluence Data Center, not Confluence Cloud. Atlassian supports its Kubernetes Helm chart and documents EKS, AKS and GKE as managed cluster options. The older AWS Quick Start and Azure Resource Manager templates are no longer supported or maintained. Atlassian states that affected Data Center subscriptions and associated Marketplace apps expire on March 28, 2029, after which the applications become read-only; evaluate the migration timeline before a new deployment. New customers cannot purchase this Data Center subscription after March 30, 2026. The remaining purchase/expansion window through March 30, 2028 is for existing Data Center customers; do not treat this listing as an unrestricted new-customer offering. Atlassian rates CVE-2026-21589 critical (9.3). Upgrade to Confluence 9.2.26, 10.2.19, or a later fixed release to prevent unauthenticated access to specifically named files under the web application root. Separately, CVE-2026-90436 is a critical unauthenticated remote-code-execution issue in Confluence 1.x–9.x when Remote API (XML-RPC and SOAP) is enabled. Upgrade to 9.2.28 or a later fixed release, or disable the remote API and verify that the Axis endpoint returns HTTP 403; Confluence 10.x and later are unaffected by the RCE. Atlassian's November 17, 2026 bulletin aggregates 266 high- and 52 critical-severity third-party CVEs, while assessing the bulletin items as non-critical in product context. Use a fixed supported target for this product and branch, and validate app compatibility before upgrading.

New customers can no longer purchase affected Data Center subscriptions after March 30, 2026. Existing Data Center customers may purchase new subscriptions and expansions until March 30, 2028. Affected subscriptions and associated Marketplace apps expire and become read-only on March 28, 2029; review the vendor migration and exception policies.

Confluence Data Center runs persistent application and collaborative-editing services with durable database, shared-home and local-index storage.


### Category fit

- collaboration: Provides self-managed team workspaces, collaborative authoring and enterprise knowledge sharing.

- content-management: Manages structured spaces, pages, attachments, templates and governed enterprise knowledge content.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://confluence.atlassian.com/doc/running-confluence-data-center-on-a-kubernetes-cluster-1085179764.html (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://confluence.atlassian.com/doc/running-confluence-data-center-on-a-kubernetes-cluster-1085179764.html (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://confluence.atlassian.com/doc/running-confluence-data-center-on-a-kubernetes-cluster-1085179764.html (checked 2026-11-16). 


### Cloud deployment evidence

- Confluence Data Center on EKS, AKS or GKE (aws, azure, gcp): https://confluence.atlassian.com/doc/running-confluence-data-center-on-a-kubernetes-cluster-1085179764.html
  Atlassian documents Confluence Data Center deployment with its Helm charts and explicitly lists Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine as managed cluster environments. The linked page applies to Confluence Data Center 11.0; select a Helm chart compatible with the installed product release.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed. Versions: 11.0; use the current compatibility matrix for other releases.


### Sources

- Install Confluence Data Center 11.0: https://confluence.atlassian.com/doc/installing-confluence-data-center-203603.html

- Run Confluence Data Center on Kubernetes: https://confluence.atlassian.com/doc/running-confluence-data-center-on-a-kubernetes-cluster-1085179764.html

- Confluence Data Center supported platforms: https://confluence.atlassian.com/doc/supported-platforms-207488198.html

- Atlassian Data Center licensing and end of life: https://www.atlassian.com/licensing/data-center

- Atlassian product-specific end-of-life and purchase eligibility: https://www.atlassian.com/licensing/data-center-end-of-life

- Atlassian CVE-2026-21589 critical file-access advisory: https://confluence.atlassian.com/security/cve-2026-21589-arbitrary-file-access-vulnerability-impacts-multiple-products-1870495748.html

- Atlassian CVE-2026-90436 Confluence RCE advisory: https://confluence.atlassian.com/security/cve-2026-90436-remote-code-execution-in-confluence-data-center-1874560038.html

- Atlassian security bulletin — November 17, 2026: https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html

### Licensing sources

- https://www.atlassian.com/licensing/data-center

- https://www.atlassian.com/licensing/data-center-end-of-life

### Infrastructure sources

- https://confluence.atlassian.com/doc/installing-confluence-data-center-203603.html

- https://confluence.atlassian.com/doc/running-confluence-data-center-on-a-kubernetes-cluster-1085179764.html


### Buyer diligence


Research coverage: 8/12 fields (67%); 7 documented, 1 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: Documented. Atlassian documents SAML 2.0 and OIDC through its Data Center SSO app. Match app compatibility to Confluence 7.12+; authentication does not assign application access or permissions. Scope: Confluence 7.12+ Data Center SSO feature baseline; existing-customer lifecycle restrictions remain. Source: https://confluence.atlassian.com/enterprise/saml-single-sign-on-for-atlassian-data-center-applications-857050705.html (reviewed 2026-11-16). Supporting source: OIDC product/version scope — https://confluence.atlassian.com/enterprise/openid-connect-for-atlassian-data-center-applications-987142159.html.

- SCIM provisioning: Documented. Atlassian’s native cloud-IdP scenario uses login-time JIT provisioning for Data Center, without regular synchronization or de-provisioning. Its cloud SCIM path is different; third-party Data Center provisioning apps require separate review. Scope: Native Data Center cloud-IdP integration described by Atlassian; not an assessment of every Marketplace add-on. Source: https://confluence.atlassian.com/enterprise/manage-users-between-cloud-and-data-center-products-1085188069.html (reviewed 2026-11-16).

- Compliance attestations: Sources checked — unresolved. Atlassian’s public SOC 2 page points to product reports, but does not establish the customer-operated Data Center boundary or report validity. Review the actual report before claiming coverage. Scope: Vendor reports versus this self-managed Data Center installation. Source: https://www.atlassian.com/trust/compliance/resources/soc2 (reviewed 2026-11-16).

- Security controls: Documented. Current advisory review: Atlassian aggregates 266 high- and 52 critical-severity third-party CVEs fixed during the month, while assessing the bulletin items as non-critical in product context. Upgrade each Data Center product to a fixed supported target, preferring the vendor-recommended LTS where appropriate, and validate app compatibility. Scope: Fixed targets include Bitbucket 10.5.2, 10.2.9 LTS or 9.4.27 LTS; Confluence 11.0.1, 10.2.20 LTS, or 9.2.27/9.2.28 LTS; and Jira/JSM 11.3.13 LTS or 10.3.27 LTS.. Source: https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Atlassian publishes product-specific Data Center Helm charts. Select a chart and application version supported for this product and configure its database, persistent storage, ingress and license; one product’s chart does not establish compatibility for another. Scope: Confluence Data Center; existing-customer eligibility and lifecycle conditions apply. Source: https://confluence.atlassian.com/doc/installing-confluence-data-center-203603.html (reviewed 2026-11-16). Deployment artifact: https://github.com/atlassian/data-center-helm-charts. Artifact reference: main (moving branch; select product-compatible chart and application release).

- Minimum footprint / sizing: Documented. The Data Center technical overview recommends at least 10 GB RAM per Confluence node, including operating-system, JVM, external-process and Synchrony allocations. Database, shared storage, node count and any separate Synchrony cluster require additional planning. Scope: Clustered Confluence Data Center node guideline; not an installation-wide total. Source: https://confluence.atlassian.com/enterprise/confluence-data-center-technical-overview-612959401.html (reviewed 2026-11-16).

- License pricing: Documented. New customers can no longer purchase affected Data Center subscriptions after March 30, 2026. Existing Data Center customers may purchase new subscriptions and expansions until March 30, 2028. Affected subscriptions and associated Marketplace apps expire and become read-only on March 28, 2029; review the vendor migration and exception policies. Scope: Confluence Data Center: software license terms; infrastructure and operating costs are separate. Source: https://www.atlassian.com/licensing/data-center (reviewed 2026-11-16). Supporting source: Edition and license conditions — https://www.atlassian.com/licensing/data-center-end-of-life.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Atlassian’s current-download feed lists 11.0.1, released 2026-11-03. This is the reviewed download snapshot, not a guarantee that every other release branch, Helm chart, app or upgrade path is compatible. Existing-customer and lifecycle restrictions still apply. Scope: Vendor current-download feed; publication day only, with no invented release time. Source: https://my.atlassian.com/download/feeds/current/confluence.json (reviewed 2026-11-16). Supporting source: Vendor release notes — https://confluence.atlassian.com/display/DOC/Confluence+11.0+Release+Notes.




### Security and lifecycle reviews

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

- Data Center purchase restrictions and 2029 retirement (lifecycle): Affected subscriptions become read-only on March 28, 2029. New customers lost purchase eligibility on March 30, 2026; existing customers have a different expansion window. Scope: Jira Software, Jira Service Management and Confluence Data Center. Bitbucket is excluded from this retirement; exceptional extensions require Atlassian agreement. Conditions: Existing-customer status and the purchased product determine eligibility. Action: Confirm purchase eligibility, migration timing and any written exception before evaluation. Source: https://www.atlassian.com/licensing/data-center-end-of-life; reviewed 2026-11-16.

- Atlassian Data Center unauthenticated file access (security-advisory): CVE-2026-21589 allows access to specifically named files under the web application root; Atlassian assigns critical severity. Scope: Jira Software: 9.12.40/10.3.26/11.3.12; JSM: 5.12.40/10.3.26/11.3.12; Confluence: 9.2.26/10.2.19; Bitbucket: 9.4.26/10.2.8/10.5.1. Versions before the appropriate branch fix are affected. Conditions: An attacker needs the exact file name and path; directory enumeration is not provided. Sensitive files in the application root change the risk. Action: Patch every affected installation to its fixed supported branch. If delayed, restrict internet access and apply the vendor WAF or product-specific rewrite mitigation to all relevant nodes. Source: https://confluence.atlassian.com/security/cve-2026-21589-arbitrary-file-access-vulnerability-impacts-multiple-products-1870495748.html; reviewed 2026-11-17.

- Confluence Remote API code-execution advisory (security-advisory): CVE-2026-90436 is an unauthenticated code-execution issue when the affected Remote API is enabled. Scope: Confluence Data Center 1.x–9.x before the applicable fix; 9.2.28 is the listed fixed LTS release. Confluence 10.x and later are unaffected. Conditions: Requires Remote API (XML-RPC and SOAP). Disabling it can break scripts, automation and add-ons. Action: Install a fixed supported release, or disable Remote API and verify HTTP 403 from the documented SOAP Axis endpoint. Source: https://confluence.atlassian.com/security/cve-2026-90436-remote-code-execution-in-confluence-data-center-1874560038.html; reviewed 2026-11-17.

- Atlassian Data Center November 17, 2026 bulletin (security-advisory): Atlassian aggregates 266 high- and 52 critical-severity third-party CVEs fixed during the month, while assessing the bulletin items as non-critical in product context. Scope: Fixed targets include Bitbucket 10.5.2, 10.2.9 LTS or 9.4.27 LTS; Confluence 11.0.1, 10.2.20 LTS, or 9.2.27/9.2.28 LTS; and Jira/JSM 11.3.13 LTS or 10.3.27 LTS. Conditions: Installed product, branch, bundled dependency, and Marketplace app compatibility determine applicability. Action: Upgrade each Data Center product to a fixed supported target, preferring the vendor-recommended LTS where appropriate, and validate app compatibility. Source: https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html; reviewed 2026-11-18.




## dotCMS Cloud Anywhere

Vendor-operated content platform deployed into a customer cloud account.

- Listing: https://launchinyourcloud.com/directory/dotcms/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Vendor-operated BYOC
- Infrastructure IDs: servers
- License: Commercial dotCMS Cloud Anywhere service terms; the public core-code licence does not grant service entitlements.
- Licensing model: commercial-only
- Installation: Cloud Anywhere onboarding and vendor management through customer-cloud access roles
- Architecture: dotCMS Cloud Anywhere tenant with vendor Lighthouse management and customer cloud access roles.
- Operations: Vendor operates the Cloud Anywhere application through its management plane and scoped customer-cloud access; agree support access, logs, egress and exit procedures.
- Product website: https://dev.dotcms.com/docs/manage/installation-and-deployment/cloud-anywhere/cloud-anywhere-quickstart-guide
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The vendor operates the installation through its control plane and AWS role or GCP service account. Public core code and Cloud Anywhere service licensing are different; this is not a fully customer-operated instance.

Commercial dotCMS Cloud Anywhere service terms; the public core-code licence does not grant service entitlements.

dotCMS Cloud Anywhere tenant with vendor Lighthouse management and customer cloud access roles. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- content-management: Vendor-operated content platform deployed into a customer cloud account.

### Deployment boundaries


- aws: Customer cloud account; Vendor / partner-operated; control plane: not-assessed. Source: https://dev.dotcms.com/docs/manage/installation-and-deployment/cloud-anywhere/cloud-anywhere-quickstart-guide (checked 2026-11-19). 

- azure: Customer cloud account; Vendor / partner-operated; control plane: not-assessed. Source: https://dev.dotcms.com/docs/manage/installation-and-deployment/cloud-anywhere/cloud-anywhere-quickstart-guide (checked 2026-11-19). 

- gcp: Customer cloud account; Vendor / partner-operated; control plane: not-assessed. Source: https://dev.dotcms.com/docs/manage/installation-and-deployment/cloud-anywhere/cloud-anywhere-quickstart-guide (checked 2026-11-19). 

Operating responsibility: dotCMS provisions and operates Cloud Anywhere through its automation and delegated access to a dedicated customer account, subscription or project. The separately customer-operated self-hosted edition is outside this listing. Source: https://dev.dotcms.com/docs/manage/installation-and-deployment/cloud-anywhere/cloud-anywhere-quickstart-guide (checked 2026-11-20).


### Cloud deployment evidence

- Cloud Anywhere Quickstart (aws, azure, gcp): https://dev.dotcms.com/docs/manage/installation-and-deployment/cloud-anywhere/cloud-anywhere-quickstart-guide
  dotCMS Cloud Anywhere tenant with vendor Lighthouse management and customer cloud access roles. The vendor operates the installation through its control plane and AWS role or GCP service account. Public core code and Cloud Anywhere service licensing are different; this is not a fully customer-operated instance.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Cloud Anywhere Quickstart: https://dev.dotcms.com/docs/manage/installation-and-deployment/cloud-anywhere/cloud-anywhere-quickstart-guide

- Azure Setup Guide: https://dev.dotcms.com/docs/manage/installation-and-deployment/cloud-anywhere/cloud-anywhere-azure-setup-guide

- BSL-1.1 LICENSE: https://github.com/dotCMS/core/blob/master/LICENSE

- Releases v26.11.18: https://github.com/dotCMS/core/releases

### Licensing sources

- https://dev.dotcms.com/docs/manage/installation-and-deployment/cloud-anywhere/cloud-anywhere-quickstart-guide

- https://github.com/dotCMS/core/blob/master/LICENSE

### Infrastructure sources

- https://dev.dotcms.com/docs/manage/installation-and-deployment/cloud-anywhere/cloud-anywhere-quickstart-guide


### Buyer diligence


Research coverage: 4/12 fields (33%); 3 documented, 1 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: Documented. The current dotAuth guide documents system/site SSO settings for OAuth2/OIDC and SAML, including separate redirects for site and administrator login. Validate the selected service plan, release and identity mapping; site inheritance is not the same as configuring every redirect at the IdP. Scope: Current dotCMS application authentication; Cloud Anywhere service entitlement/version must be confirmed. Source: https://dev.dotcms.com/docs/manage/access-and-security/dotauth/dotauth-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. Official container guidance provides Docker and multi-service Compose examples with persistent data volumes. The developer all-in-one image is for local evaluation; it is not the Cloud Anywhere managed-service architecture or a production HA baseline. Scope: Upstream application container examples; selected managed deployment follows its separate contract. Source: https://dev.dotcms.com/docs/manage/installation-and-deployment/docker/getting-started-with-dotcms-in-docker-containers (reviewed 2026-11-20). Deployment artifact: https://dev.dotcms.com/docs/manage/installation-and-deployment/docker/getting-started-with-dotcms-in-docker-containers. Artifact reference: Current reference examples; pin a supported application and backing-service release.

- Minimum footprint / sizing: Documented. The standard-stack requirements specify a multicore processor, dedicated 8+ GB RAM and 100 GB disk, with PostgreSQL and OpenSearch dependencies. These application-stack requirements do not size a contracted Cloud Anywhere topology or validate 100-user/1-TB HA capacity. Scope: Upstream standard-stack baseline; managed-service deployment sizing is separate. Source: https://dev.dotcms.com/docs/manage/installation-and-deployment/installation/requirements (reviewed 2026-11-20).

- License pricing: Sources checked — unresolved. The public core-code licence does not establish the Cloud Anywhere managed-service price, order or operating/support entitlements. Obtain the agreement for the customer-cloud service. Scope: Selected self-managed application or customer-cloud service; contract confirmation required. Source: https://dev.dotcms.com/docs/manage/installation-and-deployment/cloud-anywhere/cloud-anywhere-quickstart-guide (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## HCL Digital Experience Cloud Native 9.5

Commercial web content and digital asset management platform deployed by Helm to customer-operated Kubernetes.

- Listing: https://launchinyourcloud.com/directory/hcl-digital-experience-cloud-native/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial HCL Digital Experience Cloud Native subscription measured by user sessions and associated production processing capacity.
- Licensing model: commercial-only
- Installation: Official HCL Digital Experience Helm chart on customer Amazon EKS, Microsoft AKS or Google GKE
- Architecture: Customer-operated Kubernetes deployment with persistent application, content and asset services plus external platform dependencies.
- Operations: Customer manages Kubernetes, storage, databases and integrations, ingress, certificates, capacity, backups, upgrades and version compatibility.
- Product website: https://www.hcl-software.com/digital-experience
- Source review: 2026-11-17; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

Beginning with HCL DX 9.5 CF200, operator-based deployments are discontinued and Helm is the supported container method. Supported cloud Kubernetes deployments require x86-64 hardware, compatible Kubernetes and Helm versions, persistent storage and production sizing. HCL tests Amazon EKS, Microsoft AKS and Google GKE; exact storage and version support must be checked for the selected release.

Current HCL Digital Experience Cloud Native entitlements are commercial subscriptions. The User Session metric includes an associated production virtual-processing-capacity allowance; exact rights follow the order and License Information document.

The supported deployment runs persistent HCL DX containers on customer Kubernetes with persistent volumes and supporting stateful services. Helm is supported for CF200 and later.


### Category fit

- content-management: A web content management system with authoring, presentation templates, headless APIs and publishing workflows.

- digital-asset-management: Integrated digital asset management organizes, controls and reuses images, video and other web-ready assets.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.hcl-software.com/digital-experience/9.5/CF239/deployment/install/container/helm_deployment/aws_marketplace_helm_deployment/ (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.hcl-software.com/digital-experience/9.5/latest/get_started/system_requirements/kubernetes/kubernetes-runtime/ (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.hcl-software.com/digital-experience/9.5/latest/get_started/system_requirements/kubernetes/kubernetes-runtime/ (checked 2026-11-17). 


### Cloud deployment evidence

- HCL Digital Experience on Amazon EKS (aws): https://help.hcl-software.com/digital-experience/9.5/CF239/deployment/install/container/helm_deployment/aws_marketplace_helm_deployment/
  HCL documents deploying the entitled DX Helm chart to Amazon-managed Kubernetes in the customer's AWS environment.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- HCL Digital Experience on Microsoft Azure AKS (azure): https://help.hcl-software.com/digital-experience/9.5/latest/get_started/system_requirements/kubernetes/kubernetes-runtime/
  HCL's current support matrix explicitly lists Microsoft Azure AKS as a tested and supported full-container platform.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- HCL Digital Experience on Google GKE (gcp): https://help.hcl-software.com/digital-experience/9.5/latest/get_started/system_requirements/kubernetes/kubernetes-runtime/
  HCL's current support matrix explicitly lists Google GKE as a tested and supported full-container platform.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Current Kubernetes runtime and cloud support matrix: https://help.hcl-software.com/digital-experience/9.5/latest/get_started/system_requirements/kubernetes/kubernetes-runtime/

- AWS Marketplace Helm deployment: https://help.hcl-software.com/digital-experience/9.5/CF239/deployment/install/container/helm_deployment/aws_marketplace_helm_deployment/

- Azure Kubernetes Service Helm deployment: https://help.hcl-software.com/digital-experience/9.5/CF238/guide_me/howto/install/DeployOnAzure/

- Container deployment requirements and limitations: https://help.hcl-software.com/digital-experience/9.5/CF239/get_started/plan_deployment/container_deployment/limitations_requirements/

- HCL DX content management: https://www.help.hcl-software.com/digital-experience/9.5/CF239/get_started/product_overview/content_management/

- HCL DX digital asset management: https://www.help.hcl-software.com/digital-experience/9.5/CF239/get_started/product_overview/asset_management/

- User Session licensing: https://www.hcl-software.com/resources/license-agreements/user-session-licensing

### Licensing sources

- https://www.hcl-software.com/resources/license-agreements/user-session-licensing

### Infrastructure sources

- https://help.hcl-software.com/digital-experience/9.5/latest/get_started/system_requirements/kubernetes/kubernetes-runtime/

- https://help.hcl-software.com/digital-experience/9.5/CF239/get_started/plan_deployment/container_deployment/limitations_requirements/


### Buyer diligence


Research coverage: 12/12 fields (100%); 5 documented, 7 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: Documented. HCL documents DX 9.5 Helm deployment through AWS Marketplace. Obtain the matching subscription and container access; licensing and image versions must match the selected cumulative fix. Scope: HCL DX 9.5 AWS Marketplace Helm route. Source: https://help.hcl-software.com/digital-experience/9.5/CF239/deployment/install/container/helm_deployment/aws_marketplace_helm_deployment/ (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. The AWS Marketplace installation guide does not establish qualifying fees or commitment treatment for the selected DX offer and buyer agreement. Scope: Reviewed public evidence for HCL Digital Experience Cloud Native 9.5; unresolved within this edition/deployment. Source: https://help.hcl-software.com/digital-experience/9.5/CF239/deployment/install/container/helm_deployment/aws_marketplace_helm_deployment/ (reviewed 2026-11-17).

- Single sign-on: Sources checked — unresolved. The CF239 docs establish People Service OIDC and a DX/Leap SSO integration, but the complete primary DX authentication configuration and entitlement for this deployment were not established. Scope: Reviewed public evidence for HCL Digital Experience Cloud Native 9.5; unresolved within this edition/deployment. Source: https://help.hcl-software.com/digital-experience/9.5/CF239/extend_dx/integration/people_service/deployment/configuration/oidc_configuration/ (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. People Service documents LDAP synchronization limitations, not a DX-wide SCIM service. A supported SCIM endpoint and licence scope for the selected cumulative fix were not established. Scope: Reviewed public evidence for HCL Digital Experience Cloud Native 9.5; unresolved within this edition/deployment. Source: https://help.hcl-software.com/digital-experience/9.5/CF239/extend_dx/integration/people_service/limitations/ (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed HCL Digital Experience Cloud Native 9.5 material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage. Scope: Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited. Source: https://help.hcl-software.com/digital-experience/9.5/CF239/deployment/install/container/helm_deployment/aws_marketplace_helm_deployment/ (reviewed 2026-11-17).

- Security controls: Documented. The Helm workflow requires image access, configured credentials and persistent service configuration. Restrict Kubernetes and registry permissions and use the matching deployment security guidance. Scope: DX Helm deployment access; not an attestation. Source: https://help.hcl-software.com/digital-experience/9.5/CF239/deployment/install/container/helm_deployment/aws_marketplace_helm_deployment/ (reviewed 2026-11-17).

- Air-gapped operation: Sources checked — unresolved. The Helm installation requires entitled images and chart configuration; a supported complete offline licence, image/dependency transfer and update workflow was not established. Scope: Reviewed public evidence for HCL Digital Experience Cloud Native 9.5; unresolved within this edition/deployment. Source: https://help.hcl-software.com/digital-experience/9.5/CF239/deployment/install/container/helm_deployment/aws_marketplace_helm_deployment/ (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. The Marketplace installation uses the HCL Helm chart with configured values, container images and persistent volumes. Review the matching CF requirements; the former Operator path is not the current Helm workflow. Scope: HCL DX 9.5 CF239 Helm installation. Source: https://help.hcl-software.com/digital-experience/9.5/CF239/deployment/install/container/helm_deployment/aws_marketplace_helm_deployment/ (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. The container requirements distinguish supported Kubernetes platforms, CPU architecture, persistence and component limitations. Size Portal, content and asset services separately for the selected cumulative fix. Scope: DX cloud-native CF239 requirements; topology-specific sizing. Source: https://help.hcl-software.com/digital-experience/9.5/CF239/get_started/plan_deployment/container_deployment/limitations_requirements/ (reviewed 2026-11-17).

- License pricing: Documented. Current HCL Digital Experience Cloud Native entitlements are commercial subscriptions. The User Session metric includes an associated production virtual-processing-capacity allowance; exact rights follow the order and License Information document. Scope: HCL Digital Experience Cloud Native 9.5: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://www.hcl-software.com/resources/license-agreements/user-session-licensing (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Confirm Portal, content/asset components, cumulative-fix images, database/search/persistence and session-licence unit. A generic EKS fleet would omit required services and the HA design. A complete monthly operating estimate is not established. Scope: Requested planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA, average usage; missing workload metrics and commercial terms are explicit. Source: https://help.hcl-software.com/digital-experience/9.5/CF239/get_started/plan_deployment/container_deployment/limitations_requirements/ (reviewed 2026-11-17).

- Release snapshot / cadence: Sources checked — unresolved. CF239-scoped deployment documentation and a separately resolved current compatibility matrix were reviewed. The latest entitled CF/chart/image bundle and precise release date require confirmation. Scope: Reviewed public evidence for HCL Digital Experience Cloud Native 9.5; unresolved within this edition/deployment. Source: https://help.hcl-software.com/digital-experience/9.5/CF239/deployment/install/container/helm_deployment/aws_marketplace_helm_deployment/ (reviewed 2026-11-17).







## Liferay DXP Cloud Native Experience

Commercial digital experience, content management and digital asset platform deployed into customer cloud infrastructure with Liferay's Cloud Native Experience toolkit.

- Listing: https://launchinyourcloud.com/directory/liferay-dxp-cloud-native-experience/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Liferay DXP subscription; Cloud Native Experience provider-ready capabilities require Enterprise Subscription entitlement.
- Licensing model: commercial-only
- Installation: Provider-ready Terraform bootstrap with Kubernetes, Helm and Argo CD GitOps deployment
- Architecture: Customer-operated EKS, AKS or GKE deployment integrated with provider database, object storage and search services.
- Operations: Customer manages the cloud account, GitOps repository, Kubernetes platform, secrets, domains, certificates, capacity, backups, upgrades and application customizations.
- Product website: https://www.liferay.com/products/dxp
- Source review: 2026-11-17; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

Cloud Native Experience supports Liferay DXP 2024.Q1 and later. Provider architectures differ: AWS Ready integrates RDS, S3 and OpenSearch; Azure Ready uses AKS, Azure PostgreSQL Flexible Server, Blob Storage and Elasticsearch through ECK; GCP Ready uses GKE, Cloud SQL, Cloud Storage and ECK. The customer must provide cloud permissions, a Git repository, secret storage, compatible tools and a valid activation key. Starting with DXP 2026.Q1, all installations require an activation key.

This entry is scoped to commercial Liferay DXP Cloud Native Experience, not Liferay Portal Community Edition. Provider-ready capabilities require Enterprise Subscription entitlement and DXP requires an activation key.

Provider-ready CNE provisions managed Kubernetes and supporting stateful services in the customer's cloud. Liferay runs as persistent workloads managed through Helm and Argo CD.


### Category fit

- content-management: Liferay DXP provides web and headless content authoring, publishing, sites and digital-experience delivery on customer infrastructure.

- digital-asset-management: The DXP includes digital asset management for organizing and reusing documents and media; exact entitlement follows the selected subscription.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-aws-ready (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-azure-ready (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-gcp-ready (checked 2026-11-17). 


### Cloud deployment evidence

- Liferay DXP Cloud Native Experience AWS Ready (aws): https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-aws-ready
  Liferay documents automated deployment in the customer's AWS account with EKS, RDS, S3 and OpenSearch. Enterprise Subscription entitlement and customer cloud permissions are required.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- Liferay DXP Cloud Native Experience Azure Ready (azure): https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-azure-ready
  Liferay documents Terraform, Argo CD and Kubernetes provisioning in the customer's Azure subscription, including AKS and managed data services.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- Liferay DXP Cloud Native Experience GCP Ready (gcp): https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-gcp-ready
  Liferay documents Terraform, Argo CD and Kubernetes provisioning in the customer's Google Cloud environment, including GKE and managed data services.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Cloud Native Experience overview: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience

- AWS Ready deployment: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-aws-ready

- Azure Ready deployment: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-azure-ready

- GCP Ready deployment: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-gcp-ready

- Liferay DXP activation and subscription keys: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/setting-up-liferay/activating-liferay-dxp

- AWS Ready Enterprise Subscription requirement: https://learn.liferay.com/w/updates/release-notes/liferay-dxp/2026.q2/features/cloud-native-aws-ready-2026-q2-2

- GCP Ready Enterprise Subscription requirement: https://learn.liferay.com/w/updates/release-notes/liferay-dxp/2026.q3/features/cloud-native-gcp-ready

### Licensing sources

- https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/setting-up-liferay/activating-liferay-dxp

- https://learn.liferay.com/w/updates/release-notes/liferay-dxp/2026.q3/features/cloud-native-gcp-ready

### Infrastructure sources

- https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience

- https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-aws-ready


### Buyer diligence


Research coverage: 12/12 fields (100%); 6 documented, 6 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: Sources checked — unresolved. CNE licensing refers to Liferay Marketplace add-ons, not a provider billing offer. A current cloud Marketplace offer for the selected CNE Enterprise path was not established. Scope: Reviewed public evidence for Liferay DXP Cloud Native Experience; unresolved within this edition/deployment. Source: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/automatic-environment-licensing (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. DXP Enterprise activation and add-on delivery do not establish cloud-provider Marketplace commitment treatment. Scope: Reviewed public evidence for Liferay DXP Cloud Native Experience; unresolved within this edition/deployment. Source: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/setting-up-liferay/activating-liferay-dxp (reviewed 2026-11-17).

- Single sign-on: Documented. The DXP compatibility matrix documents SAML 2.0 and OIDC provider standards. Match the IdP and certified runtime components to the actual DXP release used by CNE. Scope: Self-hosted DXP identity compatibility; reviewed 2025.Q2 matrix. Source: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/reference/compatibility-matrices/liferay-dxp-2025-q2-compatibility-matrix (reviewed 2026-11-17).

- SCIM provisioning: Edition-dependent. DXP SCIM was introduced behind a flag in 2024.Q1, moved to a release flag in 2024.Q4 and became GA in 2025.Q1. Verify the deployed release and supported RFC operations; it does not implement arbitrary vendor schema extensions. Scope: DXP subscription/version-specific provisioning. Source: https://learn.liferay.com/es/w/dxp/security-and-administration/security/system-for-cross-domain-identity-management-scim (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed Liferay DXP Cloud Native Experience material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage. Scope: Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited. Source: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-aws-ready (reviewed 2026-11-17).

- Security controls: Documented. The CNE deployment requires controlled GitOps access, cloud credentials and activation keys. Configure secrets, network boundaries and the certified identity/runtime components rather than treating cloud provisioning as hardening. Scope: AWS Ready deployment access and secrets. Source: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-aws-ready (reviewed 2026-11-17).

- Air-gapped operation: Sources checked — unresolved. CNE documents offline activation bundles for AWS/GCP Ready, but Azure Ready 0.3.0 lacks the required Marketplace volume. This establishes offline licensing for selected paths; complete dependency mirroring, updates and integrations still need validation. Scope: Path/version-specific offline licensing, not unconditional air-gap support. Source: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/automatic-environment-licensing/licensing-an-offline-environment (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. CNE Kubernetes Ready supplies the liferay-default Helm chart; supporting Kubernetes, database, search and object storage are customer-managed. This complements provider-specific Ready automation. Pin a chart compatible with the chosen DXP release. Scope: Official Helm artifact for customer Kubernetes. Source: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-kubernetes-ready (reviewed 2026-11-17). Deployment artifact: https://github.com/liferay/liferay-portal/tree/master/cloud/helm/default. Artifact reference: master (moving branch; select a compatible chart/image release).

- Minimum footprint / sizing: Documented. The Kubernetes Ready Small tier uses two Liferay replicas, each requesting 2 CPU/12 GiB (limits 4 CPU/16 GiB), 20 GiB PVC per pod, an HA database, three search nodes and object storage. It targets up to 500 concurrent users but requires workload load testing. Scope: Kubernetes Ready Small production starting tier; AWS Ready infrastructure defaults may differ. Source: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-kubernetes-ready/architecture-sizing-and-support-model (reviewed 2026-11-17).

- License pricing: Documented. This entry is scoped to commercial Liferay DXP Cloud Native Experience, not Liferay Portal Community Edition. Provider-ready capabilities require Enterprise Subscription entitlement and DXP requires an activation key. Scope: Liferay DXP Cloud Native Experience: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/setting-up-liferay/activating-liferay-dxp (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. The Small tier supplies app/search/HA-database starting requirements, but the complete provider bill of materials, DXP entitlement and measured content/search workload still need confirmation. A complete monthly operating estimate is not established. Scope: Requested planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA, average usage; missing workload metrics and commercial terms are explicit. Source: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-kubernetes-ready/architecture-sizing-and-support-model (reviewed 2026-11-17).

- Release snapshot / cadence: Sources checked — unresolved. CNE supports DXP 2024.Q1+ and provider tooling has independent revisions. The complete latest supported DXP/chart/operator/provider-Ready combination and publication dates were not established. Scope: Reviewed public evidence for Liferay DXP Cloud Native Experience; unresolved within this edition/deployment. Source: https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience (reviewed 2026-11-17).







## Squidex

Self-hosted headless CMS with structured content, APIs and assets.

- Listing: https://launchinyourcloud.com/directory/squidex/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, render, heroku, vultr
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Application platform deployment
- Architecture: Squidex application, database and asset storage using provider-specific instructions.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://squidex.io
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.

MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Squidex application, database and asset storage using provider-specific instructions. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- content-management: Self-hosted headless CMS with structured content, APIs and assets.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-aws-ec2 (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-azure (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-gcp (checked 2026-11-19). 

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-render (checked 2026-11-19). 

- heroku: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-heroku (checked 2026-11-19). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-vultr (checked 2026-11-19). 


### Cloud deployment evidence

- AWS EC2 Guide (aws): https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-aws-ec2
  Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Guide (azure): https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-azure
  Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- GCP Guide (gcp): https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-gcp
  Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Render Guide (render): https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-render
  Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Install on Heroku | Squidex (heroku): https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-heroku
  Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Install on Vultr | Squidex (vultr): https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-vultr
  Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes SebastianStehle, kamushadenes, seamys, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/Squidex/squidex/graphs/contributors

- Upstream project: https://github.com/Squidex/squidex

### Sources

- AWS EC2 Guide: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-aws-ec2

- Azure Guide: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-azure

- GCP Guide: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-gcp

- Render Guide: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-render

- Install on Heroku | Squidex: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-heroku

- Install on Vultr | Squidex: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-vultr

- MIT LICENSE: https://github.com/Squidex/squidex/blob/master/LICENSE

- Releases v7.24.0: https://github.com/Squidex/squidex/releases

### Licensing sources

- https://github.com/Squidex/squidex/blob/master/LICENSE

### Infrastructure sources

- https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-aws-ec2

- https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-azure

- https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-gcp

- https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-render

- https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-heroku

- https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-vultr


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 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: Documented. The official external-identity guide documents configuring an external Azure AD/OAuth identity provider for self-hosted Squidex. The Compose example also exposes Google/GitHub/Microsoft credentials. The separately documented Squidex.Identity project is deprecated and must not be presented as a maintained SSO service. Scope: Self-hosted Squidex external-provider configuration; not the deprecated Squidex.Identity server. Source: https://docs.squidex.io/id-01-getting-started/installation/external-identity-providers (reviewed 2026-11-20). Supporting source: Upstream Compose identity configuration — https://raw.githubusercontent.com/Squidex/squidex-hosting/master/docker-compose/docker-compose.yml.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream hosting repository supplies a Compose stack with Squidex 7, MongoDB 6 and a Caddy proxy, persistent mounts and environment-based identity settings. These moving examples need compatible supported image versions, secrets and backups; the stack is not a replicated database/HA design. Scope: Upstream Squidex 7 Compose example; assess database support and image versions separately. Source: https://raw.githubusercontent.com/Squidex/squidex-hosting/master/docker-compose/docker-compose.yml (reviewed 2026-11-20). Deployment artifact: https://github.com/Squidex/squidex-hosting/tree/master/docker-compose. Artifact reference: master (moving branch); Squidex major 7 / MongoDB major 6 in reviewed example.

- Minimum footprint / sizing: Sources checked — unresolved. The official Compose stack establishes application, MongoDB and proxy dependencies, but no quantitative CPU/RAM/storage production floor was established in the reviewed installation materials. Confirm content volume, database replication, caches and concurrency before sizing. Scope: Upstream deployment topology; no workload-tested minimum established. Source: https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-docker (reviewed 2026-11-20). Supporting source: Reviewed Compose services — https://raw.githubusercontent.com/Squidex/squidex-hosting/master/docker-compose/docker-compose.yml.

- License pricing: Documented. MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Squidex; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/Squidex/squidex/blob/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream 7.24.0 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Squidex upstream application; verify compatibility with the selected package. Source: https://github.com/Squidex/squidex/releases/tag/7.24.0 (reviewed 2026-11-19).







## Strapi Self-Hosted

Headless CMS for managing structured content and delivering it through APIs.

- Listing: https://launchinyourcloud.com/directory/strapi/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT core; commercial Growth/Enterprise features and terms differ
- Licensing model: open-source
- Installation: Node.js production deployment with a supported SQL database; container/Kubernetes options
- Architecture: Customer-operated Node.js CMS, admin panel and database
- Operations: Customer operates application servers, database, media storage, backups and upgrades.
- Product website: https://strapi.io/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This entry covers self-hosted Strapi, not Strapi Cloud. Review workflows, audit logs and other editorial controls are plan-dependent. Confirm supported database/runtime versions and storage requirements for the selected release. Strapi 5.62.0, released November 12, 2026, includes a security patch whose detailed disclosure was delayed to allow operators time to upgrade. It also changes invalid boolean-filter handling, so self-hosted operators should review compatibility and upgrade promptly. Strapi v5.63.0 changes filter behavior: invalid or previously dropped conditions now return errors or no results, arrays are limited to 100 items, null semantics change, locale permissions are not automatically restored, and AI jobs require rolling-upgrade care. Test existing queries, permissions, and mixed-version nodes before rollout.

The broad self-hosted listing includes the MIT core and separately licensed Enterprise feature code under ee/ directories; paid hosting alone is not the reason for this classification.

Classified for the documented long-running Node.js application/server deployment with a database; headless APIs do not imply a function-based or static-only deployment.


### Category fit

- content-management: Headless content management with content modeling, editorial administration and APIs; paid governance features depend on plan.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://strapi.io/hosting (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://strapi.io/hosting (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://strapi.io/hosting (checked 2026-11-12). 


### Cloud deployment evidence

- Strapi self-hosting compatibility (aws, azure, gcp): https://strapi.io/hosting
  The vendor explicitly identifies AWS, Azure and Google Cloud for self-hosted Strapi. This is its Node.js application in customer infrastructure, not Strapi Cloud; production database, backups and updates remain customer responsibilities.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Self-hosted deployment requirements: https://docs.strapi.io/cms/deployment

- Project functionality and core license: https://github.com/strapi/strapi

- Licensing and edition terms: https://github.com/strapi/strapi/blob/develop/packages/core/content-manager/LICENSE

- Strapi 5.62.0 security release: https://github.com/strapi/strapi/releases/tag/v5.62.0

- Strapi v5.63.0 release: https://github.com/strapi/strapi/releases/tag/v5.63.0

### Licensing sources

- https://github.com/strapi/strapi/blob/develop/packages/core/content-manager/LICENSE

- https://docs.strapi.io/cms/deployment

### Infrastructure sources

- https://docs.strapi.io/cms/deployment


### 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 self-hosted pricing page offers SSO as a paid Growth add-on and includes it in Enterprise. The listed identity options include SAML 2.0 and OAuth2 providers; Community does not gain those entitlements. Scope: CMS self-hosted admin-user authentication; paid-plan/add-on scope. Source: https://strapi.io/pricing-self-hosted (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 Strapi 5 Docker guide supplies development/production Dockerfile and Compose examples for building your own application image. Strapi explicitly does not publish an official container image; do not label a third-party image as upstream-supported. Scope: Upstream courtesy examples for a custom Strapi 5 project. Source: https://docs.strapi.io/cms/installation/docker (reviewed 2026-11-20). Deployment artifact: https://docs.strapi.io/cms/installation/docker. Artifact reference: Current Strapi 5 Dockerfile/Compose examples; pin project dependencies and base images.

- Minimum footprint / sizing: Documented. The deployment guide lists a minimum of 1 CPU core, 2 GB RAM and 8 GB disk, with 2+ cores, 4 GB+ and 32 GB+ recommended. Database and workload sizing remain separate. Scope: Strapi deployment-guide baseline; not an end-to-end infrastructure bill. Source: https://docs.strapi.io/cms/deployment (reviewed 2026-11-14).

- License pricing: Documented. Community is free under MIT. Growth is listed at $45/month including three admin users, with additional users at $15/month. SSO is a separate priced add-on; Enterprise is quoted. Hosting is separate. Scope: Self-hosted CMS software plans; not Strapi Cloud hosting. Source: https://strapi.io/pricing-self-hosted (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Strapi v5.63.0 was published November 18, 2026. It changes invalid-filter, array-limit, null, locale-permission, and AI-job behavior; test queries and rolling upgrades before rollout. Scope: Upstream Strapi 5 release. Source: https://github.com/strapi/strapi/releases/tag/v5.63.0 (reviewed 2026-11-18).







## WordPress Self-Hosted

Open-source content management system with documented customer-account deployments across major clouds and application-provider images.

- Listing: https://launchinyourcloud.com/directory/wordpress-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean, oci, linode, vultr
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GPLv2 or later; themes, plugins and provider packaging may have separate terms.
- Licensing model: open-source
- Installation: Provider application images/blueprints, Azure App Service quickstart, OCI Resource Manager template, or Akamai StackScript; package and topology vary by provider
- Architecture: PHP application with a customer-controlled MySQL or MariaDB database and persistent media storage.
- Operations: Customer manages WordPress core, themes and plugins, application security, identities, content, database, media, backups, scaling and upgrades.
- Product website: https://wordpress.org/
- Source review: 2026-11-19; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

This entry covers WordPress.org self-hosting, not WordPress.com SaaS. Provider blueprints accelerate installation but do not replace application hardening, backup, patching and plugin review. Provider packages can lag upstream. The current recommended PHP/database versions and application/plugin stack need a separate patch and HA review. WordPress 7.1.5 is a security release fixing multisite privilege escalation to Super Admin, stored and reflected XSS paths and media-type hardening. Security fixes were backported to eligible older branches. Update immediately, and verify provider images that still advertise 7.1.4 or earlier rather than assuming the platform package is current.

WordPress core is released under GPLv2 or later. Themes, plugins and provider images can add separate licenses or charges.

WordPress runs on provisioned application and database capacity with durable media and database state, even when a provider manages parts of the substrate.


### Category fit

- content-management: Publishes websites, blogs and extensible structured content with themes, plugins and a browser-based editorial interface.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-quick-start-guide-wordpress.html (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://learn.microsoft.com/en-us/azure/app-service/quickstart-wordpress (checked 2026-11-18). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://cloud.google.com/wordpress (checked 2026-11-18). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.digitalocean.com/products/marketplace/catalog/wordpress/ (checked 2026-11-18). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.oracle.com/en-us/iaas/Content/ResourceManager/Reference/templates.htm (checked 2026-11-18). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://techdocs.akamai.com/quick-deploy-apps/docs/wordpress (checked 2026-11-18). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.vultr.com/one-click-wordpress (checked 2026-11-18). 


### Cloud deployment evidence

- WordPress in the customer's Amazon Lightsail account (aws): https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-quick-start-guide-wordpress.html
  AWS documents selecting a region, launching the WordPress blueprint and operating the instance in the customer's Lightsail account.
  Source type: provider-guide; reviewed: 2026-11-18; vendor support: not-assessed.

- WordPress on Azure App Service (azure): https://learn.microsoft.com/en-us/azure/app-service/quickstart-wordpress
  Microsoft's quickstart deploys the WordPress Marketplace item and backing Azure resources into the customer's selected subscription and resource group.
  Source type: provider-guide; reviewed: 2026-11-18; vendor support: not-assessed.

- WordPress on Google Cloud (gcp): https://cloud.google.com/wordpress
  Google documents customer deployments of WordPress on Google Cloud, including a Compute Engine path. Provider packaging and support scope must be reviewed.
  Source type: provider-guide; reviewed: 2026-11-18; vendor support: not-assessed.

- WordPress DigitalOcean 1-Click application (digitalocean): https://docs.digitalocean.com/products/marketplace/catalog/wordpress/
  DigitalOcean installs the full WordPress application and database on a customer Droplet. Confirm the resolved image version and production/HA design.
  Source type: provider-guide; reviewed: 2026-11-18; vendor support: not-assessed.

- OCI Resource Manager WordPress template (oci): https://docs.oracle.com/en-us/iaas/Content/ResourceManager/Reference/templates.htm
  Oracle lists a Resource Manager quickstart that deploys a WordPress instance into OCI. It is a provider application template, not a WordPress support contract or HA guarantee.
  Source type: provider-guide; reviewed: 2026-11-18; vendor support: not-assessed.

- WordPress on Akamai Cloud (Linode) (linode): https://techdocs.akamai.com/quick-deploy-apps/docs/wordpress
  Akamai documents full application/database deployment on a customer Compute Instance using StackScript 401697, with Cloud Manager and API/CLI inputs.
  Source type: provider-guide; reviewed: 2026-11-18; vendor support: not-assessed.

- Vultr One-Click WordPress (vultr): https://docs.vultr.com/one-click-wordpress
  Vultr documents launching the full WordPress application on the customer’s selected server size/location and configuring its administrator, domain and TLS.
  Source type: provider-guide; reviewed: 2026-11-18; vendor support: not-assessed.


### Community and maintenance

The project maintains a dated core release history and documents NASA’s WordPress-based web properties. This establishes maintained software and named adoption, not the cloud account or suitability of a particular plugin stack.

Reviewed 2026-11-18.

- Official maintenance and adoption evidence: https://wordpress.org/documentation/article/wordpress-versions/

- Official maintenance and adoption evidence: https://wordpress.org/showcase/nasa/

### Sources

- Launch and configure WordPress on Amazon Lightsail: https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-quick-start-guide-wordpress.html

- Create a WordPress site on Azure App Service: https://learn.microsoft.com/en-us/azure/app-service/quickstart-wordpress

- WordPress on Google Cloud: https://cloud.google.com/wordpress

- WordPress GPL license: https://wordpress.org/about/license/

- WordPress DigitalOcean 1-Click application: https://docs.digitalocean.com/products/marketplace/catalog/wordpress/

- OCI Resource Manager WordPress template: https://docs.oracle.com/en-us/iaas/Content/ResourceManager/Reference/templates.htm

- WordPress on Akamai Cloud (Linode): https://techdocs.akamai.com/quick-deploy-apps/docs/wordpress

- Vultr One-Click WordPress: https://docs.vultr.com/one-click-wordpress

- WordPress 7.1.5 security release: https://wordpress.org/news/2026/11/wordpress-7-1-5-release/

- WordPress 7.1.5 documentation: https://wordpress.org/documentation/wordpress-version/version-7-1-5/

### Licensing sources

- https://wordpress.org/about/license/

### Infrastructure sources

- https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-quick-start-guide-wordpress.html

- https://learn.microsoft.com/en-us/azure/app-service/quickstart-wordpress


### Buyer diligence


Research coverage: 12/12 fields (100%); 8 documented, 4 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: Documented. DigitalOcean offers a WordPress 1-Click Droplet, currently including WordPress 7.1.4, PHP 8.3.36 and MySQL 8.0.46. That database version is below WordPress’s current MySQL 8.4 recommendation. Microsoft also documents an App Service Marketplace item. Packaging and infrastructure charges are separate from WordPress.com. Scope: WordPress Self-Hosted: selected customer-operated edition. Source: https://docs.digitalocean.com/products/marketplace/catalog/wordpress/ (reviewed 2026-11-18). Supporting source: Microsoft WordPress deployment — https://learn.microsoft.com/en-us/azure/app-service/quickstart-wordpress. Supporting source: Lightsail WordPress blueprint — https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-quick-start-guide-wordpress.html. Supporting source: Upstream runtime/database recommendations — https://wordpress.org/about/requirements/. Offer wordpress: DigitalOcean; Droplet 1-Click application; package WordPress 7.1.4; package label latest; https://marketplace.digitalocean.com/apps/wordpress.

- Cloud commitment eligibility: Sources checked — unresolved. The Azure quickstart creates App Service and database resources, but does not establish software-offer commitment credit. Check the selected provider charges and the buyer’s agreement; WordPress core’s free license is not a transactable commitment claim. Scope: WordPress Self-Hosted: selected customer-operated edition. Source: https://learn.microsoft.com/en-us/azure/app-service/quickstart-wordpress (reviewed 2026-11-18). Supporting source: AWS commitment qualification is product/agreement-specific — https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html.

- Single sign-on: Documented. OpenID Connect Generic Client 3.11.4 provides authorization-code SSO and optional account creation/linking for WordPress logins. It is a separately installed community plugin, not bundled core or a provider-image entitlement. It requires PHP 8.0+; configure the IdP, redirect URI and linking policy. Version 3.11.4 changes state/nonce validation and requires review of PKCE and existing-user linking settings. Scope: Optional OpenID Connect Generic Client 3.11.4; WordPress user login, not every theme/plugin or external application. Source: https://wordpress.org/plugins/daggerhart-openid-connect-generic/ (reviewed 2026-11-18). Deployment artifact: https://downloads.wordpress.org/plugin/daggerhart-openid-connect-generic.3.11.4.zip. Artifact reference: OpenID Connect Generic Client 3.11.4.

- SCIM provisioning: Edition-dependent. miniOrange supplies an optional inbound SCIM endpoint: the IdP sends users to WordPress using a base URL and bearer token. Free creation is documented; profile updates, deletion/deactivation and reactivation require Premium. Enhanced group push/import are listed as future work. Soft deactivation retains the account and blocks login, but the guides do not establish revocation of existing sessions. Public package 1.2.0 is separate from the licensed Premium delivery. Scope: Third-party miniOrange WordPress provisioning plugin; inbound users, with Premium lifecycle operations; not native core SCIM. Source: https://wordpress.org/plugins/scim-user-provisioning/ (reviewed 2026-11-18). Supporting source: Provisioning operations, Premium boundary and group limitations — https://plugins.miniorange.com/wordpress-scim-user-provisioning.

- Compliance attestations: Sources checked — unresolved. The WordPress security paper describes project practices, not an independent attestation covering the buyer’s site, plugins, hosting and operations. Obtain the deployment-specific control and audit scope. Scope: WordPress Self-Hosted: selected customer-operated edition. Source: https://wordpress.org/about/security/ (reviewed 2026-11-18).

- Security controls: Documented. The hardening guide covers restricted database privileges, file permissions, protecting wp-config.php, disabling dashboard file editing, backups and logging. Core, theme and plugin updates remain customer responsibilities; a provider image does not complete this work. Current review: WordPress 7.1.5 fixes multisite privilege escalation to Super Admin, stored and reflected XSS paths and media-type hardening. Update immediately or use the corresponding supported backport, and verify the exact provider image version. Scope: WordPress core 7.1 and eligible backported branches; third-party themes and plugins are outside this advisory. Source: https://wordpress.org/news/2026/11/wordpress-7-1-5-release/ (reviewed 2026-11-19). Supporting source: Prior security-controls source — https://developer.wordpress.org/advanced-administration/security/hardening/. Supporting source: Optional OIDC plugin 3.11.4 security settings and upgrade behavior — https://wordpress.org/plugins/daggerhart-openid-connect-generic/.

- Air-gapped operation: Sources checked — unresolved. WordPress documents manual updates and WP_HTTP_BLOCK_EXTERNAL for requests made through its HTTP API. The latter allows local/site requests and does not govern arbitrary PHP networking by plugins. These controls do not validate a disconnected lifecycle for a selected theme/plugin stack. Confirm offline packages, licences, mail, IdP, media/CDN and update dependencies for that stack. Scope: WordPress Self-Hosted: selected customer-operated edition. Source: https://developer.wordpress.org/reference/classes/wp_http/block_request/ (reviewed 2026-11-18). Supporting source: Manual core update procedure — https://wordpress.org/documentation/article/updating-wordpress/.

- Deployment artifact / IaC: Documented. Akamai documents WordPress StackScript 401697 and maps its database, administrator and web-server inputs to Cloud Manager and API/CLI deployment. AWS supplies a Lightsail blueprint and OCI lists a Resource Manager WordPress template. These are provider-managed moving packages, not a pinned upstream application release. Scope: WordPress Self-Hosted: selected customer-operated edition. Source: https://techdocs.akamai.com/quick-deploy-apps/docs/wordpress (reviewed 2026-11-18). Supporting source: Lightsail blueprint — https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-quick-start-guide-wordpress.html. Supporting source: OCI Resource Manager application templates — https://docs.oracle.com/en-us/iaas/Content/ResourceManager/Reference/templates.htm.

- Minimum footprint / sizing: Documented. The project recommends PHP 8.3+, MariaDB 10.11+ or MySQL 8.4+, and HTTPS; Apache or Nginx is recommended. It does not give a universal CPU/RAM minimum. PHP 7.4/MySQL 5.5.5 compatibility is a legacy fallback, not a recommendation to use those EOL runtimes. Scope: WordPress Self-Hosted: selected customer-operated edition. Source: https://wordpress.org/about/requirements/ (reviewed 2026-11-18).

- License pricing: Documented. WordPress core is GPLv2 or later, without a core software subscription. Themes, plugins, commercial support and provider packaging may introduce separate terms and charges. Hosting and operations are additional. Scope: WordPress Self-Hosted: selected customer-operated edition. Source: https://wordpress.org/about/license/ (reviewed 2026-11-18).

- Operating cost estimate: Sources checked — unresolved. 100 internal users and 1 TB do not determine page requests, PHP workers, database I/O or media delivery. Specify traffic/concurrency, plugin stack, cache/CDN, media versus database storage, HA database and application design, backups, egress and paid extensions before estimating AWS us-east-1 operations. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://wordpress.org/about/requirements/ (reviewed 2026-11-18). Supporting source: Current AWS Linux EC2 rates; workload/topology still required — https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json. Supporting source: Storage performance and charging inputs — https://aws.amazon.com/ebs/pricing/.

- Release snapshot / cadence: Documented. WordPress 7.1.5 was released November 18, 2026. It is a security release fixing multisite privilege escalation, stored and reflected XSS paths and media-type hardening. Eligible older branches received backports; provider packages may lag. Scope: WordPress.org self-hosted core; themes, plugins and provider images require separate version review. Source: https://wordpress.org/news/2026/11/wordpress-7-1-5-release/ (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://wordpress.org/documentation/article/wordpress-versions/. Supporting source: Version-specific documentation — https://wordpress.org/documentation/wordpress-version/version-7-1-5/.




### Security and lifecycle reviews

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

- Optional WordPress OIDC plugin security settings need review (security-advisory): OpenID Connect Generic Client 3.11.4 changes login state, nonce and verified-email linking checks. PKCE defaults on for new installs but stays off on existing sites until enabled. Scope: Only WordPress sites using the optional OpenID Connect Generic Client plugin; this is not a WordPress core or every-provider-image advisory. Conditions: Existing sites that link users have Link Users Without Verified Email enabled during upgrade and receive an admin notice. The changelog provides no universal affected-version range or CVE. Action: Use the current reviewed plugin, enable PKCE after IdP testing and review linking without verified email. Check callback, account linking and recovery behavior rather than assuming upgrade changes all existing settings. Source: https://wordpress.org/plugins/daggerhart-openid-connect-generic/; reviewed 2026-11-18.

- WordPress 7.1.5 security release (security-advisory): WordPress 7.1.5 fixes multisite privilege escalation to Super Admin, stored and reflected XSS paths and media-type hardening. Scope: WordPress core 7.1 and eligible supported backport branches; themes and plugins remain separate. Conditions: Multisite administration, block-editor/media workflows and the installed core branch determine applicability. Action: Update immediately to 7.1.5 or the corresponding supported backport and verify the exact provider-image version. Source: https://wordpress.org/news/2026/11/wordpress-7-1-5-release/; reviewed 2026-11-19.



