
# TiDB Community Self-Hosted

Open-source distributed SQL database with customer-operated EKS, GKE, AKS and ACK deployment guides and a separately packaged AWS VM option.

Canonical page: https://launchinyourcloud.com/directory/tidb-community/
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.


1 listing.


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



