
# Data & analytics on Alibaba Cloud

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

Canonical page: https://launchinyourcloud.com/clouds/alibaba/data-analytics/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


## Provider guidance

- Account boundary: Alibaba Cloud account and resource group
- Provider group: cloud-infrastructure
- Provider classification: Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Source: https://www.alibabacloud.com/help/en/resource-management/resource-group/user-guide/create-a-resource-group (checked 2026-11-20).
- Network: VPC
- Identity and access: Resource Access Management (RAM)
- Installation guidance: Resource Orchestration Service (ROS) templates or Terraform; review the required RAM permissions.
- Guidance source: https://www.alibabacloud.com/help/en/ros/developer-reference/integration-overview
- Guidance reviewed: 2026-11-10


### Dedicated connectivity

Express Connect provides a dedicated on-premises-to-VPC connection. Confirm the access point, routing and application region separately from the deployment package.
Source: https://www.alibabacloud.com/help/en/express-connect/product-overview/what-is-express-connect (reviewed 2026-11-14).

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

4 listings.


## Apache Doris Self-Hosted

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

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

### Scope and qualifications

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

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

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


### Category fit

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

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

### Deployment boundaries


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

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

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


### Cloud deployment evidence

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

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

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


### Community and maintenance

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

Reviewed 2026-11-18.

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

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

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

### Sources

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

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

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

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

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

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

### Licensing sources

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

### Infrastructure sources

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

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

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


### Buyer diligence


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

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


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

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

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

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

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

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

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

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

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

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

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

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







## Matomo On-Premise

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

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

### Scope and qualifications

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

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

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


### Category fit

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

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

### Deployment boundaries


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

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

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

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


### Cloud deployment evidence

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


### Sources

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

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

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

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

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

### Licensing sources

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

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

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

### Infrastructure sources

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


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

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

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

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

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

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

- Operating cost estimate: Not researched.

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







## Tableau Server

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

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

### Scope and qualifications

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

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

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


### Category fit

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

### Deployment boundaries


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

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

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

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


### Cloud deployment evidence

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

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

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

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


### Sources

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

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

- AWS deployment options: https://help.tableau.com/current/server/en-us/ts_aws_deployment_options.htm

- Azure deployment options: https://help.tableau.com/current/server/en-us/ts_azure_deployment_options.htm

- Google Cloud deployment options: https://help.tableau.com/current/server/en-us/ts_gcp_deployment_options.htm

- Alibaba Cloud deployment options: https://help.tableau.com/current/server/en-us/ts_alibaba_deployment_options.htm

- AWS prerequisites and licensing: https://help.tableau.com/current/server/en-us/ts_aws_prerequisites.htm

### Licensing sources

- https://help.tableau.com/current/server/en-us/ts_aws_prerequisites.htm

### Infrastructure sources

- https://help.tableau.com/current/server-linux/en-us/ts_tableau_server_cloud_overview.htm

- https://help.tableau.com/current/server/en-us/admin.htm


### Buyer diligence


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

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


- Marketplace delivery: Sources checked — unresolved. Archived AWS/Azure deployment guides identify Marketplace paths with production-readiness warnings. A current production-ready offer and entitlement were not confirmed. Scope: Reviewed public evidence for Tableau Server; unresolved within this edition/deployment. Source: https://help.tableau.com/current/server/en-us/ts_aws_deployment_options.htm (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. The reviewed Server deployment/licensing material does not establish a qualifying software Marketplace offer and buyer commitment treatment. Scope: Reviewed public evidence for Tableau Server; unresolved within this edition/deployment. Source: https://help.tableau.com/current/server/en-us/ts_aws_prerequisites.htm (reviewed 2026-11-17).

- Single sign-on: Documented. The Server SCIM guide explicitly supports site-specific SAML, TSM authentication and identity pools with version qualifications. Configure the chosen Server identity method and network reachability separately from provisioning. Scope: Server identity methods applicable to SCIM. Source: https://help.tableau.com/current/server/en-us/scim_config_online.htm (reviewed 2026-11-17).

- SCIM provisioning: Documented. Server supports site-level SCIM from 2025.3. Site-specific SAML works from 2025.3.0; TSM-configured authentication and identity pools require 2025.3.1+. Entra/Okta may need an on-premises provisioning connector through the server firewall. Scope: Tableau Server SCIM; not Tableau Cloud-only documentation. Source: https://help.tableau.com/current/server/en-us/scim_config_online.htm (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed Tableau Server material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage. Scope: Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited. Source: https://help.tableau.com/current/server/en-us/activate_off.htm (reviewed 2026-11-17).

- Security controls: Documented. The offline activation guide distinguishes product keys and ATR workflows. Protect transferred activation files and configure server identity and permissions separately; disconnected activation does not confer a security attestation. Scope: Server offline activation and licence handling. Source: https://help.tableau.com/current/server/en-us/activate_off.htm (reviewed 2026-11-17).

- Air-gapped operation: Sources checked — unresolved. Offline Server activation is documented, but this alone does not establish isolation for every connector, extension, update and identity dependency. Confirm the selected full deployment and licence workflow. Scope: Offline activation versus complete air-gapped operation. Source: https://help.tableau.com/current/server/en-us/activate_off.htm (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. Vendor cloud guides describe installing Server on customer VMs. Archived AWS/Azure Quick Start and Marketplace routes carry production-readiness warnings; use a supported self-deployment design and installation media. Scope: Customer-managed Server; archived automation warnings retained. Source: https://help.tableau.com/current/server/en-us/ts_aws_deployment_options.htm (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. The production single-node recommendation is 8 physical cores/16 vCPU, 128 GB RAM for 2022.3+ and at least 50 GB disk. Multi-node/HA design needs Tableau guidance; extracts, refresh scratch space and backups add storage. Scope: Production single-node recommendation, not the complete HA design. Source: https://help.tableau.com/current/server/en-us/server_hardware_min.htm (reviewed 2026-11-17).

- License pricing: Documented. Tableau Server requires a commercial product key and the applicable user-, core- or subscription-based entitlement. Tableau Cloud is a separate hosted offering. Scope: Tableau Server: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://help.tableau.com/current/server/en-us/ts_aws_prerequisites.htm (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Obtain the supported multi-node/HA design, user-role licence mix, extract/refresh workload, repository/file-store sizing and any Windows licences. Single-node production recommendations do not price an HA farm. A complete monthly operating estimate is not established. Scope: Requested planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA, average usage; missing workload metrics and commercial terms are explicit. Source: https://help.tableau.com/current/server/en-us/server_hardware_min.htm (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. Tableau Server 2026.3 was released 2026-10-23. The release page warns Windows Server 2016/Windows 10 users to review installation issue W-24614917 before upgrading; this is Server, not Tableau Cloud/Desktop. Scope: Tableau Server vendor release record. Source: https://www.tableau.com/support/releases/server/2026.3 (reviewed 2026-11-17).







## TiDB Community Self-Hosted

Open-source distributed SQL database with customer-operated cloud Kubernetes guides and a separately packaged third-party AWS VM option.

- Listing: https://launchinyourcloud.com/directory/tidb-community/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp, azure, alibaba
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0.
- Licensing model: open-source
- Installation: TiDB Operator and versioned Kubernetes resources on EKS/GKE/AKS; the Alibaba ACK Terraform recipe has older development/test version constraints; optional Techlatest AWS single-VM bundle is separately packaged and does not supply the Operator HA topology
- Architecture: TiDB, PD and TiKV services on customer Kubernetes node pools with persistent storage, or a separately reviewed third-party single-VM bundle; optional analytics and monitoring depend on the deployment.
- Operations: Customer manages the chosen Kubernetes cluster or VM, operating system/node pools, persistent storage, networking, database identities, backups, monitoring, upgrades, scaling and database operations.
- Product website: https://www.pingcap.com/tidb/
- Source review: 2026-11-18; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

This entry covers TiDB Community, not TiDB Cloud. AKS has a complete current guide even though the deployment FAQ omits it; that difference does not negate the documented path. The ACK guide is an older development/test recipe, while the current FAQ still names ACK. Match operator/database versions and validate production permissions, storage and HA before use. An alternative Techlatest AWS image packages TiDB OSS with Grafana/Prometheus on one VM. Package 1.0.2 does not identify the database components’ versions and is not an HA cluster or PingCAP support entitlement. Do not transfer Operator sizing, offline procedures or the upstream v8.5.8 snapshot to this image.

The TiDB repository is Apache-2.0 licensed. Managed TiDB Cloud services have separate terms.

TiDB runs persistent database/storage services on customer Kubernetes node pools, or as a separately packaged single-VM OSS bundle. The seller VM is not the Operator-based production HA topology.


### Category fit

- databases-vector: Provides a distributed SQL database with horizontally scaled storage and query services.

- data-analytics: Supports scalable transactional and analytical SQL workloads on a customer-operated cluster.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-aws-eks/ (checked 2026-11-18). Source: https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html (checked 2026-11-18). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-gcp-gke/ (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-azure-aks/ (checked 2026-11-18). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.pingcap.com/tidb-in-kubernetes/v1.4/deploy-on-alibaba-cloud/ (checked 2026-11-18). 


### Cloud deployment evidence

- TiDB on Amazon EKS (aws): https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-aws-eks/
  PingCAP documents customer EKS node pools, storage and TiDB Operator deployment.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- TiDB on Google Kubernetes Engine (gcp): https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-gcp-gke/
  PingCAP documents customer GKE node pools, persistent disks and TiDB Operator deployment.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- TiDB Community on Azure AKS (azure): https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-azure-aks/
  PingCAP provides a full AKS deployment guide with customer node pools, PD/TiKV/TiDB and monitoring manifests. A deployment guide establishes a documented path, not a commercial support contract.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- TiDB on Alibaba Cloud ACK (alibaba): https://docs.pingcap.com/tidb-in-kubernetes/v1.4/deploy-on-alibaba-cloud/
  PingCAP’s v1.4 guide deploys a full cluster into customer ACK using Terraform and TiDB Operator and is scoped to development/testing. The current deployment FAQ still names ACK; old Terraform/image examples need a current-version production review.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed. Versions: TiDB Operator guide v1.4.

- Techlatest TiDB OSS single-VM bundle in customer EC2 (aws): https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html
  The seller guide subscribes to exact AWS offer prodview-ddl3tqewcoko4 and launches into the customer region/VPC/EC2 account. TiDB and its monitoring interfaces run on the VM. This is a separately packaged single-node option, not the Kubernetes HA path; package 1.0.2 leaves embedded database versions unreported. Restrict SSH/RDP and set the documented initial credentials.
  Source type: third-party-package; reviewed: 2026-11-18; vendor support: not-assessed. Edition: Repackaged open-source TiDB bundle. Versions: Seller package 1.0.2; embedded database versions unreported.


### Community and maintenance

PingCAP maintains the Apache-licensed database and operator with public contribution activity and supported LTS releases. Its named customer case-study catalog demonstrates adoption, while TiDB Cloud stories are kept separate from Community cloud evidence.

Reviewed 2026-11-18.

- Official maintenance and adoption evidence: https://github.com/pingcap/tidb/releases/tag/v8.5.8

- Official maintenance and adoption evidence: https://www.pingcap.com/case-studies/

- Official maintenance and adoption evidence: https://docs.pingcap.com/tidb-in-kubernetes/stable/tidb-operator-overview/

### Sources

- TiDB Operator overview: https://docs.pingcap.com/tidb-in-kubernetes/stable/tidb-operator-overview/

- Deploy TiDB on AWS EKS: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-aws-eks/

- Deploy TiDB on Google Cloud GKE: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-gcp-gke/

- TiDB Apache 2.0 license: https://github.com/pingcap/tidb/blob/master/LICENSE

- TiDB Community on Azure AKS: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-azure-aks/

- TiDB on Alibaba Cloud ACK: https://docs.pingcap.com/tidb-in-kubernetes/v1.4/deploy-on-alibaba-cloud/

- Current TiDB deployment FAQ: https://docs.pingcap.com/tidb/stable/deploy-and-maintain-faq/

- Exact third-party TiDB OSS AWS image: https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4

- Seller customer-account VM deployment: https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html

### Licensing sources

- https://github.com/pingcap/tidb/blob/master/LICENSE

### Infrastructure sources

- https://docs.pingcap.com/tidb-in-kubernetes/stable/tidb-operator-overview/

- https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html


### Buyer diligence


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

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


- Marketplace delivery: Documented. Techlatest.net publishes TiDB with Grafana/Prometheus as AWS AMI prodview-ddl3tqewcoko4: a repackaged open-source single-VM bundle, package 1.0.2 on CentOS Stream 9. The reviewed t2.large option charges USD 0.13/hour for seller support plus AWS resources. This is an alternative to the Operator-based Kubernetes path, not that HA topology. The seller does not name embedded TiDB/TiKV/PD versions; inspect and pin them before production rather than inheriting the upstream release snapshot. Scope: Optional third-party TiDB Community VM delivery in the customer AWS account; independent from Operator/Kubernetes topology, package versions and support. Source: https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4 (reviewed 2026-11-18). Supporting source: Seller single-VM installation and initial credentials — https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html. Supporting source: TiDB Community upstream licence — https://github.com/pingcap/tidb/blob/master/LICENSE. Offer prodview-ddl3tqewcoko4: Techlatest.net; Amazon Machine Image (AMI), x86; single-VM bundle; package Seller package 1.0.2; embedded database versions unreported; https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4.

- Cloud commitment eligibility: Sources checked — unresolved. The upstream Community Apache licence has no subscription charge. The alternative Techlatest VM has a separately billed seller-support charge on AWS Marketplace, but its exact commitment eligibility is not established by the offer. Confirm the selected offer/contract and buyer’s AWS agreement; neither the free licence nor TiDB Cloud SaaS terms settle that transaction. Scope: TiDB Community self-managed software; Operator and third-party VM delivery have separate packaging/operating scope. Source: https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4 (reviewed 2026-11-18). Supporting source: AWS commitment qualification is product/agreement-specific — https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html. Supporting source: Community licence — https://github.com/pingcap/tidb/blob/master/LICENSE.

- Single sign-on: Documented. TiDB Self-Managed v8.5 documents OIDC SSO for the TiDB Dashboard web UI, with Okta, Auth0 and self-hosted Casdoor examples. Dashboard encrypts/stores a SQL account password to complete an impersonated SQL sign-in after OIDC authentication. SQL password rotation requires reauthorization; disabling SSO erases the stored password. This establishes Dashboard sign-in only. A selected SQL client’s federated login and SCIM lifecycle require separate confirmation. Scope: TiDB Community/Self-Managed v8.5 Dashboard web UI, including its documented Kubernetes deployment; SQL-client SSO and the versions inside the third-party VM are assessed separately. Source: https://docs.pingcap.com/tidb/stable/dashboard-session-sso/ (reviewed 2026-11-18). Supporting source: Dashboard access on customer-operated Kubernetes — https://docs.pingcap.com/tidb-in-kubernetes/stable/access-dashboard/. Supporting source: Least-privileged Dashboard SQL users — https://docs.pingcap.com/tidb/stable/dashboard-user/. Supporting source: Protect Dashboard and privileged PD interfaces — https://docs.pingcap.com/tidb/stable/dashboard-ops-security/. Supporting source: Separate SQL JWT/LDAP authentication boundary — https://docs.pingcap.com/tidb/stable/security-compatibility-with-mysql/.

- SCIM provisioning: Sources checked — unresolved. JWT and LDAP authentication do not establish SCIM user/group management or automatic SQL-account deprovisioning. A current Community endpoint and supported operations were not confirmed; review provisioning and token revocation separately. Scope: TiDB Community self-managed software; Operator and third-party VM delivery have separate packaging/operating scope. Source: https://docs.pingcap.com/tidb/stable/security-compatibility-with-mysql/ (reviewed 2026-11-18).

- Compliance attestations: Sources checked — unresolved. PingCAP’s Trust Hub advertises ISO and SOC assurances and requests certificate/report access. Its specific ISO announcement identifies TiDB Cloud, a managed service, rather than this customer-operated Community cluster. A current certificate/report covering the relevant Community development/support boundary and buyer controls was not established; do not inherit TiDB Cloud attestations. Scope: TiDB Community self-managed software; Operator and third-party VM delivery have separate packaging/operating scope. Source: https://www.pingcap.com/trust-hub/compliance/ (reviewed 2026-11-18). Supporting source: Explicit TiDB Cloud ISO certification boundary — https://www.pingcap.com/press-release/announcing-iso-27001-certification-for-tidb-cloud/.

- Security controls: Documented. PingCAP documents certificates and TLS between components, plus client TLS and privileged-user/network controls. JWT SQL authentication requires trusted issuer/JWKS configuration and client TLS because the client sends the token through a clear-password plugin. Database token/LDAP authentication alone does not establish SSO or SCIM. Techlatest’s VM guide starts TiDB root with a blank password and Grafana with admin/admin; set new credentials and restrict SSH/RDP before use. Its component patch levels remain unconfirmed. Optional Dashboard OIDC SSO stores an encrypted SQL password for impersonation; use the documented least-privileged account and network/TLS controls, and reauthorize after SQL password rotation. Scope: TiDB Community self-managed software; Operator and third-party VM delivery have separate packaging/operating scope. Source: https://docs.pingcap.com/tidb/stable/enable-tls-between-components/ (reviewed 2026-11-18). Supporting source: Self-managed security configuration — https://docs.pingcap.com/tidb/stable/best-practices-for-security-configuration/. Supporting source: SQL authentication and JWT TLS requirements — https://docs.pingcap.com/tidb/stable/security-compatibility-with-mysql/. Supporting source: Seller-specific initial credential requirements — https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html. Supporting source: Dashboard OIDC credential-handling boundary — https://docs.pingcap.com/tidb/stable/dashboard-session-sso/. Supporting source: Least-privileged Dashboard SQL users — https://docs.pingcap.com/tidb/stable/dashboard-user/.

- Air-gapped operation: Documented. The Kubernetes guide explicitly describes transferring container images to a server without external network access and loading them locally. Include operator, PD/TiKV/TiDB, optional TiFlash/TiCDC, monitoring and initialization images; its v8.5.7 example is not a complete current-version image lockfile. Scope: Operator-based Kubernetes offline procedure only; the third-party VM’s offline lifecycle is not established. Source: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-general-kubernetes/ (reviewed 2026-11-18).

- Deployment artifact / IaC: Documented. The AKS guide provides a versioned TiDB custom-resource manifest from TiDB Operator v1.6.6, together with separate monitoring/dashboard manifests. The operator version and TiDB image versions are independent; review requests, storage classes and all example defaults. The optional seller VM has a separate AMI/image inventory; do not treat the Operator manifest as its installation artifact. Scope: Operator v1.6.6 Kubernetes manifest; the third-party VM is a separate delivery. Source: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-azure-aks/ (reviewed 2026-11-18). Deployment artifact: https://raw.githubusercontent.com/pingcap/tidb-operator/v1.6.6/examples/aks/tidb-cluster.yaml. Artifact reference: TiDB Operator v1.6.6 AKS example. Supporting source: Separate single-VM deployment artifact — https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html.

- Minimum footprint / sizing: Documented. The v8.5 production hardware baseline lists two TiDB nodes at 16 cores/48 GB each, three PD at 8 cores/16 GB, and three TiKV at 16 cores/64 GB, plus SSD and network requirements. Optional analytics/changefeed/monitoring add components. These are component recommendations, not exact pod requests or a benchmark for 100 users. The seller’s t2.large VM example is not this production multi-node baseline. Scope: Upstream v8.5 production component recommendations; not the third-party VM’s capacity or HA guarantee. Source: https://docs.pingcap.com/tidb/stable/hardware-and-software-requirements/ (reviewed 2026-11-18). Supporting source: Different single-VM baseline — https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html.

- License pricing: Documented. TiDB Community is Apache 2.0 licensed. PingCAP support and TiDB Cloud are separate commercial purchases. Review the licences of optional monitoring tools and other bundled components. The alternative Techlatest AMI bills USD 0.13/hour for seller support on its reviewed t2.large option, with AWS resources separate. Scope: TiDB Community self-managed software; Operator and third-party VM delivery have separate packaging/operating scope. Source: https://github.com/pingcap/tidb/blob/master/LICENSE (reviewed 2026-11-18). Supporting source: Separately transacted seller bundle pricing — https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4.

- Operating cost estimate: Sources checked — unresolved. Define SQL QPS, transaction mix, concurrency, indexes, TiKV replication, usable versus raw 1 TB, compaction headroom, TiFlash/TiCDC needs, monitoring and recovery targets. Price EKS and stateful nodes/storage across failure domains after benchmarking; the user count alone does not size this distributed database. The seller’s single-VM bundle does not provide the requested HA architecture. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://docs.pingcap.com/tidb/stable/hardware-and-software-requirements/ (reviewed 2026-11-18). Supporting source: Current AWS Linux EC2 rates; workload/topology still required — https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json. Supporting source: Storage performance and charging inputs — https://aws.amazon.com/ebs/pricing/. Supporting source: Single-VM price/topology is a different cost scope — https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4.

- Release snapshot / cadence: Documented. TiDB v8.5.8 was published August 27, 2026 and is the reviewed v8.5 LTS snapshot. Its notes include PD endpoint and TiKV dependency security fixes. The later v7.5.8 publication belongs to an older branch. Match Operator, TiKV, PD and optional component versions rather than treating the chart version as the database version. Techlatest’s AMI package 1.0.2 does not disclose its embedded database versions, so this upstream snapshot must not be inherited by that VM. Scope: Upstream TiDB v8.5 LTS snapshot; not a confirmed version for the third-party AWS image. Source: https://github.com/pingcap/tidb/releases/tag/v8.5.8 (reviewed 2026-11-18). Supporting source: Component fixes in v8.5.8 — https://docs.pingcap.com/tidb/stable/release-8.5.8. Supporting source: Separate seller package/version boundary — https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4.




### Security and lifecycle reviews

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

- TiDB v8.5.8 PD endpoint and component security review (security-advisory): The release fixes potential SSRF/upstream response exposure in PD metric endpoints, GlobalConfig namespace access and dependency vulnerabilities in TiKV/DM. Scope: The v8.5.8 component release notes; a complete affected-version range and a universal exposure claim are not established. Conditions: Exposure depends on component versions, PD endpoint accessibility and configured dependencies. Community, Cloud and unrelated LTS branches must not be treated as identical deployments. Action: Review the fixed PD/TiKV/optional component versions, restrict management endpoints and follow the matching LTS upgrade procedure. Source: https://docs.pingcap.com/tidb/stable/release-8.5.8; reviewed 2026-11-18.



