
# Digital asset management on AWS

Compare documented Digital asset management deployments on AWS, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/aws/digital-asset-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.

11 listings.


## Avalon Media System

Open-source audiovisual repository and access platform with an upstream AWS turnkey deployment.

- Listing: https://launchinyourcloud.com/directory/avalon-media-system/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Terraform
- Architecture: Avalon application and media-processing/storage services provisioned by the project's Terraform scripts.
- 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/avalonmediasystem/avalon-terraform
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Avalon application versions and turnkey Terraform versions are separate. Confirm current media-processing dependencies, storage policies and institutional access controls before production use.

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

Avalon application and media-processing/storage services provisioned by the project's Terraform scripts. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- archives-collections-management: Open-source audiovisual repository and access platform with an upstream AWS turnkey deployment.

- digital-asset-management: Open-source audiovisual repository and access platform with an upstream AWS turnkey deployment.

### Deployment boundaries


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


### Cloud deployment evidence

- avalon-terraform (aws): https://github.com/avalonmediasystem/avalon-terraform
  Avalon application and media-processing/storage services provisioned by the project's Terraform scripts. Avalon application versions and turnkey Terraform versions are separate. Confirm current media-processing dependencies, storage policies and institutional access controls before production use.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes cjcolvar, masaball, Dananji, 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/avalonmediasystem/avalon/graphs/contributors

- Upstream project: https://github.com/avalonmediasystem/avalon

### Sources

- avalon-terraform: https://github.com/avalonmediasystem/avalon-terraform

- Apache-2.0 LICENSE: https://github.com/avalonmediasystem/avalon/blob/main/LICENSE

- GitHub Releases: https://github.com/avalonmediasystem/avalon/releases

### Licensing sources

- https://github.com/avalonmediasystem/avalon/blob/main/LICENSE

### Infrastructure sources

- https://github.com/avalonmediasystem/avalon-terraform


### 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. Avalon v8.2.2 publishes an OmniAuth integration that loads configured providers, includes the SAML strategy and maps the returned identity through its user callbacks. The published source confirms this integration path; the default local-account setup does not enable SSO. Supply and test the institutional IdP, attributes and account mapping. Scope: Avalon v8.2.2 configurable OmniAuth/SAML application login; institution-specific provider configuration required. Source: https://github.com/avalonmediasystem/avalon/blob/v8.2.2/config/initializers/devise.rb (reviewed 2026-11-20). Supporting source: Published SAML strategy dependency — https://github.com/avalonmediasystem/avalon/blob/v8.2.2/Gemfile. Supporting source: Application sign-in callback — https://github.com/avalonmediasystem/avalon/blob/v8.2.2/app/controllers/users/omniauth_callbacks_controller.rb. Supporting source: Provider identity mapping — https://github.com/avalonmediasystem/avalon/blob/v8.2.2/app/models/user.rb.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official project publishes a Terraform AWS deployment with application containers, networking, persistent services and initial-admin instructions. It targets low-to-medium traffic. Configure DNS/state, credentials, compatible application/dependency images, storage and email; this is not certification of an arbitrary HA workload. Scope: Avalon AWS Terraform deployment; provisioner and application releases must be version-matched. Source: https://github.com/avalonmediasystem/avalon-terraform/blob/main/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/avalonmediasystem/avalon-terraform/tree/main. Artifact reference: main (moving branch); select compatible Avalon/container and Terraform/provider versions.

- Minimum footprint / sizing: Documented. The AWS Terraform recipe defaults to a t3.large application/Compose host with a 75 GB root volume, plus separate supporting database/storage resources. These are adjustable recipe defaults for low-to-medium traffic, not a minimum for every media library or a validated 100-user, 1 TB HA design. Scope: Avalon project AWS example allocation; transcoding, derivatives, database, object storage, backups and replicas must be sized together. Source: https://github.com/avalonmediasystem/avalon-terraform/blob/main/variables.tf (reviewed 2026-11-20). Supporting source: Recipe goals and architecture — https://github.com/avalonmediasystem/avalon-terraform/blob/main/README.md.

- License pricing: Documented. Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Avalon Media System; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/avalonmediasystem/avalon/blob/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## FormKiQ Digital Asset Management

Manage images, video, audio, and business media with a packaged DAM application, API integration, flexible metadata, approvals, and AWS deployment control.

- Listing: https://launchinyourcloud.com/directory/formkiq-digital-asset-management/
- Publisher listing: Yes — FormKiQ publishes this directory.
- Entry kind: solution; configured solution on formkiq
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: serverless
- License: Commercial FormKiQ Advanced or Enterprise; confirm required extensions
- Licensing model: commercial-only
- Installation: Configure the solution in a FormKiQ deployment; CloudFormation installs the platform.
- Architecture: Application on the FormKiQ document and workflow platform
- Operations: Customer-managed AWS deployment option; agree solution configuration, modules and support with FormKiQ.
- Product website: https://formkiq.com/solutions/digital-asset-management/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This is a business solution built on FormKiQ, not a separate infrastructure product. Its application configuration and available capabilities depend on the agreed edition and extension modules. This listing covers the customer-managed AWS option; vendor-managed deployments are outside this entry.

This listing describes the packaged Business Solution available through commercial Advanced/Enterprise deployments. The separate open-source Core platform does not by itself include this packaged solution.

Serverless baseline for this business solution; no required OpenSearch dependency is identified. Optional OpenSearch add-ons are evaluated separately and do not add a Hybrid label to this listing.


OpenSearch required for this solution: No

### Category fit

- digital-asset-management: Media metadata, rights, approvals, renditions and distribution.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq (checked 2026-11-12). 


### Cloud deployment evidence

- FormKiQ commercial AWS installation (aws): https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq
  The publisher documents customer-specific CloudFormation installation for Essentials, Advanced and Enterprise, including target AWS regions and licensed modules. Business solutions are configurations of this same AWS platform; their solution scope and entitlements must be agreed separately.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed. Edition: FormKiQ platform; solution configuration and entitlement must be agreed separately.


### Sources

- Digital Asset Management solution: https://formkiq.com/solutions/digital-asset-management/

- Business solution editions and platform relationship: https://formkiq.com/solutions/

- Commercial deployment notes: https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq

- Platform infrastructure and optional components: https://docs.formkiq.com/docs/platform/overview

- Licensing and edition terms: https://formkiq.com/pricing/

### Licensing sources

- https://formkiq.com/solutions/

- https://formkiq.com/pricing/

### Infrastructure sources

- https://formkiq.com/solutions/digital-asset-management/

- https://docs.formkiq.com/docs/platform/overview


### Buyer diligence


Research coverage: 5/12 fields (42%); 3 documented, 2 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.

This is a configured solution. Parent platform buyer facts: https://launchinyourcloud.com/directory/formkiq/#buyer-diligence. Parent entitlements, sizing and release versions are not automatically established for this solution.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The solution overview describes configurable access and workflows but does not establish its actual end-user SAML/OIDC integration, identity provider or account mapping. FormKiQ platform Cognito/JWT and IAM/API authentication are separate evidence; obtain the solution-specific login design and included commercial modules. Scope: FormKiQ Digital Asset Management; configured commercial AWS solution, not the public Core deployment; solution-user federation remains unconfirmed. Source: https://formkiq.com/solutions/digital-asset-management/ (reviewed 2026-11-21). Supporting source: Underlying platform architecture — https://docs.formkiq.com/docs/platform/overview.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Source files and renditions retain document-specific access permissions; release and external publishing services require configured boundaries. This is a vendor-described configurable control, not an independent attestation or a tested implementation. Scope: FormKiQ Digital Asset Management; customer-managed AWS deployment; configured commercial solution, not Core; agreed application configuration and modules. Source: https://formkiq.com/solutions/digital-asset-management/ (reviewed 2026-11-16).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Commercial installations use customer-specific CloudFormation templates supplied during onboarding. Request the template for this solution, licensed modules and AWS region; the public Core template does not include the configured solution. Scope: FormKiQ Digital Asset Management; customer-managed AWS deployment; configured commercial solution, not Core. Source: https://formkiq.com/solutions/digital-asset-management/ (reviewed 2026-11-16). Supporting source: Commercial deployment and customer-specific templates — https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq.

- Minimum footprint / sizing: Sources checked — unresolved. The configured solution uses customer-specific deployment and optional processing/search/integration modules. No quantitative solution-specific CPU/RAM/concurrency/storage baseline was established. Serverless platform architecture and a document-import benchmark do not size the complete business workflow, external services or HA/recovery requirements. Scope: FormKiQ Digital Asset Management; configured commercial AWS solution, not the public Core deployment; complete workload sizing remains unconfirmed. Source: https://formkiq.com/solutions/digital-asset-management/ (reviewed 2026-11-21). Supporting source: Platform architecture and optional components — https://docs.formkiq.com/docs/platform/overview. Supporting source: Commercial deployment templates — https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq.

- License pricing: Documented. The solution requires agreed commercial scope. The solution page identifies Advanced or Enterprise; confirm the edition, modules, implementation and support in a solution quote. Published base-platform prices are not the total solution price; AWS usage and connected services are additional. Scope: FormKiQ Digital Asset Management; customer-managed AWS deployment; configured commercial solution, not Core. Source: https://formkiq.com/solutions/digital-asset-management/ (reviewed 2026-11-16). Supporting source: Edition pricing and separately quoted modules/services — https://formkiq.com/pricing/.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## HCL Digital Experience Cloud Native 9.5

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

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

### Scope and qualifications

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

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

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


### Category fit

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

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

### Deployment boundaries


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

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

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


### Cloud deployment evidence

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

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

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


### Sources

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

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

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

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

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

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

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

### Licensing sources

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

### Infrastructure sources

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

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


### Buyer diligence


Research coverage: 12/12 fields (100%); 5 documented, 7 unresolved. Coverage is not a feature score.

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


- Marketplace delivery: Documented. HCL documents DX 9.5 Helm deployment through AWS Marketplace. Obtain the matching subscription and container access; licensing and image versions must match the selected cumulative fix. Scope: HCL DX 9.5 AWS Marketplace Helm route. Source: https://help.hcl-software.com/digital-experience/9.5/CF239/deployment/install/container/helm_deployment/aws_marketplace_helm_deployment/ (reviewed 2026-11-17).

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

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

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

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

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

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

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

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

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

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

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







## Liferay DXP Cloud Native Experience

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

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

### Scope and qualifications

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

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

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


### Category fit

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

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

### Deployment boundaries


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

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

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


### Cloud deployment evidence

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

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

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


### Sources

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

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

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

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

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

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

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

### Licensing sources

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

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

### Infrastructure sources

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

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


### Buyer diligence


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

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


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

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

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

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

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

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

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

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

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

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

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

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







## Lychee

Self-hosted photo gallery, albums and image sharing.

- Listing: https://launchinyourcloud.com/directory/lychee/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, 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; Docker / Compose
- Architecture: Lychee application, database and persistent originals and thumbnails.
- 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://lycheeorg.dev
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Public, protected and private album modes must be configured deliberately; hosting the server does not make every gallery private.

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

Lychee application, database and persistent originals and thumbnails. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- digital-asset-management: Self-hosted photo gallery, albums and image sharing.

### Deployment boundaries


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

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

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

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

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

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


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/lychee.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 ildyria, kamil4, nagmat84, 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/LycheeOrg/Lychee/graphs/contributors

- Upstream project: https://github.com/LycheeOrg/Lychee

### Sources

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

- Hostinger: https://www.hostinger.com/applications/lychee

- MIT LICENSE: https://raw.githubusercontent.com/LycheeOrg/Lychee/master/LICENSE

- GitHub Releases: https://github.com/LycheeOrg/Lychee/releases

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

### Licensing sources

- https://raw.githubusercontent.com/LycheeOrg/Lychee/master/LICENSE

### Infrastructure sources

- https://www.cloudron.io/store/lychee.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. Lychee v7.13.0 implements configured OAuth provider redirects/callbacks and signs users into the gallery through linked provider accounts. Optional first-login user creation is separately configurable. Configure a supported provider, credentials, callback and account-linking policy; this does not establish arbitrary SAML/SCIM support or inclusion in every Cloudron package. Scope: Upstream Lychee v7.13.0 gallery-user OAuth login; packaging and configured-provider scope. Source: https://github.com/LycheeOrg/Lychee/blob/v7.13.0/app/Actions/Oauth/Oauth.php (reviewed 2026-11-21). Supporting source: OAuth redirect/callback controller — https://github.com/LycheeOrg/Lychee/blob/v7.13.0/app/Http/Controllers/OauthController.php.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream v7.13.0 repository provides a Docker Compose configuration for the gallery, persistent uploads and supporting services. The example defaults to a moving latest application image: pin a compatible image, configure database/secrets and storage, and review its security and worker settings before production. The current install guide also links a minimal quick start. Scope: Versioned upstream Compose example; example image tags and current online quick start require explicit release selection. Source: https://github.com/LycheeOrg/Lychee/blob/v7.13.0/docker-compose.yaml (reviewed 2026-11-21). Deployment artifact: https://github.com/LycheeOrg/Lychee/blob/v7.13.0/docker-compose.yaml. Artifact reference: v7.13.0. Supporting source: Installation guide — https://lycheeorg.dev/docs/getting-started/installation/.

- 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/lychee.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: Lychee; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/LycheeOrg/Lychee/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## Nuxeo Platform

Extensible content repository and digital asset management platform.

- Listing: https://launchinyourcloud.com/directory/nuxeo-platform/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 source; distribution access, support subscriptions and add-on entitlements have separate conditions.
- Licensing model: open-source
- Installation: Deploy the documented Docker image, ZIP distribution or Kubernetes Helm chart.
- Architecture: Long-running Java application/container deployment with external production services.
- Operations: Manage runtime services, storage, configuration, backups, upgrades and subscription or package access.
- Product website: https://www.hyland.com/en/products/nuxeo
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Current LTS Docker images are private: customers request registry access through support or sales. Trial/default-image language does not grant production access to every package.

The current license documentation states Apache 2.0 for Nuxeo source and explicitly says there is no separate closed enterprise version. Subscription, private-image access and marketplace-package conditions remain material procurement constraints.

Docker/ZIP deployments run a persistent Java server; Helm runs containers. These own-infrastructure paths are classified as servers.


### Category fit

- digital-asset-management: Dedicated DAM functions cover ingestion, organization, media metadata, versioning, workflows, search and distribution.

- document-management: A configurable content repository with document metadata, versions and workflow; implementation is required.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://doc.nuxeo.com/nxdoc/2023/nuxeo-reference-architectures/ (checked 2026-11-12). 


### Cloud deployment evidence

- Nuxeo customer-operated reference architecture on AWS (aws): https://doc.nuxeo.com/nxdoc/2023/nuxeo-reference-architectures/
  The vendor reference architecture explicitly describes AWS as the target IaaS, Nuxeo server instances on Amazon Machine Images, load balancing and backing services. The reviewed page is scoped to LTS 2023; confirm the architecture and supported components for the selected maintained LTS release. Current production images require customer registry access; this is separate from Nuxeo Cloud.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

LTS 2025.27 was released October 26, 2026. Hyland identifies Electronic Arts as a Nuxeo adopter for media asset workflows.

Reviewed 2026-11-10.

- Current server release notes: https://doc.nuxeo.com/nxdoc/nuxeo-server-release-notes/

- Named Electronic Arts adoption: https://www.hyland.com/en/resources/articles/dam-vs-pim

### Sources

- LTS installation options and Connect prerequisites: https://doc.nuxeo.com/nxdoc/installation/

- Private Docker image access: https://doc.nuxeo.com/nxdoc/docker-image/

- Current DAM documentation: https://doc.nuxeo.com/nxdoc/dam/

- Versioning and asset workflow: https://doc.nuxeo.com/nxdoc/manage-and-organize/

- Software licenses: https://doc.nuxeo.com/nxdoc/licenses/

- Current LTS maintenance: https://doc.nuxeo.com/nxdoc/nuxeo-server-release-notes/

- Infrastructure or licensing evidence: https://doc.nuxeo.com/userdoc/adding-features/

### Licensing sources

- https://doc.nuxeo.com/nxdoc/licenses/

- https://doc.nuxeo.com/nxdoc/docker-image/

- https://doc.nuxeo.com/userdoc/adding-features/

### Infrastructure sources

- https://doc.nuxeo.com/nxdoc/installation/

- https://doc.nuxeo.com/nxdoc/docker-image/


### 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 LTS 2025 installation matrix lists SAML, OpenID, Kerberos and CAS authentication integrations. Configure the selected authentication module and verify identity-provider and distribution entitlements. Scope: Nuxeo Platform LTS 2025 authentication compatibility. Source: https://doc.nuxeo.com/nxdoc/installation/ (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 LTS 2025 guide publishes a Nuxeo Helm repository for Kubernetes. The chart references a private vendor image by default, requiring authorized registry access; select matching platform/chart versions and provision the other required services. Scope: Nuxeo LTS 2025 Helm deployment; not an anonymously downloadable application image. Source: https://doc.nuxeo.com/nxdoc/kubernetes-helm-chart/ (reviewed 2026-11-14). Deployment artifact: https://packages.nuxeo.com/repository/helm-releases-public/. Artifact reference: select a released chart and matching licensed Nuxeo image.

- Minimum footprint / sizing: Documented. The vendor lists 2 CPUs, 2 GB RAM and 1 GB disk merely to start a server. Production databases, search, content storage and HA require separately sized resources; this is not a 100-user or 1-TB production recommendation. Scope: LTS 2025 server startup minimum; production architecture excluded. Source: https://doc.nuxeo.com/nxdoc/installation/ (reviewed 2026-11-20).

- License pricing: Documented. Nuxeo identifies Apache-2.0 source licensing and separately recommends a support subscription. Access to the current private distribution image and optional packages must be agreed; public source licensing does not establish a subscription price. Scope: Nuxeo Platform source licence and separate distribution/support access. Source: https://doc.nuxeo.com/nxdoc/licenses/ (reviewed 2026-11-20). Supporting source: Current image-access requirements — https://doc.nuxeo.com/nxdoc/installation/.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## PeerTube

Self-hosted video publishing and federated media platform.

- Listing: https://launchinyourcloud.com/directory/peertube/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Cloudron package; Docker / Compose
- Architecture: PeerTube application, PostgreSQL, Redis, video storage and processing workers.
- 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://joinpeertube.org/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

PeerTube 8.3.2 includes a sharp/libvips security update. Federation and optional peer-to-peer playback share metadata or traffic outside the host; review those settings for confidential media. Update PeerTube and its bundled image-processing dependencies through the compatible 8.3.2-or-later upgrade process.

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

PeerTube application, PostgreSQL, Redis, video storage and processing workers. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- digital-asset-management: Self-hosted video publishing and federated media platform.

### Deployment boundaries


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

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

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

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

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

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


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/peertube.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 Chocobozzz, rigelk, s8321414, 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/Chocobozzz/PeerTube/graphs/contributors

- Upstream project: https://github.com/Chocobozzz/PeerTube

### Sources

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

- Hostinger: https://www.hostinger.com/applications/peertube

- AGPL-3.0 LICENSE: https://raw.githubusercontent.com/Chocobozzz/PeerTube/develop/LICENSE

- GitHub Releases: https://github.com/Chocobozzz/PeerTube/releases

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

- PeerTube image-processing dependency update: https://github.com/Chocobozzz/PeerTube/releases/tag/v8.3.2

### Licensing sources

- https://raw.githubusercontent.com/Chocobozzz/PeerTube/develop/LICENSE

### Infrastructure sources

- https://www.cloudron.io/store/peertube.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. PeerTube documents external authentication plugins, and Framasoft maintains an official OIDC plugin that adds provider login to the user form, with a callback, role mapping and optional group restrictions. Configure a compatible plugin release and account-migration policy. This is user federation via an optional plugin, not the core API password-token flow or a guarantee for every packaged installation. Scope: Self-hosted PeerTube external user authentication; optional official plugin and deployment/version compatibility. Source: https://docs.joinpeertube.org/admin/managing-users (reviewed 2026-11-21). Supporting source: Official OIDC plugin documentation — https://framagit.org/framasoft/peertube/official-plugins/-/blob/master/peertube-plugin-auth-openid-connect/README.md.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. PeerTube supplies a versioned production Docker Compose example and an installation guide covering the application, reverse proxy, PostgreSQL, Redis, configuration and persistent volumes. Match the example to the application image, set domains/secrets and TLS, and size transcoding/storage and backup arrangements separately; a single Compose host does not establish HA. Scope: Upstream PeerTube v8.3.2 production container example; platform packaging and HA are separate concerns. Source: https://github.com/Chocobozzz/PeerTube/blob/v8.3.2/support/docker/production/docker-compose.yml (reviewed 2026-11-21). Deployment artifact: https://github.com/Chocobozzz/PeerTube/blob/v8.3.2/support/docker/production/docker-compose.yml. Artifact reference: v8.3.2. Supporting source: Docker installation — https://docs.joinpeertube.org/install/docker.

- Minimum footprint / sizing: Documented. The Cloudron package declares 1024MB 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/peertube.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

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

- Operating cost estimate: Not researched.

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




### Security and lifecycle reviews

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

- PeerTube image-processing dependency update (security-advisory): PeerTube 8.3.2 includes security maintenance for its image-processing dependency. Scope: PeerTube 8.3.2 release and its sharp/libvips change; check the actual dependency build rather than inferring all older versions are affected. Conditions: Exposure depends on the installed image-processing libraries and enabled input paths. Action: Update PeerTube and its bundled image-processing dependencies through the compatible 8.3.2-or-later upgrade process. Source: https://github.com/Chocobozzz/PeerTube/releases/tag/v8.3.2; reviewed 2026-11-19.




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







## Piwigo

Self-hosted photo management, albums and media gallery.

- Listing: https://launchinyourcloud.com/directory/piwigo/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock
- 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: Cloudron package; Docker / Compose
- Architecture: Piwigo application, database, originals and generated images.
- 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://piwigo.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Plugins, storage and published album permissions require separate review; package versions and upstream releases can differ.

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

Piwigo application, database, originals and generated images. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- digital-asset-management: Self-hosted photo management, albums and media gallery.

### Deployment boundaries


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

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

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

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

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

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


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/piwigo.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 Piwigo-TranslationTeam, plegall, ddtddt, 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/Piwigo/Piwigo/graphs/contributors

- Upstream project: https://github.com/Piwigo/Piwigo

### Sources

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

- Hostinger: https://www.hostinger.com/applications/piwigo

- GPL-2.0 COPYING.txt: https://raw.githubusercontent.com/Piwigo/Piwigo/master/COPYING.txt

- GitHub Releases: https://github.com/Piwigo/Piwigo/releases

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

### Licensing sources

- https://raw.githubusercontent.com/Piwigo/Piwigo/master/COPYING.txt

### Infrastructure sources

- https://www.cloudron.io/store/piwigo.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 Piwigo extension catalog lists OpenIDConnectNext with Piwigo 16 compatibility. Its maintained plugin documents OIDC login, provider/client configuration and account linking, and reports testing with Piwigo 16.5/PHP 8.4. Install a compatible plugin release and choose the authorization-code flow; this is an optional integration, not automatic federation in every gallery image. Scope: Piwigo 16.x with the maintained ProximApp OpenIDConnectNext plugin; extension evidence rather than universal package inclusion. Source: https://piwigo.org/ext/index.php?eid=1049 (reviewed 2026-11-21). Supporting source: Plugin documentation — https://github.com/ProximApp/PiwigoOpenIdConnectNext/blob/master/README.md. Supporting source: Plugin release v2.2.0 — https://github.com/ProximApp/PiwigoOpenIdConnectNext/releases/tag/v2.2.0.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Piwigo documents downloading the full application archive, uploading it to a PHP web server and running the browser installer with MySQL credentials and a webmaster account. This is a maintained manual installation path, not a cloud provisioning template; select the application release and separately configure hosting, TLS, backups and upgrades. Scope: Upstream self-hosted manual installer; cloud hosting/package automation remains a separate layer. Source: https://github.com/Piwigo/piwigo-docs-en/blob/main/docs/self-hosting-piwigo/install-guides/manual-install.md (reviewed 2026-11-21). Deployment artifact: https://github.com/Piwigo/piwigo-docs-en/blob/main/docs/self-hosting-piwigo/install-guides/manual-install.md. Artifact reference: Current upstream self-hosting manual reviewed on this date. Supporting source: Versioned core release — https://github.com/Piwigo/Piwigo/tree/16.5.0.

- 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/piwigo.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

- License pricing: Documented. GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Piwigo; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/Piwigo/Piwigo/master/COPYING.txt (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## ResourceSpace Self-Hosted

Open-source digital asset management deployed on your own infrastructure.

- Listing: https://launchinyourcloud.com/directory/resourcespace/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open source; paid hosting and support available separately
- Licensing model: open-source
- Installation: Official Docker Compose or source/LAMP installation
- Architecture: Customer-operated DAM application, database and asset storage
- Operations: Customer manages the application, database, asset storage, backups and upgrades.
- Product website: https://www.resourcespace.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The official download page explicitly names AWS, Azure and Google Cloud for self-installed Docker deployments. The installation guide provides the official repository and Compose instructions. Other provider support is not inferred from Docker portability.

ResourceSpace publishes its self-hosted code under a permissive BSD-style license allowing modification and redistribution, with attribution and derivative-name trademark conditions. Paid hosting/support is separate, not evidence of proprietary feature code; inspect the actual release license for exact terms.

The listed self-hosted installation uses application servers, database services or container workloads. This classification covers that deployment option; managed storage or a vendor control plane does not make the application serverless.


Cloud evidence scope: Documented provider-specific deployment

### Category fit

- digital-asset-management: Dedicated digital asset management for organizing, finding and distributing media. This entry covers self-installation, not vendor-hosted free or managed cloud plans. Validate production sizing and backup design.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.resourcespace.com/get?from_rs=true (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.resourcespace.com/get?from_rs=true (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.resourcespace.com/get?from_rs=true (checked 2026-11-12). 


### Cloud deployment evidence

- ResourceSpace self-installation cloud compatibility (aws, azure, gcp): https://www.resourcespace.com/get?from_rs=true
  The vendor explicitly identifies AWS, Azure and Google Cloud for self-installation, alongside its separate hosted service. The linked Docker/source installation instructions establish the customer-operated application path; select compatible dependencies and arrange support separately.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Self-installation and named cloud platforms: https://www.resourcespace.com/get?from_rs=true

- Official Docker installation steps: https://www.resourcespace.com/knowledge-base/systemadmin/install_docker

- Product and self-hosting FAQ: https://www.resourcespace.com/faq

- Licensing and edition terms: https://www.resourcespace.com/docs/ResourceSpace_License_Agreement.pdf

- Licensing and edition terms: https://www.resourcespace.com/terms

### Licensing sources

- https://www.resourcespace.com/docs/ResourceSpace_License_Agreement.pdf

- https://www.resourcespace.com/faq

- https://www.resourcespace.com/terms

### Infrastructure sources

- https://www.resourcespace.com/get?from_rs=true

- https://www.resourcespace.com/knowledge-base/systemadmin/install_docker


### 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. ResourceSpace publishes a SimpleSAMLphp-based plugin for SAML 2.0 identity-provider login. Enable the plugin and exchange provider metadata; group mapping, local-login fallback and share-access rules are configurable. Metadata-URL handling and migration steps depend on the ResourceSpace/plugin version. Scope: ResourceSpace self-hosted SAML plugin; an existing compatible IdP and administrator configuration are required. Source: https://www.resourcespace.com/knowledge-base/plugins/simplesaml (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 official Docker guide links this application/database deployment repository and requires replacing database credentials before building the stack. Scope: Official ResourceSpace Docker recipe. Source: https://github.com/resourcespace/docker (reviewed 2026-11-14). Deployment artifact: https://github.com/resourcespace/docker. Artifact reference: repository default branch (moving).

- Minimum footprint / sizing: Sources checked — unresolved. The official requirements specify its LAMP stack and preview-processing tools, but do not establish a quantitative whole-host CPU/RAM/storage floor for the intended DAM workload. PHP limits and hosted storage allowances are not production capacity for originals, previews, video jobs, database and replicas. Scope: Complete self-hosted ResourceSpace deployment; current version and selected preview/AI integrations affect sizing. Source: https://www.resourcespace.com/knowledge-base/systemadmin/general_requirements (reviewed 2026-11-20).

- License pricing: Documented. The vendor FAQ states that local installation has no software licence fee or per-user charge. Paid hosting, technical/customer support and services are separate. The hosted free-storage allowance does not establish a self-hosted infrastructure cost or include a support contract. Scope: ResourceSpace self-hosted software pricing; review the actual software licence and any hosting/support agreement separately. Source: https://www.resourcespace.com/faq (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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



