
# Content management & CMS on AWS

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

Canonical page: https://launchinyourcloud.com/clouds/aws/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: AWS account
- 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.aws.amazon.com/accounts/latest/reference/getting-started.html (checked 2026-11-20).
- Network: VPC
- Identity and access: IAM roles and policies
- Installation guidance: CloudFormation or Terraform; review stack changes and requested IAM permissions.
- Guidance source: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html
- Guidance reviewed: 2026-11-10


### Private offers

AWS Marketplace private offers can contain negotiated pricing and terms for a buyer account. Confirm the product delivery model and your agreement; commitment credit is not established by a directory badge.
Source: https://docs.aws.amazon.com/marketplace/latest/buyerguide/buyer-private-offers-subscribing.html (reviewed 2026-11-14).

### Private connectivity

PrivateLink provides private endpoints to supported services and resources across VPC/account boundaries. Confirm that the selected product exposes a compatible endpoint service.
Source: https://docs.aws.amazon.com/vpc/latest/privatelink/what-is-privatelink.html (reviewed 2026-11-14).

### Cross-account operations

Use an IAM role with scoped permissions and a third-party external ID where applicable. Review the trust principal, support access and revocation separately from installation access.
Source: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_third-party.html (reviewed 2026-11-14).

### Government environments

AWS GovCloud (US) is a distinct isolated-region environment. A commercial-region product deployment does not establish availability or certification there.
Source: https://docs.aws.amazon.com/govcloud-us/latest/UserGuide/whatis.html (reviewed 2026-11-14).

The listings below have evidence for Amazon Web Services. Read each cloud evidence note for the applicable package, edition and support qualifications.

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




## CrafterCMS

Self-hosted content authoring and delivery platform.

- Listing: https://launchinyourcloud.com/directory/craftercms/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU GPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Kubernetes manifests
- Architecture: Crafter Studio, delivery services and stateful dependencies in customer AWS EKS.
- 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://github.com/craftersoftware/craftercms
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The reviewed Terraform architecture deploys the actual application. Generic statements about other Kubernetes platforms do not establish another provider-specific recipe.

GNU GPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Crafter Studio, delivery services and stateful dependencies in customer AWS EKS. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- content-management: Self-hosted content authoring and delivery platform.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/craftercms/crafter-aws-base (checked 2026-11-19). 


### Cloud deployment evidence

- crafter-aws-base (aws): https://github.com/craftercms/crafter-aws-base
  Crafter Studio, delivery services and stateful dependencies in customer AWS EKS. The reviewed Terraform architecture deploys the actual application. Generic statements about other Kubernetes platforms do not establish another provider-specific recipe.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes sumerjabri, jdrossl, jmendeza, 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/craftersoftware/craftercms/graphs/contributors

- Upstream project: https://github.com/craftersoftware/craftercms

### Sources

- crafter-aws-base: https://github.com/craftercms/crafter-aws-base

- Crafter Community: https://craftercms.com/products/crafter-community

- GPL-3.0 LICENSE: https://github.com/craftercms/craftercms/blob/develop/LICENSE

- Releases v4.7.1: https://github.com/craftercms/craftercms/releases

### Licensing sources

- https://github.com/craftercms/craftercms/blob/develop/LICENSE

### Infrastructure sources

- https://github.com/craftercms/crafter-aws-base


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 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: Documented. Current Crafter Studio documentation provides SAML and authenticated-header SSO configurations for authoring users. LDAP is separately documented. Public-site/Profile user authentication and service entitlement are distinct from Studio author login. Scope: CrafterCMS 4.7 Studio authoring authentication. Source: https://craftercms.com/docs/current/reference/modules/studio.html (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 installation documentation uses the craftercms/docker-compose repository with separate authoring and delivery directories. Configure production secrets and change default credentials; local Docker Desktop settings and a single-instance example are not an HA design. Scope: Current 4.7 authoring/delivery container installation. Source: https://craftercms.com/docs/current/by-role/system-admin/installation.html (reviewed 2026-11-20). Deployment artifact: https://github.com/craftercms/docker-compose. Artifact reference: Moving upstream deployment repository; select compatible authoring/delivery image versions.

- Minimum footprint / sizing: Documented. The scaling guide separates tiers: minimum traditional delivery is 4 cores/8 GB RAM plus swap, while authoring for roughly 1–10 concurrent users recommends 4 cores/16 GB RAM plus swap. Add search, content/storage, replicas and HA resources; do not substitute local Docker Desktop allocations for production sizing. Scope: Current 4.7 tier-specific starting recommendations; not validated 100-user/1-TB HA capacity. Source: https://craftercms.com/docs/current/by-role/system-admin/performance-and-scaling.html (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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







## Drupal

Open-source content management system for building and operating websites.

- Listing: https://launchinyourcloud.com/directory/drupal/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GPL version 2 or later for Drupal and derivative contributed files hosted by the project.
- Licensing model: open-source
- Installation: Install on your host with Composer using drupal/recommended-project and complete the site setup.
- Architecture: PHP web application with a persistent database; hosting and caching choices are implementation-specific.
- Operations: Own hosting, access control, backups, supported core/module updates and production configuration.
- Product website: https://www.drupal.org/
- Source review: 2026-11-19; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Extensions and themes expand the system; assess their maintenance and permissions individually. Drupal SA-CORE-2026-017 fixes a Critical installer path that can permit site takeover or remote code execution under specific conditions; SA-CORE-2026-018 removes a gadget chain that becomes exploitable when another insecure-deserialization flaw is present. Supported fixed releases are 11.4.13, 11.3.22 and 10.6.22. Older branches are end of life. Upgrade immediately and secure install.php/settings.php as the advisory describes.

Drupal is GPLv2-or-later. Commercial hosting, implementation or support does not turn the listed core into a proprietary edition.

The documented self-hosted PHP website and database run on server infrastructure; a static frontend would be a separate implementation.


### Category fit

- content-management: A dedicated extensible website CMS for structured content, publishing and digital experiences.

### 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-drupal.html (checked 2026-11-12). 


### Cloud deployment evidence

- Drupal server on Amazon Lightsail (aws): https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-quick-start-guide-drupal.html
  AWS documents operating a Drupal server instance on Lightsail, including administrator access, DNS, HTTPS and snapshots. Its example uses Bitnami packaging; check the current Drupal version, image terms and updates. The deployment is in the customer AWS account rather than a hosted Drupal SaaS service.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The project publishes maintained Drupal 10 and 11 release streams, including 2026 production releases. Its official technical overview identifies UNICEF and the Georgia Technology Authority as adopters.

Reviewed 2026-11-10.

- Maintained core releases: https://www.drupal.org/project/drupal/releases?version=1

- Named institutional adoption: https://new.drupal.org/about/overview/technical

### Sources

- Project capabilities and named users: https://www.drupal.org/about

- Composer installation: https://www.drupal.org/docs/getting-started/installing-drupal/get-the-code

- Licensing: https://www.drupal.org/about/licensing

- Current core releases: https://www.drupal.org/project/drupal/releases?version=1

- Drupal critical core release notice for November 18, 2026: https://www.drupal.org/psa-2026-11-16

- SA-CORE-2026-017 critical remote code execution: https://www.drupal.org/sa-core-2026-017

- SA-CORE-2026-018 gadget chain: https://www.drupal.org/sa-core-2026-018

- Drupal current core security releases: https://www.drupal.org/project/drupal/releases

### Licensing sources

- https://www.drupal.org/about/licensing

### Infrastructure sources

- https://www.drupal.org/docs/getting-started/installing-drupal/get-the-code


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The contributed OpenID Connect/OAuth client module authenticates site users through an external provider and can create Drupal users on first login. This requires installing and configuring a compatible contributed module; it is not a native Drupal-core SAML guarantee. Scope: Official Drupal.org contributed-module page; validate module/core compatibility. Source: https://www.drupal.org/project/openid_connect (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. SA-CORE-2026-017 can permit site takeover or RCE through install.php under specific conditions; SA-CORE-2026-018 removes a gadget chain that requires a separate insecure-deserialization path. Upgrade to 11.4.13, 11.3.22 or 10.6.22 and secure the installer and settings.php. Scope: Drupal core before 11.4.13, 11.3.22 or 10.6.22 on the supported branches. Source: https://www.drupal.org/sa-core-2026-017 (reviewed 2026-11-19). Supporting source: SA-CORE-2026-018 — https://www.drupal.org/sa-core-2026-018.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Drupal documents drupal/recommended-project as its official Composer project template. It installs core and locked dependencies with a separate web root; add an explicit version and review contributed modules. This is an application scaffold, not cloud infrastructure automation. Scope: Drupal Composer application template; provider packaging and runtime remain separate. Source: https://www.drupal.org/docs/develop/using-composer/manage-dependencies (reviewed 2026-11-14). Deployment artifact: https://github.com/drupal/recommended-project. Artifact reference: select a released Composer package version; default template resolves current stable.

- Minimum footprint / sizing: Documented. The upstream memory guide lists 1 GB minimum RAM and advises at least 1 GB free for Composer work. Its PHP memory settings are per-process limits, not VM sizing. The page includes Drupal 10 examples and does not validate a newer packaged image or 100-user/1-TB HA capacity. Scope: Dated upstream baseline memory guidance; benchmark the chosen Drupal version/modules. Source: https://www.drupal.org/docs/getting-started/system-requirements/memory-requirements (reviewed 2026-11-20).

- License pricing: Documented. Drupal and derivative contributed code on Drupal.org are GPL version 2 or later and can be downloaded, reused and modified under those terms. This does not include hosting, implementation, commercial support or separately supplied assets/services. Scope: Drupal project licensing FAQ; core software rather than a hosting plan. Source: https://www.drupal.org/about/licensing (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Drupal 11.4.13 is the current reviewed security release, dated November 18, 2026. Supported alternatives 11.3.22 and 10.6.22 carry the same SA-CORE-2026-017 and SA-CORE-2026-018 fixes; older branches are end of life. Scope: Drupal core supported branches; choose the fixed release for the installed maintained line. Source: https://www.drupal.org/project/drupal/releases/11.4.13 (reviewed 2026-11-19). Supporting source: Critical installer RCE advisory — https://www.drupal.org/sa-core-2026-017. Supporting source: Gadget-chain advisory — https://www.drupal.org/sa-core-2026-018.




### Security and lifecycle reviews

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

- Drupal planned critical core security updates (security-advisory): The security team announced critical fixes for November 18, 2026, 17:00–21:00 UTC, including an issue reachable without authentication. Scope: Pre-release notice for supported Drupal core lines; fixed versions and complete technical details were not yet published in the reviewed PSA. Conditions: More than one configuration is affected. Do not infer safety from authentication or from an unspecified configuration. Action: Prepare on a current supported bugfix release and reserve the announced patch window. Follow the final advisory when published; no fixed version is asserted here. Source: https://www.drupal.org/psa-2026-11-16; reviewed 2026-11-17.

- Drupal SA-CORE-2026-017 and SA-CORE-2026-018 (security-advisory): Drupal fixed a Critical installer path that can permit takeover or RCE and a separate gadget chain that can amplify another insecure-deserialization flaw. Scope: Drupal before 11.4.13, 11.3.22 or 10.6.22 on the supported branches; older branches are end of life. Conditions: The Critical path depends on installer and settings.php conditions; the gadget chain requires another unsafe deserialization path. Action: Upgrade immediately to the fixed supported branch and secure install.php and settings.php as documented. Source: https://www.drupal.org/sa-core-2026-017; reviewed 2026-11-19. Supporting source: SA-CORE-2026-018 — https://www.drupal.org/sa-core-2026-018.




## Grav

Self-hosted flat-file content management system.

- Listing: https://launchinyourcloud.com/directory/grav/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: linode, aws, digitalocean, vultr, hostinger, lumadock
- 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: Cloudron package
- Architecture: Grav PHP application and persistent content, configuration and plugins.
- 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://getgrav.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

No relational database is required by the base system; plugins and themes can introduce their own dependencies and licences. Cloudron package and upstream versions can differ.

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

Grav PHP application and persistent content, configuration and plugins. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- content-management: Self-hosted flat-file content management system.

### Deployment boundaries


- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/grav.html (checked 2026-11-19). 

- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/grav.html (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/grav.html (checked 2026-11-19). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/grav.html (checked 2026-11-19). 

- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/grav.html (checked 2026-11-19). 

- lumadock: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/grav.html (checked 2026-11-19). 


### Cloud deployment evidence

- Cloudron Store (linode, aws, digitalocean, vultr, hostinger, lumadock): https://www.cloudron.io/store/grav.html
  The reviewed Cloudron application package runs on the customer server. Pair it with Cloudron’s named-provider installation procedure; Cloudron subscriptions, package updates and upstream support are separate.
  Source type: package-platform-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes rhukster, flaviocopes, w00fz, 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/getgrav/grav/graphs/contributors

- Upstream project: https://github.com/getgrav/grav

### Sources

- Cloudron Store: https://www.cloudron.io/store/grav.html

- Akamai Quick Deploy: https://techdocs.akamai.com/quick-deploy-apps/docs/grav

- MIT LICENSE.txt: https://github.com/getgrav/grav/blob/develop/LICENSE.txt

- Releases v2.2.30: https://github.com/getgrav/grav/releases

- Cloudron customer-server and named-provider installation: https://docs.cloudron.io/installation/

### Licensing sources

- https://github.com/getgrav/grav/blob/develop/LICENSE.txt

### Infrastructure sources

- https://www.cloudron.io/store/grav.html


### 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: Documented. The Grav project documents the Trilby Media login-oauth2 plugin for third-party OAuth2 login, extending the core Login plugin with named and custom providers. Validate plugin/core compatibility and the intended login surface; the old announcement is not proof that every current Admin deployment supports every provider. Scope: Official project announcement plus maintained plugin implementation; OAuth2 Login integration. Source: https://getgrav.org/blog/oauth2-and-ldap-login-plugins (reviewed 2026-11-20). Supporting source: Login OAuth2 maintainer repository — https://github.com/trilbymedia/grav-plugin-login-oauth2.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official installation guide supplies version-addressable ZIP packages, Composer installation and source installation. The Admin package includes the Admin plugin. This establishes a deployable application artifact, not a cloud-infrastructure or HA template. Scope: Versioned Grav 1.7 guide; verify current major-version compatibility. Source: https://learn.getgrav.org/17/basics/installation (reviewed 2026-11-20). Deployment artifact: https://getgrav.org/downloads. Artifact reference: Choose a tagged Grav/Core-plus-Admin package; do not assume current downloads match 1.7 instructions.

- Minimum footprint / sizing: Documented. The Cloudron package declares 256MB minimum app memory. The platform additionally requires at least 2 GB RAM and 20 GB disk; this is not whole-system, data-volume or HA sizing. Scope: Selected Cloudron application package; add database, files, backups and concurrent workload requirements. Source: https://www.cloudron.io/store/grav.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

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

- Operating cost estimate: Not researched.

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







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







## Pimcore Platform

Integrated digital asset and content management platform with configurable data models and publishing APIs.

- Listing: https://launchinyourcloud.com/directory/pimcore/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Pimcore Open Core License (POCL); free eligibility and commercial edition requirements apply.
- Licensing model: source-available
- Installation: Use the documented Docker installation packages and configure your own hosting environment.
- Architecture: Containerized PHP application with persistent database, file storage and caching services.
- Operations: Operate hosting, database, files, caching, backups, updates and integrations; budget for implementation.
- Product website: https://pimcore.com/
- Source review: 2026-11-16; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Current editions use POCL rather than GPL. Enterprise blueprints require repository credentials; do not assume the free edition includes every advertised module. Pimcore 2026.3.5 hardens WebDAV asset permissions, document and object preview authorization, public-version ownership, password-field handling, document-editable deserialization, WebDAV delete logs, and stored-expression evaluation. Test calculated values, workflow guards, and custom document editables before rollout: unsupported expression methods are now rejected, and custom serialized classes must be allow-listed or converted to scalar or array storage. Operators on the 2026.x line should update to 2026.3.5 or later.

POCL is source-available with commercial and revenue-related conditions, not the former GPLv3 license. The current editions page describes free Community eligibility below EUR/USD 5 million annual revenue and for nonprofits/academic institutions. Check the applicable contract and module entitlements.

Documented own hosting uses a Docker application environment with database and persistent files; classified as servers.


### Category fit

- digital-asset-management: DAM capabilities include media storage, metadata, versions, asset workflows and distribution; feature availability depends on edition.

- content-management: The platform combines traditional and headless content management with reusable content, multilingual sites and multichannel publishing.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.metaways.de/en/pimcore-2/ (checked 2026-11-12). Source: https://pimcore.com/en/partners/technology-connectors (checked 2026-11-12). 


### Cloud deployment evidence

- Pimcore deployment in an existing customer AWS account through Metaways (aws): https://www.metaways.de/en/pimcore-2/
  Pimcore technology partner Metaways explicitly offers the Pimcore platform in an existing customer AWS account, with cloud resources under customer control and optional/contracted partner operations. This establishes a customer-account hosting path, not an assurance that every edition is unrestricted or customer-operated by default. Review current POCL/module entitlements and the operations agreement. Azure is described as a future option and is not assigned.
  Source type: partner-evidence; reviewed: 2026-11-12; vendor support: not-assessed.

- Pimcore identification of Metaways as a technology partner (aws): https://pimcore.com/en/partners/technology-connectors
  The Pimcore technology-alliance directory identifies Metaways as a partner. Pair that relationship with Metaways' explicit customer-AWS-account deployment statement; this partner listing alone is not the cloud evidence and does not establish current edition licensing.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- DAM and on-premises deployment: https://pimcore.com/en/products/digital-asset-management

- DAM and DXP content capabilities: https://pimcore.com/en/products/digital-asset-management/digital-asset-management?hsLang=en

- Installation: https://docs.pimcore.com/platform/2026.1/Getting_Started/Installation/

- Own hosting setup: https://docs.pimcore.com/platform/2026.1/Getting_Started/Installation/System_Setup_and_Hosting/

- Current edition license model: https://pimcore.com/en/products/open-core

- Pimcore upgrade notes: https://docs.pimcore.com/platform/Pimcore/Upgrade_Notes/

- Pimcore 2026.3.5 security release: https://github.com/pimcore/pimcore/releases/tag/v2026.3.5

### Licensing sources

- https://pimcore.com/en/products/open-core

- https://docs.pimcore.com/platform/2026.2/Pimcore/Installation_and_Upgrade/Upgrade_Notes/

### Infrastructure sources

- https://docs.pimcore.com/platform/2026.1/Getting_Started/Installation/System_Setup_and_Hosting/


### 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: Edition-dependent. The OpenID Connect enterprise bundle adds external-provider SSO to Pimcore Studio and requires an enterprise subscription. It is not a Community entitlement or a claim that every portal/front-end uses the same identity configuration. Scope: Current 2026.3 enterprise Studio bundle; installation requires Pimcore 2026.1+. Source: https://docs.pimcore.com/platform/OpenID_Connect/ (reviewed 2026-11-20). Supporting source: Enterprise bundle installation and prerequisites — https://docs.pimcore.com/platform/OpenID_Connect/Installation/.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The versioned 2026.2 guide documents the pimcore/skeleton Composer project and its Docker Compose environment. It is a local-development scaffold with placeholder credentials and mandatory product registration; hardening and commercial module access are separate. Scope: Pimcore 2026.2 skeleton, not a production-ready enterprise DAM configuration. Source: https://docs.pimcore.com/platform/2026.2/Getting_Started/Installation/Skeleton_Installation/ (reviewed 2026-11-14).

- Minimum footprint / sizing: Sources checked — unresolved. The current 2026.3 requirements list PHP 8.5+, database, Redis/search dependencies and a PHP memory_limit of at least 128M. That per-process setting is not a whole-server memory requirement; the reviewed guide does not establish a numeric production or 100-user/1-TB HA resource floor. Scope: Current 2026.3 component prerequisites; full production topology/sizing remains open. Source: https://docs.pimcore.com/platform/Getting_Started/Installation/System_Requirements (reviewed 2026-11-20).

- License pricing: Documented. The published POCL model permits free Community use for qualifying organizations below EUR/$5 million annual revenue, non-profits and academic institutions. Professional/Enterprise use and enterprise bundles have separate commercial entitlements; confirm the applicable subscription and quote. Scope: Published Open Core/Community eligibility and commercial edition positioning. Source: https://pimcore.com/en/products/open-core (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Plone

Self-hosted enterprise content management and publishing platform.

- Listing: https://launchinyourcloud.com/directory/plone/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, linode, digitalocean, hetzner
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: CloudFormation; Docker / Compose; Application platform deployment
- Architecture: Plone 6 backend, Volto frontend, database and persistent assets via plone-in-a-box.
- 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://plone.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The community provides provider-specific deployment examples; foundation governance does not imply a commercial support contract for those recipes.

GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Plone 6 backend, Volto frontend, database and persistent assets via plone-in-a-box. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- content-management: Self-hosted enterprise content management and publishing platform.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/collective/plone-in-a-box (checked 2026-11-19). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/collective/plone-in-a-box (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/collective/plone-in-a-box (checked 2026-11-19). 

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/collective/plone-in-a-box (checked 2026-11-19). 


### Cloud deployment evidence

- plone-in-a-box (aws, linode, digitalocean, hetzner): https://github.com/collective/plone-in-a-box
  Plone 6 backend, Volto frontend, database and persistent assets via plone-in-a-box. The community provides provider-specific deployment examples; foundation governance does not imply a commercial support contract for those recipes.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes mauritsvanrees, jensens, vangheem, 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/plone/Products.CMFPlone/graphs/contributors

- Upstream project: https://github.com/plone/Products.CMFPlone

### Sources

- plone-in-a-box: https://github.com/collective/plone-in-a-box

- GPL-2.0 LICENSE.md: https://github.com/plone/Products.CMFPlone/blob/master/LICENSE

- Releases v6.2.3: https://github.com/plone/Products.CMFPlone/releases

### Licensing sources

- https://github.com/plone/Products.CMFPlone/blob/master/LICENSE

### Infrastructure sources

- https://github.com/collective/plone-in-a-box


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 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: Documented. The community pas.plugins.oidc add-on documents OpenID Connect authentication for Plone. This is an add-on integration rather than a universal core entitlement; validate its Plone/backend/front-end compatibility and provider mapping for the selected deployment. Scope: Maintainer documentation for a Plone PAS OIDC add-on. Source: https://github.com/collective/pas.plugins.oidc (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. Cookieplone is the upstream-recommended project generator and creates the selected Plone backend/frontend project. It supplies an application project/deployment workflow, not an automatically hardened cloud-account infrastructure stack. Scope: Plone 6 Cookieplone project generation; Classic and Volto variants have different requirements. Source: https://6.docs.plone.org/install/create-project-cookieplone.html (reviewed 2026-11-20). Deployment artifact: https://github.com/plone/cookieplone. Artifact reference: Moving generator repository; select compatible pinned template/dependency versions.

- Minimum footprint / sizing: Documented. The Plone 6 guide recommends 2 GB or more RAM per site and 40 GB or more disk. Volto frontend installation needs at least 2 GB RAM; lower backend process minima and swap figures are not whole-stack sizing. Addons, caches, builds and HA require additional resources. Scope: Rough upstream Classic/Volto requirements, not a 100-user/1-TB HA benchmark. Source: https://6.docs.plone.org/install/create-project-cookieplone.html (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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







## Umbraco CMS Self-Hosted

MIT-licensed .NET CMS with documented customer-managed Azure and AWS hosting options.

- Listing: https://launchinyourcloud.com/directory/umbraco-cms-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure, aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT-licensed Umbraco CMS core; Umbraco Cloud, Deploy, Forms and other products have separate commercial terms.
- Licensing model: open-source
- Installation: Umbraco.Cms NuGet package and customer-managed hosting, including Azure Web Apps and AWS; provision a supported database and media storage; optional cloudimg Azure VM package has its own version, database and patch constraints
- Architecture: ASP.NET Core CMS application with a supported customer-controlled database and persistent media; Azure App Service is one documented hosting configuration.
- Operations: Customer manages application releases, database, media, settings and secrets, backups, scaling, domains, TLS and packages.
- Product website: https://umbraco.com/products/umbraco-cms/
- 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 self-hosted Umbraco CMS, not Umbraco Cloud or Heartcore. CMS 18 is STS and 17 is LTS; 13 reaches EOL December 14, 2026. Match the major version, .NET/database requirements, shared media and load-balanced deployment; commercial add-ons have separate terms. A separate cloudimg Azure VM guide packages CMS 17.5.3 with embedded SQLite. It is a single-instance option, not HA or Umbraco Cloud. Verify the actual installed build against GHSA-348f-9mg8-rhv4; affected builds require a branch-appropriate upgrade and Members-index rebuild. GHSA-5pr6-xx84-wp49 separately affects Umbraco CMS 13.0.0–13.16.4 when the Delivery API is enabled and protected or excluded content is referenced through content pickers. Upgrade to 13.16.5 or later. Versions 12 and 14–15 are end of life and require migration; CMS 17 and 18 are not affected by this specific issue.

Umbraco CMS core is MIT-licensed. Umbraco Cloud and optional commercial products are separate.

Umbraco runs as a persistent application backed by a relational database and media storage; Azure App Service abstracts servers but does not remove stateful application dependencies.


### Category fit

- content-management: Provides open-source web content authoring, publishing, templating and extensible CMS capabilities.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.umbraco.com/umbraco-cms/fundamentals/setup/server-setup/azure-web-apps (checked 2026-11-18). Source: https://www.cloudimg.co.uk/guides/umbraco-on-ubuntu-24-04-azure/ (checked 2026-11-18). 

- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.umbraco.com/umbraco-cloud/explore-umbraco-cloud/what-is-umbraco-cloud/hosting-with-umbraco-cloud-cloud-vs.-self-hosted (checked 2026-11-18). 


### Cloud deployment evidence

- Umbraco CMS on Azure Web Apps (azure): https://docs.umbraco.com/umbraco-cms/fundamentals/setup/server-setup/azure-web-apps
  Umbraco documents configuration and operation of the self-hosted CMS on Azure App Service in the customer's environment.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- Umbraco customer-managed AWS hosting (aws): https://docs.umbraco.com/umbraco-cloud/explore-umbraco-cloud/what-is-umbraco-cloud/hosting-with-umbraco-cloud-cloud-vs.-self-hosted
  Umbraco’s hosting comparison explicitly names AWS and Azure as self-hosted infrastructure managed by the customer. The CMS, database and commercial add-on lifecycle remain customer responsibilities.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- cloudimg Umbraco CMS VM in a customer Azure subscription (azure): https://www.cloudimg.co.uk/guides/umbraco-on-ubuntu-24-04-azure/
  The seller documents a complete MIT CMS deployment into the selected customer subscription/VNet, using image URN cloudimg1647283583153:umbraco-ubuntu-24-04:default:latest, nginx, .NET 10, embedded SQLite and a data disk. Its 17.5.3 guide version needs the documented security/upgrade review; it is not a clustered/HA database or an HQ-supported package.
  Source type: third-party-package; reviewed: 2026-11-18; vendor support: not-assessed. Versions: Guide application 17.5.3; verify actual image and patched build.


### Community and maintenance

The public CMS repository publishes fixes across current/LTS branches and Umbraco maintains a named implementation case-study catalog. Cloud/Heartcore case studies are not used as customer-cloud proof; the separate hosting comparison establishes the listed deployment boundary.

Reviewed 2026-11-18.

- Official maintenance and adoption evidence: https://github.com/umbraco/Umbraco-CMS/releases/tag/release-18.3.2

- Official maintenance and adoption evidence: https://umbraco.com/case-studies-testimonials/

- Official maintenance and adoption evidence: https://docs.umbraco.com/umbraco-cloud/explore-umbraco-cloud/what-is-umbraco-cloud/hosting-with-umbraco-cloud-cloud-vs.-self-hosted

### Sources

- Hosting an Umbraco infrastructure: https://docs.umbraco.com/getting-started/hosting-an-umbraco-infrastructure

- Configure Umbraco CMS for Azure Web Apps: https://docs.umbraco.com/umbraco-cms/fundamentals/setup/server-setup/azure-web-apps

- Umbraco Cloud versus self-hosted: https://docs.umbraco.com/umbraco-cloud/explore-umbraco-cloud/what-is-umbraco-cloud/hosting-with-umbraco-cloud-cloud-vs.-self-hosted

- Umbraco CMS source-code license: https://umbraco.com/products/umbraco-cms/source-code-license/

- cloudimg self-hosted Umbraco Azure VM guide: https://www.cloudimg.co.uk/guides/umbraco-on-ubuntu-24-04-azure/

- Provider exact Azure offer metadata: https://catalogapi.azure.com/offers/cloudimg1647283583153.umbraco-ubuntu-24-04?api-version=2018-08-01-beta&market=US&language=en

- Umbraco November 17, 2026 security advisory: https://umbraco.com/blog/security-advisory-security-patches-for-umbraco-cms-umbraco-workflow-umbraco-commerce-umbraco-engage-and-umbraco-mcp-server-sdk-now-available/

- GHSA-5pr6-xx84-wp49: https://github.com/umbraco/Umbraco-CMS/security/advisories/GHSA-5pr6-xx84-wp49

### Licensing sources

- https://umbraco.com/products/umbraco-cms/source-code-license/

### Infrastructure sources

- https://docs.umbraco.com/umbraco-cms/13.latest/fundamentals/setup/server-setup/azure-web-apps

- https://www.cloudimg.co.uk/guides/umbraco-on-ubuntu-24-04-azure/


### Buyer diligence


Research coverage: 12/12 fields (100%); 9 documented, 3 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. cloudimg publishes Azure VM offer cloudimg1647283583153.umbraco-ubuntu-24-04, default plan. Its guide/catalog package MIT-licensed CMS 17.5.3 on .NET 10, nginx and embedded SQLite with per-VM administrator credentials. It excludes Umbraco Cloud and paid add-ons. The guide’s version is within GHSA-348f’s affected 17.x range: verify the installed build, upgrade to the maintained patched branch and rebuild the Members index where affected. The seller’s 17.8.0 AWS guide is closed to new subscriptions. Scope: Third-party self-hosted Azure VM, default plan; not Umbraco Cloud, an HQ support commitment or an HA/clustered SQLite design. Source: https://www.cloudimg.co.uk/guides/umbraco-on-ubuntu-24-04-azure/ (reviewed 2026-11-18). Supporting source: Current seller product and offer link — https://www.cloudimg.co.uk/products/umbraco-on-ubuntu-24-04-lts-azure/. Supporting source: Provider public offer/version/availability metadata — https://catalogapi.azure.com/offers/cloudimg1647283583153.umbraco-ubuntu-24-04?api-version=2018-08-01-beta&market=US&language=en. Supporting source: Official version-specific fix and index rebuild — https://github.com/umbraco/Umbraco-CMS/security/advisories/GHSA-348f-9mg8-rhv4. Supporting source: Newer-looking AWS guide is retired for new subscribers — https://www.cloudimg.co.uk/guides/umbraco-17-8-0-on-ubuntu-24-04-aws/. Offer cloudimg1647283583153.umbraco-ubuntu-24-04: cloudimg; Azure virtual-machine image; default plan; package Guide application 17.5.3; moving latest image; https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.umbraco-ubuntu-24-04.

- Cloud commitment eligibility: Explicitly unsupported. Microsoft’s public catalog marks the reviewed cloudimg Umbraco CMS Azure VM offer as ineligible for MACC. Its software packaging/support charge therefore does not supply MACC-eligible software spend through this public offer. Recheck the current offer at procurement. Azure infrastructure, other providers, commercial add-ons and separately negotiated offers need their own eligibility and agreement review. Scope: MACC eligibility of public cloudimg offer cloudimg1647283583153.umbraco-ubuntu-24-04, default plan, US catalog checked; other procurement paths are outside this finding. Source: https://catalogapi.azure.com/offers/cloudimg1647283583153.umbraco-ubuntu-24-04?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-18). Supporting source: Microsoft definition of the catalog eligibility field — https://raw.githubusercontent.com/Azure/azure-rest-api-specs/00f083f4efcbfe54730b7af700a50327232c199a/specification/marketplacecatalog/data-plane/Marketplace/stable/2021-10-01/marketplacecatalog.json. Supporting source: Microsoft MACC purchasing and infrastructure boundaries — https://learn.microsoft.com/en-us/marketplace/azure-consumption-commitment-benefit.

- Single sign-on: Documented. The CMS supports external OAuth/OIDC login providers for backoffice users and frontend members through ASP.NET Core Identity. Configure each provider and optional auto-linking explicitly. A community Azure SSO package is not an Umbraco HQ support commitment. Scope: Umbraco CMS Self-Hosted: selected customer-operated edition. Source: https://docs.umbraco.com/umbraco-cms/reference/security/external-login-providers (reviewed 2026-11-18).

- SCIM provisioning: Sources checked — unresolved. miniOrange documents an outbound Umbraco SCIM Client: existing Backoffice Users/Members provision into a destination SCIM server. Its FAQ explicitly says it does not create Umbraco users from an IdP. The setup guide names Trial package 18.0.1, but its public NuGet version URL returned 404. Confirm the current production package/feed, CMS compatibility and licence; an inbound Umbraco provisioning requirement remains unanswered. Scope: Third-party outbound connector documentation; current deliverable and inbound provisioning are not confirmed. Source: https://plugins.miniorange.com/umbraco-scim-user-provisioning (reviewed 2026-11-18). Supporting source: Named trial package and outbound setup — https://plugins.miniorange.com/umbraco-scim-user-provisioning-setup-guide.

- Compliance attestations: Documented. Sensiba certificate 202601-189 identifies Umbraco A/S’s ISO/IEC 27001:2022 ISMS for CMS platform development/provisioning processes. It was issued January 21, 2026 and expires January 21, 2029. The certificate expressly excludes certifying products, processes or services; it does not certify a customer’s self-hosted website, plugins, database or operations. Scope: Organisational ISO 27001 management-system assurance covering CMS development/provisioning; not product or customer-deployment certification. Source: https://umbraco.com/media/vj0c1qi5/umbraco-iso-27001-certificate-jan-2026-93.pdf (reviewed 2026-11-18). Supporting source: Official certificate announcement and organisation scope — https://umbraco.com/blog/iso-27001/. Supporting source: Compliance boundaries and SOC position — https://umbraco.com/trust-center/compliance-faq/.

- Security controls: Documented. Backoffice and member authentication have separate external-login configuration and optional account auto-linking. Review provider ownership, callback URLs and linking rules. Supported major versions have different security-maintenance windows; external authentication does not remove patch obligations. A seller’s hardened OS/first-boot credentials do not establish that its older CMS package contains the member-index fix; verify the app build and required index rebuild. Current review: GHSA-5pr6-xx84-wp49 affects CMS 13.0.0–13.16.4 when the Delivery API is enabled and protected or excluded content is referenced through content pickers; upgrade to 13.16.5 or later. CMS 12 and 14–15 are end of life, while 17 and 18 are not affected by this specific issue. GHSA-348f-9mg8-rhv4 separately requires affected 17/18 sites to rebuild the Members index after upgrading. Scope: Umbraco CMS branch-specific November 17 fixes; commercial add-ons have separate advisories. Source: https://umbraco.com/blog/security-advisory-security-patches-for-umbraco-cms-umbraco-workflow-umbraco-commerce-umbraco-engage-and-umbraco-mcp-server-sdk-now-available/ (reviewed 2026-11-19). Supporting source: Prior security-controls source — https://docs.umbraco.com/umbraco-cms/reference/security/external-login-providers. Supporting source: CMS support lifecycle — https://umbraco.com/products/knowledge-center/long-term-support-and-end-of-life/. Supporting source: Older packaged application and local safeguards — https://www.cloudimg.co.uk/guides/umbraco-on-ubuntu-24-04-azure/. Supporting source: Official patch and index remediation — https://github.com/umbraco/Umbraco-CMS/security/advisories/GHSA-348f-9mg8-rhv4. Supporting source: CMS 13 Delivery API advisory — https://github.com/umbraco/Umbraco-CMS/security/advisories/GHSA-5pr6-xx84-wp49.

- Air-gapped operation: Sources checked — unresolved. The official telemetry material documents Minimal, Basic and Detailed reporting levels, while health checks can be disabled/configured individually. Those controls are not a complete disconnected CMS lifecycle. Confirm NuGet/.NET artifact transfer, news/telemetry and update requests, local identity/mail/media, and any add-on activation; the self-contained Azure SQLite image alone does not establish air-gapped operation. Scope: Umbraco CMS Self-Hosted: selected customer-operated edition. Source: https://docs.umbraco.com/sustainability-best-practices/telemetry/telemetry (reviewed 2026-11-18). Supporting source: Current CMS health-check controls — https://docs.umbraco.com/umbraco-cms/develop-with-umbraco/configuration/healthchecks. Supporting source: VM component boundary, not an offline guarantee — https://www.cloudimg.co.uk/guides/umbraco-on-ubuntu-24-04-azure/.

- Deployment artifact / IaC: Documented. The CMS is distributed as the Umbraco.Cms NuGet package; 18.3.2 is a versioned package. Azure Web Apps has a separate vendor configuration guide. Database provisioning, deployment automation and load-balanced content/media handling remain part of the customer design. cloudimg separately documents the moving Azure image URN cloudimg1647283583153:umbraco-ubuntu-24-04:default:latest; resolve its version before deployment. Scope: Umbraco CMS Self-Hosted: selected customer-operated edition. Source: https://docs.umbraco.com/umbraco-cms/fundamentals/setup/requirements (reviewed 2026-11-18). Deployment artifact: https://www.nuget.org/packages/Umbraco.Cms/18.3.2. Artifact reference: Umbraco.Cms 18.3.2. Supporting source: Current Azure Web Apps configuration — https://docs.umbraco.com/umbraco-cms/fundamentals/setup/server-setup/azure-web-apps. Supporting source: Separate VM artifact and deployment instructions — https://www.cloudimg.co.uk/guides/umbraco-on-ubuntu-24-04-azure/.

- Minimum footprint / sizing: Documented. The current CMS requirements name .NET 10, supported hosting runtimes, SQLite or SQL Server 2016+ with the required case-insensitive collation, and WebSocket/SignalR support. They do not provide a universal CPU/RAM minimum or a 100-user HA bill of materials. Check requirements again for older LTS majors. The cloudimg SQLite appliance suggests Standard_B2s (2 vCPU/4 GiB); this is a single-instance package baseline, not clustered HA sizing. Scope: Umbraco CMS Self-Hosted: selected customer-operated edition. Source: https://docs.umbraco.com/umbraco-cms/fundamentals/setup/requirements (reviewed 2026-11-18). Supporting source: Single-instance Azure appliance requirements — https://www.cloudimg.co.uk/guides/umbraco-on-ubuntu-24-04-azure/.

- License pricing: Documented. Umbraco CMS core is MIT licensed. Commercial Forms, Deploy, support and Umbraco Cloud hosting have separate terms; none is automatically included with a self-hosted core installation. The cloudimg Azure default plan charges USD 0.04/vCPU-hour for packaging/support (USD 0.08/hour at two vCPUs), plus Azure infrastructure; this is not an Umbraco HQ subscription. Scope: Umbraco CMS Self-Hosted: selected customer-operated edition. Source: https://umbraco.com/products/umbraco-cms/source-code-license/ (reviewed 2026-11-18). Supporting source: Exact Azure plan and per-core meters — https://catalogapi.azure.com/offers/cloudimg1647283583153.umbraco-ubuntu-24-04?api-version=2018-08-01-beta&market=US&language=en.

- Operating cost estimate: Sources checked — unresolved. Define editor versus public traffic, content/media split, database and Windows/Linux choice, shared media, cache, HA topology, backups and commercial add-ons. One hundred editors and 1 TB do not size the CMS’s public request workload or SQL licensing. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://docs.umbraco.com/umbraco-cms/fundamentals/setup/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. The CMS release release-18.3.2 was published November 17, 2026. GHSA-348f-9mg8-rhv4 requires affected sites to upgrade and rebuild the Members index; patch installation alone leaves existing indexed values. Version 18 is STS, 17 is LTS, and 13 reaches EOL December 14, 2026; 19.0.0-rc1 is a prerelease. The reviewed cloudimg Azure package instead documents 17.5.3, which falls within the advisory’s affected 17.x range; confirm the installed build and upgrade/rebuild where affected. CMS 13.16.5 fixes GHSA-5pr6-xx84-wp49 on the maintained 13.x line; this does not replace the current release-18.3.2 primary snapshot. Scope: Umbraco CMS Self-Hosted: selected customer-operated edition. Source: https://github.com/umbraco/Umbraco-CMS/releases/tag/release-18.3.2 (reviewed 2026-11-19). Supporting source: Official lifecycle dates — https://umbraco.com/products/knowledge-center/long-term-support-and-end-of-life/. Supporting source: Sensitive member data advisory and index rebuild — https://github.com/umbraco/Umbraco-CMS/security/advisories/GHSA-348f-9mg8-rhv4. Supporting source: Provider packaged-version boundary — https://catalogapi.azure.com/offers/cloudimg1647283583153.umbraco-ubuntu-24-04?api-version=2018-08-01-beta&market=US&language=en. Supporting source: CMS 13 Delivery API advisory — https://github.com/umbraco/Umbraco-CMS/security/advisories/GHSA-5pr6-xx84-wp49.




### Security and lifecycle reviews

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

- Umbraco sensitive member data requires upgrade and index rebuild (security-advisory): GHSA-348f-9mg8-rhv4 describes sensitive member property values exposed through the Examine members index to some authenticated backoffice users or custom index queries. Scope: The vendor identifies introduction in 17.4.0 and fixes in 17.8.2/18.3.2. The default members index in 17.0–17.3 is excluded. Read the advisory’s branch-specific range rather than applying this to every CMS major. cloudimg’s current Azure guide/plan documents CMS 17.5.3 within the affected 17.x range; resolve the actual image and installed build, including any documented backport, before assessing an instance. Conditions: Member types must have sensitive properties. The described backoffice path requires Settings and Members access without Sensitive data group membership; custom code returning all indexed fields can also expose values. Action: Install the patched version for the maintained branch and rebuild the Members index. Until upgrade, restrict the named group access and review custom code that returns indexed fields. Source: https://github.com/umbraco/Umbraco-CMS/security/advisories/GHSA-348f-9mg8-rhv4; reviewed 2026-11-18. Supporting source: Seller Azure image and application version — https://www.cloudimg.co.uk/guides/umbraco-on-ubuntu-24-04-azure/. Supporting source: Provider current offer/plan metadata — https://catalogapi.azure.com/offers/cloudimg1647283583153.umbraco-ubuntu-24-04?api-version=2018-08-01-beta&market=US&language=en.

- Umbraco 13 LTS reaches end of life in December 2026 (lifecycle): Umbraco 13 is in security-only maintenance and reaches end of life December 14, 2026. Other CMS majors have different windows. Scope: Umbraco CMS 13 deployments, including older Azure recipes; this is not an end-of-life announcement for the current CMS product. Conditions: The installed major version determines support. Version 17 is LTS and 18 is STS; neither inherits version 13’s date. Action: Inventory the installed major and plugins, and plan a tested migration to a maintained major before the applicable deadline. Source: https://umbraco.com/products/knowledge-center/long-term-support-and-end-of-life/; reviewed 2026-11-18.

- Umbraco CMS 13 protected-content Delivery API fix (security-advisory): GHSA-5pr6-xx84-wp49 fixes protected or excluded content disclosure through the Delivery API and content pickers. Scope: Umbraco CMS 13.0.0–13.16.4; fixed in 13.16.5. CMS 12 and 14–15 are end of life; CMS 17 and 18 are not affected by this specific issue. Conditions: The Delivery API must be enabled and protected or excluded content referenced through a Content Picker or Multi-Node Tree Picker. Action: Upgrade maintained CMS 13 to 13.16.5 or later; migrate end-of-life branches. Source: https://github.com/umbraco/Umbraco-CMS/security/advisories/GHSA-5pr6-xx84-wp49; reviewed 2026-11-19. Supporting source: Vendor security summary — https://umbraco.com/blog/security-advisory-security-patches-for-umbraco-cms-umbraco-workflow-umbraco-commerce-umbraco-engage-and-umbraco-mcp-server-sdk-now-available/.




## Webiny — Customer AWS Deployment

Headless CMS, website builder and file management deployed into your AWS account.

- Listing: https://launchinyourcloud.com/directory/webiny/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: serverless, hybrid
- License: Community/open-source and commercial plans; edition and governance entitlements vary
- Licensing model: open-source
- Installation: Official project setup and Webiny CLI deployment to customer AWS; Pulumi-based infrastructure.
- Architecture: AWS Lambda application APIs with DynamoDB, S3, Cognito and optional OpenSearch
- Operations: Customer deploys and upgrades the application; AWS operates the underlying managed services.
- Product website: https://www.webiny.com/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This listing covers the supported production AWS target. Standalone is currently alpha with no supported production deployment path, so no additional cloud badges are inferred. The DynamoDB setup has a serverless core; optional provisioned OpenSearch introduces a hybrid configuration under this directory’s runtime definitions. Webiny v6.5.2 includes tenant-context, permission, input, dependency, and admin MFA-reset hardening. Review tenant isolation and administrator recovery paths before upgrading; v6.4.12 is the parallel maintenance-branch release.

Community is MIT-licensed. The repository separates enterprise directories and package licenses, and Business/Enterprise feature sets use commercial licensing.

AWS Lambda and DynamoDB provide the serverless core. A configuration with provisioned OpenSearch is hybrid under this directory’s definitions. The alpha Standalone Node runtime is excluded from the production listing.


Cloud evidence scope: AWS production deployment is explicitly documented.

### Category fit

- content-management: Headless CMS and website-building platform with editorial applications and APIs deployed to customer AWS. Advanced governance and tenancy capabilities depend on plan.

- digital-asset-management: The File Manager provides content-asset storage and management. Evaluate rights, approval and distribution requirements before comparing with a dedicated enterprise DAM.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.webiny.com/docs/get-started/quickstart/aws (checked 2026-11-12). 


### Cloud deployment evidence

- Webiny customer AWS installation (aws): https://www.webiny.com/docs/get-started/quickstart/aws
  The project quick start deploys Webiny into the customer AWS account with the documented credentials and tooling. Deployment-target documentation distinguishes development from production runtime; do not infer other providers from a locally runnable service.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Production deployment target and runtime differences: https://www.webiny.com/docs/get-started/deployment-targets

- AWS installation guide: https://www.webiny.com/docs/get-started/quickstart/aws

- Platform applications: https://www.webiny.com/docs/get-started/welcome

- Edition capabilities and self-hosted plans: https://www.webiny.com/pricing

- Licensing and edition terms: https://raw.githubusercontent.com/webiny/webiny-js/next/LICENSE

- Licensing and edition terms: https://github.com/webiny/webiny-js

- Licensing and edition terms: https://www.webiny.com/docs/get-started/upgrade

- Webiny v6.5.2 release: https://github.com/webiny/webiny-js/releases/tag/v6.5.2

### Licensing sources

- https://raw.githubusercontent.com/webiny/webiny-js/next/LICENSE

- https://github.com/webiny/webiny-js

- https://www.webiny.com/docs/get-started/upgrade

### Infrastructure sources

- https://www.webiny.com/docs/get-started/deployment-targets


### Buyer diligence


Research coverage: 6/12 fields (50%); 5 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: Edition-dependent. The self-hosted plan comparison includes SSO in Enterprise and explicitly excludes it from Community and Business. Confirm the identity provider and enterprise entitlement before evaluation. Scope: Current self-hosted plan comparison; not the local Standalone alpha. Source: https://www.webiny.com/pricing (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: Webiny 6.5.2 includes tenant-context, permission, input-validation, dependency, and administrator MFA-reset fixes. Upgrade to 6.5.2 or the appropriate later maintained release and validate tenant isolation and MFA recovery. Scope: Upstream 6.5.2 release notes; the vendor does not publish a consolidated affected-version range in this record.. Source: https://github.com/webiny/webiny-js/releases/tag/v6.5.2 (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The deployment-target guide separates the AWS deployment from Standalone. AWS uses Cognito, DynamoDB and S3; Standalone uses a different local identity/storage configuration and development defaults. Do not substitute the standalone recipe for an AWS architecture. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://www.webiny.com/docs/get-started/deployment-targets (reviewed 2026-11-14).

- Minimum footprint / sizing: Sources checked — unresolved. The production AWS target uses Lambda, DynamoDB, S3 and optional OpenSearch; the local SQL/Node Standalone target is alpha. The reviewed comparison does not establish a production resource floor or capacity for a 100-user, 1-TB HA workload. Scope: Production AWS architecture; no equivalent VM sizing inferred from the local target. Source: https://www.webiny.com/docs/get-started/deployment-targets (reviewed 2026-11-20).

- License pricing: Documented. Community is free; Business starts at $79/month, with $299 and 599 monthly tiers shown. Enterprise has custom annual pricing. AWS resources are separate from the software plan. Scope: Published self-hosted software plans; check tier allocations and commercial quote. Source: https://www.webiny.com/pricing (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Webiny v6.5.2 was published November 17, 2026, with tenant-context, permission, input, dependency, and admin MFA-reset hardening. A parallel 6.4.12 maintenance release exists for that branch. Scope: Upstream Webiny 6.5 release. Source: https://github.com/webiny/webiny-js/releases/tag/v6.5.2 (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- Webiny 6.5.2 security hardening (security-advisory): Webiny 6.5.2 includes tenant-context, permission, input-validation, dependency, and administrator MFA-reset fixes. Scope: Upstream 6.5.2 release notes; the vendor does not publish a consolidated affected-version range in this record. Conditions: Applicability depends on enabled tenancy, permissions, and administration paths. Action: Upgrade to 6.5.2 or the appropriate later maintained release and validate tenant isolation and MFA recovery. Source: https://github.com/webiny/webiny-js/releases/tag/v6.5.2; 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.



