Data & analytics on Azure

Data processing, reporting and business intelligence.

34 documented options on Microsoft Azure. Provider coverage reflects reviewed evidence, not an exhaustive compatibility claim.

ListingDocumented cloudsDeployment and infrastructureLicensingInstallationOperations and limitations
ActivityInfo (Self-Managed Server)AzureCustomer-operated
Servers / containers
Commercial Only

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

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

The Azure guides describe a single application writer. Extra nodes can improve rescheduling but do not make the SQLite application active-active. Program data models and donor/grant reporting require configuration; this is not a packaged grant-award workflow.

  • Azure Web App — ActivityInfo container with its SQLite data on Azure App Service/Azure Files or a single AKS pod and managed disk. The Azure guides describe a single application writer. Extra nodes can improve rescheduling but do not make the SQLite application active-active. Program data models and donor/grant reporting require configuration; this is not a packaged grant-award workflow.

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

Cloud evidence reviewed 2026-11-19

Airbyte Self-ManagedAWS, Azure, Google Cloud, DigitalOceanCustomer-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 evidence

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

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

  • Airbyte-published v0.30.25 DigitalOcean Droplet image — 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.

    Marketplace offer · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-13

Apache Doris Self-HostedAWS, Alibaba Cloud, AzureCustomer-operated
Servers / containers
Open Source / Open Core

Apache License 2.0 for the core project; optional third-party components can carry separate or incompatible licenses.

Doris Operator on AWS EKS or Alibaba ACK/ACS, or cloudimg’s Azure VM image; pin application/operator/image versions separatelyCustomer 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.
Scope and evidence

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 on Amazon EKS — 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.

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

  • Apache Doris on Alibaba Cloud ACK/ACS — 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.

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

  • cloudimg Apache Doris VM in a customer Azure subscription — 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.

    Third party package · Reviewed 2026-11-18 · Version: Guide application 4.0.6; Azure image latest must be resolved. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-18

Apache DruidAWS, Azure, Google CloudCustomer-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 evidence

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

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

Cloud evidence reviewed 2026-11-12

Azure Trusted Research EnvironmentAzureCustomer-operated
Servers / containers
Open Source / Open Core

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

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

Airlock implements data import/export review gates; it does not supply an institution's IRB or grant-review decision process. This is an engineering reference implementation with workspace templates, not an automatically certified or supported research service.

  • Setup Instructions — Customer Azure core services, workspaces, researcher compute, storage and Airlock workflows provisioned through Terraform. Airlock implements data import/export review gates; it does not supply an institution's IRB or grant-review decision process. This is an engineering reference implementation with workspace templates, not an automatically certified or supported research service.

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

Cloud evidence reviewed 2026-11-19

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

Commercial Cloudera subscription with cloud infrastructure charges paid separately.

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

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

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

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

Cloud evidence reviewed 2026-11-17

Databricks classic computeAWS, Azure, Google CloudShared operations · vendor control plane
Servers / containers
Commercial Only

Commercial

Cloud-specific workspace provisioningThe vendor manages the control plane. Your team configures classic compute, cloud resources and policies.
Scope and evidence

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

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

  • Databricks classic compute 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.

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

  • Databricks classic compute 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.

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

Cloud evidence reviewed 2026-11-12

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

Apache License 2.0.

Official Helm deployment on EKS, AKS or GKECustomer manages Kubernetes, stateful dependencies, networking, secrets, backups, scaling, ingestion, and upgrades, including search-backend compatibility and per-version breaking-change actions.
Scope and evidence

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 Amazon EKS — The official guide deploys DataHub to a customer EKS cluster and describes optional AWS managed services for stateful dependencies.

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

  • DataHub on Azure Kubernetes Service — The official guide deploys DataHub to a customer AKS cluster and documents the required infrastructure and Helm installation.

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

  • DataHub on Google Kubernetes Engine — The official guide deploys DataHub to a customer GKE cluster with Helm and provider-managed dependency options.

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

Cloud evidence reviewed 2026-11-14

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

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

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

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

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

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

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

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

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

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

Cloud evidence reviewed 2026-11-16

Dremio Self-ManagedAWS, Azure, Google CloudCustomer-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 evidence

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

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

  • Dremio-tested EKS, AKS and GKE 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.

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

Cloud evidence reviewed 2026-11-13

EarthSoft EQuIS Enterprise — Self-HostedAzureCustomer-operated
Servers / containers
Commercial Only

Proprietary EarthSoft server and Active Client Access licenses; external viewer/service-provider terms differ

Licensed Enterprise installation on Windows Server/IIS and SQL Server, or the documented Azure Web App deploymentCustomer operates application hosting, database, network access, backups, user roles, licenses and upgrades. Obtain the installers and supported build details from EarthSoft.
Scope and evidence

This entry covers self-hosted Enterprise rather than EarthSoft-operated EQuIS Online. The official Azure installation guide deploys into client-managed Azure Web Apps and configures the database and licenses. Internal users and externally exposed viewers have different licensing arrangements. Review integrations and choose a supported build before installation.

  • EQuIS Enterprise application installation on Azure — EarthSoft documents creation and configuration of an Azure Web App and deployment of the licensed EQuIS Enterprise application package, rather than only an Azure SQL database. This is the customer-hosted Enterprise path; obtain the compatible package and required licenses from EarthSoft.

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

Cloud evidence reviewed 2026-11-12

Elastic Cloud EnterpriseAWS, Azure, Google CloudCustomer-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 hostsCustomer manages cloud instances, Linux and container runtime compatibility, XFS storage, networking, DNS, certificates, host maintenance, capacity, backups, upgrades and licensing.
Scope and evidence

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

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

Cloud evidence reviewed 2026-11-15

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

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

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

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

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

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

Cloud evidence reviewed 2026-11-17

Esri ArcGIS Enterprise (BYOL)AWS, AzureCustomer-operated
Servers / containers
Commercial Only

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

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

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.

  • AWS Cloud Builder — 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.

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

  • Azure Cloud Builder — 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.

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

Cloud evidence reviewed 2026-11-19

Estuary BYOCAWS, Azure, Google CloudVendor-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 evidence

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 AWS — The documented cross-account IAM role uses an external ID and grants AmazonEC2FullAccess.

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

  • Estuary BYOC on Azure — The guide adds Estuary's deployment application and grants a role scoped to the customer's subscription.

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

  • Estuary BYOC on Google Cloud — The guide asks for project-level Editor access for Estuary's controller principal.

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

Cloud evidence reviewed 2026-11-21

Finmars CE (Community Edition)AWS, AzureCustomer-operated
Servers / containers
Open Source / Open Core

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

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

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

  • AWS Marketplace — 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.

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

  • Install Finmars Platform | Finmars — 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.

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

Cloud evidence reviewed 2026-11-19

IBM Cognos Analytics Certified ContainersAWS, Azure, Google Cloud, IBM CloudCustomer-operated
Servers / containers
Commercial Only

Commercial, separately licensed Cognos Analytics Certified Containers entitlement.

Install IBM's entitled Cognos Analytics Helm chart on customer-managed KubernetesCustomer manages Kubernetes, databases, authentication, storage, ingress, capacity, backups and upgrades; IBM support scope varies by platform.
Scope and evidence

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 — IBM documents the certified Cognos containers on Amazon EKS, Microsoft AKS and Google GKE. Non-OpenShift support is narrower than the OpenShift delivery model.

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

  • Cognos Certified Containers on IBM Cloud Kubernetes Service — IBM's Cognos ingress framework explicitly names IBM Cloud Kubernetes Service alongside EKS, AKS and GKE. The customer operates the cluster and external dependencies.

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

Cloud evidence reviewed 2026-11-17

IBM Planning Analytics CartridgeIBM Cloud, AWS, Azure, Google CloudCustomer-operated
Servers / containers
Commercial Only

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

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

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

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

Cloud evidence reviewed 2026-11-19

Jedox Unmanaged Private CloudAzureCustomer-operated
Servers / containers
Commercial Only

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

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

The vendor's tested Azure deployment is distinct from Jedox SaaS. General multientity planning does not establish a packaged private-equity workflow. Validate the documented Kubernetes, gateway, storage and licence requirements for the selected chart.

  • Unmanaged Private Cloud — Vendor-provided Jedox Helm chart and persistent services on customer Azure Kubernetes infrastructure. The vendor's tested Azure deployment is distinct from Jedox SaaS. General multientity planning does not establish a packaged private-equity workflow. Validate the documented Kubernetes, gateway, storage and licence requirements for the selected chart.

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

Cloud evidence reviewed 2026-11-19

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

Commercial KNIME Business Hub license or Marketplace software subscription required.

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

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

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

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

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

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

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

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

Cloud evidence reviewed 2026-11-16

Matomo On-PremiseAWS, Azure, Google Cloud, Alibaba CloudCustomer-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 imageCustomer manages hosting, upgrades, security, backups, tracking configuration and scheduled report processing.
Scope and evidence

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

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

Cloud evidence reviewed 2026-11-12

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

Open-source and commercial options

Docker image or Java JARYour team manages hosting, upgrades and the application database.
Scope and evidence

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

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

Cloud evidence reviewed 2026-11-12

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

Apache License 2.0.

Official Helm charts on EKS, AKS or GKECustomer manages Kubernetes, database, search, ingestion orchestration, secrets, backups, scaling and upgrades.
Scope and evidence

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 Amazon EKS — The official guide deploys OpenMetadata with Helm on a customer EKS cluster and documents AWS database and search dependencies.

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

  • OpenMetadata on Azure Kubernetes Service — The official guide deploys OpenMetadata with Helm on a customer AKS cluster and documents Azure database and search dependencies.

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

  • OpenMetadata on Google Kubernetes Engine — The official guide deploys OpenMetadata with Helm on GKE. It explicitly notes that GKE Autopilot is incompatible with the documented Elasticsearch configuration.

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

Cloud evidence reviewed 2026-11-14

Qlik Sense Enterprise Client-ManagedAWS, Azure, Google CloudCustomer-operated
Servers / containers
Commercial Only

Commercial Qlik Sense Enterprise license.

Qlik Sense Enterprise on Windows using provider-specific AWS, Azure or Google Cloud VM guidanceCustomer manages Windows hosts, networking, certificates, identity, repository database, shared storage, load balancing, backups, scaling, upgrades and license activation.
Scope and evidence

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 AWS — Qlik documents preparing customer Amazon EC2 Windows infrastructure and installing Qlik Sense Enterprise on Windows.

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

  • Qlik Sense Enterprise on Azure — Qlik documents preparing Azure virtual machines, resource groups and networking before installing Qlik Sense Enterprise on Windows.

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

  • Qlik Sense Enterprise on Google Cloud — Qlik documents preparing Google Compute Engine Windows instances and installing Qlik Sense Enterprise on Windows.

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

Cloud evidence reviewed 2026-11-15

QuestDB Open Source Self-HostedAWS, Azure, Google CloudCustomer-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 EnterpriseCustomer manages VM and OS, data disks, networking, authentication, backups, monitoring, upgrades and capacity.
Scope and evidence

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

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

  • QuestDB on 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.

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

  • QuestDB on Google Cloud — QuestDB documents deployment to customer Compute Engine with separate durable storage.

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

  • Vendor-published QuestDB Open Source AWS AMI — 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.

    Marketplace offer · Reviewed 2026-11-18 · Scope: QuestDB Open Source · Version: AMI package 10.1.0. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-18

RADAR-base (ManagementPortal & Study Platform)AWS, AzureCustomer-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.

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

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.

  • AWS EKS Terraform — 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.

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

  • Azure Terraform — 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.

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

Cloud evidence reviewed 2026-11-19

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

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

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

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

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

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

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

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

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

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

Cloud evidence reviewed 2026-11-17

Snowplow CDI Private Managed CloudAWS, Azure, Google CloudVendor-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 evidence

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 AWS — Snowplow uses delegated cross-account access to install and operate the pipeline in the customer's selected AWS region.

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

  • Snowplow Private Managed Cloud on Azure — The Azure guide uses an application service principal and role scoped to the customer's subscription.

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

  • Snowplow Private Managed Cloud on Google Cloud — The customer enables billing and grants installation and maintenance roles in its Google Cloud project.

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

Cloud evidence reviewed 2026-11-21

Splunk EnterpriseAWS, Azure, Google CloudCustomer-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 evidence

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

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

  • Customer-managed Splunk Enterprise BYOL architecture — 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.

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

Cloud evidence reviewed 2026-11-16

Starburst EnterpriseAWS, Azure, Google CloudCustomer-operated
Servers / containers
Commercial Only

Commercial Starburst Enterprise license and entitled registry access required.

Authenticated Starburst Enterprise Helm charts on EKS, AKS or GKECustomer manages Kubernetes, dedicated node capacity, storage, networking, service database, catalogs, secrets, backups and upgrades.
Scope and evidence

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

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

Cloud evidence reviewed 2026-11-17

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

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

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

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

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

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

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

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

Cloud evidence reviewed 2026-11-17

Tableau ServerAWS, Azure, Google Cloud, Alibaba CloudCustomer-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 pathsCustomer manages the virtual machines, operating system, Tableau services, identity, networking, storage, backups, upgrades and availability.
Scope and evidence

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 Amazon Web Services — Tableau documents customer-managed EC2 installation as the production-ready AWS path. The provider guide is archived, but Tableau states the deployment remains supported.

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

  • Tableau Server on Microsoft Azure — Tableau documents customer-managed Azure VM installation as the production-ready path. The provider guide is archived, but Tableau states the deployment remains supported.

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

  • Tableau Server on Google Cloud — Tableau documents production-ready self-deployment on customer Google Compute Engine virtual machines with BYOL operation. The provider guide is archived.

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

  • Tableau Server on Alibaba Cloud — Tableau documents production-ready self-deployment on customer Alibaba Elastic Compute Service virtual machines with BYOL operation. The provider guide is archived.

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

Cloud evidence reviewed 2026-11-17

ThingsBoard Self-HostedAWS, Azure, Google CloudCustomer-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 manifestsCustomer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope and evidence

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.

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

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

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

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

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

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

Cloud evidence reviewed 2026-11-19

TiDB Community Self-HostedAWS, Google Cloud, Azure, Alibaba CloudCustomer-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 topologyCustomer 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 evidence

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 Amazon EKS — PingCAP documents customer EKS node pools, storage and TiDB Operator deployment.

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

  • TiDB on Google Kubernetes Engine — PingCAP documents customer GKE node pools, persistent disks and TiDB Operator deployment.

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

  • TiDB Community 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.

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

  • TiDB on Alibaba Cloud ACK — 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.

    Vendor / upstream documentation · Reviewed 2026-11-18 · Version: TiDB Operator guide v1.4. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Techlatest TiDB OSS single-VM bundle in customer EC2 — 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.

    Third party package · Reviewed 2026-11-18 · Scope: Repackaged open-source TiDB bundle · Version: Seller package 1.0.2; embedded database versions unreported. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-18

Deployment evidence and category fit

ActivityInfo (Self-Managed Server)

Commercial self-managed data collection, relational records and program-reporting platform.

The Azure guides describe a single application writer. Extra nodes can improve rescheduling but do not make the SQLite application active-active. Program data models and donor/grant reporting require configuration; this is not a packaged grant-award workflow.

  • Azure Web App ↗

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

    ActivityInfo container with its SQLite data on Azure App Service/Azure Files or a single AKS pod and managed disk. The Azure guides describe a single application writer. Extra nodes can improve rescheduling but do not make the SQLite application active-active. Program data models and donor/grant reporting require configuration; this is not a packaged grant-award workflow.

Cloud evidence reviewed 2026-11-19. Full listing and qualifications

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 Doris Self-Hosted

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

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.

  • cloudimg Apache Doris VM in a customer Azure subscription ↗

    Third party package · Reviewed 2026-11-18 · Version: Guide application 4.0.6; Azure image latest must be resolved. Vendor support commitment: not assessed; confirm the selected release and contract.

    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.

Cloud evidence reviewed 2026-11-18. 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

Azure Trusted Research Environment

Open-source reference platform for isolated research workspaces and controlled data movement.

Airlock implements data import/export review gates; it does not supply an institution's IRB or grant-review decision process. This is an engineering reference implementation with workspace templates, not an automatically certified or supported research service.

  • Setup Instructions ↗

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

    Customer Azure core services, workspaces, researcher compute, storage and Airlock workflows provisioned through Terraform. Airlock implements data import/export review gates; it does not supply an institution's IRB or grant-review decision process. This is an engineering reference implementation with workspace templates, not an automatically certified or supported research service.

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 ↗

    Provider guide · 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 Azure Kubernetes Service ↗

    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 AKS cluster and documents the required infrastructure and Helm installation.

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 Azure ↗

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

    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.

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

EarthSoft EQuIS Enterprise — Self-Hosted

Environmental data quality checks, reporting, visualizations and configurable dashboards; its scope is environmental and geotechnical data rather than general-purpose BI.

This entry covers self-hosted Enterprise rather than EarthSoft-operated EQuIS Online. The official Azure installation guide deploys into client-managed Azure Web Apps and configures the database and licenses. Internal users and externally exposed viewers have different licensing arrangements. Review integrations and choose a supported build before installation.

  • EQuIS Enterprise application installation on Azure ↗

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

    EarthSoft documents creation and configuration of an Azure Web App and deployment of the licensed EQuIS Enterprise application package, rather than only an Azure SQL database. This is the customer-hosted Enterprise path; obtain the compatible package and required licenses from EarthSoft.

Cloud evidence reviewed 2026-11-12. 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

Esri ArcGIS Enterprise (BYOL)

Commercial customer-operated geospatial application and analytics platform.

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.

  • Azure Cloud Builder ↗

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

    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.

Cloud evidence reviewed 2026-11-19. 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 Azure ↗

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

    The guide adds Estuary's deployment application and grants a role scoped to the customer's subscription.

Cloud evidence reviewed 2026-11-21. Full listing and qualifications

Finmars CE (Community Edition)

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

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.

  • Install Finmars Platform | Finmars ↗

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

    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.

Cloud evidence reviewed 2026-11-19. 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

Jedox Unmanaged Private Cloud

Commercial customer-operated planning, consolidation and business-reporting platform.

The vendor's tested Azure deployment is distinct from Jedox SaaS. General multientity planning does not establish a packaged private-equity workflow. Validate the documented Kubernetes, gateway, storage and licence requirements for the selected chart.

  • Unmanaged Private Cloud ↗

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

    Vendor-provided Jedox Helm chart and persistent services on customer Azure Kubernetes infrastructure. The vendor's tested Azure deployment is distinct from Jedox SaaS. General multientity planning does not establish a packaged private-equity workflow. Validate the documented Kubernetes, gateway, storage and licence requirements for the selected chart.

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 Azure Marketplace ↗

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

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

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 Azure Kubernetes Service ↗

    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 a customer AKS cluster and documents Azure database and search dependencies.

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 Azure ↗

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

    Qlik documents preparing Azure virtual machines, resource groups and networking before 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 Azure ↗

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

    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.

Cloud evidence reviewed 2026-11-18. Full listing and qualifications

RADAR-base (ManagementPortal & Study Platform)

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

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.

  • Azure Terraform ↗

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

    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.

Cloud evidence reviewed 2026-11-19. 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 Azure ↗

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

    Official SAS Terraform provisions customer Azure resources including AKS, storage and optional PostgreSQL, 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 Azure ↗

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

    The Azure guide uses an application service principal and role scoped to the customer's subscription.

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

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 Microsoft Azure ↗

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

    Tableau documents customer-managed Azure VM installation as the production-ready path. The provider guide is archived, but Tableau states the deployment remains supported.

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.

  • Azure ↗

    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 Community on Azure AKS ↗

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

    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.

Cloud evidence reviewed 2026-11-18. Full listing and qualifications

Deployment and procurement checks

Private offers
Microsoft Marketplace private offers negotiate product pricing and terms. Confirm the exact offer, billing scope and benefit eligibility rather than assuming all purchases count toward a commitment. Provider source ↗ · Reviewed 2026-11-14
Private connectivity
Azure Private Link uses private endpoints in a virtual network for supported Azure and partner services. Check application support, DNS and service availability. Provider source ↗ · Reviewed 2026-11-14
Cross-tenant operations
Azure Lighthouse supports delegated management with customer-controlled scopes and actions. Agree the roles, audit requirements and revocation plan for the selected vendor. Provider source ↗ · Reviewed 2026-11-14
Government environments
Azure Government uses isolated US datacenters and networks. Commercial Azure documentation alone does not establish a product path or compliance in Government. 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: Subscription and resource group. Access: Microsoft Entra identities and Azure RBAC. Network: Virtual Network (VNet).

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