
# Data & analytics on AWS

Compare documented Data & analytics deployments on AWS, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/aws/data-analytics/
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: AWS account
- 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.aws.amazon.com/accounts/latest/reference/getting-started.html (checked 2026-11-20).
- Network: VPC
- Identity and access: IAM roles and policies
- Installation guidance: CloudFormation or Terraform; review stack changes and requested IAM permissions.
- Guidance source: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html
- Guidance reviewed: 2026-11-10


### Private offers

AWS Marketplace private offers can contain negotiated pricing and terms for a buyer account. Confirm the product delivery model and your agreement; commitment credit is not established by a directory badge.
Source: https://docs.aws.amazon.com/marketplace/latest/buyerguide/buyer-private-offers-subscribing.html (reviewed 2026-11-14).

### Private connectivity

PrivateLink provides private endpoints to supported services and resources across VPC/account boundaries. Confirm that the selected product exposes a compatible endpoint service.
Source: https://docs.aws.amazon.com/vpc/latest/privatelink/what-is-privatelink.html (reviewed 2026-11-14).

### Cross-account operations

Use an IAM role with scoped permissions and a third-party external ID where applicable. Review the trust principal, support access and revocation separately from installation access.
Source: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_third-party.html (reviewed 2026-11-14).

### Government environments

AWS GovCloud (US) is a distinct isolated-region environment. A commercial-region product deployment does not establish availability or certification there.
Source: https://docs.aws.amazon.com/govcloud-us/latest/UserGuide/whatis.html (reviewed 2026-11-14).

The listings below have evidence for Amazon Web Services. Read each cloud evidence note for the applicable package, edition and support qualifications.

37 listings.


## Airbyte Self-Managed

Self-managed data movement and ELT platform with customer-operated connectors and job execution.

- Listing: https://launchinyourcloud.com/directory/airbyte/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Elastic License 2.0 for the Airbyte platform; connector and component licenses vary. Enterprise and Cloud offerings use separate commercial terms.
- Licensing model: source-available
- Installation: Official Helm chart for current Kubernetes deployments; cloud VMs are also documented. DigitalOcean separately lists a legacy 1-Click Droplet image.
- Architecture: Customer-operated platform services, connector jobs, metadata database and object storage
- Operations: Customer manages Kubernetes or VM capacity, the metadata database, object storage, secrets, connector images, network access, backups and upgrades.
- Product website: https://airbyte.com/
- Source review: 2026-11-13; cloud review: 2026-11-13; licensing review: 2026-11-13; infrastructure review: 2026-11-13

### Scope and qualifications

This entry covers Airbyte Self-Managed, not Airbyte Cloud or the hybrid offering. Connector jobs communicate with configured external sources and destinations. Elastic License 2.0 permits internal self-hosting but restricts offering the software as a managed service and bypassing license-key functionality. DigitalOcean lists a separate legacy v0.30.25 Marketplace image on Ubuntu 20.04. That evidence does not establish current Helm-release compatibility or current vendor support; verify image availability, upgrade paths and support for the selected release.

The Airbyte platform uses Elastic License 2.0, which permits self-hosting and source modification but restricts managed-service use and protected license functionality. Connectors and development tooling can carry different licenses; inspect the selected component and release. Commercial Enterprise and Cloud terms are separate.

The documented deployment uses long-lived Kubernetes platform services and connector job pods, with a metadata database and object storage. Managed cloud databases or object stores do not make the application runtime serverless.


### Category fit

- data-analytics: Moves data between APIs, databases, files, warehouses and lakes using customer-operated connectors and synchronization jobs.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.airbyte.com/platform/deploying-airbyte (checked 2026-11-13). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.airbyte.com/platform/deploying-airbyte (checked 2026-11-13). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.airbyte.com/platform/deploying-airbyte (checked 2026-11-13). 

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


### Cloud deployment evidence

- Airbyte self-managed deployment on named cloud providers (aws, azure, gcp): https://docs.airbyte.com/platform/deploying-airbyte
  Airbyte documents its Helm deployment for Kubernetes and explicitly names AWS, Google Cloud and Azure, including EC2/EKS and GCE/GKE examples. This is the self-managed application path; configure provider policies, external storage, secrets and production ingress separately.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Airbyte-published v0.30.25 DigitalOcean Droplet image (digitalocean): https://marketplace.digitalocean.com/apps/airbyte
  DigitalOcean lists an Airbyte-published 1-Click Droplet image, version 0.30.25 on Ubuntu 20.04, and provides creation instructions for the customer account. This is legacy, version-specific application deployment evidence, not verification of the current Helm-based release or current vendor support. Confirm image availability, compatibility, upgrade paths and support before selecting this route.
  Source type: marketplace-offer; reviewed: 2026-11-13; vendor support: not-assessed.


### Sources

- Airbyte platform and self-managed plans: https://docs.airbyte.com/platform

- Self-managed Kubernetes and cloud deployment: https://docs.airbyte.com/platform/deploying-airbyte

- Elastic License 2.0 FAQ: https://github.com/airbytehq/airbyte/blob/master/docs/community/licenses/license-faq.md

- Airbyte platform Elastic License 2.0: https://github.com/airbytehq/airbyte/blob/master/LICENSE

- Legacy Airbyte v0.30.25 DigitalOcean Marketplace image: https://marketplace.digitalocean.com/apps/airbyte

### Licensing sources

- https://github.com/airbytehq/airbyte/blob/master/LICENSE

- https://github.com/airbytehq/airbyte/blob/master/docs/community/licenses/license-faq.md

### Infrastructure sources

- https://docs.airbyte.com/platform/deploying-airbyte

- https://marketplace.digitalocean.com/apps/airbyte


### 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: Documented. The DigitalOcean 1-Click page still identifies Airbyte 0.30.25 on Ubuntu 20.04. This is legacy package evidence, not confirmation of a current release, current support or suitability for a new production deployment. Scope: Legacy DigitalOcean image; current upstream deployment requires separate validation. Source: https://marketplace.digitalocean.com/apps/airbyte (reviewed 2026-11-14). Offer airbyte: Airbyte; Droplet 1-Click; package 0.30.25; https://marketplace.digitalocean.com/apps/airbyte.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The vendor documents OIDC login for self-managed instances, but the current plan comparison emphasizes Cloud/Enterprise Flex while Core quickstart uses local credentials. The reviewed pages do not unambiguously establish federation entitlement for the selected Core distribution; obtain edition/version confirmation. Scope: Self-managed OIDC workflow; Core edition entitlement unresolved. Source: https://docs.airbyte.com/platform/access-management/sso (reviewed 2026-11-20). Supporting source: Current self-managed and hybrid plan scope — https://docs.airbyte.com/platform. Supporting source: Core quickstart authentication — https://docs.airbyte.com/platform/using-airbyte/getting-started/oss-quickstart.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Airbyte publishes abctl to install a local Kubernetes-based Core instance and a Helm deployment path for customer infrastructure. Local abctl creates its own cluster using Docker; production requires separately configured ingress, storage, secrets and chart/application compatibility. Scope: Official Core installation tooling; local cluster is not an HA architecture. Source: https://docs.airbyte.com/platform/deploying-airbyte/abctl (reviewed 2026-11-20). Deployment artifact: https://github.com/airbytehq/abctl. Artifact reference: Choose an abctl release and compatible chart version.

- Minimum footprint / sizing: Documented. The Core quickstart recommends at least 4 CPUs and 8 GB RAM; low-resource mode can run with 2 CPUs and 8 GB but disables Connector Builder. This is a local deployment profile. Connector concurrency, storage and production/HA components require separate sizing. Scope: Airbyte Core local installation; production HA excluded. Source: https://docs.airbyte.com/platform/using-airbyte/getting-started/oss-quickstart (reviewed 2026-11-20).

- License pricing: Documented. The platform is under Elastic License 2.0, including restrictions on offering a substantial hosted/managed service and bypassing licence keys. Connector licences vary. Enterprise features, support and alternative commercial rights require separate terms; this does not price infrastructure. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/airbytehq/airbyte/master/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Apache Doris Self-Hosted

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

- Listing: https://launchinyourcloud.com/directory/apache-doris/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, alibaba, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for the core project; optional third-party components can carry separate or incompatible licenses.
- Licensing model: open-source
- Installation: Doris Operator on AWS EKS or Alibaba ACK/ACS, or cloudimg’s Azure VM image; pin application/operator/image versions separately
- Architecture: Customer-operated FE/BE services with persistent storage, through Kubernetes or a separately packaged single-node Azure VM.
- Operations: Customer manages the selected Kubernetes platform or Azure VM/OS, provider permissions, networking, persistent storage, database identities, backups, monitoring, scaling and upgrades. Upstream EKS/ACK/ACS instructions and the seller VM have different host and service boundaries.
- Product website: https://doris.apache.org/
- Source review: 2026-11-18; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

This entry covers Apache Doris, not a vendor-hosted derivative. Upstream guides document EKS and Alibaba ACK/ACS; ACS needs privileged BE initialization and has service/network constraints. The separate cloudimg Azure image packages Doris 4.0.6 with one FE/BE and is not HA. Its moving image and older application version require review; seller packaging does not establish Apache support. Review quorum, replication, storage and optional dependency licences for the chosen topology.

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

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


### Category fit

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

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

### Deployment boundaries


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

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

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


### Cloud deployment evidence

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

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

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


### Community and maintenance

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

Reviewed 2026-11-18.

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

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

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

### Sources

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

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

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

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

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

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

### Licensing sources

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

### Infrastructure sources

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

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

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


### Buyer diligence


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

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


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

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

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

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

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

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

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

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

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

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

- Operating cost estimate: Sources checked — unresolved. Specify ingestion rate, query concurrency, indexes, compression, replica count, FE quorum, BE count, compaction reserve and storage-compute mode. One TB raw data and 100 users do not determine usable replicated storage, IOPS or an HA compute bill. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://doris.apache.org/docs/4.x/install/preparation/env-checking/ (reviewed 2026-11-18). Supporting source: Current AWS Linux EC2 rates; workload/topology still required — https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json. Supporting source: Storage performance and charging inputs — https://aws.amazon.com/ebs/pricing/.

- Release snapshot / cadence: Documented. Apache Doris 4.1.5-release was published October 15, 2026. This application release is separate from the date/version of Doris Operator. Use stable documentation and verify operator/application compatibility; dev documentation describes unreleased behavior. cloudimg’s Azure guide/plan packages 4.0.6; it is separate from this 4.1.5-release snapshot and the resolved image version. Scope: Apache Doris Self-Hosted: selected customer-operated edition. Source: https://github.com/apache/doris/releases/tag/4.1.5-release (reviewed 2026-11-18). Supporting source: Older Azure packaged application — https://catalogapi.azure.com/offers/cloudimg1647283583153.apache-doris-ubuntu-24-04?api-version=2018-08-01-beta&market=US&language=en.







## Apache Druid

Column-oriented analytics database for interactive queries over streaming and historical event data.

- Listing: https://launchinyourcloud.com/directory/apache-druid/
- 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 Apache Druid.
- Licensing model: open-source
- Installation: Run the official server distribution with bin/start-druid; distributed production deployments require the documented cluster services and storage configuration.
- Architecture: Customer-operated JVM analytics services, metadata store and deep storage
- Operations: Customer manages cluster sizing, ingestion, metadata and deep storage, access controls, backups and upgrades.
- Product website: https://druid.apache.org/
- Source review: 2026-11-19; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The smallest bundled configurations are evaluation examples. Data ingestion connectors and storage destinations can involve external services; configure their account and network boundaries separately. Apache Druid 39.0.0 requires Java 25 and drops Java 21 support. Its upgrade notes also change SQL INSERT/REPLACE authorization, replace SysMonitor with OshiSysMonitor, add taskStatus to task/run/time metrics, change Netty direct-memory behavior, and move the bundled MariaDB driver to 3.5.10 with jdbc:mariadb: preferred. Test permissions, dashboards, memory limits and metadata-store URLs before rollout.

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

Customer-operated JVM analytics services, metadata store and deep storage. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- data-analytics: Real-time OLAP database for SQL analysis of ingested streaming and batch data; this is an analytics engine rather than a dashboard authoring application.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://druid.apache.org/faq/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://druid.apache.org/faq/ (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://druid.apache.org/faq/ (checked 2026-11-12). 


### Cloud deployment evidence

- Apache Druid cloud deployment FAQ (aws, azure, gcp): https://druid.apache.org/faq/
  The Apache project explicitly identifies AWS, Google Cloud and Azure as deployment environments for Druid. This is a project compatibility statement paired with the installation documentation, not a managed service or certification; configure metadata, deep storage and cluster operations separately.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Apache project with a maintained upstream release history and a project-curated production adopter directory including Adikteev, AdsWizz and Airbnb.

Reviewed 2026-11-10.

- Current Druid releases: https://github.com/apache/druid/releases

- Named production adopters: https://druid.apache.org/druid-powered/

### Sources

- Official installation and runtime: https://druid.apache.org/docs/latest/operations/single-server/

- Upstream project and capabilities: https://github.com/apache/druid

- Current upstream license: https://github.com/apache/druid/blob/master/LICENSE

- Analytics functionality: https://druid.apache.org/

- Apache Druid 39.0.0 release: https://github.com/apache/druid/releases/tag/druid-39.0.0

- Apache Druid 39.0.0 upgrade notes: https://druid.apache.org/docs/39.0.0/release-info/upgrade-notes

### Licensing sources

- https://github.com/apache/druid/blob/master/LICENSE

### Infrastructure sources

- https://druid.apache.org/docs/latest/operations/single-server/


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The druid-kerberos extension provides SPNEGO/GSSAPI authentication for Druid HTTP endpoints, with service principals, keytabs, cookies and authorizer mapping. Configure compatible browser/API clients and protect every endpoint; this is Kerberos federation, not native SAML/OIDC. Scope: Upstream HTTP Kerberos/SPNEGO authentication extension. Source: https://druid.apache.org/docs/latest/development/extensions-core/druid-kerberos/ (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 server distribution includes bin/start-druid, which derives memory settings from host resources. Older single-server reference scripts are deprecated; production cluster storage/services need a separate architecture plan. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://druid.apache.org/docs/latest/operations/single-server/ (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The current 39.0.0 local quickstart requires at least 6 GiB RAM and Java 25. It is an introductory single-machine ingestion/query setup, not a production or HA footprint. Data volume, ingestion tasks, service roles and availability requirements need separate sizing. Scope: Druid 39 local tutorial baseline; production capacity excluded. Source: https://druid.apache.org/docs/latest/tutorials/index.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. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/apache/druid/master/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Apache Druid druid-39.0.0 was published November 19, 2026. It requires Java 25, changes SQL write authorization and monitoring labels, replaces SysMonitor, changes Netty direct-memory behavior and updates MariaDB Connector/J. Review the complete incompatible-change and upgrade notes. Scope: Upstream Apache Druid release; deployment packages and commercial distributions may differ. Source: https://github.com/apache/druid/releases/tag/druid-39.0.0 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/apache/druid/releases/tag/druid-38.0.0. Supporting source: Version-specific upgrade notes — https://druid.apache.org/docs/39.0.0/release-info/upgrade-notes.







## Apache Superset

Business intelligence and data exploration platform for SQL analysis, visualizations and shared dashboards.

- Listing: https://launchinyourcloud.com/directory/apache-superset/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream Superset; bundled subcomponents have their listed licenses. Commercial hosted services are separate offerings.
- Licensing model: open-source
- Installation: Install the Python application or build a Docker image; current Kubernetes guidance recommends the official Superset Kubernetes Operator. Docker Compose is documented for evaluation and customized deployments.
- Architecture: Customer-operated web application and metadata database, with optional cache and Celery workers for asynchronous queries, alerts and reports
- Operations: Customer operates the application, Kubernetes or servers, metadata database, database drivers, authentication, secrets, backups and upgrades.
- Product website: https://superset.apache.org/
- 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 documentation is marked Next and recommends the operator; the older in-tree Superset Helm chart is deprecated for new deployments. Match operator, image and configuration guidance to the selected released version. Connected databases and configured services may be hosted elsewhere. Self-hosting Superset does not relocate those data sources.

The reviewed upstream project uses Apache License 2.0. This classification covers the upstream software; third-party components and separately operated services retain their own terms.

Superset is a Python web application with persistent metadata storage. The operator deploys its components to a customer-operated Kubernetes cluster; cache and worker requirements depend on enabled features.


### Category fit

- data-analytics: SQL exploration, interactive charts and dashboards over connected databases; Superset queries existing data sources rather than supplying the underlying data warehouse.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://awslabs.github.io/data-on-eks/docs/datastacks/databases/superset-on-eks/infra (checked 2026-11-12). 


### Cloud deployment evidence

- Apache Superset infrastructure on Amazon EKS (aws): https://awslabs.github.io/data-on-eks/docs/datastacks/databases/superset-on-eks/infra
  AWS Data on EKS documents deployment of Superset with its PostgreSQL metadata backend and Redis cache in a customer EKS stack. Review the reference configuration, secrets, authentication, persistent storage and upgrades; this is self-operated Apache Superset rather than a separate hosted analytics product.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Apache governance reports describe ongoing contributor activity and 2026 release work. The ASF project metrics record Superset 6.1.0 and several operator releases in 2026. The project-maintained In the Wild directory lists organizations including Airbnb, Lyft and American Express; this is adoption evidence, not an endorsement or a cloud deployment certification.

Reviewed 2026-11-10.

- Apache Superset board reports: https://www.apache.org/foundation/board/minutes/Superset.html

- ASF release and community metrics: https://projects.apache.org/metrics/project.html?id=superset

- Project-maintained adopter directory: https://superset.apache.org/inTheWild/

### Sources

- Apache Superset capabilities: https://superset.apache.org/

- Installation methods and current Kubernetes recommendation: https://superset.apache.org/admin-docs/installation/installation-methods/

- Application and database architecture: https://superset.apache.org/admin-docs/installation/architecture/

- Official Kubernetes Operator installation: https://apache.github.io/superset-kubernetes-operator/user-guide/installation/

- Upstream Apache-2.0 and subcomponent licenses: https://github.com/apache/superset/blob/master/LICENSE.txt

### Licensing sources

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

### Infrastructure sources

- https://superset.apache.org/admin-docs/installation/architecture/

- https://apache.github.io/superset-kubernetes-operator/user-guide/installation/


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The official configuration guide supports OAuth2 authorization-code providers through Flask-AppBuilder and Authlib, including custom providers. Configure provider callbacks, role mappings and registration policy; SAML is not established by this OAuth configuration. Scope: Upstream OAuth2/FAB authentication. Source: https://superset.apache.org/admin-docs/configuration/configuring-superset/ (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 repository supplies Compose quickstarts for evaluation and development. Production needs separate database, secrets, authentication and deployment configuration; do not treat the quickstart as a production support guarantee. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://github.com/apache/superset (reviewed 2026-11-14). Deployment artifact: https://github.com/apache/superset. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Documented. The project FAQ reports 2 vCPUs and 8 GB RAM as a community-observed moderate instance, with sizing driven by concurrent activity rather than data volume. This is not a formal minimum or HA recommendation. Production metadata database, workers, cache and the queried warehouse must be sized separately. Scope: Upstream workload example; production dependencies and HA excluded. Source: https://superset.apache.org/user-docs/faq/ (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/apache/superset/master/LICENSE.txt (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

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







## AVEVA PI System (BYOL)

Commercial industrial data collection, historian and visualization system with an AWS architecture.

- Listing: https://launchinyourcloud.com/directory/aveva-pi-system/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Package / binary installer
- Architecture: AWS Outposts edge components plus regional EC2 application, database and visualization services.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://docs.aws.amazon.com/solutions/hosting-aveva-pi-system-on-aws/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The reviewed AWS Guidance includes Outposts for core collection/historian components; it is not a region-only VM installation. PI component versions and licences are separate. Industrial telemetry does not itself supply environmental-compliance document management.

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

AWS Outposts edge components plus regional EC2 application, database and visualization services. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- data-analytics: Commercial industrial data collection, historian and visualization system with an AWS architecture.

- observability: Commercial industrial data collection, historian and visualization system with an AWS architecture.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.aws.amazon.com/solutions/hosting-aveva-pi-system-on-aws/ (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Guidance (aws): https://docs.aws.amazon.com/solutions/hosting-aveva-pi-system-on-aws/
  AWS Outposts edge components plus regional EC2 application, database and visualization services. The reviewed AWS Guidance includes Outposts for core collection/historian components; it is not a region-only VM installation. PI component versions and licences are separate. Industrial telemetry does not itself supply environmental-compliance document management.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS Guidance: https://docs.aws.amazon.com/solutions/hosting-aveva-pi-system-on-aws/

- AVEVA Licensing Policy Index (Commercial EULA): https://www.aveva.com/en/legal/policies-compliance/

- Clickwrap EULA: https://www.aveva.com/en/legal/aveva-general-terms-and-conditions-eula/

- Software Lifecycle Policy (Apr 2026): https://www.aveva.com/content/dam/aveva/documents/legal/policies/AVEVA-Software-Lifecycle-and-Retirement-Policy.pdf

- PI Data Infra Amazon RDS (Sep 2025): https://www.aveva.com/en/about/news/press-releases/2025/aveva-expands-its-offerings-for-aveva-pi-data-infrastructure-with-amazon-rds/

- AVEVA World 2026 (May 2026): https://www.aveva.com/en/about/news/press-releases/2026/aveva-announces-new-capabilities-to-embed-ai-across-industrial-organizations-and-data-infrastructure-at-aveva-world-2026/

### Licensing sources

- https://www.aveva.com/en/legal/policies-compliance/

- https://www.aveva.com/en/legal/aveva-general-terms-and-conditions-eula/

### Infrastructure sources

- https://docs.aws.amazon.com/solutions/hosting-aveva-pi-system-on-aws/


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. AVEVA documents PI Vision user authentication through Windows Integrated Security/Kerberos, and its public extensibility guide describes PI Vision/PI Web API 2023 OIDC with AVEVA Identity Manager. Configure service principals/delegation or the selected OIDC flow and component permissions. This confirms the visualization/web path, not identical SSO behavior across every PI component or release. Scope: Scoped PI Vision web-user authentication; not AWS IAM or a blanket PI System protocol entitlement. Source: https://docs.aveva.com/bundle/pi-vision/page/1009076.html (reviewed 2026-11-20). Supporting source: Official PI Vision/PI Web API OIDC and SSO integration — https://github.com/AVEVA/AVEVA-Samples-PI-System/blob/main/docs/PI-Vision-Extensibility-Docs/PI%20Vision%20Extensibility%20Guide.md.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. AWS documents a multi-zone PI System architecture with PI Vision, Asset Framework, Data Archive, SQL Server and edge connectivity. This architecture diagram does not identify the entitled application installers, exact component versions or a complete deployable IaC bundle. Obtain the licensed media and version-matched installation/migration sequence. Scope: Provider architecture confirmed; actual entitled application/deployment artifacts remain unconfirmed. Source: https://docs.aws.amazon.com/solutions/hosting-aveva-pi-system-on-aws/ (reviewed 2026-11-20).

- Minimum footprint / sizing: Sources checked — unresolved. The AWS guidance separates PI Vision, Asset Framework, Data Archive and SQL/edge roles but does not provide a current CPU/RAM/storage baseline for each selected component/version. Size PI points/events, ingestion, archive growth, concurrent displays and HA. Hardware figures for other AVEVA products are not PI System sizing evidence. Scope: Provider topology, not a workload-sized bill of materials; full production sizing remains unconfirmed. Source: https://docs.aws.amazon.com/solutions/hosting-aveva-pi-system-on-aws/ (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: AVEVA PI System (BYOL); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.aveva.com/en/legal/policies-compliance/ (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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




## Databricks classic compute

Data and AI platform with classic compute in your cloud environment.

- Listing: https://launchinyourcloud.com/directory/databricks/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Shared operations · vendor control plane
- Infrastructure IDs: servers
- License: Commercial
- Licensing model: commercial-only
- Installation: Cloud-specific workspace provisioning
- Architecture: Vendor control plane; customer classic compute
- Operations: The vendor manages the control plane. Your team configures classic compute, cloud resources and policies.
- Product website: https://www.databricks.com/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This entry covers classic compute only. Serverless compute runs in a Databricks-managed environment and is outside this entry. Confirm the responsibility split and metadata flows for your cloud. Beginning November 18, 2026, new VARIANT tables created on Databricks Runtime 17.3 or later automatically use variantShredding. Databricks Runtime 15.4 cannot read or write those tables, so upgrade affected classic clusters to 16.4 or later before creating or accessing them.

This listing covers the commercially provided managed/BYOC service, not a separately licensed open-source engine or library.

Classic compute uses customer-cloud compute resources. Databricks serverless compute is a different vendor-managed deployment and is outside this listing.


### Category fit

- data-analytics: Data and AI platform with classic compute in your cloud environment.

### Deployment boundaries


- aws: Customer cloud account; Shared operations; control plane: vendor-hosted. Source: https://docs.databricks.com/aws/en/getting-started/high-level-architecture (checked 2026-11-12). 

- azure: Customer cloud account; Shared operations; control plane: vendor-hosted. Source: https://learn.microsoft.com/en-us/azure/databricks/getting-started/high-level-architecture (checked 2026-11-12). 

- gcp: Customer cloud account; Shared operations; control plane: vendor-hosted. Source: https://docs.databricks.com/gcp/en/security/network/concepts/architecture (checked 2026-11-12). 

Operating responsibility: Classic compute and workspace storage are in the customer cloud account. Databricks operates the separate management plane; the customer configures compute, networking and policy. Serverless compute is outside this listing. Source: https://docs.databricks.com/aws/en/getting-started/high-level-architecture (checked 2026-11-20).


### Cloud deployment evidence

- Databricks classic compute architecture (aws): https://docs.databricks.com/aws/en/getting-started/high-level-architecture
  The classic compute plane runs in the customer cloud account, subscription or project; Databricks operates its separate control plane. This badge describes classic compute, not serverless compute in a Databricks-managed account. Review the selected workspace networking, region and service terms.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Databricks classic compute architecture (azure): https://learn.microsoft.com/en-us/azure/databricks/getting-started/high-level-architecture
  The classic compute plane runs in the customer cloud account, subscription or project; Databricks operates its separate control plane. This badge describes classic compute, not serverless compute in a Databricks-managed account. Review the selected workspace networking, region and service terms.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.

- Databricks classic compute architecture (gcp): https://docs.databricks.com/gcp/en/security/network/concepts/architecture
  The classic compute plane runs in the customer cloud account, subscription or project; Databricks operates its separate control plane. This badge describes classic compute, not serverless compute in a Databricks-managed account. Review the selected workspace networking, region and service terms.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- AWS architecture: https://docs.databricks.com/aws/en/getting-started/high-level-architecture

- Azure architecture: https://learn.microsoft.com/en-us/azure/databricks/getting-started/high-level-architecture

- Google Cloud architecture: https://docs.databricks.com/gcp/en/security/network/concepts/architecture

- Classic versus serverless compute: https://docs.databricks.com/aws/en/compute/use-compute

- Databricks upcoming behavior changes: https://docs.databricks.com/aws/en/release-notes/whats-coming

### Licensing sources

- https://docs.databricks.com/aws/en/getting-started/high-level-architecture

### Infrastructure sources

- https://docs.databricks.com/aws/en/compute/use-compute


### 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 AWS account/workspace login configuration supports SAML 2.0 or OpenID Connect. Unified-login and emergency-access settings must be planned for the account. Scope: Databricks AWS account/workspace identity; separate vendor-operated control plane. Source: https://docs.databricks.com/aws/en/security/auth/single-sign-on/ (reviewed 2026-11-14).

- SCIM provisioning: Edition-dependent. Account-level SCIM user/group provisioning is documented with Premium or above. Identity federation is required for workspace assignment; workspace-level provisioning is legacy. Scope: Databricks on AWS; Premium or above; not a statement about every cloud edition. Source: https://docs.databricks.com/aws/en/admin/users-groups/scim (reviewed 2026-11-16).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor-supported Terraform provider manages workspaces and administrative resources; AWS infrastructure is provisioned with the AWS provider. Databricks recommends Terraform for cloud/external resources and administrative actions, and Automation Bundles for jobs and pipelines. Select compatible provider versions and least-privilege credentials. Scope: Classic AWS workspace/infrastructure administration; serverless has a different boundary. Source: https://docs.databricks.com/aws/en/dev-tools/terraform/ (reviewed 2026-11-20). Deployment artifact: https://github.com/databricks/terraform-provider-databricks. Artifact reference: Pin Databricks and cloud provider versions.

- Minimum footprint / sizing: Sources checked — unresolved. The classic-compute guide requires selecting runtime, worker types, driver, autoscaling and policies for the workload. It does not establish one platform-wide CPU/RAM floor. Size the customer-account compute separately from Databricks-hosted control-plane and optional serverless services. Scope: Classic AWS compute sizing unresolved without workload and topology. Source: https://docs.databricks.com/aws/en/compute/configure (reviewed 2026-11-20).

- License pricing: Documented. Databricks publishes usage-based product pricing in DBUs with optional committed-use contracts. Rates depend on cloud, region, workload and product. Customer-account classic infrastructure can incur a separate cloud bill; obtain the selected product rate and contract rather than treating a starting DBU price as the whole deployment cost. Scope: Databricks commercial usage model; no workload-specific quote or total cost. Source: https://www.databricks.com/product/pricing (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## DataHub OSS

Open-source data catalog and metadata platform for discovery, lineage and governance.

- Listing: https://launchinyourcloud.com/directory/datahub/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0.
- Licensing model: open-source
- Installation: Official Helm deployment on EKS, AKS or GKE
- Architecture: Customer-operated application services with database, search, graph and event-stream dependencies
- Operations: Customer manages Kubernetes, stateful dependencies, networking, secrets, backups, scaling, ingestion, and upgrades, including search-backend compatibility and per-version breaking-change actions.
- Product website: https://datahub.com/
- Source review: 2026-11-19; cloud review: 2026-11-14; licensing review: 2026-11-14; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers DataHub OSS, not DataHub Cloud. Production deployments require careful operation of the metadata database, search index, event streaming and upgrade jobs; managed provider services can replace some in-cluster dependencies. DataHub v1.9.0 removes Elasticsearch 7.x support and requires Elasticsearch 8.x or OpenSearch 2.x/3.x. Metrics are enabled by default; set METRICS_ENABLED=false to disable them. The release requires CLI/Python SDK 1.7.0.19 and Helm chart 1.1.10, and operators should review all documented breaking changes before rollout. DataHub v1.9.1 rebuilds service images on OpenJDK 25.0.5.1 for CVE-2026-114938 and removes cached Wolfi layers that retained the earlier JDK. It also fixes OpenSearch 2.x semantic search with multiple OR groups. Preserve the v1.9.0 breaking-change, search-backend, CLI and Helm upgrade requirements when applying the patch.

DataHub OSS is Apache-2.0 licensed. DataHub Cloud and associated enterprise services use separate commercial terms.

DataHub uses persistent application services and stateful database, search and event-stream components. Provider-managed dependencies do not remove application operations. DataHub v1.9.0 supports Elasticsearch 8.x or OpenSearch 2.x/3.x; GMS will not start with Elasticsearch 7.x or OpenSearch compatibility mode reporting 7.10.2.


### Category fit

- data-analytics: Provides a metadata catalog, lineage graph, discovery and governance layer for connected data systems.

### Deployment boundaries


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

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

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


### Cloud deployment evidence

- DataHub on Amazon EKS (aws): https://docs.datahub.com/docs/deploy/aws
  The official guide deploys DataHub to a customer EKS cluster and describes optional AWS managed services for stateful dependencies.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- DataHub on Azure Kubernetes Service (azure): https://docs.datahub.com/docs/deploy/azure
  The official guide deploys DataHub to a customer AKS cluster and documents the required infrastructure and Helm installation.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- DataHub on Google Kubernetes Engine (gcp): https://docs.datahub.com/docs/deploy/gcp
  The official guide deploys DataHub to a customer GKE cluster with Helm and provider-managed dependency options.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.


### Community and maintenance

The project community profiles identify Zynga running a customized DataHub fork and Farm Credit Canada hardening a Kubernetes deployment. Public contributor history shows sustained work by multiple participants, and release 1.9.0 on November 16, 2026 documents active maintenance, security updates, and significant upgrade requirements. These profiles establish project use without treating DataHub Cloud customers as proof of OSS deployment.

Reviewed 2026-11-16.

- Reviewed maintenance release v1.9.0: https://github.com/datahub-project/datahub/releases/tag/v1.9.0

- Upstream contributor history: https://github.com/datahub-project/datahub/graphs/contributors

- Community profiles: Zynga fork and Farm Credit Canada deployment: https://datahub.com/community/champions/

### Sources

- Self-hosting on Kubernetes: https://docs.datahub.com/docs/deploy/kubernetes

- AWS deployment: https://docs.datahub.com/docs/deploy/aws

- Azure deployment: https://docs.datahub.com/docs/deploy/azure

- Google Cloud deployment: https://docs.datahub.com/docs/deploy/gcp

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

- DataHub v1.9.0 release and upgrade requirements: https://github.com/datahub-project/datahub/releases/tag/v1.9.0

- Upstream contributor history: https://github.com/datahub-project/datahub/graphs/contributors

- Community profiles: Zynga fork and Farm Credit Canada deployment: https://datahub.com/community/champions/

- DataHub v1.9.0 breaking changes: https://docs.datahub.com/docs/how/breaking-changes#v190

- DataHub v1.9.1 release: https://github.com/datahub-project/datahub/releases/tag/v1.9.1

### Licensing sources

- https://github.com/datahub-project/datahub/blob/master/LICENSE

### Infrastructure sources

- https://docs.datahub.com/docs/deploy/kubernetes

- https://github.com/datahub-project/datahub/releases/tag/v1.9.0

- https://docs.datahub.com/docs/how/breaking-changes#v190


### 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-managed React application supports OIDC identity providers such as Okta, Google and Keycloak through its authentication configuration. This is separate from DataHub Cloud login setup. Scope: DataHub self-managed frontend OIDC configuration. Source: https://docs.datahub.com/docs/authentication/guides/sso/configure-oidc-react (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. v1.9.1 rebuilds GMS, frontend, MAE/MCE consumer, upgrade and actions images on OpenJDK 25.0.5.1 to address CVE-2026-114938, and removes cached Wolfi layers that could retain the prior JDK. Upgrade every service image and restart. Scope: DataHub OSS service images from the v1.9.1 release and its v1.9.0 hotfix branch. Source: https://github.com/datahub-project/datahub/releases/tag/v1.9.1 (reviewed 2026-11-19).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official Helm repository provides separate DataHub and prerequisite charts, including external database, search and Kafka dependencies. The deployment guide includes example credentials that must be replaced. Pin compatible chart and application versions, and review whether to use managed or separately operated dependencies. Scope: Official Kubernetes Helm deployment. Source: https://docs.datahub.com/docs/deploy/kubernetes (reviewed 2026-11-20). Deployment artifact: https://github.com/acryldata/datahub-helm. Artifact reference: Select compatible chart and application releases.

- Minimum footprint / sizing: Documented. The Kubernetes guide requires more than 7 GB RAM for a local Minikube deployment including dependencies. This is not a production minimum: application services, database, Kafka, search and any graph service require separate resource and availability sizing. Scope: Local all-component deployment floor; production/HA capacity excluded. Source: https://docs.datahub.com/docs/deploy/kubernetes (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/datahub-project/datahub/master/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. DataHub v1.9.1 was published November 19, 2026. It rebuilds service images on OpenJDK 25.0.5.1 for CVE-2026-114938 and fixes OpenSearch 2.x semantic search with multiple OR groups. Retain the v1.9.0 Elasticsearch/OpenSearch, CLI, Helm and breaking-change requirements. Scope: Upstream DataHub OSS service images and hotfix branch; commercial editions and provider packages may differ. Source: https://github.com/datahub-project/datahub/releases/tag/v1.9.1 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/datahub-project/datahub/releases/tag/v1.9.0.




### Security and lifecycle reviews

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

- DataHub v1.9.1 OpenJDK security rebuild (security-advisory): DataHub v1.9.1 rebuilds service images on OpenJDK 25.0.5.1 for CVE-2026-114938 and removes cached Wolfi layers retaining the older JDK. Scope: DataHub OSS GMS, frontend, MAE/MCE consumer, upgrade and actions images; fixes were also cherry-picked to the v1.9.0 hotfix branch. Conditions: Affected image and CPU/JDK behavior determine exposure. Action: Deploy fixed images for every DataHub service and restart them while retaining the v1.9.0 upgrade prerequisites. Source: https://github.com/datahub-project/datahub/releases/tag/v1.9.1; reviewed 2026-11-19.




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







## Dremio Self-Managed

Self-managed distributed SQL and lakehouse analytics platform for customer-controlled data sources.

- Listing: https://launchinyourcloud.com/directory/dremio-self-managed/
- 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 Dremio Community; Dremio Enterprise uses separate commercial terms.
- Licensing model: open-source
- Installation: Community on Docker or Kubernetes; Enterprise on Kubernetes using vendor-tested EKS, AKS or GKE environments.
- Architecture: Customer-operated coordinator and executor services with metadata and distributed storage
- Operations: Customer manages Kubernetes or container capacity, storage, security, scaling, upgrades, backups and integration with data sources.
- Product website: https://www.dremio.com/
- Source review: 2026-11-17; cloud review: 2026-11-13; licensing review: 2026-11-13; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers Dremio Community and self-managed Enterprise, not Dremio Cloud. Community and Enterprise feature, support and billing differences must be reviewed separately. Query engines require network and credential access to configured data sources. Dremio Enterprise 26.1.13 removes compromised eMudhra certificate roots, updates Brotli for CVE-2026-111497, fixes incorrect or missing query results, and addresses rare file deletion after a network partition. Certificates chaining only to the removed roots will fail after upgrading. These fixes are specific to the Enterprise release.

Dremio Community is Apache-2.0 licensed; self-managed Dremio Enterprise is commercially licensed. This classification covers the platform family and requires edition-specific feature review.

The self-managed platform runs distributed coordinator and executor services in containers or Kubernetes, with persistent metadata and distributed storage. It is a server/container workload even when managed cloud storage is used. Dremio Enterprise 26.1.13 adds configurable startup and liveness probes for Kubernetes executors.


### Category fit

- data-analytics: Provides distributed SQL queries, semantic modeling and lakehouse analytics over customer-controlled data sources.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.dremio.com/editions/ (checked 2026-11-13). Source: https://docs.dremio.com/current/deploy-dremio/kubernetes-environments/ (checked 2026-11-13). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.dremio.com/editions/ (checked 2026-11-13). Source: https://docs.dremio.com/current/deploy-dremio/kubernetes-environments/ (checked 2026-11-13). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.dremio.com/editions/ (checked 2026-11-13). Source: https://docs.dremio.com/current/deploy-dremio/kubernetes-environments/ (checked 2026-11-13). 


### Cloud deployment evidence

- Dremio self-managed editions on AWS, Azure and Google Cloud (aws, azure, gcp): https://docs.dremio.com/editions/
  Dremio identifies Community and Enterprise as self-managed on AWS, Azure and Google Cloud. Community supports Docker or Kubernetes; Enterprise self-managed uses Kubernetes. This is distinct from the fully managed Dremio Cloud service.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Dremio-tested EKS, AKS and GKE environments (aws, azure, gcp): https://docs.dremio.com/current/deploy-dremio/kubernetes-environments/
  Dremio documents active testing against Amazon EKS, Azure AKS and Google GKE and provides provider recommendations. Customers operate the selected cluster and configure storage, identity and network access.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.


### Sources

- Dremio edition and deployment comparison: https://docs.dremio.com/editions/

- Vendor-tested Kubernetes environments: https://docs.dremio.com/current/deploy-dremio/kubernetes-environments/

- Dremio OSS Apache 2.0 license: https://github.com/dremio/dremio-oss/blob/master/LICENSE

- Dremio Enterprise 26.1.13 security and reliability fixes: https://docs.dremio.com/current/release-notes/version-260-release/#26113-november-2026-enterprise

### Licensing sources

- https://github.com/dremio/dremio-oss/blob/master/LICENSE

- https://docs.dremio.com/editions/

### Infrastructure sources

- https://docs.dremio.com/current/deploy-dremio/

- https://docs.dremio.com/current/deploy-dremio/kubernetes-environments/

- https://docs.dremio.com/current/release-notes/version-260-release/#26113-november-2026-enterprise


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. The current 26.x self-managed documentation marks OpenID Connect SSO as Enterprise. OIDC handles authentication; user and group memberships are provisioned separately through SCIM. Scope: Dremio self-managed Enterprise 26.x; not Community or Dremio Cloud. Source: https://docs.dremio.com/current/security/authentication/identity-providers/oidc/ (reviewed 2026-11-14).

- SCIM provisioning: Edition-dependent. Enterprise documents SCIM 2.0 user/group provisioning with header authentication. Identity-provider configuration and the customer-accessible SCIM endpoint are required. Scope: Dremio self-managed Enterprise 26.x. Source: https://docs.dremio.com/current/security/authentication/identity-providers/scim/ (reviewed 2026-11-14).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Current Dremio 26+ Kubernetes deployment uses the v3 OCI Helm chart at Quay; the older v2 chart is incompatible. Enterprise requires authorized registry access and a valid licence key. Configure chart values, object storage, cluster services and version compatibility before deployment. Scope: Official Dremio 26+ self-managed OCI Helm distribution. Source: https://docs.dremio.com/current/deploy-dremio/deploy-on-kubernetes/ (reviewed 2026-11-20). Deployment artifact: https://docs.dremio.com/current/deploy-dremio/deploy-on-kubernetes/. Artifact reference: oci://quay.io/dremio/dremio-helm; pin the selected v3 chart release.

- Minimum footprint / sizing: Documented. The current Kubernetes guide gives an 8-CPU/16-GB smallest production coordinator and executors with at least 64 GB memory. It recommends larger 32-CPU/64-GB coordinators and 128-GB executors. Catalog, search, messaging, storage and HA add substantial resources; these are component minima, not a complete cluster. Scope: Current self-managed Kubernetes component floors; topology and query workload additional. Source: https://docs.dremio.com/current/deploy-dremio/kubernetes-environments/ (reviewed 2026-11-20).

- License pricing: Documented. The vendor pricing page identifies Dremio Enterprise as self-hosted commercial software with pricing available from sales. Its displayed per-DCU Cloud price applies to the managed service, not this Enterprise licence. Agree capacity, term and support separately from the infrastructure bill. Scope: Self-managed Enterprise quote; managed Cloud rates excluded. Source: https://www.dremio.com/pricing/ (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.




### Security and lifecycle reviews

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

- Dremio Enterprise trust-store and Brotli update (security-advisory): Enterprise 26.1.13 removes compromised CA trust roots and patches the Brotli dependency in its Open Catalog service. Scope: Dremio Enterprise 26.1.13; this release does not establish the same fixes for Community Edition. Conditions: Services whose certificates chain only to the removed roots will fail validation. Brotli applicability depends on the affected component. Action: Review certificates and the linked bulletins, then apply the appropriate Enterprise patch and test connectivity. Source: https://docs.dremio.com/current/release-notes/version-260-release/#26113-november-2026-enterprise; reviewed 2026-11-17.




## Elastic Cloud Enterprise

Commercial self-managed orchestration platform for Elastic Stack deployments across customer cloud hosts.

- Listing: https://launchinyourcloud.com/directory/elastic-cloud-enterprise/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Elastic Cloud Enterprise license required after the trial.
- Licensing model: commercial-only
- Installation: Official ECE installation script on prepared AWS, Azure or Google Cloud Linux hosts
- Architecture: Multi-host orchestration layer with coordinators, proxies, allocators and managed Elasticsearch and Kibana deployments
- Operations: Customer manages cloud instances, Linux and container runtime compatibility, XFS storage, networking, DNS, certificates, host maintenance, capacity, backups, upgrades and licensing.
- Product website: https://www.elastic.co/cloud/cloud-enterprise
- Source review: 2026-11-19; cloud review: 2026-11-15; licensing review: 2026-11-15; infrastructure review: 2026-11-15

### Scope and qualifications

This entry covers Elastic Cloud Enterprise, not Elastic Cloud Hosted or Elastic Cloud Serverless. ECE requires supported Linux and container-engine combinations, dedicated storage planning and coordinated host maintenance; automatic cloud VM patching can disrupt the platform. Elastic Cloud Enterprise 3.8.6 and 4.2.1 fix seven platform-role, retained credential and CA key, cross-deployment symlink, role-token, and platform-setting issues. Certificate-rotation users must complete the documented cleanup after upgrade, and operators should review or revoke persistent role tokens. Elastic's CVE-2026-114938 advisory states Elasticsearch 7.17.3 and later can be affected on x86-64 AVX512_VBMI CPUs. Authenticated read access can permit RCE and unauthenticated access can cause denial of service. Planned ECE 4.2.2 and 3.8.7 were not yet released at review time; until fixed images are available, apply -XX:-UseBASE64Intrinsics, restart every deployment and follow Elastic's rollout guidance.

ECE starts with a 30-day trial and then requires a valid Elastic Cloud Enterprise orchestration license.

ECE uses multiple persistent Linux hosts for orchestration, proxies and workload allocators and then runs Elastic Stack clusters on those hosts.


### Category fit

- data-analytics: Orchestrates self-managed Elasticsearch and Kibana deployments for search, analytical and data-exploration workloads.

- databases-vector: Operates Elasticsearch clusters that provide document, full-text and vector search in customer infrastructure.

- observability: Operates Elastic Stack deployments used to ingest, search and analyze logs, metrics, traces and security telemetry.

### Deployment boundaries


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

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

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


### Cloud deployment evidence

- Elastic Cloud Enterprise on public cloud hosts (aws, azure, gcp): https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/install
  Elastic's current ECE installation guide explicitly supports public-cloud hosts on AWS, Google Cloud and Microsoft Azure and installs ECE on customer-prepared virtual machines.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.


### Sources

- Install Elastic Cloud Enterprise: https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/install

- Elastic Cloud Enterprise overview: https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise

- Manage an Elastic Cloud Enterprise license: https://www.elastic.co/docs/deploy-manage/license/manage-your-license-in-ece

- Elastic Cloud Enterprise release notes: https://www.elastic.co/docs/release-notes/cloud-enterprise

- Elastic Cloud Enterprise 4.2.1 security update ESA-2026-216: https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-216/391263

- Elastic Java4Shell advisory for ECE: https://discuss.elastic.co/t/java4shell-remote-code-execution-rce-vulnerability-cve-2026-114938/391703

### Licensing sources

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

### Infrastructure sources

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


### 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. ECE supports SAML 2.0 Web Browser SSO for the orchestrator/Cloud UI, with attribute and role mappings. It does not apply to ordinary API clients or automatically configure every hosted Elasticsearch/Kibana deployment; those access policies are separate. Scope: Self-managed ECE orchestrator browser federation. Source: https://www.elastic.co/docs/deploy-manage/users-roles/cloud-enterprise-orchestrator/saml (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: ESA-2026-211, 212, 215, 216, 218, 221, and 222 cover credential escalation, retained certificate credentials and CA keys, cross-deployment access through symlinks, role-token exposure, and platform-setting authorization. Upgrade to 3.8.6, 4.2.1, or later; perform certificate cleanup where required; and review or revoke persistent role tokens. Current review: CVE-2026-114938 can affect Elasticsearch 7.17.3 and later on x86-64 AVX512_VBMI CPUs. Authenticated read access can permit RCE and unauthenticated access can cause denial of service. Elastic planned ECE 4.2.2 and 3.8.7 but had not released them when reviewed. Use -XX:-UseBASE64Intrinsics, restart every deployment and follow the vendor advisory until fixed ECE images are available. Scope: ECE-hosted Elasticsearch deployments on affected x86-64 AVX512_VBMI hardware; planned ECE versions are not recorded as released. Source: https://discuss.elastic.co/t/java4shell-remote-code-execution-rce-vulnerability-cve-2026-114938/391703 (reviewed 2026-11-19). Supporting source: Prior security-controls source — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-216/391263. Supporting source: ESA-2026-211 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-211/391260. Supporting source: ESA-2026-212 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-212/391261. Supporting source: ESA-2026-215 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-215/391262. Supporting source: ESA-2026-218 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-218/391264. Supporting source: ESA-2026-221 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-221/391265. Supporting source: ESA-2026-222 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-4-2-1-security-update-esa-2026-222/391266.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. ECE installation prepares supported Linux hosts, Docker or Podman, XFS quotas and mount points before installing the orchestrator. Follow the supported OS/container-engine matrix and deployment-specific prerequisites; generic cloud VMs alone are insufficient. Scope: Elastic Cloud Enterprise installation guide; orchestrator hosts, not Elastic Cloud Hosted. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/install (reviewed 2026-11-16).

- Minimum footprint / sizing: Documented. ECE lists an 8-GB installation floor per host role, but recommends 128–256 GB for allocator hosts and distinct control/proxy sizing. HA needs at least three hosts across three availability zones. Fast SSDs, deployment memory/storage ratios and cluster workloads materially affect the footprint; the installer floor is not production capacity. Scope: ECE host-role requirements; hosted deployment capacity and HA additional. Source: https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/ece-hardware-prereq (reviewed 2026-11-20).

- License pricing: Documented. ECE requires an Elastic-issued licence; installation activates a 30-day trial. A full ECE licence enables managed deployments at the stated Enterprise subscription feature/support level for their stack version. The page does not quote a price; obtain ECE terms separately from hosted Elastic Cloud rates and infrastructure. Scope: Commercial ECE platform/deployment licensing; numeric price requires a quote. Source: https://www.elastic.co/docs/deploy-manage/license/manage-your-license-in-ece (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Elastic Cloud Enterprise 4.2.1 was released October 20, 2026; 3.8.6 is the parallel fixed release for that maintained line. The updates address multiple platform-role, credential, certificate, token, and cross-deployment issues. Scope: Elastic Cloud Enterprise 3.8 and 4.2 maintained lines. Source: https://www.elastic.co/docs/release-notes/cloud-enterprise (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- Elastic Cloud Enterprise 3.8.6 and 4.2.1 security update (security-advisory): ESA-2026-211, 212, 215, 216, 218, 221, and 222 cover credential escalation, retained certificate credentials and CA keys, cross-deployment access through symlinks, role-token exposure, and platform-setting authorization. Scope: Most issues affect releases through 3.8.5 and 4.2.0. ESA-2026-222 affects 4.1.0 through 4.2.0 when Enterprise Search is present. Fixed releases are 3.8.6 and 4.2.1. Conditions: Several issues require particular platform roles, certificate rotation, persistent tokens, symlink paths, or Enterprise Search. Multiple advisories have no workaround. Action: Upgrade to 3.8.6, 4.2.1, or later; perform certificate cleanup where required; and review or revoke persistent role tokens. Source: https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-216/391263; reviewed 2026-11-18. Supporting source: ESA-2026-211 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-211/391260. Supporting source: ESA-2026-212 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-212/391261. Supporting source: ESA-2026-215 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-215/391262. Supporting source: ESA-2026-218 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-218/391264. Supporting source: ESA-2026-221 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-221/391265. Supporting source: ESA-2026-222 — https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-4-2-1-security-update-esa-2026-222/391266.

- Elastic Cloud Enterprise CVE-2026-114938 guidance (security-advisory): Elastic says affected Elasticsearch on x86-64 AVX512_VBMI CPUs can permit authenticated RCE and unauthenticated denial of service. Scope: ECE-hosted Elasticsearch 7.17.3 and later on affected hardware; planned ECE 4.2.2 and 3.8.7 were not yet released when reviewed. Conditions: CPU features, JDK and deployed Elasticsearch version determine exposure. Action: Apply -XX:-UseBASE64Intrinsics, restart every deployment and follow Elastic's advisory until fixed ECE images are released and deployed. Source: https://discuss.elastic.co/t/java4shell-remote-code-execution-rce-vulnerability-cve-2026-114938/391703; reviewed 2026-11-19.




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




## Esri ArcGIS Enterprise (BYOL)

Commercial customer-operated geospatial application and analytics platform.

- Listing: https://launchinyourcloud.com/directory/esri-arcgis-enterprise/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- 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: VM image
- Architecture: ArcGIS Enterprise Cloud Builder application deployments and licensed server components on AWS or Azure VMs.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://doc.esri.com/en/arcgis-enterprise-cloud-tools/latest/amazon/arcgis-enterprise-cloud-builder-for-aws.html
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Cloud Builder uses the customer's account/subscription and software licences. Geospatial analysis and environmental mapping do not establish a packaged environmental permits, filings or compliance-record workflow.

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

ArcGIS Enterprise Cloud Builder application deployments and licensed server components on AWS or Azure VMs. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- data-analytics: Commercial customer-operated geospatial application and analytics platform.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://doc.esri.com/en/arcgis-enterprise-cloud-tools/latest/amazon/arcgis-enterprise-cloud-builder-for-aws.html (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://doc.esri.com/en/arcgis-enterprise-cloud-tools/latest/azure/overview-arcgis-server-on-microsoft-azure.html (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Cloud Builder (aws): https://doc.esri.com/en/arcgis-enterprise-cloud-tools/latest/amazon/arcgis-enterprise-cloud-builder-for-aws.html
  ArcGIS Enterprise Cloud Builder application deployments and licensed server components on AWS or Azure VMs. Cloud Builder uses the customer's account/subscription and software licences. Geospatial analysis and environmental mapping do not establish a packaged environmental permits, filings or compliance-record workflow.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Cloud Builder (azure): https://doc.esri.com/en/arcgis-enterprise-cloud-tools/latest/azure/overview-arcgis-server-on-microsoft-azure.html
  ArcGIS Enterprise Cloud Builder application deployments and licensed server components on AWS or Azure VMs. Cloud Builder uses the customer's account/subscription and software licences. Geospatial analysis and environmental mapping do not establish a packaged environmental permits, filings or compliance-record workflow.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS Cloud Builder: https://doc.esri.com/en/arcgis-enterprise-cloud-tools/latest/amazon/arcgis-enterprise-cloud-builder-for-aws.html

- Azure Cloud Builder: https://doc.esri.com/en/arcgis-enterprise-cloud-tools/latest/azure/overview-arcgis-server-on-microsoft-azure.html

- Esri Master Agreement: https://www.esri.com/en-us/legal/terms/full-master-agreement

- Product Lifecycle: https://support.esri.com/en-us/products/arcgis-enterprise/life-cycle

### Licensing sources

- https://www.esri.com/en-us/legal/terms/full-master-agreement

### Infrastructure sources

- https://doc.esri.com/en/arcgis-enterprise-cloud-tools/latest/amazon/arcgis-enterprise-cloud-builder-for-aws.html

- https://doc.esri.com/en/arcgis-enterprise-cloud-tools/latest/azure/overview-arcgis-server-on-microsoft-azure.html


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Esri documents portal identities backed by organisational stores including SAML providers, with role/group permissions and federated ArcGIS Server access. Configure the actual portal/IdP and supported release. Cloud-provider IAM and ArcGIS Online accounts are distinct from the self-managed portal identity design. Scope: ArcGIS Enterprise 12.0 self-managed portal identity model. Source: https://enterprise.arcgis.com/en/get-started/12.0/windows/the-arcgis-enterprise-security-model.htm (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Esri Cloud Builder for AWS provisions a selected ArcGIS Enterprise deployment using customer licences and cloud configuration. Select compatible cloud-tool/product versions, certificates, networking and storage; supported base deployment, specialised roles and HA require separate design. Scope: Esri AWS Cloud Builder application/infrastructure delivery; licensed components and topology selection. Source: https://doc.esri.com/en/arcgis-enterprise-cloud-tools/latest/amazon/arcgis-enterprise-cloud-builder-for-aws.html (reviewed 2026-11-21). Deployment artifact: https://doc.esri.com/en/arcgis-enterprise-cloud-tools/latest/amazon/arcgis-enterprise-cloud-builder-for-aws.html. Artifact reference: Current Esri AWS Cloud Builder guide reviewed on this date.

- Minimum footprint / sizing: Sources checked — unresolved. The accessible Cloud Builder guidance establishes deployment tooling but not complete workload-sized CPU/RAM/storage for Portal, Server and Data Store roles. Legacy requirement URLs redirect to moved documentation; obtain the selected release component requirements and GIS workload/HA plan rather than applying an old all-in-one development example. Scope: ArcGIS Enterprise complete current production sizing remains unconfirmed. Source: https://doc.esri.com/en/arcgis-enterprise-cloud-tools/latest/amazon/arcgis-enterprise-cloud-builder-for-aws.html (reviewed 2026-11-21).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Esri ArcGIS Enterprise (BYOL); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.esri.com/en-us/legal/terms/full-master-agreement (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Estuary BYOC

Managed data capture, transformation, and delivery with a dedicated data plane in the customer's cloud account.

- Listing: https://launchinyourcloud.com/directory/estuary-byoc/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Vendor-operated BYOC
- Infrastructure IDs: servers
- License: Commercial BYOC under an annual Enterprise agreement with custom pricing.
- Licensing model: commercial-only
- Installation: Arrange Enterprise BYOC onboarding and grant the documented permissions in a separate AWS account, Azure subscription, or Google Cloud project.
- Architecture: Dedicated customer-cloud instances run task brokers and reactors. Estuary's control plane starts connectors and applies task configurations.
- Operations: Estuary provisions and manages data-plane resources, including patching, scaling, and deletion. The customer owns the cloud environment and manages its surrounding firewall, routing, and policies.
- Product website: https://estuary.dev/
- Source review: 2026-11-21; cloud review: 2026-11-21; licensing review: 2026-11-21; infrastructure review: 2026-11-21

### Scope and qualifications

The data plane accepts connections from Estuary's control plane and authorized users. Pipeline specifications can be pulled with flowctl. Confirm storage export and account teardown with Estuary.

Commercial BYOC under an annual Enterprise agreement with custom pricing.

Dedicated customer-cloud instances run task brokers and reactors. Estuary's control plane starts connectors and applies task configurations.


### Category fit

- data-analytics: Captures, transforms, and delivers data to analytical destinations through managed connectors.

### Deployment boundaries


- aws: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://docs.estuary.dev/private-byoc/byoc-deployments/aws-byoc/ (checked 2026-11-21). 

- azure: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://docs.estuary.dev/private-byoc/byoc-deployments/azure-byoc/ (checked 2026-11-21). 

- gcp: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://docs.estuary.dev/private-byoc/byoc-deployments/gcp-byoc/ (checked 2026-11-21). 

Operating responsibility: Estuary provisions, patches, scales and removes the customer-account data plane. Its vendor-operated control plane starts connectors and applies task configuration; the customer governs the surrounding cloud account, permissions and network policies. Source: https://docs.estuary.dev/private-byoc/byoc-deployments/ (checked 2026-11-21). Supporting source: Control-plane and management connectivity — https://docs.estuary.dev/private-byoc/networking/.


### Cloud deployment evidence

- Estuary BYOC on AWS (aws): https://docs.estuary.dev/private-byoc/byoc-deployments/aws-byoc/
  The documented cross-account IAM role uses an external ID and grants AmazonEC2FullAccess.
  Source type: vendor-documentation; reviewed: 2026-11-21; vendor support: not-assessed.

- Estuary BYOC on Azure (azure): https://docs.estuary.dev/private-byoc/byoc-deployments/azure-byoc/
  The guide adds Estuary's deployment application and grants a role scoped to the customer's subscription.
  Source type: vendor-documentation; reviewed: 2026-11-21; vendor support: not-assessed.

- Estuary BYOC on Google Cloud (gcp): https://docs.estuary.dev/private-byoc/byoc-deployments/gcp-byoc/
  The guide asks for project-level Editor access for Estuary's controller principal.
  Source type: vendor-documentation; reviewed: 2026-11-21; vendor support: not-assessed.


### Sources

- BYOC operating model: https://docs.estuary.dev/private-byoc/byoc-deployments/

- Data-plane network requirements: https://docs.estuary.dev/private-byoc/networking/

- Enterprise BYOC pricing: https://docs.estuary.dev/getting-started/pricing/

- Pull published specifications: https://docs.estuary.dev/guides/flowctl/edit-specification-locally/

- Estuary BYOC on AWS: https://docs.estuary.dev/private-byoc/byoc-deployments/aws-byoc/

- Estuary BYOC on Azure: https://docs.estuary.dev/private-byoc/byoc-deployments/azure-byoc/

- Estuary BYOC on Google Cloud: https://docs.estuary.dev/private-byoc/byoc-deployments/gcp-byoc/

### Licensing sources

- https://docs.estuary.dev/getting-started/pricing/

### Infrastructure sources

- https://docs.estuary.dev/private-byoc/networking/


### 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: Documented. Enterprise plans, including BYOC, include SSO. Estuary documents support-assisted SAML 2.0 configuration for its hosted dashboard, with domain metadata and just-in-time account creation. This is control-plane user identity, separate from connector credentials and data-plane authentication. Scope: Enterprise BYOC dashboard SSO; coordinate domain and IdP configuration with Estuary.. Source: https://docs.estuary.dev/getting-started/sso-setup/ (reviewed 2026-11-21). Supporting source: Enterprise BYOC and SSO entitlement — https://docs.estuary.dev/getting-started/pricing/.

- SCIM provisioning: Explicitly unsupported. Estuary explicitly documents just-in-time SSO account creation rather than SCIM. Tenant administrators invite users and assign access after the SSO account is created. SAML support does not establish SCIM lifecycle provisioning. Scope: Documented Estuary dashboard provisioning flow for Enterprise BYOC.. Source: https://docs.estuary.dev/getting-started/sso-setup/ (reviewed 2026-11-21).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. The provider guides document permissions and vendor-assisted provisioning. The AWS example creates a delegated IAM role with an external ID and AmazonEC2FullAccess; it does not expose a reviewed, versioned data-plane deployment template. Obtain the actual provisioning artifact, permission scope and rollback procedure from Estuary. An IAM policy example alone does not establish a reusable runtime installer. Scope: Estuary-managed BYOC runtime deployment artifact unresolved.. Source: https://docs.estuary.dev/private-byoc/byoc-deployments/aws-byoc/ (reviewed 2026-11-21). Supporting source: Azure onboarding permissions — https://docs.estuary.dev/private-byoc/byoc-deployments/azure-byoc/. Supporting source: Google Cloud onboarding permissions — https://docs.estuary.dev/private-byoc/byoc-deployments/gcp-byoc/.

- Minimum footprint / sizing: Sources checked — unresolved. The networking guide identifies broker/reactor instances, coordination and management access, but does not publish a quantitative CPU/RAM/storage baseline or HA topology. Estuary sizes the managed data plane during onboarding. Obtain connector counts, data rates, retention, replay and recovery requirements before selecting resources; 100 users and 1 TB alone do not size a streaming pipeline. Scope: Dedicated Enterprise BYOC data plane; quantitative production sizing unresolved.. Source: https://docs.estuary.dev/private-byoc/networking/ (reviewed 2026-11-21).

- License pricing: Documented. BYOC is available on annual or multi-year Enterprise contracts with custom pricing based on data volume, connector instances, deployment model, term and support. The customer pays the cloud provider directly for infrastructure. Public Cloud-plan per-GB/task-hour examples do not quote the BYOC contract. Scope: Enterprise managed BYOC commercial terms and separate cloud bill; request a quote.. Source: https://docs.estuary.dev/getting-started/pricing/ (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Finmars CE (Community Edition)

Open-source investment accounting, portfolio data and reporting software.

- Listing: https://launchinyourcloud.com/directory/finmars-ce/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: EUPL-1.2 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: VM image; Docker / Compose
- Architecture: Finmars CE application services in the vendor's customer EC2 image or documented installation.
- 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://finmars.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The reviewed AWS offer has no software licence charge; infrastructure still costs money. Portfolio analytics and accounting are not a complete private-equity investor or portfolio-company workflow suite. Keep backend, UI and provider-package versions separate.

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

Finmars CE application services in the vendor's customer EC2 image or documented installation. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- pe-portfolio-operations: Open-source investment accounting, portfolio data and reporting software.

- data-analytics: Open-source investment accounting, portfolio data and reporting software.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://aws.amazon.com/marketplace/pp/prodview-55ptwgyybwzp2 (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.finmars.com/books/installation-guide-with-azure-advanced/page/install-finmars-platform (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Marketplace (aws): https://aws.amazon.com/marketplace/pp/prodview-55ptwgyybwzp2
  Finmars CE application services in the vendor's customer EC2 image or documented installation. The reviewed AWS offer has no software licence charge; infrastructure still costs money. Portfolio analytics and accounting are not a complete private-equity investor or portfolio-company workflow suite. Keep backend, UI and provider-package versions separate.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.

- Install Finmars Platform | Finmars (azure): https://docs.finmars.com/books/installation-guide-with-azure-advanced/page/install-finmars-platform
  Finmars CE application services in the vendor's customer EC2 image or documented installation. The reviewed AWS offer has no software licence charge; infrastructure still costs money. Portfolio analytics and accounting are not a complete private-equity investor or portfolio-company workflow suite. Keep backend, UI and provider-package versions separate.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes falendary, sokolovdp, paktusov, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/finmars-platform/finmars-core/graphs/contributors

- Upstream project: https://github.com/finmars-platform/finmars-core

### Sources

- AWS Marketplace: https://aws.amazon.com/marketplace/pp/prodview-55ptwgyybwzp2

- Install Finmars Platform | Finmars: https://docs.finmars.com/books/installation-guide-with-azure-advanced/page/install-finmars-platform

- AWS Guide: https://docs.finmars.com/books/installation-guide-with-aws-simple

- Azure Guide: https://docs.finmars.com/books/installation-guide-with-azure-advanced

- EUPL-1.2: https://github.com/finmars-platform/finmars-core/blob/main/LICENSE.md

- Commits: https://github.com/finmars-platform/finmars-core/commits/main

### Licensing sources

- https://github.com/finmars-platform/finmars-core/blob/main/LICENSE.md

### Infrastructure sources

- https://aws.amazon.com/marketplace/pp/prodview-55ptwgyybwzp2

- https://docs.finmars.com/books/installation-guide-with-azure-advanced/page/install-finmars-platform


### 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: Documented. The reviewed AWS offer delivers Amazon Machine Image (AMI) from Finmars. Its package version is 1.23.0; verify the contained application and required entitlements separately. Scope: Finmars CE (Community Edition) selected AWS public offer; infrastructure and support charges are separate. Source: https://aws.amazon.com/marketplace/pp/prodview-55ptwgyybwzp2 (reviewed 2026-11-19). Offer prodview-55ptwgyybwzp2: Finmars; Amazon Machine Image (AMI); package 1.23.0; https://aws.amazon.com/marketplace/pp/prodview-55ptwgyybwzp2.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The CE installation guide initialises a bundled Keycloak realm and explicitly describes Login redirecting to the deployment authentication host and back to the Finmars dashboard. Configure domains, certificates, realm/users and secrets. External enterprise IdP brokering is a separate requirement, not automatically established by the bundled SSO flow. Scope: Finmars Community Edition documented bundled-Keycloak application-user SSO. Source: https://docs.finmars.com/books/installation-guide-with-azure-advanced/page/install-finmars-platform (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor CE guide clones the community-edition deployment repository, generates environment settings, initialises certificates/Keycloak, runs migrations and starts Docker services. Replace examples and pin compatible releases; the guide does not make every independently versioned core/frontend/image current automatically. Scope: Finmars Community Edition vendor Docker/Make installation; application and deployment versions separate. Source: https://docs.finmars.com/books/installation-guide-with-azure-advanced/page/install-finmars-platform (reviewed 2026-11-21). Deployment artifact: https://github.com/finmars-platform/finmars-community-edition. Artifact reference: Current vendor CE installation workflow reviewed on this date.

- Minimum footprint / sizing: Documented. The Azure guide chooses a B2ms Ubuntu 24.04 VM with 2 vCPU/8 GiB RAM and a 256-GiB Premium SSD OS volume. This is an installation-example host, not a measured minimum or HA recommendation; finance data, database, Keycloak, workers, storage and backups need workload validation. Scope: Finmars CE vendor Azure VM installation example, not workload/HA capacity. Source: https://docs.finmars.com/books/installation-guide-with-azure-advanced/page/create-virtual-machine (reviewed 2026-11-21).

- License pricing: Documented. EUPL-1.2 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Finmars CE (Community Edition); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/finmars-platform/finmars-core/blob/main/LICENSE.md (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream 1.22.3-stable release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Finmars CE (Community Edition) upstream application; verify compatibility with the selected package. Source: https://github.com/finmars-platform/finmars-core/releases/tag/1.22.3-stable (reviewed 2026-11-19).







## Gen3 (Data Commons Platform)

Open-source governed research-data commons with controlled-access request and authorization services.

- Listing: https://launchinyourcloud.com/directory/gen3/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Terraform; Helm / Kubernetes operator; Kubernetes manifests
- Architecture: Gen3 Terraform/Helm services on EKS with PostgreSQL, object storage, authentication and authorization services.
- 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://github.com/uc-cdis/gen3-terraform
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Research administration here means controlled data-access requests and approvals, not sponsored-award accounting. Component/chart tags are separate releases; a single workflow-chart tag is not the version of the complete commons.

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

Gen3 Terraform/Helm services on EKS with PostgreSQL, object storage, authentication and authorization services. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- data-analytics: Open-source governed research-data commons with controlled-access request and authorization services.

- research-grant-administration: Open-source governed research-data commons with controlled-access request and authorization services.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.gen3.org/gen3-resources/operator-guide/iac-terraform/ (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Terraform Guide (aws): https://docs.gen3.org/gen3-resources/operator-guide/iac-terraform/
  Gen3 Terraform/Helm services on EKS with PostgreSQL, object storage, authentication and authorization services. Research administration here means controlled data-access requests and approvals, not sponsored-award accounting. Component/chart tags are separate releases; a single workflow-chart tag is not the version of the complete commons.
  Source type: institution-deployment; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes emalinowski, AidanHilt, EliseCastle23, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/uc-cdis/gen3-terraform/graphs/contributors

- Upstream project: https://github.com/uc-cdis/gen3-terraform

### Sources

- AWS Terraform Guide: https://docs.gen3.org/gen3-resources/operator-guide/iac-terraform/

- AWS Commons TF: https://raw.githubusercontent.com/uc-cdis/gen3-terraform/master/tf_files/aws/commons/README.md

- AWS Prod Guide: https://docs.gen3.org/gen3-resources/operator-guide/helm/helm-deploy-production-example/

- Data AuthZ: https://docs.gen3.org/gen3-resources/operator-guide/authorization/

- Apache-2.0: https://raw.githubusercontent.com/uc-cdis/gen3-terraform/master/LICENSE

- Gen3 Helm Releases: https://github.com/uc-cdis/gen3-helm/releases

- Terraform Commits: https://github.com/uc-cdis/gen3-terraform/commits/master

### Licensing sources

- https://raw.githubusercontent.com/uc-cdis/gen3-terraform/master/LICENSE

### Infrastructure sources

- https://docs.gen3.org/gen3-resources/operator-guide/iac-terraform/


### 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. Gen3 documents Fence-based identity configuration and supported organisational/social methods including Google, Microsoft and research federations. Provider membership, client registration and user synchronisation require deployment configuration. Authentication is distinct from Arborist/data authorisation and development mock access. Scope: Gen3 configured commons-user identity; provider affiliation and data permissions separate. Source: https://docs.gen3.org/gen3-resources/operator-guide/gen3-authn-methods/ (reviewed 2026-11-21). Supporting source: Helm identity configuration — https://docs.gen3.org/gen3-resources/operator-guide/helm/helm-config/helm-config-auth/.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The reviewed source supplies deployment configuration for Gen3 Terraform/Helm services on EKS with PostgreSQL, object storage, authentication and authorization services. Set organization-specific secrets, networking, storage and compatible image versions before use. Scope: Reviewed deployment source collection; application images and infrastructure components have separate versions. Source: https://raw.githubusercontent.com/uc-cdis/gen3-terraform/master/tf_files/aws/commons/README.md (reviewed 2026-11-19). Deployment artifact: https://github.com/uc-cdis/gen3-terraform/tree/master/tf_files/aws/commons. Artifact reference: master (moving branch).

- Minimum footprint / sizing: Sources checked — unresolved. The prerequisites and production deployment guide require Kubernetes and workload-appropriate CPU/RAM/storage but do not establish one complete numeric minimum for the selected commons. Databases, indexes, workspaces, data volume, processing concurrency and availability must be sized together. Scope: Gen3 complete production commons footprint remains unconfirmed. Source: https://docs.gen3.org/gen3-resources/operator-guide/prerequisites/ (reviewed 2026-11-21).

- License pricing: Documented. Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Gen3 (Data Commons Platform); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/uc-cdis/gen3-terraform/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## IBM Cognos Analytics Certified Containers

Customer-managed enterprise reporting and analytics deployed by Helm to a Kubernetes cluster in the customer's cloud.

- Listing: https://launchinyourcloud.com/directory/ibm-cognos-analytics-certified-containers/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, ibm
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial, separately licensed Cognos Analytics Certified Containers entitlement.
- Licensing model: commercial-only
- Installation: Install IBM's entitled Cognos Analytics Helm chart on customer-managed Kubernetes
- Architecture: Customer-operated Kubernetes cluster running IBM Cognos containers with external databases, authentication, storage and ingress.
- Operations: Customer manages Kubernetes, databases, authentication, storage, ingress, capacity, backups and upgrades; IBM support scope varies by platform.
- Product website: https://www.ibm.com/products/cognos-analytics
- 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 Cognos Analytics Certified Containers, not IBM-hosted or on-demand Cognos offerings. Installation requires an IBM entitlement key and registry access. Support on EKS, AKS, GKE and other non-OpenShift platforms is narrower than on Red Hat OpenShift and is focused on the Cognos software, certified images, Helm orchestration, deployment and updates.

Certified Containers are a separately licensed IBM product. Installation retrieves entitled images and Helm artifacts with an IBM entitlement key.

The product runs as persistent containerized services on a customer Kubernetes cluster and requires external stateful services, ingress and production capacity planning.


### Category fit

- data-analytics: Enterprise reporting, dashboards, governed analytics and data exploration delivered by customer-managed Cognos containers.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=overview-support-policy-container-delivery-models (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=overview-support-policy-container-delivery-models (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=overview-support-policy-container-delivery-models (checked 2026-11-17). 

- ibm: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=files-ingress-cognos-analytics-framework-configuration (checked 2026-11-17). 


### Cloud deployment evidence

- Cognos Certified Containers on EKS, AKS and GKE (aws, azure, gcp): https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=overview-support-policy-container-delivery-models
  IBM documents the certified Cognos containers on Amazon EKS, Microsoft AKS and Google GKE. Non-OpenShift support is narrower than the OpenShift delivery model.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- Cognos Certified Containers on IBM Cloud Kubernetes Service (ibm): https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=files-ingress-cognos-analytics-framework-configuration
  IBM's Cognos ingress framework explicitly names IBM Cloud Kubernetes Service alongside EKS, AKS and GKE. The customer operates the cluster and external dependencies.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Cognos Analytics offerings: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=cognos-analytics-offerings

- Certified Containers overview: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=containers-overview

- Container delivery support policy: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=overview-support-policy-container-delivery-models

- Ingress configuration for named Kubernetes services: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=files-ingress-cognos-analytics-framework-configuration

- Installing and deploying Certified Containers: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers

### Licensing sources

- https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=cognos-analytics-offerings

- https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers

### Infrastructure sources

- https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=containers-overview

- https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers


### 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. Entitled registry images and Helm installation are documented; a current Marketplace offer for this Certified Containers edition was not established. Cognos hosted offerings are separate. Scope: Reviewed public evidence for IBM Cognos Analytics Certified Containers; unresolved within this edition/deployment. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Container entitlement and registry access do not establish qualifying Marketplace spend or contract-specific cloud credit eligibility. Scope: Reviewed public evidence for IBM Cognos Analytics Certified Containers; unresolved within this edition/deployment. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers (reviewed 2026-11-17).

- Single sign-on: Documented. Cognos 12.1.x documents dynamic OpenID Connect namespaces with a configured supported IdP and administrative capabilities. Confirm the namespace/provider settings for the selected container deployment. Scope: Cognos 12.1.x identity configuration; not a Cloud-only entitlement. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=providers-creating-dynamic-namespace-in-manage-component (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. The reviewed 12.1.x namespace guide supports LDAP/OIDC providers, but does not establish a Certified Containers SCIM endpoint and lifecycle operations. Scope: Reviewed public evidence for IBM Cognos Analytics Certified Containers; unresolved within this edition/deployment. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=providers-creating-dynamic-namespace-in-manage-component (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed IBM Cognos Analytics Certified Containers 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.ibm.com/support/pages/node/7250395 (reviewed 2026-11-17).

- Security controls: Documented. IBM bulletin 7250395 identifies Certified Containers 12.1.0 vulnerabilities and names 12.1.1 as the fix. Check the deployed container release against current bulletins; this historical fix is not a claim that newer releases have no vulnerabilities. Scope: Certified Containers 12.1.0-specific security bulletin; historical affected/fixed scope. Source: https://www.ibm.com/support/pages/node/7250395 (reviewed 2026-11-17).

- Air-gapped operation: Sources checked — unresolved. Registry entitlement and Helm deployment alone do not establish the complete offline image, licence, dependency and update workflow for Certified Containers. Scope: Reviewed public evidence for IBM Cognos Analytics Certified Containers; unresolved within this edition/deployment. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. IBM supplies entitled container images and Helm deployment for Certified Containers. Obtain the registry entitlement and configure ingress, persistent storage and the selected cluster; OpenShift and other Kubernetes platforms have different support boundaries. Scope: Cognos Analytics 12.1.x Certified Containers. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers (reviewed 2026-11-17).

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed container installation requires cluster, storage and deployment configuration, but did not establish a complete numerical HA sizing model for 100 users/1 TB, including reporting concurrency and auxiliary services. Scope: Certified Containers sizing; desktop/agent-only requirements excluded. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers (reviewed 2026-11-17).

- License pricing: Documented. Certified Containers are a separately licensed IBM product. Installation retrieves entitled images and Helm artifacts with an IBM entitlement key. Scope: IBM Cognos Analytics Certified Containers: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=cognos-analytics-offerings (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Obtain the current entitled container bundle, report concurrency, HA services, content-store database, storage and licence metric. User count and data volume do not size reporting/AI dependencies. 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://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers (reviewed 2026-11-17).

- Release snapshot / cadence: Sources checked — unresolved. IBM identifies container release-specific fixes, including 12.1.0 to 12.1.1 remediation, but the reviewed public records did not establish the latest entitled container/chart bundle and publication date. Scope: Reviewed public evidence for IBM Cognos Analytics Certified Containers; unresolved within this edition/deployment. Source: https://www.ibm.com/support/pages/node/7250395 (reviewed 2026-11-17).




### Security and lifecycle reviews

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

- Cognos Certified Containers 12.1.0 fixes available (security-advisory): IBM bulletin 7250395 identifies PostgreSQL JDBC and information-disclosure vulnerabilities in Certified Containers 12.1.0, with 12.1.1 named as the fix. Scope: IBM bulletin published 2025-11-07 for Certified Containers 12.1.0; not a claim that every newer Cognos release or deployment is affected. Conditions: Exposure depends on the affected components and CVE-specific prerequisites in the bulletin. The reviewed record does not establish the current entitled container bundle. Action: Check the installed container version and current IBM bulletins. For affected 12.1.0 deployments, obtain the designated fixed or later supported bundle and follow the vendor upgrade procedure. Source: https://www.ibm.com/support/pages/node/7250395; reviewed 2026-11-17.




## IBM Planning Analytics Cartridge

Licensed self-managed planning, budgeting and multidimensional analytics cartridge.

- Listing: https://launchinyourcloud.com/directory/ibm-planning-analytics/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: ibm, 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: Kubernetes manifests
- Architecture: Planning Analytics cartridge on IBM Software Hub and a supported customer OpenShift cluster with persistent TM1 and Workspace storage.
- 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://github.com/ibm-cloud-docs/cloud-pak-data
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Current Software Hub 5.4 guidance provides an application-specific install-components workflow and explicitly supports IBM Cloud, AWS, Azure and Google Cloud platform installations. Keep the platform/cartridge release aligned and verify permitted storage. The older Azure PDF is historical background; Local, SaaS, TM1 and cartridge versions and licences are separate.

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

Planning Analytics cartridge on IBM Software Hub and a supported customer OpenShift cluster with persistent TM1 and Workspace storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- data-analytics: Licensed self-managed planning, budgeting and multidimensional analytics cartridge.

### Deployment boundaries


- ibm: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing (checked 2026-11-19). 

- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing (checked 2026-11-19). 


### Cloud deployment evidence

- Application deployment guidance (ibm, aws, azure, gcp): https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing
  Planning Analytics cartridge on IBM Software Hub and a supported customer OpenShift cluster with persistent TM1 and Workspace storage. Current Software Hub 5.4 guidance provides an application-specific install-components workflow and explicitly supports IBM Cloud, AWS, Azure and Google Cloud platform installations. Keep the platform/cartridge release aligned and verify permitted storage. The older Azure PDF is historical background; Local, SaaS, TM1 and cartridge versions and licences are separate.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Additional reviewed source: https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing

- IBM Cloud CP4D Services: https://github.com/ibm-cloud-docs/cloud-pak-data/blob/master/install-services.md

- Azure ARO PA Guide (PDF): https://cp4dazuremarketplacedoc.blob.core.windows.net/ibmcp4dazuremarketplace/CP4D_MS_ARO_Deployment_Guide.pdf

- PA Pricing & CP4D Cartridge: https://www.ibm.com/products/planning-analytics/pricing

- CP4D Docs Commits: https://github.com/ibm-cloud-docs/cloud-pak-data/commits/master

- PA CASE Index (v5.4.5): https://github.com/IBM/cloud-pak/blob/master/repo/case/ibm-planning-analytics/index.yaml

- PA CASE Commits: https://github.com/IBM/cloud-pak/commits/master/repo/case/ibm-planning-analytics

- Current Software Hub cloud installation environments: https://www.ibm.com/docs/en/software-hub/5.4.x?topic=cluster-installing-red-hat-openshift

- License information for IBM Software Hub 5.4 and related services: https://www.ibm.com/support/pages/node/7275162/

### Licensing sources

- https://www.ibm.com/products/planning-analytics/pricing

### Infrastructure sources

- https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The reviewed Software Hub cartridge installation context does not establish its exact user SSO configuration. Separate Planning Analytics Cloud IBMid and Advanced Certified Containers OIDC guides apply to different offerings; confirm the cartridge release, platform/user mapping and configured provider before transferring those claims. Scope: Planning Analytics cartridge on Software Hub; selected-edition user federation remains unconfirmed. Source: https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. IBM publishes a CASE package index for Planning Analytics, separate from Local and SaaS releases. Use the application-specific install-components workflow and keep the cartridge and Software Hub refresh aligned. Scope: Planning Analytics CASE package metadata; select a compatible release and licensed image source. Source: https://github.com/IBM/cloud-pak/blob/master/repo/case/ibm-planning-analytics/index.yaml (reviewed 2026-11-19). Deployment artifact: https://github.com/IBM/cloud-pak/blob/master/repo/case/ibm-planning-analytics/index.yaml. Artifact reference: master (moving CASE package index).

- Minimum footprint / sizing: Sources checked — unresolved. Software Hub/OpenShift platform requirements are additional to the Planning Analytics cartridge and model/data resources. A complete current cartridge-specific CPU/RAM/storage and HA baseline was not verified from accessible material; standalone/TM1 or vendor-hosted sizing must not be substituted. Scope: Planning Analytics cartridge current full production sizing remains unconfirmed. Source: https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing (reviewed 2026-11-21).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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







## Matomo On-Premise

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

- Listing: https://launchinyourcloud.com/directory/matomo/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, alibaba
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GPLv3-or-later core; premium plugins use separate commercial EULA and subscription terms
- Licensing model: open-source
- Installation: PHP web-server installation or official Docker image
- Architecture: Customer-operated analytics application and MySQL/MariaDB database with scheduled report processing
- Operations: Customer manages hosting, upgrades, security, backups, tracking configuration and scheduled report processing.
- Product website: https://matomo.org/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This entry covers Matomo On-Premise rather than Matomo Cloud. Core analytics can be self-hosted, while premium capabilities and support may require separate purchases. Configure collection, consent and retention deliberately rather than treating the deployment model as a privacy-compliance guarantee.

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

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


### Category fit

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

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

### Deployment boundaries


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

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

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

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


### Cloud deployment evidence

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


### Sources

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

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

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

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

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

### Licensing sources

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

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

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

### Infrastructure sources

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


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

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

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

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

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

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

- Operating cost estimate: Not researched.

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







## Metabase Self-Hosted

Business intelligence and dashboards on your infrastructure.

- Listing: https://launchinyourcloud.com/directory/metabase/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open-source and commercial options
- Licensing model: open-source
- Installation: Docker image or Java JAR
- Architecture: Customer-operated application and database
- Operations: Your team manages hosting, upgrades and the application database.
- Product website: https://www.metabase.com/
- Source review: 2026-11-17; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Metabase documents self-hosting on AWS, Google Cloud, Azure and DigitalOcean. This entry covers self-hosting rather than Metabase Cloud. Infrastructure sizing, the application database and feature entitlements depend on the selected edition. Metabase's critical security advisory affects 0.64.0 through 0.64.3.3 and corresponding Enterprise versions. Self-hosted operators should use Open Source 0.64.3.4 or later, or Enterprise 1.64.3.4 or later. The hardening release strengthens API validation and permission checks, limits metadata exposure, improves deactivated-user session handling, removes database secrets from serialization exports, and adds optional session-signing and encryption keys.

The self-hosted platform offers an AGPL Open Source Edition alongside commercial capabilities and licensing. The classification covers the platform family described in this entry.

The listed self-hosted installation uses application servers, database services or container workloads. This classification covers that deployment option; managed storage or a vendor control plane does not make the application serverless.


### Category fit

- data-analytics: Business intelligence and dashboards on your infrastructure.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale (checked 2026-11-12). 

- digitalocean: Boundary not confirmed; Customer-operated; control plane: not-assessed. Source: https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale (checked 2026-11-12). 


### Cloud deployment evidence

- Metabase production hosting compatibility (aws, azure, gcp, digitalocean): https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale
  The vendor names AWS Elastic Beanstalk and Docker, and explicitly identifies Google Cloud, Azure and DigitalOcean as alternative hosts for the Metabase application. Pair this compatibility statement with the current installation guide and a production application database; this is self-hosting, separate from Metabase Cloud.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Installing Metabase: https://www.metabase.com/docs/latest/installation-and-operation/installing-metabase

- Production hosting options: https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale

- Licensing and edition terms: https://www.metabase.com/license

- Metabase 64 critical security update: https://github.com/metabase/metabase/security/advisories/GHSA-v44v-x8x4-mvcw

### Licensing sources

- https://www.metabase.com/license

### Infrastructure sources

- https://www.metabase.com/docs/latest/installation-and-operation/installing-metabase

- https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. SAML authentication is available on Pro and Enterprise for self-hosted deployments. This does not establish SAML for the free/open-source edition. Scope: Self-hosted Pro and Enterprise. Source: https://www.metabase.com/docs/latest/people-and-groups/authenticating-with-saml (reviewed 2026-11-14).

- SCIM provisioning: Edition-dependent. Pro and Enterprise support SCIM. The documentation names Okta and Microsoft Entra ID; Okta supports user/group provisioning while Entra supports user provisioning only. Scope: Self-hosted Pro and Enterprise; identity-provider behavior differs. Source: https://www.metabase.com/docs/latest/people-and-groups/user-provisioning (reviewed 2026-11-14).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor supplies separate Open Source and Enterprise images and publishes Compose examples. Production needs an external supported application database; embedded H2 is evaluation-only. Pin the selected image, configure persistence, TLS and backup, and do not assume an officially supported Helm chart. Scope: Official self-hosted Docker/Compose distributions. Source: https://www.metabase.com/docs/latest/installation-and-operation/running-metabase-on-docker (reviewed 2026-11-20). Deployment artifact: https://www.metabase.com/docs/latest/installation-and-operation/running-metabase-on-docker#example-docker-compose-yaml-file. Artifact reference: v65 documentation; select a compatible image tag.

- Minimum footprint / sizing: Documented. The vendor gives an application baseline of 1 core/1 GB, plus 1 core/2 GB per 20 concurrent users. The application database starts at 1 core/2 GB and needs additional capacity. Query databases, HA replicas, storage and background jobs are extra; total registered users alone is insufficient for sizing. Scope: Post-v52 production sizing guidance by concurrent users, not registered accounts. Source: https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-in-production (reviewed 2026-11-20).

- License pricing: Documented. The repository separates AGPL core code from the commercial enterprise directory and enterprise binaries. Self-hosted Pro/Enterprise features require commercial terms; the core licence does not establish paid-edition prices, support or hosting cost. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/metabase/metabase/master/LICENSE.txt (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.




### Security and lifecycle reviews

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

- Metabase 64 critical security update (security-advisory): The advisory records API, permission, metadata, session and serialization hardening in the 64 release line. Scope: Open Source 0.64.0 to before 0.64.3.4 and corresponding Pro/Enterprise 1.64 versions. Conditions: Self-hosted edition, configured integrations and exposed endpoints determine which fixes apply; optional key settings need explicit configuration. Action: Upgrade Open Source to at least 0.64.3.4 or Pro/Enterprise to at least 1.64.3.4 and follow the vendor security checklist. Source: https://github.com/metabase/metabase/security/advisories/GHSA-v44v-x8x4-mvcw; reviewed 2026-11-17.




## OpenMetadata

Open-source metadata catalog and data-governance platform deployed with customer-operated services.

- Listing: https://launchinyourcloud.com/directory/openmetadata/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0.
- Licensing model: open-source
- Installation: Official Helm charts on EKS, AKS or GKE
- Architecture: Customer-operated application, ingestion jobs, relational metadata database and search service
- Operations: Customer manages Kubernetes, database, search, ingestion orchestration, secrets, backups, scaling and upgrades.
- Product website: https://open-metadata.org/
- Source review: 2026-11-18; cloud review: 2026-11-14; licensing review: 2026-11-14; infrastructure review: 2026-11-14

### Scope and qualifications

This entry covers OpenMetadata self-hosting, not the managed Collate service. Production guides use provider-managed database and search options. GKE Autopilot is incompatible with the documented Elasticsearch dependency configuration. OpenMetadata 2.0.8 fixes authorization, revoked-token, SSO state and stale-credential, MCP consent, API-token session, impersonation, Airflow/backend authorization, unsafe URL-scheme, and dependency issues. Upgrade from 2.0.7 and retest identity and MCP flows.

The OpenMetadata repository is Apache-2.0 licensed. Collate's managed and enterprise services have separate commercial terms.

OpenMetadata runs persistent application and ingestion workloads backed by a relational database and search service. Managed dependencies do not make the application runtime serverless.


### Category fit

- data-analytics: Catalogs data assets, lineage, quality, governance and observability metadata across connected systems.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/eks (checked 2026-11-14). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/aks (checked 2026-11-14). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/gke (checked 2026-11-14). 


### Cloud deployment evidence

- OpenMetadata on Amazon EKS (aws): https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/eks
  The official guide deploys OpenMetadata with Helm on a customer EKS cluster and documents AWS database and search dependencies.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- OpenMetadata on Azure Kubernetes Service (azure): https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/aks
  The official guide deploys OpenMetadata with Helm on a customer AKS cluster and documents Azure database and search dependencies.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- OpenMetadata on Google Kubernetes Engine (gcp): https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/gke
  The official guide deploys OpenMetadata with Helm on GKE. It explicitly notes that GKE Autopilot is incompatible with the documented Elasticsearch configuration.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.


### Community and maintenance

The project community publishes recurring meetups and user spotlights describing OpenMetadata use at the Fire Department of New York and Wix. Substantive contributions from multiple participants and the November 13, 2026 release 2.0.8 establish continuing maintenance, including authorization, token, SSO, consent, impersonation and dependency fixes. The spotlights establish project adoption without certifying a particular cloud or commercial edition.

Reviewed 2026-11-18.

- OpenMetadata 2.0.8 release: https://github.com/open-metadata/OpenMetadata/releases/tag/2.0.8-release

- Upstream contributor history: https://github.com/open-metadata/OpenMetadata/graphs/contributors

- Community meetups and FDNY/Wix user spotlights: https://open-metadata.org/community

### Sources

- Amazon EKS deployment: https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/eks

- Azure AKS deployment: https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/aks

- Google GKE deployment: https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/gke

- Apache 2.0 license: https://github.com/open-metadata/OpenMetadata/blob/main/LICENSE

- Upstream contributor history: https://github.com/open-metadata/OpenMetadata/graphs/contributors

- Community meetups and FDNY/Wix user spotlights: https://open-metadata.org/community

- OpenMetadata 2.0.8 release: https://github.com/open-metadata/OpenMetadata/releases/tag/2.0.8-release

### Licensing sources

- https://github.com/open-metadata/OpenMetadata/blob/main/LICENSE

### Infrastructure sources

- https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/eks

- https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/aks

- https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/gke


### 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 2.0.x deployment guide lists Google, Okta, Auth0, Azure, Cognito, OneLogin and custom OIDC. It states that multiple authentication mechanisms cannot be used simultaneously. Scope: OpenMetadata 2.0.x server authentication. Source: https://docs.open-metadata.org/v2.0.x/deployment/security (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: OpenMetadata 2.0.8 fixes incomplete authorization, revoked-token validity, SSO state and stale credentials, MCP consent, API-token sessions, impersonation boundaries, backend authorization, unsafe URL schemes, and security dependencies. Upgrade to 2.0.8 or later and retest authentication, token revocation, MCP consent, and impersonation. Scope: Upstream 2.0.8 release notes; the individual fixes do not share one universal affected-version range.. Source: https://github.com/open-metadata/OpenMetadata/releases/tag/2.0.8-release (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The project publishes Helm deployment for OpenMetadata and external database, search and ingestion dependencies. Ingress and network policies are optional and disabled by default. Choose compatible chart/application versions and configure authentication, secrets, persistence and production network controls. Scope: Official Kubernetes Helm distribution. Source: https://docs.open-metadata.org/latest/deployment/kubernetes (reviewed 2026-11-20). Deployment artifact: https://github.com/open-metadata/openmetadata-helm-charts. Artifact reference: Select a release matching the chosen OpenMetadata version.

- Minimum footprint / sizing: Documented. The local Docker quickstart allocates at least 6 GiB memory and 4 vCPUs to Docker for the standalone stack. This is a local quickstart profile, not a production or HA minimum. External database, search, ingestion and concurrency need separate capacity planning. Scope: Local Docker stack allocation; production and HA excluded. Source: https://docs.open-metadata.org/latest/quick-start/local-docker-deployment (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/open-metadata/OpenMetadata/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. OpenMetadata 2.0.8-release, corresponding to product version 2.0.8, was published November 13, 2026. It contains material authorization, token, SSO, consent, impersonation, URL-scheme, and dependency security fixes. Scope: Upstream OpenMetadata 2.0 release. Source: https://github.com/open-metadata/OpenMetadata/releases/tag/2.0.8-release (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- OpenMetadata 2.0.8 security maintenance (security-advisory): OpenMetadata 2.0.8 fixes incomplete authorization, revoked-token validity, SSO state and stale credentials, MCP consent, API-token sessions, impersonation boundaries, backend authorization, unsafe URL schemes, and security dependencies. Scope: Upstream 2.0.8 release notes; the individual fixes do not share one universal affected-version range. Conditions: Applicability depends on enabled AI Context, MCP, SSO, impersonation, Airflow, and affected dependencies. Action: Upgrade to 2.0.8 or later and retest authentication, token revocation, MCP consent, and impersonation. Source: https://github.com/open-metadata/OpenMetadata/releases/tag/2.0.8-release; reviewed 2026-11-18.




## Qlik Sense Enterprise Client-Managed

Commercial client-managed analytics platform installed on customer cloud Windows virtual machines.

- Listing: https://launchinyourcloud.com/directory/qlik-sense-enterprise-client-managed/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Qlik Sense Enterprise license.
- Licensing model: commercial-only
- Installation: Qlik Sense Enterprise on Windows using provider-specific AWS, Azure or Google Cloud VM guidance
- Architecture: Single- or multi-node Windows services with repository database, shared storage, identity and load-balancing dependencies
- Operations: Customer manages Windows hosts, networking, certificates, identity, repository database, shared storage, load balancing, backups, scaling, upgrades and license activation.
- Product website: https://www.qlik.com/us/products/qlik-sense
- Source review: 2026-11-15; cloud review: 2026-11-15; licensing review: 2026-11-15; infrastructure review: 2026-11-15

### Scope and qualifications

This entry covers Qlik Sense Enterprise Client-Managed on Windows, not Qlik Cloud. Review current system requirements, supported Windows and database versions, multi-node topology and licensing terms before deployment.

Qlik Sense Enterprise Client-Managed is activated through a commercial subscription, perpetual or capacity/core-based license model as applicable to the agreement.

Qlik Sense Enterprise Client-Managed runs persistent Windows services and repository components on customer virtual machines.


### Category fit

- data-analytics: Provides customer-operated business intelligence, associative analytics, dashboards and governed data applications.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/AWS-deployment-instruction.htm (checked 2026-11-15). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/Azure-deployment-instruction.htm (checked 2026-11-15). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/GCP-deployment-instruction.htm (checked 2026-11-15). 


### Cloud deployment evidence

- Qlik Sense Enterprise on AWS (aws): https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/AWS-deployment-instruction.htm
  Qlik documents preparing customer Amazon EC2 Windows infrastructure and installing Qlik Sense Enterprise on Windows.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.

- Qlik Sense Enterprise on Azure (azure): https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/Azure-deployment-instruction.htm
  Qlik documents preparing Azure virtual machines, resource groups and networking before installing Qlik Sense Enterprise on Windows.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.

- Qlik Sense Enterprise on Google Cloud (gcp): https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/GCP-deployment-instruction.htm
  Qlik documents preparing Google Compute Engine Windows instances and installing Qlik Sense Enterprise on Windows.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.


### Sources

- Qlik Sense client-managed administration and deployment: https://help.qlik.com/en-US/sense-admin/May2026/Content/Sense_Helpsites/Home-deployadminister.htm

- Qlik Sense on AWS: https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/AWS-deployment-instruction.htm

- Qlik Sense on Azure: https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/Azure-deployment-instruction.htm

- Qlik Sense on Google Cloud: https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/GCP-deployment-instruction.htm

- Qlik product licenses: https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/Common/Qlik-product-licenses.htm

### Licensing sources

- https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/Common/Qlik-product-licenses.htm

### Infrastructure sources

- https://help.qlik.com/en-US/sense-admin/May2026/Content/Sense_Helpsites/Home-deployadminister.htm


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The May 2026 client-managed guide documents SAML using a configured virtual proxy, linked proxy, IdP metadata and user attributes. Configure the selected proxy prefix and identity mapping; Qlik Cloud sign-in and database-connection SSO are separate concerns. Scope: Qlik Sense Enterprise on Windows May 2026 application-user SAML. Source: https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Administer_QSEoW/Managing_QSEoW/Configure-SAML.htm (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The client-managed AWS guide documents Windows infrastructure and Qlik Sense deployment choices. Obtain the licensed installer and configure supported nodes, networking, repository/database and shared storage; cloud guidance is not a universal unattended or HA application template. Scope: Qlik Sense Enterprise on Windows May 2026 AWS installation guide. Source: https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/AWS-deployment-instruction.htm (reviewed 2026-11-21). Deployment artifact: https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/AWS-deployment-instruction.htm. Artifact reference: May 2026 documentation.

- Minimum footprint / sizing: Documented. The May 2026 requirements list multi-core x64/AVX hardware, at least 8 GB RAM and 5 GB installation disk, with data-dependent additional memory/storage and shared storage for multi-server sites. These installation requirements do not size an in-memory 1-TB analytical workload, concurrency, repository database or HA replicas. Scope: Qlik Sense Enterprise client-managed installation baseline; production data/model capacity separate. Source: https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/Common/system-requirements.htm (reviewed 2026-11-21).

- License pricing: Documented. Qlik Sense Enterprise supports access-type or token licensing. Professional/Analyzer user and Analyzer Capacity entitlements have different conditions. Signed license keys require access to the cloud license backend; confirm activation and usage terms for the customer-managed installation. Scope: Qlik Sense Enterprise client-managed, May 2026 administration guide. Source: https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/Common/Qlik-product-licenses.htm (reviewed 2026-11-16).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## QuestDB Open Source Self-Hosted

Apache-licensed time-series database installed on customer virtual machines in AWS, Azure or Google Cloud.

- Listing: https://launchinyourcloud.com/directory/questdb-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: QuestDB Open Source is Apache License 2.0; QuestDB Enterprise is separately proprietary.
- Licensing model: open-source
- Installation: Vendor AWS OSS AMI 10.1.0, or customer VM binary/systemd/container installation; validate the AMI OS lifecycle; Azure Marketplace packaging is Enterprise
- Architecture: Persistent QuestDB process with dedicated data disks, network endpoints and customer-managed operating system.
- Operations: Customer manages VM and OS, data disks, networking, authentication, backups, monitoring, upgrades and capacity.
- Product website: https://questdb.com/
- Source review: 2026-11-18; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

QuestDB Open Source excludes native replication, automatic failover and OIDC SSO in the vendor edition matrix. The requested native HA scenario therefore requires a different edition or a separately validated external design. Azure Marketplace packaging is Enterprise, not OSS. The separate free upstream AWS OSS AMI is confirmed, but its Marketplace OS label is Amazon Linux 2, whose standard support ended June 30, 2026. Resolve the actual AMI and maintained OS before production.

QuestDB Open Source is Apache-2.0. QuestDB Enterprise uses separate commercial terms.

QuestDB runs as a persistent database process on provisioned compute with durable data disks.


### Category fit

- databases-vector: Provides a high-performance time-series database with SQL and ingestion protocols on customer infrastructure.

- data-analytics: Supports time-series ingestion, SQL analytics and operational analysis of large event datasets.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://questdb.com/docs/deployment/aws/ (checked 2026-11-18). Source: https://aws.amazon.com/marketplace/pp/prodview-cddeafdirexw6 (checked 2026-11-18). 

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

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


### Cloud deployment evidence

- QuestDB on AWS (aws): https://questdb.com/docs/deployment/aws/
  QuestDB documents manual installation of the full OSS application on customer EC2 with VPC, persistent storage and operating choices. Enterprise marketplace features are not inherited.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- QuestDB on Azure (azure): https://questdb.com/docs/deployment/azure/
  The Azure guide includes customer VM deployment. Its Marketplace offer is Enterprise; use the manual OSS path for this listing and do not transfer Enterprise entitlements.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- QuestDB on Google Cloud (gcp): https://questdb.com/docs/deployment/gcp/
  QuestDB documents deployment to customer Compute Engine with separate durable storage.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- Vendor-published QuestDB Open Source AWS AMI (aws): https://aws.amazon.com/marketplace/pp/prodview-cddeafdirexw6
  The QuestDB-published AMI installs the OSS database on customer EC2. Package 10.1.0 lists Amazon Linux 2; verify the resolved image and replace unsupported OS packaging. Availability does not supply Enterprise HA, OIDC or a support entitlement.
  Source type: marketplace-offer; reviewed: 2026-11-18; vendor support: not-assessed. Edition: QuestDB Open Source. Versions: AMI package 10.1.0.


### Community and maintenance

QuestDB maintains an open source repository with contributor participation, installation instructions and current OSS releases. Enterprise customer stories do not establish OSS entitlements or customer-account hosting; provider-specific manual guides supply that evidence.

Reviewed 2026-11-18.

- Official maintenance and adoption evidence: https://github.com/questdb/questdb

- Official maintenance and adoption evidence: https://github.com/questdb/questdb/releases/tag/10.2.0

### Sources

- Deploy QuestDB on AWS: https://questdb.com/docs/deployment/aws/

- Deploy QuestDB on Azure: https://questdb.com/docs/deployment/azure/

- Deploy QuestDB on Google Cloud: https://questdb.com/docs/deployment/gcp/

- QuestDB repository and license: https://github.com/questdb/questdb

- Exact vendor AWS OSS AMI and package: https://aws.amazon.com/marketplace/pp/prodview-cddeafdirexw6

- Amazon Linux 2 lifecycle: https://aws.amazon.com/amazon-linux-2/faqs/

### Licensing sources

- https://github.com/questdb/questdb

- https://questdb.com/terms/

### Infrastructure sources

- https://questdb.com/docs/deployment/aws/

- https://questdb.com/docs/deployment/azure/

- https://questdb.com/docs/deployment/gcp/


### Buyer diligence


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

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


- Marketplace delivery: Documented. QuestDB publishes the free QuestDB Open Source AMI prodview-cddeafdirexw6 on AWS Marketplace, package 10.1.0, x86. Infrastructure is charged separately. The offer lists Amazon Linux 2.0.20210318.0; AWS ended AL2 standard support on June 30, 2026. Verify the resolved AMI OS and use a maintained image before production. This offer is distinct from Azure Enterprise packaging and does not add OSS replication, HA or OIDC. Scope: Vendor-published QuestDB Open Source AWS AMI 10.1.0; package availability is not a production recommendation. Source: https://aws.amazon.com/marketplace/pp/prodview-cddeafdirexw6 (reviewed 2026-11-18). Supporting source: Manual customer EC2 installation — https://questdb.com/docs/deployment/aws/. Supporting source: Amazon Linux 2 end of support — https://aws.amazon.com/amazon-linux-2/faqs/. Offer prodview-cddeafdirexw6: QuestDB; Amazon Machine Image (AMI), x86; package 10.1.0; https://aws.amazon.com/marketplace/pp/prodview-cddeafdirexw6.

- Cloud commitment eligibility: Explicitly unsupported. The exact reviewed QuestDB Open Source AWS AMI is free of charge in Marketplace. It supplies no billed software amount to apply toward a software-spend commitment through this offer. EC2/EBS, paid support, other editions and separately negotiated offers have separate charges and require the buyer’s applicable order and AWS agreement; the free software finding does not settle those charges. Scope: Software amount through the exact free AWS AMI prodview-cddeafdirexw6; infrastructure, paid support, other editions and private offers assessed separately. Source: https://aws.amazon.com/marketplace/pp/prodview-cddeafdirexw6 (reviewed 2026-11-18). Supporting source: AWS product-by-product commitment qualifications — https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html.

- Single sign-on: Explicitly unsupported. QuestDB’s edition comparison assigns OIDC SSO to Enterprise. Open Source has its documented local authentication controls and does not include that Enterprise OIDC feature. An external identity proxy would be a separate architecture. Scope: Native QuestDB Open Source OIDC SSO; Enterprise entitlement is excluded. Source: https://questdb.com/enterprise/ (reviewed 2026-11-18).

- SCIM provisioning: Sources checked — unresolved. The governance comparison does not establish a native OSS SCIM endpoint or user/group deprovisioning operations. Enterprise RBAC/OIDC are not evidence that SCIM is supplied in Open Source. Scope: QuestDB Open Source Self-Hosted: selected customer-operated edition. Source: https://questdb.com/docs/security/governance/ (reviewed 2026-11-18).

- Compliance attestations: Sources checked — unresolved. The current governance material advertises SOC 2 Type 2 while distinguishing Enterprise controls from OSS. No public audit period/system description established that the report covers this customer-operated OSS database and its external encryption/network controls. Obtain the full report and relevant customer-control scope; a footer badge is insufficient. Scope: QuestDB Open Source Self-Hosted: selected customer-operated edition. Source: https://questdb.com/docs/security/governance/ (reviewed 2026-11-18).

- Security controls: Documented. The edition matrix distinguishes OSS controls from Enterprise TLS, RBAC and OIDC. The AWS guide directs operators to change HTTP/PG credentials, disable unused interfaces and restrict source IPs. Design encryption and network boundaries explicitly rather than inheriting Enterprise capabilities. Scope: QuestDB Open Source Self-Hosted: selected customer-operated edition. Source: https://questdb.com/docs/security/governance/ (reviewed 2026-11-18). Supporting source: OSS instance hardening — https://questdb.com/docs/deployment/aws/. Supporting source: Disable Web Console usage telemetry — https://questdb.com/docs/configuration/telemetry/. Supporting source: AMI operating-system support boundary — https://aws.amazon.com/amazon-linux-2/faqs/.

- Air-gapped operation: Sources checked — unresolved. QuestDB documents telemetry.enabled=false, which stops Web Console usage telemetry and removes its Metrics View. Manual binaries are also available. These facts do not validate the complete disconnected OSS lifecycle: confirm a local JRE/artifact supply, restart/configuration, ingest/query clients, updates and backup/recovery. Enterprise offline-trial and backup claims are not inherited by OSS. Scope: QuestDB Open Source Self-Hosted: selected customer-operated edition. Source: https://questdb.com/docs/configuration/telemetry/ (reviewed 2026-11-18). Supporting source: OSS installation and upgrade artifact — https://questdb.com/docs/deployment/aws/.

- Deployment artifact / IaC: Documented. The manual EC2 guide links the versioned QuestDB 10.2.0 no-JRE binary archive and systemd upgrade steps. Supply a compatible JRE and review service configuration. This is an application artifact, not a complete HA Terraform stack. Scope: QuestDB Open Source Self-Hosted: selected customer-operated edition. Source: https://questdb.com/docs/deployment/aws/ (reviewed 2026-11-18). Deployment artifact: https://github.com/questdb/questdb/releases/download/10.2.0/questdb-10.2.0-no-jre-bin.tar.gz. Artifact reference: QuestDB OSS 10.2.0, no-JRE archive.

- Minimum footprint / sizing: Documented. Capacity guidance recommends 8 GB RAM for basic and 32 GB for advanced use, fast local/NVMe storage and workload-specific CPU planning. The edition comparison explicitly excludes replication and automatic failover from OSS, so this listing cannot satisfy the requested native HA design. Scope: QuestDB Open Source Self-Hosted: selected customer-operated edition. Source: https://questdb.com/docs/getting-started/capacity-planning/ (reviewed 2026-11-18). Supporting source: OSS versus Enterprise availability features — https://questdb.com/enterprise/.

- License pricing: Documented. QuestDB Open Source is Apache 2.0 licensed. Enterprise adds commercial capabilities, including replication/HA and OIDC, under separate terms; those features and licence costs are outside this OSS listing. Scope: QuestDB Open Source Self-Hosted: selected customer-operated edition. Source: https://github.com/questdb/questdb (reviewed 2026-11-18). Supporting source: Commercial edition boundary — https://questdb.com/enterprise/.

- Operating cost estimate: Sources checked — unresolved. The requested HA architecture is not supplied by native QuestDB Open Source replication/failover. Decide whether to change edition or separately validate an external recovery design before costing. Then supply ingestion rate, series/cardinality, query concurrency, retained rows, storage compression and recovery objectives. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://questdb.com/enterprise/ (reviewed 2026-11-18). Supporting source: Current AWS Linux EC2 rates; workload/topology still required — https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json. Supporting source: Storage performance and charging inputs — https://aws.amazon.com/ebs/pricing/.

- Release snapshot / cadence: Documented. QuestDB OSS 10.2.0 was published November 10, 2026. Enterprise release numbers follow a separate line. Pin the OSS binary/container and dependencies; this snapshot does not establish a support SLA or future cadence. The reviewed AWS OSS AMI packages 10.1.0 rather than upstream 10.2.0 and lists AL2; check the actual OS image lifecycle. Scope: QuestDB Open Source Self-Hosted: selected customer-operated edition. Source: https://github.com/questdb/questdb/releases/tag/10.2.0 (reviewed 2026-11-18). Supporting source: Separate AWS OSS package and OS label — https://aws.amazon.com/marketplace/pp/prodview-cddeafdirexw6. Supporting source: AL2 support ended June 30, 2026 — https://aws.amazon.com/amazon-linux-2/faqs/.




### Security and lifecycle reviews

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

- QuestDB OSS AWS offer lists an operating system past standard support (lifecycle): The reviewed QuestDB OSS AWS AMI package 10.1.0 lists Amazon Linux 2.0.20210318.0. AWS ended AL2 standard support on June 30, 2026. Scope: The OS label of AWS offer prodview-cddeafdirexw6; not all QuestDB versions, manual VM installs or other cloud packages. Conditions: Marketplace metadata can lag the actual AMI. Confirm the resolved image ID and OS before concluding that a deployed instance uses AL2; application version alone does not establish OS maintenance. Action: Verify the actual AMI OS and use maintained operating-system packaging before production. Migrate any confirmed AL2 host under the vendor/provider upgrade procedure and test backup/recovery. Source: https://aws.amazon.com/amazon-linux-2/faqs/; reviewed 2026-11-18. Supporting source: Exact QuestDB OSS offer, package and OS label — https://aws.amazon.com/marketplace/pp/prodview-cddeafdirexw6.




## RADAR-base (ManagementPortal & Study Platform)

Open-source study-management and remote research-data collection platform.

- Listing: https://launchinyourcloud.com/directory/radar-base/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Terraform; Kubernetes manifests
- Architecture: RADAR Kubernetes application services, databases and collection pipelines on Terraform-provisioned EKS or AKS.
- 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://github.com/RADAR-base/ManagementPortal
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

ManagementPortal, infrastructure modules and the full chart bundle have separate releases. Participant/data management does not establish grant administration or regulatory document-control functionality. Clinical-use validation, ethics and consent processes remain the operator's responsibility.

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

RADAR Kubernetes application services, databases and collection pipelines on Terraform-provisioned EKS or AKS. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- data-analytics: Open-source study-management and remote research-data collection platform.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/RADAR-base/RADAR-K8s-Infrastructure/main/aws/cluster/README.md (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/RADAR-base/RADAR-K8s-Infrastructure/main/azure/README.md (checked 2026-11-19). 


### Cloud deployment evidence

- AWS EKS Terraform (aws): https://raw.githubusercontent.com/RADAR-base/RADAR-K8s-Infrastructure/main/aws/cluster/README.md
  RADAR Kubernetes application services, databases and collection pipelines on Terraform-provisioned EKS or AKS. ManagementPortal, infrastructure modules and the full chart bundle have separate releases. Participant/data management does not establish grant administration or regulatory document-control functionality. Clinical-use validation, ethics and consent processes remain the operator's responsibility.
  Source type: institution-deployment; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Terraform (azure): https://raw.githubusercontent.com/RADAR-base/RADAR-K8s-Infrastructure/main/azure/README.md
  RADAR Kubernetes application services, databases and collection pipelines on Terraform-provisioned EKS or AKS. ManagementPortal, infrastructure modules and the full chart bundle have separate releases. Participant/data management does not establish grant administration or regulatory document-control functionality. Clinical-use validation, ethics and consent processes remain the operator's responsibility.
  Source type: institution-deployment; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes nivemaham, blootsvoets, dennyverbeeck, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/RADAR-base/ManagementPortal/graphs/contributors

- Upstream project: https://github.com/RADAR-base/ManagementPortal

### Sources

- AWS EKS Terraform: https://raw.githubusercontent.com/RADAR-base/RADAR-K8s-Infrastructure/main/aws/cluster/README.md

- Azure Terraform: https://raw.githubusercontent.com/RADAR-base/RADAR-K8s-Infrastructure/main/azure/README.md

- RADAR-Kubernetes: https://raw.githubusercontent.com/RADAR-base/RADAR-Kubernetes/main/README.md

- ManagementPortal Docs: https://radar-base.org/index.php/management-portal/

- Apache-2.0: https://raw.githubusercontent.com/RADAR-base/ManagementPortal/master/LICENSE.md

- ManagementPortal Releases: https://github.com/RADAR-base/ManagementPortal/releases

- K8s Releases: https://github.com/RADAR-base/RADAR-Kubernetes/releases

### Licensing sources

- https://raw.githubusercontent.com/RADAR-base/ManagementPortal/master/LICENSE.md

### Infrastructure sources

- https://raw.githubusercontent.com/RADAR-base/RADAR-K8s-Infrastructure/main/aws/cluster/README.md

- https://raw.githubusercontent.com/RADAR-base/RADAR-K8s-Infrastructure/main/azure/README.md


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The current ManagementPortal README describes browser login through an external Ory Hydra/Kratos stack and self-enrolment UI, which must run for redirects and login pages to work. Configure compatible portal/identity releases and users; this confirms the RADAR identity-stack login path, not every external enterprise SAML integration or mobile-device credential. Scope: Moving upstream RADAR ManagementPortal central identity-stack browser login. Source: https://github.com/RADAR-base/ManagementPortal/blob/master/README.md (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. RADAR-Kubernetes supplies application deployment resources; the separate AWS/Azure infrastructure repository provisions the cluster. Pin a compatible application/chart bundle and infrastructure revision rather than using the portal component version for the entire stack. Scope: Application deployment collection paired with the documented cloud infrastructure. Source: https://raw.githubusercontent.com/RADAR-base/RADAR-Kubernetes/main/README.md (reviewed 2026-11-19). Deployment artifact: https://github.com/RADAR-base/RADAR-Kubernetes. Artifact reference: main (moving application deployment collection).

- Minimum footprint / sizing: Documented. The Kubernetes deployment README gives a single-node minimum of 8 vCPU/32 GB RAM/200 GB storage, or a cluster of three nodes at 3 vCPU/16 GB/100 GB each plus 200 GB shared storage. These are infrastructure starting points; streaming, study/device volume, retention, external services and HA capacity still need validation. Scope: RADAR Kubernetes published topology minimums, not a reference-workload guarantee. Source: https://github.com/RADAR-base/RADAR-Kubernetes/blob/main/README.md (reviewed 2026-11-21).

- License pricing: Documented. Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: RADAR-base (ManagementPortal & Study Platform); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/RADAR-base/ManagementPortal/master/LICENSE.md (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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




## Snowplow CDI Private Managed Cloud

Vendor-managed behavioural event pipeline running in the customer's cloud account.

- Listing: https://launchinyourcloud.com/directory/snowplow-private-managed-cloud/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Vendor-operated BYOC
- Infrastructure IDs: servers
- License: Commercial Private Managed Cloud plan with quote-based pricing.
- Licensing model: commercial-only
- Installation: Provide a dedicated AWS account, Azure subscription, or Google Cloud project and grant the permissions in the provider guide.
- Architecture: Pipeline VM or Kubernetes resources run in the customer's cloud and load events to the customer's warehouse or lake. Snowplow hosts the management console and APIs.
- Operations: Snowplow provisions, monitors, patches, and upgrades the pipeline. The customer supplies the cloud environment, access permissions, and data destination.
- Product website: https://snowplow.io/
- Source review: 2026-11-21; cloud review: 2026-11-21; licensing review: 2026-11-21; infrastructure review: 2026-11-21

### Scope and qualifications

Snowplow requires dedicated subnets and remote operational access. Certain restricted environments, including AWS GovCloud and Azure Government, are outside the documented support scope. Agree how to preserve schema and configuration records and revoke Snowplow's access at offboarding.

Commercial Private Managed Cloud plan with quote-based pricing.

Pipeline VM or Kubernetes resources run in the customer's cloud and load events to the customer's warehouse or lake. Snowplow hosts the management console and APIs.


### Category fit

- data-analytics: Collects, validates, enriches, and delivers behavioural event data to the customer's data warehouse or lake.

### Deployment boundaries


- aws: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://docs.snowplow.io/docs/get-started/private-managed-cloud/setup-guide-aws/ (checked 2026-11-21). 

- azure: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://docs.snowplow.io/docs/get-started/private-managed-cloud/setup-guide-azure/ (checked 2026-11-21). 

- gcp: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://docs.snowplow.io/docs/get-started/private-managed-cloud/setup-guide-gcp/ (checked 2026-11-21). 

Operating responsibility: Snowplow operates, monitors and upgrades the pipeline in the customer's dedicated cloud environment. Snowplow hosts the management Console and APIs outside that data plane; the customer supplies the cloud account, permissions and warehouse or lake. Source: https://docs.snowplow.io/docs/get-started/deployment-options/ (checked 2026-11-21). Supporting source: Operational access and deployment restrictions — https://docs.snowplow.io/restrictive-access-models/.


### Cloud deployment evidence

- Snowplow Private Managed Cloud on AWS (aws): https://docs.snowplow.io/docs/get-started/private-managed-cloud/setup-guide-aws/
  Snowplow uses delegated cross-account access to install and operate the pipeline in the customer's selected AWS region.
  Source type: vendor-documentation; reviewed: 2026-11-21; vendor support: not-assessed.

- Snowplow Private Managed Cloud on Azure (azure): https://docs.snowplow.io/docs/get-started/private-managed-cloud/setup-guide-azure/
  The Azure guide uses an application service principal and role scoped to the customer's subscription.
  Source type: vendor-documentation; reviewed: 2026-11-21; vendor support: not-assessed.

- Snowplow Private Managed Cloud on Google Cloud (gcp): https://docs.snowplow.io/docs/get-started/private-managed-cloud/setup-guide-gcp/
  The customer enables billing and grants installation and maintenance roles in its Google Cloud project.
  Source type: vendor-documentation; reviewed: 2026-11-21; vendor support: not-assessed.


### Sources

- Deployment options and control-plane boundary: https://docs.snowplow.io/docs/get-started/deployment-options/

- Infrastructure and access requirements: https://docs.snowplow.io/restrictive-access-models/

- Private Managed Cloud pricing: https://snowplow.io/pricing

- Customer account boundaries and operation: https://support.snowplow.io/articles/4431218364-learn-about-snowplow-bdp

- Snowplow Private Managed Cloud on AWS: https://docs.snowplow.io/docs/get-started/private-managed-cloud/setup-guide-aws/

- Snowplow Private Managed Cloud on Azure: https://docs.snowplow.io/docs/get-started/private-managed-cloud/setup-guide-azure/

- Snowplow Private Managed Cloud on Google Cloud: https://docs.snowplow.io/docs/get-started/private-managed-cloud/setup-guide-gcp/

### Licensing sources

- https://snowplow.io/pricing

### Infrastructure sources

- https://docs.snowplow.io/restrictive-access-models/


### 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: Documented. Snowplow Console administrators can configure SSO using SAML or OpenID Connect. The PMC deployment uses the vendor-hosted Console and APIs; pricing lists SSO and user permissions on every plan. This does not establish SSO at event collectors, destination systems or the customer's cloud console. Scope: Vendor-hosted Snowplow Console identity for CDI Private Managed Cloud.. Source: https://docs.snowplow.io/docs/account-management/managing-users/ (reviewed 2026-11-21). Supporting source: PMC control-plane boundary — https://docs.snowplow.io/docs/get-started/deployment-options/. Supporting source: Plan features including SSO — https://snowplow.io/pricing.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Explicitly unsupported. PMC deployment and monitoring require Snowplow's direct public-internet access to the customer environment. The vendor explicitly excludes architectures that prohibit that access, even when customer-managed VPN or SSO gates would otherwise provide access. This managed model does not support a fully disconnected environment. Scope: Snowplow CDI PMC operational connectivity; IP allowlisting is supported, full disconnection is not.. Source: https://docs.snowplow.io/restrictive-access-models/ (reviewed 2026-11-21).

- Deployment artifact / IaC: Sources checked — unresolved. Snowplow documents a proprietary IaC platform for PMC. Its AWS setup guide links a public CloudFormation template for the SnowplowAdmin IAM role and describes a separate deployment role; that access bootstrap does not expose the complete managed pipeline installer. Obtain the release-specific deployment configuration, full permissions and rollback/export procedure from Snowplow. Self-Hosted Terraform modules describe a different operating model. Scope: Complete CDI PMC runtime artifact unresolved; AWS IAM-role bootstrap is documented separately.. Source: https://docs.snowplow.io/restrictive-access-models/ (reviewed 2026-11-21). Supporting source: AWS IAM role and CloudFormation access bootstrap — https://docs.snowplow.io/docs/get-started/private-managed-cloud/setup-guide-aws/.

- Minimum footprint / sizing: Sources checked — unresolved. The managed-cloud setup guides specify account access and dedicated networking, not a complete quantitative production CPU/RAM/storage baseline. Snowplow scales and operates the pipeline; obtain sizing against events per month, peak event rate, enrichment workloads, destinations, retention and HA/recovery objectives. Customer-console user count and warehouse data size do not establish event-pipeline capacity. Scope: CDI Private Managed Cloud production sizing unresolved; separate self-hosted examples are not a PMC guarantee.. Source: https://docs.snowplow.io/docs/get-started/private-managed-cloud/setup-guide-aws/ (reviewed 2026-11-21). Supporting source: Dedicated-subnet and operational constraints — https://docs.snowplow.io/restrictive-access-models/.

- License pricing: Documented. Private Managed Cloud is a commercial, custom-quote deployment inside the customer's AWS, Google Cloud or Azure account. The quote depends on events per month, deployment location and destinations. Confirm infrastructure, vendor service and support charges in the contract; the free hosted trial and production Self-Hosted license are separate options. Scope: CDI Private Managed Cloud quote-based commercial terms; no numeric public PMC rate established.. Source: https://snowplow.io/pricing (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Splunk Enterprise

Customer-managed platform for ingesting, indexing, searching and visualizing machine data.

- Listing: https://launchinyourcloud.com/directory/splunk-enterprise/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial end-user license based on data volume or infrastructure; limited trial, developer and Free licenses have separate restrictions.
- Licensing model: commercial-only
- Installation: Splunk Enterprise installation package on supported Linux or Windows hosts; Docker is limited to supported standalone and single-server topologies.
- Architecture: Standalone or distributed customer-operated search heads, indexers and management components, with local storage or optional SmartStore object storage
- Operations: Customer manages compute, networking, storage, data inputs, certificates, clustering, capacity, backups, license configuration, monitoring and upgrades.
- Product website: https://www.splunk.com/en_us/products/splunk-enterprise.html
- 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-managed Splunk Enterprise, not Splunk Cloud Platform. Splunk documents customer-managed BYOL architectures on AWS, Azure and Google Cloud. Current installation documentation limits supported container deployments to standalone and single-server topologies, so distributed production deployments should follow supported package-based validated architectures. Confirm supported operating systems, instance types, object-store throughput, cache sizing and clustering requirements. Splunk advance notice SVD-2026-1101 says forthcoming November disclosures are fixed in Enterprise 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 and strongly recommends those or later releases. Final CVE-specific disclosures were not live during this review; 10.6.0 Universal Forwarder users should move to 10.6.1 or later.

Splunk Enterprise is proprietary software. Production customers purchase commercial end-user licenses based on indexed data volume or licensed infrastructure. Trial, developer and Free licenses are restricted alternatives and do not establish an open-source edition.

Splunk Enterprise runs persistent standalone or distributed search, indexing and management services on customer-managed hosts. SmartStore can move indexed data to customer object storage, but the search and indexing tiers remain long-running server workloads.


### Category fit

- observability: Ingests, indexes and searches machine data for operational monitoring, troubleshooting, dashboards and alerting.

- data-analytics: Provides search, dashboards, reports and statistical analysis over indexed machine-generated data.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.splunk.com/en/splunk-enterprise/get-started/deployment-capacity-manual/10.6/performance-reference/reference-hardware (checked 2026-11-16). Source: https://help.splunk.com/en/splunk-enterprise/splunk-validated-architectures/splunk-platform-indexing-and-search/smartstore-for-splunk-platform (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.splunk.com/en/splunk-enterprise/get-started/deployment-capacity-manual/10.6/performance-reference/reference-hardware (checked 2026-11-16). Source: https://help.splunk.com/en/splunk-enterprise/splunk-validated-architectures/splunk-platform-indexing-and-search/smartstore-for-splunk-platform (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.splunk.com/en/splunk-enterprise/get-started/deployment-capacity-manual/10.6/performance-reference/reference-hardware (checked 2026-11-16). Source: https://help.splunk.com/en/splunk-enterprise/splunk-validated-architectures/splunk-platform-indexing-and-search/smartstore-for-splunk-platform (checked 2026-11-16). 


### Cloud deployment evidence

- Splunk Enterprise reference hardware for AWS, Azure and Google Cloud (aws, azure, gcp): https://help.splunk.com/en/splunk-enterprise/get-started/deployment-capacity-manual/10.6/performance-reference/reference-hardware
  Splunk explicitly states that Splunk Enterprise can be deployed on Amazon Web Services, Microsoft Azure and Google Cloud Platform, including named government, local and distributed variants. Customers must still select supported host specifications and size each deployment for its workload.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.

- Customer-managed Splunk Enterprise BYOL architecture (aws, azure, gcp): https://help.splunk.com/en/splunk-enterprise/splunk-validated-architectures/splunk-platform-indexing-and-search/smartstore-for-splunk-platform
  Splunk describes customer-managed cloud deployments as BYOL on AWS, Google Cloud or Azure and provides provider-specific SmartStore architecture guidance. This evidence concerns customer-operated Splunk Enterprise, not Splunk Cloud Platform; validate instance, network, object-store and cache requirements for the selected topology.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.


### Sources

- Splunk Enterprise installation overview: https://help.splunk.com/en/splunk-enterprise/administer/install-and-upgrade/10.6/plan-your-splunk-enterprise-installation/installation-overview

- Splunk Enterprise reference hardware: https://help.splunk.com/en/splunk-enterprise/get-started/deployment-capacity-manual/10.6/performance-reference/reference-hardware

- Customer-managed BYOL SmartStore architectures: https://help.splunk.com/en/splunk-enterprise/splunk-validated-architectures/splunk-platform-indexing-and-search/smartstore-for-splunk-platform

- Splunk Enterprise license types: https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.6/configure-splunk-licenses/types-of-splunk-enterprise-licenses

- Splunk November 2026 advance notice: https://advisory.splunk.com/advisories/SVD-2026-1101

- Splunk Enterprise 10.6 release notes: https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.6/whats-new/welcome-to-splunk-enterprise-10.6

### Licensing sources

- https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.6/configure-splunk-licenses/types-of-splunk-enterprise-licenses

- https://help.splunk.com/en/splunk-enterprise/get-started/install-and-upgrade/10.6/install-a-splunk-enterprise-license/install-a-license

### Infrastructure sources

- https://help.splunk.com/en/splunk-enterprise/administer/install-and-upgrade/10.6/plan-your-splunk-enterprise-installation/installation-overview

- https://help.splunk.com/en/splunk-enterprise/get-started/deployment-capacity-manual/10.6/performance-reference/reference-hardware

- https://help.splunk.com/en/splunk-enterprise/splunk-validated-architectures/splunk-platform-indexing-and-search/smartstore-for-splunk-platform


### Buyer diligence


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

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


- Marketplace delivery: Documented. Splunk publishes an AWS AMI with a 60-day Enterprise trial. Continued paid software use requires an external license; the AMI is not a paid Enterprise subscription or proof of software-spend commitment credit. Verify its packaged version separately from upstream releases. Scope: Vendor-published AWS offer; procurement and application hosting are distinct. Source: https://aws.amazon.com/marketplace/pp/prodview-l6oos72bsyaks (reviewed 2026-11-16). Offer prodview-l6oos72bsyaks: Splunk; EC2 AMI with trial; commercial license purchased outside Marketplace; https://aws.amazon.com/marketplace/pp/prodview-l6oos72bsyaks.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Enterprise 10.6 documents SAML 2.0 SSO, supported IdP connectivity, role/realName/mail attributes and administrator change_authentication capability. Encrypted assertions can be decrypted when configured; this does not establish SCIM provisioning. Scope: Customer-managed Splunk Enterprise 10.6 SAML configuration. Source: https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/use-saml-as-an-authentication-scheme-for-single-sign-on/configure-single-sign-on-with-saml (reviewed 2026-11-16).

- SCIM provisioning: Documented. Enterprise 10.6 documents SCIM-based deletion of SAML users with a compatible Okta integration. Its release notes identify Entra ID de-provisioning as controlled availability. These sources establish scoped de-provisioning, not unrestricted SCIM user creation, updates or group synchronization. Scope: Splunk Enterprise 10.6 SAML user-removal workflow; identity-provider and availability conditions apply. Source: https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/use-saml-as-an-authentication-scheme-for-single-sign-on/configure-sso-with-okta-as-your-identity-provider (reviewed 2026-11-16). Supporting source: 10.6 controlled-availability Entra ID feature — https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.6/whats-new/welcome-to-splunk-enterprise-10.6.

- Compliance attestations: Documented. Splunk’s 10.6 guide identifies OpenSSL FIPS Provider certificate 4985 for FIPS 140-3. NIST lists that module as active, with sunset 2030-03-10 and approved-mode conditions. This is a cryptographic-module validation; deployment OS, mode, TLS and app prerequisites remain essential and it is not a blanket Splunk deployment attestation. Scope: Splunk 10.6 documented module plus NIST validation status checked 2026-11-16. Source: https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/establish-and-maintain-compliance-with-fips-and-common-criteria-in-splunk-enterprise/secure-splunk-enterprise-with-fips (reviewed 2026-11-16). Supporting source: NIST CMVP certificate 4985 — https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/4985.

- Security controls: Documented. FIPS mode requires a supported x86-64 OS running in FIPS mode, TLS 1.2+ between nodes and compatible apps. The guide lists the older FIPS 140-2 certificate as expired in September 2026; select the supported 140-3 path and validate the full configuration. Scope: Enterprise 10.6 FIPS configuration prerequisites; not automatic security or regulatory compliance. Source: https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/establish-and-maintain-compliance-with-fips-and-common-criteria-in-splunk-enterprise/secure-splunk-enterprise-with-fips (reviewed 2026-11-16).

- Air-gapped operation: Documented. Splunk explicitly offers Enterprise for private-cloud/on-premises deployment, including air-gapped environments. This establishes the vendor’s deployment option; the selected apps, license delivery, updates, trust material and data integrations still need a disconnected operating procedure. Scope: Commercial Splunk Enterprise deployment option; not Splunk Cloud or every add-on. Source: https://www.splunk.com/en_us/products/pricing.html (reviewed 2026-11-16).

- Deployment artifact / IaC: Documented. Splunk supplies operating-system-specific Enterprise installers. Select the required platform/version and verify the published checksum. The installation guide limits Docker to supported standalone and single-server uses; a download is not a complete distributed infrastructure template. Scope: Splunk Enterprise 10.6 installation guidance; topology and platform determine the artifact. Source: https://help.splunk.com/en/splunk-enterprise/administer/install-and-upgrade/10.6/plan-your-splunk-enterprise-installation/installation-overview (reviewed 2026-11-16). Supporting source: Enterprise packages and checksums — https://www.splunk.com/en_us/download/splunk-enterprise.html.

- Minimum footprint / sizing: Documented. The Enterprise 10.6 single-instance reference specifies 12 physical cores or 24 vCPU at 2 GHz+, 12 GB RAM and a 1 Gb NIC. Storage, search concurrency, ingest volume and distributed roles require separate sizing. Scope: S1 single-instance production reference; not a multi-tier total or operating-cost estimate. Source: https://help.splunk.com/en/splunk-enterprise/get-started/deployment-capacity-manual/10.6/performance-reference/reference-hardware (reviewed 2026-11-16).

- License pricing: Documented. Splunk Enterprise is proprietary software. Production customers purchase commercial end-user licenses based on indexed data volume or licensed infrastructure. Trial, developer and Free licenses are restricted alternatives and do not establish an open-source edition. Scope: Splunk Enterprise: software license terms; infrastructure and operating costs are separate. Source: https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.6/configure-splunk-licenses/types-of-splunk-enterprise-licenses (reviewed 2026-11-16). Supporting source: Edition and license conditions — https://help.splunk.com/en/splunk-enterprise/get-started/install-and-upgrade/10.6/install-a-splunk-enterprise-license/install-a-license.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Splunk Enterprise 10.6.1 was released October 16, 2026. The release page warns against Universal Forwarder 10.6.0, while SVD-2026-1101 names 10.6.1 and maintained parallel branches as forthcoming November fix targets. Scope: Splunk Enterprise 10.6 release line; advance notice is not a final CVE matrix. Source: https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.6/whats-new/welcome-to-splunk-enterprise-10.6 (reviewed 2026-11-18). Supporting source: November 2026 advance notice — https://advisory.splunk.com/advisories/SVD-2026-1101.







## SPRUCE (Open Source GreenOps)

Open-source batch enrichment of cloud usage with estimated energy, water and carbon metrics.

- Listing: https://launchinyourcloud.com/directory/spruce-greenops/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: serverless
- License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Package / binary installer
- Architecture: SPRUCE Spark job on AWS EMR Serverless reading and writing customer S3 data.
- 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://opensourcegreenops.cloud/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

This is a job-based analytics tool, not an environmental-compliance records system. Provider names in billing inputs do not add hosting badges. Match the Java/Spark application to the supported EMR release rather than treating the script's defaults as universal.

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

The reviewed path executes Spark jobs through AWS EMR Serverless, rather than a persistent application server.


### Category fit

- data-analytics: Open-source batch enrichment of cloud usage with estimated energy, water and carbon metrics.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://opensourcegreenops.cloud/howto/emr/ (checked 2026-11-19). 


### Cloud deployment evidence

- AWS EMR Guide (aws): https://opensourcegreenops.cloud/howto/emr/
  SPRUCE Spark job on AWS EMR Serverless reading and writing customer S3 data. This is a job-based analytics tool, not an environmental-compliance records system. Provider names in billing inputs do not add hosting badges. Match the Java/Spark application to the supported EMR release rather than treating the script's defaults as universal.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes jnioche, dpol1, nikhiln64, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/DigitalPebble/spruce/graphs/contributors

- Upstream project: https://github.com/DigitalPebble/spruce

### Sources

- AWS EMR Guide: https://opensourcegreenops.cloud/howto/emr/

- launchEMR.sh: https://github.com/DigitalPebble/spruce/blob/main/scripts/launchEMR.sh

- Apache-2.0: https://github.com/DigitalPebble/spruce/blob/main/LICENSE

- Releases: https://github.com/DigitalPebble/spruce/releases

### Licensing sources

- https://github.com/DigitalPebble/spruce/blob/main/LICENSE

### Infrastructure sources

- https://opensourcegreenops.cloud/howto/emr/


### 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 reviewed SPRUCE guide describes a Spark/EMR job, not a user-facing application login. AWS IAM, EMR Studio or notebook access does not establish an independent SPRUCE user-SSO feature; select the actual operator interface and identity boundary if interactive access is required. Scope: SPRUCE batch-job identity versus optional operator UI remains unconfirmed. Source: https://github.com/DigitalPebble/spruce/blob/1.5/docs/src/howto/emr.md (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The reviewed source supplies deployment configuration for SPRUCE Spark job on AWS EMR Serverless reading and writing customer S3 data. Set organization-specific secrets, networking, storage and compatible image versions before use. Scope: SPRUCE (Open Source GreenOps) deployment example; review the full linked installation instructions. Source: https://github.com/DigitalPebble/spruce/blob/main/scripts/launchEMR.sh (reviewed 2026-11-19). Deployment artifact: https://github.com/DigitalPebble/spruce/blob/main/scripts/launchEMR.sh. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The 1.5 EMR Serverless example submits a Spark job with one 1-core/4-GB driver and one 1-core/4-GB executor. Those are example job allocations, not a permanent-host minimum; billing-report volume, Spark overhead, temporary/output storage, execution time and concurrency drive actual capacity. Scope: SPRUCE 1.5 EMR Serverless reference job configuration. Source: https://github.com/DigitalPebble/spruce/blob/1.5/docs/src/howto/emr.md (reviewed 2026-11-21).

- License pricing: Documented. Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: SPRUCE (Open Source GreenOps); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/DigitalPebble/spruce/blob/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## Starburst Enterprise

Commercial distributed SQL and analytics platform deployed by Helm into customer-operated Kubernetes.

- Listing: https://launchinyourcloud.com/directory/starburst-enterprise/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Starburst Enterprise license and entitled registry access required.
- Licensing model: commercial-only
- Installation: Authenticated Starburst Enterprise Helm charts on EKS, AKS or GKE
- Architecture: Coordinator, worker and supporting services on Kubernetes with external service database and data-source connections.
- Operations: Customer manages Kubernetes, dedicated node capacity, storage, networking, service database, catalogs, secrets, backups and upgrades.
- Product website: https://www.starburst.io/platform/starburst-enterprise/
- 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 Starburst Enterprise, not Starburst Galaxy or the upstream Trino project. Production Kubernetes deployment requires entitled images and charts, a Starburst license, dedicated adequately sized nodes and an external service database. The older AWS CloudFormation path is deprecated and is not presented as the current installation method. Starburst's November advisory fixes critical Brotli CVE-2026-111497 in 482-e.6, 480-e.13, 479-e.20, and 477-e.24. Upgrade the installed maintained branch to its fixed or later patch.

Starburst Enterprise requires a commercial license and access to authenticated container and Helm registries. The open-source Trino project is separate.

Starburst Enterprise runs persistent coordinator, worker and supporting containers on Kubernetes and requires an external service database plus production capacity planning.


### Category fit

- data-analytics: Distributed SQL query, federation and governed analytics across cloud data stores and lakehouse systems.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.starburst.io/latest/k8s/requirements.html (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.starburst.io/latest/k8s/requirements.html (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.starburst.io/latest/k8s/requirements.html (checked 2026-11-17). 


### Cloud deployment evidence

- Starburst Enterprise Kubernetes deployment on EKS, AKS and GKE (aws, azure, gcp): https://docs.starburst.io/latest/k8s/requirements.html
  Starburst documents its Enterprise Helm deployment on customer Kubernetes and explicitly supports Amazon EKS, Azure AKS and Google GKE with provider-specific ecosystem guidance. Customers operate the cluster and data services.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Starburst Enterprise on Kubernetes: https://docs.starburst.io/latest/k8s.html

- Kubernetes requirements: https://docs.starburst.io/latest/k8s/requirements.html

- AWS ecosystem and deployment: https://docs.starburst.io/latest/ecosystems/aws/

- Microsoft Azure ecosystem: https://docs.starburst.io/latest/ecosystems/microsoft/

- Google Cloud ecosystem: https://docs.starburst.io/latest/ecosystems/google/

- Starburst security advisories: https://docs.starburst.io/security/advisories.html

### Licensing sources

- https://docs.starburst.io/latest/k8s.html

### Infrastructure sources

- https://docs.starburst.io/latest/k8s.html

- https://docs.starburst.io/latest/k8s/requirements.html


### Buyer diligence


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

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


- Marketplace delivery: Documented. SEP documents AWS EKS Marketplace deployment and Google Cloud Marketplace subscriptions. The Google Click to Deploy path is recommended only for small proofs of concept; prefer the documented command-line customization path. Scope: Starburst Enterprise Marketplace, not Galaxy SaaS. Source: https://docs.starburst.io/latest/ecosystems/aws/marketplace/ (reviewed 2026-11-17). Supporting source: Google Cloud Marketplace limits and support — https://docs.starburst.io/latest/ecosystems/google/gcp-marketplace.html.

- Cloud commitment eligibility: Sources checked — unresolved. SEP Marketplace deployment is documented, but the reviewed procurement guides do not establish qualifying fees and contract-specific commitment treatment. Galaxy claims were excluded. Scope: Reviewed public evidence for Starburst Enterprise; unresolved within this edition/deployment. Source: https://docs.starburst.io/latest/ecosystems/aws/marketplace/ (reviewed 2026-11-17).

- Single sign-on: Documented. SEP supports SAML 2.0 SSO configured on the coordinator. TLS is required; authentication is separate from the access-control rules that grant data permissions. Scope: Starburst Enterprise, not Galaxy or upstream Trino. Source: https://docs.starburst.io/latest/security/saml.html (reviewed 2026-11-17).

- SCIM provisioning: Documented. SEP documents SCIM user/group synchronization with its internal group provider and a configured secret token. Configure a supported external provider and network reachability; authorization to data remains separate. Scope: SEP self-managed SCIM configuration. Source: https://docs.starburst.io/latest/security/scim-provisioning.html (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed Starburst Enterprise 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.starburst.io/latest/security/authentication-types.html (reviewed 2026-11-17).

- Security controls: Documented. Authentication requires TLS/HTTPS and a shared secret. Apply the selected authenticator plus access-control system and restrict coordinator exposure; provisioning identities does not grant unrestricted data access. Current advisory review: Starburst documents fixed builds for critical Brotli CVE-2026-111497. Upgrade the installed maintained branch to its fixed or later patch. Scope: Starburst Enterprise authentication requirements Fixed in 482-e.6, 480-e.13, 479-e.20, and 477-e.24; branch-specific affected ranges follow the vendor advisory.. Source: https://docs.starburst.io/security/advisories.html (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://docs.starburst.io/latest/security/authentication-types.html.

- Air-gapped operation: Sources checked — unresolved. SEP requires entitled images/charts and a licence. The reviewed Kubernetes requirements do not establish complete isolated licence renewal, connector dependencies and upgrades. Scope: Reviewed public evidence for Starburst Enterprise; unresolved within this edition/deployment. Source: https://docs.starburst.io/latest/k8s/requirements.html (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. SEP supplies licensed Helm charts and images in its Harbor registry. Obtain customer credentials and configure the coordinator, workers and backend database; the legacy AWS CloudFormation path is deprecated. Scope: Supported Kubernetes SEP installation. Source: https://docs.starburst.io/latest/k8s/requirements.html (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. The Kubernetes guide specifies identical dedicated nodes with 16–64 cores and 64–256 GB RAM, one coordinator/worker per node, plus an externally managed service database. This is substantially more than a small general-purpose app cluster. Scope: SEP Kubernetes node requirements; workload and HA counts still need design. Source: https://docs.starburst.io/latest/k8s/requirements.html (reviewed 2026-11-17).

- License pricing: Documented. Starburst Enterprise requires a commercial license and access to authenticated container and Helm registries. The open-source Trino project is separate. Scope: Starburst Enterprise: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://docs.starburst.io/latest/k8s.html (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Confirm coordinator failover, worker concurrency, backend database, data-source storage and licensed cores. The documented dedicated-node minimum does not by itself establish the required HA query architecture. 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.starburst.io/latest/k8s/requirements.html (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. The version policy distinguishes LTS and STS. The reviewed table lists 482-e.x LTS through 2027-08-31 and 483-e STS from October 2026 until the next release; select a supported line and review breaking changes. Scope: SEP support policy and month-level release table; not a patch timestamp. Source: https://docs.starburst.io/latest/versions.html (reviewed 2026-11-17).




### Security and lifecycle reviews

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

- Starburst Enterprise Brotli security update (security-advisory): Starburst documents fixed builds for critical Brotli CVE-2026-111497. Scope: Fixed in 482-e.6, 480-e.13, 479-e.20, and 477-e.24; branch-specific affected ranges follow the vendor advisory. Conditions: Exposure depends on the bundled Brotli decoder and reachable processing paths. Action: Upgrade the installed maintained branch to its fixed or later patch. Source: https://docs.starburst.io/security/advisories.html; reviewed 2026-11-18.




## StarRocks

Open-source distributed analytical database deployed through the StarRocks Kubernetes Operator.

- Listing: https://launchinyourcloud.com/directory/starrocks/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0
- Licensing model: open-source
- Installation: Official Kubernetes Operator on Amazon EKS or Google GKE
- Architecture: Distributed front-end, back-end and compute-node services with persistent disks or object storage
- Operations: Customer manages Kubernetes, StarRocks custom resources, storage, networking, credentials, scaling, backups, monitoring and upgrades.
- Product website: https://www.starrocks.io/
- Source review: 2026-11-18; cloud review: 2026-11-15; licensing review: 2026-11-15; infrastructure review: 2026-11-15

### Scope and qualifications

This entry covers the open-source StarRocks deployment, not a vendor-hosted service. Size front-end, back-end and compute nodes for the selected shared-nothing or shared-data topology, and validate object-storage, persistent-volume and upgrade compatibility. StarRocks 4.1.7 escapes lookup_string arguments, runs its internal query as the caller, encodes web-console output, validates proc_profile input, restricts diagnostic endpoints to administrators, masks credentials, and updates security dependencies. Upstream does not publish a CVE, severity, or universal affected range for these fixes.

The reviewed StarRocks repository uses the Apache License 2.0.

StarRocks runs persistent distributed database services and operator-managed pods on Kubernetes.


### Category fit

- data-analytics: Provides a distributed analytical database and query engine for real-time analytics, data warehousing and lakehouse workloads.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.starrocks.io/docs/deployment/sr_operator/ (checked 2026-11-15). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.starrocks.io/docs/deployment/sr_operator/ (checked 2026-11-15). 


### Cloud deployment evidence

- StarRocks Operator on EKS or GKE (aws, gcp): https://docs.starrocks.io/docs/deployment/sr_operator/
  StarRocks documents creating an Amazon EKS or Google GKE cluster, installing its Kubernetes Operator and deploying a StarRocks cluster through customer-applied custom resources.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.


### Community and maintenance

StarRocks release 4.1.7 was published on November 3, 2026, and the public contributor history records sustained upstream participation. This evidence does not establish commercial support for a particular cloud configuration.

Reviewed 2026-11-15.

- Reviewed release 4.1.7: https://github.com/StarRocks/starrocks/releases/tag/4.1.7

- Upstream contributor history: https://github.com/StarRocks/starrocks/graphs/contributors

### Sources

- StarRocks Kubernetes Operator: https://docs.starrocks.io/docs/deployment/sr_operator/

- StarRocks deployment overview: https://docs.starrocks.io/docs/deployment/

- StarRocks Apache 2.0 license: https://github.com/StarRocks/starrocks/blob/main/LICENSE.txt

- StarRocks 4.1.7 release: https://github.com/StarRocks/starrocks/releases/tag/4.1.7

- Upstream contributor history: https://github.com/StarRocks/starrocks/graphs/contributors

- StarRocks 4.1 release notes: https://docs.starrocks.io/releasenotes/release-4.1/

### Licensing sources

- https://github.com/StarRocks/starrocks/blob/main/LICENSE.txt

### Infrastructure sources

- https://docs.starrocks.io/docs/deployment/sr_operator/

- https://docs.starrocks.io/docs/deployment/


### 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. From 3.5.0, StarRocks documents OAuth2 authorization-code sign-in for its Web UI and JDBC clients. Client plugins or a browser authentication step are needed for SQL access. Configure the security integration and validate identity-provider/client compatibility; this is distinct from LDAP binds. Scope: StarRocks 3.5+ Web UI and SQL-client OAuth2. Source: https://docs.starrocks.io/docs/administration/user_privs/authentication/oauth2_authentication/ (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: StarRocks 4.1.7 hardens lookup_string SQL handling, web-console output, diagnostic endpoints, credential display, and security dependencies. Upgrade to 4.1.7 or a later maintained build and review diagnostic endpoint permissions. Scope: Upstream 4.1.7 release notes; no CVE, severity, or universal affected-version range is specified.. Source: https://github.com/StarRocks/starrocks/releases/tag/4.1.7 (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official Kubernetes Operator automates StarRocks cluster deployment and management on an existing cluster. Its documentation covers EKS and GKE and identifies it as a level-2 operator; it does not provision every underlying dependency or establish production sizing. Scope: StarRocks Kubernetes Operator documentation, Latest-4.1 branch. Source: https://docs.starrocks.io/docs/deployment/sr_operator/ (reviewed 2026-11-16).

- Minimum footprint / sizing: Documented. Alibaba Cloud recommends FE nodes with at least 8 cores/16 GB and BE nodes with at least 16 cores/64 GB for its EMR StarRocks deployment. It recommends three data replicas and workload-specific disk sizing. This provider-specific production guidance is not a universal minimum for upstream, shared-data or other-cloud installations. Scope: Alibaba EMR StarRocks node recommendation; other deployment modes differ. Source: https://www.alibabacloud.com/help/en/emr/emr-on-ecs/user-guide/faq-about-starrocks (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/StarRocks/starrocks/main/LICENSE.txt (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. StarRocks 4.1.7 has an upstream release date of October 26, 2026, and was published on GitHub November 3. It includes SQL, web-console, diagnostic-endpoint, credential-masking, and dependency hardening. Scope: Upstream StarRocks 4.1 release. Source: https://github.com/StarRocks/starrocks/releases/tag/4.1.7 (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- StarRocks 4.1.7 security hardening (security-advisory): StarRocks 4.1.7 hardens lookup_string SQL handling, web-console output, diagnostic endpoints, credential display, and security dependencies. Scope: Upstream 4.1.7 release notes; no CVE, severity, or universal affected-version range is specified. Conditions: Applicability depends on the affected functions, web and diagnostic endpoints, and bundled dependencies. Action: Upgrade to 4.1.7 or a later maintained build and review diagnostic endpoint permissions. Source: https://github.com/StarRocks/starrocks/releases/tag/4.1.7; reviewed 2026-11-18.




## StorageMAP by Datadobi

Commercial unstructured-data inventory, search and governance software for customer cloud infrastructure.

- Listing: https://launchinyourcloud.com/directory/datadobi-storagemap/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- 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: VM image
- Architecture: StorageMAP application AMI with access to selected file and object stores.
- 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://aws.amazon.com/marketplace/pp/prodview-5sy467mv6fspk
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The product inventories and manages unstructured files and objects. It does not reconstruct every retired application's business semantics. The reviewed offer uses storage-capacity subscription licensing; infrastructure and operating costs remain separate.

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

StorageMAP application AMI with access to selected file and object stores. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- legacy-system-archive-access: Commercial unstructured-data inventory, search and governance software for customer cloud infrastructure.

- data-analytics: Commercial unstructured-data inventory, search and governance software for customer cloud infrastructure.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://aws.amazon.com/marketplace/pp/prodview-5sy467mv6fspk (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Marketplace AMI (aws): https://aws.amazon.com/marketplace/pp/prodview-5sy467mv6fspk
  StorageMAP application AMI with access to selected file and object stores. The product inventories and manages unstructured files and objects. It does not reconstruct every retired application's business semantics. The reviewed offer uses storage-capacity subscription licensing; infrastructure and operating costs remain separate.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS Marketplace Terms: https://aws.amazon.com/marketplace/pp/prodview-5sy467mv6fspk

- Datadobi AWS News: https://datadobi.com/post_news/datadobi-now-available-in-aws-marketplace/

- StorageMAP DAG Launch (2026-09-24): https://datadobi.com/post_news/datadobi-adds-data-access-governance-to-storagemap-enabling-enterprises-to-answer-the-critical-question-who-has-access-to-what/

### Licensing sources

- https://aws.amazon.com/marketplace/pp/prodview-5sy467mv6fspk

### Infrastructure sources

- https://aws.amazon.com/marketplace/pp/prodview-5sy467mv6fspk


### 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: Documented. The reviewed AWS offer delivers Amazon Machine Image (AMI) from Datadobi. Its package version is 26.6; verify the contained application and required entitlements separately. Scope: StorageMAP by Datadobi selected AWS public offer; infrastructure and support charges are separate. Source: https://aws.amazon.com/marketplace/pp/prodview-5sy467mv6fspk (reviewed 2026-11-19). Offer prodview-5sy467mv6fspk: Datadobi; Amazon Machine Image (AMI); package 26.6; https://aws.amazon.com/marketplace/pp/prodview-5sy467mv6fspk.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The reviewed vendor offer and access-governance announcement do not establish SAML/OIDC for StorageMAP administrator login. Analysing source-file users and permissions is different from federating the management application; obtain the selected release identity configuration. Scope: StorageMAP administrator-user federation remains unconfirmed. Source: https://aws.amazon.com/marketplace/pp/prodview-5sy467mv6fspk (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor AWS offer delivers StorageMAP as an x86 AMI, with software/support activation and deployment-specific configuration. Choose the supported offer version and networking, protect credentials and size scan workers/database/storage separately; the AMI is a delivery artifact, not a complete migration or HA design. Scope: Datadobi vendor AWS AMI delivery; selected release and workload configuration required. Source: https://aws.amazon.com/marketplace/pp/prodview-5sy467mv6fspk (reviewed 2026-11-21). Deployment artifact: https://aws.amazon.com/marketplace/pp/prodview-5sy467mv6fspk. Artifact reference: Offer version 26.6 reviewed on this date.

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed vendor offer does not supply complete production CPU/RAM/storage sizing. Obtain capacity for scanned object/file counts, connectors, processing concurrency, database/index growth and recovery; managed data terabytes alone do not determine the control-plane footprint. Scope: StorageMAP production sizing remains unconfirmed. Source: https://aws.amazon.com/marketplace/pp/prodview-5sy467mv6fspk (reviewed 2026-11-21).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: StorageMAP by Datadobi; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://aws.amazon.com/marketplace/pp/prodview-5sy467mv6fspk (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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







## Tableau Server

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

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

### Scope and qualifications

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

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

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


### Category fit

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

### Deployment boundaries


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

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

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

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


### Cloud deployment evidence

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

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

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

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


### Sources

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

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

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

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

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

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

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

### Licensing sources

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

### Infrastructure sources

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

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


### Buyer diligence


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

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


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

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

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

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

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

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

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

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

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

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

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

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







## ThingsBoard Self-Hosted

Source-available IoT device, telemetry and dashboard platform.

- Listing: https://launchinyourcloud.com/directory/thingsboard/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Business Source License 1.1 for ThingsBoard 4.4+; production grants and a licence key are subject to device, server and attribution conditions.
- Licensing model: source-available
- Installation: Kubernetes manifests
- Architecture: ThingsBoard monolith or microservices, database and messaging/cache services on the documented cloud VM/Kubernetes paths.
- 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://thingsboard.io
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Current 4.4+ code uses BUSL-1.1 with a usage grant; do not label it Apache-licensed Community merely because older versions used that licence. Device monitoring and energy dashboards do not establish regulated environmental filings or evidence workflows.

Business Source License 1.1 for ThingsBoard 4.4+; production grants and a licence key are subject to device, server and attribution conditions.

ThingsBoard monolith or microservices, database and messaging/cache services on the documented cloud VM/Kubernetes paths. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- data-analytics: Source-available IoT device, telemetry and dashboard platform.

- observability: Source-available IoT device, telemetry and dashboard platform.

### Deployment boundaries


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

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

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


### Cloud deployment evidence

- AWS (aws): https://thingsboard.io/docs/installation/aws/
  ThingsBoard monolith or microservices, database and messaging/cache services on the documented cloud VM/Kubernetes paths. Current 4.4+ code uses BUSL-1.1 with a usage grant; do not label it Apache-licensed Community merely because older versions used that licence. Device monitoring and energy dashboards do not establish regulated environmental filings or evidence workflows.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure (azure): https://thingsboard.io/docs/installation/azure/
  ThingsBoard monolith or microservices, database and messaging/cache services on the documented cloud VM/Kubernetes paths. Current 4.4+ code uses BUSL-1.1 with a usage grant; do not label it Apache-licensed Community merely because older versions used that licence. Device monitoring and energy dashboards do not establish regulated environmental filings or evidence workflows.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- GCP (gcp): https://thingsboard.io/docs/installation/gcp/
  ThingsBoard monolith or microservices, database and messaging/cache services on the documented cloud VM/Kubernetes paths. Current 4.4+ code uses BUSL-1.1 with a usage grant; do not label it Apache-licensed Community merely because older versions used that licence. Device monitoring and energy dashboards do not establish regulated environmental filings or evidence workflows.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS: https://thingsboard.io/docs/installation/aws/

- Azure: https://thingsboard.io/docs/installation/azure/

- GCP: https://thingsboard.io/docs/installation/gcp/

- v4.4 Unification: https://thingsboard.io/docs/pe/installation/upgrade-from-ce/

- Smart Energy: https://thingsboard.io/use-cases/smart-energy/

- BUSL-1.1: https://github.com/thingsboard/thingsboard/blob/master/LICENSE

- Releases: https://github.com/thingsboard/thingsboard/releases

### Licensing sources

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

### Infrastructure sources

- https://thingsboard.io/docs/installation/aws/

- https://thingsboard.io/docs/installation/azure/

- https://thingsboard.io/docs/installation/gcp/


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The ThingsBoard guide configures OAuth2/OIDC clients and domain-specific callbacks for Web UI or mobile login, including Keycloak, Okta, Azure and social providers. Configure issuer/JWKS, trusted claims, tenant/customer mapping and account-creation policy. Device transport credentials and API tokens are separate; the selected release licence still applies. Scope: Current self-hosted ThingsBoard user login and identity mapping, distinct from device authentication. Source: https://thingsboard.io/docs/user-guide/oauth-2-support/ (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 current Ubuntu guide installs a versioned application package, Java and database, then initializes the schema and starts the service. AWS guidance separates single-VM, EKS monolith and microservice topologies. Select matching application/manifests and dependencies, replace sample secrets, and configure TLS, persistence, mail and licence activation. Scope: Official native package installation; AWS reference topologies and provider images have separate versions. Source: https://thingsboard.io/docs/user-guide/install/ubuntu/ (reviewed 2026-11-20). Deployment artifact: https://github.com/thingsboard/thingsboard/releases/tag/v4.4.0.2. Artifact reference: v4.4.0.2 application package release; match provider image/manifests separately. Supporting source: Official AWS deployment choices — https://thingsboard.io/docs/installation/aws/.

- Minimum footprint / sizing: Documented. The Ubuntu guide distinguishes a 1-core/4 GB/20 GB proof of concept from small production at 2 cores/8 GB/50 GB SSD and a larger starting tier at 4+ cores/16+ GB/100+ GB SSD. Queue/database choices add resources; the heap example is not total host capacity. Device/message rate, retention and HA require separate sizing. Scope: Current single-host tier recommendations; not a 1 TB microservice/HA sizing guarantee. Source: https://thingsboard.io/docs/user-guide/install/ubuntu/ (reviewed 2026-11-20).

- License pricing: Edition-dependent. Business Source License 1.1 for ThingsBoard 4.4+; production grants and a licence key are subject to device, server and attribution conditions. Scope: ThingsBoard Self-Hosted; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/thingsboard/thingsboard/blob/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## TiDB Community Self-Hosted

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

- Listing: https://launchinyourcloud.com/directory/tidb-community/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp, azure, alibaba
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0.
- Licensing model: open-source
- Installation: TiDB Operator and versioned Kubernetes resources on EKS/GKE/AKS; the Alibaba ACK Terraform recipe has older development/test version constraints; optional Techlatest AWS single-VM bundle is separately packaged and does not supply the Operator HA topology
- Architecture: TiDB, PD and TiKV services on customer Kubernetes node pools with persistent storage, or a separately reviewed third-party single-VM bundle; optional analytics and monitoring depend on the deployment.
- Operations: Customer manages the chosen Kubernetes cluster or VM, operating system/node pools, persistent storage, networking, database identities, backups, monitoring, upgrades, scaling and database operations.
- Product website: https://www.pingcap.com/tidb/
- Source review: 2026-11-18; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

This entry covers TiDB Community, not TiDB Cloud. AKS has a complete current guide even though the deployment FAQ omits it; that difference does not negate the documented path. The ACK guide is an older development/test recipe, while the current FAQ still names ACK. Match operator/database versions and validate production permissions, storage and HA before use. An alternative Techlatest AWS image packages TiDB OSS with Grafana/Prometheus on one VM. Package 1.0.2 does not identify the database components’ versions and is not an HA cluster or PingCAP support entitlement. Do not transfer Operator sizing, offline procedures or the upstream v8.5.8 snapshot to this image.

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

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


### Category fit

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

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

### Deployment boundaries


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

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

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

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


### Cloud deployment evidence

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

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

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

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

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


### Community and maintenance

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

Reviewed 2026-11-18.

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

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

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

### Sources

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

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

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

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

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

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

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

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

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

### Licensing sources

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

### Infrastructure sources

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

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


### Buyer diligence


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

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


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

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

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

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

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

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

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

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

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

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

- Operating cost estimate: Sources checked — unresolved. Define SQL QPS, transaction mix, concurrency, indexes, TiKV replication, usable versus raw 1 TB, compaction headroom, TiFlash/TiCDC needs, monitoring and recovery targets. Price EKS and stateful nodes/storage across failure domains after benchmarking; the user count alone does not size this distributed database. The seller’s single-VM bundle does not provide the requested HA architecture. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://docs.pingcap.com/tidb/stable/hardware-and-software-requirements/ (reviewed 2026-11-18). Supporting source: Current AWS Linux EC2 rates; workload/topology still required — https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json. Supporting source: Storage performance and charging inputs — https://aws.amazon.com/ebs/pricing/. Supporting source: Single-VM price/topology is a different cost scope — https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4.

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




### Security and lifecycle reviews

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

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




## Trino

Distributed SQL engine for querying data lakes and federated enterprise data sources.

- Listing: https://launchinyourcloud.com/directory/trino/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream Trino.
- Licensing model: open-source
- Installation: Deploy the official server tarball on Linux hosts and configure coordinator, worker and catalog settings.
- Architecture: Customer-operated Java coordinator and worker processes connected to configured data sources
- Operations: Customer manages worker capacity, catalogs, credentials, TLS, query policies, logs and version compatibility.
- Product website: https://trino.io/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The reviewed current deployment documentation requires a supported Java runtime. Data stays in its configured source systems; querying a remote catalog can cross account or network boundaries.

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

Customer-operated Java coordinator and worker processes connected to configured data sources. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- data-analytics: Distributed SQL query engine that analyzes data across configured catalogs and data sources; it does not replace those databases or object stores.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://trino.io/episodes/31.html (checked 2026-11-12). 


### Cloud deployment evidence

- Trino project deployment walkthrough on Amazon EKS (aws): https://trino.io/episodes/31.html
  The project walkthrough creates an EKS cluster and installs the Trino Helm chart into it. The published example includes older Kubernetes and tooling versions; use currently supported versions and review production configuration. This is self-operated Trino, not an EMR or Starburst service.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The Trino Software Foundation supports a volunteer-contributed project. The official release index records multiple 2026 releases, and its user directory describes named production users.

Reviewed 2026-11-10.

- Foundation and governance: https://trino.io/docs/current/appendix/legal-notices.html

- Current release history: https://trino.io/docs/current/release.html

- Named user directory: https://trino.io/users.html

### Sources

- Official installation and runtime: https://trino.io/docs/current/installation/deployment.html

- Upstream project and capabilities: https://github.com/trinodb/trino

- Current upstream license: https://trino.io/docs/current/appendix/legal-notices.html

- Coordinator, workers and catalogs: https://trino.io/docs/current/overview/concepts.html

### Licensing sources

- https://trino.io/docs/current/appendix/legal-notices.html

### Infrastructure sources

- https://trino.io/docs/current/installation/deployment.html


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The coordinator supports OAuth 2.0 authentication with OIDC discovery configuration. Configure HTTPS, client credentials and the compatible browser/CLI flow; this is not automatic identity propagation to every connected database. Scope: Trino coordinator authentication; connector authorization remains separate. Source: https://trino.io/docs/current/security/oauth2.html (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 server tarball is installed on supported Linux hosts with separate coordinator/worker/catalog configuration. The current guide requires a specific supported Java runtime; matching the Trino release and Java version is essential. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://trino.io/docs/current/installation/deployment.html (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The current deployment guide recommends production memory allocations above 32 GB per node and typically assigns 70–85% of node RAM to the JVM. Coordinators, workers, query concurrency, connectors and spill storage determine the cluster size. The sample 16-GB heap configuration is not a total production or HA minimum. Scope: Trino 484 node/JVM guidelines; topology and workload require sizing. Source: https://trino.io/docs/current/installation/deployment.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. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/trinodb/trino/master/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

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






