📣New in Public Preview: TiDB Cloud BYOC, TiDB Cloud Filesystem, PostgreSQL-compatible TiDB Cloud Starter
​
Sign InStart for Free
AI
Developer
Best Practices
API
​
Sign InStart for Free

Select Your Plan

The plan determines the throughput and performance of your TiDB resource.

TiDB Cloud provides the following options of plans. Whether you are just getting started or scaling to meet the increasing application demands, these service plans provide the flexibility and capability you need. Before creating a TiDB resource, you need to consider which option suits your need better.

TiDB Cloud Starter

TiDB Cloud Starter is a fully managed, multi-tenant database offering that provides instant, autoscaling database instances for developers and small teams.

TiDB Cloud Starter supports the following compatibility modes:

  • MySQL-compatible: provides MySQL protocol compatibility. Each eligible instance includes a monthly free quota, and you can enable consumption-based billing to continue using the instance after exceeding the free quota.

  • PostgreSQL-compatible (Public Preview): provides PostgreSQL wire protocol compatibility. PostgreSQL-compatible Starter instances are currently free during the public preview.

The free plan is ideal for developers and small teams getting started with TiDB Cloud Starter. Each compatibility mode includes a monthly free quota for storage and Request Units (RUs). The quota varies by compatibility mode.

  • No cost: This plan is free when usage is within the free quota. No credit card is required to get started.

  • Storage: Includes a monthly free storage quota.

  • Request Units: Includes Request Units (RUs) for database operations.

MySQL-compatible Starter

For each organization in TiDB Cloud, you can create a maximum of five free MySQL-compatible TiDB Cloud Starter instances by default. To create more TiDB Cloud Starter instances, you need to add a credit card and specify a spending limit.

For the first five MySQL-compatible TiDB Cloud Starter instances in your organization, whether they are free or scalable, TiDB Cloud provides a free usage quota for each of them as follows:

  • Row-based storage: 5 GiB
  • Columnar storage: 5 GiB
  • Request Units (RUs): 50 million RUs per month

A Request Unit (RU) is a unit of measure used to represent the amount of resources consumed by a single request to the database. The amount of RUs consumed by a request depends on various factors, such as the operation type or the amount of data being retrieved or modified.

Once a TiDB Cloud Starter instance reaches its usage quota, it immediately denies any new connection attempts until you increase the quota or the usage is reset upon the start of a new month. Existing connections established before reaching the quota will remain active but will experience throttling. For example, when the row-based storage of a TiDB Cloud Starter instance exceeds 5 GiB for a free TiDB Cloud Starter instance, the instance automatically restricts any new connection attempts.

To learn more about the RU consumption of different resources (including read, write, SQL CPU, and network egress), the pricing details, and the throttled information, see TiDB Cloud Starter Pricing Details.

PostgreSQL-compatible Starter

PostgreSQL-compatible TiDB Cloud Starter instances are currently free during the public preview.

For the first 10 PostgreSQL-compatible TiDB Cloud Starter instances in your organization, TiDB Cloud provides the following monthly free quota for each instance:

  • Row-based storage: 50 GiB

  • Request Units (RUs): 500 million RUs per month

When a PostgreSQL-compatible TiDB Cloud Starter instance reaches its free quota, excessive resource consumption might be subject to usage restrictions or service suspension. If you anticipate exceeding these allowances, please contact support@pingcap.com to discuss your requirements.

Instance Capacity Plan

The following instance capacity limits apply to MySQL-compatible TiDB Cloud Starter instances.

For each organization in TiDB Cloud, you can create a maximum of five branches across all TiDB Cloud Starter and Essential instances by default.

For each paid organization in TiDB Cloud, you can create up to 100 TiDB Cloud Starter instances and branches in total, with each branch counted as a separate instance.

For paid organizations building agent platforms or other services that require a large number of instances and branches, TiDB Cloud offers the Instance Capacity Plan. With this plan, each paid TiDB Cloud organization can create more than five branches and is not subject to the limit of 100 TiDB Cloud Starter instances and branches. To learn more and apply for the Instance Capacity Plan, fill out the application form.

You will receive an email notification once your application for the TiDB Cloud Instance Capacity Plan is approved.

TiDB Cloud Essential

For applications experiencing growing workloads and needing scalability in real time, the Essential plan provides the flexibility and performance to keep pace with your business growth with the following features:

  • Enhanced capabilities: includes all capabilities of the Starter plan, along with the capacity to handle larger and more complex workloads, as well as advanced security features.
  • Automatic scaling: automatically adjusts storage and computing resources to efficiently meet changing workload demands.
  • High availability: built-in fault tolerance and redundancy ensure your applications remain available and resilient, even during infrastructure failures.
  • Predictable pricing: billed based on storage and Request Capacity Units (RCUs) of the compute resources, offering transparent, usage-based pricing that scales with your needs, so you only pay for what you use without surprises.

User name prefix

For each TiDB Cloud Starter or TiDB Cloud Essential instance, TiDB Cloud generates a unique prefix to distinguish it from other instances.

Whenever you use or set a database user name, you must include the prefix in the user name. For example, assume that the prefix of your TiDB Cloud Starter or TiDB Cloud Essential instance is 3pTAoNNegb47Uc8.

  • To connect to your TiDB Cloud Starter or TiDB Cloud Essential instance:

    mysql -u '3pTAoNNegb47Uc8.root' -h <host> -P 4000 -D test --ssl-mode=VERIFY_IDENTITY --ssl-ca=<CA_root_path> -p

  • To create a database user:

    CREATE USER '3pTAoNNegb47Uc8.jeffrey';

To get the prefix for your TiDB Cloud Starter or TiDB Cloud Essential instance, take the following steps:

  1. Navigate to the My TiDB page.
  2. Click the name of your target TiDB Cloud Starter or Essential instance to go to its overview page, and then click Connect in the upper-right corner. A connection dialog is displayed.
  3. In the dialog, get the prefix from the connection string.

TiDB Cloud Premium

For mission-critical enterprise workloads that require large-scale capacity and consistent high performance, the Premium plan provides a cloud-native experience with the following features:

  • Instant elasticity: automatically scales compute resources to absorb sudden traffic spikes and maintain stable performance during peak demand.
  • Unlimited scalability: expands storage and throughput to keep pace with business growth, without physical infrastructure constraints.
  • Zero-infrastructure management: offers a fully managed service that eliminates manual scaling, patching, and capacity planning.
  • Predictable pricing: billed based on storage and Request Capacity Units (RCUs), offering transparent, usage-based pricing that scales with your needs, so you only pay for what you use without surprises.
  • Advanced security and compliance: supports advanced encryption, customer-managed encryption keys (CMEK), private networking, and compliance certifications to protect sensitive data.

TiDB Cloud BYOC

TiDB Cloud BYOC is designed for enterprise workloads that require stronger control over data location, cloud resources, network boundaries, and compliance posture. With TiDB Cloud BYOC, the TiDB Cloud control plane is managed by PingCAP, while the data plane runs in your own cloud account.

TiDB Cloud BYOC provides a managed TiDB Cloud experience with the following features:

  • Customer-owned data plane: keeps TiDB service resources, storage, networking, and data in your cloud account.
  • Managed operations: uses TiDB Cloud for deployment, scaling, monitoring, upgrades, backup and restore, and lifecycle management.
  • Flexible high availability: supports both Single-AZ and Multi-AZ deployments, enabling you to choose between lower-latency zonal deployment and higher-resilience deployment across multiple availability zones.
  • Cloud-account-level security controls: lets you apply your own cloud policies, network controls, audit logging, and compliance controls to the BYOC data plane.
  • Private connectivity: supports private network access patterns such as VPC peering, depending on your BYOC configuration.

TiDB Cloud Dedicated

TiDB Cloud Dedicated is for production use with the benefits of cross-zone high availability, horizontal scaling, and HTAP.

For TiDB Cloud Dedicated clusters, you can customize the cluster size of TiDB, TiKV, and TiFlash easily according to your business need. For each TiKV node and TiFlash node, the data on the node is replicated and distributed in different availability zones for high availability.

To create a TiDB Cloud Dedicated cluster, you need to add a payment method or apply for a Proof of Concept (PoC) trial.

TiDB Cloud Lake

TiDB Cloud Lake is a cloud-native data warehouse service for analytics workloads. It separates compute and storage, allowing you to provision warehouses independently, scale with workload changes, and store data cost-effectively in object storage.

TiDB Cloud Lake supports ANSI SQL, semi-structured data processing, vector search, and AI-oriented workflows in one platform. It is designed for teams that want a managed analytics experience without operating the underlying infrastructure themselves.

See TiDB Cloud Lake Overview and TiDB Cloud Lake Quick Start.

TiDB Cloud Filesystem

TiDB Cloud Filesystem is a persistent, shared cloud file system for applications, automation, and AI agents. Use it when files need to remain available across sessions and environments or when multiple users or workloads need controlled access to the same files. You do not need to provision or manage a TiDB database to use it.

TiDB Cloud Filesystem is currently in public preview. For more information, see TiDB Cloud Filesystem documentation.

Was this page helpful?