Data & analytics on Google Cloud
Data processing, reporting and business intelligence.
28 documented options on Google Cloud. Provider coverage reflects reviewed evidence, not an exhaustive compatibility claim.
Read this page as JSON or Markdown.
| Listing | Documented clouds | Deployment and infrastructure | Licensing | Installation | Operations and limitations |
|---|---|---|---|---|---|
| Airbyte Self-Managed | AWS, Azure, Google Cloud, DigitalOcean | Customer-operated Servers / containers | Source Available Elastic License 2.0 for the Airbyte platform; connector and component licenses vary. Enterprise and Cloud offerings use separate commercial terms. | Official Helm chart for current Kubernetes deployments; cloud VMs are also documented. DigitalOcean separately lists a legacy 1-Click Droplet image. | Customer manages Kubernetes or VM capacity, the metadata database, object storage, secrets, connector images, network access, backups and upgrades.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-13 |
| Apache Druid | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Open Source / Open Core Apache License 2.0 for upstream Apache Druid. | Run the official server distribution with bin/start-druid; distributed production deployments require the documented cluster services and storage configuration. | Customer manages cluster sizing, ingestion, metadata and deep storage, access controls, backups and upgrades.Scope and evidenceThe 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.
Cloud evidence reviewed 2026-11-12 |
| Cloud Carbon Footprint | Google Cloud | Customer-operated Servers / containers | Open Source / Open Core Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. | Application platform deployment | 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.Scope and evidenceThe named hosting path is Google App Engine; reading AWS/Azure billing does not establish app deployment there. Estimates and dashboards are not audited emissions or regulatory-compliance certifications. The moving latest release tag is not an immutable application version.
Cloud evidence reviewed 2026-11-19 |
| Cloudera on Cloud | AWS, Azure, Google Cloud | Shared operations · vendor control plane Servers / containers | Commercial Only Commercial Cloudera subscription with cloud infrastructure charges paid separately. | Register the customer cloud environment and credentials, then provision Cloudera workload services through the control plane | Cloudera operates the service control plane; the customer owns cloud resources, credentials, data governance, network integration, workload sizing and shared operational responsibilities.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-17 |
| Databricks classic compute | AWS, Azure, Google Cloud | Shared operations · vendor control plane Servers / containers | Commercial Only Commercial | Cloud-specific workspace provisioning | The vendor manages the control plane. Your team configures classic compute, cloud resources and policies.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-12 |
| DataHub OSS | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Open Source / Open Core Apache License 2.0. | Official Helm deployment on EKS, AKS or GKE | Customer manages Kubernetes, stateful dependencies, networking, secrets, backups, scaling, ingestion, and upgrades, including search-backend compatibility and per-version breaking-change actions.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-14 |
| Dataiku DSS Cloud Stacks | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial Dataiku license or license token required for the full Cloud Stacks capabilities. | AWS CloudFormation, Azure ARM template or Google Cloud Infrastructure Manager with Terraform | Customer manages cloud accounts, Fleet Manager, IAM identities, networking, VM and Kubernetes capacity, storage, TLS, backups, upgrades and license configuration.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-16 |
| Dremio Self-Managed | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Open Source / Open Core Apache License 2.0 for Dremio Community; Dremio Enterprise uses separate commercial terms. | Community on Docker or Kubernetes; Enterprise on Kubernetes using vendor-tested EKS, AKS or GKE environments. | Customer manages Kubernetes or container capacity, storage, security, scaling, upgrades, backups and integration with data sources.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-13 |
| Elastic Cloud Enterprise | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial Elastic Cloud Enterprise license required after the trial. | Official ECE installation script on prepared AWS, Azure or Google Cloud Linux hosts | Customer manages cloud instances, Linux and container runtime compatibility, XFS storage, networking, DNS, certificates, host maintenance, capacity, backups, upgrades and licensing.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-15 |
| Elastic Cloud on Kubernetes | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Source Available Elastic License 2.0 distribution with free Basic capabilities; Enterprise licensing unlocks additional features and support. | Official ECK Helm chart or Kubernetes manifests on EKS, AKS or GKE | Customer manages Kubernetes, storage, resource sizing, security, snapshots, upgrades and availability; Elastic licensing controls advanced features and support.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-17 |
| Estuary BYOC | AWS, Azure, Google Cloud | Vendor-operated BYOC Servers / containers | Commercial Only Commercial BYOC under an annual Enterprise agreement with custom pricing. | Arrange Enterprise BYOC onboarding and grant the documented permissions in a separate AWS account, Azure subscription, or Google Cloud project. | 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.Scope and evidenceThe 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.
Cloud evidence reviewed 2026-11-21 |
| IBM Cognos Analytics Certified Containers | AWS, Azure, Google Cloud, IBM Cloud | Customer-operated Servers / containers | Commercial Only Commercial, separately licensed Cognos Analytics Certified Containers entitlement. | Install IBM's entitled Cognos Analytics Helm chart on customer-managed Kubernetes | Customer manages Kubernetes, databases, authentication, storage, ingress, capacity, backups and upgrades; IBM support scope varies by platform.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-17 |
| IBM Planning Analytics Cartridge | IBM Cloud, AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. | Kubernetes manifests | 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.Scope and evidenceCurrent 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.
Cloud evidence reviewed 2026-11-19 |
| KNIME Business Hub | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial KNIME Business Hub license or Marketplace software subscription required. | Official AWS, Azure or Google Cloud Marketplace virtual-machine image | Customer manages the cloud account, virtual machine, networking, DNS, TLS, identity, storage, backups, capacity, upgrades and Business Hub license.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-16 |
| Matomo On-Premise | AWS, Azure, Google Cloud, Alibaba Cloud | Customer-operated Servers / containers | Open Source / Open Core GPLv3-or-later core; premium plugins use separate commercial EULA and subscription terms | PHP web-server installation or official Docker image | Customer manages hosting, upgrades, security, backups, tracking configuration and scheduled report processing.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-12 |
| Metabase Self-Hosted | AWS, Azure, Google Cloud, DigitalOcean | Customer-operated Servers / containers | Open Source / Open Core Open-source and commercial options | Docker image or Java JAR | Your team manages hosting, upgrades and the application database.Scope and evidenceMetabase 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.
Cloud evidence reviewed 2026-11-12 |
| OpenMetadata | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Open Source / Open Core Apache License 2.0. | Official Helm charts on EKS, AKS or GKE | Customer manages Kubernetes, database, search, ingestion orchestration, secrets, backups, scaling and upgrades.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-14 |
| Qlik Sense Enterprise Client-Managed | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial Qlik Sense Enterprise license. | Qlik Sense Enterprise on Windows using provider-specific AWS, Azure or Google Cloud VM guidance | Customer manages Windows hosts, networking, certificates, identity, repository database, shared storage, load balancing, backups, scaling, upgrades and license activation.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-15 |
| QuestDB Open Source Self-Hosted | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Open Source / Open Core QuestDB Open Source is Apache License 2.0; QuestDB Enterprise is separately proprietary. | Vendor AWS OSS AMI 10.1.0, or customer VM binary/systemd/container installation; validate the AMI OS lifecycle; Azure Marketplace packaging is Enterprise | Customer manages VM and OS, data disks, networking, authentication, backups, monitoring, upgrades and capacity.Scope and evidenceQuestDB 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.
Cloud evidence reviewed 2026-11-18 |
| SAS Viya Platform | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial SAS Viya licensing; deployment assets and a JWT license are delivered for the customer's software order. | Provision EKS, AKS or GKE with SAS Terraform projects, then deploy Kubernetes manifests generated through Kustomize and SAS automation | Customer manages Kubernetes, networking, ingress, storage, PostgreSQL, identity, sizing, backups, platform updates and licensed deployment assets.Scope and evidenceThe 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.
Cloud evidence reviewed 2026-11-17 |
| Snowplow CDI Private Managed Cloud | AWS, Azure, Google Cloud | Vendor-operated BYOC Servers / containers | Commercial Only Commercial Private Managed Cloud plan with quote-based pricing. | Provide a dedicated AWS account, Azure subscription, or Google Cloud project and grant the permissions in the provider guide. | Snowplow provisions, monitors, patches, and upgrades the pipeline. The customer supplies the cloud environment, access permissions, and data destination.Scope and evidenceSnowplow 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.
Cloud evidence reviewed 2026-11-21 |
| Splunk Enterprise | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial end-user license based on data volume or infrastructure; limited trial, developer and Free licenses have separate restrictions. | Splunk Enterprise installation package on supported Linux or Windows hosts; Docker is limited to supported standalone and single-server topologies. | Customer manages compute, networking, storage, data inputs, certificates, clustering, capacity, backups, license configuration, monitoring and upgrades.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-16 |
| Starburst Enterprise | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial Starburst Enterprise license and entitled registry access required. | Authenticated Starburst Enterprise Helm charts on EKS, AKS or GKE | Customer manages Kubernetes, dedicated node capacity, storage, networking, service database, catalogs, secrets, backups and upgrades.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-17 |
| StarRocks | AWS, Google Cloud | Customer-operated Servers / containers | Open Source / Open Core Apache License 2.0 | Official Kubernetes Operator on Amazon EKS or Google GKE | Customer manages Kubernetes, StarRocks custom resources, storage, networking, credentials, scaling, backups, monitoring and upgrades.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-15 |
| Strategy Enterprise in Your Cloud | AWS, Azure, Google Cloud, STACKIT | Vendor-operated BYOC Servers / containers | Commercial Only Commercial Strategy Enterprise subscription; customer-cloud deployment is not available with the Standard plan. | Vendor-assisted, fully managed deployment into the customer's licensed AWS, Azure Google Cloud or STACKIT environment | Strategy administers and maintains the platform; the customer supplies the cloud environment, data sources, identity, network approvals and shared governance responsibilities.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-17 |
| Tableau Server | AWS, Azure, Google Cloud, Alibaba Cloud | Customer-operated Servers / containers | Commercial Only Commercial Tableau Server product-key licensing with user-, core- or subscription-based entitlements. | Native server installer on customer virtual machines; optional AWS CloudFormation, Azure Resource Manager or marketplace BYOL paths | Customer manages the virtual machines, operating system, Tableau services, identity, networking, storage, backups, upgrades and availability.Scope and evidenceTableau'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.
Cloud evidence reviewed 2026-11-17 |
| ThingsBoard Self-Hosted | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Source Available Business Source License 1.1 for ThingsBoard 4.4+; production grants and a licence key are subject to device, server and attribution conditions. | Kubernetes manifests | 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.Scope and evidenceCurrent 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.
Cloud evidence reviewed 2026-11-19 |
| TiDB Community Self-Hosted | AWS, Google Cloud, Azure, Alibaba Cloud | Customer-operated Servers / containers | Open Source / Open Core Apache License 2.0. | 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 | Customer manages the chosen Kubernetes cluster or VM, operating system/node pools, persistent storage, networking, database identities, backups, monitoring, upgrades, scaling and database operations.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-18 |
Deployment evidence and category fit
Airbyte Self-Managed
Moves data between APIs, databases, files, warehouses and lakes using customer-operated connectors and synchronization jobs.
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.
- Airbyte self-managed deployment on named cloud providers ↗
Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Cloud evidence reviewed 2026-11-13. Full listing and qualifications
Apache Druid
Real-time OLAP database for SQL analysis of ingested streaming and batch data; this is an analytics engine rather than a dashboard authoring application.
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 Druid cloud deployment FAQ ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Cloud evidence reviewed 2026-11-12. Full listing and qualifications
Cloud Carbon Footprint
Open-source cloud-usage, energy and carbon-estimation application.
The named hosting path is Google App Engine; reading AWS/Azure billing does not establish app deployment there. Estimates and dashboards are not audited emissions or regulatory-compliance certifications. The moving latest release tag is not an immutable application version.
- GCP App Engine ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Cloud Carbon Footprint API deployed to Google App Engine with configured cloud-usage data sources. The named hosting path is Google App Engine; reading AWS/Azure billing does not establish app deployment there. Estimates and dashboards are not audited emissions or regulatory-compliance certifications. The moving latest release tag is not an immutable application version.
Cloud evidence reviewed 2026-11-19. Full listing and qualifications
Cloudera on Cloud
Managed data engineering, warehousing and analytics services operate over data in customer cloud environments.
This entry covers Cloudera's public-cloud BYOC service, not a fully customer-operated software distribution. Workloads and data run in the customer's AWS, Azure or Google Cloud environment while Cloudera operates the control plane. Service availability and implementation details differ by provider, especially on Google Cloud, so confirm each required service before procurement. Cloudera November bulletins cover critical Brotli CVE-2026-111497 and compromised eMudhra certificates. Use the TSB matrices for the exact Runtime or Private Cloud Base component and fixed build rather than applying a generic platform version.
- Cloudera workloads in customer AWS, Azure and Google Cloud environments ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Cloud evidence reviewed 2026-11-17. Full listing and qualifications
Databricks classic compute
Data and AI platform with classic compute in your cloud environment.
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.
- Databricks classic compute architecture ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Cloud evidence reviewed 2026-11-12. Full listing and qualifications
DataHub OSS
Provides a metadata catalog, lineage graph, discovery and governance layer for connected data systems.
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 on Google Kubernetes Engine ↗
Vendor / upstream documentation · Reviewed 2026-11-14. Vendor support commitment: not assessed; confirm the selected release and contract.
The official guide deploys DataHub to a customer GKE cluster with Helm and provider-managed dependency options.
Cloud evidence reviewed 2026-11-14. Full listing and qualifications
Dataiku DSS Cloud Stacks
Provides customer-operated data preparation, analytics, visual workflows, elastic computation and governed data projects.
This entry covers Dataiku Cloud Stacks, not vendor-hosted Dataiku Cloud. Dataiku states that Cloud Stacks resources run in the customer's organization or tenant and that Dataiku does not have access to customer data. Fleet Manager requires broad cloud permissions and outbound access for images, license validation and configured identity services. Dataiku DSS Free Edition is separate from the fully featured licensed Cloud Stacks deployment.
- Dataiku DSS Cloud Stacks on Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Cloud evidence reviewed 2026-11-16. Full listing and qualifications
Dremio Self-Managed
Provides distributed SQL queries, semantic modeling and lakehouse analytics over customer-controlled data sources.
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 self-managed editions on AWS, Azure and Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- Dremio-tested EKS, AKS and GKE environments ↗
Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Cloud evidence reviewed 2026-11-13. Full listing and qualifications
Elastic Cloud Enterprise
Orchestrates self-managed Elasticsearch and Kibana deployments for search, analytical and data-exploration workloads.
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.
- Elastic Cloud Enterprise on public cloud hosts ↗
Vendor / upstream documentation · Reviewed 2026-11-15. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Cloud evidence reviewed 2026-11-15. Full listing and qualifications
Elastic Cloud on Kubernetes
Search, aggregations and Kibana visualizations support interactive analysis of indexed data.
This entry covers self-managed Elastic Cloud on Kubernetes, not Elastic Cloud Hosted or Elastic Cloud Enterprise. ECK automates application lifecycle but does not transfer cluster, storage, backup or upgrade responsibility to Elastic. The free Basic license and paid Enterprise feature set differ; optional Cloud Connect services create separate external dependencies. ECK 3.5.0 fixes service-token exposure, cross-namespace certificate injection, and retained cross-namespace credentials. CVE-2026-72648 has no workaround; after upgrading, rotate the affected service token as Elastic directs.
- Elastic Cloud on Kubernetes on EKS, AKS and GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Cloud evidence reviewed 2026-11-17. Full listing and qualifications
Estuary BYOC
Captures, transforms, and delivers data to analytical destinations through managed connectors.
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.
- Estuary BYOC on Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-21. Vendor support commitment: not assessed; confirm the selected release and contract.
The guide asks for project-level Editor access for Estuary's controller principal.
Cloud evidence reviewed 2026-11-21. Full listing and qualifications
IBM Cognos Analytics Certified Containers
Enterprise reporting, dashboards, governed analytics and data exploration delivered by customer-managed Cognos containers.
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.
- Cognos Certified Containers on EKS, AKS and GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
IBM documents the certified Cognos containers on Amazon EKS, Microsoft AKS and Google GKE. Non-OpenShift support is narrower than the OpenShift delivery model.
Cloud evidence reviewed 2026-11-17. Full listing and qualifications
IBM Planning Analytics Cartridge
Licensed self-managed planning, budgeting and multidimensional analytics cartridge.
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.
- Application deployment guidance ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Cloud evidence reviewed 2026-11-19. Full listing and qualifications
KNIME Business Hub
Provides governed collaboration, automation, execution and deployment for analytical workflows and data applications.
This entry covers customer-hosted KNIME Business Hub, not the open-source KNIME Analytics Platform or KNIME's managed Hub offering. Marketplace deployments use single VM images; production capacity, availability and recovery requirements must be assessed separately. Customer-provisioned Kubernetes installation requires the applicable Self Hosted Premium package. Cloud infrastructure charges are separate from KNIME software pricing.
- KNIME Business Hub on Google Cloud Marketplace ↗
Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.
KNIME documents launching Business Hub through Google Cloud Marketplace using a Google Compute VM image in the customer's project.
Cloud evidence reviewed 2026-11-16. Full listing and qualifications
Matomo On-Premise
Website analytics and reporting over collected visitor and event data; scope is web measurement rather than a general data warehouse.
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 named-cloud compatibility FAQ ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Cloud evidence reviewed 2026-11-12. Full listing and qualifications
Metabase Self-Hosted
Business intelligence and dashboards on your infrastructure.
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.
- Metabase production hosting compatibility ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Cloud evidence reviewed 2026-11-12. Full listing and qualifications
OpenMetadata
Catalogs data assets, lineage, quality, governance and observability metadata across connected systems.
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.
- OpenMetadata on Google Kubernetes Engine ↗
Vendor / upstream documentation · Reviewed 2026-11-14. Vendor support commitment: not assessed; confirm the selected release and contract.
The official guide deploys OpenMetadata with Helm on GKE. It explicitly notes that GKE Autopilot is incompatible with the documented Elasticsearch configuration.
Cloud evidence reviewed 2026-11-14. Full listing and qualifications
Qlik Sense Enterprise Client-Managed
Provides customer-operated business intelligence, associative analytics, dashboards and governed data applications.
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 on Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-15. Vendor support commitment: not assessed; confirm the selected release and contract.
Qlik documents preparing Google Compute Engine Windows instances and installing Qlik Sense Enterprise on Windows.
Cloud evidence reviewed 2026-11-15. Full listing and qualifications
QuestDB Open Source Self-Hosted
Supports time-series ingestion, SQL analytics and operational analysis of large event datasets.
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 on Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
QuestDB documents deployment to customer Compute Engine with separate durable storage.
Cloud evidence reviewed 2026-11-18. Full listing and qualifications
SAS Viya Platform
Enterprise data preparation, analytics, reporting and decisioning delivered by the customer-operated Viya platform.
The public SAS infrastructure repositories are Apache-licensed deployment tooling; SAS Viya itself is commercial software and requires licensed order assets and a JWT license. Kubernetes and PostgreSQL are mandatory. SAS states that its infrastructure-as-code projects satisfy most, not all, deployment requirements. The viya4-deployment project can patch the same manifest but does not move an installation to a different cadence, version or software offering. SAS November bulletins cover compromised eMudhra certificates and critical Brotli CVE-2026-111497 across specified Viya branches. Use the vendor matrices to identify the exact affected component and fixed maintenance level; do not treat a generic Viya version as sufficient.
- SAS Viya infrastructure on Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
Official SAS Terraform provisions customer Google Cloud resources including GKE, storage and optional Cloud SQL, after which the customer deploys licensed Viya assets.
Cloud evidence reviewed 2026-11-17. Full listing and qualifications
Snowplow CDI Private Managed Cloud
Collects, validates, enriches, and delivers behavioural event data to the customer's data warehouse or lake.
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.
- Snowplow Private Managed Cloud on Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-21. Vendor support commitment: not assessed; confirm the selected release and contract.
The customer enables billing and grants installation and maintenance roles in its Google Cloud project.
Cloud evidence reviewed 2026-11-21. Full listing and qualifications
Splunk Enterprise
Provides search, dashboards, reports and statistical analysis over indexed machine-generated data.
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 reference hardware for AWS, Azure and Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- Customer-managed Splunk Enterprise BYOL architecture ↗
Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Cloud evidence reviewed 2026-11-16. Full listing and qualifications
Starburst Enterprise
Distributed SQL query, federation and governed analytics across cloud data stores and lakehouse systems.
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 Kubernetes deployment on EKS, AKS and GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Cloud evidence reviewed 2026-11-17. Full listing and qualifications
StarRocks
Provides a distributed analytical database and query engine for real-time analytics, data warehousing and lakehouse workloads.
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.
- StarRocks Operator on EKS or GKE ↗
Vendor / upstream documentation · Reviewed 2026-11-15. Vendor support commitment: not assessed; confirm the selected release and contract.
StarRocks documents creating an Amazon EKS or Google GKE cluster, installing its Kubernetes Operator and deploying a StarRocks cluster through customer-applied custom resources.
Cloud evidence reviewed 2026-11-15. Full listing and qualifications
Strategy Enterprise in Your Cloud
Enterprise business intelligence, dashboards, reporting, embedded analytics and governed data exploration in a dedicated environment.
This entry covers the Strategy Enterprise customer-cloud option, not Strategy Standard in the vendor's managed environment. Strategy describes the service as fully managed despite its deployment in a customer-licensed AWS, Azure Google Cloud or STACKIT environment, so it is classified as BYOC rather than fully customer-operated. Confirm contract-specific account ownership, cloud-resource billing, service availability, support boundaries and cloud-commitment eligibility before procurement.
- Strategy Enterprise in customer-licensed AWS, Azure or Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Cloud evidence reviewed 2026-11-17. Full listing and qualifications
Tableau Server
Enterprise analytics, governed data exploration, dashboards and business-intelligence publishing on a customer-operated server.
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 on Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
Tableau documents production-ready self-deployment on customer Google Compute Engine virtual machines with BYOL operation. The provider guide is archived.
Cloud evidence reviewed 2026-11-17. Full listing and qualifications
ThingsBoard Self-Hosted
Source-available IoT device, telemetry and dashboard platform.
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.
- GCP ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Cloud evidence reviewed 2026-11-19. Full listing and qualifications
TiDB Community Self-Hosted
Supports scalable transactional and analytical SQL workloads on a customer-operated cluster.
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.
- TiDB on Google Kubernetes Engine ↗
Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
PingCAP documents customer GKE node pools, persistent disks and TiDB Operator deployment.
Cloud evidence reviewed 2026-11-18. Full listing and qualifications
Deployment and procurement checks
- Private offers
- Cloud Marketplace vendors can negotiate a private offer for a specified Cloud Billing account. Check duration, renewal terms and commitment treatment in the actual agreement. Provider source ↗ · Reviewed 2026-11-14
- Private connectivity
- Private Service Connect connects VPC consumers to supported managed or producer services. Confirm the actual product endpoint and network/DNS architecture. Provider source ↗ · Reviewed 2026-11-14
- External workload access
- Workload Identity Federation can grant external workloads scoped Google Cloud access without long-lived service-account keys. Validate the trust configuration and exact roles. Provider source ↗ · Reviewed 2026-11-14
- Regulated environments
- Assured Workloads applies control packages for residency and access boundaries. Confirm supported services, regions and the product deployment; it is not automatic product certification. Provider source ↗ · Reviewed 2026-11-14
For every provider, confirm marketplace/private-offer terms, commitment eligibility, regional service availability, private connectivity and any vendor access against your selected deployment. Provider capabilities do not automatically establish application support.
Plan this deployment
Account boundary: Google Cloud project. Access: IAM policies and service accounts. Network: VPC network.
Provider documentation ↗ · Guidance reviewed 2026-11-10. Confirm the application edition, region, support access, backup locations and operating responsibilities before choosing.
Compare this category across clouds · Search these listings · Compare 2–4 listings