Software on Alibaba Cloud
Software with a documented deployment path in a customer environment on Alibaba Cloud.
16 listings, including 16 from other publishers. Search and filter Alibaba Cloud listings →
Read this page as JSON or Markdown.
Each listing needs its own deployment evidence. A cloud badge identifies a documented option, not a certification or an exclusive list of compatible providers. FormKiQ listings carry a Directory Publisher disclosure.
Customer-account guidance
- Account boundary
- Alibaba Cloud account and resource group
- Network
- VPC
- Identity & access
- Resource Access Management (RAM)
- Deployment tooling
- Resource Orchestration Service (ROS) templates or Terraform; review the required RAM permissions.
Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Provider boundary source ↗ · Checked 2026-11-20
Official provider guidance ↗ · Source reviewed 2026-11-10. Check region, service availability, backup destinations and support access for your deployment.
Deployment and procurement checks
- 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. 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.
Browse by category
13 categories on Alibaba Cloud. Counts show matching listings; a listing can appear in more than one category.
Business operations1 category
Content & collaboration3 categories
Data & analytics3 categories
Developer platforms & operations3 categories
AI tools & infrastructure3 categories
No categories match your search.
Documented software
Deployment evidence and qualifications
Apache-licensed analytical database with upstream AWS EKS/Alibaba ACK/ACS guides and a separately packaged cloudimg Azure VM path.
- Apache Doris on Alibaba Cloud ACK/ACS ↗
Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: Apache License 2.0 for the core project; optional third-party components can carry separate or incompatible licenses.
Cloud evidence reviewed 2026-11-18. Read the full listing and sources →
- Apache Doris on Alibaba Cloud ACK/ACS ↗
Deployment evidence and qualifications
Visual AI application and RAG workflow platform available as a self-hosted container stack.
- Dify Docker deployment on Alibaba Cloud ECS ↗
Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
Alibaba Cloud documents cloning upstream Dify and running its Docker deployment on a customer ECS instance. The example then integrates an MCP server; model providers and other outbound integrations must be reviewed separately.
- Dify Community Edition full application on Alibaba Compute Nest ↗
Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
Alibaba documents a Dify Community Edition service instance that creates ECS compute in the customer-selected VPC, zone and region, then exposes the installed Dify application for administrator registration. This is application hosting rather than an MCP/model connector, and is separate from the licensed Dify AWS Premium offering. Review model endpoints and release compatibility.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer operates the containers, persistent stores, secrets, backups and upgrades; commercial edition support varies.
Scope: Self-hosting Dify does not itself host every model used by a flow. Model-provider plugins, embedding services, tools and connectors may send inputs or retrieved content outside the deployment. Select local endpoints where required and review each dependency. This entry does not conflate the generic self-hosted stack with the separately licensed AWS Premium edition. Dify 1.20.0 changes deployment and API behavior: OPENAPI_ENABLED defaults to true, shared.env is retired, six migrations apply from 1.19, and HITL, plugin-daemon, OpenShell, and optional file-scanning requirements change. It also fixes OAuth callback reuse, member-role enforcement, vector deletion scope, public stream detail exposure, and CVE-2026-116591.
License: Modified Apache 2.0 terms; multi-workspace service operation and frontend branding can require commercial authorization.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Dify Docker deployment on Alibaba Cloud ECS ↗
Deployment evidence and qualifications
Commercial customer-hosted file platform with virtual data-room controls for confidential business documents.
- FileCloud Server installation on Alibaba Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The vendor documents FileCloud Server deployment using its ECS instance in the customer account. Confirm image version, licensing, storage and security requirements; this is not FileCloud Online.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer maintains server infrastructure, storage, backups, configuration and upgrades under the selected FileCloud support arrangement.
Scope: The VDR page explicitly supports on-premises deployment. This listing selects FileCloud Server, not FileCloud Online or the separately scoped Community Edition. Verify VDR controls, access features and governance requirements against the selected Server license. FileCloud’s November 13, 2026 advisories say high-availability deployments using MongoDB replica sets through 23.263.3 are affected by critical CVE-2026-118383; restrict port 27017 to trusted hosts until 23.264. RHEL deployments should also verify that Apache mod_http2 is not exposed to HTTP/2 because CVE-2026-119618 applies when it is loaded.
License: Commercial FileCloud Server license; edition-dependent capabilities
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- FileCloud Server installation on Alibaba Cloud ↗
Deployment evidence and qualifications
Commercial self-hosted file management and sharing platform.
- Websoft9 FileRun ↗
Third party package · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
FileRun application and database on a Websoft9 customer-cloud VM. The application package sits on a separately installed Websoft9 platform. FileRun annual subscriptions and licensed domain terms are separate from platform and cloud bills.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: The application package sits on a separately installed Websoft9 platform. FileRun annual subscriptions and licensed domain terms are separate from platform and cloud bills.
License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Websoft9 FileRun ↗
Deployment evidence and qualifications
Source control and CI/CD on infrastructure you operate.
- GitLab Community Edition on Alibaba Cloud ECS ↗
Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
Alibaba documents GitLab Community Edition Docker deployment on Alibaba Cloud Linux 3 ECS as well as older package-based examples. Use the Community Edition path for this listing; JiHu GitLab is a separately distributed edition and old CentOS examples are not a current production recommendation.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Your team operates, upgrades and backs up the installation.
Scope: GitLab documents AWS, Azure and Google Cloud installations. Oracle and Alibaba Cloud also publish deployment guides. These are documented deployment paths, not a promise of identical support or feature availability. Check operating system, edition and region requirements. GitLab 19.5.4, 19.4.6, and 19.3.8 patch critical CVE-2026-105437 in the bundled Git. Affected self-managed versions are 16.2 through versions before 19.3.8, 19.4 before 19.4.6, and 19.5 before 19.5.4. Upgrade immediately. Self-compiled deployments must also rebuild the Git binaries embedded in Gitaly and the Git installation referenced by git.bin_path, or use a distribution-patched Git 2.56.1 or later. GitLab 19.5.6, 19.4.8, and 19.3.9 address a high-severity cross-site scripting issue plus CI/CD and workspace authorization flaws. On November 20, GitLab issued CE/EE patches 19.6.1, 19.5.8, and 19.4.10 for CVE-2026-132825 and related Ruby flaws. GitLab recommends upgrading affected self-managed installations immediately. Official Linux packages and container images include patched Ruby. Source builds must rebuild the Ruby used by GitLab with 3.3.14 or 3.4.13, or a later patch in the same minor series.
License: Free and paid tiers
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- GitLab Community Edition on Alibaba Cloud ECS ↗
Deployment evidence and qualifications
Self-hosted web analytics with visitor, campaign and website reporting on customer servers.
- 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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages hosting, upgrades, security, backups, tracking configuration and scheduled report processing.
Scope: 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.
License: GPLv3-or-later core; premium plugins use separate commercial EULA and subscription terms
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Matomo named-cloud compatibility FAQ ↗
Deployment evidence and qualifications
Open-source knowledge-base, RAG and agent-workflow platform deployable into an Alibaba Cloud account.
- MaxKB Community Edition service instance in Alibaba Compute Nest ↗
Provider guide · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.
Alibaba Cloud documents creation of a MaxKB Community Edition service instance in a customer-selected region, zone, VPC and VSwitch using customer-selected ECS capacity and billing. The deployed application is reached through the ECS public address on port 8080. The workflow requires broad ECS, VPC, ROS and Compute Nest permissions and returns default administrator credentials that must be changed.
- MaxKB image deployment from Alibaba Cloud Marketplace ↗
Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.
The publisher documents selecting the MaxKB image while purchasing an Alibaba Cloud server, starting the image and opening port 8080 in the customer's security group. It recommends at least 4 CPU cores and 8 GB RAM and instructs administrators to replace the default password after first login.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages the ECS host, VPC and security-group exposure, administrator credentials, persistent PostgreSQL data, backups, upgrades, capacity and credentials for model and tool integrations.
Scope: The Compute Nest deployment requires RAM permissions with full access to ECS, VPC and ROS plus Compute Nest user access; review and reduce deployment privileges after provisioning where practical. Community Edition is single-tenant, x86-64 only and supports single-node or cold-standby deployment rather than Enterprise clustering. RBAC, SSO, audit logs, open API access, conversation-user authorization and several enterprise integrations are reserved for paid editions. Current upstream v2 installation guidance calls for at least 4 CPU cores, 8 GB RAM and 100 GB of disk, exposes the web service on port 8080 and supplies default administrator credentials that must be changed immediately. The publisher recommends offline installation for production and requires a database backup before upgrades. Public or separately hosted model, embedding, reranking and tool providers can receive application data even when MaxKB itself runs in the customer account. The current upstream v2 container image and persistence paths differ from the legacy English guide; check the release packaged by the cloud installer before applying upstream configuration or upgrades. MaxKB v2.10.9-lts fixes multiple cross-workspace access and deletion flaws, stored XSS with account-takeover impact, custom-tool secret exposure, SSRF paths including possible cloud-credential theft, anonymous provider API-key disclosure and unauthorized conversation or knowledge-base access. Upgrade the LTS line and retest workspace, tool and provider boundaries.
License: GNU General Public License version 3 for Community Edition. Professional and Enterprise editions add separately licensed features and support.
Cloud evidence reviewed 2026-11-16. Read the full listing and sources →
- MaxKB Community Edition service instance in Alibaba Compute Nest ↗
Deployment evidence and qualifications
Commercial enterprise AI software suite deployed on customer cloud GPU instances or managed Kubernetes clusters.
- NVIDIA AI Enterprise on Oracle Cloud and Alibaba Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.
NVIDIA's current cloud matrix includes standard instances on Oracle Cloud Infrastructure and Alibaba Cloud, NVIDIA AI Enterprise VM images on OCI and GPU-optimized VM images on Alibaba Cloud. Customers must confirm the supported component set, certified instance and license path.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages cloud GPU instances or Kubernetes, drivers, GPU Operator and container runtime, networking, storage, identities, NGC access, model services, monitoring, upgrades and license activation.
Scope: This entry covers customer-operated NVIDIA AI Enterprise software, not a managed AI service. A license is required and is not included with most standard, GPU-optimized VMI or managed-Kubernetes deployments; on-demand NVIDIA AI Enterprise VMIs and private offers use separate included-license processes. Not every component is available on every cloud or deployment model. GPU deployments are generally licensed per GPU, while CPU-only instances require an instance license. Tencent Cloud and ByteDance Volcano Engine have documented standard-instance BYOL paths. These guides require certified software and supported instance types; they do not establish that every GPU, component or provider image is eligible. Their per-instance wording differs from the general per-GPU licensing guidance, so confirm the applicable licensing unit. The November lifecycle matrix lists active 9.0/R620, 8.3/R595, and 7.9 LTSB/R580 branches with different end dates. NeMo Microservices support ended October 1, 2026, after 25.12 became the final GA release; select and patch each component branch independently.
License: Commercial NVIDIA AI Enterprise subscription, consumption or perpetual license; most customer-cloud paths require BYOL.
Cloud evidence reviewed 2026-11-16. Read the full listing and sources →
- NVIDIA AI Enterprise on Oracle Cloud and Alibaba Cloud ↗
Deployment evidence and qualifications
Commercial self-hosted office editing and real-time document collaboration server deployed as a cloud marketplace image.
- ONLYOFFICE Docs Enterprise Alibaba Cloud Marketplace image ↗
Vendor / upstream documentation · Reviewed 2026-11-19 · Scope: Docs Enterprise. Vendor support commitment: not assessed; confirm the selected release and contract.
ONLYOFFICE documents creating the Docs Enterprise ECS instance from Alibaba Cloud Marketplace in the customer's account and configuring its region, network, storage and security settings.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer operates the cloud instance, networking and integrations; software entitlement is purchased through a marketplace or directly from ONLYOFFICE.
Scope: Docs Enterprise is an editing and collaboration server, not a complete file repository. It normally integrates with a separate content platform. Marketplace billing and direct annual or lifetime licensing are distinct procurement routes. The reviewed AWS x86 50-connection offer packages 9.4.0. This image version is separate from the current Docs website release banner, other connection tiers, ARM and Alibaba packages.
License: Commercial proprietary connection-based license with annual and lifetime purchase options
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- ONLYOFFICE Docs Enterprise Alibaba Cloud Marketplace image ↗
Deployment evidence and qualifications
Document processing and retrieval platform for building RAG and agentic knowledge applications.
- RAGFlow Community deployment on Alibaba Cloud Compute Nest ↗
Provider guide · Reviewed 2026-11-12 · Scope: Community / upstream open-source; third-party distribution where noted. Vendor support commitment: not assessed; confirm the selected release and contract.
Alibaba Cloud documents provisioning a RAGFlow Community service instance with customer ECS, VPC and vSwitch parameters. This is distinct from the managed AI-Native Database Service integration. Review image version, access controls, model endpoints and the broad example RAM permissions before production.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages document storage, indexing, app services, access controls, model endpoints, backups and upgrades.
Scope: Deployment options include customer AWS, Azure and Google Cloud infrastructure, Alibaba Compute Nest, and a Railway project. The evidence trail identifies the publishers and template versions. Hosting RAGFlow does not automatically self-host its LLM, embeddings or reranker; choose private or local model endpoints where required.
License: Apache License 2.0 for upstream RAGFlow; models, data assets and dependencies retain their own terms.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- RAGFlow Community deployment on Alibaba Cloud Compute Nest ↗
Deployment evidence and qualifications
Commercial self-managed Kubernetes application platform installed and operated in customer cloud accounts.
- OpenShift on Alibaba Cloud — Technology Preview ↗
Vendor / upstream documentation · Reviewed 2026-11-15 · Version: 4.21 Technology Preview. Vendor support commitment: not assessed; confirm the selected release and contract.
Red Hat documents Assisted Installer deployment using customer Alibaba Cloud OSS images, ECS machines, VPC and DNS. This 4.21 path is Technology Preview: outside production SLAs, potentially incomplete and not recommended by Red Hat for production.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages cloud accounts, installer credentials, cluster machines, networking, identity, storage, registry, monitoring, backups, upgrades and Red Hat subscriptions.
Scope: This entry covers self-managed OpenShift Container Platform, not OpenShift Dedicated, ROSA, Azure Red Hat OpenShift or other managed services. The installer can provision infrastructure or integrate with customer-provisioned resources; review credential scope, subscription entitlements and lifecycle support before installation. The documented Alibaba Cloud Assisted Installer path is Technology Preview, outside Red Hat production SLAs and not recommended for production.
License: Commercial Red Hat OpenShift subscription.
Cloud evidence reviewed 2026-11-15. Read the full listing and sources →
- OpenShift on Alibaba Cloud — Technology Preview ↗
Deployment evidence and qualifications
Licensed ERP for financials, purchasing, inventory and customer operations.
- Alibaba Docs ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Customer-managed SAP Business One application and a certified database on cloud VMs. The Azure, Google Cloud and Alibaba guides describe customer infrastructure. Application, database, operating-system and partner entitlements remain separate; check SAP certification for the actual release and topology.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: The Azure, Google Cloud and Alibaba guides describe customer infrastructure. Application, database, operating-system and partner entitlements remain separate; check SAP certification for the actual release and topology.
License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Alibaba Docs ↗
Deployment evidence and qualifications
Commercial observability platform installed by Helm into a dedicated customer Kubernetes cluster.
- SUSE Observability server installation on Alibaba ACK ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
The server guide supplies ACK-specific Helm values for stateful backend PVCs, each at least 20 GiB. This is server deployment evidence, distinct from monitoring an ACK cluster with an agent. Apply the selected HA sizing profile and provider storage requirements.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages the Kubernetes cluster, persistent storage, sizing, ingress, certificates, backups, upgrades and monitored-system access.
Scope: This entry covers the self-hosted server product, not SUSE Cloud Observability SaaS. Installation requires a license key, compatible Helm and Kubernetes versions, persistent storage and dedicated sizing. High-availability and non-high-availability profiles are not interchangeable after installation, so choose the production topology before deployment. SUSE Observability 2.13.0 includes authentication, disk, and backup fixes and requires the documented sequential upgrade path. Version 2.10 reached end of support on November 12, 2026; move through supported intermediate releases as required.
License: Commercial SUSE Observability self-hosted subscription and license key required.
Cloud evidence reviewed 2026-11-17. Read the full listing and sources →
- SUSE Observability server installation on Alibaba ACK ↗
Deployment evidence and qualifications
Open-source Kubernetes security platform with documented customer-operated deployment on AWS, Azure, Google Cloud, IBM Cloud, Alibaba Cloud and OCI.
- SUSE Security on six named public-cloud Kubernetes services ↗
Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
SUSE explicitly names AWS EKS, Azure AKS, Google Cloud, IBM Cloud Kubernetes, Alibaba Cloud and Oracle Cloud and links full Kubernetes/Helm application deployment. Confirm tested platform versions and privileges. GKE Autopilot requires allowlists; AWS ECS is no longer supported in the requirements guide.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages Kubernetes, registry access, Helm values, storage, certificates, policies, upgrades, monitoring and cluster privileges.
Scope: This entry covers upstream NeuVector/SUSE Security deployment; subscription images/support can require commercial entitlements. SUSE names six public-cloud Kubernetes targets. Resolve the conflicting manager-redundancy guidance before HA design, and apply GKE Autopilot allowlists where required. Scan-policy/compliance functions do not certify the customer installation.
License: Apache License 2.0 for NeuVector; Rancher Prime delivery and commercial support have separate subscription terms.
Cloud evidence reviewed 2026-11-18. Read the full listing and sources →
- SUSE Security on six named public-cloud Kubernetes services ↗
Deployment evidence and qualifications
Commercial analytics and business-intelligence server installed and operated on customer cloud virtual machines.
- Tableau Server on Alibaba Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
Tableau documents production-ready self-deployment on customer Alibaba Elastic Compute Service virtual machines with BYOL operation. The provider guide is archived.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Operations: Customer manages the virtual machines, operating system, Tableau services, identity, networking, storage, backups, upgrades and availability.
Scope: 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.
License: Commercial Tableau Server product-key licensing with user-, core- or subscription-based entitlements.
Cloud evidence reviewed 2026-11-17. Read the full listing and sources →
- Tableau Server on Alibaba Cloud ↗
Deployment evidence and qualifications
Open-source distributed SQL database with customer-operated cloud Kubernetes guides and a separately packaged third-party AWS VM option.
- TiDB on Alibaba Cloud ACK ↗
Vendor / upstream documentation · Reviewed 2026-11-18 · Version: TiDB Operator guide v1.4. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer cloud account. Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
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.
Scope: 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.
License: Apache License 2.0.
Cloud evidence reviewed 2026-11-18. Read the full listing and sources →
- TiDB on Alibaba Cloud ACK ↗
Compare all cloud providers · Plan a deployment · Browse without publisher listings