pingcap · ti-chi-bot · Jul 15, 2025 · Jul 9, 2025 · Jul 15, 2025 · Jul 15, 2025
diff --git a/TOC-tidb-cloud.md b/TOC-tidb-cloud.md
diff --git a/media/develop/aws-lambda-cf-create-stack.png b/media/develop/aws-lambda-cf-create-stack.png
diff --git a/media/develop/aws-lambda-cf-stack-config-option.png b/media/develop/aws-lambda-cf-stack-config-option.png
diff --git a/media/develop/aws-lambda-cf-stack-config-review.png b/media/develop/aws-lambda-cf-stack-config-review.png
diff --git a/media/develop/aws-lambda-cf-stack-config.png b/media/develop/aws-lambda-cf-stack-config.png
diff --git a/media/develop/aws-lambda-get-apigateway-invoke-url.png b/media/develop/aws-lambda-get-apigateway-invoke-url.png
diff --git a/media/develop/aws-lambda-structure-overview.png b/media/develop/aws-lambda-structure-overview.png
diff --git a/media/develop/aws-lambda-tidbcloud-connection-info.png b/media/develop/aws-lambda-tidbcloud-connection-info.png
diff --git a/media/tidb-cloud/azure-create-private-endpoint-service-resource-id.png b/media/tidb-cloud/azure-create-private-endpoint-service-resource-id.png
diff --git a/media/tidb-cloud/azure-private-endpoint-arch.png b/media/tidb-cloud/azure-private-endpoint-arch.png
diff --git a/media/tidb-cloud/azure-private-endpoint-dns-ip.png b/media/tidb-cloud/azure-private-endpoint-dns-ip.png
diff --git a/media/tidb-cloud/azure-private-endpoint-resource-id.png b/media/tidb-cloud/azure-private-endpoint-resource-id.png
diff --git a/media/tidb-cloud/blank_transparent_placeholder.png b/media/tidb-cloud/blank_transparent_placeholder.png
diff --git a/...tidb-cloud/changefeed/connect-to-aws-self-hosted-kafka-privatelink-service.jpeg b/...tidb-cloud/changefeed/connect-to-aws-self-hosted-kafka-privatelink-service.jpeg
diff --git a/...idb-cloud/changefeed/connect-to-azure-self-hosted-kafka-privatelink-service.png b/...idb-cloud/changefeed/connect-to-azure-self-hosted-kafka-privatelink-service.png
diff --git a/...t-to-google-cloud-self-hosted-kafka-private-service-connect-by-kafka-proxy.jpeg b/...t-to-google-cloud-self-hosted-kafka-private-service-connect-by-kafka-proxy.jpeg
diff --git a/...t-to-google-cloud-self-hosted-kafka-private-service-connect-by-portmapping.jpeg b/...t-to-google-cloud-self-hosted-kafka-private-service-connect-by-portmapping.jpeg
diff --git a/media/tidb-cloud/connected-ai-chat-example.png b/media/tidb-cloud/connected-ai-chat-example.png
diff --git a/media/tidb-cloud/connected-lark-ticket-creation-1.png b/media/tidb-cloud/connected-lark-ticket-creation-1.png
diff --git a/media/tidb-cloud/connected-lark-ticket-creation-2.png b/media/tidb-cloud/connected-lark-ticket-creation-2.png
diff --git a/media/tidb-cloud/connected-lark-ticket-creation-3.png b/media/tidb-cloud/connected-lark-ticket-creation-3.png
diff --git a/media/tidb-cloud/connected-lark-ticket-creation-4.png b/media/tidb-cloud/connected-lark-ticket-creation-4.png
diff --git a/media/tidb-cloud/connected-lark-ticket-interaction-1.png b/media/tidb-cloud/connected-lark-ticket-interaction-1.png
diff --git a/media/tidb-cloud/connected-slack-ticket-creation-1.png b/media/tidb-cloud/connected-slack-ticket-creation-1.png
diff --git a/media/tidb-cloud/connected-slack-ticket-creation-2.png b/media/tidb-cloud/connected-slack-ticket-creation-2.png
diff --git a/media/tidb-cloud/connected-slack-ticket-creation-3.png b/media/tidb-cloud/connected-slack-ticket-creation-3.png
diff --git a/media/tidb-cloud/connected-slack-ticket-creation-4.png b/media/tidb-cloud/connected-slack-ticket-creation-4.png
diff --git a/media/tidb-cloud/connected-slack-ticket-creation-5.png b/media/tidb-cloud/connected-slack-ticket-creation-5.png
diff --git a/media/tidb-cloud/connected-slack-ticket-interaction-1.png b/media/tidb-cloud/connected-slack-ticket-interaction-1.png
diff --git a/media/tidb-cloud/connected-slack-ticket-interaction-2.png b/media/tidb-cloud/connected-slack-ticket-interaction-2.png
diff --git a/media/tidb-cloud/connected-slack-ticket-interaction-3.png b/media/tidb-cloud/connected-slack-ticket-interaction-3.png
diff --git a/media/tidb-cloud/connected-slack-ticket-interaction-4.png b/media/tidb-cloud/connected-slack-ticket-interaction-4.png
diff --git a/media/tidb-cloud/connected-slack-ticket-interaction-5.png b/media/tidb-cloud/connected-slack-ticket-interaction-5.png
diff --git a/media/tidb-cloud/connected-slack-ticket-interaction-6.png b/media/tidb-cloud/connected-slack-ticket-interaction-6.png
diff --git a/media/tidb-cloud/connected-slack-ticket-interaction-7.png b/media/tidb-cloud/connected-slack-ticket-interaction-7.png
diff --git a/media/tidb-cloud/connected-slack-ticket-interaction-8.png b/media/tidb-cloud/connected-slack-ticket-interaction-8.png
diff --git a/media/tidb-cloud/connected-slack-ticket-interaction-creation.gif b/media/tidb-cloud/connected-slack-ticket-interaction-creation.gif
diff --git a/media/tidb-cloud/connected-slack-ticket-interaction-reply.gif b/media/tidb-cloud/connected-slack-ticket-interaction-reply.gif
diff --git a/media/tidb-cloud/data-service/GPTs1.png b/media/tidb-cloud/data-service/GPTs1.png
diff --git a/media/tidb-cloud/dedicated-external-storage/azure-sas-create.png b/media/tidb-cloud/dedicated-external-storage/azure-sas-create.png
diff --git a/media/tidb-cloud/dedicated-external-storage/azure-sas-position.png b/media/tidb-cloud/dedicated-external-storage/azure-sas-position.png
diff --git a/media/tidb-cloud/implementation-of-tidb-node-group.png b/media/tidb-cloud/implementation-of-tidb-node-group.png
diff --git a/media/tidb-cloud/migration-job-select-all.png b/media/tidb-cloud/migration-job-select-all.png
diff --git a/media/tidb-cloud/migration-job-select-db-blacklist1.png b/media/tidb-cloud/migration-job-select-db-blacklist1.png
diff --git a/media/tidb-cloud/migration-job-select-db-blacklist2.png b/media/tidb-cloud/migration-job-select-db-blacklist2.png
diff --git a/media/tidb-cloud/migration-job-select-db.png b/media/tidb-cloud/migration-job-select-db.png
diff --git a/media/tidb-cloud/migration-job-select-tables.png b/media/tidb-cloud/migration-job-select-tables.png
diff --git a/media/tidb-cloud/private-endpoint/create-endpoint-2.png b/media/tidb-cloud/private-endpoint/create-endpoint-2.png
diff --git a/media/tidb-cloud/serverless-external-storage/azure-sas-create.png b/media/tidb-cloud/serverless-external-storage/azure-sas-create.png
diff --git a/media/tidb-cloud/serverless-external-storage/azure-sas-position.png b/media/tidb-cloud/serverless-external-storage/azure-sas-position.png
diff --git a/media/tidb-cloud/serverless-external-storage/azure-storage-account-overview.png b/media/tidb-cloud/serverless-external-storage/azure-storage-account-overview.png
diff --git a/media/tidb-cloud/serverless-external-storage/gcs-service-account-key.png b/media/tidb-cloud/serverless-external-storage/gcs-service-account-key.png
diff --git a/media/tidb-cloud/serverless-external-storage/gcs-service-account.png b/media/tidb-cloud/serverless-external-storage/gcs-service-account.png
diff --git a/media/tidb-cloud/serverless-regional-high-avaliability-aws.png b/media/tidb-cloud/serverless-regional-high-avaliability-aws.png
diff --git a/media/tidb-cloud/serverless-zonal-high-avaliability-aws.png b/media/tidb-cloud/serverless-zonal-high-avaliability-aws.png
diff --git a/media/tidb-cloud/tidb-cloud-alert-subscription.png b/media/tidb-cloud/tidb-cloud-alert-subscription.png
diff --git a/media/tidb-cloud/tidb-cloud-clinic.png b/media/tidb-cloud/tidb-cloud-clinic.png
diff --git a/media/tidb-cloud/tidb-cloud-combo-box.png b/media/tidb-cloud/tidb-cloud-combo-box.png
diff --git a/media/tidb-cloud/tidb-cloud-dedicated-architecture.png b/media/tidb-cloud/tidb-cloud-dedicated-architecture.png
diff --git a/media/tidb-cloud/tidb-node-group-change-name.png b/media/tidb-cloud/tidb-node-group-change-name.png
diff --git a/media/tidb-cloud/tidb-node-group-change-node-count.png b/media/tidb-cloud/tidb-node-group-change-node-count.png
diff --git a/media/tidb-cloud/tidb-node-group-connect-public-endpoint.png b/media/tidb-cloud/tidb-node-group-connect-public-endpoint.png
diff --git a/media/tidb-cloud/tidb-node-group-create.png b/media/tidb-cloud/tidb-node-group-create.png
diff --git a/media/tidb-cloud/tidb-node-group-delete.png b/media/tidb-cloud/tidb-node-group-delete.png
diff --git a/media/tidb-cloud/v8.5.0_oltp_insert.png b/media/tidb-cloud/v8.5.0_oltp_insert.png
diff --git a/media/tidb-cloud/v8.5.0_oltp_point_select.png b/media/tidb-cloud/v8.5.0_oltp_point_select.png
diff --git a/media/tidb-cloud/v8.5.0_oltp_read_write.png b/media/tidb-cloud/v8.5.0_oltp_read_write.png
diff --git a/media/tidb-cloud/v8.5.0_oltp_update_index.png b/media/tidb-cloud/v8.5.0_oltp_update_index.png
diff --git a/media/tidb-cloud/v8.5.0_oltp_update_non_index.png b/media/tidb-cloud/v8.5.0_oltp_update_non_index.png
diff --git a/media/tidb-cloud/v8.5.0_tpcc.png b/media/tidb-cloud/v8.5.0_tpcc.png
diff --git a/media/vector-search/hybrid-search-overview.svg b/media/vector-search/hybrid-search-overview.svg
diff --git a/tidb-cloud/_index.md b/tidb-cloud/_index.md
@@ -1,5 +1,5 @@
 ---
-title: TiDB Cloud
+title: TiDB Cloud Documentation
 aliases: ['/tidbcloud/privacy-policy', '/tidbcloud/terms-of-service', '/tidbcloud/service-level-agreement']
 hide_sidebar: true
 hide_commit: true
@@ -12,20 +12,22 @@ summary: TiDB Cloud is a fully-managed Database-as-a-Service (DBaaS) that brings
 
 [Why TiDB Cloud](https://docs.pingcap.com/tidbcloud/tidb-cloud-intro)
 
-[Architecture](https://docs.pingcap.com/tidbcloud/tidb-cloud-intro#architecture)
+[Key Concepts](https://docs.pingcap.com/tidbcloud/key-concepts)
 
 [FAQ](https://docs.pingcap.com/tidbcloud/tidb-cloud-faq)
 
 </LearningPath>
 
 <LearningPath label="Try" icon="cloud5">
 
-[Try Out TiDB Cloud](https://docs.pingcap.com/tidbcloud/tidb-cloud-quickstart)
+[Try Out TiDB Cloud Serverless](https://docs.pingcap.com/tidbcloud/tidb-cloud-quickstart)
 
 [Try Out TiDB + AI](https://docs.pingcap.com/tidbcloud/vector-search-get-started-using-python)
 
 [Try Out HTAP](https://docs.pingcap.com/tidbcloud/tidb-cloud-htap-quickstart)
 
+[Try Out TiDB Cloud CLI](https://docs.pingcap.com/tidbcloud/get-started-with-cli)
+
 [Proof of Concept](https://docs.pingcap.com/tidbcloud/tidb-cloud-poc)
 
 </LearningPath>
@@ -70,7 +72,9 @@ summary: TiDB Cloud is a fully-managed Database-as-a-Service (DBaaS) that brings
 
 [From Amazon Aurora MySQL](https://docs.pingcap.com/tidbcloud/migrate-from-aurora-bulk-import)
 
-[From Amazon S3 or GCS](https://docs.pingcap.com/tidbcloud/migrate-from-amazon-s3-or-gcs)
+[From Amazon RDS for Oracle](https://docs.pingcap.com/tidbcloud/migrate-from-oracle-using-aws-dms)
+
+[From TiDB Self-Managed](https://docs.pingcap.com/tidbcloud/migrate-from-op-tidb)
 
 [From CSV Files](https://docs.pingcap.com/tidbcloud/import-csv-files)
 
@@ -146,12 +150,12 @@ summary: TiDB Cloud is a fully-managed Database-as-a-Service (DBaaS) that brings
 
 <LearningPath label="Reference" icon="cloud-dev">
 
+[SQL Reference](https://docs.pingcap.com/tidbcloud/basic-sql-operations)
+
 [System Variables](https://docs.pingcap.com/tidbcloud/system-variables)
 
 [Release Notes](https://docs.pingcap.com/tidbcloud/tidb-cloud-release-notes)
 
-[SQL Reference](https://docs.pingcap.com/tidbcloud/basic-sql-operations)
-
 </LearningPath>
 
 </LearningPathContainer>
diff --git a/tidb-cloud/ai-feature-concepts.md b/tidb-cloud/ai-feature-concepts.md
@@ -0,0 +1,50 @@
+---
+title: AI Features
+summary: Learn about AI features for TiDB Cloud.
+---
+
+# AI Features
+
+The AI features in TiDB Cloud enable you to fully leverage advanced technologies for data exploration, search, and integration. From natural language-driven SQL query generation to high-performance vector search, TiDB combines database capabilities with modern AI features to power innovative applications. With support for popular AI frameworks, embedding models, and seamless integration with ORM libraries, TiDB offers a versatile platform for use cases such as semantic search and AI-powered analytics.
+
+This document highlights these AI features and how they enhance the TiDB experience.
+
+## Chat2Query (Beta)
+
+Chat2Query is an AI-powered feature integrated into SQL Editor that assists users in generating, debugging, or rewriting SQL queries using natural language instructions. For more information, see [Explore your data with AI-assisted SQL Editor](/tidb-cloud/explore-data-with-chat2query.md).
+
+In addition, TiDB Cloud provides a Chat2Query API for TiDB Cloud Serverless clusters. After it is enabled, TiDB Cloud will automatically create a system Data App called Chat2Query and a Chat2Data endpoint in Data Service. You can call this endpoint to let AI generate and execute SQL statements by providing instructions. For more information, see [Get started with Chat2Query API](/tidb-cloud/use-chat2query-api.md).
+
+## Vector search (Beta)
+
+Vector search is a search method that prioritizes the meaning of your data to deliver relevant results.
+
+Unlike traditional full-text search, which relies on exact keyword matching and word frequency, vector search converts various data types (such as text, images, or audio) into high-dimensional vectors and queries based on the similarity between these vectors. This search method captures the semantic meaning and contextual information of the data, leading to a more precise understanding of user intent.
+
+Even when the search terms do not exactly match the content in the database, vector search can still provide results that align with the user's intent by analyzing the semantics of the data. For example, a full-text search for "a swimming animal" only returns results containing these exact keywords. In contrast, vector search can return results for other swimming animals, such as fish or ducks, even if these results do not contain the exact keywords.
+
+For more information, see [Vector Search (Beta) Overview](/vector-search/vector-search-overview.md).
+
+## AI integrations
+
+### AI frameworks
+
+TiDB provides official support for several popular AI frameworks, enabling you to easily integrate AI applications developed based on these frameworks with TiDB Vector Search.
+
+For a list of supported AI frameworks, see [Vector Search Integration Overview](/vector-search/vector-search-integration-overview.md#ai-frameworks).
+
+### Embedding models and services
+
+A vector embedding, also known as an embedding, is a sequence of numbers that represents real-world objects in a high-dimensional space. It captures the meaning and context of unstructured data, such as documents, images, audio, and videos.
+
+Embedding models are algorithms that transform data into [vector embeddings](/vector-search/vector-search-overview.md#vector-embedding). The choice of an appropriate embedding model is crucial for ensuring the accuracy and relevance of semantic search results.
+
+TiDB Vector Search supports storing vectors of up to 16383 dimensions, which accommodates most embedding models. For unstructured text data, you can find top-performing text embedding models on the [Massive Text Embedding Benchmark (MTEB) Leaderboard](https://huggingface.co/spaces/mteb/leaderboard).
+
+### Object Relational Mapping (ORM) libraries
+
+Object Relational Mapping (ORM) libraries are tools that facilitate the interaction between applications and relational databases by allowing developers to work with database records as if they were objects in their programming language of choice.
+
+TiDB lets you integrate vector search with ORM libraries to manage vector data alongside traditional relational data. This integration is particularly useful for applications that need to store and query vector embeddings generated by AI models. By using ORM libraries, developers can seamlessly interact with vector data stored in TiDB, leveraging the database's capabilities to perform complex vector operations like nearest neighbor search.
+
+For a list of supported ORM libraries, see [Vector Search Integration Overview](/vector-search/vector-search-integration-overview.md#object-relational-mapping-orm-libraries).
diff --git a/tidb-cloud/api-overview.md b/tidb-cloud/api-overview.md
@@ -3,7 +3,7 @@ title: TiDB Cloud API Overview
 summary: Learn about what is TiDB Cloud API, its features, and how to use API to manage your TiDB Cloud clusters.
 ---
 
-# TiDB Cloud API Overview <span style="color: #fff; background-color: #00bfff; border-radius: 4px; font-size: 0.5em; vertical-align: middle; margin-left: 16px; padding: 0 2px;">Beta</span>
+# TiDB Cloud API Overview (Beta)
 
 > **Note:**
 >
@@ -27,6 +27,6 @@ To start using TiDB Cloud API, refer to the following resources in TiDB Cloud AP
         - [Billing](https://docs.pingcap.com/tidbcloud/api/v1beta1/billing)
         - [Data Service](https://docs.pingcap.com/tidbcloud/api/v1beta1/dataservice)
         - [IAM](https://docs.pingcap.com/tidbcloud/api/v1beta1/iam)
-        - [MSP](https://docs.pingcap.com/tidbcloud/api/v1beta1/msp)
+        - [MSP (Deprecated)](https://docs.pingcap.com/tidbcloud/api/v1beta1/msp)
     - [v1beta](https://docs.pingcap.com/tidbcloud/api/v1beta#tag/Project)
 - [Changelog](https://docs.pingcap.com/tidbcloud/api/v1beta#section/API-Changelog)
diff --git a/tidb-cloud/architecture-concepts.md b/tidb-cloud/architecture-concepts.md
@@ -0,0 +1,104 @@
+---
+title: Architecture
+summary: Learn about architecture concepts for TiDB Cloud.
+---
+
+# Architecture
+
+TiDB Cloud is a fully-managed Database-as-a-Service (DBaaS) that brings the flexibility and power of [TiDB](https://docs.pingcap.com/tidb/stable/overview), an open-source HTAP (Hybrid Transactional and Analytical Processing) database, to AWS, Azure, and Google Cloud.
+
+TiDB is MySQL-compatible, making it easy to migrate and work with existing applications, while offering seamless scalability to handle everything from small workloads to massive, high-performance clusters. It supports both transactional (OLTP) and analytical (OLAP) workloads in one system, simplifying operations and enabling real-time insights.
+
+TiDB Cloud provides two deployment options: **TiDB Cloud** **Serverless**, for auto-scaling, cost-efficient workloads, and **TiDB Cloud Dedicated**, for enterprise-grade applications with dedicated resources and advanced capabilities. TiDB Cloud makes it easy to scale your database, handle complex management tasks, and stay focused on developing reliable, high-performing applications.
+
+## TiDB Cloud Serverless
+
+TiDB Cloud Serverless is a fully managed serverless solution that provides HTAP capabilities similar to traditional TiDB, while offering auto-scaling to alleviate users' burdens related to capacity planning and management complexities. It includes a free tier for basic usage, with consumption-based billing for any usage that exceeds the free limits. TiDB Cloud Serverless offers two types of high availability to address varying operational requirements.
+
+By default, clusters utilizing the Zonal High Availability option have all components located within the same availability zone, which results in lower network latency.
+
+![TiDB Cloud Serverless zonal high availability](/media/tidb-cloud/serverless-zonal-high-avaliability-aws.png)
+
+For applications that require maximum infrastructure isolation and redundancy, the Regional High Availability option distributes nodes across multiple availability zones.
+
+![TiDB Cloud Serverless regional high availability](/media/tidb-cloud/serverless-regional-high-avaliability-aws.png)
+
+## TiDB Cloud Dedicated
+
+TiDB Cloud Dedicated is designed for mission-critical businesses, offering high availability across multiple availability zones, horizontal scaling, and full HTAP capabilities.
+
+Built on isolated cloud resources such as VPCs, VMs, managed Kubernetes services, and cloud storage, it leverages the infrastructure of major cloud providers. TiDB Cloud Dedicated clusters support the complete TiDB feature set, enabling rapid scaling, reliable backups, deployment within specific VPCs, and geographic-level disaster recovery.
+
+![TiDB Cloud Dedicated Architecture](/media/tidb-cloud/tidb-cloud-dedicated-architecture.png)
+
+## TiDB Cloud console
+
+The [TiDB Cloud console](https://tidbcloud.com/) is the web-based management interface for both TiDB Cloud Serverless and TiDB Cloud Dedicated. It provides tools to manage clusters, import or migrate data, monitor performance metrics, configure backups, set up security controls, and integrate with other cloud services, all from a single, user-friendly platform.
+
+## TiDB Cloud CLI (Beta)
+
+The TiDB Cloud CLI, `ticloud`, allows you to manage TiDB Cloud Serverless and TiDB Cloud Dedicated directly from your terminal with simple commands. You can perform tasks such as:
+
+- Creating, deleting, and listing clusters.
+- Importing data into clusters.
+- Exporting data from clusters.
+
+For more information, see [TiDB Cloud CLI Reference](/tidb-cloud/cli-reference.md).
+
+## TiDB Cloud API (Beta)
+
+The TiDB Cloud API is a REST-based interface that provides programmatic access to manage resources across TiDB Cloud Serverless and TiDB Cloud Dedicated. It enables automated and efficient handling of tasks such as managing projects, clusters, backups, restores, data imports, billing, and other resources in [TiDB Cloud Data Service](/tidb-cloud/data-service-overview.md).
+
+For more information, see [TiDB Cloud API Overview](/tidb-cloud/api-overview.md).
+
+## Nodes
+
+In TiDB Cloud, each cluster consists of TiDB, TiKV, and TiFlash nodes.
+
+- In a TiDB Cloud Dedicated cluster, you can fully manage the number and size of your dedicated TiDB, TiKV, and TiFlash nodes according to your performance requirements. For more information, see [Scalability](/tidb-cloud/scalability-concepts.md).
+- In a TiDB Cloud Serverless cluster, the number and size of TiDB, TiKV, and TiFlash nodes are automatically managed. This ensures seamless scaling, eliminating the need for users to handle node configuration or management tasks.
+
+### TiDB node
+
+A [TiDB node](/tidb-computing.md) is a stateless SQL layer that connects to applications using a MySQL-compatible endpoint. It handles tasks like parsing, optimizing, and creating distributed execution plans for SQL queries.
+
+You can deploy multiple TiDB nodes to scale horizontally and manage higher workloads. These nodes work with load balancers, such as TiProxy or HAProxy, to provide a seamless interface. TiDB nodes do not store data themselves---they forward data requests to TiKV nodes for row-based storage or TiFlash nodes for columnar storage.
+
+### TiKV node
+
+A [TiKV node](/tikv-overview.md) is the backbone of data storage in the TiDB architecture, serving as a distributed transactional key-value storage engine that delivers reliability, scalability, and high availability.
+
+**Key features:**
+
+- **Region-based data storage**
+
+    - Data is divided into [Regions](https://docs.pingcap.com/tidb/dev/glossary#regionpeerraft-group), each covering a specific Key Range (left-closed, right-open interval: `StartKey` to `EndKey`).
+    - Multiple Regions coexist within each TiKV node to ensure efficient data distribution.
+
+- **Transactional support**
+
+    - TiKV nodes provide native distributed transaction support at the key-value level, ensuring Snapshot Isolation as the default isolation level.
+    - The TiDB node translates SQL execution plans into calls to the TiKV node API, enabling seamless SQL-level transaction support.
+
+- **High availability**
+
+    - All data in TiKV nodes is replicated (default: three replicas) for durability.
+    - TiKV ensures native high availability and supports automatic failover, safeguarding against node failures.
+
+- **Scalability and reliability**
+
+    - TiKV nodes are designed to handle expanding datasets while maintaining distributed consistency and fault tolerance.
+
+### TiFlash node
+
+A [TiFlash node](/tiflash/tiflash-overview.md) is a specialized type of storage node within the TiDB architecture. Unlike ordinary TiKV nodes, TiFlash is designed for analytical acceleration with a columnar storage model.
+
+**Key features:**
+
+- **Columnar storage**
+
+    TiFlash nodes store data in a columnar format, making them optimized for analytical queries and significantly improving performance for read-intensive workloads.
+
+- **Vector search index support**
+
+    The vector search index feature uses TiFlash replicas for tables, enabling advanced search capabilities and improving efficiency in complex analytical scenarios.
diff --git a/tidb-cloud/backup-and-restore-concepts.md b/tidb-cloud/backup-and-restore-concepts.md
@@ -0,0 +1,42 @@
+---
+title: Backup & Restore
+summary: Learn about backup & restore concepts for TiDB Cloud.
+---
+
+# Backup & Restore
+
+TiDB Cloud Backup & Restore features are designed to safeguard your data and ensure business continuity by enabling you to back up and recover cluster data.
+
+## Automatic backup
+
+For both TiDB Cloud Serverless and TiDB Cloud Dedicated clusters, snapshot backups are taken automatically by default and stored according to your backup retention policy.
+
+For more information, see the following:
+
+- [Automatic backups for TiDB Cloud Serverless clusters](/tidb-cloud/backup-and-restore-serverless.md#automatic-backups)
+- [Automatic backups for TiDB Cloud Dedicated clusters](/tidb-cloud/backup-and-restore.md#turn-on-auto-backup)
+
+## Manual backup
+
+Manual backup is a feature of TiDB Cloud Dedicated that enables you to back up your data to a known state as needed, and then restore to that state at any time.
+
+For more information, see [Perform a manual backup](/tidb-cloud/backup-and-restore.md#perform-a-manual-backup).
+
+## Dual region backup
+
+Dual region backup is a feature of TiDB Cloud Dedicated that enables you to replicate backups from your cluster region to another different region. After it is enabled, all backups are automatically replicated to the specified region. This provides cross-region data protection and disaster recovery capabilities. It is estimated that approximately 99% of the data can be replicated to the secondary region within an hour.
+
+For more information, see [Turn on dual region backup](/tidb-cloud/backup-and-restore.md#turn-on-dual-region-backup).
+
+## Point-in-time Restore
+
+Point-in-time Restore is a feature that enables you to restore data of any point in time to a new cluster. You can use it to:
+
+- Reduce RPO in disaster recovery.
+- Resolve cases of data write errors by restoring point-in-time that is before the error event.
+- Audit the historical data of the business.
+
+If you want to perform Point-in-time Restore, note the following:
+
+- For TiDB Cloud Serverless clusters, Point-in-time Restore is available only for scalable clusters and not available for free clusters. For more information, see [Restore mode](/tidb-cloud/backup-and-restore-serverless.md#restore-mode).
+- For TiDB Cloud Dedicated clusters, you need to [enable PITR](/tidb-cloud/backup-and-restore.md#turn-on-point-in-time-restore) in advance.