
# AI tools & infrastructure on Alibaba Cloud

Compare documented AI tools & infrastructure deployments on Alibaba Cloud, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/alibaba/ai-tools/
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.

4 listings.


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




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







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






