
# AI tools & infrastructure on Google Cloud

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

Canonical page: https://launchinyourcloud.com/clouds/gcp/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: Google Cloud project
- Provider group: cloud-infrastructure
- Provider classification: Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Source: https://docs.cloud.google.com/resource-manager/docs/creating-managing-projects (checked 2026-11-20).
- Network: VPC network
- Identity and access: IAM policies and service accounts
- Installation guidance: Terraform, optionally using Infrastructure Manager for resource provisioning; deploy the application separately.
- Guidance source: https://docs.cloud.google.com/infrastructure-manager/docs/overview
- Guidance reviewed: 2026-11-10


### Private offers

Cloud Marketplace vendors can negotiate a private offer for a specified Cloud Billing account. Check duration, renewal terms and commitment treatment in the actual agreement.
Source: https://docs.cloud.google.com/marketplace/docs/offers/discover-private-offers (reviewed 2026-11-14).

### Private connectivity

Private Service Connect connects VPC consumers to supported managed or producer services. Confirm the actual product endpoint and network/DNS architecture.
Source: https://docs.cloud.google.com/vpc/docs/private-service-connect (reviewed 2026-11-14).

### External workload access

Workload Identity Federation can grant external workloads scoped Google Cloud access without long-lived service-account keys. Validate the trust configuration and exact roles.
Source: https://docs.cloud.google.com/iam/docs/workload-identity-federation (reviewed 2026-11-14).

### Regulated environments

Assured Workloads applies control packages for residency and access boundaries. Confirm supported services, regions and the product deployment; it is not automatic product certification.
Source: https://docs.cloud.google.com/assured-workloads/docs/overview (reviewed 2026-11-14).

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

24 listings.


## AnythingLLM Docker

Self-hosted application for document-grounded AI chat, retrieval and agents.

- Listing: https://launchinyourcloud.com/directory/anythingllm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT License for upstream AnythingLLM; model weights, connectors and provider services have separate terms.
- Licensing model: open-source
- Installation: Run the official Docker edition on a customer-operated host with persistent application storage and configured model/vector endpoints.
- Architecture: Customer-operated web application and document/retrieval storage with configurable inference providers
- Operations: Customer manages users, documents, persistent storage, model access, integration secrets, backups and upgrades.
- Product website: https://anythingllm.com/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

MIT License for upstream AnythingLLM; model weights, connectors and provider services have separate terms. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated web application and document/retrieval storage with configurable inference providers. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- ai-applications-rag: Multi-user application for document-grounded chat, RAG and agents with configurable model and vector-database integrations.

- ai-tools: Self-hosted AI application interface and retrieval/agent integrations; model inference is separately configured.

### Deployment boundaries


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

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.anythingllm.com/installation-docker/overview (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.anythingllm.com/installation-docker/overview (checked 2026-11-12). 


### Cloud deployment evidence

- AnythingLLM Docker installation overview (aws, gcp, railway): https://docs.anythingllm.com/installation-docker/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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Public release notes credit named contributors and new contributors across multiple releases, alongside an established open contribution process.

Reviewed 2026-11-10.

- Release maintenance and contributor credits: https://github.com/Mintplex-Labs/anything-llm/releases

- Community contribution process: https://github.com/Mintplex-Labs/anything-llm

### Sources

- Official installation and runtime: https://docs.anythingllm.com/installation-docker/overview

- Upstream project and capabilities: https://github.com/Mintplex-Labs/anything-llm

- Current upstream license: https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/master/LICENSE

- AnythingLLM v1.20.0 release: https://github.com/Mintplex-Labs/anything-llm/releases/tag/v1.20.0

### Licensing sources

- https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/master/LICENSE

### Infrastructure sources

- https://docs.anythingllm.com/installation-docker/overview


### 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: Documented. The self-hosted Docker configuration offers Simple SSO passthrough: a trusted application uses an API key to issue short-lived single-use login links for existing users. It requires multi-user mode and a configured admin. This is a bespoke integration, not native SAML/OIDC federation; the vendor recommends internally exposed instances. Scope: Docker Simple SSO passthrough; not standards-based federation. Source: https://docs.anythingllm.com/configuration (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: AnythingLLM v1.20.0 hardens embed history, extension API-key authorization, workspace-agent access, password recovery, framing, and document-tool downloads. Upgrade the server and extension to compatible 1.20+ releases and review optional MCP identity forwarding. Scope: Upstream v1.20.0 release notes; no consolidated affected-version range is asserted.. Source: https://github.com/Mintplex-Labs/anything-llm/releases/tag/v1.20.0 (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Docker guide documents a prebuilt application image or source-built Compose setup. Persistent storage and user permissions must be configured; local model/vector endpoints and their resources are separate. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.anythingllm.com/installation-docker/local-docker (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The Docker requirements list 2 GB RAM, a two-core CPU with AVX2 and 5 GB storage as a small starting profile. Model inference, embeddings, vector storage, documents and concurrency can require much more; verify AVX2 passthrough on virtual machines. This is not an HA or 1-TB production recommendation. Scope: Self-hosted Docker baseline; model services, data and HA additional. Source: https://docs.anythingllm.com/installation-docker/system-requirements (reviewed 2026-11-20).

- License pricing: Documented. The reviewed upstream core is MIT 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/Mintplex-Labs/anything-llm/master/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. AnythingLLM v1.20.0 was published November 17, 2026. It includes access and session hardening plus MCP identity forwarding and timeout changes; keep server and extension versions compatible. Scope: Upstream AnythingLLM self-hosted release. Source: https://github.com/Mintplex-Labs/anything-llm/releases/tag/v1.20.0 (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- AnythingLLM 1.20.0 access hardening (security-advisory): AnythingLLM v1.20.0 hardens embed history, extension API-key authorization, workspace-agent access, password recovery, framing, and document-tool downloads. Scope: Upstream v1.20.0 release notes; no consolidated affected-version range is asserted. Conditions: Applicability depends on enabled embedding, extensions, agents, recovery, and document tools. Action: Upgrade the server and extension to compatible 1.20+ releases and review optional MCP identity forwarding. Source: https://github.com/Mintplex-Labs/anything-llm/releases/tag/v1.20.0; reviewed 2026-11-18.




## Arize Phoenix Self-Hosted

AI observability and evaluation server for traces, datasets and application experiments.

- Listing: https://launchinyourcloud.com/directory/phoenix/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, railway, render
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Elastic License 2.0; includes restrictions on providing the software as a hosted/managed service and on license-key circumvention. This is source-available.
- Licensing model: source-available
- Installation: Use the official self-hosted Docker/Compose or Kubernetes deployment instructions and configure persistent storage and instrumentation endpoints.
- Architecture: Customer-operated trace/evaluation application with persistent trace and dataset storage
- Operations: Customer manages trace capture, storage, authentication, retention, evaluation providers, backups and upgrades.
- Product website: https://arize.com/phoenix/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

Elastic License 2.0; includes restrictions on providing the software as a hosted/managed service and on license-key circumvention. This is source-available. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated trace/evaluation application with persistent trace and dataset storage. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- ai-observability: AI trace collection, evaluation, datasets, experiments and prompt analysis for instrumented model applications.

- ai-tools: AI development and operations tooling for tracing and evaluation rather than a model-serving runtime.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://arize.com/docs/phoenix/self-hosting (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://arize.com/docs/phoenix/self-hosting (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://arize.com/docs/phoenix/self-hosting (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://arize.com/docs/phoenix/self-hosting (checked 2026-11-12). 

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://arize.com/docs/phoenix/self-hosting (checked 2026-11-12). 


### Cloud deployment evidence

- Phoenix self-hosting deployment options (aws, azure, gcp, railway): https://arize.com/docs/phoenix/self-hosting
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Phoenix self-hosted Render Blueprint (render): https://arize.com/docs/phoenix/self-hosting
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Arize's June 2026 maintainer account describes actual participation outside the core team: it attributes OIDC authentication to users needing Keycloak/Cognito and credits contributors with expanding framework integrations and OpenInference. The upstream release history shows continuing maintenance. This concerns concrete community involvement rather than repository star counts; it does not certify any named customer's deployment model.

Reviewed 2026-11-10.

- Maintainer account of user-contributed authentication and integrations: https://arize.com/blog/phoenix-10k/

- Current Phoenix maintenance releases: https://github.com/Arize-ai/phoenix/releases

### Sources

- Official installation and runtime: https://arize.com/docs/phoenix/self-hosting

- Upstream project and capabilities: https://github.com/Arize-ai/phoenix

- Current upstream license: https://raw.githubusercontent.com/Arize-ai/phoenix/main/LICENSE

### Licensing sources

- https://raw.githubusercontent.com/Arize-ai/phoenix/main/LICENSE

### Infrastructure sources

- https://arize.com/docs/phoenix/self-hosting


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Phoenix documents OAuth2 authorization-code login with OIDC provider discovery, configured alongside application authentication and secret settings. Configure the trusted provider, callback and account policy; client API keys remain a separate surface. Scope: Self-hosted Phoenix UI OAuth2/OIDC. Source: https://arize.com/docs/phoenix/deployment/authentication (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream Phoenix repository provides self-hosting/container documentation for the observability server. Match persistence and authentication settings to the chosen release; instrumented applications and model services remain separate. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://github.com/arize-ai/phoenix (reviewed 2026-11-14). Deployment artifact: https://github.com/arize-ai/phoenix. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Sources checked — unresolved. The self-hosting guide documents deployment, storage/database configuration and trace retention, but does not establish a complete CPU/RAM minimum for a specified workload. Size span ingestion, retention, database, evaluation/model dependencies and redundant service instances. Hosted Arize AX sizing is a separate offering. Scope: Phoenix self-hosted application and data services; numeric workload sizing unresolved. Source: https://arize.com/docs/phoenix/self-hosting/deploying-phoenix.md (reviewed 2026-11-20).

- License pricing: Documented. Phoenix uses Elastic License 2.0, including limits on offering substantial hosted/managed functionality and bypassing licence controls. This is not an unrestricted Apache/MIT licence or a hosted-service price; review commercial service/support terms separately. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/Arize-ai/phoenix/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

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







## Cloudera on Cloud

Cloudera-managed control plane that provisions data, analytics and AI workload services into a customer's public-cloud account.

- Listing: https://launchinyourcloud.com/directory/cloudera-on-cloud/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Shared operations · vendor control plane
- Infrastructure IDs: servers
- License: Commercial Cloudera subscription with cloud infrastructure charges paid separately.
- Licensing model: commercial-only
- Installation: Register the customer cloud environment and credentials, then provision Cloudera workload services through the control plane
- Architecture: Vendor-operated control plane with data, compute, networking and workload environments in the customer's cloud account.
- Operations: Cloudera operates the service control plane; the customer owns cloud resources, credentials, data governance, network integration, workload sizing and shared operational responsibilities.
- Product website: https://www.cloudera.com/products/cloudera-cloud.html
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers 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 on Cloud is a commercial subscription service. Customer cloud-resource charges and Cloudera software/service consumption are separate.

The customer account contains persistent data and compute services while Cloudera operates an external control plane. Runtime topology varies by selected workload service.


### Category fit

- data-analytics: Managed data engineering, warehousing and analytics services operate over data in customer cloud environments.

- streaming: Cloudera provides streaming ingestion and processing services where supported by the selected cloud deployment.

- ai-tools: Machine-learning and AI workload services are available within the Cloudera platform, subject to provider and subscription availability.

### Deployment boundaries


- aws: Customer cloud account; Shared operations; control plane: vendor-hosted. Source: https://docs.cloudera.com/cdp-public-cloud/cloud/getting-started/topics/cdp-set_up_cloud_prerequisites.html (checked 2026-11-17). 

- azure: Customer cloud account; Shared operations; control plane: vendor-hosted. Source: https://docs.cloudera.com/cdp-public-cloud/cloud/getting-started/topics/cdp-set_up_cloud_prerequisites.html (checked 2026-11-17). 

- gcp: Customer cloud account; Shared operations; control plane: vendor-hosted. Source: https://docs.cloudera.com/cdp-public-cloud/cloud/getting-started/topics/cdp-set_up_cloud_prerequisites.html (checked 2026-11-17). 

Operating responsibility: Cloudera operates the control plane while workloads run in the customer's cloud accounts. Customer responsibilities include credentials, account policies, workload configuration and data governance; confirm each selected service's responsibility split. Source: https://www.cloudera.com/products/trust-center/shared-responsibility-model.html (checked 2026-11-20).


### Cloud deployment evidence

- Cloudera workloads in customer AWS, Azure and Google Cloud environments (aws, azure, gcp): https://docs.cloudera.com/cdp-public-cloud/cloud/getting-started/topics/cdp-set_up_cloud_prerequisites.html
  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.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Cloudera public-cloud architecture and ownership: https://docs.cloudera.com/cdp-public-cloud/cloud/overview/topics/cdp-public-cloud.html

- Cloud prerequisites and credential setup: https://docs.cloudera.com/cdp-public-cloud/cloud/getting-started/topics/cdp-set_up_cloud_prerequisites.html

- Cloudera workload services: https://docs.cloudera.com/cdp-public-cloud/cloud/overview/topics/cdp-services.html

- Cloudera pricing: https://www.cloudera.com/products/pricing.html

- Cloudera TSB-2026-1007: https://docs.cloudera.com/cdp-private-cloud-base/7.3.3/private-release-notes/topics/tsb-2026-1007.html

- Cloudera TSB-2026-1009: https://docs.cloudera.com/runtime/7.3.3/public-release-notes/topics/tsb-2026-1009.html

### Licensing sources

- https://www.cloudera.com/products/pricing.html

### Infrastructure sources

- https://docs.cloudera.com/cdp-public-cloud/cloud/overview/topics/cdp-public-cloud.html

- https://docs.cloudera.com/cdp-public-cloud/cloud/overview/topics/cdp-services.html


### Buyer diligence


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

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


- Marketplace delivery: Sources checked — unresolved. The Google partnership page still labels Marketplace deployment coming soon. A current offer for the selected workload service and provider was not established from these sources. Scope: Reviewed public evidence for Cloudera on Cloud; unresolved within this edition/deployment. Source: https://www.cloudera.com/partners/solutions/google-cloud-platform.html (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Platform pricing and cloud cost-optimization guidance do not establish which software fees qualify for a buyer’s committed-spend agreement. Scope: Reviewed public evidence for Cloudera on Cloud; unresolved within this edition/deployment. Source: https://www.cloudera.com/products/pricing.html (reviewed 2026-11-17).

- Single sign-on: Documented. Management Console supports federation using enterprise SAML IdP metadata. Identity-provider creation is privileged; duplicate group names across IdPs can grant unintended memberships. Scope: Cloudera-managed control plane for customer-cloud workloads. Source: https://docs.cloudera.com/management-console/cloud/user-management/topics/mc-setting-up-the-identity-provider-in-cdp.html (reviewed 2026-11-17).

- SCIM provisioning: Documented. Cloudera documents SCIM with Entra ID alongside SAML federation. Only one SCIM IdP per account is supported; userName and group-name changes are unsupported, so choose stable identifiers. Scope: Cloudera account provisioning, not a self-hosted SCIM server. Source: https://docs.cloudera.com/management-console/cloud/user-management/topics/mc-configuring_scim_with_azure_ad.html (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed Cloudera on Cloud material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage. Scope: Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited. Source: https://docs.cloudera.com/management-console/cloud/user-management/topics/mc-known_issues_and_troubleshooting_related_to_idp_setup_in_cdp.html (reviewed 2026-11-17).

- Security controls: Documented. The user-management guidance warns about mutable identity keys and concurrent SAML/SCIM group synchronization. Align stable NameID/userName values and review privileged account/group mappings. Current advisory review: Cloudera TSBs address critical Brotli CVE-2026-111497 and compromised eMudhra certificates in specified CDP components. Apply the exact fixed component build and review affected certificate trust. Scope: Management Console identity synchronization and permissions Affected and fixed versions vary by Runtime and Private Cloud Base component; consult TSB-2026-1007 and TSB-2026-1009.. Source: https://docs.cloudera.com/cdp-private-cloud-base/7.3.3/private-release-notes/topics/tsb-2026-1007.html (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://docs.cloudera.com/management-console/cloud/user-management/topics/mc-known_issues_and_troubleshooting_related_to_idp_setup_in_cdp.html. Supporting source: TSB-2026-1009 — https://docs.cloudera.com/runtime/7.3.3/public-release-notes/topics/tsb-2026-1009.html.

- Air-gapped operation: Sources checked — unresolved. This listing uses an external vendor control plane. The reviewed public-cloud setup does not establish complete isolated operation; Cloudera Private Cloud documentation is a different offering. Scope: Reviewed public evidence for Cloudera on Cloud; unresolved within this edition/deployment. Source: https://docs.cloudera.com/cdp-public-cloud/cloud/getting-started/topics/cdp-set_up_cloud_prerequisites.html (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. Customer-cloud setup requires cloud account credentials, network prerequisites and an environment registration before Cloudera provisions workloads. The vendor control plane remains external to the customer account. Scope: Cloudera public-cloud environment setup; services differ by provider. Source: https://docs.cloudera.com/cdp-public-cloud/cloud/getting-started/topics/cdp-set_up_cloud_prerequisites.html (reviewed 2026-11-17).

- Minimum footprint / sizing: Sources checked — unresolved. The platform offers multiple workload services with different node, storage and database needs. The overview does not establish one minimum HA footprint for 100 users/1 TB; select the actual services and workload configuration. Scope: Cloudera on cloud workload-specific sizing. Source: https://docs.cloudera.com/cdp-public-cloud/cloud/overview/topics/cdp-services.html (reviewed 2026-11-17).

- License pricing: Documented. Cloudera on Cloud is a commercial subscription service. Customer cloud-resource charges and Cloudera software/service consumption are separate. Scope: Cloudera on Cloud: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://www.cloudera.com/products/pricing.html (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Select workload services, Data Lake/runtime topology, data scans/compute-hours and provider-specific service availability. Vendor fees and customer-cloud resources are billed separately. A complete monthly operating estimate is not established. Scope: Requested planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA, average usage; missing workload metrics and commercial terms are explicit. Source: https://docs.cloudera.com/cdp-public-cloud/cloud/overview/topics/cdp-services.html (reviewed 2026-11-17).

- Release snapshot / cadence: Sources checked — unresolved. Management Console and customer-cloud workload services have independent release/runtime lines. A single platform latest-version number or universal upgrade schedule was not established. Scope: Reviewed public evidence for Cloudera on Cloud; unresolved within this edition/deployment. Source: https://docs.cloudera.com/cdp-public-cloud/cloud/overview/topics/cdp-services.html (reviewed 2026-11-17).




### Security and lifecycle reviews

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

- Cloudera November 2026 Brotli and certificate bulletins (security-advisory): Cloudera TSBs address critical Brotli CVE-2026-111497 and compromised eMudhra certificates in specified CDP components. Scope: Affected and fixed versions vary by Runtime and Private Cloud Base component; consult TSB-2026-1007 and TSB-2026-1009. Conditions: Bundled Brotli and certificate trust stores determine exposure. Action: Apply the exact fixed component build and review affected certificate trust. Source: https://docs.cloudera.com/cdp-private-cloud-base/7.3.3/private-release-notes/topics/tsb-2026-1007.html; reviewed 2026-11-18. Supporting source: TSB-2026-1009 — https://docs.cloudera.com/runtime/7.3.3/public-release-notes/topics/tsb-2026-1009.html.




## Dataiku DSS Cloud Stacks

Commercial Dataiku DSS deployment managed through Fleet Manager inside a customer AWS, Azure or Google Cloud tenant.

- Listing: https://launchinyourcloud.com/directory/dataiku-dss-cloud-stacks/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Dataiku license or license token required for the full Cloud Stacks capabilities.
- Licensing model: commercial-only
- Installation: AWS CloudFormation, Azure ARM template or Google Cloud Infrastructure Manager with Terraform
- Architecture: Customer-hosted Fleet Manager provisioning VM-backed DSS instances and optional elastic Kubernetes compute in the customer's cloud tenant
- Operations: Customer manages cloud accounts, Fleet Manager, IAM identities, networking, VM and Kubernetes capacity, storage, TLS, backups, upgrades and license configuration.
- Product website: https://www.dataiku.com/product/
- Source review: 2026-11-16; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

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.

The listed fully featured Cloud Stacks deployment requires a Dataiku license or license token. Dataiku documents a separate DSS Free Edition, but that does not determine the licensing of the listed Cloud Stacks offering.

Cloud Stacks deploys a persistent Fleet Manager and VM-backed DSS nodes in the customer tenant, with optional EKS, AKS or GKE elastic-compute clusters.


### Category fit

- data-analytics: Provides customer-operated data preparation, analytics, visual workflows, elastic computation and governed data projects.

- ai-tools: Provides customer-operated data science, machine-learning, generative-AI, model-deployment and AI-governance capabilities.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://doc.dataiku.com/dss/latest/installation/cloudstacks-aws/guided-setup-new-vpc-elastic-compute.html (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://doc.dataiku.com/dss/latest/installation/cloudstacks-azure/guided-setup-new-vnet-elastic-compute.html (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://doc.dataiku.com/dss/latest/installation/cloudstacks-gcp/guided-setup-new-vpc-elastic-compute.html (checked 2026-11-16). 


### Cloud deployment evidence

- Dataiku DSS Cloud Stacks on AWS (aws): https://doc.dataiku.com/dss/latest/installation/cloudstacks-aws/guided-setup-new-vpc-elastic-compute.html
  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.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.

- Dataiku DSS Cloud Stacks on Azure (azure): https://doc.dataiku.com/dss/latest/installation/cloudstacks-azure/guided-setup-new-vnet-elastic-compute.html
  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.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.

- Dataiku DSS Cloud Stacks on Google Cloud (gcp): https://doc.dataiku.com/dss/latest/installation/cloudstacks-gcp/guided-setup-new-vpc-elastic-compute.html
  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.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.


### Sources

- Dataiku DSS installation options: https://doc.dataiku.com/dss/latest/installation/

- Dataiku Cloud Stacks for AWS: https://doc.dataiku.com/dss/latest/installation/cloudstacks-aws/index.html

- Dataiku Cloud Stacks for Azure: https://doc.dataiku.com/dss/latest/installation/cloudstacks-azure/index.html

- Dataiku Cloud Stacks for Google Cloud: https://doc.dataiku.com/dss/latest/installation/cloudstacks-gcp/index.html

- Dataiku DSS licensing: https://doc.dataiku.com/dss/latest/operations/license.html

### Licensing sources

- https://doc.dataiku.com/dss/latest/operations/license.html

- https://doc.dataiku.com/dss/latest/installation/cloudstacks-aws/tenant-settings.html

### Infrastructure sources

- https://doc.dataiku.com/dss/latest/installation/

- https://doc.dataiku.com/dss/latest/installation/cloudstacks-aws/index.html

- https://doc.dataiku.com/dss/latest/installation/cloudstacks-azure/concepts.html

- https://doc.dataiku.com/dss/latest/installation/cloudstacks-gcp/index.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: Sources checked — unresolved. The reviewed Dataiku Trial offer delivers an AWS AMI and uses an externally purchased license. That does not establish the current fully featured Cloud Stacks entitlement or a Fleet Manager deployment; confirm the selected contract and installer separately. Scope: Trial AMI versus the listed commercial Cloud Stacks offering. Source: https://aws.amazon.com/marketplace/pp/prodview-hrcm5q34opptc (reviewed 2026-11-16).

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. DSS 15 documents SAML and OpenID Connect SSO. Its SAML compatibility list includes Okta, Entra ID, ADFS, Auth0 and Keycloak; encrypted SAML assertions are explicitly unsupported. Configure the DSS instance and identity provider together. Scope: DSS instance authentication within Cloud Stacks; license and enabled features still govern entitlement. Source: https://doc.dataiku.com/dss/latest/security/sso.html (reviewed 2026-11-16). Supporting source: DSS authentication mechanisms — https://doc.dataiku.com/dss/latest/security/authentication/.

- SCIM provisioning: Sources checked — unresolved. DSS documents SSO/LDAP/Azure AD user suppliers, login-time provisioning and administrative synchronization. These mechanisms do not establish a SCIM protocol endpoint; the reviewed authentication manual leaves direct SCIM support unresolved. Scope: DSS 15 user suppliers and synchronization; not a claim that SCIM is unsupported. Source: https://doc.dataiku.com/dss/latest/security/authentication/ (reviewed 2026-11-16).

- Compliance attestations: Documented. Dataiku’s published certificate 1850881-6 covers its organizational ISMS/PIMS supporting the Dataiku platform, including R&D. It was issued 2026-04-30 and expires 2027-12-14, subject to surveillance. The certificate expressly does not authorize labeling products, processes or services as certified; it does not certify the customer’s Cloud Stacks environment. Scope: Dataiku Inc. ISO/IEC 27001:2022 and 27701:2019 organizational management systems; not a customer-deployment certificate. Source: https://downloads.dataiku.com/publicdocs/Dataiku_ISO_27001_Certificate_of_Registration.pdf (reviewed 2026-11-16). Supporting source: Self-managed and SaaS account boundaries — https://www.dataiku.com/legal/trust.

- Security controls: Documented. For AWS Cloud Stacks, Fleet Manager recommends an IAM instance profile for cloud API calls. If it stores secrets, they are encrypted with an AWS KMS customer-managed key. HTTP access is used for image lists, license verification and OIDC. Scope: Fleet Manager AWS access, optional secret storage and outbound requirements. Source: https://doc.dataiku.com/dss/latest/installation/cloudstacks-aws/tenant-settings.html (reviewed 2026-11-16).

- Air-gapped operation: Sources checked — unresolved. DSS 15 documents offline document-extraction resources, but Fleet Manager’s standard Cloud Stacks setup uses HTTP for image lists, license updates/verification and OIDC. The reviewed material does not establish an end-to-end disconnected Cloud Stacks procedure. Scope: Cloud Stacks/Fleet Manager boundary; an offline DSS feature does not establish a disconnected management stack. Source: https://doc.dataiku.com/dss/latest/installation/cloudstacks-aws/tenant-settings.html (reviewed 2026-11-16). Supporting source: DSS 15 air-gapped extraction upgrade notes — https://doc.dataiku.com/dss/latest/release_notes/15.html.

- Deployment artifact / IaC: Documented. The GCP guide deploys Fleet Manager with Infrastructure Manager and Terraform. It identifies gs://dataiku-cloudstacks/templates/fleet-manager/15.2.1/fleet-manager-instance.tf and a separate terraform.tfvars file. This is the guide’s versioned example, not a universal latest-version claim; AWS uses CloudFormation and Azure uses ARM templates. Scope: Cloud Stacks Fleet Manager; provider-specific templates and permissions. Source: https://doc.dataiku.com/dss/latest/installation/cloudstacks-gcp/guided-setup-new-vpc-elastic-compute.html (reviewed 2026-11-16). Supporting source: AWS Cloud Stacks — https://doc.dataiku.com/dss/latest/installation/cloudstacks-aws/index.html. Supporting source: Azure Cloud Stacks — https://doc.dataiku.com/dss/latest/installation/cloudstacks-azure/concepts.html.

- Minimum footprint / sizing: Documented. DSS 15’s server requirements specify x86-64 Linux and at least 32 GB RAM, with more for in-memory data and additional users. This sizes the DSS application component only; Fleet Manager, execution infrastructure and cloud services add resources. Scope: DSS 15 application requirements; not a complete Cloud Stacks architecture estimate. Source: https://doc.dataiku.com/dss/latest/installation/custom/requirements.html (reviewed 2026-11-16).

- License pricing: Documented. The listed fully featured Cloud Stacks deployment requires a Dataiku license or license token. Dataiku documents a separate DSS Free Edition, but that does not determine the licensing of the listed Cloud Stacks offering. Scope: Dataiku DSS Cloud Stacks: software license terms; infrastructure and operating costs are separate. Source: https://doc.dataiku.com/dss/latest/operations/license.html (reviewed 2026-11-16). Supporting source: Edition and license conditions — https://doc.dataiku.com/dss/latest/installation/cloudstacks-aws/tenant-settings.html.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The reviewed vendor release is 15.2.2, published 2026-11-06. This is a dated, scoped snapshot; it does not establish compatibility with another chart, cloud package or commercial edition. Scope: DSS application release; Fleet Manager templates and deployed instance versions may differ; source supplies a publication day, not a timestamp. Source: https://doc.dataiku.com/dss/latest/release_notes/15.html (reviewed 2026-11-16).







## Elastic Cloud on Kubernetes

Elastic's Kubernetes operator for deploying and operating Elasticsearch, Kibana and related Elastic Stack resources in customer clusters.

- Listing: https://launchinyourcloud.com/directory/elastic-cloud-on-kubernetes/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Elastic License 2.0 distribution with free Basic capabilities; Enterprise licensing unlocks additional features and support.
- Licensing model: source-available
- Installation: Official ECK Helm chart or Kubernetes manifests on EKS, AKS or GKE
- Architecture: Customer-operated Kubernetes operator and Elastic Stack stateful workloads with persistent storage.
- Operations: Customer manages Kubernetes, storage, resource sizing, security, snapshots, upgrades and availability; Elastic licensing controls advanced features and support.
- Product website: https://www.elastic.co/elastic-cloud-kubernetes
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers 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.

The ECK and Elastic Stack distribution is governed by Elastic License 2.0 rather than an OSI-approved open-source license. A free Basic tier is available; Enterprise features and support require a subscription.

ECK manages persistent Elasticsearch and related container workloads on customer Kubernetes with durable volumes and operator reconciliation.


### Category fit

- databases-vector: Elasticsearch provides distributed document storage, full-text search and vector search in a customer cluster.

- observability: Elastic Stack collects and analyzes logs, metrics and traces; exact integrations and features depend on the selected license.

- data-analytics: Search, aggregations and Kibana visualizations support interactive analysis of indexed data.

- ai-tools: Vector search and licensed machine-learning capabilities support retrieval and AI-oriented workloads.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s (checked 2026-11-17). 


### Cloud deployment evidence

- Elastic Cloud on Kubernetes on EKS, AKS and GKE (aws, azure, gcp): https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s
  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.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Deploy Elastic Cloud on Kubernetes: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s

- Install ECK with Helm or manifests: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/install

- Manage the ECK license: https://www.elastic.co/docs/deploy-manage/license/manage-your-license-in-eck

- Self-managed Elastic pricing and editions: https://www.elastic.co/pricing/self-managed

- ECK 3.5.0 security update ESA-2026-113: https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-113/389493

- ECK 3.5.0 security update ESA-2026-145: https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-145/390105

- ECK 3.5.0 security update ESA-2026-146: https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-146/390106

### Licensing sources

- https://www.elastic.co/docs/deploy-manage/license/manage-your-license-in-eck

- https://www.elastic.co/pricing/self-managed

### Infrastructure sources

- https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s

- https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/install


### Buyer diligence


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

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


- Marketplace delivery: Edition-dependent. Elastic documents an ECK BYOL offering inside Google Distributed Cloud air-gapped Marketplace. This is a specific isolated GDC deployment route, not proof that an Elastic Cloud Hosted marketplace subscription delivers ECK in a customer AWS account. Scope: ECK in GDC air-gapped Marketplace; separate from hosted Elastic procurement. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/eck-gdch (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. A GDC air-gapped BYOL Marketplace route does not establish AWS Marketplace commitment treatment for a self-managed ECK Enterprise subscription. Scope: Reviewed public evidence for Elastic Cloud on Kubernetes; unresolved within this edition/deployment. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/eck-gdch (reviewed 2026-11-17).

- Single sign-on: Edition-dependent. ECK deployments can configure Elasticsearch/Kibana external SAML or OIDC realms, with the applicable self-managed subscription. Elastic Cloud organization SSO is a separate control plane. Scope: ECK application authentication; subscription eligibility must be checked. Source: https://www.elastic.co/docs/deploy-manage/users-roles/cluster-or-deployment-auth/managed-credentials-eck (reviewed 2026-11-17). Supporting source: Self-managed subscription feature matrix — https://www.elastic.co/pricing/self-managed.

- SCIM provisioning: Sources checked — unresolved. ECK documents external realms and native/file user management, but a native ECK application SCIM provisioning endpoint was not established. Ingesting another product’s SCIM audit logs is not SCIM support. Scope: Reviewed public evidence for Elastic Cloud on Kubernetes; unresolved within this edition/deployment. Source: https://www.elastic.co/docs/deploy-manage/users-roles/cluster-or-deployment-auth/managed-credentials-eck (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed Elastic Cloud on Kubernetes material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage. Scope: Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited. Source: https://www.elastic.co/docs/deploy-manage/users-roles/cluster-or-deployment-auth/managed-credentials-eck (reviewed 2026-11-17).

- Security controls: Documented. ECK manages credentials in Kubernetes secrets and supports rotation and disabling the default elastic superuser when using external identity. Restrict secret/RBAC access and configure application roles. Current advisory review: ESA-2026-113, 145, and 146 fix service-token exposure, cross-namespace certificate injection, and retained cross-namespace credentials. Upgrade to ECK 3.5.0 or later and rotate the service token where directed. Scope: ECK managed credentials and external realms Affected ECK releases before 3.5.0; exact component and configuration ranges follow the three advisories.. Source: https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-113/389493 (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://www.elastic.co/docs/deploy-manage/users-roles/cluster-or-deployment-auth/managed-credentials-eck. Supporting source: ESA-2026-145 — https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-145/390105. Supporting source: ESA-2026-146 — https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-146/390106.

- Air-gapped operation: Documented. ECK documents offline operation with locally mirrored operator and Elastic Stack images. Integrations also need local package, artifact and endpoint repositories; mirroring the operator alone is insufficient. Scope: ECK isolated deployment with all selected dependencies staged. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/air-gapped-install (reviewed 2026-11-17). Supporting source: Additional offline dependency repositories — https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/eck-gdch.

- Deployment artifact / IaC: Documented. Elastic supplies ECK installation through Helm or Kubernetes manifests. Pin the operator and compatible Elastic application versions and configure persistent storage and RBAC; the operator is not a vendor-operated service. Scope: Self-managed ECK operator installation. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/install (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. HA guidance calls for three master-eligible nodes, multiple nodes per data tier and at least one index replica. CPU, memory, shard layout and disk headroom depend on indexing/search workload; no universal 100-user minimum is established. Scope: ECK availability topology, not benchmarked resource sizing. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/nodes-orchestration (reviewed 2026-11-17).

- License pricing: Documented. The ECK and Elastic Stack distribution is governed by Elastic License 2.0 rather than an OSI-approved open-source license. A free Basic tier is available; Enterprise features and support require a subscription. Scope: Elastic Cloud on Kubernetes: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://www.elastic.co/docs/deploy-manage/license/manage-your-license-in-eck (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Illustrative priced infrastructure subtotal: USD 1,428.76/month. Three 8-vCPU/64-GiB workers across three AZs host three master/data nodes and two Kibana replicas. The storage assumption is 1,000 GB primary indexed data plus one replica, with 3,000 GB total data capacity and 150 GB boot capacity. This is not a complete operating-cost estimate or a validated capacity/SLA claim. Scope: Editorial ECK scenario; load/ingest rate and indexed-data expansion must be measured. Separate shard/zone placement and failure testing are required. No Savings Plans, Spot or credits.. Source: https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json (reviewed 2026-11-17). Supporting source: Product topology/sizing basis — https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/nodes-orchestration. Supporting source: Current AWS documentation: us-east-1 gp3 capacity example — https://docs.aws.amazon.com/solutions/latest/cloud-migration-factory-on-aws/cost.html. Supporting source: EBS performance and charging qualifications — https://aws.amazon.com/ebs/pricing/. Supporting source: EKS standard versus extended support pricing — https://aws.amazon.com/eks/pricing/.

- Release snapshot / cadence: Documented. Elastic Cloud on Kubernetes 3.5.0 fixes service-token exposure, cross-namespace certificate injection, and retained cross-namespace credentials. Rotate the service token after upgrade where ESA-2026-113 requires it. Scope: ECK operator 3.5.0 security update. Source: https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-113/389493 (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- Elastic Cloud on Kubernetes 3.5.0 security update (security-advisory): ESA-2026-113, 145, and 146 fix service-token exposure, cross-namespace certificate injection, and retained cross-namespace credentials. Scope: Affected ECK releases before 3.5.0; exact component and configuration ranges follow the three advisories. Conditions: Namespace boundaries, service tokens, and managed resource lifecycle determine exposure. CVE-2026-72648 has no workaround. Action: Upgrade to ECK 3.5.0 or later and rotate the service token where directed. Source: https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-113/389493; reviewed 2026-11-18. Supporting source: ESA-2026-145 — https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-145/390105. Supporting source: ESA-2026-146 — https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-146/390106.




## Hyperscience Hypercell

Commercial document-intake and extraction platform installed into customer Kubernetes infrastructure.

- Listing: https://launchinyourcloud.com/directory/hyperscience/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Helm / Kubernetes operator; Kubernetes manifests
- Architecture: Hyperscience Helm application, database, object storage, workers and separately prepared container registry on AWS or GKE Standard.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://help.hyperscience.ai/deployment/docs/helm-chart
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

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.

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

Hyperscience Helm application, database, object storage, workers and separately prepared container registry on AWS or GKE Standard. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- correspondence-management: Commercial document-intake and extraction platform installed into customer Kubernetes infrastructure.

- ai-tools: Commercial document-intake and extraction platform installed into customer Kubernetes infrastructure.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.hyperscience.ai/deployment/docs/helm-chart (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.hyperscience.ai/deployment/docs/kubernetes-installation-overview (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.hyperscience.ai/deployment/docs/helm-chart (checked 2026-11-19). 


### Cloud deployment evidence

- Helm Chart (AWS/GCP) (aws, gcp): https://help.hyperscience.ai/deployment/docs/helm-chart
  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.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Kubernetes Installation Overview (azure): https://help.hyperscience.ai/deployment/docs/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.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Helm Chart (AWS/GCP): https://help.hyperscience.ai/deployment/docs/helm-chart

- Kubernetes Installation Overview: https://help.hyperscience.ai/deployment/docs/kubernetes-installation-overview

- hsk8s CLI (ECR/GAR): https://help.hyperscience.ai/deployment/docs/artifacts-management-and-hsk8s-hyperscience-kubernetes-cli

- Gov Mailrooms & Correspondence: https://www.hyperscience.ai/blog/the-trusted-ai-infrastructure-behind-modern-government/

- Hyperscience EULA: https://www.hyperscience.ai/legal-documents/eula/

- V44 Release Notes (2026-11-18): https://help.hyperscience.ai/docs/v44-release-notes

- Security Advisory (2026-10-30): https://help.hyperscience.ai/docs/security-advisory

- Helm Releases: https://help.hyperscience.ai/deployment/docs/news-and-release-notes

- Hypercell Brotli decoder remediation: https://help.hyperscience.ai/docs/security-advisory

### Licensing sources

- https://www.hyperscience.ai/legal-documents/eula/

### Infrastructure sources

- https://help.hyperscience.ai/deployment/docs/helm-chart

- https://help.hyperscience.ai/deployment/docs/kubernetes-installation-overview


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The private-cloud deployment guide documents SP-initiated SAML federation using IdP metadata, attribute mapping and signed/encrypted assertion settings. Only one of SAML, OIDC, LDAP or Google authentication can be enabled. Confirm the application/chart version and licensed integration before rollout. Scope: Private-cloud/on-premises Hyperscience identity configuration. Source: https://help.hyperscience.ai/deployment/docs/saml.md (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor supplies an entitled Helm chart and hsk8s tooling, with AWS/GCP values examples and separate application-image delivery. Pin chart and application versions independently; configure external secrets, database, storage and worker/GPU tiers. Sample image tags do not establish the current supported release. Scope: Commercial Hypercell Kubernetes distribution; entitled artifacts required. Source: https://help.hyperscience.ai/deployment/docs/helm-chart (reviewed 2026-11-20). Deployment artifact: https://help.hyperscience.ai/deployment/docs/artifacts-management-and-hsk8s-hyperscience-kubernetes-cli. Artifact reference: Vendor-provided HS_HELM_CHART; choose compatible application/chart releases.

- Minimum footprint / sizing: Sources checked — unresolved. The VM guide requires at least 8 logical cores with a 1:4 CPU-to-GB-RAM ratio and documents throughput examples. These VM numbers do not establish the complete Helm/Kubernetes namespace, trainer, database and object-store footprint. Obtain current chart resource values and workload/HA sizing; ORCA GPU requirements are separate. Scope: VM baseline documented; selected Kubernetes production footprint unresolved. Source: https://help.hyperscience.ai/deployment/docs/infrastructure-requirements.md (reviewed 2026-11-20). Supporting source: Kubernetes dependencies and deployment boundary — https://help.hyperscience.ai/deployment/docs/kubernetes-installation-overview.md.

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.




### Security and lifecycle reviews

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

- Hypercell Brotli decoder remediation (security-advisory): The vendor documents CVE-2026-111497 and version-dependent PDF/HTTP response exposure. Scope: Hypercell v33.0–v44.0; the vendor lists fixes 44.0.2, 43.2.5, 42.3.19, 42.0.27, 41.0.39 and 40.0.39. Other or archived lines need an agreed upgrade path. Conditions: PDF decoding is an additional path in v42–v44; earlier listed versions have configured HTTP-response exposure. SaaS patching does not patch customer installations. Action: Apply the fix for the installed Hypercell line and follow the documented sequential upgrades or temporary workarounds. Source: https://help.hyperscience.ai/docs/security-advisory; reviewed 2026-11-19.




## KNIME Business Hub

Commercial workflow collaboration and automation platform launched from AWS, Azure or Google Cloud Marketplace VM images.

- Listing: https://launchinyourcloud.com/directory/knime-business-hub/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial KNIME Business Hub license or Marketplace software subscription required.
- Licensing model: commercial-only
- Installation: Official AWS, Azure or Google Cloud Marketplace virtual-machine image
- Architecture: Single Marketplace virtual machine containing KNIME Business Hub services and execution infrastructure with persistent customer storage
- Operations: Customer manages the cloud account, virtual machine, networking, DNS, TLS, identity, storage, backups, capacity, upgrades and Business Hub license.
- Product website: https://www.knime.com/knime-hub
- Source review: 2026-11-16; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

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 Basic, Standard and Enterprise are commercial offerings. Marketplace software pricing or a separately obtained BYOL license applies, depending on the selected image.

The reviewed Marketplace paths run KNIME Business Hub and its execution services on a persistent virtual machine in the customer's cloud account.


### Category fit

- data-analytics: Provides governed collaboration, automation, execution and deployment for analytical workflows and data applications.

- ai-tools: Provides customer-operated execution and governance for data-science, machine-learning and generative-AI workflows.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.knime.com/hub/latest/aws_marketplace_business_hub_guide/ (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.knime.com/hub/latest/azure_marketplace_business_hub_guide/ (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.knime.com/hub/latest/gc_marketplace_business_hub_guide/ (checked 2026-11-16). 


### Cloud deployment evidence

- KNIME Business Hub on AWS Marketplace (aws): https://docs.knime.com/hub/latest/aws_marketplace_business_hub_guide/
  KNIME documents launching Business Hub from an AWS Marketplace AMI into the customer's AWS account, with Marketplace or BYOL software licensing.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.

- KNIME Business Hub on Azure Marketplace (azure): https://docs.knime.com/hub/latest/azure_marketplace_business_hub_guide/
  KNIME documents launching Business Hub from an Azure Marketplace single-VM image into the customer's Azure subscription.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.

- KNIME Business Hub on Google Cloud Marketplace (gcp): https://docs.knime.com/hub/latest/gc_marketplace_business_hub_guide/
  KNIME documents launching Business Hub through Google Cloud Marketplace using a Google Compute VM image in the customer's project.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.


### Sources

- KNIME Business Hub on AWS Marketplace: https://docs.knime.com/hub/latest/aws_marketplace_business_hub_guide/

- KNIME Business Hub on Azure Marketplace: https://docs.knime.com/hub/latest/azure_marketplace_business_hub_guide/

- KNIME Business Hub on Google Cloud Marketplace: https://docs.knime.com/hub/latest/gc_marketplace_business_hub_guide/

- KNIME Business Hub installation guide: https://docs.knime.com/hub/latest/business_hub_installation_guide/

- KNIME Business Hub pricing and licensing: https://www.knime.com/knime-hub-pricing

### Licensing sources

- https://www.knime.com/knime-hub-pricing

- https://docs.knime.com/hub/latest/aws_marketplace_business_hub_guide/

### Infrastructure sources

- https://docs.knime.com/hub/latest/aws_marketplace_business_hub_guide/

- https://docs.knime.com/hub/latest/azure_marketplace_business_hub_guide/

- https://docs.knime.com/hub/latest/gc_marketplace_business_hub_guide/


### Buyer diligence


Research coverage: 10/12 fields (83%); 9 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: Edition-dependent. The official AWS and Azure guides link Basic, Standard and BYOL VM offers. PAYG software charges or a separate BYOL entitlement apply; cloud infrastructure charges are additional. Availability does not establish cloud-commitment eligibility. Scope: Vendor-linked AWS/Azure VM offers; region, edition and agreement govern purchase. Source: https://docs.knime.com/hub/latest/aws_marketplace_business_hub_guide/ (reviewed 2026-11-16). Supporting source: Azure Marketplace offer links — https://docs.knime.com/hub/latest/azure_marketplace_business_hub_guide/. Offer prodview-nzgqreu746eq2: KNIME; Single-instance AMI; Basic PAYG; https://aws.amazon.com/marketplace/pp/prodview-nzgqreu746eq2. Offer prodview-cd3xzq7m5fqjg: KNIME; Single-instance AMI; Standard PAYG; https://aws.amazon.com/marketplace/pp/prodview-cd3xzq7m5fqjg. Offer prodview-gwty5knsn4bp2: KNIME; Single-instance AMI; BYOL; https://aws.amazon.com/marketplace/pp/prodview-gwty5knsn4bp2. Offer knime.knime-business-hub-basic: KNIME; Virtual-machine image; Basic; https://azuremarketplace.microsoft.com/en-us/marketplace/apps/knime.knime-business-hub-basic?tab=Overview. Offer knime.knime-business-hub-standard: KNIME; Virtual-machine image; Standard; https://azuremarketplace.microsoft.com/en-us/marketplace/apps/knime.knime-business-hub-standard?tab=Overview. Offer knime.knime-business-hub-byol: KNIME; Virtual-machine image; BYOL; https://azuremarketplace.microsoft.com/en-us/marketplace/apps/knime.knime-business-hub-byol?tab=Overview.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The customer-managed installation uses Keycloak and can federate to an external identity provider through SAML 2.0, OIDC or OAuth 2.0. Map required username, email and name attributes in the knime realm. Scope: Customer-managed Business Hub identity setup; not the Knime-managed SaaS setup. Source: https://docs.knime.com/hub/latest/business_hub_installation_guide/ (reviewed 2026-11-16).

- SCIM provisioning: Edition-dependent. Standard and Enterprise document SCIM user/group provisioning, tested with Okta and Microsoft Entra ID. An administrator creates an application password/token; align usernames with the SSO mappings. Other SCIM clients are not covered by the stated test matrix. Scope: Business Hub Standard/Enterprise; excludes Basic. Source: https://docs.knime.com/hub/latest/business_hub_advanced_admin_guide/ (reviewed 2026-11-16).

- Compliance attestations: Sources checked — unresolved. The reviewed security manual explicitly describes a Knime-managed AWS/Azure account. Its ISO and encryption statements therefore do not establish a current attestation for this customer-managed Business Hub installation; obtain the applicable report/certificate scope. Scope: Knime-managed service documentation versus customer-managed Business Hub. Source: https://docs.knime.com/admin/security/ (reviewed 2026-11-16).

- Security controls: Documented. The AWS guide says its default security group exposes application and administration ports to all IPs, and its default EBS volume is unencrypted. Restrict administrative access and configure encryption before production use. Scope: AWS Marketplace guide defaults; deployment configuration remains the customer’s responsibility. Source: https://docs.knime.com/hub/latest/aws_marketplace_business_hub_guide/ (reviewed 2026-11-16).

- Air-gapped operation: Edition-dependent. The customer-managed Argo CD guide supplies an airgap bundle containing images and Helm charts. Obtain the target-version bundle from KNIME, import it into private registries and apply registry overrides. The guide requires Self Hosted Premium for the covered on-premises installation. Scope: Customer-managed Argo CD installation; not an automatic entitlement or procedure for every Marketplace VM. Source: https://docs.knime.com/hub/latest/business_hub_argocd_installation_guide/prerequisites (reviewed 2026-11-16).

- Deployment artifact / IaC: Documented. KNIME documents single-VM Marketplace images for AWS, Azure and Google Cloud. These contain a local Kubernetes installation; custom infrastructure follows a separate installation path. Select an offer and region matching the intended edition and license. Scope: Marketplace VM delivery, not a multi-node reference architecture. Source: https://docs.knime.com/hub/latest/aws_marketplace_business_hub_guide/ (reviewed 2026-11-16). Supporting source: Azure VM image deployment — https://docs.knime.com/hub/latest/azure_marketplace_business_hub_guide/. Supporting source: Google Cloud VM image deployment — https://docs.knime.com/hub/latest/gc_marketplace_business_hub_guide/.

- Minimum footprint / sizing: Documented. The AWS AMI guide recommends m5.4xlarge and one 512 GiB EBS volume as the starting minimum. Workflow load, backup and failover needs can require more. Scope: AWS Marketplace single-VM starting configuration; not a cost or HA estimate. Source: https://docs.knime.com/hub/latest/aws_marketplace_business_hub_guide/ (reviewed 2026-11-16).

- License pricing: Documented. KNIME Business Hub Basic, Standard and Enterprise are commercial offerings. Marketplace software pricing or a separately obtained BYOL license applies, depending on the selected image. Scope: KNIME Business Hub: software license terms; infrastructure and operating costs are separate. Source: https://www.knime.com/knime-hub-pricing (reviewed 2026-11-16). Supporting source: Edition and license conditions — https://docs.knime.com/hub/latest/aws_marketplace_business_hub_guide/.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The reviewed vendor release is 1.19.0, published 2026-09-03. This is a dated, scoped snapshot; it does not establish compatibility with another chart, cloud package or commercial edition. Scope: Business Hub application release; Marketplace VM and installation-package versions require separate checks; source supplies a publication day, not a timestamp. Source: https://docs.knime.com/hub/latest/business_hub_release_notes/1.19/ (reviewed 2026-11-16).







## Langflow Self-Hosted

Visual AI workflow and agent builder with Docker and persistent PostgreSQL deployment.

- Listing: https://launchinyourcloud.com/directory/langflow/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT for the upstream project; connected models, providers and bundles have their own terms.
- Licensing model: open-source
- Installation: Official Docker image or Docker Compose; Python installation and Kubernetes options are also documented.
- Architecture: Customer-operated flow application with persistent database and configured model/tool endpoints
- Operations: Customer manages the application, database, access controls, installed components, backups and version upgrades.
- Product website: https://www.langflow.org/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

The reviewed upstream Langflow project uses the MIT license. This classification covers that project; connected model weights, provider services and third-party components have their own terms.

Official images run the application on a Docker host; the Compose deployment adds persistent PostgreSQL storage. Model-serving hardware is a separate requirement if inference is also self-hosted.


### Category fit

- ai-applications-rag: Visual builder and runtime for AI flows, agents and model integrations. Local model endpoints are configurable; a flow can also call externally hosted providers.

- ai-tools: Visual AI workflow and agent builder with Docker and persistent PostgreSQL deployment.

### Deployment boundaries


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

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.langflow.org/deployment-architecture (checked 2026-11-12). 

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


### Cloud deployment evidence

- Langflow Kubernetes deployment architecture (aws, azure, gcp): https://docs.langflow.org/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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Docker and Docker Compose deployment: https://docs.langflow.org/deployment-docker

- Model components and local endpoints: https://docs.langflow.org/components-models

- Upstream MIT license: https://github.com/langflow-ai/langflow/blob/main/LICENSE

- Langflow 1.13.3 release: https://github.com/langflow-ai/langflow/releases/tag/v1.13.3

### Licensing sources

- https://github.com/langflow-ai/langflow/blob/main/LICENSE

### Infrastructure sources

- https://docs.langflow.org/deployment-docker


### 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: Documented. Current 1.13 documentation supports an upstream OIDC proxy/SSO gateway forwarding tokens that Langflow validates using issuer, audience and JWKS. It can provision a local user; built-in credentials remain a separate path. Configure the gateway and validation explicitly and replace development identity-provider examples. Scope: Langflow 1.13 external-token validation with a separately operated SSO gateway. Source: https://docs.langflow.org/external-authentication (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: Langflow 1.13.3 extends custom-component policy enforcement to background workflows and invalidates native sessions after password changes. Upgrade to 1.13.3 or later and retest component policy and session revocation. Scope: Upstream 1.13.3 release notes; no consolidated affected-version range is asserted.. Source: https://github.com/langflow-ai/langflow/releases/tag/v1.13.3 (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Docker guide provides an official image and Compose with persistent PostgreSQL, plus custom-image options. Preserve database/flow data and configure secrets, access controls and model-provider credentials. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.langflow.org/deployment-docker (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. Langflow OSS lists a dual-core CPU and 2 GB RAM minimum, recommending a multi-core CPU and at least 4 GB. This covers the Python application; external databases, model inference, workflow concurrency and HA are additional. Scope: Langflow OSS application baseline; model and production topology excluded. Source: https://docs.langflow.org/get-started-installation (reviewed 2026-11-20).

- License pricing: Documented. The reviewed upstream core is MIT 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/langflow-ai/langflow/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Langflow v1.13.3 was published November 17, 2026. It applies custom-component policy to background workflows, invalidates native sessions after password changes, updates security dependencies, and aligns Docker and wheel packaging. Scope: Upstream Langflow self-hosted release. Source: https://github.com/langflow-ai/langflow/releases/tag/v1.13.3 (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- Langflow 1.13.3 policy and session hardening (security-advisory): Langflow 1.13.3 extends custom-component policy enforcement to background workflows and invalidates native sessions after password changes. Scope: Upstream 1.13.3 release notes; no consolidated affected-version range is asserted. Conditions: Applicability depends on custom components, workflow execution mode, and native authentication. Action: Upgrade to 1.13.3 or later and retest component policy and session revocation. Source: https://github.com/langflow-ai/langflow/releases/tag/v1.13.3; reviewed 2026-11-18.




## Langfuse Self-Hosted

Self-hosted LLM observability, evaluations and prompt-management platform.

- Listing: https://launchinyourcloud.com/directory/langfuse/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, railway, render
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT core; designated enterprise directories and add-on capabilities use separate license terms or keys.
- Licensing model: open-source
- Installation: Docker Compose for a single VM; Helm/Kubernetes and official AWS, Azure and Google Cloud Terraform modules.
- Architecture: Application and worker containers with PostgreSQL, ClickHouse, Redis/Valkey and object storage
- Operations: Customer operates the deployment, persistence, access policies, retention, backups and scaling.
- Product website: https://langfuse.com/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

The main codebase uses MIT terms outside designated enterprise directories. Enterprise code requires a separate valid license, so the directory treats the combined product as open-core.

The documented deployment uses application/worker containers and persistent database, cache and object-storage services. Host/cluster capacity and database operations remain part of the self-hosted system.


Cloud evidence scope: Documented provider-specific deployment

### Category fit

- ai-observability: LLM/agent tracing, evaluation and prompt management deployed with customer-controlled storage. Evaluation and optional gateway providers must be scoped independently.

- ai-tools: Self-hosted LLM observability, evaluations and prompt-management platform.

- observability: Application/model traces and experiment visibility for AI workloads. Infrastructure metrics and broader application monitoring require separately selected tooling.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://langfuse.com/self-hosting/deployment/aws (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://langfuse.com/self-hosting/deployment/azure (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://langfuse.com/self-hosting/deployment/gcp (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://langfuse.com/self-hosting/deployment/railway (checked 2026-11-12). 

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://langfuse.com/self-hosting/deployment/render (checked 2026-11-12). 


### Cloud deployment evidence

- Langfuse customer cloud deployment on AWS (aws): https://langfuse.com/self-hosting/deployment/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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Langfuse customer cloud deployment on Azure (azure): https://langfuse.com/self-hosting/deployment/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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Langfuse customer cloud deployment on Google Cloud (gcp): https://langfuse.com/self-hosting/deployment/gcp
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Langfuse v3 community Railway deployment (railway): https://langfuse.com/self-hosting/deployment/railway
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Langfuse v4 community Render Blueprint (render): https://langfuse.com/self-hosting/deployment/render
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Docker Compose on a VM: https://langfuse.com/self-hosting/deployment/docker-compose

- Self-hosting architecture and provider dependencies: https://langfuse.com/self-hosting

- AWS account Terraform deployment: https://langfuse.com/self-hosting/deployment/aws

- Azure account Terraform deployment: https://langfuse.com/self-hosting/deployment/azure

- Google Cloud account Terraform deployment: https://langfuse.com/self-hosting/deployment/gcp

- Core and enterprise licensing: https://github.com/langfuse/langfuse/blob/main/LICENSE

- Licensing and edition terms: https://github.com/langfuse/langfuse/blob/main/ee/LICENSE

- Langfuse v3 community Railway deployment: https://langfuse.com/self-hosting/deployment/railway

- Langfuse v4 community Render Blueprint: https://langfuse.com/self-hosting/deployment/render

- Langfuse v4.82.0 release: https://github.com/langfuse/langfuse/releases/tag/v4.82.0

### Licensing sources

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

- https://github.com/langfuse/langfuse/blob/main/ee/LICENSE

### Infrastructure sources

- https://langfuse.com/self-hosting/deployment/docker-compose

- https://langfuse.com/self-hosting/deployment/aws

- https://langfuse.com/self-hosting/deployment/azure

- https://langfuse.com/self-hosting/deployment/gcp


### 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: Documented. The self-hosted guide documents OAuth/OIDC providers including Keycloak, Okta, Entra ID and a custom issuer. Configure account linking, email verification and access policy; SCIM and separately licensed enterprise features require their own review. Scope: Self-hosted OAuth/OIDC sign-in. Source: https://langfuse.com/self-hosting/security/authentication-and-sso (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: Langfuse v4.82.0 fixes a server-side request forgery path in GitHub Enterprise SSO. Upgrade to v4.82.0 or later and restrict outbound SSO connectivity. Scope: Upstream v4.82.0 release; the vendor did not publish an affected-version range in the reviewed note.. Source: https://github.com/langfuse/langfuse/releases/tag/v4.82.0 (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream Compose recipe defines application services and backing data services. Pin a compatible Langfuse release and review credentials, persistent storage and exposed ports. Scope: Upstream Compose recipe; supporting-service operations remain customer responsibilities. Source: https://github.com/langfuse/langfuse/blob/main/docker-compose.yml (reviewed 2026-11-14). Deployment artifact: https://github.com/langfuse/langfuse/blob/main/docker-compose.yml. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The vendor recommends at least 2 CPUs and 4 GB RAM for application containers and at least two Web instances for HA. Worker, ClickHouse, PostgreSQL, Redis and blob storage capacity are additional. Confirm per-container resources and retention/ingestion volume rather than treating this as the whole-stack footprint. Scope: Langfuse Web/Worker resource recommendation; backing services additional. Source: https://langfuse.com/self-hosting/deployment/infrastructure/containers (reviewed 2026-11-20).

- License pricing: Documented. Core code is MIT licensed, while ee directories, including application and worker enterprise paths, use a separate enterprise licence. Optional commercial features and support need separate terms; underlying databases, object storage and model services are additional. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/langfuse/langfuse/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Langfuse v4.82.0 was published November 17, 2026. It fixes an SSRF path in GitHub Enterprise SSO and moves audit logs to ClickHouse. Scope: Upstream Langfuse self-hosted release. Source: https://github.com/langfuse/langfuse/releases/tag/v4.82.0 (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- Langfuse GitHub Enterprise SSO SSRF fix (security-advisory): Langfuse v4.82.0 fixes a server-side request forgery path in GitHub Enterprise SSO. Scope: Upstream v4.82.0 release; the vendor did not publish an affected-version range in the reviewed note. Conditions: Requires the affected GitHub Enterprise SSO configuration and a reachable outbound target. Action: Upgrade to v4.82.0 or later and restrict outbound SSO connectivity. Source: https://github.com/langfuse/langfuse/releases/tag/v4.82.0; reviewed 2026-11-18.




## LiteLLM Proxy Self-Hosted

Self-hosted AI API gateway providing model routing, access controls and usage tracking.

- Listing: https://launchinyourcloud.com/directory/litellm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, railway, render
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT outside the enterprise directory; enterprise code and features have separate license terms.
- Licensing model: open-source
- Installation: Official container image, Docker Compose or Kubernetes deployment; production infrastructure examples are documented.
- Architecture: Customer-operated gateway with optional PostgreSQL persistence and configured model endpoints
- Operations: 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.
- Product website: https://www.litellm.ai/
- Source review: 2026-11-19; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

The gateway has an MIT-licensed base and separately licensed enterprise features. The enterprise documentation describes a license key enabling restricted capabilities in the gateway, beyond paid hosting or support alone.

The gateway runs as provisioned application containers or Kubernetes workloads; persistent key/spend storage can use PostgreSQL. Inference compute is a separate dependency rather than included in the gateway.


### Category fit

- ai-inference-gateways: Self-hosted model API gateway for routing, virtual keys, spend tracking and policy enforcement. It routes inference requests; it is not an inference engine for all supported models.

- ai-tools: Self-hosted AI API gateway providing model routing, access controls and usage tracking.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.litellm.ai/docs/proxy/deploy (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.litellm.ai/docs/proxy/deploy (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.litellm.ai/docs/proxy/deploy (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.litellm.ai/docs/proxy/deploy (checked 2026-11-12). 

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.litellm.ai/docs/proxy/deploy (checked 2026-11-12). 


### Cloud deployment evidence

- LiteLLM production deployment (aws, azure, gcp): https://docs.litellm.ai/docs/proxy/deploy
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- LiteLLM Railway and Render deployment options (railway, render): https://docs.litellm.ai/docs/proxy/deploy
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Production deployment: https://docs.litellm.ai/docs/proxy/deploy

- Gateway request flow and functionality: https://docs.litellm.ai/docs/simple_proxy

- MIT core and enterprise exception: https://github.com/BerriAI/litellm/blob/main/LICENSE

- Licensing and edition terms: https://docs.litellm.ai/docs/enterprise

- Supply-chain incident and Cosign verification guidance: https://docs.litellm.ai/blog/security-incident-oct-21-2026

- Canonical LiteLLM incident investigation: https://docs.litellm.ai/blog/security-incident-oct-21-2026-attack-chain

- LiteLLM v1.110.0 release: https://github.com/BerriAI/litellm/releases/tag/v1.110.0

- LiteLLM v1.108.11 LTS release: https://github.com/BerriAI/litellm/releases/tag/v1.108.11

- LiteLLM v1.110.1: https://github.com/BerriAI/litellm/releases/tag/v1.110.1

- LiteLLM v1.108.12 LTS: https://github.com/BerriAI/litellm/releases/tag/v1.108.12

### Licensing sources

- https://github.com/BerriAI/litellm/blob/main/LICENSE

- https://docs.litellm.ai/docs/enterprise

### Infrastructure sources

- https://docs.litellm.ai/docs/proxy/deploy


### 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. The Admin UI documents OIDC SSO. From 1.76.0, it is free for up to five users; larger deployments require an Enterprise licence. Configure issuer, callbacks, roles and database/master-key prerequisites. This is Admin UI identity, distinct from model API virtual keys. Scope: LiteLLM Admin UI OIDC; user-count/Enterprise entitlement applies. Source: https://docs.litellm.ai/docs/proxy/admin_ui_sso (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Release images and Helm charts use keyless Cosign from v1.111.0-dev.3; verify the documented workflow identity and issuer. Earlier releases use historical keys. The October 21 v1.107.0 compromise also affected mutable image tags; compare digests and exposure windows because affected images had valid historical signatures. Follow the incident remediation guidance for executed artifacts. Current advisory review: LiteLLM 1.108.11 LTS fixes Bedrock guarded_text handling and restricts os.environ team settings to proxy administrators. Upgrade the selected release line and recheck guardrail output and proxy-administrator permissions. Current review: v1.108.12 LTS fixes tool_policy allowing a /v1/messages request through when a blocked tool name exceeded 64 characters. Upgrade the maintained LTS line and retest tool-policy enforcement. Scope: LiteLLM 1.108 LTS /v1/messages tool_policy; standard and other maintained lines require their own release review. Source: https://github.com/BerriAI/litellm/releases/tag/v1.108.12 (reviewed 2026-11-19). Supporting source: Prior security-controls source — https://github.com/BerriAI/litellm/releases/tag/v1.108.11. Supporting source: Canonical incident investigation — https://docs.litellm.ai/blog/security-incident-oct-21-2026-attack-chain. Supporting source: Prior security-controls source — https://docs.litellm.ai/blog/security-incident-oct-21-2026.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official Helm guide documents Kubernetes installation and configurable database/secret settings. Select matching chart/image versions and review the separate scaling and production-readiness guidance. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.litellm.ai/docs/proxy/deploy/helm (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The current production guide starts load testing at 1 vCPU and 4 GiB per worker, preferably one worker per Kubernetes pod. Memory depends on queued requests, payloads, stream duration and logging. PostgreSQL, Redis for multiple workers/instances, HA and model inference are additional. Scope: Gateway per-worker load-test starting point; backing services and inference excluded. Source: https://docs.litellm.ai/docs/proxy/prod (reviewed 2026-11-20).

- License pricing: Documented. Core code outside litellm/enterprise is MIT licensed; the enterprise directory has separate terms. Enterprise features and support need separate entitlement and pricing. Upstream model APIs, infrastructure and operating labour are additional. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/BerriAI/litellm/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. LiteLLM v1.110.1 was published November 19, 2026. It refreshes the Wolfi base and changes the UI image to slim nginx, removing curl. The maintained v1.108.12 LTS line fixes a tool_policy bypass for blocked tool names longer than 64 characters. Scope: Upstream LiteLLM standard release; select and maintain either the standard or LTS line. Source: https://github.com/BerriAI/litellm/releases/tag/v1.110.1 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/BerriAI/litellm/releases/tag/v1.110.0. Supporting source: LiteLLM v1.108.11 LTS — https://github.com/BerriAI/litellm/releases/tag/v1.108.11. Supporting source: v1.108.12 LTS security fix — https://github.com/BerriAI/litellm/releases/tag/v1.108.12.




### Security and lifecycle reviews

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

- LiteLLM LTS proxy security fixes (security-advisory): LiteLLM 1.108.11 LTS fixes Bedrock guarded_text handling and restricts os.environ team settings to proxy administrators. Scope: LiteLLM 1.108 LTS line; standard-line deployments should use their corresponding maintained release. Conditions: Applicability depends on Bedrock guardrails and team-setting permissions. Action: Upgrade the selected release line and recheck guardrail output and proxy-administrator permissions. Source: https://github.com/BerriAI/litellm/releases/tag/v1.108.11; reviewed 2026-11-18.

- LiteLLM 1.108.12 LTS tool-policy fix (security-advisory): LiteLLM 1.108.12 LTS prevents blocked tool names longer than 64 characters from bypassing tool_policy on /v1/messages. Scope: LiteLLM 1.108 LTS /v1/messages tool-policy enforcement. Conditions: The request must use a blocked tool name longer than 64 characters. Action: Upgrade the maintained LTS line to 1.108.12 or later and retest tool-policy enforcement. Source: https://github.com/BerriAI/litellm/releases/tag/v1.108.12; reviewed 2026-11-19.




## Milvus

Vector database for similarity search and retrieval over embedding collections.

- Listing: https://launchinyourcloud.com/directory/milvus/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream Milvus.
- Licensing model: open-source
- Installation: Run the official standalone Docker or versioned Docker Compose deployment; distributed deployments have separate operational requirements.
- Architecture: Customer-operated vector database and persistent storage, with deployment-specific metadata and write-ahead-log services
- Operations: Customer manages persistent volumes, collections, indexes, access controls, capacity, backups and upgrades.
- Product website: https://milvus.io/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

Apache License 2.0 for upstream Milvus. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated vector database and persistent storage, with deployment-specific metadata and write-ahead-log services. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- databases-vector: Vector database for approximate nearest-neighbor retrieval over embeddings and associated metadata.

- ai-tools: Embedding storage and vector retrieval infrastructure for AI search and RAG applications.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://milvus.io/docs/eks.md (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://milvus.io/docs/azure.md (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://milvus.io/docs/gcp.md (checked 2026-11-12). 


### Cloud deployment evidence

- Milvus deployment on Amazon EKS (aws): https://milvus.io/docs/eks.md
  Official instructions provision Amazon EKS and deploy Milvus using Helm. Review persistent storage, object storage, networking and cluster sizing for the selected version.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Milvus deployment on Azure Kubernetes Service (azure): https://milvus.io/docs/azure.md
  Official instructions provision Azure Kubernetes Service and deploy Milvus using Helm. Review persistent storage, object storage, networking and cluster sizing for the selected version.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Milvus deployment on Google Kubernetes Engine (gcp): https://milvus.io/docs/gcp.md
  Official instructions provision Google Kubernetes Engine and deploy Milvus using Helm. Review persistent storage, object storage, networking and cluster sizing for the selected version.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Milvus documents governance under the LF AI & Data Foundation with Zilliz as a major contributor. Its public release stream records continuing October 2026 maintenance.

Reviewed 2026-11-10.

- Foundation and contributing community: https://github.com/milvus-io/milvus

- Current release maintenance: https://github.com/milvus-io/milvus/releases

### Sources

- Official installation and runtime: https://milvus.io/docs/install_standalone-docker.md

- Upstream project and capabilities: https://github.com/milvus-io/milvus

- Current upstream license: https://github.com/milvus-io/milvus/blob/master/LICENSE

### Licensing sources

- https://github.com/milvus-io/milvus/blob/master/LICENSE

### Infrastructure sources

- https://milvus.io/docs/install_standalone-docker.md


### 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. The current core authentication guide uses username/password credentials and SDK token fields with explicitly enabled authorization. It does not establish native SAML/OIDC federation or automatic IdP/group mapping. Hosted Zilliz console SSO is a different deployment; confirm an upstream integration before relying on it. Scope: Self-hosted Milvus core user authentication; federation unresolved. Source: https://milvus.io/docs/authenticate.md (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official standalone Docker guide links a script fetched from master. Its image selection moves and its upgrade command does not validate arbitrary version transitions; inspect the script and use matching versioned Compose when required. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://milvus.io/docs/install_standalone-docker.md (reviewed 2026-11-14). Deployment artifact: https://raw.githubusercontent.com/milvus-io/milvus/master/scripts/standalone_embed.sh. Artifact reference: master script (moving; inspect its selected image).

- Minimum footprint / sizing: Documented. The standalone requirements specify 8 GB RAM, recommend 16 GB and recommend at least 4 CPU cores with a supported SIMD instruction set. Dataset/index size and storage performance govern actual resources; distributed requirements differ. Scope: Milvus 3.0.x standalone requirements as reviewed. Source: https://milvus.io/docs/prerequisite-docker.md (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. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/milvus-io/milvus/master/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

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







## MLflow Tracking Server Self-Hosted

Self-hosted experiment tracking and LLM/agent observability with customer-controlled metadata and artifacts.

- Listing: https://launchinyourcloud.com/directory/mlflow/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache 2.0 for upstream MLflow; connected model providers and managed distributions have separate terms.
- Licensing model: open-source
- Installation: Python MLflow server command, official Docker Compose bundle or Kubernetes Helm deployment.
- Architecture: Customer-operated tracking/API server with configurable metadata database and artifact storage
- Operations: Customer operates server access, metadata and artifact stores, retention, backups, scaling and version upgrades.
- Product website: https://mlflow.org/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

The upstream self-hosted tracking server is Apache-2.0 licensed. This classification does not extend to separate managed MLflow distributions, connected model providers or their commercial services.

The tracking server runs as a Python service or container with metadata/artifact stores. A local SQLite example is not a production architecture; separately plan persistent database, storage and application-runtime infrastructure.


### Category fit

- ai-observability: Experiment tracking and LLM/agent tracing server. This entry describes customer-hosted tracking/observability services, not every model runtime, managed MLflow product or inference backend.

- ai-tools: Self-hosted experiment tracking and LLM/agent observability with customer-controlled metadata and artifacts.

- observability: Application/model traces and experiment visibility for AI workloads. Infrastructure metrics and broader application monitoring require separately selected tooling.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://mlflow.org/docs/latest/self-hosting/deploy-to-cloud/aws/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://mlflow.org/docs/latest/self-hosting/deploy-to-cloud/azure/ (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://mlflow.org/docs/latest/self-hosting/deploy-to-cloud/gcp/ (checked 2026-11-12). 


### Cloud deployment evidence

- Self-hosted MLflow deployment on AWS (aws): https://mlflow.org/docs/latest/self-hosting/deploy-to-cloud/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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Self-hosted MLflow deployment on Azure (azure): https://mlflow.org/docs/latest/self-hosting/deploy-to-cloud/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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Self-hosted MLflow deployment on Google Cloud (gcp): https://mlflow.org/docs/latest/self-hosting/deploy-to-cloud/gcp/
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Self-hosting server and deployment methods: https://mlflow.org/docs/latest/self-hosting/

- LLM/agent tracing and captured data: https://mlflow.org/docs/latest/genai/tracing/

- Apache 2.0 license: https://github.com/mlflow/mlflow/blob/master/LICENSE.txt

### Licensing sources

- https://github.com/mlflow/mlflow/blob/master/LICENSE.txt

### Infrastructure sources

- https://mlflow.org/docs/latest/self-hosting/


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The official guide documents the community-maintained mlflow-oidc-auth plugin and an SSO reverse-proxy pattern. This provides UI/API OIDC integration, but plugin maintenance, MLflow-version compatibility and client token behavior require separate review; it is not a claim of vendor-operated identity support. Scope: Officially documented community-plugin/proxy integration. Source: https://mlflow.org/docs/latest/self-hosting/security/sso/ (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The self-hosting guide links an upstream Compose bundle with MLflow, PostgreSQL and object storage, plus an official Helm option. Configure production credentials and persistence rather than retaining development defaults. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://mlflow.org/docs/latest/self-hosting/ (reviewed 2026-11-14). Deployment artifact: https://github.com/mlflow/mlflow/tree/master/docker-compose. Artifact reference: master Compose bundle (moving).

- Minimum footprint / sizing: Sources checked — unresolved. The self-hosted guide documents the UI/API tracking server, metadata backend and artifact-store configuration, but not a universal production CPU/RAM minimum. Size runs/traces, request concurrency, database, artifact storage and redundancy; starting the default local SQLite server does not establish production or HA capacity. Scope: Self-hosted tracking-server topology; numeric production sizing unresolved. Source: https://mlflow.org/docs/latest/self-hosting/architecture/tracking-server/ (reviewed 2026-11-20).

- 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. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/mlflow/mlflow/master/LICENSE.txt (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

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







## n8n Self-Hosted

Automate integrations and business processes with a customer-hosted workflow editor and runtime.

- Listing: https://launchinyourcloud.com/directory/n8n/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean, heroku, hetzner
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Sustainable Use License for covered code; separate commercial Enterprise license for enterprise components
- Licensing model: source-available
- Installation: Docker Compose with persistent data; database and worker topology selected for workload
- Architecture: Customer-operated workflow runtime, credentials store and persistent execution data
- Operations: Customer manages servers/containers, secrets, database, backup/restore, scaling and upgrades.
- Product website: https://n8n.io/
- Source review: 2026-11-19; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

The core is under the Sustainable Use License with use restrictions, not an OSI open-source license. Enterprise-marked code requires a separate commercial Enterprise license. A free self-hosted option does not change the core license model.

Reviewed topology runs long-lived containers and persistent workflow/credential storage. Event triggers do not make the self-hosted control/runtime stack function-based serverless.


### Category fit

- workflow-automation: Visual integration/workflow automation with custom code and connectors; connected systems and AI providers may receive workflow data.

- ai-tools: Orchestrates AI providers, agents, tools and memory as workflows. Model inference and external service dependencies are configured separately.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-aws (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-azure (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-google-cloud-run (checked 2026-11-12). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-digital-ocean (checked 2026-11-12). 

- heroku: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-heroku (checked 2026-11-12). 

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-hetzner (checked 2026-11-12). 


### Cloud deployment evidence

- n8n deployment on AWS (aws): https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-aws
  Project instructions deploy n8n and PostgreSQL on customer-operated EKS. Review persistence, ingress and production scaling requirements.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- n8n deployment on Azure (azure): https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-azure
  Project instructions deploy n8n with PostgreSQL on Azure Kubernetes Service in the customer subscription.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- n8n deployment on Google Cloud Run (gcp): https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- n8n self-hosted deployment on DigitalOcean (digitalocean): https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-digital-ocean
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- n8n self-hosted deployment on Heroku (heroku): https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- n8n self-hosted deployment on Hetzner (hetzner): https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Current self-hosted Docker Compose guide: https://docs.n8n.io/deploy/host-n8n/install-options/install-using-docker-compose

- Official license boundaries: https://github.com/n8n-io/n8n/blob/master/LICENSE.md

- Workflow automation project: https://github.com/n8n-io/n8n

- AI workflow components and integrations: https://docs.n8n.io/build/integrate-ai.md

- n8n self-hosted deployment on DigitalOcean: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-digital-ocean

- n8n self-hosted deployment on Heroku: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-heroku

- n8n self-hosted deployment on Hetzner: https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-hetzner

- n8n@2.48.6 release: https://github.com/n8n-io/n8n/releases/tag/n8n%402.48.6

- n8n@1.123.99 release: https://github.com/n8n-io/n8n/releases/tag/n8n%401.123.99

- Patched V8 runtime integration: https://github.com/n8n-io/n8n/pull/43703

### Licensing sources

- https://github.com/n8n-io/n8n/blob/master/LICENSE.md

### Infrastructure sources

- https://docs.n8n.io/deploy/host-n8n/install-options/install-using-docker-compose


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. SAML or OIDC SSO is documented for self-hosted Business and Enterprise. Instance-owner or administrator privileges are required to configure it. Scope: Self-hosted Business and Enterprise; not the unlicensed Community edition. Source: https://docs.n8n.io/deploy/host-n8n/configure-n8n/security/configure-sso.md (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor documents Linux Compose installation and links n8n-hosting configurations for different architectures. Configure persistent data, database, encryption key, domain and TLS; choose the production topology rather than treating the minimal single-server recipe as HA. Scope: Official self-hosted Compose deployment. Source: https://docs.n8n.io/hosting/installation/server-setups/docker-compose/ (reviewed 2026-11-20). Deployment artifact: https://github.com/n8n-io/n8n-hosting. Artifact reference: Select and pin a compatible versioned application image.

- Minimum footprint / sizing: Sources checked — unresolved. The self-hosted memory guide ties RAM usage to execution concurrency, JSON/binary payload size and workflow behavior. It does not establish one safe server minimum. Size main processes, workers/task runners, PostgreSQL, queue-mode Redis, binary storage and HA after measuring representative workflows. Scope: Self-hosted workflow-dependent sizing; complete production footprint unresolved. Source: https://docs.n8n.io/hosting/scaling/memory-errors/ (reviewed 2026-11-20). Supporting source: Production topology and dependencies — https://docs.n8n.io/deploy/host-n8n/install-options/production-requirements.md.

- License pricing: Documented. The Sustainable Use License permits internal business or non-commercial/personal use under its conditions. Enterprise files are separately licensed, and other branches have specific restrictions. Commercial redistribution or embedded use must be checked against vendor terms; self-hosting does not grant every Enterprise feature. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/n8n-io/n8n/master/LICENSE.md (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. n8n n8n@2.48.6 was published November 19, 2026. Official 2.x images use a patched Node 26.13.0 runtime carrying a V8 process-abort fix. Maintained 1.x users should use n8n@1.123.99 or later, which moves to Node 24.22.3. Scope: Upstream n8n 2.x release; the 1.x maintenance line has a separate fixed build. Source: https://github.com/n8n-io/n8n/releases/tag/n8n%402.48.6 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/n8n-io/n8n/releases/tag/n8n%402.47.7. Supporting source: Maintained 1.x runtime fix — https://github.com/n8n-io/n8n/releases/tag/n8n%401.123.99. Supporting source: Patched V8 runtime integration — https://github.com/n8n-io/n8n/pull/43703.







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







## Onyx Self-Hosted

Self-hosted enterprise search and AI assistant platform with connectors and retrieval infrastructure.

- Listing: https://launchinyourcloud.com/directory/onyx/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT Community Edition; Business and Enterprise features use separate commercial terms.
- Licensing model: open-source
- Installation: Docker Compose on a VM or official Kubernetes and Terraform deployment
- Architecture: Customer-operated web/API services, background workers, PostgreSQL, Redis, search and object storage
- Operations: Customer manages application services, databases, search, object storage, connectors, model credentials, backups, scaling and upgrades.
- Product website: https://www.onyx.app/
- Source review: 2026-11-14; cloud review: 2026-11-14; licensing review: 2026-11-14; infrastructure review: 2026-11-14

### Scope and qualifications

This entry covers 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 Community Edition is MIT-licensed. Business and Enterprise features, images and support have separate commercial terms.

Onyx runs web services, workers and persistent database, cache, search and object-storage dependencies on VMs or Kubernetes.


### Category fit

- ai-applications-rag: Provides enterprise search, connectors and retrieval-augmented AI assistants over customer-selected knowledge sources.

- ai-tools: Provides self-hosted indexing, retrieval, model integration and agent services for building internal AI experiences.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.onyx.app/deployment/cloud/aws/ec2 (checked 2026-11-14). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.onyx.app/deployment/cloud/azure (checked 2026-11-14). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.onyx.app/deployment/cloud/gcp (checked 2026-11-14). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.onyx.app/deployment/cloud/digital_ocean (checked 2026-11-14). 


### Cloud deployment evidence

- Onyx on AWS (aws): https://docs.onyx.app/deployment/cloud/aws/ec2
  Onyx documents self-hosting on a customer EC2 instance and links a production EKS architecture using AWS managed dependencies.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- Onyx on Azure (azure): https://docs.onyx.app/deployment/cloud/azure
  Onyx documents self-hosting on an Azure VM and an AKS Terraform path using customer Azure managed services.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- Onyx on Google Cloud (gcp): https://docs.onyx.app/deployment/cloud/gcp
  Onyx documents Compute Engine and production GKE deployment paths in the customer's Google Cloud project.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- Onyx on DigitalOcean (digitalocean): https://docs.onyx.app/deployment/cloud/digital_ocean
  Onyx documents installing its self-hosted stack on a customer DigitalOcean Droplet.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.


### Community and maintenance

Onyx has sustained, substantive code participation from multiple contributors. Release 5.1.2 on November 12, 2026 records continuing maintenance, including permission-handling and retrieval fixes. Contributor and release histories establish maintained project participation; they do not establish that paid Business or Enterprise features are included in the MIT Community Edition.

Reviewed 2026-11-14.

- Reviewed maintenance release v5.1.2: https://github.com/onyx-dot-app/onyx/releases/tag/v5.1.2

- Upstream contributor history: https://github.com/onyx-dot-app/onyx/graphs/contributors

### Sources

- AWS EC2 deployment: https://docs.onyx.app/deployment/cloud/aws/ec2

- Azure deployment: https://docs.onyx.app/deployment/cloud/azure

- Google Cloud deployment: https://docs.onyx.app/deployment/cloud/gcp

- DigitalOcean deployment: https://docs.onyx.app/deployment/cloud/digital_ocean

- Community license: https://github.com/onyx-dot-app/onyx/blob/main/LICENSE

- Reviewed maintenance release v5.1.2: https://github.com/onyx-dot-app/onyx/releases/tag/v5.1.2

- Upstream contributor history: https://github.com/onyx-dot-app/onyx/graphs/contributors

- Current Business and Enterprise edition boundaries: https://docs.onyx.app/deployment/enterprise_edition.md

### Licensing sources

- https://github.com/onyx-dot-app/onyx/blob/main/LICENSE

- https://docs.onyx.app/deployment/enterprise_edition.md

### Infrastructure sources

- https://docs.onyx.app/deployment/cloud/aws/ec2

- https://docs.onyx.app/deployment/cloud/gcp


### 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: Documented. The upstream Enterprise section advertises Google OAuth, OIDC and SAML sign-in. The README does not establish every Community-versus-Enterprise protocol entitlement; confirm the selected self-hosted edition and identity configuration. Scope: Enterprise feature statement; exact protocol entitlement not fully established. Source: https://github.com/onyx-dot-app/onyx (reviewed 2026-11-14).

- SCIM provisioning: Edition-dependent. The upstream Enterprise section describes group synchronization and SCIM user provisioning. Confirm the licensed self-hosted implementation and supported lifecycle operations rather than assuming Community includes them. Scope: Onyx Enterprise feature statement. Source: https://github.com/onyx-dot-app/onyx (reviewed 2026-11-14).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official Docker guide uses the upstream deployment/docker_compose directory and an environment template. The default image tag moves; replace example storage credentials and configure the selected inference/storage services. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.onyx.app/deployment/local/docker (reviewed 2026-11-14). Deployment artifact: https://github.com/onyx-dot-app/onyx/tree/main/deployment/docker_compose. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The vendor gives Lite minimum 2 vCPUs/2 GB RAM/10 GB disk and Standard minimum 4 vCPUs/10 GB RAM/32 GB plus roughly 2.5 times indexed data. Its Standard per-container example totals about 12 CPUs/24 GB. These describe different profiles; connector/index volume, model services and HA require additional sizing. Scope: Vendor Lite/Standard profiles; per-container and single-instance recommendations differ. Source: https://docs.onyx.app/deployment/getting_started/resourcing.md (reviewed 2026-11-20).

- License pricing: Documented. Core code is MIT licensed; ee directories are under the Onyx Enterprise License. Enterprise features need their own entitlement and quote. The MIT core licence does not establish all-edition feature access, support or model/hosting prices. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/onyx-dot-app/onyx/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

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







## Open WebUI Self-Hosted

Self-hosted AI chat and knowledge interface for local model servers and cloud APIs.

- Listing: https://launchinyourcloud.com/directory/open-webui/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open WebUI license based on BSD-style terms with additional branding restrictions and defined exceptions; enterprise terms may be required for rebranding.
- Licensing model: source-available
- Installation: Official Docker image, Python installation or Kubernetes deployment.
- Architecture: Customer-operated web application and conversation storage connected to model providers
- Operations: Customer runs application storage, authentication, provider configuration, updates and backups.
- Product website: https://openwebui.com/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

The current Open WebUI license adds branding restrictions to BSD-style terms, with small-deployment and permission/license exceptions. Classified here as source-available rather than treating the current version as unmodified BSD-3-Clause.

The application runs as a Docker/Python server or Kubernetes workload with persistent conversation/user storage. Local inference is a separate server or accelerator workload, depending on the chosen model.


### Category fit

- ai-applications-rag: Deployable team chat and model-access interface with retrieval features. It is an interface and application layer, not an included license or runtime for every connected model.

- ai-tools: Self-hosted AI chat and knowledge interface for local model servers and cloud APIs.

### Deployment boundaries


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

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.openwebui.com/deployment/azure-container-apps/ (checked 2026-11-12). 

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


### Cloud deployment evidence

- Open WebUI deployment on AWS ECS / Fargate (aws): https://docs.openwebui.com/deployment/aws-ecs/
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Open WebUI deployment on Azure Container Apps (azure): https://docs.openwebui.com/deployment/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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Open WebUI deployment on Google Cloud Run (gcp): https://docs.openwebui.com/deployment/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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Installation options: https://docs.openwebui.com/getting-started/quick-start/

- Local and cloud model connections: https://docs.openwebui.com/getting-started/quick-start/connect-a-provider/

- Current license and branding conditions: https://docs.openwebui.com/license/

- Licensing and edition terms: https://github.com/open-webui/open-webui/blob/main/LICENSE

- Open WebUI v0.13.4 release: https://github.com/open-webui/open-webui/releases/tag/v0.13.4

### Licensing sources

- https://github.com/open-webui/open-webui/blob/main/LICENSE

- https://docs.openwebui.com/license/

### Infrastructure sources

- https://docs.openwebui.com/getting-started/quick-start/


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Upstream documents OAuth/OIDC and trusted-header authentication. Only one generic OIDC provider is configured through OPENID_PROVIDER_URL at a time; trusted-header use requires an isolated trusted proxy. Scope: Upstream authentication configuration; review provider and session settings. Source: https://docs.openwebui.com/features/authentication-access/auth/sso/ (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream Compose example includes Open WebUI and Ollama with persistent volumes. Its defaults use moving image references and an empty application secret; configure production credentials and pin versions. Scope: Upstream example; model resources and service exposure require separate review. Source: https://github.com/open-webui/open-webui/blob/main/docker-compose.yaml (reviewed 2026-11-14). Deployment artifact: https://github.com/open-webui/open-webui/blob/main/docker-compose.yaml. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The performance guide shows a container example reserving 2 CPUs/4 GB RAM with limits of 4 CPUs/8 GB. Multi-user deployments need PostgreSQL; scaled replicas also require shared services. Local inference, embeddings, extraction, vector storage and HA are additional. This is an example allocation, not a validated 100-user or 1-TB minimum. Scope: Application-container example; full stack and workload sizing excluded. Source: https://docs.openwebui.com/troubleshooting/performance/ (reviewed 2026-11-20). Supporting source: Shared infrastructure for scaled deployments — https://docs.openwebui.com/enterprise/deployment/.

- License pricing: Documented. Current Open WebUI has custom terms restricting branding changes, with exceptions including deployments of at most 50 end users in a rolling 30-day period, written permission or an enterprise licence. A 100-user deployment cannot assume the small-deployment branding exception. Model and infrastructure costs are separate. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/open-webui/open-webui/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Open WebUI v0.13.4 was published November 17, 2026. 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. The release also replaces Direct Connections and Integrations with Tether and migrates image settings. Scope: Upstream Open WebUI self-hosted release; the Terminals version and migration requirements apply only to deployments using Terminals server connections. Source: https://github.com/open-webui/open-webui/releases/tag/v0.13.4 (reviewed 2026-11-18).







## Qdrant Self-Hosted

Self-hosted vector database for semantic retrieval and AI application data.

- Listing: https://launchinyourcloud.com/directory/qdrant/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache 2.0 for the upstream database; managed cloud offerings and support have separate commercial terms.
- Licensing model: open-source
- Installation: Official Docker image for local/server deployment; production storage, access controls and scaling require configuration.
- Architecture: Customer-operated vector-search server and persistent collection storage
- Operations: Customer manages persistence, backups, access controls, upgrades and any distributed-cluster operations.
- Product website: https://qdrant.tech/
- Source review: 2026-11-14; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

The listed upstream self-hosted database is Apache-2.0 licensed. Separate managed hosting or support does not change this database classification; this entry does not classify a proprietary managed-cloud control plane.

The database runs as a persistent server/container process with collection storage; production capacity, replicas and backup storage must be planned. Embedding-model compute is separate.


### Category fit

- databases-vector: Vector database for similarity and hybrid retrieval in AI applications. Model inference and embedding creation are separate from the core database deployment.

- ai-tools: Self-hosted vector database for semantic retrieval and AI application data.

### Deployment boundaries


- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cloud.google.com/kubernetes-engine/docs/tutorials/deploy-qdrant (checked 2026-11-12). 


### Cloud deployment evidence

- Self-operated Qdrant cluster on Google Kubernetes Engine (gcp): https://docs.cloud.google.com/kubernetes-engine/docs/tutorials/deploy-qdrant
  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.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Local/server Docker quickstart: https://qdrant.tech/documentation/quickstart/

- Embedding options, including local FastEmbed: https://qdrant.tech/documentation/embeddings/

- Apache 2.0 license: https://github.com/qdrant/qdrant/blob/master/LICENSE

- Qdrant 1.20.1 security and maintenance release: https://github.com/qdrant/qdrant/releases/tag/v1.20.1

### Licensing sources

- https://github.com/qdrant/qdrant/blob/master/LICENSE

### Infrastructure sources

- https://qdrant.tech/documentation/quickstart/


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The self-hosted core security guide documents API keys, including scoped access keys, TLS and audit controls. It does not establish a native SAML/OIDC login flow or a reviewed external-IdP integration for this edition. Qdrant Cloud console identity is a separate service and is not transferred to the core database. Scope: Self-hosted core authentication; federated user sign-on unresolved. Source: https://qdrant.tech/documentation/security/ (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The local quickstart identifies the official Qdrant Docker server and persistent storage. A local evaluation command is not a hardened production installation; configure network access, authentication and durable storage. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://qdrant.tech/documentation/quickstart/ (reviewed 2026-11-14). Deployment artifact: https://hub.docker.com/r/qdrant/qdrant. Artifact reference: select a released Qdrant image tag.

- Minimum footprint / sizing: Sources checked — unresolved. The capacity guide models vectors, dimensions/datatype, HNSW, payload indexes, memory tiers and replication, with headroom and representative-data testing. It does not establish a single minimum from a user count or total source-data size. Determine vector counts/dimensions, retention, replicas and query/ingestion rates, then use the sizing calculator and benchmark. Scope: Vector/workload-specific sizing methodology; numeric minimum for the requested deployment unresolved. Source: https://qdrant.tech/documentation/capacity-planning/ (reviewed 2026-11-20).

- 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. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/qdrant/qdrant/master/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

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







## RAGFlow

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

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

### Scope and qualifications

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

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

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


### Category fit

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

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

### Deployment boundaries


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

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

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

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

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


### Cloud deployment evidence

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

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

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

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

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

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


### Community and maintenance

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

Reviewed 2026-11-10.

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

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

### Sources

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

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

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

### Licensing sources

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

### Infrastructure sources

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


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

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

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

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

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

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

- Operating cost estimate: Not researched.

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







## Red Hat OpenShift AI Self-Managed

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

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

### Scope and qualifications

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

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

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


### Category fit

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

### Deployment boundaries


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

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

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

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

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


### Cloud deployment evidence

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


### Sources

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

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

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

### Licensing sources

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

### Infrastructure sources

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


### Buyer diligence


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

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


- Marketplace delivery: Sources checked — unresolved. OperatorHub installation and required subscriptions do not establish a specific cloud Marketplace offer for the Self-Managed AI entitlement. Managed add-ons and generic OpenShift offers are separate. Scope: Reviewed public evidence for Red Hat OpenShift AI Self-Managed; unresolved within this edition/deployment. Source: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install (reviewed 2026-11-17).

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

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

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

- Compliance attestations: Sources checked — unresolved. The reviewed Red Hat OpenShift AI Self-Managed material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage. Scope: Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited. Source: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install (reviewed 2026-11-17).

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

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

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

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

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

- Operating cost estimate: Sources checked — unresolved. Select OpenShift HA topology, enabled AI components, model size, GPU needs, concurrency, object storage and both subscription entitlements. Operator installation minima do not size inference/training. A complete monthly operating estimate is not established. Scope: Requested planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA, average usage; missing workload metrics and commercial terms are explicit. Source: https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install (reviewed 2026-11-17).

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




### Security and lifecycle reviews

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

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




## SAS Viya Platform

Commercial analytics and AI platform deployed into a customer-operated managed Kubernetes cluster.

- Listing: https://launchinyourcloud.com/directory/sas-viya-platform/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial SAS Viya licensing; deployment assets and a JWT license are delivered for the customer's software order.
- Licensing model: commercial-only
- Installation: Provision EKS, AKS or GKE with SAS Terraform projects, then deploy Kubernetes manifests generated through Kustomize and SAS automation
- Architecture: Customer-operated EKS, AKS or GKE cluster running SAS Viya containers, CAS, PostgreSQL integrations and persistent storage.
- Operations: Customer manages Kubernetes, networking, ingress, storage, PostgreSQL, identity, sizing, backups, platform updates and licensed deployment assets.
- Product website: https://www.sas.com/en_us/software/viya.html
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

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 requires a commercial order, licensed deployment assets and a JWT license. Apache licenses on the public infrastructure repositories apply to tooling, not the Viya product distribution.

SAS Viya runs persistent container workloads on managed Kubernetes with CAS compute, shared storage and PostgreSQL. Terraform projects provision customer infrastructure but do not complete the application deployment.


### Category fit

- data-analytics: Enterprise data preparation, analytics, reporting and decisioning delivered by the customer-operated Viya platform.

- ai-tools: Model development, machine learning, model management and AI operationalization; exact products depend on the licensed order.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/sassoftware/viya4-iac-aws (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/sassoftware/viya4-iac-azure (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/sassoftware/viya4-iac-gcp (checked 2026-11-17). 


### Cloud deployment evidence

- SAS Viya infrastructure on AWS (aws): https://github.com/sassoftware/viya4-iac-aws
  Official SAS Terraform provisions customer AWS resources including EKS, storage and optional RDS, after which the customer deploys licensed Viya assets.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- SAS Viya infrastructure on Azure (azure): https://github.com/sassoftware/viya4-iac-azure
  Official SAS Terraform provisions customer Azure resources including AKS, storage and optional PostgreSQL, after which the customer deploys licensed Viya assets.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- SAS Viya infrastructure on Google Cloud (gcp): https://github.com/sassoftware/viya4-iac-gcp
  Official SAS Terraform provisions customer Google Cloud resources including GKE, storage and optional Cloud SQL, after which the customer deploys licensed Viya assets.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Introduction to SAS Viya Platform: https://documentation.sas.com/api/docsets/calintro/v_001/content/calintro.pdf?locale=en

- SAS Viya Platform system requirements: https://documentation.sas.com/api/collections/itopscdc/v_069/docsets/itopssr/content/itopssr.pdf?locale=en

- AWS infrastructure as code: https://github.com/sassoftware/viya4-iac-aws

- Azure infrastructure as code: https://github.com/sassoftware/viya4-iac-azure

- Google Cloud infrastructure as code: https://github.com/sassoftware/viya4-iac-gcp

- SAS Viya deployment automation: https://github.com/sassoftware/viya4-deployment

- How to buy SAS Viya: https://www.sas.com/en_us/software/viya/how-to-buy-sas-viya.html

- SAS compromised eMudhra certificates bulletin: https://support.sas.com/en/security-bulletins/compromised-emudhra-certificates-vulnerabilities.html

- SAS Brotli CVE-2026-111497 bulletin: https://support.sas.com/en/security-bulletins/google-brotli-decoder-vulnerability-cve-2026-111497.html

### Licensing sources

- https://documentation.sas.com/api/docsets/calintro/v_001/content/calintro.pdf?locale=en

- https://www.sas.com/en_us/software/viya/how-to-buy-sas-viya.html

### Infrastructure sources

- https://documentation.sas.com/api/collections/itopscdc/v_069/docsets/itopssr/content/itopssr.pdf?locale=en

- https://github.com/sassoftware/viya4-deployment


### Buyer diligence


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

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


- Marketplace delivery: Edition-dependent. SAS documents buying Viya through cloud marketplaces and specifically links Microsoft Marketplace. Select the matching packaged offering and delivery/entitlement terms; this is not proof every Marketplace offer matches a Terraform-based licensed deployment. Scope: Viya software procurement; offering selection required. Source: https://www.sas.com/en_us/software/viya/how-to-buy-sas-viya.html (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. The purchasing page links packaged Viya offerings, but does not establish qualifying charges for this licensed platform deployment under the buyer cloud agreement. Workbench is separate. Scope: Reviewed public evidence for SAS Viya Platform; unresolved within this edition/deployment. Source: https://www.sas.com/en_us/software/viya/how-to-buy-sas-viya.html (reviewed 2026-11-17).

- Single sign-on: Documented. Viya documents SAML and OIDC web SSO. Configure a compatible identity provider and matching certificates; this is distinct from user provisioning. Scope: Reviewed SAS Viya platform requirements; web authentication; reviewed 2025.10 requirements. Source: https://documentation.sas.com/api/collections/itopscdc/v_069/docsets/itopssr/content/itopssr.pdf?locale=en (reviewed 2026-11-17).

- SCIM provisioning: Documented. Viya supports SCIM 2.0, tested with Okta and Entra ID. Disable LDAP when using SCIM; SAML/OIDC, HTTPS, a public-CA certificate and inbound IdP access are required. Google Identity provisioning is not supported in this reviewed configuration. Scope: Viya SCIM requirements; selected identity configuration; reviewed 2025.10 requirements. Source: https://documentation.sas.com/api/collections/itopscdc/v_069/docsets/itopssr/content/itopssr.pdf?locale=en (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed SAS Viya Platform material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage. Scope: Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited. Source: https://documentation.sas.com/api/collections/itopscdc/v_069/docsets/itopssr/content/itopssr.pdf?locale=en (reviewed 2026-11-17).

- Security controls: Documented. The requirements separate service/user accounts, elevated deployment permissions, TLS/identity and database dependencies. Apply the selected platform security configuration; a reference to a security standard is not an independent deployment attestation. Current advisory review: SAS bulletins address compromised eMudhra certificates and critical Brotli CVE-2026-111497 in specified Viya components and branches. Apply the exact fixed maintenance level for each affected component and review certificate trust. Scope: Viya installation security prerequisites; reviewed 2025.10 requirements Affected and fixed maintenance levels vary by Viya component and branch; consult both vendor matrices.. Source: https://support.sas.com/en/security-bulletins/compromised-emudhra-certificates-vulnerabilities.html (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://documentation.sas.com/api/collections/itopscdc/v_069/docsets/itopssr/content/itopssr.pdf?locale=en. Supporting source: Brotli CVE-2026-111497 bulletin — https://support.sas.com/en/security-bulletins/google-brotli-decoder-vulnerability-cve-2026-111497.html.

- Air-gapped operation: Edition-dependent. The reviewed 2025.10 guide documents air-gapped deployment using SAS Mirror Manager: download entitled content outside the isolated network, transfer it and populate an internal registry without contacting the SAS entitlement/container services. Match the order assets, cadence and component dependencies. Scope: SAS Viya 2025.10 air-gapped deployment procedure; confirm compatibility with the purchased cadence assets. Source: https://documentation.sas.com/api/collections/itopscdc/v_069/docsets/dplyml0phy0dkr/content/dplyml0phy0dkr.pdf?locale=en (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. SAS publishes Terraform for AWS infrastructure and separate deployment automation for the licensed Viya manifests. Pin a compatible tooling revision and SAS order assets; the Apache-licensed automation does not license the application. Scope: SAS-owned AWS IaC repository. Source: https://github.com/sassoftware/viya4-iac-aws (reviewed 2026-11-17). Deployment artifact: https://github.com/sassoftware/viya4-iac-aws. Artifact reference: default branch (moving; select a compatible release). Supporting source: Viya deployment automation — https://github.com/sassoftware/viya4-deployment.

- Minimum footprint / sizing: Documented. Sizing depends on licensed workloads, CAS/compute roles, Kubernetes node pools, storage bandwidth and PostgreSQL. The requirements include provider-specific sizing; 100 users and 1 TB alone do not determine a supported HA cluster. Scope: SAS Viya platform and workload-specific sizing; reviewed 2025.10 requirements. Source: https://documentation.sas.com/api/collections/itopscdc/v_069/docsets/itopssr/content/itopssr.pdf?locale=en (reviewed 2026-11-17).

- License pricing: Documented. SAS Viya requires a commercial order, licensed deployment assets and a JWT license. Apache licenses on the public infrastructure repositories apply to tooling, not the Viya product distribution. Scope: SAS Viya Platform: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://documentation.sas.com/api/docsets/calintro/v_001/content/calintro.pdf?locale=en (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Choose the licensed Viya modules/cadence, CAS/compute pools, data-in-memory requirements, HA services and storage throughput. The order-specific topology and commercial licence price are not public. A complete monthly operating estimate is not established. Scope: Requested planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA, average usage; missing workload metrics and commercial terms are explicit. Source: https://documentation.sas.com/api/collections/itopscdc/v_069/docsets/itopssr/content/itopssr.pdf?locale=en (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. SAS publishes monthly Stable releases and Long-Term Support releases about every six months, aggregating prior Stable changes. Obtain deployment assets for the purchased order and cadence; automation repository tags are not Viya application releases. Scope: Viya platform cadence policy; exact order/version assets remain separate. Source: https://documentation.sas.com/api/collections/itopscdc/v_066/docsets/itopscon/content/itopscon.pdf?locale=en (reviewed 2026-11-17).




### Security and lifecycle reviews

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

- SAS Viya November 2026 certificate and Brotli bulletins (security-advisory): SAS bulletins address compromised eMudhra certificates and critical Brotli CVE-2026-111497 in specified Viya components and branches. Scope: Affected and fixed maintenance levels vary by Viya component and branch; consult both vendor matrices. Conditions: Bundled trust stores, certificates, and Brotli-using components determine exposure. Action: Apply the exact fixed maintenance level for each affected component and review certificate trust. Source: https://support.sas.com/en/security-bulletins/compromised-emudhra-certificates-vulnerabilities.html; reviewed 2026-11-18. Supporting source: Brotli CVE-2026-111497 bulletin — https://support.sas.com/en/security-bulletins/google-brotli-decoder-vulnerability-cve-2026-111497.html.




## SGLang

Model-serving framework for running supported language and multimodal models on customer-controlled compute.

- Listing: https://launchinyourcloud.com/directory/sglang/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream SGLang. Model weights and hardware/runtime dependencies have their own licenses.
- Licensing model: open-source
- Installation: Install the package or use official containers; the reviewed primary installation path targets Linux with supported NVIDIA GPUs and compatible drivers.
- Architecture: Customer-operated inference server and model weights on configured accelerator hosts
- Operations: Customer manages accelerator capacity, model artifacts, runtime compatibility, endpoint access, including isolation of debug and dumper routes, monitoring, and upgrades.
- Product website: https://sglang.io/
- Source review: 2026-11-16; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

Apache License 2.0 for upstream SGLang. Model weights and hardware/runtime dependencies have their own licenses. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated inference server and model weights on configured accelerator hosts. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- ai-inference-gateways: Model-serving framework for LLM and multimodal inference; an inference runtime rather than a full multi-provider governance gateway.

- ai-tools: Customer-operated inference infrastructure for serving supported model weights.

### Deployment boundaries


- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cloud.google.com/kubernetes-engine/docs/how-to/setup-multicluster-inference-gateway (checked 2026-11-12). 


### Cloud deployment evidence

- SGLang compatibility with GKE Inference Gateway (gcp): https://docs.cloud.google.com/kubernetes-engine/docs/how-to/setup-multicluster-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.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The upstream release history documents hundreds of pull requests from many named contributors and sustained releases; its README describes production use across labs, platforms and enterprises.

Reviewed 2026-11-10.

- Release maintenance and contributor participation: https://github.com/sgl-project/sglang/releases

- Project and production-use context: https://raw.githubusercontent.com/sgl-project/sglang/main/README.md

### Sources

- Official installation and runtime: https://docs.sglang.io/docs/get-started/install

- Upstream project and capabilities: https://github.com/sgl-project/sglang

- Current upstream license: https://raw.githubusercontent.com/sgl-project/sglang/main/LICENSE

- CVE-2026-111391 debug dumper filter code injection: https://nvd.nist.gov/vuln/detail/CVE-2026-111391

- Upstream SGLang dumper-filter RCE issue: https://github.com/sgl-project/sglang/issues/44188

- SGLang v0.5.23 debug dumper implementation: https://github.com/sgl-project/sglang/blob/v0.5.23/python/sglang/srt/debug_utils/dumper.py#L1309-L1320

- CVE-2026-111391 primary record and affected-version range: https://cveawg.mitre.org/api/cve/CVE-2026-111391

### Licensing sources

- https://raw.githubusercontent.com/sgl-project/sglang/main/LICENSE

### Infrastructure sources

- https://docs.sglang.io/docs/get-started/install


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. Server arguments document inference and administrative API keys with separate endpoint rules. The reviewed upstream configuration does not establish SAML/OIDC login, user provisioning or a supported IdP integration. Confirm a gateway-based identity design instead of treating a static API key as SSO. Scope: Upstream inference-server/API authentication; federation unresolved. Source: https://docs.sglang.ai/advanced_features/server_arguments.html (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. The reported shared-API dumper exposure requires DUMPER_SERVER_PORT=reuse and access to configure a filter followed by a model execution. Without a separate admin key, an ordinary API key can reach the route; without any API key, it can be anonymous. A configured admin key is required when present. Keep dumper/debug routes disabled or network-isolated. The CVE enumerates 0.5.10–0.5.22; retained filter code in 0.5.23 is not by itself a complete assessment of every authentication configuration. Scope: Debug dumper trust boundary and deployment precautions; not a blanket claim that all SGLang endpoints or all later releases are unauthenticated. Source: https://github.com/sgl-project/sglang/issues/44188 (reviewed 2026-11-16). Supporting source: Primary CVE record — https://cveawg.mitre.org/api/cve/CVE-2026-111391. Supporting source: SGLang v0.5.23 shared dumper route and authentication level — https://github.com/sgl-project/sglang/blob/v0.5.23/python/sglang/srt/entrypoints/http_server.py. Supporting source: SGLang v0.5.23 filter implementation — https://github.com/sgl-project/sglang/blob/v0.5.23/python/sglang/srt/debug_utils/dumper.py#L1309-L1320.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream installation guide supplies container, Compose and Kubernetes options for model serving. Match model/backend, accelerator drivers and selected image; examples do not establish a universal GPU or memory minimum. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.sglang.io/docs/get-started/install (reviewed 2026-11-14).

- Minimum footprint / sizing: Sources checked — unresolved. The server configuration sizes model loading, quantization, parallelism, KV cache and admitted requests through memory controls such as mem-fraction-static. It does not establish one safe CPU/RAM/VRAM minimum. Select model, precision, context, concurrency and availability, then validate the chosen accelerator topology. Scope: Model and serving-configuration dependent; complete production footprint unresolved. Source: https://docs.sglang.ai/advanced_features/server_arguments.html (reviewed 2026-11-20).

- 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/sgl-project/sglang/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

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




### Security and lifecycle reviews

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

- SGLang debug dumper code execution (security-advisory): CVE-2026-111391 identifies code execution in the debug dumper filter. Check the debug endpoint exposure and authentication boundary. Scope: CVE record: SGLang 0.5.10–0.5.22. The open upstream report and reviewed v0.5.23 code do not establish a fixed release. Conditions: Requires dumper configuration access and a subsequent model execution reaching a dumper hook. In shared-API mode, an ordinary API key can suffice without a separate admin key; authentication configuration changes exposure. Action: Disable or isolate debug dumper endpoints and verify an upstream fix before treating a newer release as remediated. Source: https://cveawg.mitre.org/api/cve/CVE-2026-111391; reviewed 2026-11-16. Supporting source: Upstream report and authentication conditions — https://github.com/sgl-project/sglang/issues/44188. Supporting source: Reviewed v0.5.23 filter implementation — https://github.com/sgl-project/sglang/blob/v0.5.23/python/sglang/srt/debug_utils/dumper.py#L1309-L1320.




## Strategy Enterprise in Your Cloud

Vendor-managed enterprise analytics and AI platform deployed as a dedicated single-tenant environment in the customer's public-cloud account.

- Listing: https://launchinyourcloud.com/directory/strategy-enterprise/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp, stackit
- Operating model: Vendor-operated BYOC
- Infrastructure IDs: servers
- License: Commercial Strategy Enterprise subscription; customer-cloud deployment is not available with the Standard plan.
- Licensing model: commercial-only
- Installation: Vendor-assisted, fully managed deployment into the customer's licensed AWS, Azure Google Cloud or STACKIT environment
- Architecture: Dedicated containerized Strategy services in a customer-licensed VPC or VNet, administered and maintained by Strategy.
- Operations: Strategy administers and maintains the platform; the customer supplies the cloud environment, data sources, identity, network approvals and shared governance responsibilities.
- Product website: https://software.strategy.com/pricing
- Source review: 2026-11-17; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

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.

The customer-cloud option is a commercial Strategy Enterprise service. Strategy Standard is vendor-hosted and does not include deployment into the customer's cloud; exact entitlements and cloud-credit treatment follow the Enterprise contract.

Strategy describes a dedicated single-tenant, containerized environment using cloud virtual networks and provider infrastructure in the customer's licensed cloud, with Strategy operating the platform.


### Category fit

- data-analytics: Enterprise business intelligence, dashboards, reporting, embedded analytics and governed data exploration in a dedicated environment.

- ai-tools: Enterprise includes customizable AI agents and AI-assisted analysis capabilities; exact features and model integrations follow the contracted platform.

### Deployment boundaries


- aws: Customer cloud account; Vendor / partner-operated; control plane: not-assessed. Source: https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise (checked 2026-11-17). 

- azure: Customer cloud account; Vendor / partner-operated; control plane: not-assessed. Source: https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise (checked 2026-11-17). 

- gcp: Customer cloud account; Vendor / partner-operated; control plane: not-assessed. Source: https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise (checked 2026-11-17). 

- stackit: Customer cloud account; Vendor / partner-operated; control plane: not-assessed. Source: https://software.strategy.com/pricing (checked 2026-11-17). 

Operating responsibility: Strategy Enterprise is fully managed in the customer's selected cloud environment. The customer administers the analytics solution while Strategy maintains platform infrastructure and application upgrades. Source: https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise (checked 2026-11-20). Supporting source: Enterprise customer-cloud eligibility, including STACKIT — https://software.strategy.com/pricing.


### Cloud deployment evidence

- Strategy Enterprise in customer-licensed AWS, Azure or Google Cloud (aws, azure, gcp): https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise
  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.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- Strategy Enterprise customer-cloud deployment on STACKIT (stackit): https://software.strategy.com/pricing
  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.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Strategy plans, customer-cloud option and named providers: https://software.strategy.com/pricing

- Strategy Managed Cloud Enterprise security and operating model: https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise

- Strategy on AWS and customer-licensed cloud environments: https://software.strategy.com/ecosystems/aws

- Strategy product licensing list: https://software.strategy.com/company/product-listing

- Strategy for regulated industries and customer-cloud custody: https://software.strategy.com/ecosystems/regulated-industries

### Licensing sources

- https://software.strategy.com/pricing

- https://software.strategy.com/company/product-listing

### Infrastructure sources

- https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise

- https://software.strategy.com/pricing


### Buyer diligence


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

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


- Marketplace delivery: Sources checked — unresolved. The Enterprise FAQ permits customer-cloud deployment and conditional commitment usage, but does not identify the offer/delivery terms for each provider. Confirm the managed Enterprise order. Scope: Reviewed public evidence for Strategy Enterprise in Your Cloud; unresolved within this edition/deployment. Source: https://software.strategy.com/pricing (reviewed 2026-11-17).

- Cloud commitment eligibility: Edition-dependent. The Enterprise pricing FAQ states usage can count toward cloud commitments/credits for the supported customer-cloud deployment. Confirm the provider agreement, offer and eligible charges; Standard is a different deployment tier. Scope: Enterprise customer-cloud procurement statement, conditional eligibility. Source: https://software.strategy.com/pricing (reviewed 2026-11-17).

- Single sign-on: Sources checked — unresolved. Strategy Library documents SAML/OIDC interaction with SCIM, but the reviewed guide does not establish the managed Enterprise package, IdP configuration and contractual entitlement for this listing. Scope: Strategy One identity features versus purchased Enterprise service. Source: https://www2.strategy.com/producthelp/Current/WorkstationWeb/en-us/Content/config_lib_server_scim.htm (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. Strategy One Library documents SCIM 2.0 from September 2025, but the reviewed material does not establish which Library release, enablement and entitlement are supplied in the purchased managed Enterprise environment. Confirm these before treating it as included. Scope: Strategy One feature evidence; managed Enterprise delivery/entitlement unconfirmed. Source: https://www2.strategy.com/producthelp/Current/Workstation/en-us/Content/config_lib_server_scim.htm (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The Enterprise security page names SOC 2, ISO 27001 and other frameworks, but the actual report/certificate scope, audit period and applicability to the purchased customer-account deployment were not available in the reviewed page. Scope: Enterprise marketing claims versus scoped current attestation. Source: https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise (reviewed 2026-11-17).

- Security controls: Documented. The Enterprise architecture describes a dedicated, single-tenant customer-account boundary with vendor administration and VPC configuration. Review the operational access and responsibility split in the contract. Scope: Enterprise account/network boundary; certification scope reviewed separately. Source: https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise (reviewed 2026-11-17).

- Air-gapped operation: Sources checked — unresolved. Customer-account/VPC custody and dedicated vendor management do not establish no-internet operation, offline licensing or isolated vendor administration. Scope: Reviewed public evidence for Strategy Enterprise in Your Cloud; unresolved within this edition/deployment. Source: https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. Enterprise is vendor-managed in the customer cloud account. Obtain the approved provisioning/access design and region/topology with the Enterprise order; a public self-service Terraform/Helm artifact is not established. Scope: Vendor-operated Enterprise deployment, not Standard hosted service. Source: https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise (reviewed 2026-11-17).

- Minimum footprint / sizing: Sources checked — unresolved. The managed Enterprise page does not publish a complete HA bill of materials for 100 users/1 TB. Obtain the service topology, regional availability, capacity and responsibility split in the quote. Scope: Reviewed public evidence for Strategy Enterprise in Your Cloud; unresolved within this edition/deployment. Source: https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise (reviewed 2026-11-17).

- License pricing: Documented. The customer-cloud option is a commercial Strategy Enterprise service. Strategy Standard is vendor-hosted and does not include deployment into the customer's cloud; exact entitlements and cloud-credit treatment follow the Enterprise contract. Scope: Strategy Enterprise in Your Cloud: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://software.strategy.com/pricing (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Obtain the managed Enterprise HA deployment/region bill of materials, user roles, service fees, data-processing profile and cloud-resource billing boundary from the vendor. A complete monthly operating estimate is not established. Scope: Requested planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA, average usage; missing workload metrics and commercial terms are explicit. Source: https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise (reviewed 2026-11-17).

- Release snapshot / cadence: Sources checked — unresolved. Strategy One Library feature dates do not establish the release installed or upgrade cadence in the contracted Enterprise managed service. Obtain its maintenance and version policy. Scope: Reviewed public evidence for Strategy Enterprise in Your Cloud; unresolved within this edition/deployment. Source: https://www2.strategy.com/producthelp/Current/Workstation/en-us/Content/config_lib_server_scim.htm (reviewed 2026-11-17).







## vLLM Self-Hosted

Self-hosted model inference and serving engine with OpenAI-compatible APIs.

- Listing: https://launchinyourcloud.com/directory/vllm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache 2.0 for vLLM; model weights and supporting dependencies have independent licenses and access conditions.
- Licensing model: open-source
- Installation: Official vLLM Docker image or supported Python installation; choose a compatible hardware/backend configuration.
- Architecture: Customer-operated model-serving process, model weights and inference hardware
- Operations: Customer manages model acquisition, hardware capacity, endpoint protection, availability, upgrades and model/runtime compatibility.
- Product website: https://vllm.ai/
- Source review: 2026-11-17; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-17

### Scope and qualifications

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.

The reviewed inference runtime is Apache-2.0 licensed. Its license does not grant rights to the model weights served by that runtime; check model and dependency terms separately.

vLLM is a running inference-server workload. Hardware support and capacity depend on the model and selected backend; the documented container paths include accelerator-specific images, and CPU support is separately documented. In v0.34.0, the KV-cache allocator sizes from free memory after warmup and defaults to gpu_memory_utilization=1.0; revalidate GPU headroom, and set 0.9 or disable extensible cache to retain prior sizing. ROCm 10.0 replaces 7.2 for published images and wheels.


### Category fit

- ai-inference-gateways: Model inference engine and OpenAI-compatible serving API for compatible model weights. Distinct from an API gateway that forwards calls to proprietary hosted models.

- ai-tools: Self-hosted model inference and serving engine with OpenAI-compatible APIs.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.vllm.ai/projects/production-stack/en/vllm-stack-0.1.4/deployment/cloud-deployment/aws.html (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.vllm.ai/projects/production-stack/en/vllm-stack-0.1.4/deployment/cloud-deployment/azure.html (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.vllm.ai/projects/production-stack/en/vllm-stack-0.1.4/deployment/cloud-deployment/gcp.html (checked 2026-11-12). 


### Cloud deployment evidence

- vLLM Production Stack deployment on Amazon EKS (aws): https://docs.vllm.ai/projects/production-stack/en/vllm-stack-0.1.4/deployment/cloud-deployment/aws.html
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- vLLM Production Stack deployment on Azure Kubernetes Service (azure): https://docs.vllm.ai/projects/production-stack/en/vllm-stack-0.1.4/deployment/cloud-deployment/azure.html
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- vLLM Production Stack deployment on Google Kubernetes Engine (gcp): https://docs.vllm.ai/projects/production-stack/en/vllm-stack-0.1.4/deployment/cloud-deployment/gcp.html
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Official Docker serving images: https://docs.vllm.ai/en/latest/deployment/docker/

- Online serving: https://docs.vllm.ai/en/latest/serving/online_serving/

- Usage statistics and opt-out: https://docs.vllm.ai/en/latest/usage/usage_stats/

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

- vLLM v0.34.0 breaking upgrade notes: https://github.com/vllm-project/vllm/releases/tag/v0.34.0

### Licensing sources

- https://github.com/vllm-project/vllm/blob/main/LICENSE

### Infrastructure sources

- https://docs.vllm.ai/en/latest/deployment/docker/

- https://github.com/vllm-project/vllm/releases/tag/v0.34.0


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The security guide documents API-key protection for specified HTTP path prefixes and warns that other sensitive endpoints remain unprotected. It does not establish a native SAML/OIDC user sign-on workflow. Use a reviewed gateway/network design; an API bearer key alone is not corporate SSO or complete endpoint protection. Scope: Upstream inference-server auth surface; federated user integration unresolved. Source: https://docs.vllm.ai/en/latest/usage/security/ (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The stable deployment guide links the official vllm/vllm-openai image for a CUDA-backed OpenAI-compatible server. Select a release/architecture tag and compatible GPU drivers; model memory, credentials and optional dependencies need separate review. Scope: Stable upstream CUDA image path; not the latest developer-preview guide or a GPU sizing guarantee. Source: https://docs.vllm.ai/en/stable/deployment/docker/ (reviewed 2026-11-14). Deployment artifact: https://hub.docker.com/r/vllm/vllm-openai. Artifact reference: select a stable version and architecture tag; latest is moving.

- Minimum footprint / sizing: Sources checked — unresolved. The stable memory guide sizes serving around model weights, precision/quantization, tensor parallelism, context length, batch size and cache. A supported accelerator alone does not establish sufficient memory. Select the exact model and target throughput/latency, then benchmark VRAM/RAM and HA replica requirements. Scope: Model-specific inference sizing; no universal numeric footprint established. Source: https://docs.vllm.ai/en/stable/configuration/conserving_memory/ (reviewed 2026-11-20).

- 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/vllm-project/vllm/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The reviewed upstream release is v0.34.0, published 2026-11-16. This is a dated release snapshot, not a support designation, a future cadence promise or approval to replace a provider package. Scope: Upstream vllm-project/vllm release record; commercial editions, LTS branches and provider packages can differ. Source: https://github.com/vllm-project/vllm/releases/tag/v0.34.0 (reviewed 2026-11-17).







## Weaviate Self-Hosted

Self-hosted vector-search database for retrieval and AI applications.

- Listing: https://launchinyourcloud.com/directory/weaviate/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: BSD-3-Clause core outside the wl directory; wl code and associated enterprise features require a separate enterprise license/key.
- Licensing model: open-source
- Installation: Docker or Docker Compose, or a Kubernetes deployment using Helm. Google’s GKE guide uses Terraform to provision the cluster.
- Architecture: Customer-operated vector database, persistent storage and optional model integrations
- Operations: Customer manages authentication, storage, backup, scaling, configuration and upgrades.
- Product website: https://weaviate.io/
- Source review: 2026-11-21; cloud review: 2026-11-21; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

The current repository distinguishes BSD-3-Clause code outside wl/ from enterprise-licensed wl/ code and features enabled by a license key. The complete current product is therefore classified as open-core, not uniformly BSD licensed.

Docker/Compose or Kubernetes runs a provisioned persistent database service. Data-plane ownership does not include optional external model integrations; choose and size those separately.


### Category fit

- databases-vector: Vector database supporting pre-vectorized search and configurable model integrations. Connected embedding/generation modules and enterprise features are separate dependencies.

- ai-tools: Self-hosted vector-search database for retrieval and AI applications.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.weaviate.io/deploy/production/aws (checked 2026-11-21). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cloud.google.com/kubernetes-engine/docs/tutorials/deploy-weaviate (checked 2026-11-21). 


### Cloud deployment evidence

- Weaviate self-managed AWS deployment options (aws): https://docs.weaviate.io/deploy/production/aws
  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.
  Source type: vendor-documentation; reviewed: 2026-11-21; vendor support: not-assessed.

- Deploy self-hosted Weaviate on Google Kubernetes Engine (gcp): https://docs.cloud.google.com/kubernetes-engine/docs/tutorials/deploy-weaviate
  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.
  Source type: provider-guide; reviewed: 2026-11-21; vendor support: not-assessed.


### Sources

- Docker and persistent-storage deployment: https://docs.weaviate.io/deploy/installation-guides/docker-installation

- Default telemetry and configuration: https://docs.weaviate.io/deploy/configuration/telemetry

- Core and enterprise license split: https://github.com/weaviate/weaviate/blob/main/LICENSE

- Weaviate v1.39.17 maintenance release: https://github.com/weaviate/weaviate/releases/tag/v1.39.17

- Runtime reindex restart fix: https://github.com/weaviate/weaviate/pull/13755

- Deploy self-hosted Weaviate on Google Kubernetes Engine: https://docs.cloud.google.com/kubernetes-engine/docs/tutorials/deploy-weaviate

### Licensing sources

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

### Infrastructure sources

- https://docs.weaviate.io/deploy/installation-guides/docker-installation


### 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: Documented. Self-hosted Weaviate supports OpenID Connect alongside API keys, with Docker and Kubernetes configuration examples. Authentication and RBAC authorization are separate; configure issuer/client settings and role mapping, and disable anonymous access for production. Scope: Self-hosted database OIDC authentication. Source: https://docs.weaviate.io/deploy/configuration/authentication (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. The self-managed authentication guide supports API keys and OIDC and also permits anonymous access. Configure authentication and authorization together; an anonymous quickstart is not a protected production endpoint. Scope: Weaviate database/API controls; not a vendor compliance attestation. Source: https://docs.weaviate.io/deploy/configuration/authentication (reviewed 2026-11-14).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Docker guide supplies an official image and configurable Compose recipe. Its default example enables anonymous access; configure authentication, persistent volumes and required modules before exposing the service. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.weaviate.io/deploy/installation-guides/docker-installation (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The resource-planning guide estimates roughly 3 GB memory for one million uncompressed 384-dimensional float32 vectors using its two-times rule. HNSW connectivity, compression, payloads, replicas and concurrency change requirements; CPU affects query/import throughput. This is an index-sizing example, not a complete minimum or 1-TB/HA guarantee. Scope: Upstream vector-index memory example; full workload/topology sizing additional. Source: https://docs.weaviate.io/weaviate/concepts/resources (reviewed 2026-11-20).

- License pricing: Documented. Code outside the wl directory is BSD-3-Clause; wl contains separately licensed Enterprise functionality enabled by a licence key. The core licence does not grant those features. Obtain Enterprise pricing and support terms separately from infrastructure. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/weaviate/weaviate/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v1.40.5, published 2026-11-10. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. The maintained v1.39 branch has a separate v1.39.17 runtime-reindex restart fix; this does not replace the newer v1.40.5 primary snapshot. Scope: Upstream weaviate/weaviate release record; commercial editions and deployment packages may differ. Source: https://github.com/weaviate/weaviate/releases/tag/v1.40.5 (reviewed 2026-11-19). Supporting source: v1.39.17 maintenance release — https://github.com/weaviate/weaviate/releases/tag/v1.39.17. Supporting source: Runtime reindex fix — https://github.com/weaviate/weaviate/pull/13755.






