Sign InTry Free

TiDB Serverless Limitations and Quotas

TiDB Serverless works with almost all workloads that TiDB supports, but there are some feature differences between TiDB Self-Hosted or TiDB Dedicated clusters and TiDB Serverless clusters. This document describes the limitations of TiDB Serverless.

We are constantly filling in the feature gaps between TiDB Serverless and TiDB Dedicated. If you require these features or capabilities in the gap, use TiDB Dedicated or contact us for a feature request.


Audit logs



  • Data persisted in your TiDB Serverless cluster is encrypted using the encryption tool provided by the cloud provider that manages your cluster. However, TiDB Serverless does not provide any additional optional measures for protecting data at-rest on disks beyond infrastructure-level encryption.
  • Using customer-managed encryption keys (CMEK) is currently unavailable.

Maintenance window

Monitoring and diagnosis

Self-service upgrades

  • TiDB Serverless is a fully managed deployment of TiDB. Major and minor version upgrades of TiDB Serverless are handled by TiDB Cloud and therefore cannot be initiated by users.

Stream data

  • Changefeed is not supported for TiDB Serverless currently.
  • Data Migration is not supported for TiDB Serverless currently.


  • Transaction can not last longer than 30 minutes.
  • For more details about SQL limitations, refer to Limited SQL Features.

Usage quota

For each organization in TiDB Cloud, you can create a maximum of five free clusters by default. To create more TiDB Serverless clusters, you need to add a credit card and create scalable clusters for the usage.

For the first five TiDB Serverless clusters in your organization, whether they are free or scalable, TiDB Cloud provides a free usage quota for each of them as follows:

The Request Unit (RU) is a unit of measurement used to track the resource consumption of a query or transaction. It is a metric that allows you to estimate the computational resources required to process a specific request in the database. The request unit is also the billing unit for TiDB Cloud Serverless service.

Once a cluster 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.

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 Serverless Pricing Details.

If you want to create a TiDB Serverless cluster with an additional quota, you can select the scalable cluster plan and edit the spending limit on the cluster creation page. For more information, see Create a TiDB Serverless cluster.

After creating a TiDB Serverless cluster, you can still check and edit the spending limit on your cluster overview page. For more information, see Manage Spending Limit for TiDB Serverless Clusters.

Was this page helpful?

Download PDFRequest docs changesAsk questions on Discord
One-stop & interactive experience of TiDB's capabilities WITHOUT registration.
TiDB Dedicated
TiDB Serverless
Get Demo
Get Started
© 2024 PingCAP. All Rights Reserved.
Privacy Policy.