Content management & CMS on AWS

Headless content platforms, website publishing and editorial APIs.

14 documented options on Amazon Web Services. Provider coverage reflects reviewed evidence, not an exhaustive compatibility claim.

ListingDocumented cloudsDeployment and infrastructureLicensingInstallationOperations and limitations
Confluence Data CenterAWS, Azure, Google CloudCustomer-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 installationCustomer manages Kubernetes or hosts, the database, shared and local storage, Synchrony, load balancing, networking, TLS, identity, Marketplace apps, backups, monitoring and upgrades.
Scope and evidence

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

    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.

Cloud evidence reviewed 2026-11-16

CrafterCMSAWSCustomer-operated
Servers / containers
Open Source / Open Core

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

Kubernetes manifestsCustomer 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 evidence

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

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

    Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-19

dotCMS Cloud AnywhereAWS, Azure, Google CloudVendor-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 rolesVendor operates the Cloud Anywhere application through its management plane and scoped customer-cloud access; agree support access, logs, egress and exit procedures.
Scope and evidence

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

    Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-19

DrupalAWSCustomer-operated
Servers / containers
Open Source / Open Core

GPL version 2 or later for Drupal and derivative contributed files hosted by the project.

Install on your host with Composer using drupal/recommended-project and complete the site setup.Own hosting, access control, backups, supported core/module updates and production configuration.
Scope and evidence

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 server on Amazon Lightsail — 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.

    Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-12

GravLinode, AWS, DigitalOcean, Vultr, Hostinger, LumaDockCustomer-operated
Servers / containers
Open Source / Open Core

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

Cloudron packageCustomer 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 evidence

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.

  • Cloudron Store — 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.

    Package platform documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-19

HCL Digital Experience Cloud Native 9.5AWS, Azure, Google CloudCustomer-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 GKECustomer manages Kubernetes, storage, databases and integrations, ingress, certificates, capacity, backups, upgrades and version compatibility.
Scope and evidence

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 Amazon EKS — HCL documents deploying the entitled DX Helm chart to Amazon-managed Kubernetes in the customer's AWS environment.

    Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.

  • HCL Digital Experience on Microsoft Azure AKS — HCL's current support matrix explicitly lists Microsoft Azure AKS as a tested and supported full-container platform.

    Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.

  • HCL Digital Experience on Google GKE — HCL's current support matrix explicitly lists Google GKE as a tested and supported full-container platform.

    Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-17

Liferay DXP Cloud Native ExperienceAWS, Azure, Google CloudCustomer-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 deploymentCustomer manages the cloud account, GitOps repository, Kubernetes platform, secrets, domains, certificates, capacity, backups, upgrades and application customizations.
Scope and evidence

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

    Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Liferay DXP Cloud Native Experience Azure Ready — Liferay documents Terraform, Argo CD and Kubernetes provisioning in the customer's Azure subscription, including AKS and managed data services.

    Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Liferay DXP Cloud Native Experience GCP Ready — Liferay documents Terraform, Argo CD and Kubernetes provisioning in the customer's Google Cloud environment, including GKE and managed data services.

    Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-17

Pimcore PlatformAWSCustomer-operated
Servers / containers
Source Available

Pimcore Open Core License (POCL); free eligibility and commercial edition requirements apply.

Use the documented Docker installation packages and configure your own hosting environment.Operate hosting, database, files, caching, backups, updates and integrations; budget for implementation.
Scope and evidence

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.

  • Pimcore deployment in an existing customer AWS account through Metaways — 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.

    Partner evidence · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Pimcore identification of Metaways as a technology partner — 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.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-12

PloneAWS, Linode, DigitalOcean, HetznerCustomer-operated
Servers / containers
Open Source / Open Core

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

CloudFormation; Docker / Compose; Application platform deploymentCustomer 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 evidence

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

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

    Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-19

SquidexAWS, Azure, Google Cloud, Render, Heroku, VultrCustomer-operated
Servers / containers
Open Source / Open Core

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

Application platform deploymentCustomer 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 evidence

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.

  • AWS EC2 Guide — 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.

    Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Azure Guide — 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.

    Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

  • GCP Guide — 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.

    Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Render Guide — 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.

    Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Install on Heroku | Squidex — 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.

    Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Install on Vultr | Squidex — 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.

    Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-19

Strapi Self-HostedAWS, Azure, Google CloudCustomer-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 optionsCustomer operates application servers, database, media storage, backups and upgrades.
Scope and evidence

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

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-12

Umbraco CMS Self-HostedAzure, AWSCustomer-operated
Servers / containers
Open Source / Open Core

MIT-licensed Umbraco CMS core; Umbraco Cloud, Deploy, Forms and other products have separate commercial terms.

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 constraintsCustomer manages application releases, database, media, settings and secrets, backups, scaling, domains, TLS and packages.
Scope and evidence

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 on Azure Web Apps — Umbraco documents configuration and operation of the self-hosted CMS on Azure App Service in the customer's environment.

    Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Umbraco customer-managed AWS hosting — 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.

    Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

  • cloudimg Umbraco CMS VM in a customer Azure subscription — 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.

    Third party package · Reviewed 2026-11-18 · Version: Guide application 17.5.3; verify actual image and patched build. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-18

Webiny — Customer AWS DeploymentAWSCustomer-operated
Serverless, Hybrid
Open Source / Open Core

Community/open-source and commercial plans; edition and governance entitlements vary

Official project setup and Webiny CLI deployment to customer AWS; Pulumi-based infrastructure.Customer deploys and upgrades the application; AWS operates the underlying managed services.
Scope and evidence

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.

  • Webiny customer AWS installation — 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.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-12

WordPress Self-HostedAWS, Azure, Google Cloud, DigitalOcean, Oracle Cloud, Linode, VultrCustomer-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 providerCustomer manages WordPress core, themes and plugins, application security, identities, content, database, media, backups, scaling and upgrades.
Scope and evidence

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 in the customer's Amazon Lightsail account — AWS documents selecting a region, launching the WordPress blueprint and operating the instance in the customer's Lightsail account.

    Provider guide · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

  • WordPress on Azure App Service — Microsoft's quickstart deploys the WordPress Marketplace item and backing Azure resources into the customer's selected subscription and resource group.

    Provider guide · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

  • WordPress on Google Cloud — Google documents customer deployments of WordPress on Google Cloud, including a Compute Engine path. Provider packaging and support scope must be reviewed.

    Provider guide · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

  • WordPress DigitalOcean 1-Click application — DigitalOcean installs the full WordPress application and database on a customer Droplet. Confirm the resolved image version and production/HA design.

    Provider guide · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

  • OCI Resource Manager WordPress template — 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.

    Provider guide · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

  • WordPress on Akamai Cloud (Linode) — Akamai documents full application/database deployment on a customer Compute Instance using StackScript 401697, with Cloud Manager and API/CLI inputs.

    Provider guide · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Vultr 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.

    Provider guide · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

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

CrafterCMS

Self-hosted content authoring and delivery platform.

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

  • crafter-aws-base ↗

    Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

    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.

Cloud evidence reviewed 2026-11-19. 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

Drupal

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

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 server on Amazon Lightsail ↗

    Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

    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.

Cloud evidence reviewed 2026-11-12. Full listing and qualifications

Grav

Self-hosted flat-file content management system.

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.

  • Cloudron Store ↗

    Package platform documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

    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.

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 Amazon EKS ↗

    Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.

    HCL documents deploying the entitled DX Helm chart to Amazon-managed Kubernetes in the customer's AWS environment.

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 AWS Ready ↗

    Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.

    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.

Cloud evidence reviewed 2026-11-17. Full listing and qualifications

Pimcore Platform

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

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.

  • Pimcore deployment in an existing customer AWS account through Metaways ↗

    Partner evidence · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

    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.

  • Pimcore identification of Metaways as a technology partner ↗

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

    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.

Cloud evidence reviewed 2026-11-12. Full listing and qualifications

Plone

Self-hosted enterprise content management and publishing platform.

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

  • plone-in-a-box ↗

    Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

    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.

Cloud evidence reviewed 2026-11-19. 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.

  • AWS EC2 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

Umbraco CMS Self-Hosted

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

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 customer-managed AWS hosting ↗

    Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

    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.

Cloud evidence reviewed 2026-11-18. Full listing and qualifications

Webiny — Customer AWS Deployment

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

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.

  • Webiny customer AWS installation ↗

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

    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.

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 in the customer's Amazon Lightsail account ↗

    Provider guide · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

    AWS documents selecting a region, launching the WordPress blueprint and operating the instance in the customer's Lightsail account.

Cloud evidence reviewed 2026-11-18. Full listing and qualifications

Deployment and procurement checks

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. Provider source ↗ · 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. Provider source ↗ · 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. Provider source ↗ · 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. 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: AWS account. Access: IAM roles and policies. Network: VPC.

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