TiDB Community Self-Hosted
Open-source distributed SQL database with customer-operated cloud Kubernetes guides and a separately packaged third-party AWS VM option.
9 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
TiDB v8.5.8 PD endpoint and component security review
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.
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.
Primary source · Reviewed 2026-11-18
What lands where
Supplied by
Vendor or project
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
Runs in
Documented customer environment
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.
- AWS: Customer cloud account
- Google Cloud: Customer cloud account
- Azure: Customer cloud account
- Alibaba Cloud: Customer cloud account
- AWS
- Azure
- Google Cloud
- Alibaba Cloud
Servers / containers
Operated by
Your team
Customer manages the chosen Kubernetes cluster or VM, operating system/node pools, persistent storage, networking, database identities, backups, monitoring, upgrades, scaling and database operations.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
TiDB on Amazon EKS ↗ · Source checked 2026-11-18
Techlatest TiDB OSS single-VM bundle in customer EC2 ↗ · Source checked 2026-11-18
- Google Cloud: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
TiDB on Google Kubernetes Engine ↗ · Source checked 2026-11-18
- Azure: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
TiDB Community on Azure AKS ↗ · Source checked 2026-11-18
- Alibaba Cloud: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
TiDB on Alibaba Cloud ACK ↗ · Source checked 2026-11-18
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | 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 |
|---|---|
| Infrastructure | Servers / containers 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. |
| Licensing model | Open Source / Open Core The TiDB repository is Apache-2.0 licensed. Managed TiDB Cloud services have separate terms. |
| License | Apache License 2.0. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
12 of 12 fields researched (100%) · 8 documented · 4 unresolved. Evidence coverage is not a feature score.
- Marketplace delivery
AvailableEvidence and scope for Marketplace delivery
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.
Optional third-party TiDB Community VM delivery in the customer AWS account; independent from Operator/Kubernetes topology, package versions and support · Source ↗ · Seller single-VM installation and initial credentials ↗ · TiDB Community upstream licence ↗ · Offer prodview-ddl3tqewcoko4 ↗ — Techlatest.net; Amazon Machine Image (AMI), x86; single-VM bundle; package Seller package 1.0.2; embedded database versions unreported · Reviewed 2026-11-18
Documented · Editor reviewed.
- Cloud commitment eligibility
Not confirmedEvidence and scope for Cloud commitment eligibility
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.
TiDB Community self-managed software; Operator and third-party VM delivery have separate packaging/operating scope · Source ↗ · AWS commitment qualification is product/agreement-specific ↗ · Community licence ↗ · Reviewed 2026-11-18
Sources checked — unresolved · Editor reviewed.
- Single sign-on
AvailableEvidence and scope for Single sign-on
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.
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 ↗ · Dashboard access on customer-operated Kubernetes ↗ · Least-privileged Dashboard SQL users ↗ · Protect Dashboard and privileged PD interfaces ↗ · Separate SQL JWT/LDAP authentication boundary ↗ · Reviewed 2026-11-18
Documented · Editor reviewed.
- SCIM provisioning
Not confirmedEvidence and scope for SCIM provisioning
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.
TiDB Community self-managed software; Operator and third-party VM delivery have separate packaging/operating scope · Source ↗ · Reviewed 2026-11-18
Sources checked — unresolved · Editor reviewed.
- Compliance attestations
Not confirmedEvidence and scope for Compliance attestations
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.
TiDB Community self-managed software; Operator and third-party VM delivery have separate packaging/operating scope · Source ↗ · Explicit TiDB Cloud ISO certification boundary ↗ · Reviewed 2026-11-18
Sources checked — unresolved · Editor reviewed.
- Security controls
DocumentedEvidence and scope for Security controls
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.
TiDB Community self-managed software; Operator and third-party VM delivery have separate packaging/operating scope · Source ↗ · Self-managed security configuration ↗ · SQL authentication and JWT TLS requirements ↗ · Seller-specific initial credential requirements ↗ · Dashboard OIDC credential-handling boundary ↗ · Least-privileged Dashboard SQL users ↗ · Reviewed 2026-11-18
Documented · Editor reviewed.
- Air-gapped operation
AvailableEvidence and scope for Air-gapped operation
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.
Operator-based Kubernetes offline procedure only; the third-party VM’s offline lifecycle is not established · Source ↗ · Reviewed 2026-11-18
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
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.
Operator v1.6.6 Kubernetes manifest; the third-party VM is a separate delivery · Source ↗ · Deployment artifact ↗ (TiDB Operator v1.6.6 AKS example) · Separate single-VM deployment artifact ↗ · Reviewed 2026-11-18
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
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.
Upstream v8.5 production component recommendations; not the third-party VM’s capacity or HA guarantee · Source ↗ · Different single-VM baseline ↗ · Reviewed 2026-11-18
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
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.
TiDB Community self-managed software; Operator and third-party VM delivery have separate packaging/operating scope · Source ↗ · Separately transacted seller bundle pricing ↗ · Reviewed 2026-11-18
Documented · Editor reviewed.
- Operating cost estimate
Not confirmedEvidence and scope for Operating cost estimate
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.
Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput · Source ↗ · Current AWS Linux EC2 rates; workload/topology still required ↗ · Storage performance and charging inputs ↗ · Single-VM price/topology is a different cost scope ↗ · Reviewed 2026-11-18
Sources checked — unresolved · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
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.
Upstream TiDB v8.5 LTS snapshot; not a confirmed version for the third-party AWS image · Source ↗ · Component fixes in v8.5.8 ↗ · Separate seller package/version boundary ↗ · Reviewed 2026-11-18
Documented · Editor reviewed.
Scope & considerations
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.
Community & 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.
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.
Compare within Databases & vector
- Apache Doris Self-HostedApache-licensed analytical database with upstream AWS EKS/Alibaba ACK/ACS guides and a separately packaged cloudimg Azure VM path.
- AWS
- Azure
- Alibaba Cloud
- ClickHouse BYOCManaged analytical database with its data plane in your cloud account.
- AWS
- Azure
- Google Cloud
- CockroachDB BYOCVendor-managed CockroachDB service deployed into the customer's AWS, Azure or Google Cloud account.
- AWS
- Azure
- Google Cloud
- Couchbase Server Enterprise EditionSelf-managed distributed NoSQL database deployed in customer-controlled Kubernetes with the Couchbase Operator.
- AWS
- Azure
- Google Cloud
- Elastic Cloud EnterpriseCommercial self-managed orchestration platform for Elastic Stack deployments across customer cloud hosts.
- AWS
- Azure
- Google Cloud
- Elastic Cloud on KubernetesElastic's Kubernetes operator for deploying and operating Elasticsearch, Kibana and related Elastic Stack resources in customer clusters.
- AWS
- Azure
- Google Cloud
- Meilisearch Community EditionSelf-hosted search engine for typo-tolerant full-text, semantic and hybrid retrieval.
- AWS
- Google Cloud
- DigitalOcean
- MilvusVector database for similarity search and retrieval over embedding collections.
- AWS
- Azure
- Google Cloud
Showing 8 of 18 other listings in Databases & vector. These products address related workflows; read their category-fit notes before comparing scope. See all of Databases & vector →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- TiDB Operator overview ↗docs.pingcap.com
- Deploy TiDB on AWS EKS ↗docs.pingcap.com
- Deploy TiDB on Google Cloud GKE ↗docs.pingcap.com
- TiDB Apache 2.0 license ↗github.com
- TiDB Community on Azure AKS ↗docs.pingcap.com
- TiDB on Alibaba Cloud ACK ↗docs.pingcap.com
- Current TiDB deployment FAQ ↗docs.pingcap.com
- Exact third-party TiDB OSS AWS image ↗aws.amazon.com
- Seller customer-account VM deployment ↗www.techlatest.net
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- TiDB on Amazon EKS ↗ · AWS
Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
PingCAP documents customer EKS node pools, storage and TiDB Operator deployment.
- TiDB on Google Kubernetes Engine ↗ · Google Cloud
Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
PingCAP documents customer GKE node pools, persistent disks and TiDB Operator deployment.
- TiDB Community on Azure AKS ↗ · Azure
Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
PingCAP provides a full AKS deployment guide with customer node pools, PD/TiKV/TiDB and monitoring manifests. A deployment guide establishes a documented path, not a commercial support contract.
- TiDB on Alibaba Cloud ACK ↗ · Alibaba Cloud
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.
- Techlatest TiDB OSS single-VM bundle in customer EC2 ↗ · AWS
Third party package · Reviewed 2026-11-18 · Scope: Repackaged open-source TiDB bundle · Version: Seller package 1.0.2; embedded database versions unreported. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- TiDB on Amazon EKS ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Official maintenance and adoption evidence ↗github.com
- Official maintenance and adoption evidence ↗www.pingcap.com
- Official maintenance and adoption evidence ↗docs.pingcap.com