Billing Overview
Last updated:2026-01-30 14:40:38
This document mainly introduces the specifications, billing modes, and pricing of the TDMQ for MQTT cluster.
Product Series
TDMQ for MQTT currently offers multiple edition specifications. For differences between editions, see Product Series. Each specification provides two billing methods: yearly/monthly subscription (prepaid) and pay-as-you-go (postpaid).
Billing Mode
TDMQ for MQTT clusters support two billing modes: Monthly subscription (prepaid) and pay-as-you-go (postpaid). The differences between billing modes are as follows:
Billing Mode | Monthly Subscription (Prepaid) | Pay as you go (Postpaid) |
Billing instruction | Select specified specifications and prepay for a certain period before you can use the resources. | Select specified specifications to create a cluster and pay after using the resources. |
Billing Cycle | Billed based on the purchased duration of the order. | Billed by the hour, with daily deductions. Usage less than one hour is rounded up to one hour. |
Applicable Scenario | Suitable for scenarios with stable business scale and long-term usage, offering discounted pricing to help reduce long-term costs. | Suitable for short-term scenarios such as testing or uncertain traffic peaks, billed on a pay-as-you-go basis to avoid idle resource wastage. |
Changing the billing mode | Not supported. | Not supported. |
Change the cluster specification | Supported | Supported. |
Cluster specification downgrade | Supported | Supported |
Billing Items
TDMQ for MQTT edition is sold in the form of clusters. The billing item composition is as follows:
Billing Item | Required | Billing Mode | Billing Rules |
Compute specifications | Yes | yearly/monthly subscription/pay-as-you-go | Provide multiple TPS specifications, with each specifying the cluster's number of client connections, separately purchasable connection limit, and message read/write TPS capacity limit. |
Number of connections | No | yearly/monthly subscription/pay-as-you-go | If the number of connections included in your current MQTT cluster specification cannot meet your requirements, you can purchase additional connections separately. |
Public Network Traffic Fees | No | Pay-as-you-go | Enabling public network access will incur fees based on actual traffic usage, billed by the total amount of data transmitted over the public network (in GB). Settlements occur hourly, with charges calculated according to actual usage. You can disable this feature at any time. If public network access is not enabled, no fees will be incurred. |
Pricing
Compute Specification Fees
The compute specifications provided by TDMQ for MQTT and the performance limits for each specification are as shown in the table below:
TPS specifications: The TPS capacity provided by the MQTT cluster, including the sum of production TPS and consumption TPS.
Number of connections: Refers to the sum of online clients and offline clients with preserved sessions at any given moment.
Notes:
When the MQTT protocol is used to send and receive messages, each message's send/receive operation is counted as 1 basic unit of measurement. TPS specifications are comprehensively calculated based on the sum of three dimensions: message service QoS, message storage resource usage, and message size. Specifically:
Message Service QoS
Message Service QoS=0 is calculated as 1 TPS.
Message Service QoS=1 is calculated as 2 TPS.
Message Service QoS=2 is calculated as 5 TPS.
Storage Resource Usage
When messages use the Will feature and Retain feature, they require additional Broker storage resources. Therefore, when users configure the Will and Retain features, an additional 10 TPS is calculated for each.
message body size
Each message is calculated in units of 4KB. If the size is less than 4KB, no additional TPS is calculated; for every additional 4KB, an additional 1 TPS is calculated.
For example, a cluster has 3 clients connected at the same time. At this time, the cluster sends a QoS=1 message to the first client, with a message body size of 64KB. The corresponding cluster production TPS specification is calculated as 2 + ceil(64/4 - 1) = 17 TPS. The cluster receives a QoS=2 message from the second client with the Retain feature enabled, with a message body size of 32KB. The corresponding cluster message TPS specification is calculated as 5 + 10 + ceil(32/4 - 1) = 22 TPS. The third client connects to the cluster and enables the Will feature, with an additional calculation of 10 TPS. At this time, the comprehensive cluster TPS specification is calculated as 17 + 22 + 10 = 49 TPS.
Edition | TPS Specification | Complimentary Free Connections (Number) | Maximum Number of Connections (Purchased Separately) (Number) | Price |
Basic Edition (New purchases have been discontinued) | 2000 | 2000 | Connections cannot be purchased separately. | |
| 5000 | 5000 | | |
Pro Edition | 2000 | 2000 | 20000 | |
| 5000 | 5000 | 50000 | |
| 10000 | 10000 | 100000 | |
| 20000 | 20000 | 200000 | |
| 50000 | 50000 | 500000 | |
Number of Connections Cost
After selecting the TPS size, if the number of connections provided free of charge within the corresponding specifications still does not meet your requirements, you can purchase additional connections separately. Connections are purchased with the cluster TPS specification as the basic unit (1 unit). The pricing is as follows:
Edition | Purchasable Connections (unit) | Price |
Pro Edition | 1x TPS specification 2x TPS specification 5x TPS specification 10x TPS specification | |
Basic Edition (no longer available for new purchases) | Connections cannot be purchased separately. | |
Public Network Traffic Fees
Notes:
The current billed traffic is outbound traffic (Mbps), indicating the traffic from Cloud Load Balancer (CLB) to the public network.
To prevent high costs caused by sudden traffic bursts, you can specify an upper limit on the bandwidth. If the traffic volume exceeds the upper limit of the bandwidth, packets will be discarded by default, and no fees will be charged.
The unit conversion scale for traffic is 1024. That is, 1 TB = 1024 GB, and 1 GB = 1024 MB.
Region | Price (Unit: USD/GB) |
Guangzhou/Shanghai/Beijing/Nanjing | 0.14 |
Shanghai Autonomous Driving Cloud | 0.23 |
Singapore/Silicon Valley/Frankfurt | 0.19 |
Purchase Methods
You can log in to the TDMQ for MQTT console for self-service purchase. For specific steps, see Create Cluster.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback