AI tools & infrastructure

AI applications, model operations, inference and supporting vector databases.

31 listings, including 31 from other publishers. Entries cover the deployment options documented on their individual pages.

Watch this category with RSS · Build a requirements shortlist

Deployment comparison

ListingDocumented cloudsDeployment and infrastructureLicensingInstallationOperations and limitations
AnythingLLM DockerAWS, Google Cloud, RailwayCustomer-operated
Servers / containers
Open Source / Open Core

MIT License for upstream AnythingLLM; model weights, connectors and provider services have separate terms.

Run the official Docker edition on a customer-operated host with persistent application storage and configured model/vector endpoints.Customer manages users, documents, persistent storage, model access, integration secrets, backups and upgrades.
Scope and evidence

The Docker edition supports multi-user operation and differs from the desktop application. Local inference is an option; configured external LLMs, embeddings, vector stores and agent tools can send data outside the account. AnythingLLM v1.20.0 hardens embed history, extension API-key authorization, workspace-agent access, password recovery, framing, and document-tool downloads. Optional MCP identity forwarding creates a new outbound identity path; keep the server and extension on compatible 1.20+ versions.

  • AnythingLLM Docker installation overview — The project explicitly names AWS, Google Cloud and Railway for self-hosting the Docker edition, paired with its Docker installation workflow. This is an upstream hosting compatibility statement. Model endpoints, embeddings and external vector stores are separately configured and can have different data boundaries.

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

Cloud evidence reviewed 2026-11-12

Arize Phoenix Self-HostedAWS, Azure, Google Cloud, Railway, RenderCustomer-operated
Servers / containers
Source Available

Elastic License 2.0; includes restrictions on providing the software as a hosted/managed service and on license-key circumvention. This is source-available.

Use the official self-hosted Docker/Compose or Kubernetes deployment instructions and configure persistent storage and instrumentation endpoints.Customer manages trace capture, storage, authentication, retention, evaluation providers, backups and upgrades.
Scope and evidence

The self-hosted product is distinct from commercial Arize offerings. Traces may contain prompts and outputs; evaluation jobs can call separately configured external model services even when trace storage is local.

  • Phoenix self-hosting deployment options — The current Phoenix self-hosting index includes a Railway one-click template as well as AWS CloudFormation, Azure ARM and Google Cloud Run. These deploy the Phoenix application, not the separately licensed Arize AX product. A Railway project is customer-controlled while Railway manages its infrastructure.

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

  • Phoenix self-hosted Render Blueprint — The vendor self-hosting index offers a Render one-click Blueprint for Phoenix alongside its Railway, AWS, Azure and Google Cloud options. This is the self-hosted Phoenix application, separate from Arize AX; customer workspace control does not imply ownership of the platform infrastructure.

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

Cloud evidence reviewed 2026-11-12

Cloudera on CloudAWS, Azure, Google CloudShared operations · vendor control plane
Servers / containers
Commercial Only

Commercial Cloudera subscription with cloud infrastructure charges paid separately.

Register the customer cloud environment and credentials, then provision Cloudera workload services through the control planeCloudera operates the service control plane; the customer owns cloud resources, credentials, data governance, network integration, workload sizing and shared operational responsibilities.
Scope and evidence

This entry covers Cloudera's public-cloud BYOC service, not a fully customer-operated software distribution. Workloads and data run in the customer's AWS, Azure or Google Cloud environment while Cloudera operates the control plane. Service availability and implementation details differ by provider, especially on Google Cloud, so confirm each required service before procurement. Cloudera November bulletins cover critical Brotli CVE-2026-111497 and compromised eMudhra certificates. Use the TSB matrices for the exact Runtime or Private Cloud Base component and fixed build rather than applying a generic platform version.

  • Cloudera workloads in customer AWS, Azure and Google Cloud environments — Cloudera documents registering customer AWS, Azure and Google Cloud environments and credentials so its control plane can provision workload resources. Provider service availability differs and must be checked for the selected workload.

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

Cloud evidence reviewed 2026-11-17

Dataiku DSS Cloud StacksAWS, Azure, Google CloudCustomer-operated
Servers / containers
Commercial Only

Commercial Dataiku license or license token required for the full Cloud Stacks capabilities.

AWS CloudFormation, Azure ARM template or Google Cloud Infrastructure Manager with TerraformCustomer manages cloud accounts, Fleet Manager, IAM identities, networking, VM and Kubernetes capacity, storage, TLS, backups, upgrades and license configuration.
Scope and evidence

This entry covers Dataiku Cloud Stacks, not vendor-hosted Dataiku Cloud. Dataiku states that Cloud Stacks resources run in the customer's organization or tenant and that Dataiku does not have access to customer data. Fleet Manager requires broad cloud permissions and outbound access for images, license validation and configured identity services. Dataiku DSS Free Edition is separate from the fully featured licensed Cloud Stacks deployment.

  • Dataiku DSS Cloud Stacks on AWS — Dataiku documents using an AWS CloudFormation template to deploy Fleet Manager into the customer's AWS account, then provisioning DSS nodes and optional EKS elastic-compute clusters.

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

  • Dataiku DSS Cloud Stacks on Azure — Dataiku documents deploying Fleet Manager and its supporting resources through an Azure ARM template, then provisioning DSS instances and optional AKS elastic compute in the customer's subscription.

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

  • Dataiku DSS Cloud Stacks on Google Cloud — Dataiku documents deploying Fleet Manager through Google Cloud Infrastructure Manager using its supplied Terraform configuration, then provisioning DSS instances and optional GKE elastic compute in the customer's projects.

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

Cloud evidence reviewed 2026-11-16

Dify Self-HostedAlibaba CloudCustomer-operated
Servers / containers
Source Available

Modified Apache 2.0 terms; multi-workspace service operation and frontend branding can require commercial authorization.

Official Docker Compose deployment; pin a release and configure its required services.Customer operates the containers, persistent stores, secrets, backups and upgrades; commercial edition support varies.
Scope and evidence

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.

  • Dify Docker deployment on Alibaba Cloud ECS — 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.

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

  • Dify Community Edition full application on Alibaba Compute Nest — 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.

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

Cloud evidence reviewed 2026-11-12

Elastic Cloud on KubernetesAWS, Azure, Google CloudCustomer-operated
Servers / containers
Source Available

Elastic License 2.0 distribution with free Basic capabilities; Enterprise licensing unlocks additional features and support.

Official ECK Helm chart or Kubernetes manifests on EKS, AKS or GKECustomer manages Kubernetes, storage, resource sizing, security, snapshots, upgrades and availability; Elastic licensing controls advanced features and support.
Scope and evidence

This entry covers self-managed Elastic Cloud on Kubernetes, not Elastic Cloud Hosted or Elastic Cloud Enterprise. ECK automates application lifecycle but does not transfer cluster, storage, backup or upgrade responsibility to Elastic. The free Basic license and paid Enterprise feature set differ; optional Cloud Connect services create separate external dependencies. ECK 3.5.0 fixes service-token exposure, cross-namespace certificate injection, and retained cross-namespace credentials. CVE-2026-72648 has no workaround; after upgrading, rotate the affected service token as Elastic directs.

  • Elastic Cloud on Kubernetes on EKS, AKS and GKE — Elastic documents ECK for managed Kubernetes services including Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine. The customer owns and operates the cluster and persistent storage.

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

Cloud evidence reviewed 2026-11-17

Hyperscience HypercellAWS, Azure, Google CloudCustomer-operated
Servers / containers
Commercial Only

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

Helm / Kubernetes operator; Kubernetes manifestsCustomer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope and evidence

The Helm guide supplies complete AWS and GCP values, including application storage permissions. Registry integration alone is not a hosting badge. Hypercell application versions, Helm charts and Kubernetes support dates are separate. The October 2026 decoder advisory and the current v44 flow/block upgrade instructions must be checked before exposing document processing; hosted FedRAMP claims do not transfer to this installation. The vendor Azure reference diagram depicts the complete platform, Blob storage and PostgreSQL; its namespace label still says GKE, so validate the Azure-specific values with the vendor. Apply the fix for the installed Hypercell line and follow the documented sequential upgrades or temporary workarounds.

  • Helm Chart (AWS/GCP) — Hyperscience Helm application, database, object storage, workers and separately prepared container registry on AWS or GKE Standard. The Helm guide supplies complete AWS and GCP values, including application storage permissions. Registry integration alone is not a hosting badge. Hypercell application versions, Helm charts and Kubernetes support dates are separate. The October 2026 decoder advisory and the current v44 flow/block upgrade instructions must be checked before exposing document processing; hosted FedRAMP claims do not transfer to this installation. The vendor Azure reference diagram depicts the complete platform, Blob storage and PostgreSQL; its namespace label still says GKE, so validate the Azure-specific values with the vendor.

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

  • Kubernetes Installation Overview — Hyperscience Helm application, database, object storage, workers and separately prepared container registry on AWS or GKE Standard. The Helm guide supplies complete AWS and GCP values, including application storage permissions. Registry integration alone is not a hosting badge. Hypercell application versions, Helm charts and Kubernetes support dates are separate. The October 2026 decoder advisory and the current v44 flow/block upgrade instructions must be checked before exposing document processing; hosted FedRAMP claims do not transfer to this installation. The vendor Azure reference diagram depicts the complete platform, Blob storage and PostgreSQL; its namespace label still says GKE, so validate the Azure-specific values with the vendor.

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

Cloud evidence reviewed 2026-11-19

KNIME Business HubAWS, Azure, Google CloudCustomer-operated
Servers / containers
Commercial Only

Commercial KNIME Business Hub license or Marketplace software subscription required.

Official AWS, Azure or Google Cloud Marketplace virtual-machine imageCustomer manages the cloud account, virtual machine, networking, DNS, TLS, identity, storage, backups, capacity, upgrades and Business Hub license.
Scope and evidence

This entry covers customer-hosted KNIME Business Hub, not the open-source KNIME Analytics Platform or KNIME's managed Hub offering. Marketplace deployments use single VM images; production capacity, availability and recovery requirements must be assessed separately. Customer-provisioned Kubernetes installation requires the applicable Self Hosted Premium package. Cloud infrastructure charges are separate from KNIME software pricing.

  • KNIME Business Hub on AWS Marketplace — KNIME documents launching Business Hub from an AWS Marketplace AMI into the customer's AWS account, with Marketplace or BYOL software licensing.

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

  • KNIME Business Hub on Azure Marketplace — KNIME documents launching Business Hub from an Azure Marketplace single-VM image into the customer's Azure subscription.

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

  • KNIME Business Hub on Google Cloud Marketplace — KNIME documents launching Business Hub through Google Cloud Marketplace using a Google Compute VM image in the customer's project.

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

Cloud evidence reviewed 2026-11-16

Langflow Self-HostedAWS, Azure, Google CloudCustomer-operated
Servers / containers
Open Source / Open Core

MIT for the upstream project; connected models, providers and bundles have their own terms.

Official Docker image or Docker Compose; Python installation and Kubernetes options are also documented.Customer manages the application, database, access controls, installed components, backups and version upgrades.
Scope and evidence

The reviewed model-component docs support Ollama and configurable OpenAI-compatible endpoints as well as commercial providers. External models, embeddings, tools or custom components can move data beyond the host. Hosting Langflow is distinct from hosting those dependencies and from any vendor-managed service. Langflow 1.13.3 enforces custom-component policy in background workflows, invalidates native sessions after password changes, updates security dependencies, and aligns Docker and wheel packaging. Recheck custom components and session behavior after upgrading.

  • Langflow Kubernetes deployment architecture — The project explicitly identifies EKS, AKS and GKE for its Helm deployment. Separate the development IDE from the production runtime, and review PostgreSQL, model endpoints and external vector stores.

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

Cloud evidence reviewed 2026-11-12

Langfuse Self-HostedAWS, Azure, Google Cloud, Railway, RenderCustomer-operated
Servers / containers
Open Source / Open Core

MIT core; designated enterprise directories and add-on capabilities use separate license terms or keys.

Docker Compose for a single VM; Helm/Kubernetes and official AWS, Azure and Google Cloud Terraform modules.Customer operates the deployment, persistence, access policies, retention, backups and scaling.
Scope and evidence

Traces can contain prompts, outputs and other sensitive application data, so configure capture and retention deliberately. Self-hosted trace storage does not move the underlying application model into the same account. Optional model-based evaluators or the gateway use configured providers, which may be external. The single-VM Compose example does not provide production high availability or backups. Langfuse v4.82.0 fixes an SSRF path in GitHub Enterprise SSO and moves audit logs to ClickHouse. Review outbound SSO connectivity and audit-log storage during upgrade.

  • Langfuse customer cloud deployment on AWS — The vendor documents deployment of the self-hosted Langfuse application and its backing services in the customer account or project, including provider-specific infrastructure. This is distinct from Langfuse Cloud; database, object storage, model calls and enterprise licensing must be configured for the chosen topology.

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

  • Langfuse customer cloud deployment on Azure — The vendor documents deployment of the self-hosted Langfuse application and its backing services in the customer account or project, including provider-specific infrastructure. This is distinct from Langfuse Cloud; database, object storage, model calls and enterprise licensing must be configured for the chosen topology.

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

  • Langfuse customer cloud deployment on Google Cloud — The vendor documents deployment of the self-hosted Langfuse application and its backing services in the customer account or project, including provider-specific infrastructure. This is distinct from Langfuse Cloud; database, object storage, model calls and enterprise licensing must be configured for the chosen topology.

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

  • Langfuse v3 community Railway deployment — The vendor documents a community-maintained Railway template for the complete Langfuse v3 stack. This establishes that version-specific application deployment; the same page explicitly distinguishes the v4 alternatives. The vendor does not systematically test the community template. Review the template services, image tags, database timezones and upgrade path.

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

  • Langfuse v4 community Render Blueprint — The vendor documents a community-maintained v4 Blueprint with separate web and worker services, PostgreSQL, Key Value, ClickHouse and MinIO. It creates the full application in the customer Render workspace. Review service plans, persistent disks, object-storage exposure and recovery procedures; community support is best-effort.

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

Cloud evidence reviewed 2026-11-12

LibreChat Self-HostedRailway, DigitalOceanCustomer-operated
Servers / containers
Open Source / Open Core

MIT

Official Railway one-click template or Docker on a DigitalOcean Ubuntu DropletCustomer manages the Railway project or DigitalOcean Droplet, application secrets, model credentials, data services, backups, scaling and upgrades. Railway operates its platform; Droplet users also maintain the operating system and Docker runtime.
Scope and evidence

The Railway path runs in the customer's project on platform-managed infrastructure; the DigitalOcean path uses a customer-operated Droplet. External model, embedding, search and tool providers receive data according to customer configuration. Review generated secrets, public networking, persistent data services and image updates before production use.

  • LibreChat one-click deployment on Railway — LibreChat documents creating a Railway account, reviewing the template's three containers and environment variables, deploying the services and accessing the resulting LibreChat URL in the customer's Railway project.

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

  • LibreChat deployment on DigitalOcean — The upstream guide creates an Ubuntu Droplet in the customer DigitalOcean project, configures a user and firewall, then links to the Docker installation steps. The example is for a small personal deployment, not a production sizing guarantee.

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

Cloud evidence reviewed 2026-11-15

LiteLLM Proxy Self-HostedAWS, Azure, Google Cloud, Railway, RenderCustomer-operated
Servers / containers
Open Source / Open Core

MIT outside the enterprise directory; enterprise code and features have separate license terms.

Official container image, Docker Compose or Kubernetes deployment; production infrastructure examples are documented.Customer manages gateway availability, credentials, database, access policies, logs and upgrades, including pinning versions and verifying release artifacts with the documented version-appropriate Cosign method; model providers remain separate services.
Scope and evidence

The gateway forwards each request to its configured model provider. Self-hosting the proxy does not ensure prompts stay inside the account: external model APIs, guardrail services and logging integrations can receive data. Use appropriate self-hosted inference endpoints and explicitly review outbound integrations when required. For release integrity, release images and the Helm chart starting with v1.111.0-dev.3 use keyless Cosign signatures bound to LiteLLM's release workflow; earlier releases require the documented historical public keys. The October 21 incident affected PyPI v1.107.0 and Docker Hub/GHCR v1.107.0 plus mutable latest, main-latest and main-stable tags during the documented exposure windows. Check the incident's artifact digests and remediation instructions; the compromised images carried valid historical signatures, so signature verification alone does not establish safety. LiteLLM v1.110.0 changes authentication, guardrail, accounting, and S3 behavior. The 1.108.11 LTS patch also fixes Bedrock guarded_text handling and restricts os.environ team settings to proxy administrators; review both the selected release line and existing incident-response or image-signing guidance. LiteLLM v1.108.12 LTS fixes tool_policy allowing blocked /v1/messages tool names longer than 64 characters. The standard v1.110.1 UI image changes to slim nginx and removes curl while retaining wget and nc, so retest health probes and scripts that assume curl.

  • LiteLLM production deployment — Official production guidance covers EKS, AKS and GKE with Helm, plus Terraform on AWS and Google Cloud. The proxy, database and Redis deployment is separate from the model services it calls.

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

  • LiteLLM Railway and Render deployment options — The current upstream deployment guide supplies Railway and Render deployment buttons in addition to its EKS/AKS/GKE instructions, followed by readiness and Admin UI verification. These are customer application deployments on managed platforms; configure persistent data, secrets and external model-provider endpoints separately.

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

Cloud evidence reviewed 2026-11-12

LocalAIAWSCustomer-operated
Servers / containers
Open Source / Open Core

MIT License for upstream LocalAI. Model artifacts and inference backends can have different license and hardware requirements.

Run official CPU/GPU Docker images or the documented binaries and configure models, storage and endpoint access.Customer manages models, backends, hardware capacity, API authentication, persistent storage and upgrades.
Scope and evidence

CPU availability does not guarantee acceptable performance for every model. Model galleries and artifact downloads contact external registries; optional integrations and remote backends can change data boundaries.

  • LocalAI and Flowise on AWS EKS with Pulumi — This Pulumi-authored deployment recipe, linked by the LocalAI project, runs LocalAI inference and Flowise on customer EKS infrastructure. The demonstrated configuration uses CPU inference; review model licenses, current images, resource sizing and network exposure rather than assuming GPU support or production hardening.

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

Cloud evidence reviewed 2026-11-12

MaxKB Community EditionAlibaba CloudCustomer-operated
Servers / containers
Open Source / Open Core

GNU General Public License version 3 for Community Edition. Professional and Enterprise editions add separately licensed features and support.

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.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.
Scope and evidence

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.

  • MaxKB Community Edition service instance in Alibaba Compute Nest — 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.

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

  • MaxKB image deployment from Alibaba Cloud Marketplace — 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.

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

Cloud evidence reviewed 2026-11-16

MilvusAWS, Azure, Google CloudCustomer-operated
Servers / containers
Open Source / Open Core

Apache License 2.0 for upstream Milvus.

Run the official standalone Docker or versioned Docker Compose deployment; distributed deployments have separate operational requirements.Customer manages persistent volumes, collections, indexes, access controls, capacity, backups and upgrades.
Scope and evidence

Current installation scripts can track a different image than a selected stable release; use versioned configurations for reproducibility. Model inference and embedding generation are separate workloads. Managed Zilliz offerings are outside this listing.

  • Milvus deployment on Amazon EKS — Official instructions provision Amazon EKS and deploy Milvus using Helm. Review persistent storage, object storage, networking and cluster sizing for the selected version.

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

  • Milvus deployment on Azure Kubernetes Service — Official instructions provision Azure Kubernetes Service and deploy Milvus using Helm. Review persistent storage, object storage, networking and cluster sizing for the selected version.

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

  • Milvus deployment on Google Kubernetes Engine — Official instructions provision Google Kubernetes Engine and deploy Milvus using Helm. Review persistent storage, object storage, networking and cluster sizing for the selected version.

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

Cloud evidence reviewed 2026-11-12

Minute (i.AI)AWSCustomer-operated
Servers / containers
Open Source / Open Core

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

TerraformCustomer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope and evidence

The project is explicitly in incubation. Government and council reports establish pilot use; the public Terraform depends on environment, identity and shared-platform resources that an adopting organization must supply. Azure Speech and language-model calls can send recording or transcript data outside the AWS application boundary. Human review remains necessary for formal minutes.

  • Terraform ECS — AWS ECS application and worker services, database, SQS, storage and separately configured speech and language-model services. The project is explicitly in incubation. Government and council reports establish pilot use; the public Terraform depends on environment, identity and shared-platform resources that an adopting organization must supply. Azure Speech and language-model calls can send recording or transcript data outside the AWS application boundary. Human review remains necessary for formal minutes.

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

Cloud evidence reviewed 2026-11-19

MLflow Tracking Server Self-HostedAWS, Azure, Google CloudCustomer-operated
Servers / containers
Open Source / Open Core

Apache 2.0 for upstream MLflow; connected model providers and managed distributions have separate terms.

Python MLflow server command, official Docker Compose bundle or Kubernetes Helm deployment.Customer operates server access, metadata and artifact stores, retention, backups, scaling and version upgrades.
Scope and evidence

Traces can capture model inputs, outputs and intermediate metadata. Point clients at the customer-hosted server and review recording/redaction settings. Applications, evaluators and optional model integrations may still call external providers; hosting the tracking server does not host all training or inference runtimes. Production database, storage and security configuration differ from a local quickstart.

  • Self-hosted MLflow deployment on AWS — The project documents deployment of the MLflow server, metadata database and artifact storage on AWS. This does not refer to a managed MLflow edition or to model serving alone.

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

  • Self-hosted MLflow deployment on Azure — The project documents deployment of the MLflow server, metadata database and artifact storage on Azure. This does not refer to a managed MLflow edition or to model serving alone.

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

  • Self-hosted MLflow deployment on Google Cloud — The project documents deployment of the MLflow server, metadata database and artifact storage on Google Cloud. This does not refer to a managed MLflow edition or to model serving alone.

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

Cloud evidence reviewed 2026-11-12

n8n Self-HostedAWS, Azure, Google Cloud, DigitalOcean, Heroku, HetznerCustomer-operated
Servers / containers
Source Available

Sustainable Use License for covered code; separate commercial Enterprise license for enterprise components

Docker Compose with persistent data; database and worker topology selected for workloadCustomer manages servers/containers, secrets, database, backup/restore, scaling and upgrades.
Scope and evidence

This entry excludes n8n Cloud. The Sustainable Use License has use restrictions and should not be described as unrestricted open-source licensing. Enterprise components require the appropriate commercial license. External integrations, AI providers and optional assistant services require separate data-flow review. n8n@2.48.6 and the maintained n8n@1.123.99 line move official images to patched Node runtimes carrying a V8 process-abort fix. The 1.x image also moves to Node 24.22.3, while 2.x pins a patched Node 26.13.0. Update the selected line and verify custom images use the fixed runtime.

  • n8n deployment on AWS — Project instructions deploy n8n and PostgreSQL on customer-operated EKS. Review persistence, ingress and production scaling requirements.

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

  • n8n deployment on Azure — Project instructions deploy n8n with PostgreSQL on Azure Kubernetes Service in the customer subscription.

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

  • n8n deployment on Google Cloud Run — The project documents Cloud Run deployment. Its easy mode is not the production configuration; follow the durable-mode guidance for production and review execution and persistence constraints.

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

  • n8n self-hosted deployment on DigitalOcean — The project provides a provider-specific application deployment guide, including customer project/server creation, persistent application data and n8n configuration. DigitalOcean and Hetzner use customer-operated servers; Heroku uses a customer app and PostgreSQL service on platform-managed infrastructure. This is separate from n8n Cloud.

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

  • n8n self-hosted deployment on Heroku — The project provides a provider-specific application deployment guide, including customer project/server creation, persistent application data and n8n configuration. DigitalOcean and Hetzner use customer-operated servers; Heroku uses a customer app and PostgreSQL service on platform-managed infrastructure. This is separate from n8n Cloud.

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

  • n8n self-hosted deployment on Hetzner — The project provides a provider-specific application deployment guide, including customer project/server creation, persistent application data and n8n configuration. DigitalOcean and Hetzner use customer-operated servers; Heroku uses a customer app and PostgreSQL service on platform-managed infrastructure. This is separate from n8n Cloud.

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

Cloud evidence reviewed 2026-11-12

NVIDIA AI EnterpriseAWS, Azure, Google Cloud, Oracle Cloud, Alibaba Cloud, Tencent Cloud, Volcano EngineCustomer-operated
Servers / containers
Commercial Only

Commercial NVIDIA AI Enterprise subscription, consumption or perpetual license; most customer-cloud paths require BYOL.

NVIDIA AI Enterprise or GPU-optimized cloud VM images, standard instances with BYOL, or managed Kubernetes on supported cloud providersCustomer manages cloud GPU instances or Kubernetes, drivers, GPU Operator and container runtime, networking, storage, identities, NGC access, model services, monitoring, upgrades and license activation.
Scope and evidence

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 on AWS, Azure and Google Cloud — 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.

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

  • NVIDIA AI Enterprise on Oracle Cloud and Alibaba Cloud — 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.

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

  • NVIDIA AI Enterprise on Tencent Cloud standard instances — 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.

    Vendor / upstream documentation · Reviewed 2026-11-16 · Scope: NVIDIA AI Enterprise standard-instance BYOL. Vendor support commitment: not assessed; confirm the selected release and contract.

  • NVIDIA AI Enterprise on ByteDance Volcano Engine standard instances — 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.

    Vendor / upstream documentation · Reviewed 2026-11-16 · Scope: NVIDIA AI Enterprise standard-instance BYOL. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-16

Onyx Self-HostedAWS, Azure, Google Cloud, DigitalOceanCustomer-operated
Servers / containers
Open Source / Open Core

MIT Community Edition; Business and Enterprise features use separate commercial terms.

Docker Compose on a VM or official Kubernetes and Terraform deploymentCustomer manages application services, databases, search, object storage, connectors, model credentials, backups, scaling and upgrades.
Scope and evidence

This entry covers self-hosted Onyx, not a vendor-hosted environment. External LLM, embedding and connector services receive data according to the customer's configuration. Business and Enterprise features and support require separate commercial entitlements.

  • Onyx on AWS — Onyx documents self-hosting on a customer EC2 instance and links a production EKS architecture using AWS managed dependencies.

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

  • Onyx on Azure — Onyx documents self-hosting on an Azure VM and an AKS Terraform path using customer Azure managed services.

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

  • Onyx on Google Cloud — Onyx documents Compute Engine and production GKE deployment paths in the customer's Google Cloud project.

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

  • Onyx on DigitalOcean — Onyx documents installing its self-hosted stack on a customer DigitalOcean Droplet.

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

Cloud evidence reviewed 2026-11-14

Open WebUI Self-HostedAWS, Azure, Google CloudCustomer-operated
Servers / containers
Source Available

Open WebUI license based on BSD-style terms with additional branding restrictions and defined exceptions; enterprise terms may be required for rebranding.

Official Docker image, Python installation or Kubernetes deployment.Customer runs application storage, authentication, provider configuration, updates and backups.
Scope and evidence

The UI sends messages to the model endpoint selected for a conversation. Local Ollama or vLLM endpoints can keep inference on customer infrastructure; cloud APIs, embeddings, tools and plugins have separate data flows. The current license restricts branding removal in larger deployments, with small-deployment, permission and enterprise-license exceptions; review the actual terms. Open WebUI v0.13.4 replaces Direct Connections and Integrations with Tether and migrates image settings. Deployments using Terminals server connections require Terminals 0.4.0 or later; upgrading that server from 0.3.x requires manual migration. Open Terminal and Tether terminal connections are unaffected by this migration. Tether introduces user-device and local-command paths that require explicit trust review.

  • Open WebUI deployment on AWS ECS / Fargate — Project deployment instructions cover the application on AWS ECS / Fargate with external database, Redis and file storage. Model inference is separate; review model endpoints, egress and WebSocket/runtime limits.

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

  • Open WebUI deployment on Azure Container Apps — Project deployment instructions cover the application on Azure Container Apps with external database, Redis and file storage. Model inference is separate; review model endpoints, egress and WebSocket/runtime limits.

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

  • Open WebUI deployment on Google Cloud Run — Project deployment instructions cover the application on Google Cloud Run with external database, Redis and file storage. Model inference is separate; review model endpoints, egress and WebSocket/runtime limits.

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

Cloud evidence reviewed 2026-11-12

OpenLITDigitalOceanCustomer-operated
Servers / containers
Open Source / Open Core

Apache License 2.0 for upstream OpenLIT. Models and external integrations have separate terms.

Run the official Docker Compose platform or documented Kubernetes deployment with its persistent telemetry services.Customer manages telemetry collection, analytical storage, capture policies, access controls, retention and upgrades.
Scope and evidence

Configure instrumentation to send telemetry to the self-hosted receiver. Optional LLM-based evaluations and integrations can call external services; hosting the observability platform does not host every model being observed.

  • OpenLIT deployment on DigitalOcean Kubernetes — DigitalOcean documents the OpenLIT Kubernetes add-on, Helm installation verification and access to the application in the customer cluster. Review the included application and ClickHouse versions, persistent storage and access controls; this is the observability platform, not just its instrumentation SDK.

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

Cloud evidence reviewed 2026-11-12

OpenSearchRailwayCustomer-operated
Servers / containers
Open Source / Open Core

Apache License 2.0 for upstream OpenSearch. Separately operated managed services and connected model or data services have their own terms.

Run official Docker images and customize the documented Docker Compose examples; native package and tarball installations are also documented.Customer manages cluster sizing, storage, shard and replica layout, TLS, users and roles, ingestion, snapshots, monitoring and upgrades.
Scope and evidence

Sample deployments and demo security settings require production configuration. Official images distributed through Amazon ECR are not evidence of an AWS-specific deployment. The listing covers self-operated OpenSearch; Amazon OpenSearch Service and other managed services are separate delivery models. Embeddings and AI connectors can involve external models or services. OpenSearch 3.10.0 removes experimental Views and macOS x64 archives and fixes remote-store data-loss or stall paths, bulk-index corruption, heap leaks, snapshot queue stalls, remote-translog issues, and OOM behavior. Validate plugins, Dashboards, and storage recovery before upgrading.

  • Self-operated OpenSearch and Dashboards on Railway — The community recipe deploys OpenSearch 3 and Dashboards as customer-project services, with the search API on private networking. Its wrappers derive from upstream OpenSearch images. Review node count, heap/storage sizing, security plugin configuration, TLS and backups; this is separate from Amazon OpenSearch Service and does not imply high availability.

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

Cloud evidence reviewed 2026-11-12

Qdrant Self-HostedGoogle CloudCustomer-operated
Servers / containers
Open Source / Open Core

Apache 2.0 for the upstream database; managed cloud offerings and support have separate commercial terms.

Official Docker image for local/server deployment; production storage, access controls and scaling require configuration.Customer manages persistence, backups, access controls, upgrades and any distributed-cluster operations.
Scope and evidence

The local quickstart is an installation starting point, not a secured production configuration. Applications can supply their own vectors or use separately configured embedding models. External embedding APIs and hosted inference can receive source data even when the database is self-hosted; local FastEmbed is a documented alternative. This entry excludes Qdrant Cloud hosting. Qdrant 1.20.1, released November 13, 2026, prevents collection-scoped JWTs from viewing snapshot telemetry for collections they cannot access; operators using scoped JWTs should upgrade.

  • Self-operated Qdrant cluster on Google Kubernetes Engine — Google documents provisioning a regional GKE cluster and installing Qdrant with Helm and persistent disks. The customer operates the database cluster; this is separate from Qdrant Cloud and its separately offered Hybrid Cloud service.

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

Cloud evidence reviewed 2026-11-12

RAGFlowAWS, Azure, Google Cloud, Alibaba Cloud, RailwayCustomer-operated
Servers / containers
Open Source / Open Core

Apache License 2.0 for upstream RAGFlow; models, data assets and dependencies retain their own terms.

Versioned upstream Docker Compose, provider-specific VM packages or community deployment templates; select a path compatible with the intended RAGFlow release.Customer manages document storage, indexing, app services, access controls, model endpoints, backups and upgrades.
Scope and evidence

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.

  • Community RAGFlow deployment on AWS ECS Fargate through stdapi.ai — 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.

    Community template · Reviewed 2026-11-12 · Scope: Community / upstream open-source; third-party distribution where noted · Version: 0.26.4. Vendor support commitment: not assessed; confirm the selected release and contract.

  • cloudimg RAGFlow Azure VM deployment and operations guide — 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.

    Third party package · Reviewed 2026-11-12 · Scope: Community / upstream open-source; third-party distribution where noted · Version: 0.26.4. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Techlatest RAGFlow VM deployment in a customer Google Cloud project — 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.

    Third party package · Reviewed 2026-11-12 · Scope: Community / upstream open-source; third-party distribution where noted. Vendor support commitment: not assessed; confirm the selected release and contract.

  • RAGFlow Community deployment on Alibaba Cloud Compute Nest — 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.

    Provider guide · Reviewed 2026-11-12 · Scope: Community / upstream open-source; third-party distribution where noted. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Community RAGFlow Railway application stack — 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.

    Community template · Reviewed 2026-11-12 · Scope: Community / upstream open-source; third-party distribution where noted · Version: 0.27.1. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Railway deployment image source and release pin — 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.

    Community template · Reviewed 2026-11-12 · Scope: Community / upstream open-source; third-party distribution where noted · Version: 0.27.1. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-12

Red Hat OpenShift AI Self-ManagedAWS, Azure, Google Cloud, Oracle Cloud, IBM CloudCustomer-operated
Servers / containers
Commercial Only

Commercial Red Hat OpenShift AI Self-Managed subscription; an eligible OpenShift subscription is also required.

OpenShift AI Operator through OperatorHub or the oc command-line interfaceCustomer manages the OpenShift cluster, storage, accelerators, identity, networking, model data, backups and upgrades within Red Hat's supported configuration matrix.
Scope and evidence

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

  • OpenShift AI Self-Managed on supported OpenShift public-cloud platforms — Red Hat's Self-Managed matrix explicitly lists OpenShift Container Platform on AWS, Azure, Google Cloud, IBM Cloud and Oracle Cloud. The selected OpenShift release, subscriptions, storage, accelerator and component restrictions apply; managed cloud-service add-ons are a separate offering.

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

Cloud evidence reviewed 2026-11-17

SAS Viya PlatformAWS, Azure, Google CloudCustomer-operated
Servers / containers
Commercial Only

Commercial SAS Viya licensing; deployment assets and a JWT license are delivered for the customer's software order.

Provision EKS, AKS or GKE with SAS Terraform projects, then deploy Kubernetes manifests generated through Kustomize and SAS automationCustomer manages Kubernetes, networking, ingress, storage, PostgreSQL, identity, sizing, backups, platform updates and licensed deployment assets.
Scope and evidence

The public SAS infrastructure repositories are Apache-licensed deployment tooling; SAS Viya itself is commercial software and requires licensed order assets and a JWT license. Kubernetes and PostgreSQL are mandatory. SAS states that its infrastructure-as-code projects satisfy most, not all, deployment requirements. The viya4-deployment project can patch the same manifest but does not move an installation to a different cadence, version or software offering. SAS November bulletins cover compromised eMudhra certificates and critical Brotli CVE-2026-111497 across specified Viya branches. Use the vendor matrices to identify the exact affected component and fixed maintenance level; do not treat a generic Viya version as sufficient.

  • SAS Viya infrastructure on AWS — Official SAS Terraform provisions customer AWS resources including EKS, storage and optional RDS, after which the customer deploys licensed Viya assets.

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

  • SAS Viya infrastructure on Azure — Official SAS Terraform provisions customer Azure resources including AKS, storage and optional PostgreSQL, after which the customer deploys licensed Viya assets.

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

  • SAS Viya infrastructure on Google Cloud — Official SAS Terraform provisions customer Google Cloud resources including GKE, storage and optional Cloud SQL, after which the customer deploys licensed Viya assets.

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

Cloud evidence reviewed 2026-11-17

SGLangGoogle CloudCustomer-operated
Servers / containers
Open Source / Open Core

Apache License 2.0 for upstream SGLang. Model weights and hardware/runtime dependencies have their own licenses.

Install the package or use official containers; the reviewed primary installation path targets Linux with supported NVIDIA GPUs and compatible drivers.Customer manages accelerator capacity, model artifacts, runtime compatibility, endpoint access, including isolation of debug and dumper routes, monitoring, and upgrades.
Scope and evidence

Model downloads may require external registries and gated-model credentials. Pin compatible model/runtime/image versions and review model-specific permissions. Generic container instructions do not establish deployment badges for every hyperscaler. CVE-2026-111391 rates SGLang 0.5.10 through 0.5.22 critical (CVSS v4.0 9.2) for Python code execution through the debug dumper filter. The upstream report demonstrates the shared-API path with DUMPER_SERVER_PORT=reuse: an ordinary API-key holder can reach it when no separate admin API key is configured; access can be anonymous when no API key is configured. With an admin API key configured, that key is required. Exploitation also requires access to the dumper configuration and a subsequent model execution that reaches a dumper hook. Upstream issue #44188 remains open, and the v0.5.23 tag still contains the eval-based filter path even though that tag is outside the CVE record's enumerated affected range. Do not enable or expose the debug dumper endpoint; restrict it at the network layer and verify an upstream fix before treating a later version as remediated.

  • SGLang compatibility with GKE Inference Gateway — Google explicitly supports SGLang as an alternative model server in its customer-operated multi-cluster GKE inference architecture. The worked manifests use vLLM; SGLang requires its own deployment, serving port, metric mapping and compatible Endpoint Picker image. Review GPU/model requirements, licenses and resource availability.

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

Cloud evidence reviewed 2026-11-12

Strategy Enterprise in Your CloudAWS, Azure, Google Cloud, STACKITVendor-operated BYOC
Servers / containers
Commercial Only

Commercial Strategy Enterprise subscription; customer-cloud deployment is not available with the Standard plan.

Vendor-assisted, fully managed deployment into the customer's licensed AWS, Azure Google Cloud or STACKIT environmentStrategy administers and maintains the platform; the customer supplies the cloud environment, data sources, identity, network approvals and shared governance responsibilities.
Scope and evidence

This entry covers the Strategy Enterprise customer-cloud option, not Strategy Standard in the vendor's managed environment. Strategy describes the service as fully managed despite its deployment in a customer-licensed AWS, Azure Google Cloud or STACKIT environment, so it is classified as BYOC rather than fully customer-operated. Confirm contract-specific account ownership, cloud-resource billing, service availability, support boundaries and cloud-commitment eligibility before procurement.

  • Strategy Enterprise in customer-licensed AWS, Azure or Google Cloud — Strategy documents a dedicated single-tenant deployment in a customer-licensed AWS, Azure or GCP environment and states that its cloud team administers and maintains the service on the customer's behalf. The pricing page separately limits own-cloud deployment to Enterprise.

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

  • Strategy Enterprise customer-cloud deployment on STACKIT — The current pricing FAQ explicitly lists STACKIT alongside AWS, Azure and Google Cloud for Enterprise deployment in the customer cloud environment. Standard is vendor-hosted; contract-specific regions, account access, support and commitment eligibility remain procurement checks.

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

Cloud evidence reviewed 2026-11-17

vLLM Self-HostedAWS, Azure, Google CloudCustomer-operated
Servers / containers
Open Source / Open Core

Apache 2.0 for vLLM; model weights and supporting dependencies have independent licenses and access conditions.

Official vLLM Docker image or supported Python installation; choose a compatible hardware/backend configuration.Customer manages model acquisition, hardware capacity, endpoint protection, availability, upgrades and model/runtime compatibility.
Scope and evidence

This entry covers the inference server, not a hosted model service. It can run supported model weights on customer infrastructure, but those weights may need external downloads or access approval and are not licensed by vLLM. Review default usage telemetry and optional outbound integrations; hosting inference does not automatically create an air-gapped system. vLLM v0.34.0 removes Model Runner V1; configurations setting VLLM_USE_V2_MODEL_RUNNER=0 now fail at startup. It changes the default block size from 16 to 64, enables extensible KV cache by default with gpu_memory_utilization defaulting to 1.0, drops ROCm 7.2 wheels and images in favor of ROCm 10.0, requires huggingface_hub 2.0.0 or later, and removes QuTLASS/fp_quant and Marlin W4A8 support. Review the upstream breaking-change table and test model, quantization, memory, and accelerator compatibility before rollout.

  • vLLM Production Stack deployment on Amazon EKS — The project publishes Amazon EKS provisioning and vLLM deployment scripts in its versioned Production Stack guide. Verify current chart versions, model licenses, accelerator availability, GPU quotas and storage; this is customer-hosted inference, not a hosted model API.

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

  • vLLM Production Stack deployment on Azure Kubernetes Service — The project publishes Azure Kubernetes Service provisioning and vLLM deployment scripts in its versioned Production Stack guide. Verify current chart versions, model licenses, accelerator availability, GPU quotas and storage; this is customer-hosted inference, not a hosted model API.

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

  • vLLM Production Stack deployment on Google Kubernetes Engine — The project publishes Google Kubernetes Engine provisioning and vLLM deployment scripts in its versioned Production Stack guide. Verify current chart versions, model licenses, accelerator availability, GPU quotas and storage; this is customer-hosted inference, not a hosted model API.

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

Cloud evidence reviewed 2026-11-12

Weaviate Self-HostedAWS, Google CloudCustomer-operated
Servers / containers
Open Source / Open Core

BSD-3-Clause core outside the wl directory; wl code and associated enterprise features require a separate enterprise license/key.

Docker or Docker Compose, or a Kubernetes deployment using Helm. Google’s GKE guide uses Terraform to provision the cluster.Customer manages authentication, storage, backup, scaling, configuration and upgrades.
Scope and evidence

The Docker defaults include anonymous access and default telemetry; production installations must configure the intended controls. Pre-vectorized data can be searched without an external vectorizer, but enabled embedding, reranking or generation integrations may call external providers. Telemetry is enabled by default and has a documented opt-out; the entire current codebase must not be described as uniformly BSD-licensed. Weaviate v1.39.17 fixes a v1.39 runtime-reindex restart bug in which writes arriving before reindex resumed could be absent from the new property index, or an incomplete index could be swapped in after partial files disappeared. Operators remaining on v1.39 should update and verify filter/search results; the primary reviewed release remains the newer v1.40.5 line.

  • Weaviate self-managed AWS deployment options — The vendor documents a self-managed EKS deployment path. Use that path for this listing: the same page also describes Shared Cloud marketplace SaaS, which is a separate deployment option.

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

  • Deploy self-hosted Weaviate on Google Kubernetes Engine — Google documents provisioning a private GKE Standard or Autopilot cluster in the customer’s project with Terraform and installing Weaviate with Helm. The customer operates the database.

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

Cloud evidence reviewed 2026-11-21

Choose 2–4 listings to compare

Browse listing cards

How these listings fit

AnythingLLM Docker
Self-hosted AI application interface and retrieval/agent integrations; model inference is separately configured.
Arize Phoenix Self-Hosted
AI development and operations tooling for tracing and evaluation rather than a model-serving runtime.
Cloudera on Cloud
Machine-learning and AI workload services are available within the Cloudera platform, subject to provider and subscription availability.
Dataiku DSS Cloud Stacks
Provides customer-operated data science, machine-learning, generative-AI, model-deployment and AI-governance capabilities.
Dify Self-Hosted
Visual AI application and RAG workflow platform available as a self-hosted container stack.
Elastic Cloud on Kubernetes
Vector search and licensed machine-learning capabilities support retrieval and AI-oriented workloads.
Hyperscience Hypercell
Commercial document-intake and extraction platform installed into customer Kubernetes infrastructure.
KNIME Business Hub
Provides customer-operated execution and governance for data-science, machine-learning and generative-AI workflows.
Langflow Self-Hosted
Visual AI workflow and agent builder with Docker and persistent PostgreSQL deployment.
Langfuse Self-Hosted
Self-hosted LLM observability, evaluations and prompt-management platform.
LibreChat Self-Hosted
Provides a self-hosted interface and orchestration layer for model endpoints, agents, MCP tools, authentication and administrative controls.
LiteLLM Proxy Self-Hosted
Self-hosted AI API gateway providing model routing, access controls and usage tracking.
LocalAI
Customer-operated model-serving infrastructure with CPU and optional accelerator backends.
MaxKB Community Edition
Customer-hosted agent and workflow platform with knowledge bases, MCP and tool integrations, and configurable language, embedding, reranking and multimodal models.
Milvus
Embedding storage and vector retrieval infrastructure for AI search and RAG applications.
Minute (i.AI)
Open-source meeting transcription and minute generation developed for public-sector use.
MLflow Tracking Server Self-Hosted
Self-hosted experiment tracking and LLM/agent observability with customer-controlled metadata and artifacts.
n8n Self-Hosted
Orchestrates AI providers, agents, tools and memory as workflows. Model inference and external service dependencies are configured separately.
NVIDIA AI Enterprise
Provides an enterprise-supported suite of AI frameworks, infrastructure software, operations components and development tools.
Onyx Self-Hosted
Provides self-hosted indexing, retrieval, model integration and agent services for building internal AI experiences.
Open WebUI Self-Hosted
Self-hosted AI chat and knowledge interface for local model servers and cloud APIs.
OpenLIT
AI instrumentation, evaluation and operational feedback tooling with a self-hosted platform.
OpenSearch
Vector storage, semantic search and retrieval for AI applications and RAG. Embedding generation and model connectors have separately configured runtimes and data flows.
Qdrant Self-Hosted
Self-hosted vector database for semantic retrieval and AI application data.
RAGFlow
Self-hosted document ingestion, retrieval and context infrastructure for AI applications.
Red Hat OpenShift AI Self-Managed
AI workbenches, pipelines, model serving and lifecycle tooling delivered on a customer-operated OpenShift platform.
SAS Viya Platform
Model development, machine learning, model management and AI operationalization; exact products depend on the licensed order.
SGLang
Customer-operated inference infrastructure for serving supported model weights.
Strategy Enterprise in Your Cloud
Enterprise includes customizable AI agents and AI-assisted analysis capabilities; exact features and model integrations follow the contracted platform.
vLLM Self-Hosted
Self-hosted model inference and serving engine with OpenAI-compatible APIs.
Weaviate Self-Hosted
Self-hosted vector-search database for retrieval and AI applications.

Review dates and sources appear on each listing. Functionality, edition, deployment and licensing must be checked together. Filter this category with cloud and deployment controls →

All categories · Suggest a listing or correction