Content management & CMS on Google Cloud
Headless content platforms, website publishing and editorial APIs.
7 documented options on Google Cloud. Provider coverage reflects reviewed evidence, not an exhaustive compatibility claim.
Read this page as JSON or Markdown.
| Listing | Documented clouds | Deployment and infrastructure | Licensing | Installation | Operations and limitations |
|---|---|---|---|---|---|
| Confluence Data Center | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial Atlassian Data Center term license for eligible existing customers; new-customer sales ended March 30, 2026. Affected subscriptions expire March 28, 2029. | Official Atlassian Helm chart on Amazon EKS, Azure AKS or Google GKE, or package-based single-node and clustered installation | Customer manages Kubernetes or hosts, the database, shared and local storage, Synchrony, load balancing, networking, TLS, identity, Marketplace apps, backups, monitoring and upgrades.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-16 |
| dotCMS Cloud Anywhere | AWS, Azure, Google Cloud | Vendor-operated BYOC Servers / containers | Commercial Only Commercial dotCMS Cloud Anywhere service terms; the public core-code licence does not grant service entitlements. | Cloud Anywhere onboarding and vendor management through customer-cloud access roles | Vendor operates the Cloud Anywhere application through its management plane and scoped customer-cloud access; agree support access, logs, egress and exit procedures.Scope and evidenceThe 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.
Cloud evidence reviewed 2026-11-19 |
| HCL Digital Experience Cloud Native 9.5 | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial HCL Digital Experience Cloud Native subscription measured by user sessions and associated production processing capacity. | Official HCL Digital Experience Helm chart on customer Amazon EKS, Microsoft AKS or Google GKE | Customer manages Kubernetes, storage, databases and integrations, ingress, certificates, capacity, backups, upgrades and version compatibility.Scope and evidenceBeginning 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.
Cloud evidence reviewed 2026-11-17 |
| Liferay DXP Cloud Native Experience | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial Liferay DXP subscription; Cloud Native Experience provider-ready capabilities require Enterprise Subscription entitlement. | Provider-ready Terraform bootstrap with Kubernetes, Helm and Argo CD GitOps deployment | Customer manages the cloud account, GitOps repository, Kubernetes platform, secrets, domains, certificates, capacity, backups, upgrades and application customizations.Scope and evidenceCloud 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.
Cloud evidence reviewed 2026-11-17 |
| Squidex | AWS, Azure, Google Cloud, Render, Heroku, Vultr | Customer-operated Servers / containers | Open Source / Open Core MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms. | Application platform deployment | 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.Scope and evidenceThe 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.
Cloud evidence reviewed 2026-11-19 |
| Strapi Self-Hosted | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Open Source / Open Core MIT core; commercial Growth/Enterprise features and terms differ | Node.js production deployment with a supported SQL database; container/Kubernetes options | Customer operates application servers, database, media storage, backups and upgrades.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-12 |
| WordPress Self-Hosted | AWS, Azure, Google Cloud, DigitalOcean, Oracle Cloud, Linode, Vultr | Customer-operated Servers / containers | Open Source / Open Core GPLv2 or later; themes, plugins and provider packaging may have separate terms. | Provider application images/blueprints, Azure App Service quickstart, OCI Resource Manager template, or Akamai StackScript; package and topology vary by provider | Customer manages WordPress core, themes and plugins, application security, identities, content, database, media, backups, scaling and upgrades.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-18 |
Deployment evidence and category fit
Confluence Data Center
Manages structured spaces, pages, attachments, templates and governed enterprise knowledge content.
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.
- Confluence Data Center on EKS, AKS or GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-16 · Version: 11.0; use the current compatibility matrix for other releases. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Cloud evidence reviewed 2026-11-16. Full listing and qualifications
dotCMS Cloud Anywhere
Vendor-operated content platform deployed into a customer cloud account.
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.
- Cloud Anywhere Quickstart ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Cloud evidence reviewed 2026-11-19. Full listing and qualifications
HCL Digital Experience Cloud Native 9.5
A web content management system with authoring, presentation templates, headless APIs and publishing workflows.
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.
- HCL Digital Experience on Google GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
HCL's current support matrix explicitly lists Google GKE as a tested and supported full-container platform.
Cloud evidence reviewed 2026-11-17. Full listing and qualifications
Liferay DXP Cloud Native Experience
Liferay DXP provides web and headless content authoring, publishing, sites and digital-experience delivery on customer infrastructure.
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.
- Liferay DXP Cloud Native Experience GCP Ready ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
Liferay documents Terraform, Argo CD and Kubernetes provisioning in the customer's Google Cloud environment, including GKE and managed data services.
Cloud evidence reviewed 2026-11-17. Full listing and qualifications
Squidex
Self-hosted headless CMS with structured content, APIs and assets.
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.
- GCP Guide ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Cloud evidence reviewed 2026-11-19. Full listing and qualifications
Strapi Self-Hosted
Headless content management with content modeling, editorial administration and APIs; paid governance features depend on plan.
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.
- Strapi self-hosting compatibility ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Cloud evidence reviewed 2026-11-12. Full listing and qualifications
WordPress Self-Hosted
Publishes websites, blogs and extensible structured content with themes, plugins and a browser-based editorial interface.
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 on Google Cloud ↗
Provider guide · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
Google documents customer deployments of WordPress on Google Cloud, including a Compute Engine path. Provider packaging and support scope must be reviewed.
Cloud evidence reviewed 2026-11-18. Full listing and qualifications
Deployment and procurement checks
- Private offers
- Cloud Marketplace vendors can negotiate a private offer for a specified Cloud Billing account. Check duration, renewal terms and commitment treatment in the actual agreement. Provider source ↗ · Reviewed 2026-11-14
- Private connectivity
- Private Service Connect connects VPC consumers to supported managed or producer services. Confirm the actual product endpoint and network/DNS architecture. Provider source ↗ · Reviewed 2026-11-14
- External workload access
- Workload Identity Federation can grant external workloads scoped Google Cloud access without long-lived service-account keys. Validate the trust configuration and exact roles. Provider source ↗ · Reviewed 2026-11-14
- Regulated environments
- Assured Workloads applies control packages for residency and access boundaries. Confirm supported services, regions and the product deployment; it is not automatic product certification. Provider source ↗ · Reviewed 2026-11-14
For every provider, confirm marketplace/private-offer terms, commitment eligibility, regional service availability, private connectivity and any vendor access against your selected deployment. Provider capabilities do not automatically establish application support.
Plan this deployment
Account boundary: Google Cloud project. Access: IAM policies and service accounts. Network: VPC network.
Provider documentation ↗ · Guidance reviewed 2026-11-10. Confirm the application edition, region, support access, backup locations and operating responsibilities before choosing.
Compare this category across clouds · Search these listings · Compare 2–4 listings