
# Software on Oracle Cloud

Explore software with documented Oracle Cloud Infrastructure deployment, customer-account guidance, licensing qualifications and source evidence.

Canonical page: https://launchinyourcloud.com/clouds/oci/
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: Tenancy and compartment
- 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.oracle.com/en-us/iaas/Content/Identity/Tasks/managingcompartments.htm (checked 2026-11-20).
- Network: Virtual Cloud Network (VCN)
- Identity and access: OCI IAM policies and identities
- Installation guidance: Terraform, optionally orchestrated through OCI Resource Manager stacks.
- Guidance source: https://docs.oracle.com/en-us/iaas/Content/ResourceManager/Concepts/resourcemanager.htm
- Guidance reviewed: 2026-11-10


### Dedicated connectivity

FastConnect links a customer data center privately to OCI. Review partner/circuit availability, routing and redundancy; an OCI application guide does not automatically include that connectivity.
Source: https://docs.oracle.com/en-us/iaas/Content/Network/Concepts/fastconnect.htm (reviewed 2026-11-14).

The listings below have evidence for Oracle Cloud Infrastructure. Read each cloud evidence note for the applicable package, edition and support qualifications.

23 listings.


## Coroot Community Edition

Self-hosted application observability with service maps, logs, metrics, traces and continuous profiling.

- Listing: https://launchinyourcloud.com/directory/coroot-community/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for Coroot Community Edition. Enterprise Edition has separate subscription terms.
- Licensing model: open-source
- Installation: Install the Coroot Operator and Community Edition Helm chart on the customer's Kubernetes cluster.
- Architecture: Customer-operated Coroot server and agents. ClickHouse stores logs, traces and profiles, and metrics can use ClickHouse or Prometheus.
- Operations: The customer manages the operator, image versions, privileged node-agent permissions, storage capacity, telemetry retention, backup and recovery, and access to the UI.
- Product website: https://coroot.com/
- Source review: 2026-11-20; cloud review: 2026-11-20; licensing review: 2026-11-20; infrastructure review: 2026-11-20

### Scope and qualifications

The node agent requires privileged access for eBPF and host inspection, and upstream describes AWS Fargate support as basic. Anonymous usage statistics are enabled by default and can be disabled. The operator updates unpinned Coroot component images automatically. Native SAML/OIDC SSO is Enterprise-only. The Coroot server v1.29.4, Community chart 0.3.3 and operator chart 0.10.8 are separate version tracks; inspect and pin each required image.

Apache-2.0 applies to the published Community code. The Kubernetes guide identifies the separate licensed Enterprise chart.

Coroot and its agents run as Kubernetes workloads. Cluster node agents use eBPF and require compatible Linux kernels and privileged access.


### Category fit

- observability: Node and cluster agents collect operational telemetry for application monitoring and troubleshooting.

### Deployment boundaries


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

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.coroot.com/installation/requirements/ (checked 2026-11-20). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.coroot.com/installation/requirements/ (checked 2026-11-20). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.coroot.com/installation/requirements/ (checked 2026-11-20). 


### Cloud deployment evidence

- Coroot on Amazon EKS (aws): https://docs.coroot.com/installation/requirements/
  The vendor explicitly names EKS as a supported Kubernetes environment. Use the linked Community Helm instructions to deploy the operator, server and agents. The vendor specifies basic support for Fargate.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.

- Coroot on Azure AKS (azure): https://docs.coroot.com/installation/requirements/
  The vendor explicitly names AKS among supported Kubernetes environments. The Community Helm guide installs the server and agents on the customer's cluster, subject to privileges and Linux requirements.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.

- Coroot on Google GKE (gcp): https://docs.coroot.com/installation/requirements/
  The vendor explicitly names GKE among supported Kubernetes environments. The Community Helm guide installs the server and agents on the customer's cluster.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.

- Coroot on Oracle OKE (oci): https://docs.coroot.com/installation/requirements/
  The vendor explicitly names OKE among supported Kubernetes environments. The Community Helm guide installs the server and agents on the customer's cluster.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.


### Community and maintenance

The upstream project has sustained public contributor history (including def, apetruhin, Split174) and a reviewed dated v1.29.4 release. This establishes maintenance/community participation rather than a production suitability, support or capacity guarantee.

Reviewed 2026-11-20.

- Public contributor history: https://github.com/coroot/coroot/graphs/contributors

- Reviewed dated upstream release: https://github.com/coroot/coroot/releases/tag/v1.29.4

### Sources

- Community Helm installation and operating requirements: https://docs.coroot.com/installation/kubernetes/

- Supported orchestrators and Linux requirements: https://docs.coroot.com/installation/requirements/

- Coroot assembly and telemetry flow: https://docs.coroot.com/installation/architecture/

- ClickHouse storage and retention: https://docs.coroot.com/configuration/clickhouse/

- Apache-2.0 license: https://github.com/coroot/coroot/blob/main/LICENSE

- Upstream release history: https://github.com/coroot/coroot/releases

- Usage statistics and opt-out: https://docs.coroot.com/misc/anonymous-usage-statistics/

- Operator package: https://github.com/coroot/helm-charts/releases/download/coroot-operator-0.10.8/coroot-operator-0.10.8.tgz

- Published chart index: https://coroot.github.io/helm-charts/index.yaml

- Buyer evidence: sso: https://docs.coroot.com/configuration/authentication/

- Buyer evidence: footprint: https://github.com/coroot/helm-charts/releases/download/coroot-ce-0.3.3/coroot-ce-0.3.3.tgz

- Buyer evidence: licensePricing: https://github.com/coroot/coroot/blob/v1.29.4/LICENSE

- Buyer evidence: release: https://github.com/coroot/coroot/releases/tag/v1.29.4

- Public contributor history: https://github.com/coroot/coroot/graphs/contributors

### Licensing sources

- https://github.com/coroot/coroot/blob/main/LICENSE

- https://docs.coroot.com/installation/kubernetes/

### Infrastructure sources

- https://docs.coroot.com/installation/kubernetes/

- https://docs.coroot.com/installation/architecture/


### 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. The reviewed edition and deployment sources do not establish an exact marketplace offer, seller and delivery artifact that entitle this edition. A vendor SaaS subscription or another edition is insufficient. Scope: Coroot Community Edition: reviewed customer-cloud deployment. Source: https://docs.coroot.com/installation/kubernetes/ (reviewed 2026-11-20).

- Cloud commitment eligibility: Sources checked — unresolved. No exact offer and buyer-agreement combination establishes cloud-commitment credit. Customer infrastructure charges, software procurement and private-offer eligibility must be assessed separately. Scope: Coroot Community Edition: reviewed customer-cloud deployment. Source: https://docs.coroot.com/installation/kubernetes/ (reviewed 2026-11-20).

- Single sign-on: Explicitly unsupported. The authentication guide explicitly reserves native SAML/OIDC single sign-on for Coroot Enterprise. Community has local users with Admin, Editor and Viewer roles. An external authentication proxy would be a separate configuration, not native Community SSO. Scope: Native Coroot Community authentication; Enterprise is a separate edition. Source: https://docs.coroot.com/configuration/authentication/ (reviewed 2026-11-20).

- SCIM provisioning: Sources checked — unresolved. The reviewed sources do not establish a SCIM endpoint and supported user/group lifecycle for this edition. SSO and just-in-time account creation are not SCIM evidence. Scope: Coroot Community Edition: reviewed customer-cloud deployment. Source: https://docs.coroot.com/installation/kubernetes/ (reviewed 2026-11-20).

- Compliance attestations: Sources checked — unresolved. No reviewed independent report establishes certification of this customer-operated deployment and its infrastructure. Publisher or SaaS attestations do not automatically cover the customer installation; obtain scope, validity and shared responsibilities. Scope: Coroot Community Edition: reviewed customer-cloud deployment. Source: https://docs.coroot.com/installation/kubernetes/ (reviewed 2026-11-20).

- Security controls: Documented. Community provides local-user authentication, three predefined roles and API-key service accounts. Set the initial admin password before exposure and review anonymous-mode settings. Node agents need privileged eBPF/host access; review the operator ClusterRole and its optional restriction on global secret access. Scope: Configured Community access controls and privileged collector/operator boundary. Source: https://docs.coroot.com/configuration/authentication/ (reviewed 2026-11-20). Supporting source: Node-agent privilege requirements — https://docs.coroot.com/installation/kubernetes/. Supporting source: Inspected operator permissions/configuration — https://github.com/coroot/helm-charts/releases/download/coroot-operator-0.10.8/coroot-operator-0.10.8.tgz.

- Air-gapped operation: Sources checked — unresolved. The reviewed sources do not establish a complete disconnected installation, update and licensing workflow. A telemetry opt-out alone does not establish air-gapped support; review registry, package, identity and optional external-service dependencies. Scope: Coroot Community Edition: reviewed customer-cloud deployment. Source: https://docs.coroot.com/installation/kubernetes/ (reviewed 2026-11-20).

- Deployment artifact / IaC: Documented. The inspected coroot-ce 0.3.3 chart creates a Community custom resource and requires a separately installed operator; the reviewed operator chart is 0.10.8 (operator application 1.10.8). Neither chart version identifies the Coroot server release. Pin server, node-agent and cluster-agent images to prevent the documented automatic upgrades. Scope: Community custom resource plus separately versioned operator and component images. Source: https://docs.coroot.com/installation/kubernetes/ (reviewed 2026-11-20). Deployment artifact: https://github.com/coroot/helm-charts/releases/download/coroot-ce-0.3.3/coroot-ce-0.3.3.tgz. Artifact reference: coroot-ce 0.3.3; sha256:e6213b27a4e73924d2fe03c12aa815ebd8ec806436c3a5ab9bd4a8801c18e6f3; operator chart 0.10.8 / operator 1.10.8. Supporting source: Operator package — https://github.com/coroot/helm-charts/releases/download/coroot-operator-0.10.8/coroot-operator-0.10.8.tgz. Supporting source: Published chart index — https://coroot.github.io/helm-charts/index.yaml.

- Minimum footprint / sizing: Documented. The inspected Community chart defaults to 10 GiB Coroot storage, 10 GiB Prometheus storage and 100 GiB per ClickHouse instance. Its default ClickHouse layout is one shard/replica; the installation guide overrides this to two shards and two replicas. Operator requests are 100m CPU/64 MiB. These are component defaults, not total cluster CPU/RAM minima or an HA capacity guarantee. Scope: Chart-specific storage and operator request baseline; server/agent/database sizing remains workload-dependent. Source: https://github.com/coroot/helm-charts/releases/download/coroot-ce-0.3.3/coroot-ce-0.3.3.tgz (reviewed 2026-11-20). Supporting source: Separate operator requests — https://github.com/coroot/helm-charts/releases/download/coroot-operator-0.10.8/coroot-operator-0.10.8.tgz. Supporting source: Installation layout and replica override — https://docs.coroot.com/installation/kubernetes/. Supporting source: Kernel and orchestrator prerequisites — https://docs.coroot.com/installation/requirements/.

- License pricing: Documented. Coroot Community v1.29.4 is licensed under Apache-2.0. This establishes the software licence rather than a per-seat subscription; Enterprise features/support, dependencies and infrastructure have separate costs. Scope: Upstream Community code; excludes Enterprise subscriptions. Source: https://github.com/coroot/coroot/blob/v1.29.4/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Sources checked — unresolved. No complete dated operating-cost estimate is established. The AWS us-east-1 baseline of 100 internal users, 1 TB stored data and HA still needs daily telemetry ingestion, retention, monitored infrastructure, query concurrency and commercial entitlements. Human user count does not size the telemetry backend. Scope: Coroot Community Edition: reviewed customer-cloud deployment. Source: https://docs.coroot.com/installation/kubernetes/ (reviewed 2026-11-20).

- Release snapshot / cadence: Documented. The reviewed Coroot Community server snapshot is v1.29.4, published November 18, 2026. Operator, server, agents and charts are independently versioned; this snapshot does not guarantee support or pin the complete installation. Scope: Upstream Community server release. Source: https://github.com/coroot/coroot/releases/tag/v1.29.4 (reviewed 2026-11-20).







## FileCloud Server — Self-Hosted VDR

Commercial customer-hosted file platform with virtual data-room controls for confidential business documents.

- Listing: https://launchinyourcloud.com/directory/filecloud-server/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, oci, alibaba
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial FileCloud Server license; edition-dependent capabilities
- Licensing model: commercial-only
- Installation: FileCloud Server installation on supported customer infrastructure
- Architecture: Persistent customer-operated server application and file storage; follow the Server system requirements and selected deployment package.
- Operations: Customer maintains server infrastructure, storage, backups, configuration and upgrades under the selected FileCloud support arrangement.
- Product website: https://www.filecloud.com/
- Source review: 2026-11-14; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The VDR page explicitly supports on-premises deployment. This listing selects FileCloud Server, not FileCloud Online or the separately scoped Community Edition. Verify VDR controls, access features and governance requirements against the selected Server license. FileCloud’s November 13, 2026 advisories say high-availability deployments using MongoDB replica sets through 23.263.3 are affected by critical CVE-2026-118383; restrict port 27017 to trusted hosts until 23.264. RHEL deployments should also verify that Apache mod_http2 is not exposed to HTTP/2 because CVE-2026-119618 applies when it is loaded.

Commercial FileCloud Server software under the vendor EULA. A separate free Community Edition does not establish open-source licensing or business VDR feature entitlement.

Persistent customer-operated server application and file storage; follow the Server system requirements and selected deployment package.


### Category fit

- data-rooms-ma-document-management: Self-hosted virtual data rooms for transaction due diligence and controlled external document sharing; confirm the required governance edition.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/installing-filecloud-server/installation/amazon-web-services-aws-installation (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/installing-filecloud-server/installation/microsoft-azure-installation (checked 2026-11-12). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/installing-filecloud-server/installation/oracle-cloud-installation (checked 2026-11-12). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/installing-filecloud-server/installation/alibaba-cloud-installation (checked 2026-11-12). 


### Cloud deployment evidence

- FileCloud Server installation on AWS (aws): https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/installing-filecloud-server/installation/amazon-web-services-aws-installation
  The vendor documents FileCloud Server deployment using its vendor AMI on EC2. Confirm image version, licensing, storage and security requirements; this is not FileCloud Online.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- FileCloud Server installation on Azure (azure): https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/installing-filecloud-server/installation/microsoft-azure-installation
  The vendor documents FileCloud Server deployment using its vendor virtual machine image. Confirm image version, licensing, storage and security requirements; this is not FileCloud Online.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- FileCloud Server installation on Oracle Cloud Infrastructure (oci): https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/installing-filecloud-server/installation/oracle-cloud-installation
  The vendor documents FileCloud Server deployment using its Marketplace image in a customer compartment. Confirm image version, licensing, storage and security requirements; this is not FileCloud Online.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- FileCloud Server installation on Alibaba Cloud (alibaba): https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/installing-filecloud-server/installation/alibaba-cloud-installation
  The vendor documents FileCloud Server deployment using its ECS instance in the customer account. Confirm image version, licensing, storage and security requirements; this is not FileCloud Online.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- VDR functions and on-premises deployment: https://www.filecloud.com/vdr/

- Server system requirements: https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/about-filecloud-for-administrators/requirements

- Server license purchasing and editions: https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/filecloud-site-maintenance/managing-filecloud-licenses/filecloud-license-purchase-and-renewal

- Software end-user license agreement: https://www.filecloud.com/eula/

- FileCloud Apache HTTP Server security advisory: https://docs.filecloud.com/fcdoc/latest/server/security-advisories/2026-security-advisories/filecloud-release-23-263-security-advisories/advisory-2026-11-02-apache-http-server-remote-code-execution-cve-2026-119618

- FileCloud MongoDB replica-set security advisory: https://docs.filecloud.com/fcdoc/latest/server/security-advisories/2026-security-advisories/filecloud-release-23-263-security-advisories/advisory-2026-11-03-mongodb-replica-set-remote-code-execution-cve-2026-118383

### Licensing sources

- https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/filecloud-site-maintenance/managing-filecloud-licenses/filecloud-license-purchase-and-renewal

- https://www.filecloud.com/eula/

### Infrastructure sources

- https://www.filecloud.com/vdr/

- https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/about-filecloud-for-administrators/requirements


### 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 Server administrator guide documents SAML 2.0 web SSO. It records upgrade-specific SimpleSAML configuration changes; configure the customer identity provider and deployment keys rather than assuming hosted-service settings apply. Scope: FileCloud Server web authentication; specific commercial entitlement must be confirmed. Source: https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/filecloud-site-setup/user-authentication-settings/single-sign-on-sso/saml-single-sign-on-support (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Edition-dependent. The vendor VDR deployment page explicitly includes air-gapped environments and FileCloud Server. This establishes an offered deployment option, not proof that every integration, license activation or update workflow works offline. Scope: Vendor-described FileCloud Server/VDR option; agree the offline implementation scope. Source: https://www.filecloud.com/vdr/ (reviewed 2026-11-14).

- Deployment artifact / IaC: Documented. The vendor installation index provides supported Linux/Windows installation and cloud deployment paths. Select a release-compatible package, operating system/database and licence, then configure TLS, persistent storage, backups and updates; application installation is separate from a complete HA design. Scope: FileCloud Server supported installation paths; platform prerequisites and HA separate. Source: https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/installing-filecloud-server/installation (reviewed 2026-11-21). Deployment artifact: https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/installing-filecloud-server/installation. Artifact reference: Current vendor installation index reviewed on this date.

- Minimum footprint / sizing: Documented. The sizing model publishes a 3,000-user/API-rate HA example using roughly three 8-vCPU/32-GB web nodes, a load balancer and a three-node MongoDB replica set with separate resources. Its older m4-instance references and usage assumptions are illustrative, not a current 100-user minimum; check AVX/runtime support and size storage, sync devices and backups. Scope: FileCloud Server documented workload/HA example; not a modern instance quote or universal minimum. Source: https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/about-filecloud-for-administrators/filecloud-sizing-guide (reviewed 2026-11-21).

- License pricing: Documented. The vendor describes Server licence purchase/renewal through its portal, plan selection, licensed site and user-seat additions, with support options and quotes. Select the self-hosted Server entitlement rather than assuming FileCloud Online hosting terms; retain the applicable EULA and renewal order. Scope: FileCloud Server commercial site/user licensing and renewal process. Source: https://docs.filecloud.com/fcdoc/latest/server/filecloud-administrator-guide/filecloud-site-maintenance/managing-filecloud-licenses/filecloud-license-purchase-and-renewal (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## GitLab Self-Managed

Source control and CI/CD on infrastructure you operate.

- Listing: https://launchinyourcloud.com/directory/gitlab/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp, oci, alibaba
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Free and paid tiers
- Licensing model: open-source
- Installation: Linux package, container or Helm chart
- Architecture: Customer-operated application and storage
- Operations: Your team operates, upgrades and backs up the installation.
- Product website: https://about.gitlab.com/
- Source review: 2026-11-20; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-17

### Scope and qualifications

GitLab documents AWS, Azure and Google Cloud installations. Oracle and Alibaba Cloud also publish deployment guides. These are documented deployment paths, not a promise of identical support or feature availability. Check operating system, edition and region requirements. GitLab 19.5.4, 19.4.6, and 19.3.8 patch critical CVE-2026-105437 in the bundled Git. Affected self-managed versions are 16.2 through versions before 19.3.8, 19.4 before 19.4.6, and 19.5 before 19.5.4. Upgrade immediately. Self-compiled deployments must also rebuild the Git binaries embedded in Gitaly and the Git installation referenced by git.bin_path, or use a distribution-patched Git 2.56.1 or later. GitLab 19.5.6, 19.4.8, and 19.3.9 address a high-severity cross-site scripting issue plus CI/CD and workspace authorization flaws. On November 20, GitLab issued CE/EE patches 19.6.1, 19.5.8, and 19.4.10 for CVE-2026-132825 and related Ruby flaws. GitLab recommends upgrading affected self-managed installations immediately. Official Linux packages and container images include patched Ruby. Source builds must rebuild the Ruby used by GitLab with 3.3.14 or 3.4.13, or a later patch in the same minor series.

Community Edition uses MIT terms; Enterprise Edition adds components under a more restrictive commercial license.

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.


### Category fit

- devops: Source control and CI/CD on infrastructure you operate.

### Deployment boundaries


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

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.gitlab.com/install/cloud_providers/ (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.gitlab.com/install/cloud_providers/ (checked 2026-11-12). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.oracle.com/cd/G26828_02/books/DeploySCM/c-installing-gitlab.html (checked 2026-11-12). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.alibabacloud.com/help/en/ecs/user-guide/deploy-and-use-gitlab (checked 2026-11-12). 


### Cloud deployment evidence

- GitLab Self-Managed cloud installation guides (aws, azure, gcp): https://docs.gitlab.com/install/cloud_providers/
  The upstream installation index links full GitLab Self-Managed deployment on AWS, Azure and Google Cloud. Choose the Linux package, chart or reference architecture appropriate to the selected edition, scale and supported release; a GitLab Runner alone is not the GitLab application.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- GitLab Community Edition on Alibaba Cloud ECS (alibaba): https://www.alibabacloud.com/help/en/ecs/user-guide/deploy-and-use-gitlab
  Alibaba documents GitLab Community Edition Docker deployment on Alibaba Cloud Linux 3 ECS as well as older package-based examples. Use the Community Edition path for this listing; JiHu GitLab is a separately distributed edition and old CentOS examples are not a current production recommendation.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.

- Oracle GitLab application deployment in an OCI tenancy (oci): https://docs.oracle.com/cd/G26828_02/books/DeploySCM/c-installing-gitlab.html
  Oracle explicitly documents the GitLab application VM, customer tenancy, region, compartment, compute and VCN configuration, and administrator login. This confirms the provider deployment model. Its linked quick-start architecture has been retired, so these instructions do not establish a currently maintained one-click stack; validate the installer and supported GitLab release before using the legacy automation.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- GitLab cloud installation: https://docs.gitlab.com/install/cloud_providers/

- Alibaba Cloud deployment: https://www.alibabacloud.com/help/en/ecs/user-guide/deploy-and-use-gitlab

- Licensing and edition terms: https://docs.gitlab.com/development/licensing/

- Oracle GitLab application deployment in an OCI tenancy: https://docs.oracle.com/cd/G26828_02/books/DeploySCM/c-installing-gitlab.html

- GitLab critical patch release for CVE-2026-105437: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-4-released/

- GitLab 19.5.6 security patch release: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-6-released/

- GitLab 19.6.1 critical Ruby patch announcement: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-6-1-released/?nav=19.6.1

- Upstream Ruby security advisory: https://www.ruby-lang.org/en/news/2026/11/18/multiple-vulnerabilities-in-regexp-and-string/

### Licensing sources

- https://docs.gitlab.com/development/licensing/

### Infrastructure sources

- https://docs.gitlab.com/install/cloud_providers/

- https://www.alibabacloud.com/help/en/ecs/user-guide/deploy-and-use-gitlab

- https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-4-released/


### Buyer diligence


Research coverage: 10/12 fields (83%); 10 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: Edition-dependent. GitLab documents AWS Marketplace self-service/private offers and Google Cloud Marketplace private offers for paid subscriptions. Delivery/billing does not by itself change where a selected GitLab installation runs. Scope: Premium/Ultimate subscription procurement; self-hosting and SaaS offers must be distinguished. Source: https://about.gitlab.com/cloud-partner-marketplaces/ (reviewed 2026-11-14).

- Cloud commitment eligibility: Edition-dependent. GitLab states eligible cloud-marketplace purchases can count toward committed spend on AWS or Google Cloud. Confirm the specific offer, billing account and buyer agreement; this is not an unconditional credit guarantee. Scope: Vendor procurement statement; actual provider commitment terms govern eligibility. Source: https://about.gitlab.com/cloud-partner-marketplaces/ (reviewed 2026-11-14).

- Single sign-on: Documented. Instance-wide SAML SSO is documented for Self-Managed Free, Premium and Ultimate. Group SAML and advanced group mapping have separate tier requirements. Scope: GitLab Self-Managed instance authentication; not GitLab.com group SSO. Source: https://docs.gitlab.com/integration/saml/ (reviewed 2026-11-14).

- SCIM provisioning: Edition-dependent. SCIM is documented for Self-Managed Premium and Ultimate, with SAML configured. The API implements part of RFC7644; verify the supported identity provider and operations. Scope: GitLab Self-Managed / Dedicated, Premium and Ultimate. Source: https://docs.gitlab.com/administration/settings/scim_setup/ (reviewed 2026-11-14).

- Compliance attestations: Not researched.

- Security controls: Documented. On November 20, GitLab issued CE/EE patches 19.6.1, 19.5.8, and 19.4.10 for CVE-2026-132825 and related Ruby flaws. GitLab recommends upgrading affected self-managed installations immediately. Official Linux packages and container images include patched Ruby. Source builds must rebuild the Ruby used by GitLab with 3.3.14 or 3.4.13, or a later patch in the same minor series. Scope: GitLab Self-Managed CE/EE, including Linux packages, containers and self-compiled installations. The separate bundled Git fix has its own requirements.. Source: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-6-1-released/?nav=19.6.1 (reviewed 2026-11-20). Supporting source: Upstream Ruby security advisory — https://www.ruby-lang.org/en/news/2026/11/18/multiple-vulnerabilities-in-regexp-and-string/.

- Air-gapped operation: Edition-dependent. Self-Managed Free, Premium and Ultimate have an offline installation workflow. Transfer the correct packages/images and handle scanners, AI and update dependencies separately. Scope: Documented offline Self-Managed configuration, not default online installation. Source: https://docs.gitlab.com/topics/offline/ (reviewed 2026-11-14).

- Deployment artifact / IaC: Documented. The official self-managed guide publishes Compose YAML for versioned Community or Enterprise images with persistent configuration, logs and data. It warns against placing the all-in-one Docker image in Kubernetes; use the Helm chart/operator there. Configure hostname, TLS, secrets, backups and runner capacity separately. Scope: Official self-managed Docker/Compose installation. Source: https://docs.gitlab.com/install/docker/installation/ (reviewed 2026-11-20). Deployment artifact: https://docs.gitlab.com/install/docker/installation/#install-gitlab-by-using-docker-compose. Artifact reference: Select explicit version-ce.0 or version-ee.0 image tag.

- Minimum footprint / sizing: Documented. The single-node baseline is 8 vCPU and 16 GB RAM. A memory-constrained configuration can use at least 8 GB; distributed sizing is component- and workload-specific. Scope: Self-Managed single-node baseline; not a total production cost estimate. Source: https://docs.gitlab.com/install/requirements/ (reviewed 2026-11-14).

- License pricing: Documented. GitLab Self-Managed offers tier-based subscriptions applying to the whole instance; all instance users share the selected features. A GitLab.com subscription cannot be transferred to Self-Managed. Select the required tier, seats and add-ons; this does not establish a complete hosting/support cost. Scope: GitLab Self-Managed instance-wide commercial tiers. Source: https://docs.gitlab.com/subscriptions/choosing_subscription/ (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. GitLab published 19.6.1 on November 20, 2026, with parallel Ruby security patches 19.5.8 and 19.4.10. Scope: GitLab Self-Managed Community and Enterprise editions. Source: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-6-1-released/?nav=19.6.1 (reviewed 2026-11-20).




### Security and lifecycle reviews

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

- GitLab bundled Git command-execution advisory (security-advisory): CVE-2026-105437 concerns a Git heap-write flaw that can reach command execution inside Gitaly. Scope: GitLab CE/EE 16.2 to before 19.3.8, 19.4 to before 19.4.6, and 19.5 to before 19.5.4. Conditions: All installation types are covered unless the vendor identifies an exception. Source builds need both Gitaly-embedded Git and git.bin_path checked. Action: Install the patched release for the deployed branch. Rebuild the required Git binaries for source installations, or use a distribution fix for the CVE. Source: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-4-released/; reviewed 2026-11-17.

- GitLab 19.5.6 security update (security-advisory): GitLab 19.5.6, 19.4.8, and 19.3.9 fix a high-severity cross-site scripting issue and authorization weaknesses in CI/CD and workspaces. Scope: GitLab CE/EE patch lines 19.3, 19.4, and 19.5; consult the vendor table for the affected versions. Conditions: Impact depends on enabled features, user roles, and exposed endpoints. This record does not replace the separate bundled-Git CVE review. Action: Upgrade to 19.5.6, 19.4.8, or 19.3.9 for the deployed branch, or a later supported patch. Source: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-6-released/; reviewed 2026-11-18.

- GitLab critical bundled Ruby security update (security-advisory): GitLab updated bundled Ruby for CVE-2026-132825 and related upstream Ruby security issues. Scope: Self-managed GitLab CE/EE releases before 19.4.10, 19.5 releases before 19.5.8, and 19.6 releases before 19.6.1, per GitLab. Conditions: Official Linux packages and container images carry the fixed Ruby. Self-compiled installations manage Ruby separately. Action: Upgrade to 19.6.1, 19.5.8, or 19.4.10 as appropriate. For source builds, rebuild GitLab’s Ruby with 3.3.14, 3.4.13, or a later patch in the same minor series. Source: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-6-1-released/?nav=19.6.1; reviewed 2026-11-20. Supporting source: Upstream Ruby security advisory — https://www.ruby-lang.org/en/news/2026/11/18/multiple-vulnerabilities-in-regexp-and-string/.




## JetBrains YouTrack Server

Customer-hosted project and issue management application from JetBrains.

- Listing: https://launchinyourcloud.com/directory/youtrack-server/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Proprietary YouTrack Server subscription; a limited free-user tier is available
- Licensing model: commercial-only
- Installation: Official YouTrack Docker image and Server installation documentation
- Architecture: Persistent Docker server deployment with mounted application data, configuration, logs and backup directories.
- Operations: Customer manages Docker/server resources, persistent data, backups, TLS/network configuration and upgrades.
- Product website: https://www.jetbrains.com/youtrack/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This entry selects YouTrack Server. Free user allowances do not make the application open source, and each installation requires its own license. Review optional integrations and AI services separately from the self-hosted project-tracking deployment.

YouTrack Server is proprietary subscription software, including when used within its free-user allowance. The Server agreement and selected plan determine install rights, updates and user/agent entitlements.

Persistent Docker server deployment with mounted application data, configuration, logs and backup directories.


### Category fit

- project-management: Task and issue tracking with Scrum/Kanban boards, planning and progress reporting for project teams.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.jetbrains.com/help/youtrack/server/deploy-youtrack-kubernetes.html (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.jetbrains.com/help/youtrack/server/deploy-youtrack-kubernetes.html (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.jetbrains.com/help/youtrack/server/deploy-youtrack-kubernetes.html (checked 2026-11-12). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.jetbrains.com/help/youtrack/server/deploy-youtrack-kubernetes.html (checked 2026-11-12). 


### Cloud deployment evidence

- YouTrack Server Kubernetes deployment on named cloud services (aws, azure, gcp, oci): https://www.jetbrains.com/help/youtrack/server/deploy-youtrack-kubernetes.html
  JetBrains names Amazon EKS, Azure Kubernetes Service, Oracle Container Engine for Kubernetes and Google Kubernetes Engine for YouTrack Server, with a worked GKE deployment. The instructions deploy a single YouTrack node with persistent volumes; multi-node application installations are not supported. Check the current image, license, storage and backup requirements rather than treating Kubernetes as application clustering.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Official server installation and updates: https://www.jetbrains.com/help/youtrack/server/installation-and-upgrade.html

- Docker deployment and persistent directories: https://www.jetbrains.com/help/youtrack/server/youtrack-docker-installation.html

- Project-management functionality: https://www.jetbrains.com/youtrack/features/agile_project_management.html

- Server software subscription agreement: https://www.jetbrains.com/legal/docs/youtrack/subscription/

- Server/free-tier license scope: https://www.jetbrains.com/youtrack/buy/?section=server&with-helpdesk=true

### Licensing sources

- https://www.jetbrains.com/legal/docs/youtrack/subscription/

- https://www.jetbrains.com/youtrack/buy/?section=server&with-helpdesk=true

### Infrastructure sources

- https://www.jetbrains.com/help/youtrack/server/installation-and-upgrade.html

- https://www.jetbrains.com/help/youtrack/server/youtrack-docker-installation.html


### 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 Server SAML 2.0 module configures YouTrack as a service provider for an external identity provider. Configure metadata, certificate trust and callback URLs; login-time user/group updates differ from separately configured SCIM provisioning. Scope: YouTrack Server 2026.2 user authentication, not a Cloud-only claim. Source: https://www.jetbrains.com/help/youtrack/server/saml-authentication-module.html (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. JetBrains distributes YouTrack Server as an official Docker image for evaluation and production. Configure persistent data/conf/log/backup directories and use a selected versioned image. Scope: YouTrack Server 2026.2 installation guide. Source: https://www.jetbrains.com/help/youtrack/server/youtrack-docker-installation.html (reviewed 2026-11-14). Deployment artifact: https://hub.docker.com/r/jetbrains/youtrack. Artifact reference: versioned image tag must be selected.

- Minimum footprint / sizing: Documented. The Server 2026.2 guide states 1.5 GB minimum RAM with JVM minimums of 1,024 MB heap and 250 MB Metaspace. Storage guidance is roughly 1 GB per 5,000 issues before attachment variation. Database growth and transactions drive sizing; this is not a 1-TB HA topology. Scope: Upstream Server sizing guidelines; issue and attachment workload are material. Source: https://www.jetbrains.com/help/youtrack/server/youtrack-supported-environments.html (reviewed 2026-11-20).

- License pricing: Documented. The current Server license guide grants free use for up to ten users and three helpdesk agents. New commercial purchases from June 23, 2026 use annual user-pack subscriptions; earlier perpetual licenses have different terms. Each installation needs its own license; confirm the current pack price and renewal terms. Scope: Current Server licensing; historical perpetual-license and Cloud pricing are separate. Source: https://www.jetbrains.com/help/youtrack/server/manage-youtrack-server-license.html (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Joomla!

Customer-operated content management and website publishing platform.

- Listing: https://launchinyourcloud.com/directory/joomla/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: oci, digitalocean, linode, vultr, northflank
- 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: Application platform deployment
- Architecture: Joomla web application, database, web server and persistent site assets.
- 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://www.joomla.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The Oracle architecture, provider marketplace packages and Northflank recipe are separate paths. Joomla stable versions, release candidates and extension releases must be distinguished.

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

Joomla web application, database, web server and persistent site assets. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- content-management: Customer-operated content management and website publishing platform.

### Deployment boundaries


- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.oracle.com/en/solutions/joomla-with-mds/ (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://marketplace.digitalocean.com/apps/openlitespeed-joomla (checked 2026-11-19). 

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

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.vultr.com/how-to-use-vultrs-joomla-marketplace-application (checked 2026-11-19). 

- northflank: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://northflank.com/guides/deploy-joomla-on-northflank (checked 2026-11-19). 


### Cloud deployment evidence

- OCI Architecture (oci): https://docs.oracle.com/en/solutions/joomla-with-mds/
  Joomla web application, database, web server and persistent site assets. The Oracle architecture, provider marketplace packages and Northflank recipe are separate paths. Joomla stable versions, release candidates and extension releases must be distinguished.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- DO Marketplace (digitalocean): https://marketplace.digitalocean.com/apps/openlitespeed-joomla
  Joomla web application, database, web server and persistent site assets. The Oracle architecture, provider marketplace packages and Northflank recipe are separate paths. Joomla stable versions, release candidates and extension releases must be distinguished.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.

- Akamai Quick Deploy (linode): https://techdocs.akamai.com/quick-deploy-apps/docs/joomla
  Joomla web application, database, web server and persistent site assets. The Oracle architecture, provider marketplace packages and Northflank recipe are separate paths. Joomla stable versions, release candidates and extension releases must be distinguished.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Vultr Docs (vultr): https://docs.vultr.com/how-to-use-vultrs-joomla-marketplace-application
  Joomla web application, database, web server and persistent site assets. The Oracle architecture, provider marketplace packages and Northflank recipe are separate paths. Joomla stable versions, release candidates and extension releases must be distinguished.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.

- Northflank Guide (northflank): https://northflank.com/guides/deploy-joomla-on-northflank
  Joomla web application, database, web server and persistent site assets. The Oracle architecture, provider marketplace packages and Northflank recipe are separate paths. Joomla stable versions, release candidates and extension releases must be distinguished.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes brianteeman, wilsonge, infograf768, 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/joomla/joomla-cms/graphs/contributors

- Upstream project: https://github.com/joomla/joomla-cms

### Sources

- OCI Architecture: https://docs.oracle.com/en/solutions/joomla-with-mds/

- DO Marketplace: https://marketplace.digitalocean.com/apps/openlitespeed-joomla

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

- Vultr Docs: https://docs.vultr.com/how-to-use-vultrs-joomla-marketplace-application

- Northflank Guide: https://northflank.com/guides/deploy-joomla-on-northflank

- GPL-2.0 LICENSE.txt: https://github.com/joomla/joomla-cms/blob/6.2-dev/LICENSE.txt

- Releases v6.2.1-rc1: https://github.com/joomla/joomla-cms/releases

### Licensing sources

- https://github.com/joomla/joomla-cms/blob/6.2-dev/LICENSE.txt

### Infrastructure sources

- https://docs.oracle.com/en/solutions/joomla-with-mds/

- https://marketplace.digitalocean.com/apps/openlitespeed-joomla

- https://techdocs.akamai.com/quick-deploy-apps/docs/joomla

- https://docs.vultr.com/how-to-use-vultrs-joomla-marketplace-application

- https://northflank.com/guides/deploy-joomla-on-northflank


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. miniOrange publishes a SAML service-provider extension and explicitly states Joomla 3/4/5/6 compatibility. This is a third-party extension with its own plan and support terms, not an included Joomla-core feature; validate the exact site version, provider and purchased plugin capabilities. Scope: Extension vendor documentation for Joomla 6-compatible SAML; not upstream Joomla support. Source: https://plugins.miniorange.com/joomla-single-sign-on-sso (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Akamai documents deploying its Joomla Quick Deploy application through Cloud Manager, API, CLI or Terraform using StackScript 985372. This is a provider-maintained package/recipe; verify the installed Joomla version and upgrade path separately from the upstream release. Scope: Akamai/Linode Joomla application deployment recipe; not a Joomla upstream HA template. Source: https://techdocs.akamai.com/quick-deploy-apps/docs/joomla (reviewed 2026-11-20). Deployment artifact: https://techdocs.akamai.com/quick-deploy-apps/docs/joomla. Artifact reference: Current provider StackScript 985372 examples; package/application versions can differ.

- Minimum footprint / sizing: Sources checked — unresolved. The current Joomla 6.x technical requirements recommend a PHP memory limit of at least 256 MB and specify supported PHP, database and web-server versions. That limit is per PHP process, not a VM/RAM or HA capacity floor; whole-deployment sizing remains unconfirmed. Scope: Joomla 6.x software requirements; no complete host footprint established. Source: https://manual.joomla.org/docs/next/get-started/technical-requirements/ (reviewed 2026-11-20).

- License pricing: Documented. GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Joomla!; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/joomla/joomla-cms/blob/6.2-dev/LICENSE.txt (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## Mattermost Self-Hosted

Self-hosted team messaging and collaborative operational workflows on customer infrastructure.

- Listing: https://launchinyourcloud.com/directory/mattermost/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure, oci, aws, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT Team Edition; commercial Enterprise offerings and separately licensed components; inspect the selected edition
- Licensing model: open-source
- Installation: Linux binary/packages or Mattermost Kubernetes Operator; provider architectures and Azure/OCI Marketplace guides
- Architecture: Customer-operated application with PostgreSQL and file/object storage
- Operations: Customer maintains the deployment, database, storage, upgrades and availability; subscriptions govern supported enterprise capabilities.
- Product website: https://mattermost.com/
- Source review: 2026-11-17; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-17

### Scope and qualifications

Team Edition is intended for small teams and lacks the commercial governance and enterprise identity capabilities. Enterprise Entry has limits; paid features require the applicable subscription. The current Docker Compose guide is for evaluation/testing and is not recommended for production/HA. The vendor provides AWS and Google Cloud self-hosted architectures alongside Azure VM and OCI OKE deployment guides. Mattermost 12.0.2 and the November 5 patches for maintained 11.x branches contain medium-to-high severity security fixes. For v12 upgrades, verify community and custom plugin compatibility.

The listed self-hosted family includes MIT Team Edition and commercial Enterprise offerings with proprietary capabilities and feature entitlements. The license of a public core, community build or plugin must not be applied to the complete Enterprise distribution.

Production documentation uses persistent Linux application hosts or Kubernetes, PostgreSQL and file storage. Azure provisions a VM scale set; the OCI option provisions OKE and managed database/storage components. Mattermost 12 drops RHEL 7 and 8, requires glibc 2.34 or later, PostgreSQL 15 or later, and OpenSearch 2.x or later.


Cloud evidence scope: Official customer-subscription Azure VM and customer-tenancy Oracle OKE guides establish these paths; unreviewed provider badges are omitted.

### Category fit

- collaboration: Team channels, messaging, file sharing and collaborative operational workflows; production scale, identity and governance capabilities depend on edition.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.mattermost.com/deployment-guide/server/linux/deploy-azure-native-vm (checked 2026-11-12). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.mattermost.com/deployment-guide/server/kubernetes/deploy-k8s-oke (checked 2026-11-12). 

- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.mattermost.com/deployment-guide/deployment-architecture (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.mattermost.com/deployment-guide/deployment-architecture (checked 2026-11-12). 


### Cloud deployment evidence

- Mattermost customer cloud deployment on Azure (azure): https://docs.mattermost.com/deployment-guide/server/linux/deploy-azure-native-vm
  The vendor documents the full Mattermost application in the customer Azure subscription or OCI tenancy. The OKE Marketplace option uses Enterprise Edition; Kubernetes/Operator and enterprise features require their applicable plan, separate from Team Edition and the evaluation-only Compose example.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Mattermost customer cloud deployment on Oracle Cloud (oci): https://docs.mattermost.com/deployment-guide/server/kubernetes/deploy-k8s-oke
  The vendor documents the full Mattermost application in the customer Azure subscription or OCI tenancy. The OKE Marketplace option uses Enterprise Edition; Kubernetes/Operator and enterprise features require their applicable plan, separate from Team Edition and the evaluation-only Compose example.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Mattermost self-hosted provider architecture and sizing (aws, gcp): https://docs.mattermost.com/deployment-guide/deployment-architecture
  The vendor architecture builder explicitly includes AWS and Google Cloud hosting for the self-hosted application, with separate VM and Kubernetes deployment options and linked installation instructions. These are application hosting architectures, not Mattermost Cloud residency or storage adapters. Provider SKU suggestions are illustrative; size and validate the selected deployment and edition.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Editions and feature restrictions: https://docs.mattermost.com/product-overview/editions-and-offerings

- Business and licensing: https://docs.mattermost.com/product-overview/faq-license

- Linux deployment: https://docs.mattermost.com/deployment-guide/server/deploy-linux

- Kubernetes deployment: https://docs.mattermost.com/deployment-guide/server/deploy-kubernetes

- Container deployment caveats: https://docs.mattermost.com/deployment-guide/server/deploy-containers

- Azure Native VM deployment: https://docs.mattermost.com/deployment-guide/server/linux/deploy-azure-native-vm

- Oracle OKE deployment: https://docs.mattermost.com/deployment-guide/server/kubernetes/deploy-k8s-oke

- Licensing and edition terms: https://docs.mattermost.com/developers/integrate/plugins/source-available-license

- Mattermost self-hosted provider architecture and sizing: https://docs.mattermost.com/deployment-guide/deployment-architecture

- Mattermost v12 security and upgrade changelog: https://docs.mattermost.com/product-overview/mattermost-v12-changelog

### Licensing sources

- https://docs.mattermost.com/product-overview/editions-and-offerings

- https://docs.mattermost.com/product-overview/faq-license

- https://docs.mattermost.com/developers/integrate/plugins/source-available-license

### Infrastructure sources

- https://docs.mattermost.com/deployment-guide/server/deploy-linux

- https://docs.mattermost.com/deployment-guide/server/deploy-kubernetes

- https://docs.mattermost.com/product-overview/mattermost-v12-changelog


### 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 current SAML documentation lists Entry, Professional, Enterprise and Enterprise Advanced. It distinguishes tested Okta, OneLogin and ADFS integrations from custom identity providers that require validation. Scope: Current Mattermost commercial distribution plan names; not a blanket Team Edition entitlement. Source: https://docs.mattermost.com/onboard/sso-saml (reviewed 2026-11-14).

- SCIM provisioning: Explicitly unsupported. The SAML provisioning FAQ explicitly states SCIM is not supported and refers administrators to AD/LDAP for provisioning/deactivation. This is a documented limitation, rather than an unanswered field. Scope: Current SAML user-lifecycle documentation; recheck for the selected release. Source: https://docs.mattermost.com/administration-guide/onboard/sso-saml-entraid (reviewed 2026-11-14).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official container guide uses the mattermost/docker Compose repository with application and PostgreSQL containers and an optional NGINX proxy. Configure secrets, persistent paths, domain and TLS; the quick-start Compose stack is not automatically a clustered production deployment. Scope: Self-managed Docker deployment; HA architecture is a separate design. Source: https://docs.mattermost.com/deployment-guide/server/deploy-containers.html (reviewed 2026-11-20). Deployment artifact: https://github.com/mattermost/docker. Artifact reference: Moving deployment repository; pin supported server and PostgreSQL versions.

- Minimum footprint / sizing: Documented. The upstream traditional-deployment guide gives a small-team baseline of 1 vCPU and 2 GB RAM for 1–1,000 registered users. Activity, peak file sharing, database/storage and multi-server HA alter sizing; this is not a complete 1-TB HA design. Scope: Upstream small/medium single-server baseline; enterprise multi-server sizing is separate. Source: https://docs.mattermost.com/deployment-guide/software-hardware-requirements.html (reviewed 2026-11-20).

- License pricing: Documented. The current offerings guide distinguishes commercial self-hosted Enterprise Edition from its free Entry mode and paid subscriptions. Entry has server-wide feature/usage limits; advanced entitlements require a trial or subscription. Exact paid-plan pricing and infrastructure costs remain separate. Scope: Current self-hosted Entry/Enterprise offerings; do not reuse historical Team Edition or SaaS pricing. Source: https://docs.mattermost.com/product-overview/editions-and-offerings.html (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.




### Security and lifecycle reviews

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

- Mattermost maintained-line security review (security-advisory): The v12 changelog records medium/high security fixes and important runtime and plugin compatibility changes. Scope: Mattermost 12.0.2 and the maintained 11.x patches identified in the November 5 security notice. Conditions: Individual vulnerability details follow the vendor disclosure schedule; plugins, PostgreSQL and optional search integrations have separate compatibility requirements. Action: Use the appropriate maintained-line patch. For v12, review plugin compatibility, glibc 2.34+, PostgreSQL 15+ and OpenSearch 2.x+ where used. Source: https://docs.mattermost.com/product-overview/mattermost-v12-changelog; reviewed 2026-11-17.




## NetBird Self-Hosted Community Edition

Open-source zero-trust networking control plane self-hosted on a customer cloud VM.

- Listing: https://launchinyourcloud.com/directory/netbird-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean, hetzner, oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Mixed open-source terms: BSD-3-Clause generally and AGPL-3.0 for server control-plane directories; Enterprise features require a commercial license.
- Licensing model: open-source
- Installation: Official self-hosting script and Docker Compose on a Linux VM; advanced deployment supports a custom identity provider
- Architecture: Customer-operated management, signal, relay or STUN, dashboard, identity and state services; peers form direct WireGuard tunnels where possible
- Operations: Customer manages the VM, domain, TLS, firewall ports, identity configuration, control-plane state, relay capacity, backups, upgrades and availability.
- Product website: https://netbird.io/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

This entry covers the Community self-hosted edition, not NetBird Cloud or the Enterprise Commercial License. The quickstart is single-node; high availability and commercial SCIM or traffic-flow features are outside this edition. The cited advanced guide also establishes DigitalOcean, Hetzner and OCI paths. Its multi-container configuration differs from the combined-server quickstart; preserve version and migration boundaries. The pinned quickstart script still uses latest for several images, which must be locked separately.

Community code is open source but mixed-licensed: most repository code is BSD-3-Clause, while server control-plane directories are AGPL-3.0. Enterprise-licensed features are excluded.

The quickstart deploys the full control plane as persistent containers on a customer-operated Linux VM.


### Category fit

- identity-access-management: Provides self-hosted identity-aware zero-trust network access with users, policies, device peers, routes and private-resource controls.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (checked 2026-11-19). 

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (checked 2026-11-19). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (checked 2026-11-19). 


### Cloud deployment evidence

- NetBird self-hosted control plane on a cloud VM (aws, azure, gcp, digitalocean, hetzner, oci): https://docs.netbird.io/selfhosted/selfhosted-guide
  The advanced self-hosting guide explicitly names AWS, DigitalOcean, Hetzner, Google Cloud and Azure VMs, uses Hetzner for its worked installation and documents OCI guest-firewall requirements for UDP 3478. It describes the older multi-container layout; the current quickstart uses the combined netbird-server layout. Select compatible files and configure provider and guest firewalls for the chosen architecture.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed. Edition: Community Edition.


### Community and maintenance

The reviewed upstream contributor history includes mlsmaycon, pascal-fischer, lixmal, with sustained contributions alongside the dated application release and public installation history. This establishes maintained community participation, not a commercial support, compliance or capacity guarantee.

Reviewed 2026-11-19.

- Upstream contributor history: https://github.com/netbirdio/netbird/graphs/contributors

- Reviewed upstream application release: https://github.com/netbirdio/netbird/releases/tag/v0.83.1

### Sources

- NetBird self-hosting quickstart: https://docs.netbird.io/selfhosted/selfhosted-quickstart

- NetBird advanced self-hosting guide: https://docs.netbird.io/selfhosted/selfhosted-guide

- NetBird repository license: https://github.com/netbirdio/netbird/blob/main/LICENSE

- NetBird Enterprise edition boundary: https://docs.netbird.io/selfhosted/enterprise

- Reviewed deployment artifact reference: https://github.com/netbirdio/netbird/releases/download/v0.83.1/getting-started.sh

- Upstream release and published installer digest: https://github.com/netbirdio/netbird/releases/tag/v0.83.1

- Upstream contributor history: https://github.com/netbirdio/netbird/graphs/contributors

### Licensing sources

- https://github.com/netbirdio/netbird/blob/main/LICENSE

- https://docs.netbird.io/selfhosted/enterprise

### Infrastructure sources

- https://docs.netbird.io/selfhosted/selfhosted-quickstart

- https://docs.netbird.io/selfhosted/selfhosted-guide


### Buyer diligence


Research coverage: 12/12 fields (100%); 7 documented, 5 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. The reviewed deployment and licensing sources did not establish a public cloud-marketplace offer that unambiguously entitles the selected self-hosted edition. Obtain the exact offer ID, seller, delivery artifact and edition terms before treating marketplace procurement as available. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (reviewed 2026-11-19).

- Cloud commitment eligibility: Sources checked — unresolved. Customer-cloud deployment or marketplace delivery does not by itself establish cloud-spend commitment eligibility. Confirm the exact offer, billed dimensions, private-offer terms and buyer agreement. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (reviewed 2026-11-19).

- Single sign-on: Documented. The advanced Community self-hosting guide supports a custom OpenID Connect identity provider and names self-hosted and managed IdP options. Enterprise-only identity lifecycle features are separate. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (reviewed 2026-11-19).

- SCIM provisioning: Explicitly unsupported. NetBird's edition comparison places SCIM user and group provisioning in the Enterprise Commercial License, not Community Edition. Treat SCIM as unavailable for this selected Community listing. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/enterprise (reviewed 2026-11-19).

- Compliance attestations: Sources checked — unresolved. The reviewed product and deployment sources did not establish an independent compliance attestation whose assessed scope covers this customer-operated edition and its local infrastructure. Obtain the current report and map customer responsibilities. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-quickstart (reviewed 2026-11-19).

- Security controls: Edition-dependent. The self-hosted control plane supports OIDC identity, policy-controlled peer access and customer-managed TLS, firewall and state. Community Edition excludes Enterprise SCIM, traffic-flow logging and active-active HA; secure relay, backup and upgrade operations remain customer responsibilities. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (reviewed 2026-11-19). Supporting source: Community and Enterprise capability boundary — https://docs.netbird.io/selfhosted/enterprise.

- Air-gapped operation: Sources checked — unresolved. The reviewed sources did not establish a fully disconnected installation, update and license workflow for this selected edition. Identify required registries, package repositories, telemetry, identity, activation and support endpoints before claiming air-gapped operation. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (reviewed 2026-11-19).

- Deployment artifact / IaC: Documented. The v0.83.1 release publishes getting-started.sh with a verified SHA-256 digest. The script defaults several NetBird containers to latest, so pinning the script does not pin the complete deployment. Review and lock the generated Compose images and persistent state before production use. Scope: Community combined-server quickstart script; advanced multi-container configuration is separate. Source: https://docs.netbird.io/selfhosted/selfhosted-quickstart (reviewed 2026-11-19). Deployment artifact: https://github.com/netbirdio/netbird/releases/download/v0.83.1/getting-started.sh. Artifact reference: v0.83.1/getting-started.sh; sha256:25ee5000a7421cb51a7c4c0f9090788951f531aba171d1fbff676f66d3265bfe. Supporting source: Upstream release and published installer digest — https://github.com/netbirdio/netbird/releases/tag/v0.83.1.

- Minimum footprint / sizing: Documented. The quickstart specifies one publicly reachable Linux VM with at least 1 CPU and 2 GB RAM plus Docker Compose, a domain and required TCP/UDP ports. This is a small single-node baseline, not an HA or large-fleet sizing recommendation. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-quickstart (reviewed 2026-11-19).

- License pricing: Documented. The selected Community Edition is open source under mixed BSD-3-Clause and AGPL-3.0 terms and does not require the Enterprise license. Enterprise HA, SCIM and related capabilities are separately commercial. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://github.com/netbirdio/netbird/blob/main/LICENSE (reviewed 2026-11-19). Supporting source: Enterprise license boundary — https://docs.netbird.io/selfhosted/enterprise.

- Operating cost estimate: Sources checked — unresolved. No complete dated operating-cost estimate is established. Define provider and region, workload, availability, retention, storage growth, network transfer, support, software entitlement and operating labor before estimating total cost. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (reviewed 2026-11-19).

- Release snapshot / cadence: Documented. The reviewed upstream v0.83.1 release was published 2026-11-13. Provider images and installer/component packages can differ; this snapshot does not promise a support window or future cadence. Scope: NetBird Self-Hosted Community Edition upstream application, independently versioned from provider packages. Source: https://github.com/netbirdio/netbird/releases/tag/v0.83.1 (reviewed 2026-11-19).







## NVIDIA AI Enterprise

Commercial enterprise AI software suite deployed on customer cloud GPU instances or managed Kubernetes clusters.

- Listing: https://launchinyourcloud.com/directory/nvidia-ai-enterprise/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, oci, alibaba, tencent, volcano
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial NVIDIA AI Enterprise subscription, consumption or perpetual license; most customer-cloud paths require BYOL.
- Licensing model: commercial-only
- Installation: NVIDIA AI Enterprise or GPU-optimized cloud VM images, standard instances with BYOL, or managed Kubernetes on supported cloud providers
- Architecture: Licensed NVIDIA AI containers and infrastructure software on customer GPU virtual machines, managed Kubernetes clusters or marketplace OpenShift
- Operations: Customer manages cloud GPU instances or Kubernetes, drivers, GPU Operator and container runtime, networking, storage, identities, NGC access, model services, monitoring, upgrades and license activation.
- Product website: https://www.nvidia.com/en-us/data-center/products/ai-enterprise/
- Source review: 2026-11-18; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers customer-operated NVIDIA AI Enterprise software, not a managed AI service. A license is required and is not included with most standard, GPU-optimized VMI or managed-Kubernetes deployments; on-demand NVIDIA AI Enterprise VMIs and private offers use separate included-license processes. Not every component is available on every cloud or deployment model. GPU deployments are generally licensed per GPU, while CPU-only instances require an instance license. Tencent Cloud and ByteDance Volcano Engine have documented standard-instance BYOL paths. These guides require certified software and supported instance types; they do not establish that every GPU, component or provider image is eligible. Their per-instance wording differs from the general per-GPU licensing guidance, so confirm the applicable licensing unit. The November lifecycle matrix lists active 9.0/R620, 8.3/R595, and 7.9 LTSB/R580 branches with different end dates. NeMo Microservices support ended October 1, 2026, after 25.12 became the final GA release; select and patch each component branch independently.

NVIDIA AI Enterprise requires a commercial subscription, consumption or perpetual entitlement. Cloud instances are usually BYOL unless the selected on-demand VMI or private offer explicitly includes licensing. The Tencent and Volcano standard-instance guides state one license per cloud instance, while the general licensing guide describes per-GPU BYOL. Confirm the applicable unit for the selected instance, GPU count and agreement before purchase.

NVIDIA AI Enterprise runs licensed AI containers and infrastructure components on persistent customer GPU or CPU instances and Kubernetes worker nodes.


### Category fit

- ai-tools: Provides an enterprise-supported suite of AI frameworks, infrastructure software, operations components and development tools.

- ai-inference-gateways: Includes supported inference and model-serving components for deploying generative-AI and machine-learning workloads.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/overview.html (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/overview.html (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/overview.html (checked 2026-11-16). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/overview.html (checked 2026-11-16). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/overview.html (checked 2026-11-16). 

- tencent: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/tencent-standard-instance.html (checked 2026-11-16). 

- volcano: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/bytedance-volcano-engine-standard-instance.html (checked 2026-11-16). 


### Cloud deployment evidence

- NVIDIA AI Enterprise on AWS, Azure and Google Cloud (aws, azure, gcp): https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/overview.html
  NVIDIA documents standard instances, NVIDIA VM images, GPU-optimized VM images, managed Kubernetes and marketplace OpenShift paths across AWS, Azure and Google Cloud. License inclusion varies by image and offer; standard instances and managed Kubernetes generally require BYOL.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.

- NVIDIA AI Enterprise on Oracle Cloud and Alibaba Cloud (oci, alibaba): https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/overview.html
  NVIDIA's current cloud matrix includes standard instances on Oracle Cloud Infrastructure and Alibaba Cloud, NVIDIA AI Enterprise VM images on OCI and GPU-optimized VM images on Alibaba Cloud. Customers must confirm the supported component set, certified instance and license path.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.

- NVIDIA AI Enterprise on Tencent Cloud standard instances (tencent): https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/tencent-standard-instance.html
  NVIDIA documents installing its licensed stack on customer standard instances using a certified Ubuntu operating system, supported NVIDIA drivers, Docker and Container Toolkit, then pulling NGC containers. This is a BYOL installation rather than an included-license marketplace image. Select an instance from the supported-cloud-services matrix; the guide states one license per cloud instance, which must be reconciled with the general licensing guide and the customer agreement.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed. Edition: NVIDIA AI Enterprise standard-instance BYOL.

- NVIDIA AI Enterprise on ByteDance Volcano Engine standard instances (volcano): https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/bytedance-volcano-engine-standard-instance.html
  NVIDIA documents installing its licensed stack on customer standard instances using a certified Ubuntu operating system, supported NVIDIA drivers, Docker and Container Toolkit, then pulling NGC containers. This is a BYOL installation rather than an included-license marketplace image. Select an instance from the supported-cloud-services matrix; the guide states one license per cloud instance, which must be reconciled with the general licensing guide and the customer agreement.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed. Edition: NVIDIA AI Enterprise standard-instance BYOL.


### Sources

- NVIDIA AI Enterprise cloud deployment guide: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/index.html

- NVIDIA AI Enterprise cloud deployment overview: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/overview.html

- NVIDIA AI Enterprise on AWS: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/aws-overview.html

- NVIDIA AI Enterprise on Azure: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/azure-overview.html

- NVIDIA AI Enterprise on Google Cloud: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/google-overview.html

- NVIDIA AI Enterprise licensing: https://docs.nvidia.com/ai-enterprise/planning-resource/licensing-guide/latest/licensing.html

- NVIDIA AI Enterprise on Tencent Cloud standard instances: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/tencent-standard-instance.html

- NVIDIA AI Enterprise on ByteDance Volcano Engine standard instances: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/bytedance-volcano-engine-standard-instance.html

- NVIDIA AI Enterprise documentation: https://docs.nvidia.com/ai-enterprise/

- NVIDIA AI Enterprise lifecycle: https://docs.nvidia.com/ai-enterprise/lifecycle/latest/index.html

### Licensing sources

- https://docs.nvidia.com/ai-enterprise/planning-resource/licensing-guide/latest/licensing.html

- https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/tencent-standard-instance.html

- https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/bytedance-volcano-engine-standard-instance.html

### Infrastructure sources

- https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/overview.html

- https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/index.html

- https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/tencent-standard-instance.html

- https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/bytedance-volcano-engine-standard-instance.html


### Buyer diligence


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

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


- Marketplace delivery: Edition-dependent. The deployment matrix distinguishes license-included AI Enterprise VM images/private offers from BYOL paths. A generic GPU-optimized image or Kubernetes installation does not include AI Enterprise licensing merely because it comes from a cloud provider. Scope: Offer-specific licensing; no cloud-commitment eligibility established. Source: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/overview.html (reviewed 2026-11-16).

- Cloud commitment eligibility: Edition-dependent. NVIDIA explicitly states that AI Enterprise AWS Marketplace private offers are eligible toward an AWS committed-spend agreement. Confirm the specific offer and buyer agreement; this statement does not establish Azure/GCP credit or eligibility for every image or BYOL purchase. Scope: Vendor statement for AI Enterprise AWS Marketplace private offers only. Source: https://www.nvidia.com/en-us/data-center/lp/aws-marketplace-offer/ (reviewed 2026-11-16).

- Single sign-on: Sources checked — unresolved. AI Enterprise is a suite with independently versioned application and infrastructure components. NGC/catalog account authentication does not establish SAML/OIDC for every deployed microservice or workload. Select the actual NIM/framework/management components and confirm their runtime identity integrations and entitlements. Scope: Suite-wide runtime SSO cannot be established from distribution/account access. Source: https://docs.nvidia.com/ai-enterprise/latest/user-guide/index.html (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Sources checked — unresolved. Government Ready, STIG-hardening and FIPS-library statements describe selected NVIDIA software branches. The reviewed page does not establish a current independent attestation for the complete customer-account deployment, third-party integrations or every suite component. Scope: Selected software-artifact assurances versus a customer-deployment audit. Source: https://docs.nvidia.com/ai-enterprise/planning-resource/ai-enterprise-infrastructure-software/latest/enterprise-software-built-on-open-source.html (reviewed 2026-11-16).

- Security controls: Documented. NVIDIA describes Government Ready infrastructure software and Production Branch application software using STIG-hardened containers, FIPS-compliant libraries and monthly security/maintenance patches. The statement is branch-specific; it does not certify every suite component, cloud image or customer deployment. Scope: AI Enterprise infrastructure software and application Production Branch; not an independent customer-environment attestation. Source: https://docs.nvidia.com/ai-enterprise/planning-resource/ai-enterprise-infrastructure-software/latest/enterprise-software-built-on-open-source.html (reviewed 2026-11-16).

- Air-gapped operation: Documented. NVIDIA documents registering a Delegated License Service appliance on an air-gapped network by manually transferring registration details through its Licensing Portal. This confirms an offline licensing workflow for applicable components, not disconnected compatibility of every AI Enterprise service or model. Scope: NVIDIA License System DLS workflow; component licensing and application dependencies differ. Source: https://docs.nvidia.com/license-system/latest/nvidia-license-system-quick-start-guide/ (reviewed 2026-11-16). Supporting source: When AI Enterprise requires the license system — https://docs.nvidia.com/ai-enterprise/planning-resource/licensing-guide/latest/license-system.html.

- Deployment artifact / IaC: Documented. NVIDIA provides provider-specific image, standard-instance and Kubernetes procedures rather than one universal template. Tencent and Volcano standard-instance guides require a supported instance, certified Ubuntu, NVIDIA driver, Docker, Container Toolkit and NGC tooling, with BYOL. Scope: Supported cloud matrix; component, operating system and instance compatibility must all match. Source: https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/overview.html (reviewed 2026-11-16). Supporting source: Tencent standard instance — https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/tencent-standard-instance.html. Supporting source: Volcano Engine standard instance — https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/bytedance-volcano-engine-standard-instance.html.

- Minimum footprint / sizing: Sources checked — unresolved. The suite includes multiple frameworks, drivers, operators and NIM services, each with its own support matrix. NIM directs buyers to model- and hardware-specific prerequisites. No suite-wide CPU/RAM/VRAM minimum is established; select components, model profiles, supported GPUs, concurrency and redundancy before sizing. Scope: Suite/component/model dependent; complete workload footprint unresolved. Source: https://docs.nvidia.com/ai-enterprise/latest/user-guide/index.html (reviewed 2026-11-20). Supporting source: NIM component-specific prerequisite path — https://docs.nvidia.com/nim/large-language-models/latest/get-started/index.html.

- License pricing: Documented. The current licensing guide lists a one-year self-managed subscription at USD 4,500 per GPU including standard support. Multi-year, perpetual, educational and partner terms differ. Cloud-marketplace and bundled-hardware entitlements have separate rules; this software list price excludes GPU infrastructure and is not a workload quote. For Tencent/Volcano BYOL paths, the previously noted per-instance versus per-GPU unit still needs contract confirmation. Scope: Self-managed NVIDIA Partner Network list price; CSP marketplace terms differ. Source: https://docs.nvidia.com/ai-enterprise/planning-resource/licensing-guide/latest/pricing.html (reviewed 2026-11-20). Supporting source: Cloud BYOL unit requires separate confirmation — https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/tencent-standard-instance.html. Supporting source: Volcano Engine BYOL path — https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/bytedance-volcano-engine-standard-instance.html.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. NVIDIA's November 2026 lifecycle material lists active 9.0/R620, 8.3/R595, and 7.9 LTSB/R580 branches with distinct support windows. NeMo Microservices support ended October 1, 2026, after 25.12 was designated the final GA release. Scope: AI Enterprise component and branch lifecycle; no single suite version covers every deployment. Source: https://docs.nvidia.com/ai-enterprise/lifecycle/latest/index.html (reviewed 2026-11-18).







## Oracle E-Business Suite on OCI (Customer-Managed)

Customer-managed Oracle enterprise application suite provisioned or migrated into the customer's OCI tenancy.

- Listing: https://launchinyourcloud.com/directory/oracle-e-business-suite-oci/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Oracle E-Business Suite Suite or Component licenses; separate technology licensing may apply.
- Licensing model: commercial-only
- Installation: Oracle E-Business Suite Cloud Manager One-Click or Advanced Provisioning, or lift-and-shift tooling
- Architecture: Persistent application tier on OCI Compute with database tier on Compute or supported OCI Database services
- Operations: Customer DBAs operate the E-Business Suite environment and OCI resources; Oracle Customer Success Services is optional.
- Product website: https://www.oracle.com/applications/ebusiness/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Oracle describes the OCI deployment as the same E-Business Suite used on premises and applies bring-your-own-license terms. Validate the current certified EBS release, database, region and Cloud Manager combination in My Oracle Support before provisioning.

Oracle E-Business Suite requires commercial Suite or Component licenses; database and other technology entitlements may be separate.

The application tier runs on customer OCI Compute, with the database on Compute or a supported customer OCI Database service.


### Category fit

- erp-crm: Runs Oracle's enterprise financials, supply-chain, human-capital and related business applications in a customer OCI tenancy.

### Deployment boundaries


- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679337.htm (checked 2026-11-19). 


### Cloud deployment evidence

- Oracle E-Business Suite Cloud Manager in the customer OCI tenancy (oci): https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679337.htm
  Oracle documents deploying Cloud Manager inside the customer's OCI tenancy to provision and manage complete E-Business Suite environments on customer OCI resources.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Oracle E-Business Suite Cloud Manager in an OCI tenancy: https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679337.htm

- Prepare an OCI tenancy for E-Business Suite: https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679340.htm

- Oracle E-Business Suite on OCI FAQ: https://docs.oracle.com/cd/E72030_01/infoportal/ebscfaq.html

- Oracle E-Business Suite licensing: https://docs.oracle.com/cd/E26401_01/doc.122/e22950/T422699g54568.htm

- Buyer evidence: iac: https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679339.htm

### Licensing sources

- https://docs.oracle.com/cd/E26401_01/doc.122/e22950/T422699g54568.htm

- https://docs.oracle.com/cd/E72030_01/infoportal/ebscfaq.html

### Infrastructure sources

- https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679337.htm

- https://docs.oracle.com/cd/E72030_01/infoportal/ebscfaq.html


### Buyer diligence


Research coverage: 12/12 fields (100%); 2 documented, 10 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. The reviewed deployment and licensing sources did not establish a public cloud-marketplace offer that unambiguously entitles the selected self-hosted edition. Obtain the exact offer ID, seller, delivery artifact and edition terms before treating marketplace procurement as available. Scope: Oracle E-Business Suite on OCI (Customer-Managed): selected customer-operated edition. Source: https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679337.htm (reviewed 2026-11-19).

- Cloud commitment eligibility: Sources checked — unresolved. Customer-cloud deployment or marketplace delivery does not by itself establish cloud-spend commitment eligibility. Confirm the exact offer, billed dimensions, private-offer terms and buyer agreement. Scope: Oracle E-Business Suite on OCI (Customer-Managed): selected customer-operated edition. Source: https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679337.htm (reviewed 2026-11-19).

- Single sign-on: Edition-dependent. Oracle documents EBS SSO through a WebLogic-hosted E-Business Suite Asserter and OCI IAM. Third-party IdPs federate through IAM, not directly with the asserter. Availability requires an eligible IAM domain type (Oracle Apps Premium, Premium or External) or legacy IDCS Standard; user provisioning is separate. Scope: Oracle E-Business Suite Asserter; verify supported EBS/WebLogic/JDK/asserter versions and current identity entitlements. Source: https://docs.oracle.com/en-us/iaas/Content/Identity/ebs/faq_using-ebs-asserter-faq.htm (reviewed 2026-11-20). Supporting source: Legacy IDCS integration component compatibility — https://docs.oracle.com/en/cloud/paas/identity-cloud/uaids/typical-workflow-using-e-business-suite-asserter-authenticate-oracle-e-business-suite-oracle-ident.html.

- SCIM provisioning: Sources checked — unresolved. The reviewed sources did not establish a SCIM endpoint or automated user and group lifecycle for this selected edition. SSO, directory authentication or just-in-time account creation would not by themselves establish SCIM. Scope: Oracle E-Business Suite on OCI (Customer-Managed): selected customer-operated edition. Source: https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679337.htm (reviewed 2026-11-19).

- Compliance attestations: Sources checked — unresolved. The reviewed product and deployment sources did not establish an independent compliance attestation whose assessed scope covers this customer-operated edition and its local infrastructure. Obtain the current report and map customer responsibilities. Scope: Oracle E-Business Suite on OCI (Customer-Managed): selected customer-operated edition. Source: https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679337.htm (reviewed 2026-11-19).

- Security controls: Sources checked — unresolved. The deployment documentation establishes customer control of infrastructure but does not by itself establish a complete hardened baseline. Review identity, encryption, secrets, network exposure, audit logging, backups, patching and incident response for the selected topology. Scope: Oracle E-Business Suite on OCI (Customer-Managed): selected customer-operated edition. Source: https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679337.htm (reviewed 2026-11-19).

- Air-gapped operation: Sources checked — unresolved. The reviewed sources did not establish a fully disconnected installation, update and license workflow for this selected edition. Identify required registries, package repositories, telemetry, identity, activation and support endpoints before claiming air-gapped operation. Scope: Oracle E-Business Suite on OCI (Customer-Managed): selected customer-operated edition. Source: https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679337.htm (reviewed 2026-11-19).

- Deployment artifact / IaC: Sources checked — unresolved. Oracle documents provisioning through the Cloud Manager Marketplace image, but the public guide leaves the image version/date as a selector and does not establish a fixed image OCID or complete licensed EBS installer manifest. Confirm the exact Cloud Manager image, EBS/application/database bundle and certification matrix through the customer’s Oracle entitlements before deployment. Scope: Exact licensed Oracle EBS/Cloud Manager deployment artifacts; the documented customer-OCI hosting path remains established. Source: https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679339.htm (reviewed 2026-11-19).

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed sources describe the deployment components but do not provide one complete production sizing model for the buyer's users, data volume, traffic, retention and availability target. Size every application and managed-service dependency. Scope: Oracle E-Business Suite on OCI (Customer-Managed): selected customer-operated edition. Source: https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679337.htm (reviewed 2026-11-19).

- License pricing: Edition-dependent. Commercial Oracle E-Business Suite Suite or Component licenses; separate technology licensing may apply. Infrastructure, support and operating labor are separate unless the order states otherwise. Scope: Oracle E-Business Suite on OCI (Customer-Managed): selected customer-operated edition. Source: https://docs.oracle.com/cd/E26401_01/doc.122/e22950/T422699g54568.htm (reviewed 2026-11-19).

- Operating cost estimate: Sources checked — unresolved. No complete dated operating-cost estimate is established. Define provider and region, workload, availability, retention, storage growth, network transfer, support, software entitlement and operating labor before estimating total cost. Scope: Oracle E-Business Suite on OCI (Customer-Managed): selected customer-operated edition. Source: https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679337.htm (reviewed 2026-11-19).

- Release snapshot / cadence: Sources checked — unresolved. The reviewed documentation establishes a current deployment path but not a durable release snapshot, support window and upgrade cadence for every included component. Record the exact application, installer, image, chart and dependency versions selected for production. Scope: Oracle E-Business Suite on OCI (Customer-Managed): selected customer-operated edition. Source: https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679337.htm (reviewed 2026-11-19).







## Oracle FLEXCUBE Universal Banking

Commercial universal-banking software with retail/corporate lending and customer OCI deployment architecture.

- Listing: https://launchinyourcloud.com/directory/oracle-flexcube/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Package / binary installer
- Architecture: Licensed FLEXCUBE application, database and networking tiers in customer OCI.
- 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://docs.oracle.com/en/solutions/flexcube-oci/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The architecture covers the customer's deployed banking system, not a hosted banking subscription. Match application, database, Java/runtime and third-party licensing and validate the bank-specific production design.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Licensed FLEXCUBE application, database and networking tiers in customer OCI. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- financial-application-management: Commercial universal-banking software with retail/corporate lending and customer OCI deployment architecture.

### Deployment boundaries


- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.oracle.com/en/solutions/flexcube-oci/ (checked 2026-11-19). 


### Cloud deployment evidence

- OCI Reference Architecture (oci): https://docs.oracle.com/en/solutions/flexcube-oci/
  Licensed FLEXCUBE application, database and networking tiers in customer OCI. The architecture covers the customer's deployed banking system, not a hosted banking subscription. Match application, database, Java/runtime and third-party licensing and validate the bank-specific production design.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- OCI Reference Architecture: https://docs.oracle.com/en/solutions/flexcube-oci/

- Oracle Software Contracts: https://www.oracle.com/contracts/software/

- OMA A-Z: https://www.oracle.com/contracts/a-z/oma/

- FLEXCUBE Docs: https://docs.oracle.com/en/industries/financial-services/flexcube/index.html

### Licensing sources

- https://www.oracle.com/contracts/software/

- https://www.oracle.com/contracts/a-z/oma/

### Infrastructure sources

- https://docs.oracle.com/en/solutions/flexcube-oci/


### Buyer diligence


Research coverage: 4/12 fields (33%); 3 documented, 1 unresolved. Coverage is not a feature score.

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The vendor FLEXCUBE UBS 14.7.2 security guide explicitly supports SAML SSO and distinguishes it from LDAP/MSAD password authentication. Select a currently supported compatible release, IdP and installation properties; OCI administrator login and every bundled banking component are separate identity surfaces. Scope: Versioned FLEXCUBE UBS 14.7.2 documented SAML capability; current deployment compatibility required. Source: https://docs.oracle.com/cd/F87755_01/PDF/Installation/Environment%20Setup/Security_Guide.pdf (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. The OCI guide provides a FLEXCUBE reference infrastructure architecture and recommendations, but does not establish the complete entitled application installer or a release-matched turnkey deployment artifact. Obtain the vendor package and supported WebLogic/database/application installation procedure. Scope: FLEXCUBE application delivery artifact remains unconfirmed; OCI architecture is separate. Source: https://docs.oracle.com/en/solutions/flexcube-oci/ (reviewed 2026-11-21).

- Minimum footprint / sizing: Documented. The OCI reference architecture names VM.Standard2.2 as a starting minimum shape and at least 256 GB ASM storage for its described database, with separate redundant application/database tiers. It uses older Oracle Linux 7.7-era assumptions. Revalidate current OS/shapes, licences, banking workload and HA sizing rather than treating it as a current universal minimum. Scope: Historical vendor FLEXCUBE OCI architecture sizing reference; current workload/releases require validation. Source: https://docs.oracle.com/en/solutions/flexcube-oci/ (reviewed 2026-11-21).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Oracle FLEXCUBE Universal Banking; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.oracle.com/contracts/software/ (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Oracle Hyperion EPM Self-Managed

Commercial self-managed financial consolidation, planning and performance-reporting applications.

- Listing: https://launchinyourcloud.com/directory/oracle-hyperion-epm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Terraform
- Architecture: Hyperion application, database, storage and network tiers provisioned through the OCI reference architecture.
- 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://docs.oracle.com/en/solutions/deploy-hyperion-oci/index.html
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The selected self-managed application family is 11.2.x. Newer cloud-service or Smart View release numbers must not be used as its server version. Generic corporate consolidation is distinct from a packaged private-capital operations platform.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Hyperion application, database, storage and network tiers provisioned through the OCI reference architecture. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- data-analytics: Commercial self-managed financial consolidation, planning and performance-reporting applications.

### Deployment boundaries


- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.oracle.com/en/solutions/deploy-hyperion-oci/index.html (checked 2026-11-19). 


### Cloud deployment evidence

- OCI Terraform Guide (oci): https://docs.oracle.com/en/solutions/deploy-hyperion-oci/index.html
  Hyperion application, database, storage and network tiers provisioned through the OCI reference architecture. The selected self-managed application family is 11.2.x. Newer cloud-service or Smart View release numbers must not be used as its server version. Generic corporate consolidation is distinct from a packaged private-capital operations platform.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- OCI Terraform Guide: https://docs.oracle.com/en/solutions/deploy-hyperion-oci/index.html

- EPM 11.2 Docs: https://docs.oracle.com/en/applications/enterprise-performance-management/11.2/

- Oracle Software Contracts: https://www.oracle.com/contracts/software/

- EPM Portal: https://docs.oracle.com/en/applications/enterprise-performance-management/index.html

- Lifetime Support: https://www.oracle.com/support/lifetime-support/

### Licensing sources

- https://www.oracle.com/contracts/software/

### Infrastructure sources

- https://docs.oracle.com/en/solutions/deploy-hyperion-oci/index.html


### Buyer diligence


Research coverage: 4/12 fields (33%); 3 documented, 1 unresolved. Coverage is not a feature score.

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The EPM 11.2 security guide enables user SSO through Shared Services using a trusted custom HTTP header supplied by an identity/security agent. Configure the agent, protected entry points, user directories and logout before enabling it. This is a specific trusted-header integration, not proof of generic direct SAML login in every EPM component. Scope: Oracle Hyperion EPM 11.2 shared-services user SSO boundary. Source: https://docs.oracle.com/en/applications/enterprise-performance-management/11.2/epmsc/header_based_auth_sso_steps_config_epm.html (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Oracle publishes Terraform-based OCI infrastructure guidance for Hyperion/EPM Windows/database tiers and HA patterns. The guide references legacy Terraform 0.13 tooling, so adapt and validate supported tooling/releases. It provisions the platform; entitled EPM software installation and application configuration remain separate. Scope: Vendor EPM OCI reference infrastructure automation; legacy tooling and separate licensed applications. Source: https://docs.oracle.com/en/solutions/deploy-hyperion-oci/index.html (reviewed 2026-11-21). Deployment artifact: https://docs.oracle.com/en/solutions/deploy-hyperion-oci/index.html. Artifact reference: Published Oracle OCI Hyperion infrastructure solution reviewed on this date.

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed OCI deployment guide describes topology and HA choices but does not establish complete quantitative current sizing for the selected EPM applications. Obtain application/database/search/Essbase resources, model/data volume, concurrent planners, batch workload and recovery capacity; an infrastructure blueprint is not a workload baseline. Scope: Hyperion EPM selected-application production sizing remains unconfirmed. Source: https://docs.oracle.com/en/solutions/deploy-hyperion-oci/index.html (reviewed 2026-11-21).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Oracle Hyperion EPM Self-Managed; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.oracle.com/contracts/software/ (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Oracle Insurance Policy Administration (OIPA) (BYOL)

Commercial life and annuity policy-administration software with associated claims workflows.

- Listing: https://launchinyourcloud.com/directory/oracle-insurance-policy-administration/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Docker / Compose
- Architecture: Customer OCI application compute, licensed Java application server and Oracle ATP database.
- 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://docs.oracle.com/cd/G50044_01/docker_atp_install_guides/oipa_on_oracle_cloud_infrastructure/Content/Docker/OIPA%20Deployment%20on%20OCI.htm
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The vendor documents setup in the customer's tenancy and compartments. This is the documented OIPA product, not a general property-and-casualty claims suite. Application-server, database and OIPA entitlements and versions require matching.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Customer OCI application compute, licensed Java application server and Oracle ATP database. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- claims-management: Commercial life and annuity policy-administration software with associated claims workflows.

### Deployment boundaries


- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.oracle.com/cd/G50044_01/docker_atp_install_guides/oipa_on_oracle_cloud_infrastructure/Content/Docker/OIPA%20Deployment%20on%20OCI.htm (checked 2026-11-19). 


### Cloud deployment evidence

- OIPA OCI Setup (oci): https://docs.oracle.com/cd/G50044_01/docker_atp_install_guides/oipa_on_oracle_cloud_infrastructure/Content/Docker/OIPA%20Deployment%20on%20OCI.htm
  Customer OCI application compute, licensed Java application server and Oracle ATP database. The vendor documents setup in the customer's tenancy and compartments. This is the documented OIPA product, not a general property-and-casualty claims suite. Application-server, database and OIPA entitlements and versions require matching.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- OIPA OCI Setup: https://docs.oracle.com/cd/G50044_01/docker_atp_install_guides/oipa_on_oracle_cloud_infrastructure/Content/Docker/OIPA%20Deployment%20on%20OCI.htm

- OIPA ATP DB Setup: https://docs.oracle.com/cd/G50044_01/docker_atp_install_guides/oipa_database_setup_on_oracle_atp/Content/Docker/Deploy%20the%20OIPA%20and%20IVS%20database%20schema%20on%20ATP/index.htm

- OIPA Claims Scope: https://www.oracle.com/financial-services/insurance/policy-administration/

- OIPA Licensing 12.2: https://docs.oracle.com/cd/G50044_01/oipa_license_guide/Content/Licensing%20Information/index.htm

- Oracle Contracts: https://www.oracle.com/contracts/

- OIPA 12.2.0.0 Portal: https://docs.oracle.com/cd/G50044_01/index.html

- OIPA 12.2 Release Notes: https://docs.oracle.com/cd/G50044_01/oipa_oirp_releasenotes/Content/Release%20Notes/OIPA%20Release%20Notes/index.htm

### Licensing sources

- https://docs.oracle.com/cd/G50044_01/oipa_license_guide/Content/Licensing%20Information/index.htm

- https://www.oracle.com/contracts/

### Infrastructure sources

- https://docs.oracle.com/cd/G50044_01/docker_atp_install_guides/oipa_on_oracle_cloud_infrastructure/Content/Docker/OIPA%20Deployment%20on%20OCI.htm


### 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 current 12.2 guide documents native OIDC browser authorization-code login, enabled with application.isSSOEnabled and oidc-config.yaml. It describes issuer/JWKS validation, claim mapping and optional local provisioning with configured company/security group. Configure HTTPS and provider/redirect/audience settings; OCI console SSO is a separate identity surface. Scope: OIPA 12.2.0.0 native application-user OIDC; service identities and OCI administration separate. Source: https://docs.oracle.com/cd/G50044_01/oipa_security_guide/Content/OIPA%20Security%20Guide/User%20Authentication.htm (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Oracle documents customer-tenancy OCI networking/compute/ATP setup plus licensed OIPA and database-schema deployment guides. Supply compatible entitled application/runtime packages and configure database, secrets and persistence; these are application/platform installation procedures rather than an unrestricted public turnkey stack. Scope: OIPA 12.2 documentation library OCI/manual deployment and licensed packages. Source: https://docs.oracle.com/cd/G50044_01/docker_atp_install_guides/oipa_on_oracle_cloud_infrastructure/Content/Docker/OIPA%20Deployment%20on%20OCI.htm (reviewed 2026-11-21). Deployment artifact: https://docs.oracle.com/cd/G50044_01/index.html. Artifact reference: Oracle OIPA library G50044_01 / 12.2.0.0. Supporting source: ATP schema deployment — https://docs.oracle.com/cd/G50044_01/docker_atp_install_guides/oipa_database_setup_on_oracle_atp/Content/Docker/Deploy%20the%20OIPA%20and%20IVS%20database%20schema%20on%20ATP/index.htm.

- Minimum footprint / sizing: Documented. The library benchmark describes two compute VMs running eight Cycle agents, four per VM, at 6 GB JVM heap each, with a separately configured Oracle database using a 50-GB SGA. This is a published batch-test configuration with its own policy/activity volume, not a host minimum, interactive-user workload or HA/cost estimate. Scope: OIPA 12.2 report with legacy V12.1 path labels; component-level benchmark configuration only. Source: https://docs.oracle.com/cd/G50044_01/oipa_performance_summary_report_oracle/Content/Performance%20Summary%20Report%20-%20Oracle%20Server/V12.1.0.0/Cycle03.htm (reviewed 2026-11-21).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Oracle Insurance Policy Administration (OIPA) (BYOL); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://docs.oracle.com/cd/G50044_01/oipa_license_guide/Content/Licensing%20Information/index.htm (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Oracle JD Edwards EnterpriseOne (BYOL)

Licensed ERP for financial, supply-chain and business operations in a customer OCI tenancy.

- Listing: https://launchinyourcloud.com/directory/oracle-jd-edwards-enterpriseone/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Package / binary installer
- Architecture: JD Edwards application, web and database tiers on customer OCI infrastructure.
- 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://docs.oracle.com/en/solutions/learn-architecture-deploy-jd-edwards/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Bring-your-own-licence software and database entitlements are separate from OCI infrastructure billing.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

JD Edwards application, web and database tiers on customer OCI infrastructure. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Licensed ERP for financial, supply-chain and business operations in a customer OCI tenancy.

### Deployment boundaries


- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.oracle.com/en/solutions/learn-architecture-deploy-jd-edwards/ (checked 2026-11-19). 


### Cloud deployment evidence

- OCI JDE Guide (oci): https://docs.oracle.com/en/solutions/learn-architecture-deploy-jd-edwards/
  JD Edwards application, web and database tiers on customer OCI infrastructure. Bring-your-own-licence software and database entitlements are separate from OCI infrastructure billing.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- OCI JDE Guide: https://docs.oracle.com/en/solutions/learn-architecture-deploy-jd-edwards/

- Oracle Contracts: https://www.oracle.com/corporate/contracts/

- JDE Release 26 Docs: https://docs.oracle.com/en/applications/jd-edwards/

### Licensing sources

- https://www.oracle.com/corporate/contracts/

### Infrastructure sources

- https://docs.oracle.com/en/solutions/learn-architecture-deploy-jd-edwards/


### 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 EnterpriseOne 9.2 Security Administration Guide documents SSO through Oracle Access Management for the EnterpriseOne web client. The integration does not cover Collaborative Portal. OAM deployment, authentication policy and middleware entitlements must be evaluated separately. Scope: JD Edwards EnterpriseOne 9.2 web-client integration; not a native general-purpose OIDC/SAML provider claim. Source: https://docs.oracle.com/en/applications/jd-edwards/administration/9.2.x/eotsc/understanding-jd-edwards-enterpriseone-single-sign-on-through-1.html (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Oracle documents obtaining One-Click Provisioning archives from Software Delivery Cloud, selecting compatible application/tools releases, accepting the licence, and reassembling/checking the downloaded parts. This is entitled vendor provisioning software, not a public immutable Terraform template. Scope: EnterpriseOne 9.2 Linux One-Click Provisioning; provisioning server, selected release media and licence rights required. Source: https://docs.oracle.com/en/applications/jd-edwards/one-click-provisioning/9.2/eoiol/obtaining-using-archive-files-one-click-provisioning-opl.html (reviewed 2026-11-20). Deployment artifact: https://edelivery.oracle.com/. Artifact reference: EnterpriseOne 9.2; select application/tools release and archive part numbers.

- Minimum footprint / sizing: Sources checked — unresolved. Oracle describes separate provisioning, deployment, development, presentation, application and database roles, including HA/DR architecture choices. The reviewed architecture does not establish a single quantitative resource floor for the selected modules and proposed workload. Scope: Complete customer-operated EnterpriseOne environment; provisioning-server prerequisites alone do not size the application and database tiers. Source: https://docs.oracle.com/en/solutions/learn-architecture-deploy-jd-edwards/ (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Oracle JD Edwards EnterpriseOne (BYOL); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.oracle.com/corporate/contracts/ (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Oracle PeopleSoft Grants — Customer-Managed

Customer-managed sponsored-research grants application integrated with PeopleSoft financial modules.

- Listing: https://launchinyourcloud.com/directory/peoplesoft-grants/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Oracle licenses; Grants requires additional PeopleSoft applications
- Licensing model: commercial-only
- Installation: Oracle PeopleSoft deployment packages and licensed application installation
- Architecture: Persistent enterprise application, web/middleware and database environment on customer physical or virtual servers.
- Operations: Customer operates the PeopleSoft environment, database, integrations, backups and patching; follow Oracle certification and application update guidance.
- Product website: https://www.oracle.com/applications/peoplesoft/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

PeopleSoft Grants is not a standalone application. Oracle states that all functionality requires purchased General Ledger, Project Costing, Contracts and Billing applications. The documented grants process concerns sponsored research rather than general-purpose grantmaking. The November 2026 Critical Security Patch Update is final: Oracle lists 13 PeopleSoft patches, six issues potentially exploitable without authentication, a maximum CVSS score of 9.8, and affected PeopleTools 8.61 through 8.63. Apply the applicable final CSPU packages after checking installed PeopleTools components.

Commercial PeopleSoft application licenses apply. Oracle explicitly requires purchased General Ledger, Project Costing, Contracts and Billing for the complete Grants functionality; installation package access is not an entitlement.

Persistent enterprise application, web/middleware and database environment on customer physical or virtual servers.


### Category fit

- grants-management: Sponsored-research proposal approval, award funding, budgets, billing and reporting within the PeopleSoft application suite.

- research-grant-administration: Research proposal preparation and submission, projects, protocols, award negotiation and post-award processing.

### Deployment boundaries


- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.oracle.com/cd/E52319_01/infoportal/peoplesoft_cloud_faq.html (checked 2026-11-12). 


### Cloud deployment evidence

- PeopleSoft on Oracle Cloud Infrastructure FAQ (oci): https://docs.oracle.com/cd/E52319_01/infoportal/peoplesoft_cloud_faq.html
  Oracle documents customer-hosted licensed PeopleSoft applications, including FSCM, on OCI, with Cloud Manager deployment options. Grants runs within the licensed FSCM environment; confirm the application modules, database license and supported release.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Physical and virtual deployment framework: https://docs.oracle.com/en/applications/peoplesoft/peopletools/8.63/peopletools-863-deployment-packages-installation/understanding-peoplesoft-deployment-framework.html

- Obtaining installation packages: https://docs.oracle.com/en/applications/peoplesoft/peopletools/8.63/peopletools-863-deployment-packages-installation/understanding-peoplesoft-peopletools-deployment-packages.html

- Sponsored research functionality and required purchased applications: https://docs.oracle.com/en/applications/peoplesoft/financials-and-supply-chain-management/9.2.056/peoplesoft-grants/peoplesoft-grants-business-processes.html

- Oracle November 2026 Critical Security Patch Update: https://www.oracle.com/security-alerts/cspunov2026.html

### Licensing sources

- https://docs.oracle.com/en/applications/peoplesoft/financials-and-supply-chain-management/9.2.056/peoplesoft-grants/peoplesoft-grants-business-processes.html

- https://docs.oracle.com/en/applications/peoplesoft/peopletools/8.63/peopletools-863-deployment-packages-installation/understanding-peoplesoft-peopletools-deployment-packages.html

### Infrastructure sources

- https://docs.oracle.com/en/applications/peoplesoft/peopletools/8.63/peopletools-863-deployment-packages-installation/understanding-peoplesoft-deployment-framework.html

- https://docs.oracle.com/en/applications/peoplesoft/peopletools/8.63/peopletools-863-deployment-packages-installation/understanding-peoplesoft-peopletools-deployment-packages.html


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. PeopleTools 8.63 documents shared sign-on among PeopleSoft applications and desktop/network integration, with configured trust/token and application identities. Grants inherits its selected PeopleSoft/PeopleTools security platform; this does not establish every external SAML/OIDC integration or purchased IAM component automatically. Scope: PeopleSoft Grants platform-level shared sign-on; compatible PeopleTools deployment and trust configuration. Source: https://docs.oracle.com/en/applications/peoplesoft/peopletools/8.63/security-administration/authentication-single-signon.html (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: Oracle's final November 2026 CSPU lists 13 PeopleSoft patches, six issues potentially exploitable without authentication, and a maximum CVSS score of 9.8. Apply the applicable final CSPU packages and follow Oracle's branch and component instructions. Scope: PeopleTools 8.61 through 8.63; application-specific applicability depends on installed components.. Source: https://www.oracle.com/security-alerts/cspunov2026.html (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Oracle documents Deployment Packages (DPKs) for PeopleTools deployment and configuration, including middle-tier domains and Automated Configuration Management. Obtain packages for the licensed PeopleSoft application and supported OS; a DPK does not prove Grants is configured or licensed. Scope: PeopleTools 8.63 deployment mechanism; not a public Grants-specific IaC artifact. Source: https://docs.oracle.com/en/applications/peoplesoft/peopletools/8.63/peopletools-863-deployment-packages-installation/understanding-peoplesoft-deployment-framework.html (reviewed 2026-11-14).

- Minimum footprint / sizing: Sources checked — unresolved. The Grants business-process and deployment-framework documents establish application/deployment context but do not give a complete numeric production CPU/RAM/storage baseline. Size the shared Financials stack, database, batch/reports and HA; Cloud Manager or PeopleTools appliance sizing is not Grants workload sizing. Scope: PeopleSoft Grants production sizing remains unconfirmed. Source: https://docs.oracle.com/en/applications/peoplesoft/financials-and-supply-chain-management/9.2.056/peoplesoft-grants/peoplesoft-grants-business-processes.html (reviewed 2026-11-21).

- License pricing: Documented. Oracle lists PeopleSoft Financials, Project Costing and Contracts as prerequisite licences for Grants, with restricted-use PeopleTools rights governed by application licensing. Confirm all purchased products, licence metrics, database/middleware and support in the order; Grants is not a standalone free module. Scope: PeopleSoft FSCM 9.2 Grants commercial prerequisites and restricted-use framework. Source: https://docs.oracle.com/en/applications/peoplesoft/financials-and-supply-chain-management/licensing-information-user-manual-for-peoplesoft-financials-and-supply-chain-management-9-2/peoplesoft-fscm-9-2-prerequisites-entitled-products-restricted-use-licenses.html (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.




### Security and lifecycle reviews

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

- PeopleSoft November 2026 Critical Security Patch Update (security-advisory): Oracle's final November 2026 CSPU lists 13 PeopleSoft patches, six issues potentially exploitable without authentication, and a maximum CVSS score of 9.8. Scope: PeopleTools 8.61 through 8.63; application-specific applicability depends on installed components. Conditions: The Oracle risk matrix and installed PeopleTools components determine applicability to a particular Grants deployment. Action: Apply the applicable final CSPU packages and follow Oracle's branch and component instructions. Source: https://www.oracle.com/security-alerts/cspunov2026.html; reviewed 2026-11-18.




## Oracle PeopleSoft HCM (BYOL)

Licensed PeopleSoft human-capital and employee records applications in a customer OCI tenancy.

- Listing: https://launchinyourcloud.com/directory/oracle-peoplesoft-hcm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: OCI Cloud Manager and licensed PeopleSoft deployment packages
- Architecture: PeopleSoft HCM application, web and database tiers managed using OCI Cloud Manager.
- 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://docs.oracle.com/en/applications/peoplesoft/cloud-manager/index.html
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

HCM and Grants are distinct application suites on the same PeopleSoft platform. Cloud Manager releases do not establish a particular HCM update image or security patch.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

PeopleSoft HCM application, web and database tiers managed using OCI Cloud Manager. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- hr-employee-records-management: Licensed PeopleSoft human-capital and employee records applications in a customer OCI tenancy.

### Deployment boundaries


- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.oracle.com/en/applications/peoplesoft/cloud-manager/index.html (checked 2026-11-19). 


### Cloud deployment evidence

- OCI Cloud Manager Docs (oci): https://docs.oracle.com/en/applications/peoplesoft/cloud-manager/index.html
  PeopleSoft HCM application, web and database tiers managed using OCI Cloud Manager. HCM and Grants are distinct application suites on the same PeopleSoft platform. Cloud Manager releases do not establish a particular HCM update image or security patch.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- OCI Cloud Manager Docs: https://docs.oracle.com/en/applications/peoplesoft/cloud-manager/index.html

- PeopleSoft HCM Portal: https://docs.oracle.com/cd/E52319_01/infoportal/hcm.html

- Oracle Contracts: https://www.oracle.com/corporate/contracts/

- PeopleSoft Docs 2026: https://docs.oracle.com/en/applications/peoplesoft/index.html

### Licensing sources

- https://www.oracle.com/corporate/contracts/

### Infrastructure sources

- https://docs.oracle.com/en/applications/peoplesoft/cloud-manager/index.html


### 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. Oracle documents PeopleSoft HCM user SSO through OCI IAM Identity Domains and App Gateway: the gateway authenticates the browser and passes mapped identity headers to PeopleSoft. The tutorial requires Oracle Apps Premium identity licensing and PeopleSoft configuration; it protects the web UI rather than every non-HTTP integration. Scope: PeopleSoft HCM web-user SSO through a separately licensed identity gateway, not Cloud Manager administrator login. Source: https://docs.oracle.com/en/learn/oci-iam-auth-peoplesoft/ (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Oracle PeopleSoft Cloud Manager defines repeatable environment templates combining a selected application deployment package (DPK), topology, database, security and policies, then provisions an environment from that template. Supply the licensed HCM DPK and compatible PeopleTools/Cloud Manager versions; this is Cloud Manager automation on OCI rather than an unrestricted public HCM Terraform package. Scope: Oracle PeopleSoft HCM on OCI via licensed DPK and Cloud Manager environment templates; version compatibility and entitlement are deployment-specific. Source: https://docs.oracle.com/cd/F48809_01/pcd91pbr13/eng/pcd/cmif/ManagingTemplate.html (reviewed 2026-11-21). Deployment artifact: https://docs.oracle.com/cd/F48809_01/pcd91pbr13/eng/pcd/cmif/ManagingTemplate.html. Artifact reference: PeopleSoft Cloud Manager 9.1, PeopleBook update 13. Supporting source: Provisioning environments — https://docs.oracle.com/cd/F32972_01/pcd91pbr11/eng/pcd/cmif/task_ManagingEnvironments.html.

- Minimum footprint / sizing: Sources checked — unresolved. Cloud Manager templates select a topology and application/database attributes; that configurability does not establish an HCM production CPU/RAM/storage minimum. Cloud Manager appliance sizing also is not application sizing. Confirm licensed HCM/PeopleTools/database versions, concurrent sessions, batch/payroll peaks, recovery requirements and HA topology before costing an environment. Scope: PeopleSoft HCM application sizing remains unconfirmed; OCI management appliance or template choices are not a universal HCM minimum. Source: https://docs.oracle.com/cd/F48809_01/pcd91pbr13/eng/pcd/cmif/ManagingTemplate.html (reviewed 2026-11-21).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Oracle PeopleSoft HCM (BYOL); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.oracle.com/corporate/contracts/ (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Oracle Siebel CRM (BYOL)

Customer-managed Oracle CRM and enterprise customer-service applications.

- Listing: https://launchinyourcloud.com/directory/oracle-siebel-crm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Kubernetes manifests; Application platform deployment
- Architecture: Siebel application and gateway tiers, database and OCI deployment tooling.
- 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://docs.oracle.com/en/solutions/oci-oke-siebel-deploy/index.html
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

OCI Cloud Manager and Kubernetes automation are deployment components; their versions do not establish the licensed Siebel application release.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Siebel application and gateway tiers, database and OCI deployment tooling. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Customer-managed Oracle CRM and enterprise customer-service applications.

### Deployment boundaries


- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.oracle.com/en/solutions/oci-oke-siebel-deploy/index.html (checked 2026-11-19). 


### Cloud deployment evidence

- OCI OKE Guide (oci): https://docs.oracle.com/en/solutions/oci-oke-siebel-deploy/index.html
  Siebel application and gateway tiers, database and OCI deployment tooling. OCI Cloud Manager and Kubernetes automation are deployment components; their versions do not establish the licensed Siebel application release.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- OCI OKE Guide: https://docs.oracle.com/en/solutions/oci-oke-siebel-deploy/index.html

- OCI Arch: https://docs.oracle.com/en/solutions/learn-architecture-deploy-siebel/understand-oracle-siebel-crm-architecture-oracle-cloud-infrastructure.html

- Oracle Contracts: https://www.oracle.com/corporate/contracts/

- Siebel Bookshelf 26.x: https://docs.oracle.com/en/applications/siebel/

### Licensing sources

- https://www.oracle.com/corporate/contracts/

### Infrastructure sources

- https://docs.oracle.com/en/solutions/oci-oke-siebel-deploy/index.html


### Buyer diligence


Research coverage: 4/12 fields (33%); 2 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.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Siebel supports integration with external Web SSO: a trusted gateway authenticates the user and passes the subject in a request header. Siebel does not itself provide a SAML assertion consumer/validator. The identity solution and header trust boundary must be designed and supported separately. Scope: Siebel CRM 17, 18 and later as covered by the Security Guide; external authentication is required. Source: https://docs.oracle.com/cd/G30554_01/books/Secur/c-About-Implementing-Federated-Single-SignOn-ak2955398.html (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. Oracle documents a Siebel Cloud Manager/GitLab workflow for OKE and database deployment, but the reviewed high-level playbook does not identify a complete version-matched Siebel runtime image/manifest bundle. Confirm the entitled Cloud Manager build, application images and generated deployment payload before production. Scope: Customer-operated Siebel OCI provisioning path established; exact production application artifacts remain unresolved. Source: https://docs.oracle.com/en/solutions/oci-oke-siebel-deploy/index.html (reviewed 2026-11-20). Supporting source: GitLab artifact prerequisites — https://docs.oracle.com/en/solutions/oci-oke-siebel-deploy/considerations-gitlab.html. Supporting source: OCI resource provisioning — https://docs.oracle.com/en/solutions/oci-oke-siebel-deploy/learn-oci-resources.html.

- Minimum footprint / sizing: Sources checked — unresolved. The OCI reference architecture uses three OKE worker nodes plus a separate database, persistent storage and Cloud Manager/GitLab services. It does not establish a complete quantitative CPU/RAM/storage minimum for the proposed Siebel workload or a validated HA capacity profile. Scope: Complete Siebel environment, including provisioning and database services; three worker nodes alone are not a sizing estimate. Source: https://docs.oracle.com/en/solutions/oci-oke-siebel-deploy/index.html (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Oracle Siebel CRM (BYOL); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.oracle.com/corporate/contracts/ (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Oracle WebCenter Content 14c on OCI

Commercial enterprise content and records management deployed by an Oracle Marketplace stack into a customer OCI tenancy.

- Listing: https://launchinyourcloud.com/directory/oracle-webcenter-content/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Oracle WebCenter Content Paid or bring-your-own-license offering; database and component entitlements are separate.
- Licensing model: commercial-only
- Installation: OCI Marketplace image and Resource Manager stack for WebCenter Content 14.1.2
- Architecture: Customer-operated WebCenter Content application and middleware virtual machines with database, storage and OCI networking.
- Operations: Customer manages OCI compartments, networking, compute, database, storage, identity, TLS, backups, patch bundles, scaling and license compliance.
- Product website: https://www.oracle.com/middleware/technologies/webcenter-content.html
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers WebCenter Content 14.1.2 on Oracle Cloud Infrastructure, not a vendor-hosted content service. The Marketplace supports Paid and BYOL offers and can include Universal Content Management, Enterprise Capture, Imaging and Records Management according to the purchased entitlement. The Quick Start topology is a deployment accelerator, not proof of high availability; validate the current patch bundle, database entitlement and production topology. The November 2026 Marketplace update is 26.11.1 and includes JDK 21.0.13.1, the WebCenter November CSPU, Enterprise Capture updates, and Outside In updates. Oracle's final CSPU also covers unauthenticated Content Server issues; apply only the packages applicable to 12.2.1.4 or 14.1.2.0.

Oracle offers Paid and BYOL Marketplace variants. WebCenter Content, Records Management and database use remain governed by the purchased Oracle entitlements; Marketplace deployment does not grant unrelated component rights.

The OCI Marketplace solution deploys persistent WebCenter Content and middleware services with durable database and storage dependencies.


### Category fit

- document-management: Enterprise capture, content storage, metadata, search, workflows and controlled document access in a customer-operated deployment.

- records-management: Records capabilities are included in the licensed WebCenter Content family and support managed retention and disposition workflows.

### Deployment boundaries


- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.oracle.com/en/cloud/paas/webcenter-content/webcenter-content-on-marketplace/index.html (checked 2026-11-17). 


### Cloud deployment evidence

- WebCenter Content 14.1.2 stack in a customer OCI tenancy (oci): https://docs.oracle.com/en/cloud/paas/webcenter-content/webcenter-content-on-marketplace/index.html
  Oracle documents launching a VM-based WebCenter Content stack through OCI Marketplace and Resource Manager into the selected customer compartment. Paid and BYOL variants are available; the customer operates the resulting OCI resources.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- WebCenter Content 14c Marketplace deployment: https://docs.oracle.com/en/cloud/paas/webcenter-content/webcenter-content-on-marketplace/index.html

- WebCenter Content Marketplace licensing: https://docs.oracle.com/en/cloud/paas/webcenter-content/webcenter-content-marketplace-license/index.html

- WebCenter Content Marketplace 26.11.1 release notes: https://docs.oracle.com/en/cloud/paas/webcenter-content/content-marketplace-whatsnew/index.html

- WebCenter Content management and records capabilities: https://docs.oracle.com/en/middleware/webcenter/content/14.1.2/webcenter-content-manage/index.html

- Oracle November 2026 Critical Security Patch Update: https://www.oracle.com/security-alerts/cspunov2026.html

### Licensing sources

- https://docs.oracle.com/en/cloud/paas/webcenter-content/webcenter-content-marketplace-license/index.html

### Infrastructure sources

- https://docs.oracle.com/en/cloud/paas/webcenter-content/webcenter-content-on-marketplace/index.html


### Buyer diligence


Research coverage: 12/12 fields (100%); 7 documented, 5 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. Oracle documents paid and BYOL WebCenter Content stacks in OCI Marketplace, provisioned through Resource Manager. Select the matching Content release and purchased entitlements; this is not WebCenter Portal. Scope: WebCenter Content 14c OCI Marketplace. Source: https://docs.oracle.com/en/cloud/paas/webcenter-content/webcenter-content-on-marketplace/index.html (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Paid/BYOL Marketplace licensing is documented, but OCI commitment or credit treatment for the selected Content offer and buyer agreement is not established. Scope: Reviewed public evidence for Oracle WebCenter Content 14c on OCI; unresolved within this edition/deployment. Source: https://docs.oracle.com/en/cloud/paas/webcenter-content/webcenter-content-marketplace-license/index.html (reviewed 2026-11-17).

- Single sign-on: Documented. The 14c Marketplace guide documents SAML 2.0 federation with IDCS for WebCenter Content. Create the identity application and configure Content role mappings; changing the service hostname requires reapplying SSO configuration. Scope: WebCenter Content section of the combined 14c Marketplace guide. Source: https://docs.oracle.com/en/cloud/paas/webcenter/webcenter-on-marketplace/index.html (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. Content SAML role mappings are documented, but the reviewed guide does not establish a Content SCIM endpoint, supported operations or license entitlement. IDCS capabilities alone do not establish Content provisioning support. Scope: WebCenter Content 14c, not generic identity-domain capabilities. Source: https://docs.oracle.com/en/cloud/paas/webcenter/webcenter-on-marketplace/index.html (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed Oracle WebCenter Content 14c on OCI 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://docs.oracle.com/en/cloud/paas/webcenter/webcenter-on-marketplace/index.html (reviewed 2026-11-17).

- Security controls: Documented. Provisioning requires customer-controlled IAM, network access and secrets. The guide documents Vault-backed configuration and separate Content roles; restrict administrative access and preserve the configured service hostname. Current advisory review: Oracle's November 2026 CSPU includes unauthenticated Content Server vulnerabilities and updates for supported WebCenter Content branches. Apply the applicable November CSPU packages and JDK update for the deployed branch. Scope: Marketplace deployment controls; not a compliance attestation Oracle WebCenter Content 12.2.1.4 and 14.1.2.0; several Content Server entries have a maximum CVSS score of 6.9.. Source: https://www.oracle.com/security-alerts/cspunov2026.html (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://docs.oracle.com/en/cloud/paas/webcenter/webcenter-on-marketplace/index.html. Supporting source: Marketplace 26.11.1 notes — https://docs.oracle.com/en/cloud/paas/webcenter-content/content-marketplace-whatsnew/index.html.

- Air-gapped operation: Sources checked — unresolved. The OCI Marketplace workflow uses OCI services and optional IDCS federation. A fully disconnected 14c installation, entitlement renewal and patch-transfer procedure was not established. Scope: Reviewed public evidence for Oracle WebCenter Content 14c on OCI; unresolved within this edition/deployment. Source: https://docs.oracle.com/en/cloud/paas/webcenter-content/webcenter-content-on-marketplace/index.html (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. The Marketplace workflow launches a Resource Manager stack into a selected compartment. Configure the database, networking, keys and storage before provisioning; Quick Start defaults do not establish a production HA design. Scope: 14c Marketplace stack workflow; not a separately pinned Terraform repository. Source: https://docs.oracle.com/en/cloud/paas/webcenter-content/webcenter-content-on-marketplace/index.html (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. The tenancy prerequisites include Compute, database, load balancing, block storage and Vault services. Size the selected VM shape, node count and database for the workload; these service prerequisites are not a complete capacity model. Scope: 14c Marketplace prerequisites; customer-managed supporting services. Source: https://docs.oracle.com/en/cloud/paas/webcenter-content/webcenter-content-on-marketplace/index.html (reviewed 2026-11-17).

- License pricing: Documented. Oracle offers Paid and BYOL Marketplace variants. WebCenter Content, Records Management and database use remain governed by the purchased Oracle entitlements; Marketplace deployment does not grant unrelated component rights. Scope: Oracle WebCenter Content 14c on OCI: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://docs.oracle.com/en/cloud/paas/webcenter-content/webcenter-content-marketplace-license/index.html (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Only OCI deployment is confirmed for this listing; an AWS scenario is outside the evidenced deployment. Obtain an OCI region, licensed topology and database quote rather than pricing an unconfirmed AWS installation. 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://docs.oracle.com/en/cloud/paas/webcenter-content/webcenter-content-on-marketplace/index.html (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. The November 2026 Marketplace notes list 26.11.1 with JDK 21.0.13.1, the WebCenter November CSPU, Enterprise Capture updates, and Outside In updates. The source provides month-level timing only. Scope: WebCenter Content 14c Marketplace release notes. Source: https://docs.oracle.com/en/cloud/paas/webcenter-content/content-marketplace-whatsnew/index.html (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- Oracle WebCenter Content November 2026 CSPU (security-advisory): Oracle's November 2026 CSPU includes unauthenticated Content Server vulnerabilities and updates for supported WebCenter Content branches. Scope: Oracle WebCenter Content 12.2.1.4 and 14.1.2.0; several Content Server entries have a maximum CVSS score of 6.9. Conditions: Applicability depends on installed components, exposed interfaces, and user interaction for the specific CVE. Action: Apply the applicable November CSPU packages and JDK update for the deployed branch. Source: https://www.oracle.com/security-alerts/cspunov2026.html; reviewed 2026-11-18. Supporting source: Marketplace 26.11.1 notes — https://docs.oracle.com/en/cloud/paas/webcenter-content/content-marketplace-whatsnew/index.html.




## Red Hat OpenShift AI Self-Managed

Commercial AI and machine-learning platform installed as an Operator on a customer-operated Red Hat OpenShift cluster.

- Listing: https://launchinyourcloud.com/directory/red-hat-openshift-ai-self-managed/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp, oci, ibm
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Red Hat OpenShift AI Self-Managed subscription; an eligible OpenShift subscription is also required.
- Licensing model: commercial-only
- Installation: OpenShift AI Operator through OperatorHub or the oc command-line interface
- Architecture: OpenShift operators and persistent AI workbench, pipeline, model-serving and supporting services on customer Kubernetes infrastructure.
- Operations: Customer manages the OpenShift cluster, storage, accelerators, identity, networking, model data, backups and upgrades within Red Hat's supported configuration matrix.
- Product website: https://www.redhat.com/en/technologies/cloud-computing/openshift/openshift-ai
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers OpenShift AI Self-Managed, not Red Hat's managed cloud-service add-on. Support depends on a compatible OpenShift Container Platform release, storage and accelerator matrix, and active subscriptions. Underlying OpenShift and cloud infrastructure are operated by the customer. RHSA-2026:95872 is a critical OpenShift AI 3.5.3 security update covering nine CVEs. Use Red Hat's package and deployment scope to determine affected components, then apply 3.5.3 or a later supported update.

The selected Self-Managed product requires a Red Hat OpenShift AI subscription and an eligible OpenShift platform entitlement. Open-source components do not grant the complete supported product entitlement.

OpenShift AI runs persistent operator-managed workloads on customer OpenShift clusters with storage, compute and optional accelerator dependencies.


### Category fit

- ai-tools: AI workbenches, pipelines, model serving and lifecycle tooling delivered on a customer-operated OpenShift platform.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://access.redhat.com/articles/rhoai-supported-configs (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://access.redhat.com/articles/rhoai-supported-configs (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://access.redhat.com/articles/rhoai-supported-configs (checked 2026-11-17). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://access.redhat.com/articles/rhoai-supported-configs (checked 2026-11-17). 

- ibm: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://access.redhat.com/articles/rhoai-supported-configs (checked 2026-11-17). 


### Cloud deployment evidence

- OpenShift AI Self-Managed on supported OpenShift public-cloud platforms (aws, azure, gcp, oci, ibm): https://access.redhat.com/articles/rhoai-supported-configs
  Red Hat's Self-Managed matrix explicitly lists OpenShift Container Platform on AWS, Azure, Google Cloud, IBM Cloud and Oracle Cloud. The selected OpenShift release, subscriptions, storage, accelerator and component restrictions apply; managed cloud-service add-ons are a separate offering.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- OpenShift AI supported configurations: https://access.redhat.com/articles/rhoai-supported-configs

- OpenShift AI Self-Managed 3.5 installation and subscription: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install

- RHSA-2026:95872: https://access.redhat.com/errata/RHSA-2026%3A95872

### Licensing sources

- https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install

### Infrastructure sources

- https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install


### Buyer diligence


Research coverage: 12/12 fields (100%); 7 documented, 5 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. OperatorHub installation and required subscriptions do not establish a specific cloud Marketplace offer for the Self-Managed AI entitlement. Managed add-ons and generic OpenShift offers are separate. Scope: Reviewed public evidence for Red Hat OpenShift AI Self-Managed; unresolved within this edition/deployment. Source: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Self-Managed AI and underlying OpenShift subscriptions need offer-specific confirmation before software charges are treated as eligible cloud commitment spend. Scope: Reviewed public evidence for Red Hat OpenShift AI Self-Managed; unresolved within this edition/deployment. Source: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install (reviewed 2026-11-17).

- Single sign-on: Documented. OpenShift AI uses the identity provider configured for its OpenShift cluster. Configure cluster identity and AI user/admin groups; this does not establish a separate application SCIM endpoint. Scope: Self-managed OpenShift AI 3.5 identity through the cluster. Source: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. AI authentication delegates to the OpenShift IdP. The reviewed installation guide does not establish a separate AI SCIM endpoint or the provisioning capabilities of the buyer’s chosen IdP. Scope: Reviewed public evidence for Red Hat OpenShift AI Self-Managed; unresolved within this edition/deployment. Source: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed Red Hat OpenShift AI Self-Managed 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://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install (reviewed 2026-11-17).

- Security controls: Documented. Installation requires cluster administrator access, a configured IdP and compatible subscriptions. Configure access groups and certificate trust for workbenches, models, pipelines and object storage. Current advisory review: RHSA-2026:95872 is a critical OpenShift AI 3.5.3 update covering nine CVEs. Apply OpenShift AI 3.5.3 or a later supported update following Red Hat's erratum. Scope: OpenShift AI cluster access prerequisites Red Hat OpenShift AI 3.5 packages identified in the erratum.. Source: https://access.redhat.com/errata/RHSA-2026%3A95872 (reviewed 2026-11-18). Supporting source: Certificate trust in disconnected deployments — https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed_in_a_disconnected_environment/working-with-certificates_certs. Supporting source: Prior security-controls source — https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install.

- Air-gapped operation: Documented. Red Hat supplies a separate disconnected installation guide using mirrored Operator/container content. Required model, notebook, accelerator and object-storage dependencies must also be staged for the selected components. Scope: Self-managed OpenShift AI disconnected installation. Source: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed_in_a_disconnected_environment/ (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. Install the supported OpenShift AI Operator on an entitled, compatible OpenShift cluster and enable the required components. Cluster creation, storage, accelerators and model assets remain separate deployment work. Scope: OpenShift AI Self-Managed 3.5 Operator installation. Source: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. Installing the Operator requires at least two workers with 8 CPU/32 GiB each; single-node OpenShift requires 32 CPU/128 GiB. Workloads, models, accelerators and storage need additional resources; these installation minima do not establish HA workload capacity. Scope: OpenShift AI 3.5 installation minima; platform/control-plane resources additional. Source: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install (reviewed 2026-11-17).

- License pricing: Documented. The selected Self-Managed product requires a Red Hat OpenShift AI subscription and an eligible OpenShift platform entitlement. Open-source components do not grant the complete supported product entitlement. Scope: Red Hat OpenShift AI Self-Managed: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Select OpenShift HA topology, enabled AI components, model size, GPU needs, concurrency, object storage and both subscription entitlements. Operator installation minima do not size inference/training. 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://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. Red Hat OpenShift AI 3.5.3 was published as critical security advisory RHSA-2026:95872 on November 6, 2026 and covers nine CVEs. Scope: Red Hat OpenShift AI self-managed 3.5. Source: https://access.redhat.com/errata/RHSA-2026%3A95872 (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- Red Hat OpenShift AI 3.5.3 critical security update (security-advisory): RHSA-2026:95872 is a critical OpenShift AI 3.5.3 update covering nine CVEs. Scope: Red Hat OpenShift AI 3.5 packages identified in the erratum. Conditions: Installed components and package versions determine applicability. Action: Apply OpenShift AI 3.5.3 or a later supported update following Red Hat's erratum. Source: https://access.redhat.com/errata/RHSA-2026%3A95872; reviewed 2026-11-18.




## ScyllaDB Enterprise Self-Managed

Self-managed distributed NoSQL database deployed on customer-controlled cloud virtual machines.

- Listing: https://launchinyourcloud.com/directory/scylladb-enterprise-self-managed/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: ScyllaDB Source Available License Agreement for current Enterprise releases; eligibility and capacity limits apply unless covered by paid terms.
- Licensing model: source-available
- Installation: Official cloud image/AMI, with a documented AWS CloudFormation cluster example
- Architecture: Customer-operated ScyllaDB nodes with cloud networking and local or attached persistent storage
- Operations: Customer manages topology, networking, authentication, capacity, backups, monitoring, patching and upgrades.
- Product website: https://www.scylladb.com/product/scylla-enterprise/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Current stable documentation covers ScyllaDB 2026.3 and labels each provider path self-managed, separately from ScyllaDB Cloud. The source-available license is not OSI open source; its free grant has eligibility and aggregate capacity limits, and commercial customers require paid terms.

Current ScyllaDB Enterprise is source-available under ScyllaDB's agreement, not an OSI-approved license. The agreement imposes eligibility, usage and commercial-customer restrictions.

The database runs directly on customer-controlled cloud compute instances; multi-node durability, storage layout and replication are customer-operated.


### Category fit

- databases-vector: Distributed NoSQL wide-column database for high-throughput, low-latency application data.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-aws.html (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-azure.html (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-gcp.html (checked 2026-11-19). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-oci.html (checked 2026-11-19). 


### Cloud deployment evidence

- Self-managed ScyllaDB 2026.3 on AWS (aws): https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-aws.html
  Official instructions launch ScyllaDB AMIs into the customer's AWS VPC and distinguish this self-managed deployment from ScyllaDB Cloud.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed. Versions: 2026.3 documentation.

- Self-managed ScyllaDB 2026.3 on Google Cloud (gcp): https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-gcp.html
  Official instructions use the customer's active Google Cloud account and gcloud to launch ScyllaDB images and call the deployment self-managed.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed. Versions: 2026.3 documentation.

- Self-managed ScyllaDB 2026.3 on Azure (azure): https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-azure.html
  Official instructions use the customer's Azure subscription and resource group to create a ScyllaDB VM and call the deployment self-managed.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed. Versions: 2026.3 documentation.

- Self-managed ScyllaDB 2026.3 on OCI (oci): https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-oci.html
  Official instructions deploy the bring-your-own-license ScyllaDB Marketplace image into the customer's OCI tenancy, compartment, VCN and compute instance and call the deployment self-managed.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed. Versions: 2026.3 documentation.


### Sources

- Install ScyllaDB 2026.3: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/

- ScyllaDB Enterprise self-managed product: https://www.scylladb.com/product/

- Supported ScyllaDB versions: https://docs.scylladb.com/stable/versioning/version-support.html

- ScyllaDB Source Available License Agreement: https://www.scylladb.com/scylladb-software-license-agreement/

- Buyer evidence: marketplace: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-oci.html

- Buyer evidence: commitments: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-aws.html

- Reviewed deployment artifact reference: https://s3.amazonaws.com/downloads.scylladb.com/downloads/scylla/aws/cloudformation/scylla_cluster_2026.3.6_x86_64.yaml

- Buyer evidence: footprint: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-gcp.html

- Source-available licensing FAQ: https://www.scylladb.com/source-available-faq/

### Licensing sources

- https://www.scylladb.com/scylladb-software-license-agreement/

- https://www.scylladb.com/source-available-faq/

### Infrastructure sources

- https://docs.scylladb.com/manual/stable/getting-started/install-scylla/


### 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: Documented. ScyllaDB documents a bring-your-own-license Marketplace image for self-managed Enterprise deployment in OCI. The other reviewed cloud paths use vendor images or instructions and do not establish equivalent Marketplace offers. Scope: ScyllaDB Enterprise Self-Managed: selected customer-operated edition. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-oci.html (reviewed 2026-11-19).

- Cloud commitment eligibility: Sources checked — unresolved. Customer-cloud deployment or marketplace delivery does not by itself establish cloud-spend commitment eligibility. Confirm the exact offer, billed dimensions, private-offer terms and buyer agreement. Scope: ScyllaDB Enterprise Self-Managed: selected customer-operated edition. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-aws.html (reviewed 2026-11-19).

- Single sign-on: Sources checked — unresolved. The reviewed installation and edition sources did not establish the exact SSO protocols, identity-provider support and entitlement for this selected edition. Confirm authentication, role mapping and break-glass access before deployment. Scope: ScyllaDB Enterprise Self-Managed: selected customer-operated edition. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/ (reviewed 2026-11-19).

- SCIM provisioning: Sources checked — unresolved. The reviewed sources did not establish a SCIM endpoint or automated user and group lifecycle for this selected edition. SSO, directory authentication or just-in-time account creation would not by themselves establish SCIM. Scope: ScyllaDB Enterprise Self-Managed: selected customer-operated edition. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/ (reviewed 2026-11-19).

- Compliance attestations: Sources checked — unresolved. The reviewed product and deployment sources did not establish an independent compliance attestation whose assessed scope covers this customer-operated edition and its local infrastructure. Obtain the current report and map customer responsibilities. Scope: ScyllaDB Enterprise Self-Managed: selected customer-operated edition. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/ (reviewed 2026-11-19).

- Security controls: Edition-dependent. The provider guides deploy customer-controlled database nodes and networking. The buyer must explicitly configure authentication, encryption, firewall rules, monitoring, backup and repair; image delivery alone is not a hardened cluster baseline. Scope: ScyllaDB Enterprise Self-Managed: selected customer-operated edition. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/ (reviewed 2026-11-19).

- Air-gapped operation: Sources checked — unresolved. The reviewed sources did not establish a fully disconnected installation, update and license workflow for this selected edition. Identify required registries, package repositories, telemetry, identity, activation and support endpoints before claiming air-gapped operation. Scope: ScyllaDB Enterprise Self-Managed: selected customer-operated edition. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-aws.html (reviewed 2026-11-19).

- Deployment artifact / IaC: Documented. The AWS guide links a versioned x86 CloudFormation cluster example for 2026.3.6. It provisions EC2 networking and cluster resources and accepts a regional Scylla AMI. Review its public-address/SSH settings, initial credentials, instance count and licence limits; this sample is not a validated production HA or cost design. Scope: AWS x86 sample stack; ARM templates and other providers have separate images and configuration. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-aws.html (reviewed 2026-11-19). Deployment artifact: https://s3.amazonaws.com/downloads.scylladb.com/downloads/scylla/aws/cloudformation/scylla_cluster_2026.3.6_x86_64.yaml. Artifact reference: scylla_cluster_2026.3.6_x86_64.yaml; SHA-256 71c636562d0e5ea54633ba4c0f95a32a1db139726a46923c2372e6550cfb6c7c.

- Minimum footprint / sizing: Documented. The GCP image launch guide requires at least 2 vCPUs. This bootstrap requirement does not establish production node count, RAM, local SSD capacity, HA, replication, compaction or a 1-TB workload design; follow provider-specific sizing and licence limits separately. Scope: ScyllaDB 2026.3 GCP image launch minimum only; not a cluster-wide production footprint. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-gcp.html (reviewed 2026-11-19).

- License pricing: Edition-dependent. The current source-available agreement provides a restricted free grant subject to eligibility and aggregate capacity limits; commercial customers and use beyond those terms require a paid agreement. Validate legal eligibility and capacity calculations. Scope: ScyllaDB Enterprise Self-Managed: selected customer-operated edition. Source: https://www.scylladb.com/scylladb-software-license-agreement/ (reviewed 2026-11-19). Supporting source: Source-available licensing FAQ — https://www.scylladb.com/source-available-faq/.

- Operating cost estimate: Sources checked — unresolved. No complete dated operating-cost estimate is established. Define provider and region, workload, availability, retention, storage growth, network transfer, support, software entitlement and operating labor before estimating total cost. Scope: ScyllaDB Enterprise Self-Managed: selected customer-operated edition. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-aws.html (reviewed 2026-11-19).

- Release snapshot / cadence: Documented. The current stable self-managed installation documentation is labeled ScyllaDB 2026.3. Verify the exact patch and its support window before deploying provider images or performing an upgrade. Scope: ScyllaDB Enterprise Self-Managed: selected customer-operated edition. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/ (reviewed 2026-11-19).







## Solix Application Retirement — Customer-Managed

Archive retired applications while retaining searchable access to historical business information.

- Listing: https://launchinyourcloud.com/directory/solix-application-retirement/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, oci, ibm
- Operating model: Customer-operated
- Infrastructure IDs: unspecified
- License: Commercial Enterprise Edition
- Licensing model: commercial-only
- Installation: Vendor-assisted customer-managed enterprise deployment; confirm supported package/topology
- Architecture: Customer-managed archival platform and data storage
- Operations: Customer-managed deployment is available; agree implementation, support, upgrades and infrastructure ownership with Solix.
- Product website: https://www.solix.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Solix documents application retirement and separately describes customer-managed and self-managed on-premises/private/public-cloud options. This entry excludes fully managed SOLIXCloud SaaS. Public installation commands and specific customer-account hyperscaler deployment paths were not verified.

This entry covers the licensed Enterprise Edition customer-managed application retirement option. Self-management and public-cloud deployment do not imply open-source rights.

Customer-hosted installation is documented, but the reviewed public material does not specify enough runtime detail to classify it. Confirm the supported server or container topology with the vendor.


### Category fit

- legacy-system-archive-access: Dedicated application retirement and historical-data archival access using the customer-managed enterprise option. Vendor-assisted enterprise installation; no public installer was verified. Confirm package, deployment topology and responsibility split.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://bsmedia.business-standard.com/_media/bs/data/announcements/bse/06092025/3528499d-78aa-4f75-9656-074933f4ddc2.pdf (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://bsmedia.business-standard.com/_media/bs/data/announcements/bse/06092025/3528499d-78aa-4f75-9656-074933f4ddc2.pdf (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://bsmedia.business-standard.com/_media/bs/data/announcements/bse/06092025/3528499d-78aa-4f75-9656-074933f4ddc2.pdf (checked 2026-11-12). Source: https://www.solix.com/documents/case-studies/how-a-clean-energy-utility-saved-millions-with-solixcloud.pdf (checked 2026-11-12). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://bsmedia.business-standard.com/_media/bs/data/announcements/bse/06092025/3528499d-78aa-4f75-9656-074933f4ddc2.pdf (checked 2026-11-12). 

- ibm: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://bsmedia.business-standard.com/_media/bs/data/announcements/bse/06092025/3528499d-78aa-4f75-9656-074933f4ddc2.pdf (checked 2026-11-12). 


### Cloud deployment evidence

- Solix private deployment and enterprise archiving platform disclosure (aws, azure, gcp, oci, ibm): https://bsmedia.business-standard.com/_media/bs/data/announcements/bse/06092025/3528499d-78aa-4f75-9656-074933f4ddc2.pdf
  The parent company's 2024-25 annual report, printed page 46/PDF page 48, describes CDP Private on an organization's existing cloud instances with in-house application management. Its Enterprise Archiving architecture includes Application Retirement above named AWS, Azure, Google Cloud, Oracle Cloud and IBM Cloud infrastructure, and states that the bundle is offered privately as well as as SaaS. This is a platform compatibility disclosure, not a release-specific installation guide; confirm the current private package, topology, licenses and operating agreement.
  Source type: corporate-disclosure; reviewed: 2026-11-12; vendor support: not-assessed.

- Solix Application Retirement customer case on a Google Cloud private tenant (gcp): https://www.solix.com/documents/case-studies/how-a-clean-energy-utility-saved-millions-with-solixcloud.pdf
  The vendor case documents Application Retirement on a Google Cloud private tenant, delivered collaboratively with Kyndryl. It corroborates a real private deployment; it does not by itself establish customer account ownership or customer operations. Use the separate CDP Private disclosure for the customer-operated option and agree the exact contract and support boundaries.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Application retirement functionality: https://www.solix.com/products/application-retirement-solution/

- Explicit customer-managed deployment option: https://www.solix.com/solixcloud/

- Enterprise Edition deployment options: https://www.solix.com/products/enterprise-edition/

- Official self-managed private/public-cloud deployment statement: https://www.solix.com/documents/datasheets/solix-cloud-data-management-for-sap.pdf

### Licensing sources

- https://www.solix.com/products/enterprise-edition/

- https://www.solix.com/solixcloud/

### Infrastructure sources

- https://www.solix.com/products/application-retirement-solution/


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The reviewed product and Enterprise Edition pages describe governance and deployment options but do not establish the customer-managed retirement application identity integration, provider protocol or account mapping. A hosted-service SSO statement cannot settle the selected customer-hosted edition. Scope: Solix customer-managed application retirement SSO remains unconfirmed. Source: https://www.solix.com/products/application-retirement-solution/ (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Sources checked — unresolved. The product page mentions SOC 2 and ISO 27001 alongside SolixCloud options. It does not establish an assessed scope for the customer-managed Application Retirement installation. Scope: Customer-managed application versus vendor cloud scope unresolved. Source: https://www.solix.com/products/application-retirement-solution/ (reviewed 2026-11-14).

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. Solix advertises implementation services and multiple deployment options, but the reviewed public material does not expose a release-specific installer, chart or infrastructure artifact for customer-managed retirement. Obtain the supported delivery package and deployment procedure. Scope: Customer-managed Solix installation artifact remains unconfirmed. Source: https://www.solix.com/products/enterprise-edition/ (reviewed 2026-11-21).

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed enterprise/product material does not establish numeric customer-managed CPU/RAM/storage or HA requirements. Size ingestion, source formats, indexed archive volume, retrieval concurrency and retention separately from the vendor-operated cloud service. Scope: Customer-managed application retirement sizing remains unconfirmed. Source: https://www.solix.com/products/enterprise-edition/ (reviewed 2026-11-21).

- License pricing: Documented. Solix describes Enterprise Edition as a consumption-based commercial bundle including preservation products and application retirement, with on-premises, hybrid and cloud options. Obtain the applicable customer-managed order, consumption metric, support and non-production/DR rights; no SOLIXCloud SaaS rate is substituted for that agreement. Scope: Current Enterprise Edition commercial model; negotiated customer-managed entitlement and price remain order-specific. Source: https://www.solix.com/products/enterprise-edition/ (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## SUSE Security (NeuVector)

Open-source Kubernetes security platform with documented customer-operated deployment on AWS, Azure, Google Cloud, IBM Cloud, Alibaba Cloud and OCI.

- Listing: https://launchinyourcloud.com/directory/suse-security-neuvector/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp, ibm, alibaba, oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for NeuVector; Rancher Prime delivery and commercial support have separate subscription terms.
- Licensing model: open-source
- Installation: SUSE Security Helm chart or manifests on public-cloud Kubernetes
- Architecture: Manager, controller and scanner services plus an enforcer DaemonSet inside the customer Kubernetes cluster.
- Operations: Customer manages Kubernetes, registry access, Helm values, storage, certificates, policies, upgrades, monitoring and cluster privileges.
- Product website: https://www.suse.com/products/security/
- Source review: 2026-11-18; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

This entry covers upstream NeuVector/SUSE Security deployment; subscription images/support can require commercial entitlements. SUSE names six public-cloud Kubernetes targets. Resolve the conflicting manager-redundancy guidance before HA design, and apply GKE Autopilot allowlists where required. Scan-policy/compliance functions do not certify the customer installation.

NeuVector is Apache-2.0 licensed. SUSE subscriptions can add entitled delivery, integrations and support.

SUSE Security runs controller, scanner and enforcement workloads on customer Kubernetes nodes.


### Category fit

- devops: Adds runtime security, vulnerability scanning and policy enforcement to customer Kubernetes delivery environments.

- observability: Provides workload, network and security-event visibility for Kubernetes clusters.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html (checked 2026-11-18). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html (checked 2026-11-18). 

- ibm: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html (checked 2026-11-18). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html (checked 2026-11-18). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html (checked 2026-11-18). 


### Cloud deployment evidence

- SUSE Security on six named public-cloud Kubernetes services (aws, azure, gcp, ibm, alibaba, oci): https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html
  SUSE explicitly names AWS EKS, Azure AKS, Google Cloud, IBM Cloud Kubernetes, Alibaba Cloud and Oracle Cloud and links full Kubernetes/Helm application deployment. Confirm tested platform versions and privileges. GKE Autopilot requires allowlists; AWS ECS is no longer supported in the requirements guide.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.


### Community and maintenance

NeuVector publishes contribution/governance instructions and maintained public application and Helm releases. This is sustained upstream participation rather than a star-count threshold; commercial SUSE support remains a separately purchased entitlement.

Reviewed 2026-11-18.

- Official maintenance and adoption evidence: https://github.com/neuvector/neuvector/blob/main/CONTRIBUTING.md

- Official maintenance and adoption evidence: https://github.com/neuvector/neuvector/releases/tag/v5.6.4

- Official maintenance and adoption evidence: https://github.com/neuvector/neuvector-helm/releases/tag/v2.11.4

### Sources

- Deploy SUSE Security on public-cloud Kubernetes: https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html

- Deploy SUSE Security with Helm: https://documentation.suse.com/cloudnative/security/latest/en/helm.html

- SUSE Security support matrix: https://www.suse.com/suse-neuvector/support-matrix/all-supported-versions/neuvector-v-all-versions/

- NeuVector Apache 2.0 license: https://github.com/neuvector/neuvector/blob/main/LICENSE

### Licensing sources

- https://github.com/neuvector/neuvector/blob/main/LICENSE

### Infrastructure sources

- https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html


### Buyer diligence


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

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


- Marketplace delivery: Edition-dependent. SUSE’s security guide routes AWS procurement through its multi-product Rancher/SUSE subscription offer. The current offer is a private-offer commercial contract labelled SaaS delivery; it is not a standalone upstream OSS AMI or proof of included NeuVector support. Confirm the Security entitlement in the order. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/5.6/en/awsmarketplace.html (reviewed 2026-11-18). Supporting source: Actual SUSE Cloud Marketplace Program offer — https://aws.amazon.com/marketplace/pp/prodview-b6es6ar6n4siw. Offer prodview-b6es6ar6n4siw: SUSE; SaaS-labelled multi-product private-offer subscription; https://aws.amazon.com/marketplace/pp/prodview-b6es6ar6n4siw.

- Cloud commitment eligibility: Sources checked — unresolved. The multi-product private-offer route does not settle the buyer’s commitment eligibility or whether SUSE Security is included in the selected contract. Confirm exact entitlement, billable dimensions and cloud agreement. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://aws.amazon.com/marketplace/pp/prodview-b6es6ar6n4siw (reviewed 2026-11-18). Supporting source: AWS commitment qualification is product/agreement-specific — https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html.

- Single sign-on: Documented. The v5.6 guide documents SAML 2.0 SSO, including Okta and group-to-role mapping. Signed assertions are required; encrypted assertions are not supported by this documented configuration. Set a deliberate default role rather than assuming group import grants appropriate access. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/5.6/en/saml.html (reviewed 2026-11-18).

- SCIM provisioning: Sources checked — unresolved. SAML group-to-role mapping does not establish a SCIM server or provisioning/deprovisioning operations. Confirm a current endpoint and user-removal behavior for the selected OSS or subscription-delivered edition. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/5.6/en/saml.html (reviewed 2026-11-18).

- Compliance attestations: Documented. LRQA certificate 10726335 covers SUSE’s ISO/IEC 27001:2022 ISMS and ISO/IEC 27701:2019 PIMS; schedule page 28 explicitly includes NeuVector, LLC. Issued November 4, 2025, it expires November 3, 2028. This is organisational information/privacy management assurance, not certification of a customer’s NeuVector cluster, protected workloads, configuration or operations. Scope: SUSE organisational management systems including the scheduled NeuVector entity; not a customer-deployment attestation. Source: https://www.suse.com/support/security/certifications/SUSE-ISO-27001-ISO-27701.pdf (reviewed 2026-11-18). Supporting source: Official SUSE certificate index — https://www.suse.com/support/security/certifications/isoiec-certification/.

- Security controls: Documented. NeuVector documents SAML role mapping and signed-assertion requirements. Enforcers run on cluster nodes and controllers coordinate security policy, so deployment needs the documented privileged access and network visibility. Scope cluster roles and protect console/controller access. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/5.6/en/saml.html (reviewed 2026-11-18). Supporting source: Runtime and component requirements — https://documentation.suse.com/cloudnative/security/5.6/en/requirements.html. Supporting source: Cloud network and topology requirements — https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html.

- Air-gapped operation: Documented. The air-gap guide mirrors charts and images using Skopeo/zstd, transfers them and deploys from an internal registry. Its example versions are older than the current 5.6 line; resolve matching current application/chart/scanner versions and arrange offline vulnerability-database updates. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/5.6/en/airgap.html (reviewed 2026-11-18).

- Deployment artifact / IaC: Documented. NeuVector maintains a Helm chart for manager/controller/enforcer/scanner deployment. The reviewed chart release is v2.11.4, separate from application v5.6.4. Pin image tags and check values/privileges; air-gap documentation’s historical chart example is not a current version pin. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/latest/en/helm.html (reviewed 2026-11-18). Deployment artifact: https://github.com/neuvector/neuvector-helm/releases/tag/v2.11.4. Artifact reference: NeuVector Helm chart v2.11.4.

- Minimum footprint / sizing: Documented. The requirements recommend three controllers for HA, an enforcer on each worker and separate scanner/manager resources. Controller minimum is 1 CPU/2 GB; an enforcer needs 1+ CPU/1 GB and a scanner 1 CPU/2 GB before workload growth. The public-cloud guide warns against multiple managers behind a load balancer because of session state, while requirements suggest manager redundancy; resolve that design before claiming full HA. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://documentation.suse.com/cloudnative/security/5.6/en/requirements.html (reviewed 2026-11-18). Supporting source: Manager scaling caveat and cloud topology — https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html.

- License pricing: Documented. Upstream NeuVector is Apache 2.0 licensed. SUSE subscription-delivered images, support and Rancher Prime integrations may require commercial entitlements. The multi-product AWS order is distinct from the free upstream code licence. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://github.com/neuvector/neuvector/blob/main/LICENSE (reviewed 2026-11-18). Supporting source: SUSE commercial procurement path — https://documentation.suse.com/cloudnative/security/5.6/en/awsmarketplace.html.

- Operating cost estimate: Sources checked — unresolved. Size by protected Kubernetes node count, network throughput, container/image scan volume, registry retention and HA controller/scanner design, not directory users. Include per-node enforcers, scan capacity, persistent configuration and any SUSE support subscription. The manager redundancy conflict also needs resolution. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://documentation.suse.com/cloudnative/security/5.6/en/requirements.html (reviewed 2026-11-18). Supporting source: Current AWS Linux EC2 rates; workload/topology still required — https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json. Supporting source: Storage performance and charging inputs — https://aws.amazon.com/ebs/pricing/.

- Release snapshot / cadence: Documented. NeuVector v5.6.4 was published October 27, 2026; chart v2.11.4 is a separate release. When upgrading from before v5.6.0, SUSE requires restarting/redeploying existing scanner pods for critical CVE severity handling. Maintenance releases on older branches are not a newer major-line snapshot. Scope: SUSE Security (NeuVector): selected customer-operated edition. Source: https://github.com/neuvector/neuvector/releases/tag/v5.6.4 (reviewed 2026-11-18). Supporting source: 5.6.4 upgrade and scanner requirements — https://documentation.suse.com/cloudnative/security/5.6/en/5x.html. Supporting source: Separate chart release — https://github.com/neuvector/neuvector-helm/releases/tag/v2.11.4.




### Security and lifecycle reviews

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

- NeuVector scanner restart required for critical-severity results (security-advisory): SUSE requires existing scanner pods to restart or redeploy when upgrading from before 5.6.0 to 5.6.4 or later, so cached capabilities recognize critical CVE severity. Scope: Upgrades from pre-5.6.0 controllers with existing scanner pods; not a claim of a new exploitable vulnerability in every NeuVector installation. Conditions: Older scanners cache the controller capability response. SUSE also calls for current scanner/CVE database content for PHP vulnerability checks. Action: Follow the 5.6.4 scanner restart and database-update instructions, including the transfer process in isolated environments. Source: https://documentation.suse.com/cloudnative/security/5.6/en/5x.html; reviewed 2026-11-18.




## WordPress Self-Hosted

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

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

### Scope and qualifications

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

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

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


### Category fit

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

### Deployment boundaries


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

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

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

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

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

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

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


### Cloud deployment evidence

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

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

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

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

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

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

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


### Community and maintenance

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

Reviewed 2026-11-18.

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

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

### Sources

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

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

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

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

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

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

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

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

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

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

### Licensing sources

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

### Infrastructure sources

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

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


### Buyer diligence


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

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


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

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

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

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

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

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

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

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

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

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

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

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




### Security and lifecycle reviews

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

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

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




## YugabyteDB Anywhere

Commercial self-managed database-as-a-service control plane for YugabyteDB clusters.

- Listing: https://launchinyourcloud.com/directory/yugabytedb-anywhere/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial installed-software license; YugabyteDB core components have separate source licenses.
- Licensing model: commercial-only
- Installation: Installer or Helm deployment, followed by customer-cloud provider configuration
- Architecture: Customer-operated management control plane and distributed database universe nodes
- Operations: Customer operates YugabyteDB Anywhere and its database nodes while the software automates provisioning, scaling, backups and upgrades.
- Product website: https://www.yugabyte.com/yugabytedb-anywhere/
- Source review: 2026-11-14; cloud review: 2026-11-14; licensing review: 2026-11-14; infrastructure review: 2026-11-14

### Scope and qualifications

This entry covers YugabyteDB Anywhere, not the managed YugabyteDB Aeon service or a manual deployment of only the open-source database. Cloud provider configurations require customer credentials, network access and supported machine images.

YugabyteDB Anywhere is commercial installed software. The open-source YugabyteDB database and evaluation packages have separate terms and do not replace the production YBA entitlement.

YugabyteDB Anywhere and the database universe run as persistent control-plane and database-server workloads on VMs or Kubernetes.


### Category fit

- databases-vector: Provides a self-managed control plane for deploying and operating distributed YugabyteDB database clusters across customer cloud infrastructure.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/aws/ (checked 2026-11-14). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/azure/ (checked 2026-11-14). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/gcp/ (checked 2026-11-14). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/oci/ (checked 2026-11-14). 


### Cloud deployment evidence

- YugabyteDB Anywhere AWS provider (aws): https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/aws/
  Yugabyte documents customer AWS credentials, regions, networks and VM provisioning for YBA-managed database universes.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- YugabyteDB Anywhere Azure provider (azure): https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/azure/
  Yugabyte documents customer Azure subscription credentials, resource groups, networks and VM provisioning for YBA-managed universes.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- YugabyteDB Anywhere Google Cloud provider (gcp): https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/gcp/
  Yugabyte documents customer GCP service accounts, projects, regions and instance provisioning for YBA-managed universes.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- YugabyteDB Anywhere OCI provider (oci): https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/oci/
  Yugabyte documents customer OCI credentials, regions, availability domains and VM provisioning for YBA-managed universes.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.


### Sources

- YugabyteDB Anywhere overview: https://docs.yugabyte.com/stable/yugabyte-platform/

- Provider configurations: https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/

- Deployment planning: https://docs.yugabyte.com/stable/yugabyte-platform/create-deployments/create-universes-overview/

- Installed software license terms: https://www.yugabyte.com/legal/installed-software-terms/

### Licensing sources

- https://www.yugabyte.com/legal/installed-software-terms/

- https://docs.yugabyte.com/stable/faq/general/

### Infrastructure sources

- https://docs.yugabyte.com/stable/yugabyte-platform/

- https://docs.yugabyte.com/stable/yugabyte-platform/prepare/


### 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. YugabyteDB Anywhere documents OIDC authentication for its management console with IdP/client configuration and user/role mapping. This is management-platform SSO, distinct from database-user OIDC and from the vendor-operated Aeon service. Scope: YugabyteDB Anywhere administrator console; database identities separate. Source: https://docs.yugabyte.com/stable/yugabyte-platform/administer-yugabyte-platform/oidc-authentication/ (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Documented. YBA documents manual database-release upload for air-gapped instances and additional software prerequisites for offline database nodes. Prepare dependencies and the management/data-plane network; this is not the default connected installation. Scope: Documented YBA offline release-management path. Source: https://docs.yugabyte.com/stable/yugabyte-platform/manage-deployments/ybdb-releases/ (reviewed 2026-11-14). Supporting source: Offline database-node prerequisites — https://docs.yugabyte.com/stable/yugabyte-platform/prepare/server-nodes-software/.

- Deployment artifact / IaC: Documented. The vendor YBA Installer deploys and manages YugabyteDB Anywhere using a downloaded release, YAML configuration and installer lifecycle commands. Provision the management host and permissions separately from database universe nodes; pin a supported release and configure storage, TLS and backups. Scope: YugabyteDB Anywhere management-platform installer, not the whole managed database estate. Source: https://docs.yugabyte.com/stable/yugabyte-platform/install-yugabyte-platform/install-software/installer/ (reviewed 2026-11-21). Deployment artifact: https://docs.yugabyte.com/stable/yugabyte-platform/install-yugabyte-platform/install-software/installer/. Artifact reference: Current stable vendor YBA Installer documentation.

- Minimum footprint / sizing: Documented. The YBA management-server VM requires 4 cores, 8 GB RAM and 215 GB disk on x86 Linux. Database universes run on separate nodes and need separate sizing; these figures are not a complete database footprint. Scope: YugabyteDB Anywhere management VM only; a license file is required. Source: https://docs.yugabyte.com/stable/yugabyte-platform/prepare/server-yba/ (reviewed 2026-11-14).

- License pricing: Documented. The installed-software terms explicitly include YugabyteDB Anywhere and license executable use under an Order Form with capacity metrics such as vCPU/CPU cores. Monitor contracted usage and review support, increases and renewal terms; the open-source database core licence is a different entitlement. Scope: April 2026 installed-software commercial terms for YugabyteDB Anywhere. Source: https://www.yugabyte.com/legal/installed-software-terms/ (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






