
# Software on Alibaba Cloud

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

Canonical page: https://launchinyourcloud.com/clouds/alibaba/
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: Alibaba Cloud account and resource group
- Provider group: cloud-infrastructure
- Provider classification: Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Source: https://www.alibabacloud.com/help/en/resource-management/resource-group/user-guide/create-a-resource-group (checked 2026-11-20).
- Network: VPC
- Identity and access: Resource Access Management (RAM)
- Installation guidance: Resource Orchestration Service (ROS) templates or Terraform; review the required RAM permissions.
- Guidance source: https://www.alibabacloud.com/help/en/ros/developer-reference/integration-overview
- Guidance reviewed: 2026-11-10


### Dedicated connectivity

Express Connect provides a dedicated on-premises-to-VPC connection. Confirm the access point, routing and application region separately from the deployment package.
Source: https://www.alibabacloud.com/help/en/express-connect/product-overview/what-is-express-connect (reviewed 2026-11-14).

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

16 listings.


## Apache Doris Self-Hosted

Apache-licensed analytical database with upstream AWS EKS/Alibaba ACK/ACS guides and a separately packaged cloudimg Azure VM path.

- Listing: https://launchinyourcloud.com/directory/apache-doris/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, alibaba, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for the core project; optional third-party components can carry separate or incompatible licenses.
- Licensing model: open-source
- Installation: Doris Operator on AWS EKS or Alibaba ACK/ACS, or cloudimg’s Azure VM image; pin application/operator/image versions separately
- Architecture: Customer-operated FE/BE services with persistent storage, through Kubernetes or a separately packaged single-node Azure VM.
- Operations: Customer manages the selected Kubernetes platform or Azure VM/OS, provider permissions, networking, persistent storage, database identities, backups, monitoring, scaling and upgrades. Upstream EKS/ACK/ACS instructions and the seller VM have different host and service boundaries.
- Product website: https://doris.apache.org/
- 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 Apache Doris, not a vendor-hosted derivative. Upstream guides document EKS and Alibaba ACK/ACS; ACS needs privileged BE initialization and has service/network constraints. The separate cloudimg Azure image packages Doris 4.0.6 with one FE/BE and is not HA. Its moving image and older application version require review; seller packaging does not establish Apache support. Review quorum, replication, storage and optional dependency licences for the chosen topology.

Apache Doris core is Apache-2.0 licensed. Optional third-party dependencies must be reviewed separately.

Doris runs persistent FE/BE database services on provisioned Kubernetes capacity or a separately packaged Azure VM/data disk. AWS EKS, Alibaba ACK/ACS and the single-node cloudimg VM have different initialization, redundancy and service constraints.


### Category fit

- data-analytics: Provides a massively parallel analytical database for real-time reporting and large-scale SQL analytics.

- databases-vector: Runs a persistent distributed analytical database on customer-controlled compute and storage.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://doris.apache.org/docs/4.x/install/deploy-on-kubernetes/doris-operator/on-aws/ (checked 2026-11-18). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://doris.apache.org/docs/4.x/install/deploy-on-kubernetes/doris-operator/on-alibaba/ (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudimg.co.uk/guides/apache-doris-on-ubuntu-24-04-azure/ (checked 2026-11-18). 


### Cloud deployment evidence

- Apache Doris on Amazon EKS (aws): https://doris.apache.org/docs/4.x/install/deploy-on-kubernetes/doris-operator/on-aws/
  The stable 4.x guide covers AWS EKS node/IAM preparation and links to Doris Operator for the application cluster. Review the full operator manifests and replica/storage design; the separate CloudFormation trial template is not HA.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- Apache Doris on Alibaba Cloud ACK/ACS (alibaba): https://doris.apache.org/docs/4.x/install/deploy-on-kubernetes/doris-operator/on-alibaba/
  The stable 4.x guide deploys a DorisCluster through Doris Operator on customer ACK or ACS, including private image registry, FE/BE resources and service/load-balancer configuration. ACS requires privileged mode for BE initialization; use ACK if that capability is unavailable.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- cloudimg Apache Doris VM in a customer Azure subscription (azure): https://www.cloudimg.co.uk/guides/apache-doris-on-ubuntu-24-04-azure/
  The seller documents subscription/resource group/VNet selection and the image URN cloudimg1647283583153:apache-doris-ubuntu-24-04:default:latest. It installs full FE/BE services with a dedicated disk, local administrator credentials and SQL/HTTP access. The guide packages 4.0.6 as a single-node deployment, not HA or an upstream support contract; resolve the moving image before use.
  Source type: third-party-package; reviewed: 2026-11-18; vendor support: not-assessed. Versions: Guide application 4.0.6; Azure image latest must be resolved.


### Community and maintenance

Apache Doris publishes its PMC/committer team and a named user catalog, including production analytics users, alongside current application releases. Governance/adoption does not establish a managed service’s customer-account boundary.

Reviewed 2026-11-18.

- Official maintenance and adoption evidence: https://doris.apache.org/community/team/

- Official maintenance and adoption evidence: https://doris.apache.org/users/

- Official maintenance and adoption evidence: https://github.com/apache/doris/releases/tag/4.1.5-release

### Sources

- Apache Doris 4.x AWS EKS preparation: https://doris.apache.org/docs/4.x/install/deploy-on-kubernetes/doris-operator/on-aws/

- Stable Doris Operator overview: https://doris.apache.org/docs/4.x/install/deploy-on-kubernetes/doris-operator/doris-operator-overview/

- Apache Doris license: https://github.com/apache/doris/blob/master/LICENSE.txt

- Apache Doris on Alibaba Cloud ACK/ACS: https://doris.apache.org/docs/4.x/install/deploy-on-kubernetes/doris-operator/on-alibaba/

- cloudimg full Azure deployment guide: https://www.cloudimg.co.uk/guides/apache-doris-on-ubuntu-24-04-azure/

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

### Licensing sources

- https://github.com/apache/doris/blob/master/LICENSE.txt

### Infrastructure sources

- https://doris.apache.org/docs/4.x/install/deploy-on-kubernetes/doris-operator/on-aws/

- https://doris.apache.org/docs/4.x/install/deploy-on-kubernetes/doris-operator/on-alibaba/

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


### 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. cloudimg publishes Azure VM offer cloudimg1647283583153.apache-doris-ubuntu-24-04, default plan. The seller guide and current public catalog identify Apache Doris 4.0.6, one FE and one BE, OpenJDK 17 and a dedicated data disk. This is a charged third-party package of Apache-licensed Doris, not VeloDB Cloud or an upstream support commitment. Resolve the exact image behind the moving latest URN and review upgrades; a single-node image is not an HA cluster. Scope: Third-party Azure VM package; US public-catalog availability and seller guide checked; not every region, version or production topology. Source: https://www.cloudimg.co.uk/guides/apache-doris-on-ubuntu-24-04-azure/ (reviewed 2026-11-18). Supporting source: Current seller product and Marketplace link — https://www.cloudimg.co.uk/products/apache-doris-on-ubuntu-24-04-lts-azure/. Supporting source: Provider public offer, plan and availability metadata — https://catalogapi.azure.com/offers/cloudimg1647283583153.apache-doris-ubuntu-24-04?api-version=2018-08-01-beta&market=US&language=en. Offer cloudimg1647283583153.apache-doris-ubuntu-24-04: cloudimg; Azure virtual-machine image; default plan; package Guide application 4.0.6; moving latest image; https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.apache-doris-ubuntu-24-04.

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

- Single sign-on: Sources checked — unresolved. Version-4.x documentation describes custom pluggable authenticators for OIDC/JWT and BI-tool sign-on, while its authentication overview lists built-in passwords and LDAP. No reviewed ready-to-use, supported OIDC plugin/version is established here. Confirm the plugin, protocol and client handshake rather than treating the SPI as bundled SSO. Scope: 4.x custom authentication extension path; packaged federation unresolved. Source: https://doris.apache.org/docs/4.x/key-features/pluggable-auth/ (reviewed 2026-11-20). Supporting source: Built-in authentication scope — https://doris.apache.org/docs/4.x/admin-manual/auth/authentication-and-authorization/.

- SCIM provisioning: Sources checked — unresolved. Doris 4.x pluggable authentication, LDAP group mapping and Ranger authorisation do not establish an inbound SCIM endpoint. Confirm a current provisioning integration/artifact, user/group create/update/deactivate/delete behavior, SQL role mapping and active-session handling; authentication extension points alone do not settle lifecycle management. Scope: Apache Doris Self-Hosted: selected customer-operated edition. Source: https://doris.apache.org/docs/4.x/key-features/pluggable-auth/ (reviewed 2026-11-18).

- Compliance attestations: Sources checked — unresolved. Apache’s stable 4.x documentation establishes authentication and authorisation configuration, not an independent attestation for the customer’s Doris cluster. No current report/certificate with a relevant assessed boundary was established. Assess the actual FE/BE/operator, identity and data-source components and request the supplier/operating assurance the buyer requires. Scope: Apache Doris Self-Hosted: selected customer-operated edition. Source: https://doris.apache.org/docs/4.x/key-features/pluggable-auth/ (reviewed 2026-11-18).

- Security controls: Documented. Doris documents RBAC roles/grants, LDAP authentication, IP restrictions and configurable password policy. The password-policy default is not a hardened deployment guarantee; configure the selected controls and protect FE/BE endpoints. The Azure seller generates a per-VM root password and defaults the NSG to SSH only. Its overview says loopback binding while the plan says all interfaces: inspect listeners and NSG rules before enabling SQL/HTTP access. Scope: Apache Doris Self-Hosted: selected customer-operated edition. Source: https://doris.apache.org/docs/admin-manual/auth/authentication-and-authorization/ (reviewed 2026-11-18). Supporting source: Azure first-boot credentials and network defaults — https://www.cloudimg.co.uk/guides/apache-doris-on-ubuntu-24-04-azure/. Supporting source: Provider description/plan binding disagreement — https://catalogapi.azure.com/offers/cloudimg1647283583153.apache-doris-ubuntu-24-04?api-version=2018-08-01-beta&market=US&language=en.

- Air-gapped operation: Sources checked — unresolved. The 4.x guide explicitly warns that external LDAP/KDC/Ranger integrations are unsuitable when unreachable in an air-gapped cluster and recommends local accounts/RBAC. That is an identity-design constraint, not a complete offline lifecycle. Confirm all FE/BE/operator/OS artifacts, image mirroring, upgrades, backups and internal data-source dependencies for the selected stable release. Scope: Apache Doris Self-Hosted: selected customer-operated edition. Source: https://doris.apache.org/docs/4.x/key-features/pluggable-auth/ (reviewed 2026-11-18). Supporting source: Current operator/private-registry installation evidence — https://doris.apache.org/docs/4.x/install/deploy-on-kubernetes/doris-operator/doris-operator-overview/.

- Deployment artifact / IaC: Documented. Apache maintains Doris Operator for custom-resource deployment and lifecycle management, with AWS and Alibaba-specific preparation guides. Pin operator and FE/BE image versions separately. The AWS CloudFormation quickstart is explicitly a test/experience path with a single FE, not the HA reference. The separate Azure image uses the moving URN cloudimg1647283583153:apache-doris-ubuntu-24-04:default:latest; resolve and pin its image version. Scope: Apache Doris Self-Hosted: selected customer-operated edition. Source: https://doris.apache.org/docs/4.x/install/deploy-on-kubernetes/doris-operator/doris-operator-overview/ (reviewed 2026-11-18). Supporting source: Version 4.x AWS preparation — https://doris.apache.org/docs/4.x/install/deploy-on-kubernetes/doris-operator/on-aws/. Supporting source: Version 4.x Alibaba ACK/ACS preparation — https://doris.apache.org/docs/4.x/install/deploy-on-kubernetes/doris-operator/on-alibaba/. Supporting source: Testing-only CloudFormation limitations — https://doris.apache.org/docs/dev/install/deploy-on-cloud/doris-on-aws/. Supporting source: Upstream operator artifact repository — https://github.com/apache/doris-operator. Supporting source: Azure image URN and CLI deployment — https://www.cloudimg.co.uk/guides/apache-doris-on-ubuntu-24-04-azure/.

- Minimum footprint / sizing: Documented. The stable 4.x hardware guide gives FE memory minimum 16 GB and recommended 64 GB+, and BE memory of CPU cores × 4 GB minimum and × 8 GB recommended. It recommends SSDs, ext4/xfs and 10 Gb networking. Set FE quorum, BE replication, compression and compaction reserve explicitly; a single-FE trial is not HA. cloudimg instead suggests Standard_B4ms (4 vCPU/16 GiB) for its single-node appliance; this is not the upstream production/HA sizing baseline. Scope: Apache Doris Self-Hosted: selected customer-operated edition. Source: https://doris.apache.org/docs/4.x/install/preparation/env-checking/ (reviewed 2026-11-18). Supporting source: Separate Azure appliance sizing — https://www.cloudimg.co.uk/guides/apache-doris-on-ubuntu-24-04-azure/.

- License pricing: Documented. Apache Doris is Apache 2.0 licensed. Review optional dependencies and distribution components under their own notices. Vendor-hosted derivatives, commercial support and marketplace repackaging have separate terms. The reviewed Azure default plan charges USD 0.04/vCPU-hour for cloudimg packaging/support (USD 0.16/hour at four vCPUs), plus Azure infrastructure; the upstream Apache licence stays free. Scope: Apache Doris Self-Hosted: selected customer-operated edition. Source: https://github.com/apache/doris/blob/master/LICENSE.txt (reviewed 2026-11-18). Supporting source: Exact Azure plan and per-core meters — https://catalogapi.azure.com/offers/cloudimg1647283583153.apache-doris-ubuntu-24-04?api-version=2018-08-01-beta&market=US&language=en.

- Operating cost estimate: Sources checked — unresolved. Specify ingestion rate, query concurrency, indexes, compression, replica count, FE quorum, BE count, compaction reserve and storage-compute mode. One TB raw data and 100 users do not determine usable replicated storage, IOPS or an HA compute bill. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://doris.apache.org/docs/4.x/install/preparation/env-checking/ (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. Apache Doris 4.1.5-release was published October 15, 2026. This application release is separate from the date/version of Doris Operator. Use stable documentation and verify operator/application compatibility; dev documentation describes unreleased behavior. cloudimg’s Azure guide/plan packages 4.0.6; it is separate from this 4.1.5-release snapshot and the resolved image version. Scope: Apache Doris Self-Hosted: selected customer-operated edition. Source: https://github.com/apache/doris/releases/tag/4.1.5-release (reviewed 2026-11-18). Supporting source: Older Azure packaged application — https://catalogapi.azure.com/offers/cloudimg1647283583153.apache-doris-ubuntu-24-04?api-version=2018-08-01-beta&market=US&language=en.







## Dify Self-Hosted

Visual AI application and RAG workflow platform available as a self-hosted container stack.

- Listing: https://launchinyourcloud.com/directory/dify/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: alibaba
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Modified Apache 2.0 terms; multi-workspace service operation and frontend branding can require commercial authorization.
- Licensing model: source-available
- Installation: Official Docker Compose deployment; pin a release and configure its required services.
- Architecture: Customer-operated application, workers, PostgreSQL and vector-store services
- Operations: Customer operates the containers, persistent stores, secrets, backups and upgrades; commercial edition support varies.
- Product website: https://dify.ai/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Self-hosting Dify does not itself host every model used by a flow. Model-provider plugins, embedding services, tools and connectors may send inputs or retrieved content outside the deployment. Select local endpoints where required and review each dependency. This entry does not conflate the generic self-hosted stack with the separately licensed AWS Premium edition. Dify 1.20.0 changes deployment and API behavior: OPENAPI_ENABLED defaults to true, shared.env is retired, six migrations apply from 1.19, and HITL, plugin-daemon, OpenShell, and optional file-scanning requirements change. It also fixes OAuth callback reuse, member-role enforcement, vector deletion scope, public stream detail exposure, and CVE-2026-116591.

Classified here as source-available because the upstream license modifies Apache 2.0 with multi-workspace service and frontend-branding conditions. Some uses require separate commercial authorization; this is not an unmodified Apache-licensed core.

Docker Compose runs application services, workers and persistent database/vector-store containers on a host. This is provisioned server/container infrastructure; using a managed external model does not make this platform serverless.


### Category fit

- ai-applications-rag: Visual application, agent-workflow and retrieval-augmented generation platform. The application platform is deployable; selected models and plugins are separate dependencies.

- ai-tools: Visual AI application and RAG workflow platform available as a self-hosted container stack.

### Deployment boundaries


- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.alibabacloud.com/help/en/openapi/integrating-openapi-mcp-server-in-dify (checked 2026-11-12). Source: https://help.aliyun.com/en/compute-nest/use-cases/dify-community-edition-service-instance-deployment-document (checked 2026-11-12). 


### Cloud deployment evidence

- Dify Docker deployment on Alibaba Cloud ECS (alibaba): https://www.alibabacloud.com/help/en/openapi/integrating-openapi-mcp-server-in-dify
  Alibaba Cloud documents cloning upstream Dify and running its Docker deployment on a customer ECS instance. The example then integrates an MCP server; model providers and other outbound integrations must be reviewed separately.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.

- Dify Community Edition full application on Alibaba Compute Nest (alibaba): https://help.aliyun.com/en/compute-nest/use-cases/dify-community-edition-service-instance-deployment-document
  Alibaba documents a Dify Community Edition service instance that creates ECS compute in the customer-selected VPC, zone and region, then exposes the installed Dify application for administrator registration. This is application hosting rather than an MCP/model connector, and is separate from the licensed Dify AWS Premium offering. Review model endpoints and release compatibility.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Docker Compose deployment: https://docs.dify.ai/en/self-host/deploy/quick-start/docker-compose

- Application capabilities and integrations: https://github.com/langgenius/dify

- Current license and additional conditions: https://github.com/langgenius/dify/blob/main/LICENSE

- Dify Community Edition full application on Alibaba Compute Nest: https://help.aliyun.com/en/compute-nest/use-cases/dify-community-edition-service-instance-deployment-document

- Dify 1.20.0 release: https://github.com/langgenius/dify/releases/tag/1.20.0

### Licensing sources

- https://github.com/langgenius/dify/blob/main/LICENSE

### Infrastructure sources

- https://docs.dify.ai/en/self-host/deploy/quick-start/docker-compose


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. SAML, OIDC and OAuth2 SSO appear in the self-hosted Enterprise feature comparison and are enabled by an Enterprise licence. This does not establish those features for an unlicensed Community installation; confirm identity-provider and end-user/admin coverage. Scope: Self-hosted Enterprise licence; Community differs. Source: https://dify.ai/pricing/dify-enterprise (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: Dify 1.20.0 fixes OAuth callback reuse, member-role enforcement, vector deletion scope, public stream detail exposure, CVE-2026-116591, and security dependencies. Apply the 1.20.0 migrations and configuration changes, or a later supported release, and retest authentication and public endpoints. Scope: Upstream Dify 1.20.0 release; consult its linked advisories for component-specific ranges.. Source: https://github.com/langgenius/dify/releases/tag/1.20.0 (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream Compose file is generated from its template and environment configuration. Use a consistent release checkout rather than mixing generated files or dependency settings across releases. Scope: Upstream multi-service deployment; models and integrations need separate configuration. Source: https://github.com/langgenius/dify/blob/main/docker/docker-compose.yaml (reviewed 2026-11-14). Deployment artifact: https://github.com/langgenius/dify/blob/main/docker/docker-compose.yaml. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The Compose quickstart specifies at least 2 CPU cores and 4 GiB RAM. The selected database, vector store, models and workload may require more resources. Scope: Quickstart application stack; not model-serving or production HA sizing. Source: https://docs.dify.ai/en/self-host/deploy/quick-start/docker-compose (reviewed 2026-11-14).

- License pricing: Documented. Dify uses modified Apache-2.0 terms, with additional conditions for multi-tenant workspaces and frontend branding. Certain uses require a commercial licence. Do not treat it as unmodified Apache-2.0; Enterprise, support and model-provider charges are separate. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/langgenius/dify/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Dify 1.20.0 was published November 18, 2026. It includes six migrations from 1.19, retires shared.env, changes OPENAPI_ENABLED and HITL behavior, and requires review of plugin-daemon, OpenShell, and file-scanning configuration. Scope: Upstream Dify self-hosted 1.20 release. Source: https://github.com/langgenius/dify/releases/tag/1.20.0 (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- Dify 1.20.0 security update (security-advisory): Dify 1.20.0 fixes OAuth callback reuse, member-role enforcement, vector deletion scope, public stream detail exposure, CVE-2026-116591, and security dependencies. Scope: Upstream Dify 1.20.0 release; consult its linked advisories for component-specific ranges. Conditions: Exposure depends on enabled OAuth, public application streams, role configuration, vector stores, and affected dependencies. Action: Apply the 1.20.0 migrations and configuration changes, or a later supported release, and retest authentication and public endpoints. Source: https://github.com/langgenius/dify/releases/tag/1.20.0; reviewed 2026-11-18.




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







## FileRun

Commercial self-hosted file management and sharing platform.

- Listing: https://launchinyourcloud.com/directory/filerun/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, alibaba
- 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: Application platform deployment; Docker / Compose
- Architecture: FileRun application and database on a Websoft9 customer-cloud VM.
- 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://support.websoft9.com/en/docs/filerun/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The application package sits on a separately installed Websoft9 platform. FileRun annual subscriptions and licensed domain terms are separate from platform and cloud bills.

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

FileRun application and database on a Websoft9 customer-cloud VM. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Commercial self-hosted file management and sharing platform.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://support.websoft9.com/en/docs/filerun/ (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://support.websoft9.com/en/docs/filerun/ (checked 2026-11-19). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://support.websoft9.com/en/docs/filerun/ (checked 2026-11-19). 


### Cloud deployment evidence

- Websoft9 FileRun (aws, azure, alibaba): https://support.websoft9.com/en/docs/filerun/
  FileRun application and database on a Websoft9 customer-cloud VM. The application package sits on a separately installed Websoft9 platform. FileRun annual subscriptions and licensed domain terms are separate from platform and cloud bills.
  Source type: third-party-package; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Websoft9 FileRun: https://support.websoft9.com/en/docs/filerun/

- Websoft9 AWS: https://support.websoft9.com/en/docs/install-aws/

- Websoft9 Azure: https://support.websoft9.com/en/docs/install-azure/

- Websoft9 Alibaba: https://support.websoft9.com/en/docs/install-alibabacloud/

- FileRun Pricing & Terms: https://filerun.com/pricing

- FileRun 2026 Updates: https://docs.filerun.com/api_2026_3_changes

### Licensing sources

- https://filerun.com/pricing

### Infrastructure sources

- https://support.websoft9.com/en/docs/filerun/


### 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. Current FileRun ships OpenID Connect and OAuth2 plugins, with SAML available through SimpleSAMLphp. Only one authentication plugin can be active at once; test its configuration and review local-superuser exceptions and licence entitlement. Scope: FileRun 2026.3 authentication plugins. Source: https://docs.filerun.com/authentication_integration (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official Docker guide publishes Compose YAML for FileRun and MariaDB with persistent directories, and optional Tika/Elasticsearch. Its application image floats; pin a compatible release, replace example secrets and configure HTTPS and backups. Scope: Official self-hosted Compose recipe; not HA. Source: https://docs.filerun.com/docker (reviewed 2026-11-20). Deployment artifact: https://docs.filerun.com/docker. Artifact reference: Moving documentation; select a versioned application image.

- Minimum footprint / sizing: Sources checked — unresolved. The current guide gives a PHP floor of 20 MB per request and a 256-MB Docker PHP limit, with database memory additional. The Docker guide requires at least 2 GB for optional Elasticsearch. It does not establish total CPU/RAM sizing for a production or HA workload; previews and indexing materially change capacity. Scope: FileRun 2026.3 component guidance; total production minimum unresolved. Source: https://docs.filerun.com/requirements (reviewed 2026-11-20). Supporting source: Optional indexing memory — https://docs.filerun.com/docker.

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

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




## Matomo On-Premise

Self-hosted web analytics with visitor, campaign and website reporting on customer servers.

- Listing: https://launchinyourcloud.com/directory/matomo/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, alibaba
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GPLv3-or-later core; premium plugins use separate commercial EULA and subscription terms
- Licensing model: open-source
- Installation: PHP web-server installation or official Docker image
- Architecture: Customer-operated analytics application and MySQL/MariaDB database with scheduled report processing
- Operations: Customer manages hosting, upgrades, security, backups, tracking configuration and scheduled report processing.
- Product website: https://matomo.org/
- 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 covers Matomo On-Premise rather than Matomo Cloud. Core analytics can be self-hosted, while premium capabilities and support may require separate purchases. Configure collection, consent and retention deliberately rather than treating the deployment model as a privacy-compliance guarantee.

Matomo On-Premise combines a GPLv3 core and open-source plugins with separately licensed commercial premium plugins. Premium plugin source and redistribution rights are governed by the InnoCraft EULA rather than the core GPL license.

Official installation runs on a web/shared/dedicated server with a database, or using the official Docker image. Higher-volume reporting uses a scheduled cron task rather than an event-driven application runtime.


### Category fit

- web-analytics: Website traffic, campaign and behavior analytics on customer-controlled servers; premium analytics plugins have separate commercial licensing.

- data-analytics: Website analytics and reporting over collected visitor and event data; scope is web measurement rather than a general data warehouse.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://matomo.org/faq/how-to-install/faq_31411/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://matomo.org/faq/how-to-install/faq_31411/ (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://matomo.org/faq/how-to-install/faq_31411/ (checked 2026-11-12). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://matomo.org/faq/how-to-install/faq_31411/ (checked 2026-11-12). 


### Cloud deployment evidence

- Matomo named-cloud compatibility FAQ (aws, azure, gcp, alibaba): https://matomo.org/faq/how-to-install/faq_31411/
  The vendor explicitly confirms Matomo On-Premise compatibility with AWS, Azure, Google Cloud and Alibaba Cloud, and links its installation requirements. This is a compatibility statement, not a cloud-provider certification or a managed Matomo Cloud offering.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- On-Premise product scope: https://matomo.org/matomo-on-premise/

- Official installation instructions: https://matomo.org/faq/on-premise/installing-matomo/

- Core and premium plugin licenses: https://matomo.org/faq/general/matomo-analytics-licences-for-core-tracker-and-plugins/

- Core legal notice: https://raw.githubusercontent.com/matomo-org/matomo/5.x-dev/LEGALNOTICE

- Licensing and edition terms: https://matomo.org/faq/general/faq_22573/

### Licensing sources

- https://matomo.org/faq/general/matomo-analytics-licences-for-core-tracker-and-plugins/

- https://matomo.org/faq/general/faq_22573/

- https://raw.githubusercontent.com/matomo-org/matomo/5.x-dev/LEGALNOTICE

### Infrastructure sources

- https://matomo.org/faq/on-premise/installing-matomo/


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. On-premises SAML uses the paid LoginSAML premium feature from Matomo Marketplace. Provider setup and user provisioning options require configuration; this is separate from a Matomo Cloud subscription. Scope: Self-hosted Matomo with LoginSAML premium feature. Source: https://matomo.org/faq/general/set-up-login-with-saml-authentication/ (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Matomo-maintained Docker repository supplies application/web-server and database examples. Persistent data, TLS, scheduled archiving and plugin/edition choices require deployment-specific configuration. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://github.com/matomo-org/docker (reviewed 2026-11-14). Deployment artifact: https://github.com/matomo-org/docker. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Documented. For up to 100k monthly page views the vendor suggests one server with 2 CPUs, 2 GB RAM and 50 GB SSD; at 1 million, 4 CPUs, 8 GB and 250 GB SSD. Larger workloads separate database and application roles. Tracking requests, segments and retention govern sizing; 100 internal users and 1 TB alone do not define an HA analytics workload. Scope: On-premises traffic-tier recommendations; not a benchmark or total operating-cost estimate. Source: https://matomo.org/faq/on-premise/matomo-requirements/ (reviewed 2026-11-20).

- License pricing: Documented. The On-Premise core is free to download under GPLv3; premium plugins and support have separate commercial terms. The paid LoginSAML feature is not implied by the free core. Select the plugin/site entitlements and current quote separately from server and operations costs. Scope: Core versus commercial plugin software terms; excludes Matomo Cloud and infrastructure. Source: https://matomo.org/faq/general/matomo-analytics-licences-for-core-tracker-and-plugins/ (reviewed 2026-11-20). Supporting source: On-Premise product and free core — https://matomo.org/matomo-on-premise/.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was 5.14.2, published 2026-10-22. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream matomo-org/matomo release record; commercial editions and deployment packages may differ. Source: https://github.com/matomo-org/matomo/releases/tag/5.14.2 (reviewed 2026-11-14).







## MaxKB Community Edition

Open-source knowledge-base, RAG and agent-workflow platform deployable into an Alibaba Cloud account.

- Listing: https://launchinyourcloud.com/directory/maxkb-community/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: alibaba
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU General Public License version 3 for Community Edition. Professional and Enterprise editions add separately licensed features and support.
- Licensing model: open-source
- Installation: Create the documented MaxKB Community Edition service instance through Alibaba Cloud Compute Nest, or use the publisher-documented Alibaba Cloud Marketplace image on a customer ECS server.
- Architecture: Customer-operated MaxKB application with PostgreSQL and pgvector storage on an Alibaba Cloud ECS host
- Operations: Customer manages the ECS host, VPC and security-group exposure, administrator credentials, persistent PostgreSQL data, backups, upgrades, capacity and credentials for model and tool integrations.
- Product website: https://www.maxkb.cn/
- Source review: 2026-11-19; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

The Compute Nest deployment requires RAM permissions with full access to ECS, VPC and ROS plus Compute Nest user access; review and reduce deployment privileges after provisioning where practical. Community Edition is single-tenant, x86-64 only and supports single-node or cold-standby deployment rather than Enterprise clustering. RBAC, SSO, audit logs, open API access, conversation-user authorization and several enterprise integrations are reserved for paid editions. Current upstream v2 installation guidance calls for at least 4 CPU cores, 8 GB RAM and 100 GB of disk, exposes the web service on port 8080 and supplies default administrator credentials that must be changed immediately. The publisher recommends offline installation for production and requires a database backup before upgrades. Public or separately hosted model, embedding, reranking and tool providers can receive application data even when MaxKB itself runs in the customer account. The current upstream v2 container image and persistence paths differ from the legacy English guide; check the release packaged by the cloud installer before applying upstream configuration or upgrades. MaxKB v2.10.9-lts fixes multiple cross-workspace access and deletion flaws, stored XSS with account-takeover impact, custom-tool secret exposure, SSRF paths including possible cloud-credential theft, anonymous provider API-key disclosure and unauthorized conversation or knowledge-base access. Upgrade the LTS line and retest workspace, tool and provider boundaries.

This listing is scoped to the GPLv3 Community Edition. Professional and Enterprise editions add commercially licensed X-Pack capabilities, deployment options and vendor support; their entitlements are not implied by this classification.

Alibaba Compute Nest provisions the Community Edition on customer-selected ECS capacity, VPC, VSwitch, zone and region. The application and its persistent PostgreSQL/pgvector data run as provisioned server workloads rather than a serverless or vendor-managed service.


### Category fit

- ai-applications-rag: Self-hosted knowledge ingestion, document vectorization, RAG, question-answering and agent-workflow platform with configurable model providers.

- ai-tools: Customer-hosted agent and workflow platform with knowledge bases, MCP and tool integrations, and configurable language, embedding, reranking and multimodal models.

### Deployment boundaries


- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.aliyun.com/en/compute-nest/use-cases/maxkb-community-edition-service-instance-deployment-document (checked 2026-11-16). Source: https://docs.maxkb.pro/installation/aliyun/ (checked 2026-11-16). 


### Cloud deployment evidence

- MaxKB Community Edition service instance in Alibaba Compute Nest (alibaba): https://help.aliyun.com/en/compute-nest/use-cases/maxkb-community-edition-service-instance-deployment-document
  Alibaba Cloud documents creation of a MaxKB Community Edition service instance in a customer-selected region, zone, VPC and VSwitch using customer-selected ECS capacity and billing. The deployed application is reached through the ECS public address on port 8080. The workflow requires broad ECS, VPC, ROS and Compute Nest permissions and returns default administrator credentials that must be changed.
  Source type: provider-guide; reviewed: 2026-11-16; vendor support: not-assessed.

- MaxKB image deployment from Alibaba Cloud Marketplace (alibaba): https://docs.maxkb.pro/installation/aliyun/
  The publisher documents selecting the MaxKB image while purchasing an Alibaba Cloud server, starting the image and opening port 8080 in the customer's security group. It recommends at least 4 CPU cores and 8 GB RAM and instructs administrators to replace the default password after first login.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.


### Community and maintenance

The official repository publishes an active versioned release stream and public contribution, code-of-conduct and security workflows. This establishes public project maintenance but does not certify any adopter's hosting topology.

Reviewed 2026-11-16.

- Upstream project and contribution workflow: https://github.com/1Panel-dev/MaxKB

- Current upstream releases: https://github.com/1Panel-dev/MaxKB/releases

### Sources

- Alibaba Compute Nest Community Edition deployment: https://help.aliyun.com/en/compute-nest/use-cases/maxkb-community-edition-service-instance-deployment-document

- Publisher Alibaba Cloud Marketplace deployment guide: https://docs.maxkb.pro/installation/aliyun/

- Upstream platform capabilities and technical stack: https://github.com/1Panel-dev/MaxKB

- Online container installation and requirements: https://docs.fit2cloud.com/maxkb/installation/online_installtion/

- Production-oriented offline installation and upgrade guidance: https://docs.fit2cloud.com/maxkb/installation/offline_installtion/

- Community, Professional and Enterprise edition comparison: https://www.maxkb.cn/price

- Community Edition GPLv3 license: https://github.com/1Panel-dev/MaxKB/blob/v2/LICENSE

- MaxKB v2.10.9-lts release: https://github.com/1Panel-dev/MaxKB/releases/tag/v2.10.9-lts

- MaxKB GHSA-5545-9jgw-jg2g: https://github.com/1Panel-dev/MaxKB/security/advisories/GHSA-5545-9jgw-jg2g

- MaxKB GHSA-mgph-cpg8-q442: https://github.com/1Panel-dev/MaxKB/security/advisories/GHSA-mgph-cpg8-q442

### Licensing sources

- https://github.com/1Panel-dev/MaxKB/blob/v2/LICENSE

- https://www.maxkb.cn/price

### Infrastructure sources

- https://help.aliyun.com/en/compute-nest/use-cases/maxkb-community-edition-service-instance-deployment-document

- https://docs.fit2cloud.com/maxkb/installation/online_installtion/

- https://github.com/1Panel-dev/MaxKB


### Buyer diligence


Research coverage: 8/12 fields (67%); 8 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: Documented. Alibaba Cloud documents a Community Edition Compute Nest service that creates an ECS-based deployment in the customer’s selected network. The vendor’s separately priced Marketplace Professional Edition is a different entitlement; its pricing does not price this Community listing. Scope: Provider-documented Community Compute Nest service; separate from the Professional Marketplace offer. Source: https://help.aliyun.com/en/compute-nest/use-cases/maxkb-community-edition-service-instance-deployment-document (reviewed 2026-11-16). Supporting source: Edition pricing and Professional Marketplace distinction — https://www.maxkb.cn/price.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Explicitly unsupported. The edition matrix excludes LDAP, OIDC, CAS, OAuth2 and SAML2 single sign-on from Community Edition and includes them in Professional/Enterprise. This does not establish SCIM provisioning. Scope: Community Edition only; commercial edition entitlements differ. Source: https://www.maxkb.cn/price (reviewed 2026-11-16).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. The edition matrix reserves full RBAC and system-operation logs for Professional/Enterprise. The online installer publishes default administrator credentials; replace them and configure access controls before exposing an instance. Current review: v2.10.9-lts fixes cross-workspace file and SKILL access/deletion, stored XSS with account-takeover impact, custom-tool secret exposure, multiple SSRF paths, anonymous provider API-key disclosure and unauthorized conversation or knowledge-base access. Upgrade and retest workspace and provider boundaries. Scope: MaxKB Community LTS; the release does not publish one universal affected-version range. Source: https://github.com/1Panel-dev/MaxKB/releases/tag/v2.10.9-lts (reviewed 2026-11-19). Supporting source: Prior security-controls source — https://www.maxkb.cn/price. Supporting source: Online installation and default account — https://docs.maxkb.pro/installation/online_installtion/. Supporting source: GHSA-5545-9jgw-jg2g — https://github.com/1Panel-dev/MaxKB/security/advisories/GHSA-5545-9jgw-jg2g. Supporting source: GHSA-mgph-cpg8-q442 — https://github.com/1Panel-dev/MaxKB/security/advisories/GHSA-mgph-cpg8-q442.

- Air-gapped operation: Documented. The v2 guide documents transferring a Community offline-installer archive, configuring it locally and applying offline upgrades after backups. That confirms offline application installation; models, embeddings, integrations and their dependencies must also be available inside the isolated environment. Scope: MaxKB v2 Community offline installation and upgrades; not a claim that external model APIs work disconnected. Source: https://docs.fit2cloud.com/maxkb/installation/offline_installtion/ (reviewed 2026-11-16).

- Deployment artifact / IaC: Documented. The current v2 guide uses registry.fit2cloud.com/maxkb/maxkb and persists data at /opt/maxkb. The English legacy guide uses different images/data paths; do not mix those configurations or assume compatibility with an older cloud package. Select and test a matching release. Scope: Current upstream v2 container example; untagged image is not an immutable release. Source: https://docs.fit2cloud.com/maxkb/installation/online_installtion/ (reviewed 2026-11-16). Supporting source: Versioned offline-installer example — https://docs.fit2cloud.com/maxkb/installation/offline_installtion/.

- Minimum footprint / sizing: Documented. The current v2 guide specifies at least 4 CPU cores, 8 GB RAM and 100 GB disk, with Docker 26+ recommended or the bundled Docker. Community package architecture and single-node/cold-standby limits follow the edition matrix; model hosting needs separate sizing. Scope: Community v2 application baseline, excluding model/GPU services and workload-specific capacity. Source: https://docs.fit2cloud.com/maxkb/installation/offline_installtion/ (reviewed 2026-11-16). Supporting source: Edition architecture/deployment matrix — https://www.maxkb.cn/price.

- License pricing: Documented. This listing is scoped to the GPLv3 Community Edition. Professional and Enterprise editions add commercially licensed X-Pack capabilities, deployment options and vendor support; their entitlements are not implied by this classification. Scope: MaxKB Community Edition: software license terms; infrastructure and operating costs are separate. Source: https://github.com/1Panel-dev/MaxKB/blob/v2/LICENSE (reviewed 2026-11-16). Supporting source: Edition and license conditions — https://www.maxkb.cn/price.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. MaxKB v2.10.9-lts was published November 19, 2026. It fixes cross-workspace authorization, stored XSS, secret exposure, SSRF, provider-key disclosure and unauthorized conversation or knowledge-base access issues. Scope: Upstream MaxKB Community LTS release; commercial editions and deployment packages may differ. Source: https://github.com/1Panel-dev/MaxKB/releases/tag/v2.10.9-lts (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/1Panel-dev/MaxKB/releases/tag/v2.10.8-lts.




### Security and lifecycle reviews

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

- MaxKB v2.10.9-lts security update (security-advisory): MaxKB v2.10.9-lts fixes cross-workspace authorization, stored XSS, secret exposure, SSRF, provider-key disclosure and unauthorized data access. Scope: MaxKB Community LTS; the release does not publish one universal affected-version range. Conditions: Workspace membership, custom tools, provider configuration, anonymous access and reachable metadata or internal services determine applicability. Action: Upgrade to v2.10.9-lts or later and retest workspace, tool, provider and anonymous-access boundaries. Source: https://github.com/1Panel-dev/MaxKB/releases/tag/v2.10.9-lts; reviewed 2026-11-19. Supporting source: GHSA-5545-9jgw-jg2g — https://github.com/1Panel-dev/MaxKB/security/advisories/GHSA-5545-9jgw-jg2g. Supporting source: GHSA-mgph-cpg8-q442 — https://github.com/1Panel-dev/MaxKB/security/advisories/GHSA-mgph-cpg8-q442.




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







## ONLYOFFICE Docs Enterprise

Commercial self-hosted office editing and real-time document collaboration server deployed as a cloud marketplace image.

- Listing: https://launchinyourcloud.com/directory/onlyoffice-docs-enterprise/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, alibaba
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary connection-based license with annual and lifetime purchase options
- Licensing model: commercial-only
- Installation: AWS Marketplace AMI or Alibaba Cloud Marketplace image
- Architecture: Preconfigured persistent Linux virtual server containing the office software and required components
- Operations: Customer operates the cloud instance, networking and integrations; software entitlement is purchased through a marketplace or directly from ONLYOFFICE.
- Product website: https://www.onlyoffice.com/docs-enterprise
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Docs Enterprise is an editing and collaboration server, not a complete file repository. It normally integrates with a separate content platform. Marketplace billing and direct annual or lifetime licensing are distinct procurement routes. The reviewed AWS x86 50-connection offer packages 9.4.0. This image version is separate from the current Docs website release banner, other connection tiers, ARM and Alibaba packages.

Docs Enterprise is proprietary commercial software licensed by concurrent connections; Community Server and other ONLYOFFICE products are separate scopes.

The complete Docs Enterprise server is delivered as a persistent customer-cloud virtual machine image.


### Category fit

- collaboration: Provides self-hosted browser-based office editing and real-time document co-authoring for integration with a content platform.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://helpcenter.onlyoffice.com/docs/installation/enterprise/hosted-solutions/install-ami (checked 2026-11-19). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://helpcenter.onlyoffice.com/docs/installation/enterprise/hosted-solutions/install-alibaba (checked 2026-11-19). 


### Cloud deployment evidence

- ONLYOFFICE Docs Enterprise AWS Marketplace AMI (aws): https://helpcenter.onlyoffice.com/docs/installation/enterprise/hosted-solutions/install-ami
  ONLYOFFICE documents launching the preconfigured Docs Enterprise AMI into the customer's AWS account and selecting its EC2 networking, storage and security settings.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed. Edition: Docs Enterprise.

- ONLYOFFICE Docs Enterprise Alibaba Cloud Marketplace image (alibaba): https://helpcenter.onlyoffice.com/docs/installation/enterprise/hosted-solutions/install-alibaba
  ONLYOFFICE documents creating the Docs Enterprise ECS instance from Alibaba Cloud Marketplace in the customer's account and configuring its region, network, storage and security settings.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed. Edition: Docs Enterprise.


### Sources

- Install ONLYOFFICE Docs Enterprise from AWS Marketplace: https://helpcenter.onlyoffice.com/docs/installation/enterprise/hosted-solutions/install-ami

- Install ONLYOFFICE Docs Enterprise from Alibaba Cloud Marketplace: https://helpcenter.onlyoffice.com/docs/installation/enterprise/hosted-solutions/install-alibaba

- ONLYOFFICE Docs Enterprise licensing FAQ: https://helpcenter.onlyoffice.com/docs/installation/enterprise/faq

- ONLYOFFICE Docs Enterprise pricing: https://www.onlyoffice.com/docs-enterprise-prices

- Exact reviewed AWS offer and package version: https://aws.amazon.com/marketplace/pp/prodview-m47ijkzvv34ea

### Licensing sources

- https://helpcenter.onlyoffice.com/docs/installation/enterprise/faq

- https://www.onlyoffice.com/docs-enterprise-prices

### Infrastructure sources

- https://helpcenter.onlyoffice.com/docs/installation/enterprise/hosted-solutions/install-ami

- https://helpcenter.onlyoffice.com/docs/installation/enterprise/hosted-solutions/install-alibaba


### Buyer diligence


Research coverage: 12/12 fields (100%); 3 documented, 9 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. ONLYOFFICE documents Docs Enterprise images in AWS Marketplace and Alibaba Cloud Marketplace. The customer launches the complete server image in its own account; verify the selected listing, seller, included connection entitlement and billing term. Scope: ONLYOFFICE Docs Enterprise: selected customer-operated edition. Source: https://helpcenter.onlyoffice.com/docs/installation/enterprise/hosted-solutions/install-ami (reviewed 2026-11-19). Supporting source: Alibaba Cloud Marketplace image — https://helpcenter.onlyoffice.com/docs/installation/enterprise/hosted-solutions/install-alibaba. Supporting source: Exact reviewed AWS offer and package version — https://aws.amazon.com/marketplace/pp/prodview-m47ijkzvv34ea. Offer prodview-m47ijkzvv34ea: Ascensio Systems Inc; x86 AMI; Docs Enterprise 50 simultaneous connections; package 9.4.0 (AMI package); https://aws.amazon.com/marketplace/pp/prodview-m47ijkzvv34ea.

- 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: ONLYOFFICE Docs Enterprise: selected customer-operated edition. Source: https://helpcenter.onlyoffice.com/docs/installation/enterprise/hosted-solutions/install-ami (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: ONLYOFFICE Docs Enterprise: selected customer-operated edition. Source: https://helpcenter.onlyoffice.com/docs/installation/enterprise/hosted-solutions/install-ami (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: ONLYOFFICE Docs Enterprise: selected customer-operated edition. Source: https://helpcenter.onlyoffice.com/docs/installation/enterprise/hosted-solutions/install-ami (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: ONLYOFFICE Docs Enterprise: selected customer-operated edition. Source: https://helpcenter.onlyoffice.com/docs/installation/enterprise/hosted-solutions/install-ami (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: ONLYOFFICE Docs Enterprise: selected customer-operated edition. Source: https://helpcenter.onlyoffice.com/docs/installation/enterprise/hosted-solutions/install-ami (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: ONLYOFFICE Docs Enterprise: selected customer-operated edition. Source: https://helpcenter.onlyoffice.com/docs/installation/enterprise/hosted-solutions/install-ami (reviewed 2026-11-19).

- Deployment artifact / IaC: Documented. Ascensio Systems publishes AWS offer prodview-m47ijkzvv34ea for Docs Enterprise, 50 simultaneous connections, with x86 AMI package version 9.4.0. This is one concrete marketplace artifact; other connection tiers, ARM offers, Alibaba images and direct licences are separate. A current Docs website banner does not establish this image’s version. Scope: AWS x86 Docs Enterprise 50-connection AMI offer; regional AMI selection remains part of launch. Source: https://aws.amazon.com/marketplace/pp/prodview-m47ijkzvv34ea (reviewed 2026-11-19). Deployment artifact: https://aws.amazon.com/marketplace/pp/prodview-m47ijkzvv34ea. Artifact reference: prodview-m47ijkzvv34ea; x86 AMI package 9.4.0; 50 simultaneous connections.

- 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: ONLYOFFICE Docs Enterprise: selected customer-operated edition. Source: https://helpcenter.onlyoffice.com/docs/installation/enterprise/hosted-solutions/install-ami (reviewed 2026-11-19).

- License pricing: Documented. ONLYOFFICE publishes connection-based Docs Enterprise annual and lifetime choices. Confirm the required simultaneous-connection tier, support, updates, marketplace billing and integration scope; infrastructure is separate. Scope: ONLYOFFICE Docs Enterprise: selected customer-operated edition. Source: https://www.onlyoffice.com/docs-enterprise-prices (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: ONLYOFFICE Docs Enterprise: selected customer-operated edition. Source: https://helpcenter.onlyoffice.com/docs/installation/enterprise/hosted-solutions/install-ami (reviewed 2026-11-19).

- Release snapshot / cadence: Sources checked — unresolved. The reviewed AWS x86 50-connection AMI is packaged as 9.4.0, while the Docs website advertises a newer application release. An exact application publication date, complete entitlement/upgrade bundle and equivalent Alibaba image snapshot were not established here. Keep the selected offer version separate from the general application banner. Scope: ONLYOFFICE Docs Enterprise: selected customer-operated edition. Source: https://aws.amazon.com/marketplace/pp/prodview-m47ijkzvv34ea (reviewed 2026-11-19).







## RAGFlow

Document processing and retrieval platform for building RAG and agentic knowledge applications.

- Listing: https://launchinyourcloud.com/directory/ragflow/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, alibaba, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream RAGFlow; models, data assets and dependencies retain their own terms.
- Licensing model: open-source
- Installation: Versioned upstream Docker Compose, provider-specific VM packages or community deployment templates; select a path compatible with the intended RAGFlow release.
- Architecture: Customer-operated document/retrieval application with deployment-specific stateful storage and configured model services
- Operations: Customer manages document storage, indexing, app services, access controls, model endpoints, backups and upgrades.
- Product website: https://ragflow.io/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Deployment options include customer AWS, Azure and Google Cloud infrastructure, Alibaba Compute Nest, and a Railway project. The evidence trail identifies the publishers and template versions. Hosting RAGFlow does not automatically self-host its LLM, embeddings or reranker; choose private or local model endpoints where required.

Apache License 2.0 for upstream RAGFlow; models, data assets and dependencies retain their own terms. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated document/retrieval application with deployment-specific stateful storage and configured model services. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- ai-applications-rag: Document understanding, knowledge ingestion and retrieval-augmented/agentic question answering with configurable LLM, embedding and reranking endpoints.

- ai-tools: Self-hosted document ingestion, retrieval and context infrastructure for AI applications.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/stdapi-ai/samples/tree/main/getting_started_ragflow (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudimg.co.uk/guides/ragflow-on-ubuntu-24-04-azure/ (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.techlatest.net/support/ragflow_support/gcp_gettingstartedguide/index.html (checked 2026-11-12). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.aliyun.com/en/compute-nest/use-cases/ragflow-community-edition-service-instance-deployment-document (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/ragflow-ai (checked 2026-11-12). Source: https://github.com/gridalpha/ragflow-railway/blob/main/Dockerfile (checked 2026-11-12). 


### Cloud deployment evidence

- Community RAGFlow deployment on AWS ECS Fargate through stdapi.ai (aws): https://github.com/stdapi-ai/samples/tree/main/getting_started_ragflow
  The sample provisions the RAGFlow application and workers, OpenSearch, Aurora PostgreSQL, Valkey, S3 and a Bedrock gateway in the customer AWS account. Source inspection confirms the v0.26.4 Python image pin; it does not establish compatibility with the 1.0 Go rewrite. This community integration also requires the separately billed stdapi.ai gateway and Bedrock access. Review its documented networking, client-security, availability and cost limitations before use.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed. Edition: Community / upstream open-source; third-party distribution where noted. Versions: 0.26.4.

- cloudimg RAGFlow Azure VM deployment and operations guide (azure): https://www.cloudimg.co.uk/guides/ragflow-on-ubuntu-24-04-azure/
  The image publisher documents an Azure VM in the customer subscription running the complete Compose stack, including Elasticsearch, MySQL, MinIO, Redis and a local embedding service. Its guide pins RAGFlow v0.26.4, not 1.0. This is a third-party repackaged image with additional support charges, not an upstream-endorsed distribution. Confirm image access, current patch/migration requirements, TLS configuration and the separately configured chat-model endpoint.
  Source type: third-party-package; reviewed: 2026-11-12; vendor support: not-assessed. Edition: Community / upstream open-source; third-party distribution where noted. Versions: 0.26.4.

- Techlatest RAGFlow VM deployment in a customer Google Cloud project (gcp): https://www.techlatest.net/support/ragflow_support/gcp_gettingstartedguide/index.html
  The image publisher documents selecting the customer project, deployment service account, zone, network and Compute Engine VM, then completing RAGFlow initialization and configuring its bundled Ollama models. This is a third-party packaged deployment; the guide does not establish a specific current RAGFlow release or 1.0 compatibility. Confirm the image version, support charges, model licenses, resource sizing and network exposure before use.
  Source type: third-party-package; reviewed: 2026-11-12; vendor support: not-assessed. Edition: Community / upstream open-source; third-party distribution where noted.

- RAGFlow Community deployment on Alibaba Cloud Compute Nest (alibaba): https://help.aliyun.com/en/compute-nest/use-cases/ragflow-community-edition-service-instance-deployment-document
  Alibaba Cloud documents provisioning a RAGFlow Community service instance with customer ECS, VPC and vSwitch parameters. This is distinct from the managed AI-Native Database Service integration. Review image version, access controls, model endpoints and the broad example RAM permissions before production.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed. Edition: Community / upstream open-source; third-party distribution where noted.

- Community RAGFlow Railway application stack (railway): https://railway.com/deploy/ragflow-ai
  This community template deploys the application, Elasticsearch, MySQL, Redis, a local embedding service and object storage into the customer Railway project. Its linked Dockerfile pins upstream RAGFlow v0.27.1 with a Railway startup/configuration wrapper. The template is not proof of 1.0 compatibility or upstream support; review migrations and the separately configured chat-model endpoint. Railway manages the underlying infrastructure.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed. Edition: Community / upstream open-source; third-party distribution where noted. Versions: 0.27.1.

- Railway deployment image source and release pin (railway): https://github.com/gridalpha/ragflow-railway/blob/main/Dockerfile
  Source inspection confirms the v0.27.1 base image and the custom configuration, nginx and startup wrapper used by the linked Railway template. The upstream 1.0 release changes the architecture and requires its documented migration path; do not substitute a new image tag without reviewing the complete stack.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed. Edition: Community / upstream open-source; third-party distribution where noted. Versions: 0.27.1.


### Community and maintenance

Current release notes document continued 2026 releases and dozens of named contributors across successive versions; the upstream README records a 1.0.0 release on 6 November 2026.

Reviewed 2026-11-10.

- Current releases and contributors: https://github.com/infiniflow/ragflow/releases

- Release chronology and deployment instructions: https://raw.githubusercontent.com/infiniflow/ragflow/main/README.md

### Sources

- Upstream project and capabilities: https://github.com/infiniflow/ragflow

- Current upstream license: https://raw.githubusercontent.com/infiniflow/ragflow/main/LICENSE

- RAGFlow 1.0 release and migration requirements: https://ragflow.io/docs/v1.0.0/release_notes

### Licensing sources

- https://raw.githubusercontent.com/infiniflow/ragflow/main/LICENSE

### Infrastructure sources

- https://github.com/infiniflow/ragflow


### 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: Sources checked — unresolved. A vendor maintainer identifies OAuth2/OIDC SSO in Enterprise, while the reviewed v1.0.0 Go deployment reference does not establish a supported federation configuration for that OSS release. Older OAuth configuration examples must not be assumed compatible with the new backend. Confirm edition, release and identity-provider configuration. Scope: RAGFlow v1.0 Go OSS versus Enterprise federation; current entitlement/configuration unresolved. Source: https://raw.githubusercontent.com/infiniflow/ragflow/v1.0.0/docker/README.md (reviewed 2026-11-20). Supporting source: Vendor-maintainer Enterprise SSO statement — https://github.com/infiniflow/ragflow/issues/15882.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The v1.0.0 Compose file includes a separate dependency configuration and reads its image selection from the release environment. Use the matching release configuration; this artifact does not establish a migration path or compatibility for older provider packages. Scope: Upstream v1.0.0 Compose; not evidence of compatibility with the listed 0.x provider packages. Source: https://github.com/infiniflow/ragflow/blob/v1.0.0/docker/docker-compose.yml (reviewed 2026-11-14). Deployment artifact: https://github.com/infiniflow/ragflow/blob/v1.0.0/docker/docker-compose.yml. Artifact reference: v1.0.0. Supporting source: Versioned RAGFlow 1.0.0 quickstart — https://ragflow.io/docs/v1.0.0/.

- Minimum footprint / sizing: Documented. The 1.0 quickstart recommends a starting point of 4 CPU cores, 16 GB RAM and 50 GB free disk. Models, document engines and concurrency can require more; this does not size the older third-party cloud packages. Scope: Upstream 1.0 quickstart; provider packages may target 0.x. Source: https://ragflow.io/docs/v1.0.0/ (reviewed 2026-11-14).

- License pricing: Documented. The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate. Model weights and external model APIs require their own review. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/infiniflow/ragflow/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v1.0.0, published 2026-11-06. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream infiniflow/ragflow release record; commercial editions and deployment packages may differ. Source: https://github.com/infiniflow/ragflow/releases/tag/v1.0.0 (reviewed 2026-11-14).







## Red Hat OpenShift Container Platform

Commercial self-managed Kubernetes application platform installed and operated in customer cloud accounts.

- Listing: https://launchinyourcloud.com/directory/openshift-container-platform/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, ibm, alibaba
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Red Hat OpenShift subscription.
- Licensing model: commercial-only
- Installation: OpenShift installation on AWS, Azure, Google Cloud or IBM Cloud; Assisted Installer Technology Preview on Alibaba Cloud
- Architecture: Customer-operated control-plane and worker machines with integrated operators, networking, storage and cluster services
- Operations: Customer manages cloud accounts, installer credentials, cluster machines, networking, identity, storage, registry, monitoring, backups, upgrades and Red Hat subscriptions.
- Product website: https://www.redhat.com/en/technologies/cloud-computing/openshift/container-platform
- Source review: 2026-11-15; cloud review: 2026-11-15; licensing review: 2026-11-15; infrastructure review: 2026-11-15

### Scope and qualifications

This entry covers self-managed OpenShift Container Platform, not OpenShift Dedicated, ROSA, Azure Red Hat OpenShift or other managed services. The installer can provision infrastructure or integrate with customer-provisioned resources; review credential scope, subscription entitlements and lifecycle support before installation. The documented Alibaba Cloud Assisted Installer path is Technology Preview, outside Red Hat production SLAs and not recommended for production.

The selected self-managed OpenShift Container Platform edition is delivered through a commercial Red Hat subscription with entitlement and support terms.

OpenShift Container Platform runs persistent control-plane and worker nodes plus integrated cluster operators and storage services in the customer cloud.


### Category fit

- backend-platforms: Provides a self-managed Kubernetes application platform with integrated operators, developer workflows, networking, registry and cluster services.

- devops: Provides platform engineering, build, deployment and operations workflows for applications across customer-managed clusters.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installation_overview/installation_overview (checked 2026-11-15). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installation_overview/installation_overview (checked 2026-11-15). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installation_overview/installation_overview (checked 2026-11-15). 

- ibm: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installing_on_ibm_cloud/index (checked 2026-11-15). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installing_on_alibaba_cloud/index (checked 2026-11-15). 


### Cloud deployment evidence

- Self-managed OpenShift Container Platform on AWS, Azure or Google Cloud (aws, azure, gcp): https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installation_overview/installation_overview
  Red Hat's current installation overview explicitly distinguishes self-managed OpenShift Container Platform and documents installer- and user-provisioned installation paths on AWS, Microsoft Azure and Google Cloud using customer accounts and credentials.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.

- Self-managed OpenShift on IBM Cloud (ibm): https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installing_on_ibm_cloud/index
  Red Hat documents installer-provisioned deployment into customer IBM Cloud infrastructure, including account IAM/API keys, region selection, VPC networking and cluster administration.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed. Versions: 4.21.

- OpenShift on Alibaba Cloud — Technology Preview (alibaba): https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installing_on_alibaba_cloud/index
  Red Hat documents Assisted Installer deployment using customer Alibaba Cloud OSS images, ECS machines, VPC and DNS. This 4.21 path is Technology Preview: outside production SLAs, potentially incomplete and not recommended by Red Hat for production.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed. Versions: 4.21 Technology Preview.


### Sources

- OpenShift Container Platform 4.21 installation overview: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installation_overview/installation_overview

- Red Hat self-managed OpenShift subscription guide: https://www.redhat.com/en/resources/self-managed-openshift-subscription-guide

- Self-managed OpenShift on IBM Cloud: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installing_on_ibm_cloud/index

- OpenShift on Alibaba Cloud — Technology Preview: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installing_on_alibaba_cloud/index

### Licensing sources

- https://www.redhat.com/en/resources/self-managed-openshift-subscription-guide

### Infrastructure sources

- https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installation_overview/installation_overview


### 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 4.20 Authentication Operator supports an external OIDC identity provider using authorization-code flow, discovery and mapped claims. This authenticates platform users; applications running on the cluster need their own identity integration. Review browser/CLI token workflows and selected provider compatibility. Scope: OpenShift 4.20 platform-user OIDC through the integrated OAuth service. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/observability/authentication_and_authorization/using-rbac (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. Red Hat documents installer-provisioned AWS infrastructure using the release-matched openshift-install tool, install configuration, pull secret and cloud credentials. Customer-managed networking and permissions require review. Use the entitled Red Hat release distribution; the upstream installer source alone is not the product entitlement. Scope: OpenShift Container Platform 4.20 AWS installer path. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/installing_on_aws/installer-provisioned-infrastructure (reviewed 2026-11-20). Deployment artifact: https://github.com/openshift/installer. Artifact reference: Upstream installer source; obtain matching Red Hat release tooling and pull secret.

- Minimum footprint / sizing: Documented. The 4.20 AWS installation matrix gives bootstrap/control-plane minima of 4 vCPUs, 16 GB RAM and 100 GB disk, and compute nodes 2 vCPUs, 8 GB and 100 GB. A standard cluster uses multiple control-plane and worker machines; workload pods, operators, storage, bootstrap and HA capacity are additional. Scope: OpenShift 4.20 per-machine installation floors, not complete workload sizing. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/installing_on_aws/installer-provisioned-infrastructure (reviewed 2026-11-20).

- License pricing: Documented. Self-managed subscriptions can use core-pairs or bare-metal nodes. On hyperscaler VMs, one core-pair covers four vCPUs; aggregate compute-node entitlement and support level must be sized. AI accelerators may require separate subscriptions. Obtain the applicable order and price. Scope: Red Hat self-managed OpenShift Container Platform subscription guide. Source: https://www.redhat.com/en/resources/self-managed-openshift-subscription-guide (reviewed 2026-11-16).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## SAP Business One (BYOL)

Licensed ERP for financials, purchasing, inventory and customer operations.

- Listing: https://launchinyourcloud.com/directory/sap-business-one/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure, gcp, alibaba
- 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: Customer-managed SAP Business One application and a certified database on cloud VMs.
- 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://learn.microsoft.com/en-us/azure/sap/workloads/business-one-azure
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The Azure, Google Cloud and Alibaba guides describe customer infrastructure. Application, database, operating-system and partner entitlements remain separate; check SAP certification for the actual release and topology.

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

Customer-managed SAP Business One application and a certified database on cloud VMs. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Licensed ERP for financials, purchasing, inventory and customer operations.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://learn.microsoft.com/en-us/azure/sap/workloads/business-one-azure (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cloud.google.com/sap/docs/sap-business-one-deployment-guide (checked 2026-11-19). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.alibabacloud.com/help/en/sap-solution/sap-b1-implementation-guide (checked 2026-11-19). 


### Cloud deployment evidence

- Azure Docs (azure): https://learn.microsoft.com/en-us/azure/sap/workloads/business-one-azure
  Customer-managed SAP Business One application and a certified database on cloud VMs. The Azure, Google Cloud and Alibaba guides describe customer infrastructure. Application, database, operating-system and partner entitlements remain separate; check SAP certification for the actual release and topology.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- GCP Docs (gcp): https://docs.cloud.google.com/sap/docs/sap-business-one-deployment-guide
  Customer-managed SAP Business One application and a certified database on cloud VMs. The Azure, Google Cloud and Alibaba guides describe customer infrastructure. Application, database, operating-system and partner entitlements remain separate; check SAP certification for the actual release and topology.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Alibaba Docs (alibaba): https://www.alibabacloud.com/help/en/sap-solution/sap-b1-implementation-guide
  Customer-managed SAP Business One application and a certified database on cloud VMs. The Azure, Google Cloud and Alibaba guides describe customer infrastructure. Application, database, operating-system and partner entitlements remain separate; check SAP certification for the actual release and topology.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Azure Docs: https://learn.microsoft.com/en-us/azure/sap/workloads/business-one-azure

- GCP Docs: https://docs.cloud.google.com/sap/docs/sap-business-one-deployment-guide

- Alibaba Docs: https://www.alibabacloud.com/help/en/sap-solution/sap-b1-implementation-guide

- GCP SAP B1 BYOL Guide: https://docs.cloud.google.com/sap/docs/sap-business-one-planning-guide

- SAP Help Portal: https://help.sap.com/docs/SAP_BUSINESS_ONE

- SAP B1 2026 News: https://news.sap.com/2026/11/sap-business-one-30-years-of-growing-together/

### Licensing sources

- https://docs.cloud.google.com/sap/docs/sap-business-one-planning-guide

- https://help.sap.com/docs/SAP_BUSINESS_ONE

### Infrastructure sources

- https://learn.microsoft.com/en-us/azure/sap/workloads/business-one-azure

- https://docs.cloud.google.com/sap/docs/sap-business-one-deployment-guide

- https://www.alibabacloud.com/help/en/sap-solution/sap-b1-implementation-guide


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. SAP Business One documents external OpenID Connect identity providers registered in the SLD control center, with provider users bound to company users before activation. This is the Business One IAM path, distinct from the separate Cloud Control Center product. Scope: SAP Business One 10.0 IAM documentation; verify the selected feature package, provider and client compatibility. Source: https://help.sap.com/docs/SAP_BUSINESS_ONE_IAM/548d6202b2b6491b824a488cfc447343/13c565324759468490589d60e6c75a92.html (reviewed 2026-11-20). Supporting source: Identity and authentication introduction — https://help.sap.com/docs/SAP_BUSINESS_ONE_IAM/548d6202b2b6491b824a488cfc447343/7f94c5836fad44e6a02322d39e229cc3.html.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Google Cloud guide provisions SAP HANA using its Terraform scale-up guide, then installs licensed SAP Business One using the SAP administrator guide. Infrastructure/HANA automation is not a complete Business One application installer; acquire and version-match SAP media and entitlements separately. Scope: Business One for SAP HANA on Google Cloud; not the SQL Server edition or an end-to-end HA template. Source: https://docs.cloud.google.com/sap/docs/sap-business-one-deployment-guide (reviewed 2026-11-20). Supporting source: Planning and BYOL requirements — https://docs.cloud.google.com/sap/docs/sap-business-one-planning-guide.

- Minimum footprint / sizing: Sources checked — unresolved. The provider planning guide requires an SAP-certified HANA machine and workload-specific memory/storage sizing. Its 32-vCPU/834-GB disk performance example is not a universal Business One minimum, and the documented single-node architecture is not an HA design for the proposed workload. Scope: Business One 10.0 for SAP HANA on Google Cloud; CPU, memory, storage and redundancy require a selected certified configuration. Source: https://docs.cloud.google.com/sap/docs/sap-business-one-planning-guide (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: SAP Business One (BYOL); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://docs.cloud.google.com/sap/docs/sap-business-one-planning-guide (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## SUSE Observability Self-Hosted

Commercial observability platform installed by Helm into a dedicated customer Kubernetes cluster.

- Listing: https://launchinyourcloud.com/directory/suse-observability-self-hosted/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp, alibaba
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial SUSE Observability self-hosted subscription and license key required.
- Licensing model: commercial-only
- Installation: SUSE Observability server Helm chart on EKS, AKS, GKE or Alibaba ACK, with provider-specific storage configuration
- Architecture: Persistent observability services, ingestion and storage components on a dedicated customer Kubernetes cluster.
- Operations: Customer manages the Kubernetes cluster, persistent storage, sizing, ingress, certificates, backups, upgrades and monitored-system access.
- Product website: https://www.suse.com/products/observability/
- 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 the self-hosted server product, not SUSE Cloud Observability SaaS. Installation requires a license key, compatible Helm and Kubernetes versions, persistent storage and dedicated sizing. High-availability and non-high-availability profiles are not interchangeable after installation, so choose the production topology before deployment. SUSE Observability 2.13.0 includes authentication, disk, and backup fixes and requires the documented sequential upgrade path. Version 2.10 reached end of support on November 12, 2026; move through supported intermediate releases as required.

The self-hosted SUSE Observability product requires a commercial subscription and license key. SUSE Cloud Observability is a separate hosted offering.

SUSE Observability runs persistent stateful services on a dedicated Kubernetes cluster with durable storage and substantial capacity requirements.


### Category fit

- observability: Collects, correlates and visualizes Kubernetes topology, metrics, events and related operational signals in a customer-operated deployment.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/en-us/cloudnative/suse-observability/latest/en/installing-suse-obs.html (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/en-us/cloudnative/suse-observability/latest/en/installing-suse-obs.html (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/en-us/cloudnative/suse-observability/latest/en/installing-suse-obs.html (checked 2026-11-17). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/install-stackstate/kubernetes_openshift/ack.html (checked 2026-11-17). 


### Cloud deployment evidence

- SUSE Observability on EKS, AKS and GKE (aws, azure, gcp): https://documentation.suse.com/en-us/cloudnative/suse-observability/latest/en/installing-suse-obs.html
  The server-installation guide explicitly covers the Observability server on EKS, AKS and GKE and supplies the Helm installation. The customer operates the dedicated server cluster, default storage class, persistent volumes and ingress; monitored-cluster agent integrations are separate.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- SUSE Observability server installation on Alibaba ACK (alibaba): https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/install-stackstate/kubernetes_openshift/ack.html
  The server guide supplies ACK-specific Helm values for stateful backend PVCs, each at least 20 GiB. This is server deployment evidence, distinct from monitoring an ACK cluster with an agent. Apply the selected HA sizing profile and provider storage requirements.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Install SUSE Observability self-hosted: https://documentation.suse.com/en-us/cloudnative/suse-observability/latest/en/installing-suse-obs.html

- Kubernetes quick start and named-cloud integrations: https://documentation.suse.com/en-us/cloudnative/suse-observability/latest/en/k8s-quick-start-guide.html

- SUSE subscription terms: https://www.suse.com/products/subscription_terms.pdf

- Alibaba ACK server Helm installation and PVC minimums: https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/install-stackstate/kubernetes_openshift/ack.html

- SUSE Observability 2.13.0 release notes: https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/release-notes/v2.13.0.html

- SUSE product lifecycle: https://www.suse.com/lifecycle/

### Licensing sources

- https://www.suse.com/products/subscription_terms.pdf

- https://documentation.suse.com/en-us/cloudnative/suse-observability/latest/en/installing-suse-obs.html

### Infrastructure sources

- https://documentation.suse.com/en-us/cloudnative/suse-observability/latest/en/installing-suse-obs.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: Sources checked — unresolved. The reviewed server guide supplies a licensed Helm repository, not a cloud-provider billing offer. A current Marketplace offer for this self-hosted server was not established. Scope: Reviewed public evidence for SUSE Observability Self-Hosted; unresolved within this edition/deployment. Source: https://documentation.suse.com/cloudnative/suse-observability/latest/en/installing-suse-obs.html (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. The self-hosted SUSE subscription and Helm installation do not establish an eligible offer or contract-specific cloud commitment treatment. Scope: Reviewed public evidence for SUSE Observability Self-Hosted; unresolved within this edition/deployment. Source: https://www.suse.com/products/subscription_terms.pdf (reviewed 2026-11-17).

- Single sign-on: Documented. The server supports OIDC, including Rancher and Keycloak configurations, or LDAP as the selected authentication mechanism. Only one mechanism is configured at a time; map external groups to the intended server roles. Scope: SUSE Observability server authentication. Source: https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/security/authentication/authentication_options.html (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. The server supports selected OIDC/LDAP authentication and role mappings, but a SCIM provisioning endpoint and lifecycle operations were not established. Scope: Reviewed public evidence for SUSE Observability Self-Hosted; unresolved within this edition/deployment. Source: https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/security/authentication/authentication_options.html (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed SUSE Observability Self-Hosted 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://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/security/authentication/authentication_options.html (reviewed 2026-11-17).

- Security controls: Documented. The default shared administrator password is explicitly not production-ready. Configure an external identity method, limit administrator roles and review RBAC before production use. Scope: Server identity and role hardening; not monitored-cluster agent settings. Source: https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/security/authentication/authentication_options.html (reviewed 2026-11-17).

- Air-gapped operation: Documented. SUSE supplies an air-gapped server installation workflow: download the charts/images, transfer them to the isolated network, load a private registry and apply the licensed Helm configuration. Configure registry credentials and preserve the chosen sizing profile. Scope: Licensed self-hosted Observability server, not agents only. Source: https://documentation.suse.com/cloudnative/suse-observability/latest/en/k8s-suse-rancher-prime-air-gapped.html (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. The server installer uses the SUSE Observability Helm repository, licence key and a selected sizing profile. It provisions the Observability backend on EKS/AKS/GKE; agent installation is a separate workflow. Scope: Self-hosted server Helm installation. Source: https://documentation.suse.com/cloudnative/suse-observability/latest/en/installing-suse-obs.html (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. The smallest HA profile (150-ha) requests 49.8 CPU and 130.7 GiB RAM across at least three workers, with 2,595 GiB default storage. It is based on observed default-node capacity, not users; spare rolling-update capacity is additional. Scope: Observability 150-ha resource requests, not CPU limits or physical-node counts. Source: https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/install-stackstate/requirements.html (reviewed 2026-11-17).

- License pricing: Documented. The self-hosted SUSE Observability product requires a commercial subscription and license key. SUSE Cloud Observability is a separate hosted offering. Scope: SUSE Observability Self-Hosted: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://www.suse.com/products/subscription_terms.pdf (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Illustrative priced infrastructure subtotal: USD 3,656.44/month. Three 32-vCPU/128-GiB workers price the minimum 150-ha profile, plus its 2,595 GiB default PVC request and 150 GB boot allowance. For this illustration each requested GiB is budgeted as one EBS billing GB. This is not a complete operating-cost estimate or a validated capacity/SLA claim. Scope: Smallest documented HA profile, not a conversion from 100 users/1 TB into monitored-node capacity. It exceeds a 1 TB storage allowance before boot volumes. 96 vCPU/384 GiB fleet leaves nominal CPU/memory capacity after one worker loss; scheduling, AZ/storage failover and rolling updates still need validation.. Source: 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 (reviewed 2026-11-17). Supporting source: Product topology/sizing basis — https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/install-stackstate/requirements.html. Supporting source: Current AWS documentation: us-east-1 gp3 capacity example — https://docs.aws.amazon.com/solutions/latest/cloud-migration-factory-on-aws/cost.html. Supporting source: EBS performance and charging qualifications — https://aws.amazon.com/ebs/pricing/. Supporting source: EKS standard versus extended support pricing — https://aws.amazon.com/eks/pricing/.

- Release snapshot / cadence: Documented. The self-hosted Helm chart v2.13.0 release notes are dated November 12, 2026. They list SUSE Observability 2.13.0, Values helper chart 1.4.13 (deprecated since 2.8.0), Agent 1.7.64 and CLI 3.9.0. Component versions are separate; apply every version-specific upgrade step from the installed version through 2.13.0, including the changed scheduling precedence. Scope: Dated SUSE Observability self-hosted Helm release snapshot; the deprecated Values helper chart is not a universal installation requirement. Source: https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/release-notes/v2.13.0.html (reviewed 2026-11-18).







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




## Tableau Server

Commercial analytics and business-intelligence server installed and operated on customer cloud virtual machines.

- Listing: https://launchinyourcloud.com/directory/tableau-server/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, alibaba
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Tableau Server product-key licensing with user-, core- or subscription-based entitlements.
- Licensing model: commercial-only
- Installation: Native server installer on customer virtual machines; optional AWS CloudFormation, Azure Resource Manager or marketplace BYOL paths
- Architecture: Customer-operated Tableau Server on cloud virtual machines in a single-node or distributed topology.
- Operations: Customer manages the virtual machines, operating system, Tableau services, identity, networking, storage, backups, upgrades and availability.
- Product website: https://www.tableau.com/products/server
- Source review: 2026-11-17; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

Tableau's provider-specific public-cloud guides are archived and no longer updated, although Tableau states that these deployments remain supported. Native virtual-machine self-deployment is the consistently documented production-ready path; marketplace and Quick Start options are convenience paths and should not be treated as the preferred production architecture. Tableau recommends Tableau Cloud where it meets the customer's requirements.

Tableau Server requires a commercial product key and the applicable user-, core- or subscription-based entitlement. Tableau Cloud is a separate hosted offering.

The production self-managed path installs Tableau Server on persistent cloud virtual machines; distributed deployments use multiple nodes and external cloud services.


### Category fit

- data-analytics: Enterprise analytics, governed data exploration, dashboards and business-intelligence publishing on a customer-operated server.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.tableau.com/current/server/en-us/ts_aws_deployment_options.htm (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.tableau.com/current/server/en-us/ts_azure_deployment_options.htm (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.tableau.com/current/server/en-us/ts_gcp_deployment_options.htm (checked 2026-11-17). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.tableau.com/current/server/en-us/ts_alibaba_deployment_options.htm (checked 2026-11-17). 


### Cloud deployment evidence

- Tableau Server on Amazon Web Services (aws): https://help.tableau.com/current/server/en-us/ts_aws_deployment_options.htm
  Tableau documents customer-managed EC2 installation as the production-ready AWS path. The provider guide is archived, but Tableau states the deployment remains supported.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- Tableau Server on Microsoft Azure (azure): https://help.tableau.com/current/server/en-us/ts_azure_deployment_options.htm
  Tableau documents customer-managed Azure VM installation as the production-ready path. The provider guide is archived, but Tableau states the deployment remains supported.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- Tableau Server on Google Cloud (gcp): https://help.tableau.com/current/server/en-us/ts_gcp_deployment_options.htm
  Tableau documents production-ready self-deployment on customer Google Compute Engine virtual machines with BYOL operation. The provider guide is archived.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- Tableau Server on Alibaba Cloud (alibaba): https://help.tableau.com/current/server/en-us/ts_alibaba_deployment_options.htm
  Tableau documents production-ready self-deployment on customer Alibaba Elastic Compute Service virtual machines with BYOL operation. The provider guide is archived.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Tableau Server public-cloud overview: https://help.tableau.com/current/server-linux/en-us/ts_tableau_server_cloud_overview.htm

- Tableau Server administrator overview: https://help.tableau.com/current/server/en-us/admin.htm

- AWS deployment options: https://help.tableau.com/current/server/en-us/ts_aws_deployment_options.htm

- Azure deployment options: https://help.tableau.com/current/server/en-us/ts_azure_deployment_options.htm

- Google Cloud deployment options: https://help.tableau.com/current/server/en-us/ts_gcp_deployment_options.htm

- Alibaba Cloud deployment options: https://help.tableau.com/current/server/en-us/ts_alibaba_deployment_options.htm

- AWS prerequisites and licensing: https://help.tableau.com/current/server/en-us/ts_aws_prerequisites.htm

### Licensing sources

- https://help.tableau.com/current/server/en-us/ts_aws_prerequisites.htm

### Infrastructure sources

- https://help.tableau.com/current/server-linux/en-us/ts_tableau_server_cloud_overview.htm

- https://help.tableau.com/current/server/en-us/admin.htm


### 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. Archived AWS/Azure deployment guides identify Marketplace paths with production-readiness warnings. A current production-ready offer and entitlement were not confirmed. Scope: Reviewed public evidence for Tableau Server; unresolved within this edition/deployment. Source: https://help.tableau.com/current/server/en-us/ts_aws_deployment_options.htm (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. The reviewed Server deployment/licensing material does not establish a qualifying software Marketplace offer and buyer commitment treatment. Scope: Reviewed public evidence for Tableau Server; unresolved within this edition/deployment. Source: https://help.tableau.com/current/server/en-us/ts_aws_prerequisites.htm (reviewed 2026-11-17).

- Single sign-on: Documented. The Server SCIM guide explicitly supports site-specific SAML, TSM authentication and identity pools with version qualifications. Configure the chosen Server identity method and network reachability separately from provisioning. Scope: Server identity methods applicable to SCIM. Source: https://help.tableau.com/current/server/en-us/scim_config_online.htm (reviewed 2026-11-17).

- SCIM provisioning: Documented. Server supports site-level SCIM from 2025.3. Site-specific SAML works from 2025.3.0; TSM-configured authentication and identity pools require 2025.3.1+. Entra/Okta may need an on-premises provisioning connector through the server firewall. Scope: Tableau Server SCIM; not Tableau Cloud-only documentation. Source: https://help.tableau.com/current/server/en-us/scim_config_online.htm (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed Tableau Server material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage. Scope: Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited. Source: https://help.tableau.com/current/server/en-us/activate_off.htm (reviewed 2026-11-17).

- Security controls: Documented. The offline activation guide distinguishes product keys and ATR workflows. Protect transferred activation files and configure server identity and permissions separately; disconnected activation does not confer a security attestation. Scope: Server offline activation and licence handling. Source: https://help.tableau.com/current/server/en-us/activate_off.htm (reviewed 2026-11-17).

- Air-gapped operation: Sources checked — unresolved. Offline Server activation is documented, but this alone does not establish isolation for every connector, extension, update and identity dependency. Confirm the selected full deployment and licence workflow. Scope: Offline activation versus complete air-gapped operation. Source: https://help.tableau.com/current/server/en-us/activate_off.htm (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. Vendor cloud guides describe installing Server on customer VMs. Archived AWS/Azure Quick Start and Marketplace routes carry production-readiness warnings; use a supported self-deployment design and installation media. Scope: Customer-managed Server; archived automation warnings retained. Source: https://help.tableau.com/current/server/en-us/ts_aws_deployment_options.htm (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. The production single-node recommendation is 8 physical cores/16 vCPU, 128 GB RAM for 2022.3+ and at least 50 GB disk. Multi-node/HA design needs Tableau guidance; extracts, refresh scratch space and backups add storage. Scope: Production single-node recommendation, not the complete HA design. Source: https://help.tableau.com/current/server/en-us/server_hardware_min.htm (reviewed 2026-11-17).

- License pricing: Documented. Tableau Server requires a commercial product key and the applicable user-, core- or subscription-based entitlement. Tableau Cloud is a separate hosted offering. Scope: Tableau Server: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://help.tableau.com/current/server/en-us/ts_aws_prerequisites.htm (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Obtain the supported multi-node/HA design, user-role licence mix, extract/refresh workload, repository/file-store sizing and any Windows licences. Single-node production recommendations do not price an HA farm. A complete monthly operating estimate is not established. Scope: Requested planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA, average usage; missing workload metrics and commercial terms are explicit. Source: https://help.tableau.com/current/server/en-us/server_hardware_min.htm (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. Tableau Server 2026.3 was released 2026-10-23. The release page warns Windows Server 2016/Windows 10 users to review installation issue W-24614917 before upgrading; this is Server, not Tableau Cloud/Desktop. Scope: Tableau Server vendor release record. Source: https://www.tableau.com/support/releases/server/2026.3 (reviewed 2026-11-17).







## TiDB Community Self-Hosted

Open-source distributed SQL database with customer-operated cloud Kubernetes guides and a separately packaged third-party AWS VM option.

- Listing: https://launchinyourcloud.com/directory/tidb-community/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp, azure, alibaba
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0.
- Licensing model: open-source
- Installation: TiDB Operator and versioned Kubernetes resources on EKS/GKE/AKS; the Alibaba ACK Terraform recipe has older development/test version constraints; optional Techlatest AWS single-VM bundle is separately packaged and does not supply the Operator HA topology
- Architecture: TiDB, PD and TiKV services on customer Kubernetes node pools with persistent storage, or a separately reviewed third-party single-VM bundle; optional analytics and monitoring depend on the deployment.
- Operations: Customer manages the chosen Kubernetes cluster or VM, operating system/node pools, persistent storage, networking, database identities, backups, monitoring, upgrades, scaling and database operations.
- Product website: https://www.pingcap.com/tidb/
- 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 TiDB Community, not TiDB Cloud. AKS has a complete current guide even though the deployment FAQ omits it; that difference does not negate the documented path. The ACK guide is an older development/test recipe, while the current FAQ still names ACK. Match operator/database versions and validate production permissions, storage and HA before use. An alternative Techlatest AWS image packages TiDB OSS with Grafana/Prometheus on one VM. Package 1.0.2 does not identify the database components’ versions and is not an HA cluster or PingCAP support entitlement. Do not transfer Operator sizing, offline procedures or the upstream v8.5.8 snapshot to this image.

The TiDB repository is Apache-2.0 licensed. Managed TiDB Cloud services have separate terms.

TiDB runs persistent database/storage services on customer Kubernetes node pools, or as a separately packaged single-VM OSS bundle. The seller VM is not the Operator-based production HA topology.


### Category fit

- databases-vector: Provides a distributed SQL database with horizontally scaled storage and query services.

- data-analytics: Supports scalable transactional and analytical SQL workloads on a customer-operated cluster.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-aws-eks/ (checked 2026-11-18). Source: https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html (checked 2026-11-18). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-gcp-gke/ (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-azure-aks/ (checked 2026-11-18). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.pingcap.com/tidb-in-kubernetes/v1.4/deploy-on-alibaba-cloud/ (checked 2026-11-18). 


### Cloud deployment evidence

- TiDB on Amazon EKS (aws): https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-aws-eks/
  PingCAP documents customer EKS node pools, storage and TiDB Operator deployment.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- TiDB on Google Kubernetes Engine (gcp): https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-gcp-gke/
  PingCAP documents customer GKE node pools, persistent disks and TiDB Operator deployment.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- TiDB Community on Azure AKS (azure): https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-azure-aks/
  PingCAP provides a full AKS deployment guide with customer node pools, PD/TiKV/TiDB and monitoring manifests. A deployment guide establishes a documented path, not a commercial support contract.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- TiDB on Alibaba Cloud ACK (alibaba): https://docs.pingcap.com/tidb-in-kubernetes/v1.4/deploy-on-alibaba-cloud/
  PingCAP’s v1.4 guide deploys a full cluster into customer ACK using Terraform and TiDB Operator and is scoped to development/testing. The current deployment FAQ still names ACK; old Terraform/image examples need a current-version production review.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed. Versions: TiDB Operator guide v1.4.

- Techlatest TiDB OSS single-VM bundle in customer EC2 (aws): https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html
  The seller guide subscribes to exact AWS offer prodview-ddl3tqewcoko4 and launches into the customer region/VPC/EC2 account. TiDB and its monitoring interfaces run on the VM. This is a separately packaged single-node option, not the Kubernetes HA path; package 1.0.2 leaves embedded database versions unreported. Restrict SSH/RDP and set the documented initial credentials.
  Source type: third-party-package; reviewed: 2026-11-18; vendor support: not-assessed. Edition: Repackaged open-source TiDB bundle. Versions: Seller package 1.0.2; embedded database versions unreported.


### Community and maintenance

PingCAP maintains the Apache-licensed database and operator with public contribution activity and supported LTS releases. Its named customer case-study catalog demonstrates adoption, while TiDB Cloud stories are kept separate from Community cloud evidence.

Reviewed 2026-11-18.

- Official maintenance and adoption evidence: https://github.com/pingcap/tidb/releases/tag/v8.5.8

- Official maintenance and adoption evidence: https://www.pingcap.com/case-studies/

- Official maintenance and adoption evidence: https://docs.pingcap.com/tidb-in-kubernetes/stable/tidb-operator-overview/

### Sources

- TiDB Operator overview: https://docs.pingcap.com/tidb-in-kubernetes/stable/tidb-operator-overview/

- Deploy TiDB on AWS EKS: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-aws-eks/

- Deploy TiDB on Google Cloud GKE: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-gcp-gke/

- TiDB Apache 2.0 license: https://github.com/pingcap/tidb/blob/master/LICENSE

- TiDB Community on Azure AKS: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-azure-aks/

- TiDB on Alibaba Cloud ACK: https://docs.pingcap.com/tidb-in-kubernetes/v1.4/deploy-on-alibaba-cloud/

- Current TiDB deployment FAQ: https://docs.pingcap.com/tidb/stable/deploy-and-maintain-faq/

- Exact third-party TiDB OSS AWS image: https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4

- Seller customer-account VM deployment: https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html

### Licensing sources

- https://github.com/pingcap/tidb/blob/master/LICENSE

### Infrastructure sources

- https://docs.pingcap.com/tidb-in-kubernetes/stable/tidb-operator-overview/

- https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html


### 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. Techlatest.net publishes TiDB with Grafana/Prometheus as AWS AMI prodview-ddl3tqewcoko4: a repackaged open-source single-VM bundle, package 1.0.2 on CentOS Stream 9. The reviewed t2.large option charges USD 0.13/hour for seller support plus AWS resources. This is an alternative to the Operator-based Kubernetes path, not that HA topology. The seller does not name embedded TiDB/TiKV/PD versions; inspect and pin them before production rather than inheriting the upstream release snapshot. Scope: Optional third-party TiDB Community VM delivery in the customer AWS account; independent from Operator/Kubernetes topology, package versions and support. Source: https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4 (reviewed 2026-11-18). Supporting source: Seller single-VM installation and initial credentials — https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html. Supporting source: TiDB Community upstream licence — https://github.com/pingcap/tidb/blob/master/LICENSE. Offer prodview-ddl3tqewcoko4: Techlatest.net; Amazon Machine Image (AMI), x86; single-VM bundle; package Seller package 1.0.2; embedded database versions unreported; https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4.

- Cloud commitment eligibility: Sources checked — unresolved. The upstream Community Apache licence has no subscription charge. The alternative Techlatest VM has a separately billed seller-support charge on AWS Marketplace, but its exact commitment eligibility is not established by the offer. Confirm the selected offer/contract and buyer’s AWS agreement; neither the free licence nor TiDB Cloud SaaS terms settle that transaction. Scope: TiDB Community self-managed software; Operator and third-party VM delivery have separate packaging/operating scope. Source: https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4 (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. Supporting source: Community licence — https://github.com/pingcap/tidb/blob/master/LICENSE.

- Single sign-on: Documented. TiDB Self-Managed v8.5 documents OIDC SSO for the TiDB Dashboard web UI, with Okta, Auth0 and self-hosted Casdoor examples. Dashboard encrypts/stores a SQL account password to complete an impersonated SQL sign-in after OIDC authentication. SQL password rotation requires reauthorization; disabling SSO erases the stored password. This establishes Dashboard sign-in only. A selected SQL client’s federated login and SCIM lifecycle require separate confirmation. Scope: TiDB Community/Self-Managed v8.5 Dashboard web UI, including its documented Kubernetes deployment; SQL-client SSO and the versions inside the third-party VM are assessed separately. Source: https://docs.pingcap.com/tidb/stable/dashboard-session-sso/ (reviewed 2026-11-18). Supporting source: Dashboard access on customer-operated Kubernetes — https://docs.pingcap.com/tidb-in-kubernetes/stable/access-dashboard/. Supporting source: Least-privileged Dashboard SQL users — https://docs.pingcap.com/tidb/stable/dashboard-user/. Supporting source: Protect Dashboard and privileged PD interfaces — https://docs.pingcap.com/tidb/stable/dashboard-ops-security/. Supporting source: Separate SQL JWT/LDAP authentication boundary — https://docs.pingcap.com/tidb/stable/security-compatibility-with-mysql/.

- SCIM provisioning: Sources checked — unresolved. JWT and LDAP authentication do not establish SCIM user/group management or automatic SQL-account deprovisioning. A current Community endpoint and supported operations were not confirmed; review provisioning and token revocation separately. Scope: TiDB Community self-managed software; Operator and third-party VM delivery have separate packaging/operating scope. Source: https://docs.pingcap.com/tidb/stable/security-compatibility-with-mysql/ (reviewed 2026-11-18).

- Compliance attestations: Sources checked — unresolved. PingCAP’s Trust Hub advertises ISO and SOC assurances and requests certificate/report access. Its specific ISO announcement identifies TiDB Cloud, a managed service, rather than this customer-operated Community cluster. A current certificate/report covering the relevant Community development/support boundary and buyer controls was not established; do not inherit TiDB Cloud attestations. Scope: TiDB Community self-managed software; Operator and third-party VM delivery have separate packaging/operating scope. Source: https://www.pingcap.com/trust-hub/compliance/ (reviewed 2026-11-18). Supporting source: Explicit TiDB Cloud ISO certification boundary — https://www.pingcap.com/press-release/announcing-iso-27001-certification-for-tidb-cloud/.

- Security controls: Documented. PingCAP documents certificates and TLS between components, plus client TLS and privileged-user/network controls. JWT SQL authentication requires trusted issuer/JWKS configuration and client TLS because the client sends the token through a clear-password plugin. Database token/LDAP authentication alone does not establish SSO or SCIM. Techlatest’s VM guide starts TiDB root with a blank password and Grafana with admin/admin; set new credentials and restrict SSH/RDP before use. Its component patch levels remain unconfirmed. Optional Dashboard OIDC SSO stores an encrypted SQL password for impersonation; use the documented least-privileged account and network/TLS controls, and reauthorize after SQL password rotation. Scope: TiDB Community self-managed software; Operator and third-party VM delivery have separate packaging/operating scope. Source: https://docs.pingcap.com/tidb/stable/enable-tls-between-components/ (reviewed 2026-11-18). Supporting source: Self-managed security configuration — https://docs.pingcap.com/tidb/stable/best-practices-for-security-configuration/. Supporting source: SQL authentication and JWT TLS requirements — https://docs.pingcap.com/tidb/stable/security-compatibility-with-mysql/. Supporting source: Seller-specific initial credential requirements — https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html. Supporting source: Dashboard OIDC credential-handling boundary — https://docs.pingcap.com/tidb/stable/dashboard-session-sso/. Supporting source: Least-privileged Dashboard SQL users — https://docs.pingcap.com/tidb/stable/dashboard-user/.

- Air-gapped operation: Documented. The Kubernetes guide explicitly describes transferring container images to a server without external network access and loading them locally. Include operator, PD/TiKV/TiDB, optional TiFlash/TiCDC, monitoring and initialization images; its v8.5.7 example is not a complete current-version image lockfile. Scope: Operator-based Kubernetes offline procedure only; the third-party VM’s offline lifecycle is not established. Source: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-general-kubernetes/ (reviewed 2026-11-18).

- Deployment artifact / IaC: Documented. The AKS guide provides a versioned TiDB custom-resource manifest from TiDB Operator v1.6.6, together with separate monitoring/dashboard manifests. The operator version and TiDB image versions are independent; review requests, storage classes and all example defaults. The optional seller VM has a separate AMI/image inventory; do not treat the Operator manifest as its installation artifact. Scope: Operator v1.6.6 Kubernetes manifest; the third-party VM is a separate delivery. Source: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-azure-aks/ (reviewed 2026-11-18). Deployment artifact: https://raw.githubusercontent.com/pingcap/tidb-operator/v1.6.6/examples/aks/tidb-cluster.yaml. Artifact reference: TiDB Operator v1.6.6 AKS example. Supporting source: Separate single-VM deployment artifact — https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html.

- Minimum footprint / sizing: Documented. The v8.5 production hardware baseline lists two TiDB nodes at 16 cores/48 GB each, three PD at 8 cores/16 GB, and three TiKV at 16 cores/64 GB, plus SSD and network requirements. Optional analytics/changefeed/monitoring add components. These are component recommendations, not exact pod requests or a benchmark for 100 users. The seller’s t2.large VM example is not this production multi-node baseline. Scope: Upstream v8.5 production component recommendations; not the third-party VM’s capacity or HA guarantee. Source: https://docs.pingcap.com/tidb/stable/hardware-and-software-requirements/ (reviewed 2026-11-18). Supporting source: Different single-VM baseline — https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html.

- License pricing: Documented. TiDB Community is Apache 2.0 licensed. PingCAP support and TiDB Cloud are separate commercial purchases. Review the licences of optional monitoring tools and other bundled components. The alternative Techlatest AMI bills USD 0.13/hour for seller support on its reviewed t2.large option, with AWS resources separate. Scope: TiDB Community self-managed software; Operator and third-party VM delivery have separate packaging/operating scope. Source: https://github.com/pingcap/tidb/blob/master/LICENSE (reviewed 2026-11-18). Supporting source: Separately transacted seller bundle pricing — https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4.

- Operating cost estimate: Sources checked — unresolved. Define SQL QPS, transaction mix, concurrency, indexes, TiKV replication, usable versus raw 1 TB, compaction headroom, TiFlash/TiCDC needs, monitoring and recovery targets. Price EKS and stateful nodes/storage across failure domains after benchmarking; the user count alone does not size this distributed database. The seller’s single-VM bundle does not provide the requested HA architecture. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://docs.pingcap.com/tidb/stable/hardware-and-software-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/. Supporting source: Single-VM price/topology is a different cost scope — https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4.

- Release snapshot / cadence: Documented. TiDB v8.5.8 was published August 27, 2026 and is the reviewed v8.5 LTS snapshot. Its notes include PD endpoint and TiKV dependency security fixes. The later v7.5.8 publication belongs to an older branch. Match Operator, TiKV, PD and optional component versions rather than treating the chart version as the database version. Techlatest’s AMI package 1.0.2 does not disclose its embedded database versions, so this upstream snapshot must not be inherited by that VM. Scope: Upstream TiDB v8.5 LTS snapshot; not a confirmed version for the third-party AWS image. Source: https://github.com/pingcap/tidb/releases/tag/v8.5.8 (reviewed 2026-11-18). Supporting source: Component fixes in v8.5.8 — https://docs.pingcap.com/tidb/stable/release-8.5.8. Supporting source: Separate seller package/version boundary — https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4.




### Security and lifecycle reviews

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

- TiDB v8.5.8 PD endpoint and component security review (security-advisory): The release fixes potential SSRF/upstream response exposure in PD metric endpoints, GlobalConfig namespace access and dependency vulnerabilities in TiKV/DM. Scope: The v8.5.8 component release notes; a complete affected-version range and a universal exposure claim are not established. Conditions: Exposure depends on component versions, PD endpoint accessibility and configured dependencies. Community, Cloud and unrelated LTS branches must not be treated as identical deployments. Action: Review the fixed PD/TiKV/optional component versions, restrict management endpoints and follow the matching LTS upgrade procedure. Source: https://docs.pingcap.com/tidb/stable/release-8.5.8; reviewed 2026-11-18.



