Pricing for TiDB Cloud
How pricing changes as you scale: upgrade triggers, cost cliffs, and plan structure (not a live price list).
Freshness & verification
Pricing behavior (not a price list)
These points describe when users typically pay more and what usage patterns trigger upgrades.
Actions that trigger upgrades
- Need MySQL compatibility with distributed SQL patterns
- Need HTAP capabilities (real-time analytics on transactional data)
- Need horizontal scaling without sharding complexity
- Need multi-region MySQL-compatible database with strong consistency
What gets expensive first
- Distributed SQL operating model requires careful fit validation
- HTAP use cases must justify the complexity
- Cost drivers differ from single-node databases
- Not every workload benefits; can be overkill early
Plans and variants (structural only)
Grouped by type to show structure, not to rank or recommend SKUs.
- Compute + storage - primary drivers - Pricing usually scales with compute size, storage, and traffic patterns.
- HTAP capabilities - TiFlash analytics - Real-time analytics on transactional data adds compute and storage costs.
- High availability - replicas/backups - Reliability features add cost but reduce operational risk.
- Official pricing: https://www.pingcap.com/pricing/
Compare pricing trade-offs head-to-head
Use these comparisons when you are down to two finalists and need a clearer trade-off view.
Next step: constraints + what breaks first
Pricing tells you the cost cliffs; constraints tell you what forces a redesign.
Sources & verification
Pricing and behavioral information comes from public documentation and structured research. When information is incomplete or volatile, we prefer to say so rather than guess.
Something outdated or wrong? Pricing, features, and product scope change. If you spot an error or have a source that updates this page, send us a correction. We prioritize vendor-verified updates and linkable sources.