What it does
TiDB Self-Managed is PingCAP's distributed SQL database for teams that deploy and operate the database on their own infrastructure. The product documentation describes support for OLTP, OLAP, and HTAP use cases, strong consistency, high availability, and elastic scaling. It is the self-managed engine, not the hosted TiDB Cloud Starter service.
Use the quick start as a development cluster
The self-managed documentation offers a quick start for a local test cluster on macOS or Linux and a single-machine Linux setup. That is a sensible way to explore TiDB's SQL workflow before planning a real deployment. The quick-start page explicitly cautions that these paths are for non-production use, not comprehensive stability or production testing. When a prototype becomes an operational system, follow the separate production installation or Kubernetes instructions and plan for the cluster's machines, storage, upgrades, and monitoring.
The engine is aimed at distributed SQL workloads that need transactional and analytical queries in one database family. The overview describes TiDB as strongly consistent and highly available and positions it for OLTP, OLAP, and HTAP. Those architectural goals do not remove the need to size and administer the cluster: in this edition, your organization is responsible for running it on infrastructure it controls.
A different deployment from TiDB Cloud
This entry covers the self-managed software documented by PingCAP. The existing TiDB Cloud Starter listing is a separately managed service, so the provisioning and operations described there should not be read as steps for this edition. The TiDB repository's license file identifies Apache License 2.0; commercial support or other PingCAP services are outside this listing.
Strengths
- The documentation gives macOS and Linux users a local test-cluster path before they plan a production installation.
- The product overview covers transactional, analytical, and hybrid transactional/analytical use cases in a distributed SQL design.
- The repository identifies the self-managed engine as Apache-2.0-licensed software.
Watch out for
- Operating the self-managed product means providing and administering the infrastructure; the quick-start deployment is explicitly not for production use.
Best for
- Evaluating distributed SQL on a local development cluster.
- Teams planning to operate a horizontally scalable SQL system on their own infrastructure.
- Investigating transactional and analytical workloads that share a database platform.
Sources
- What is TiDB Self-Managed - TiDB Docs (Oct 25, 2026)
- Quick Start with TiDB Self-Managed - TiDB Docs (Oct 25, 2026)
- tidb/LICENSE at master - pingcap/tidb - GitHub (Oct 25, 2026)