Billing Overview
Last updated: 2025-12-02 17:27:18
Billing Mode
TencentDB for MySQL offers the following billing mode:
Billing Mode | Payment Mode | Use Case |
Monthly subscription | It is suitable for long-term needs with relatively stable business volume. The cost is more moderate compared to the pay-as-you-go billing. The longer the purchase duration, the greater the discount. | |
Pay-as-you-go | In this postpaid billing mode, you can apply for resources for on-demand use and will be charged based on the actual usage at the billing time. | It is suitable for instantaneously fluctuating businesses. In this mode, instances can be released immediately after the use to save costs. |
Instance Pricing
Billing formula
Total fees = memory and cpu fees + storage capacity fees + backup capacity fees + traffic fees (currently waived)
Billable items
Billable Item | Description |
memory and cpu fees | The cost of the instance specifications selected on the purchase page, which include memory and CPU, supports both subscription and pay-as-you-go tiered pricing. For pricing details, please see Product Pricing. The pay-as-you-go pricing adopts a three-tier system, where longer usage periods result in greater discounts: Tier 1 (T1) applies from 0 to 96 hours; Tier 2 (T2) from 96 to 360 hours; and Tier 3 (T3) for usage beyond 360 hours. |
storage capacity fees | The cost of the disk size selected on the purchase page supports both annual/monthly subscription and pay-as-you-go billing. For pricing details, please see Product Pricing. The storage space is utilized for storing essential data files for the operation of the cloud database MySQL, including shared tablespaces, error log files, REDO LOG, UNDO LOG, data dictionaries, and binlog, among others. |
backup capacity fees | TencentDB for MySQL offer complimentary backup storage quotas based on the region. The size of the free backup storage is equivalent to the sum of the storage spaces of all dual-node and triple-node instances (including primary and disaster recovery instances) within the specified region. For information on charges applicable to backup storage exceeding the free quota, please see Backup Space Billing. |
traffic fees | Public network traffic fees are currently waived. |
You may directly utilize the Pricing Calculator to view the composite pricing of the products you require, thereby estimating the cost of resources. To ensure the accuracy of the prices obtained, please log in to Tencent Cloud before proceeding to view them.
Note:
The disk fee (storage space fee) of a read-only instance is consistent with that of the primary instance. You can see Product Pricing for details, as shown below.
Read-Only Analysis Engine Pricing Overview
The billing formula for the MySQL read-only analytics engine is as follows:
For single-node selection: Total cost of the read-only analytics engine = Cost of single-node computing resources + Unit price of storage space × Purchased storage capacity
Multi-node: Total read-only analysis engine fees = Fees of total multi-node computing resources + Total storage space of all nodes x Unit price of storage space
Note：
When selecting multi-node, the number of purchased nodes can be either 2 or 3.
Compute Resource Pricing of Read-Only Analysis Engine
When creating a read-only analytics engine instance, you can specify the number of nodes. A single-node configuration defaults to one node, while multi-node configurations allow you to choose between two or three nodes. The unit price of computing resources varies between single-node and multi-node setups. You may refer to the table below for detailed pricing information.
Instance Type | Compute Node Specifications | Beijing, Shanghai, Guangzhou, Chengdu, and Nanjing | Hong Kong (China) | Singapore, Virginia, São Paulo, and Frankfurt | |||
| | Monthly Subscription (USD/Month) | Pay-as-You-Go (USD/Hour) | Monthly Subscription (USD/Month) | Pay-as-You-Go (USD/Hour) | Monthly Subscription (USD/Month) | Pay-as-You-Go (USD/Hour) |
General | 4-core 16 GB single-node | 64.28571429 | 0.13392857 | 107.3571429 | 0.22366071 | 156.25 | 0.325 |
General | 8-core 32 GB single-node | 100 | 0.20833333 | 167 | 0.34791666 | 312.5 | 0.65 |
General | 16-core 64 GB single-node | 200 | 0.41666667 | 334 | 0.69583333 | 625 | 1.3 |
General | 24-core 96 GB single-node | 535.71428571 | 1.11607143 | 894.6428571 | 1.86383928 | 937.5 | 1.953125 |
General | 32-core 128 GB single-node | 714.28571429 | 1.48809524 | 1192.857143 | 2.48511905 | 1250 | 2.60416667 |
General | 64-core 256 GB single-node | 1428.57142857 | 2.97619048 | 2385.714286 | 4.9702381 | 2500 | 5.20833334 |
General | 96-core 384 GB single-node | 2142.85714286 | 4.46428571 | 3578.571429 | 7.45535713 | 3750 | 7.8125 |
General | 128-core 512 GB single-node | 2857.14285714 | 5.95238095 | 4771.428571 | 9.94047618 | 5000 | 10.41666666 |
Instance Type | Compute Node Specifications | Beijing, Shanghai, Guangzhou, Chengdu, and Nanjing | Hong Kong (China) | Singapore, Virginia, São Paulo, and Frankfurt | |||
| | Monthly Subscription (USD/Month) | Pay-as-You-Go (USD/Hour) | Monthly Subscription (USD/Month) | Pay-as-You-Go (USD/Hour) | Monthly Subscription (USD/Month) | Pay-as-You-Go (USD/Hour) |
General | 4-core 16 GB | 89.28571429 | 0.18571429 | 149.1071429 | 0.31014284 | 156.25 | 0.325 |
General | 8-core 32 GB | 178.5714286 | 0.37142857 | 298.2142857 | 0.62028571 | 312.5 | 0.65 |
General | 12-core 48 GB | 267.8571429 | 0.55714285 | 447.3214286 | 0.93042856 | 468.75 | 0.975 |
General | 16-core 64 GB | 357.1428571 | 0.74285714 | 596.4285714 | 1.24057142 | 625 | 1.3 |
General | 20-core 80 GB | 446.4285715 | 0.92857145 | 745.5357145 | 1.5507142 | 781.25 | 1.625 |
General | 24-core 96 GB | 535.7142857 | 1.11607143 | 894.6428571 | 1.86383928 | 937.5 | 1.953125 |
General | 28-core 112 GB | 625 | 1.3 | 1043.75 | 2.17099988 | 1093.75 | 2.275 |
General | 32-core 128 GB | 714.2857143 | 1.48809524 | 1192.857143 | 2.48511905 | 1250 | 2.60416667 |
General | 36-core 144 GB | 803.5714286 | 1.67142861 | 1341.964286 | 2.79128556 | 1406.25 | 2.925 |
General | 40-core 160 GB | 892.8571429 | 1.85714285 | 1491.071429 | 3.10142855 | 1562.5 | 3.25 |
General | 48-core 192 GB | 1071.428571 | 2.22857142 | 1789.285714 | 3.72171426 | 1875 | 3.9 |
General | 56-core 224 GB | 1250 | 2.6 | 2087.5 | 4.34199997 | 2187.5 | 4.55 |
General | 60-core 240 GB | 1339.285715 | 2.78571425 | 2236.607143 | 4.6521428 | 2343.75 | 4.875 |
General | 64-core 256 GB | 1428.571429 | 2.97619048 | 2385.714286 | 4.9702381 | 2500 | 5.20833334 |
General | 72-core 288 GB | 1607.142857 | 3.34714285 | 2683.928571 | 5.58972856 | 2812.5 | 5.8575 |
General | 80-core 320 GB | 1785.714286 | 3.7142857 | 2982.142857 | 6.2028571 | 3125 | 6.5 |
General | 84-core 336 GB | 1875 | 3.89999995 | 3131.25 | 6.51299992 | 3281.25 | 6.825 |
General | 96-core 384 GB | 2142.857143 | 4.46428571 | 3578.571429 | 7.45535713 | 3750 | 7.8125 |
General | 108-core 432 GB | 2410.714286 | 5.01428565 | 4025.892857 | 8.37385704 | 4218.75 | 8.775 |
General | 112-core 448 GB | 2500 | 5.19999998 | 4175 | 8.68399994 | 4375 | 9.1 |
General | 120-core 480 GB | 2678.571429 | 5.5714285 | 4473.214286 | 9.3042856 | 4687.5 | 9.75 |
General | 128-core 512 GB | 2857.142857 | 5.95238095 | 4771.428571 | 9.94047618 | 5000 | 10.41666666 |
General | 144-core 576 GB | 3214.285713 | 6.68571426 | 5367.857142 | 11.16514278 | 5625 | 11.7 |
General | 160-core 640 GB | 3571.428571 | 7.4285714 | 5964.285714 | 12.4057142 | 6250 | 13 |
General | 168-core 672 GB | 3750 | 7.81250001 | 6262.5 | 13.04687496 | 6562.5 | 13.67187502 |
General | 192-core 768 GB | 4285.714286 | 8.92714285 | 7157.142858 | 14.90832856 | 7500 | 15.6225 |
General | 216-core 864 GB | 4821.428571 | 10.04464287 | 8051.785714 | 16.77455352 | 8437.5 | 17.57812502 |
General | 224-core 896 GB | 5000 | 10.41666668 | 8350.000001 | 17.39583335 | 8750 | 18.22916669 |
General | 240-core 960 GB | 5357.142857 | 11.1428571 | 8946.428571 | 18.6085713 | 9375 | 19.5 |
General | 256-core 1024 GB | 5714.285714 | 11.9057142 | 9542.857142 | 19.88254286 | 10000 | 20.835 |
General | 288-core 1152 GB | 6428.571429 | 13.3928571 | 10735.71429 | 22.36607142 | 11250 | 23.4375 |
General | 320-core 1280 GB | 7142.857143 | 14.8809524 | 11928.57143 | 24.8511905 | 12500 | 26.0416667 |
General | 336-core 1344 GB | 7499.999999 | 15.6 | 12525 | 26.05199982 | 13125 | 27.3 |
General | 360-core 1440 GB | 8035.714285 | 16.73571425 | 13419.64286 | 27.9486428 | 14062.5 | 29.2875 |
General | 384-core 1536 GB | 8571.428571 | 17.8585714 | 14314.28571 | 29.82381429 | 15000 | 31.25249995 |
General | 432-core 1728 GB | 9642.857142 | 20.05714278 | 16103.57143 | 33.49542834 | 16875 | 35.1 |
General | 448-core 1792 GB | 10000 | 20.83333336 | 16700 | 34.7916667 | 17500 | 36.45833338 |
General | 480-core 1920 GB | 10714.28571 | 22.2857142 | 17892.85714 | 37.2171426 | 18750 | 39 |
General | 504-core 2016 GB | 11250 | 23.42999995 | 18787.5 | 39.12809992 | 19687.5 | 41.0025 |
General | 512-core 2048 GB | 11428.57143 | 23.80952384 | 19085.71429 | 39.7619048 | 20000 | 41.66666672 |
General | 576-core 2304 GB | 12857.14286 | 26.78571426 | 21471.42857 | 44.73214278 | 22500 | 46.875 |
General | 640-core 2560 GB | 14285.71429 | 29.7619048 | 23857.14286 | 49.702381 | 25000 | 52.0833334 |
General | 648-core 2592 GB | 14464.28571 | 30.12428565 | 24155.35714 | 50.30755704 | 25312.5 | 52.7175 |
General | 672-core 2688 GB | 15000 | 31.24999997 | 25050 | 52.18749991 | 26250 | 54.6875 |
General | 720-core 2880 GB | 16071.42857 | 33.4285713 | 26839.28571 | 55.8257139 | 28125 | 58.5 |
General | 768-core 3072 GB | 17142.85714 | 35.71428568 | 28628.57143 | 59.64285704 | 30000 | 62.5 |
General | 864-core 3456 GB | 19285.71429 | 40.17857139 | 32207.14286 | 67.09821417 | 33750 | 70.3125 |
General | 896-core 3584 GB | 20000 | 41.66666665 | 33400 | 69.58333326 | 35000 | 72.91666664 |
General | 960-core 3840 GB | 21428.57143 | 44.6428571 | 35785.71429 | 74.5535713 | 37500 | 78.125 |
General | 1024-core 4096 GB | 22857.14286 | 47.6190476 | 38171.42857 | 79.52380944 | 40000 | 83.3333333 |
General | 1152-core 4608 GB | 25714.28572 | 53.5714284 | 42942.85716 | 89.46428568 | 45000 | 93.75 |
General | 1280-core 5120 GB | 28571.42857 | 59.528571 | 47714.28571 | 99.4127143 | 50000 | 104.175 |
Storage Space Pricing of Read-Only Analysis Engine
Regardless of whether it is a single-node mode or a multi-node mode, the unit price of storage space for the read-only analytics engine remains unchanged.
Beijing, Shanghai, Guangzhou, Chengdu, and Nanjing | Hong Kong (China) | Singapore, Virginia, São Paulo, and Frankfurt | |||
Monthly Subscription (USD/GB/Month) | Pay-as-You-Go (USD/GB/Hour) | Monthly Subscription (USD/GB/Month) | Pay-as-You-Go (USD/GB/Hour) | Monthly Subscription (USD/GB/Month) | Pay-as-You-Go (USD/GB/Hour) |
0.282 | 0.00039167 | 0.3384 | 0.000514 | 0.2286 | 0.000413 |
Value-Added Service Pricing Overview
Database Audit Pricing
Database auditing facilitates the recording of access to the database and the execution of SQL statements, aiding organizations in risk management and enhancing data security levels. Charges for database auditing apply only after it has been activated. The pricing is detailed in the table below. For more comprehensive information, please see Database Audit Billing Overview.
Region | Price (USD/GB/Hour) | |
| Frequent Access Storage | Infrequent Access Storage |
China (including finance regions, Hong Kong, Macao, and Taiwan) | 0.00147059 | 0.00018382 |
Other countries and regions | 0.00220588 | 0.00027573 |
Database Proxy Pricing
The Database Proxy acts as a network proxy service situated between the cloud database service and application services, facilitating the proxying of all requests made by application services when accessing the database. This service operates on a pay-as-you-go basis, with the billing unit being CU. Pricing for the Database Proxy varies by region, as detailed in the table below. For more comprehensive information, you are encouraged to see Commercial Billing and Activity Description for Database Proxy.
Note：
The term CU refers to the minimum billing specification of the database proxy (i.e. the price for a 2-core proxy specification with 4,000 MB memory). There are three specifications for the database proxy node: a 2-core one with 4,000 MB memory, a 4-core one with 8,000 MB memory, and an 8-core one with 16,000 MB memory. These correspond to 1 CU, 2 CU, and 4 CU respectively.
Region | Price (USD/CU/Hour) |
Shanghai, Nanjing, Chongqing, Chengdu, Guangzhou, Beijing | 0.06865672 |
Hong Kong (China) | 0.11492537 |
Jakarta, Virginia, Bangkok, Tokyo, Singapore, Seoul, Toronto, Frankfurt, Silicon Valley, São Paulo | 0.11791045 |
Shenzhen Finance, Beijing Finance, Shanghai Finance | 0.11641791 |
Note：
The regions displayed above represent all the regions where the current instance supports deployment. Some regions do not yet support the database proxy feature. The regions that do support it include Beijing, Shanghai, Guangzhou, Shanghai Finance, Beijing Finance, Chengdu, Chongqing, Nanjing, Hong Kong (China), Tokyo, Bangkok, Virginia, Silicon Valley, Seoul, and Singapore.
CPU Elastic Scale-out Price
The CPU elastic scale-out feature can effectively alleviate performance pressure caused by sudden requests, adapt to peak business traffic, and ensure the stability of online businesses. It also supports CPU scale-in during periods of decreased traffic to avoid resource waste. The specific billing formula and price are as follows. Go to Billing Instructions for more detailed information.
Billing Formula
The CPU elastic scale-out feature is charged in pay-as-you-go mode. It is charged by the minute, and the fee is deducted once per hour.
Billing formula = (Single-core fee x Added CPU cores) x Scale-out duration (minutes)/60.
Single-Core Fee
Region | Unit Price (USD/Core/Hour) |
Chengdu and Chongqing | 0.03 |
Guangzhou, Shanghai, Beijing, and Nanjing | 0.04 |
Hong Kong (China), Tokyo, Seoul, and Bangkok | 0.0495 |
Frankfurt and São Paulo | 0.0365 |
Singapore, Jakarta, Silicon Valley, Virginia, and Riyadh | 0.061 |
Region | Unit Price (USD/Core/Hour) |
Chengdu and Chongqing | 0.06 |
Guangzhou, Shanghai, Beijing, and Nanjing | 0.08 |
Hong Kong (China), Tokyo, Seoul, and Bangkok | 0.099 |
Frankfurt and São Paulo | 0.073 |
Singapore, Jakarta, Silicon Valley, Virginia, and Riyadh | 0.122 |
Region | Unit Price (USD/Core/Hour) |
Chengdu and Chongqing | 0.09 |
Guangzhou, Shanghai, Beijing, and Nanjing | 0.12 |
Hong Kong (China), Tokyo, Seoul, and Bangkok | 0.1485 |
Frankfurt and São Paulo | 0.1095 |
Singapore, Jakarta, Silicon Valley, Virginia, and Riyadh | 0.183 |
Billing Examples
Note:
The prices used in the following examples are for demonstration purposes only, which may vary depending on regions, campaigns, or policies. Please see the pricing page for actual prices.
Suppose that:
You purchase a monthly-subscribed Two-Node TencentDB for MySQL instance with 4 cores, 8,000 MB memory, and 500 GB disk space in the Guangzhou Zone 3 for 1 month.
You purchase a monthly-subscribed Two-Node TencentDB for MySQL instance with 4 cores, 8,000 MB memory, and 200 GB disk space in the Guangzhou Zone 4 for 1 month.
Total fees = memory and cpu fees + storage capacity fees + backup capacity fees
Memory and cpu fees
In the Guangzhou region, the monthly rate for an instance with 4 cores and 8000MB is 120 USD/month. Therefore, the cost for memory and cpu = 2 × 120 USD/month × 1 month = 240 USD.
Storage capacity fees
In the Guangzhou region, the monthly subscription rate for instance disks is 0.10588 USD/GB/month. Therefore, the cost for storage capacity = (500GB + 200GB) × 0.10588 USD/GB/month × 1 month = 74.116 USD.
Backup capacity fees
The high-availability TencentDB for MySQL instance in Guangzhou Zone 3 has 500 GB storage capacity per month, and the one in Guangzhou Zone 4 has 200 GB storage capacity per month, so you can have 700 GB backup capacity free of charge in the Guangzhou region every month.
Usage of backup capacity that exceeds the free tier are calculated on an hourly basis according to the following rule. For example, if your data backups reach 800 GB and log backups reach 100 GB, your total backup capacity usage in Guangzhou will exceed 700 GB, and your hourly billable backup capacity will be 200 GB (800 + 100 - 700 = 200).
Backup capacity fees (hourly) = 200 GB (usage of backup capacity that exceeds the free tier may change over time) x 0.000113 USD/GB/hour.
FAQs
Why are additional fees incurred for my monthly-subscribed instance?
Usage of backup capacity that exceeds the free tier will be charged. Please check whether your usage of backup capacity exceeds the free tier.
You can check the usage of backup capacity on the Database Backup page in the TencentDB for MySQL console. For more information about backup capacity pricing, please see Backup Space Billing.
Will Tencent Cloud charge for pay-as-you-go instances if they are idle?
Yes. If you stop using pay-as-you-go resources, please terminate them as soon as possible to avoid further fees.
What files are stored in the storage capacity?
Data files: the space which your data takes up, including created tables and indexes.
System files (necessary for the database): shared tablespaces, error logs, redo logs, undo logs, and data dictionaries.
Binlogs: binlogs record all DDL and DML statements (except SELECT and SHOW statements) and are used to replicate and restore database data. The more data changes, the more binlogs. To reduce the space binlogs take up, they can be uploaded to COS.
Documentation
You can purchase TencentDB for MySQL instances through the console or API. For more information, please see Purchase Methods.
TencentDB for MySQL sends alert messages to you before it expires and its resources are repossessed. For more information, please see Overdue Payment.
You can return TencentDB for MySQL instances and request a refund. For more information, please see Refund.
TencentDB for MySQL supports the conversion of billing modes. For more information, please see Pay-as-You-Go to Monthly Subscription.
You can adjust TencentDB for MySQL instances to a higher or lower specification. For more information, please see Instance Adjustment Fee.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback