ApsaraMQ for RocketMQ serverless instances are billed pay-as-you-go based on actual resource usage. Select an instance type that matches your workload to optimize costs.
Notes
-
This topic covers billing for ApsaraMQ for RocketMQ Serverless shared and dedicated instances. For existing Standard and Professional Edition billing, see Billing of existing Serverless Standard and Professional Edition instances.
-
For differences between shared/dedicated and existing Standard/Professional Edition billable items, see Differences in billable items between existing Serverless Standard/Professional Edition instances and shared/dedicated instances.
Limits
Enabling public network access for a Serverless instance requires SDK code changes. See Version Guide for Public Network Access for Serverless Instances.
Billable items
ApsaraMQ for RocketMQ serverless instances are billed pay-as-you-go starting from instance creation. Bills are generated hourly.
Billable items:
Message requests fee
Applies to ApsaraMQ for RocketMQ serverless instances using the pay-by-messaging-request billing method.
Billing formula
Message requests fee = Total number of message requests × Unit price per request (USD/request)
How message requests are counted
Number of message requests = Number of received messages + Number of delivered messages
-
Number of received messages: The number of messages that the server-side receives from producers. For example, if the server-side receives five messages for a topic, the number of received messages is five.
-
Number of delivered messages: The number of times the server-side delivers messages to consumers. Each successful delivery to a consumer counts as one delivery request, regardless of whether the consumer processes the message or returns an ACK response.
-
Payload size: The number of delivery requests is calculated based on the message size in 4 KB blocks. A message smaller than 4 KB counts as 4 KB. For example, delivering an 18 KB message results in ⌈18/4⌉ = 5 delivery requests.
Note⌈ ⌉ indicates rounding up.
Tiered pricing
Unit prices vary by region.
Unit prices in public cloud regions (USD/million requests)
|
Region |
Tier |
Total monthly message requests (100 millions) |
Normal message |
Scheduled/delayed message |
Transactional message |
Scheduled/delayed message |
Transactional message |
Ordered message |
|
Send and consume |
Consume |
Consume |
Send |
Send |
Send and consume |
|||
|
China (Hangzhou), China (Shanghai), China (Shenzhen), China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Chengdu), China (Ulanqab), China (Heyuan), China (Guangzhou), China (Fuzhou - Local Region - Phasing Out), China (Nanjing - Local Region - Phasing Out), Zhengzhou (China Unicom Cloud), China (Hong Kong), Singapore, Japan (Tokyo), Germany (Frankfurt), UK (London), US (Silicon Valley), US (Virginia), South Korea (Seoul), Thailand (Bangkok), Malaysia (Kuala Lumpur), Indonesia (Jakarta), Philippines (Manila) |
Tier 1 |
(0, 10] |
0.305 |
1.525 |
||||
|
Tier 2 |
(10, 50] |
0.183 |
0.915 |
|||||
|
Tier 3 |
(50, 200] |
0.153 |
0.765 |
|||||
|
Tier 4 |
>200 |
0.122 |
0.61 |
|||||
|
UAE (Dubai) |
Tier 1 |
(0, 10] |
0.61 |
3.05 |
||||
|
Tier 2 |
(10, 50] |
0.366 |
1.83 |
|||||
|
Tier 3 |
(50, 200] |
0.306 |
1.53 |
|||||
|
Tier 4 |
>200 |
0.244 |
1.22 |
|||||
|
US (Atlanta) |
Tier 1 |
(0, 10] |
0.412 |
2.059 |
||||
|
Tier 2 |
(10, 50] |
0.247 |
1.235 |
|||||
|
Tier 3 |
(50, 200] |
0.207 |
1.033 |
|||||
|
Tier 4 |
>200 |
0.165 |
0.824 |
|||||
Unit prices in the Saudi Arabia region (USD/million requests)
|
Region |
Billing Tiers |
Total monthly message requests (100 millions) |
Normal message |
Scheduled/delayed message |
Transactional message |
Scheduled/delayed message |
Transactional message |
Ordered message |
|
Send and consume |
Consume |
Consume |
Send |
Send |
Send and consume |
|||
|
SAU (Riyadh - Partner Region) |
Tier 1 |
(0, 10] |
0.366 |
1.83 |
||||
|
Tier 2 |
(10, 50] |
0.2196 |
1.098 |
|||||
|
Tier 3 |
(50, 200] |
0.1836 |
0.918 |
|||||
|
Tier 4 |
>200 |
0.1464 |
0.732 |
|||||
Instance fee
The instance fee applies to ApsaraMQ for RocketMQ serverless instances using the pay-by-messaging-request billing method. It primarily covers PrivateLink instance fees across two zones and includes a free quota for connections and metadata.
Unit price
|
Region |
Unit price (USD/instance/hour) |
|
All regions |
0.0452 |
Billing example
The fee for one month (30 days) is calculated as follows: 0.0452 × 24 × 30 = USD 32.544.
Provisioned capacity fee
Applies to ApsaraMQ for RocketMQ serverless instances using the Provisioned + Elastic billing method. Calculated based on provisioned capacity and usage duration.
Billing formula
Hourly provisioned capacity fee = Provisioned capacity (TPS) × Unit price of provisioned capacity (USD/TPS/hour)
Unit price
Unit prices in public cloud regions
|
Region |
Tier |
Shared |
Dedicated |
||
|
Provisioned capacity specification (TPS) |
Unit price (USD/TPS/hour) |
Provisioned capacity specification (TPS) |
Unit price (USD/TPS/hour) |
||
|
China (Hangzhou), China (Shanghai), China (Shenzhen), China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Chengdu), China (Ulanqab), China (Heyuan), China (Guangzhou), China (Fuzhou - Local Region - Phasing Out), China (Nanjing - Local Region - Phasing Out), Zhengzhou (China Unicom Cloud), China (Hong Kong), Singapore, Japan (Tokyo), Germany (Frankfurt), UK (London), US (Silicon Valley), US (Virginia), South Korea (Seoul), Thailand (Bangkok), Malaysia (Kuala Lumpur), Indonesia (Jakarta), Philippines (Manila) |
Tier 1 |
(0, 2000] |
0.000135 |
(0, 5000] |
0.000173 |
|
Tier 2 |
(2000, 8000] |
0.000113 |
(5000, 20000] |
0.000128 |
|
|
Tier 3 |
(8000, 50000] |
0.00006 |
(20000, 100000] |
0.000098 |
|
|
Tier 4 |
>50000 |
0.000045 |
>100000 |
0.000075 |
|
|
UAE (Dubai) |
Tier 1 |
(0, 2000] |
0.00027 |
(0, 5000] |
0.000346 |
|
Tier 2 |
(2000, 8000] |
0.000226 |
(5000, 20000] |
0.000256 |
|
|
Tier 3 |
(8000, 50000] |
0.00012 |
(20000, 100000] |
0.000196 |
|
|
Tier 4 |
>50000 |
0.00009 |
>100000 |
0.00015 |
|
|
US (Atlanta) |
Tier 1 |
(0, 2000] |
0.000182 |
(0, 5000] |
0.000234 |
|
Tier 2 |
(2000, 8000] |
0.000153 |
(5000, 20000] |
0.000173 |
|
|
Tier 3 |
(8000, 50000] |
0.000081 |
(20000, 100000] |
0.000132 |
|
|
Tier 4 |
>50000 |
0.000061 |
>100000 |
0.000101 |
|
Unit prices in the Saudi Arabia region
|
Region |
Tier |
Shared |
Dedicated |
||
|
Provisioned capacity specification (TPS) |
Unit price (USD/TPS/hour) |
Provisioned capacity specification (TPS) |
Unit price (USD/TPS/hour) |
||
|
SAU (Riyadh - Partner Region) |
Tier 1 |
(0, 2000] |
0.000162 |
(0, 5000] |
0.0002076 |
|
Tier 2 |
(2000, 8000] |
0.0001356 |
(5000, 20000] |
0.0001536 |
|
|
Tier 3 |
(8000, 50000] |
0.000072 |
(20000, 100000] |
0.0001176 |
|
|
Tier 4 |
>50000 |
0.000054 |
>100000 |
0.00009 |
|
Billing example
Assume that you have a shared Serverless instance in the China (Hangzhou) region. The billing method is Provisioned + Elastic, and the provisioned capacity is 4,000 TPS. The hourly provisioned capacity fee is calculated as follows: 2,000 × 0.000135 + (4,000 - 2,000) × 0.000113 = USD 0.496. The fee for one month (30 days) is then calculated as follows: 0.496 × 24 × 30 = USD 357.12.
Elastic TPS fee
For ApsaraMQ for RocketMQ serverless instances using the Provisioned + Elastic billing method, an elastic TPS fee applies to usage exceeding the provisioned capacity.
Billing formula
<hetu formula="Hourly elastic TPS fee=\sum_{1\le i\le 60} [T_i×Elastic TPS]×Elastic TPS unit price (USD/TPS/minute)" hetuid="79bd114d-a5d6-445a-b50d-77cd4fe3e995" id="fb0c71c992wxw" style="display:inline-block;max-width:100%;overflow:auto;vertical-align:middle" type="xFormula"><span class="katex"><span aria-hidden="true" class="katex-html"><span class="base"><span class="strut" style="height:0.6833em;">Hourly elasticTPSfee=</span><span class="strut" style="height:2.4229em;vertical-align:-1.3728em;"><span class="vlist-t vlist-t2"><span class="vlist-r"><span class="vlist" style="height:1.05em;"><span style="top:-1.8723em;margin-left:0em;"><span class="pstrut" style="height:3.05em;"><span class="mord mtight"><span class="mord vbox mtight"><span class="thinbox mtight"><span class="clap mtight"><span class="strut" style="height:0.7955em;vertical-align:-0.136em;"><span><span class="mord mtight"><span class="mord mtight">1\lei\le60</span></span></span></span></span></span></span></span></span><span class="pstrut" style="height:3.05em;"><span class="mop op-symbol large-op">∑</span></span></span></span><span class="vlist" style="height:1.3728em;"><span></span></span></span></span>[<span class="mord mathnormal" style="margin-right:0.13889em;">T</span>i×</span><span class="strut" style="height:1em;vertical-align:-0.25em;">ElasticTPS]×</span><span class="strut" style="height:1em;vertical-align:-0.25em;">ElasticTPSunit price (USD/TPS/minute)</span></span></span></span></hetu>
In this formula, T1, T2, ..., Ti, ..., T60 represent the first, second, ..., i-th, and 60th minutes of the hour, respectively.
Unit price
Unit prices in public cloud regions
|
Region |
Unit price (USD/TPS/hour) |
|
|
Shared |
Dedicated |
|
|
China (Hangzhou), China (Shanghai), China (Shenzhen), China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Chengdu), China (Ulanqab), China (Heyuan), China (Guangzhou), China (Fuzhou - Local Region - Phasing Out), China (Nanjing - Local Region - Phasing Out), Zhengzhou (China Unicom Cloud), China (Hong Kong), Singapore, Japan (Tokyo), Germany (Frankfurt), UK (London), US (Silicon Valley), US (Virginia), South Korea (Seoul), Thailand (Bangkok), Malaysia (Kuala Lumpur), Indonesia (Jakarta), Philippines (Manila) |
0.000019 |
0.000025 |
|
UAE (Dubai) |
0.000038 |
0.00005 |
|
US (Atlanta) |
0.000026 |
0.000034 |
Unit prices in the Saudi Arabia region
|
Region |
Unit price (USD/TPS/hour) |
|
|
Shared |
Dedicated |
|
|
SAU (Riyadh - Partner Region) |
0.0000228 |
0.00003 |
Billing example
Assume that you have a shared serverless instance in the China (Hangzhou) region. The billing method is Provisioned + Elastic, and the provisioned capacity is 5,000 TPS. In a specific hour, the instance runs as follows:
|
Time |
Minute 00 |
Minute 01 |
Minute 02 |
Minute 03 |
...... |
Minute 58 |
59 points |
|
Peak actual TPS of the instance (requests/second) |
5200 |
5300 |
4000 |
4500 |
All less than 5,000 |
4800 |
5100 |
|
Incremental TPS value (requests/second) |
200 |
300 |
0 |
0 |
0 |
0 |
100 |
In this hour, the elastic TPS fee for the instance is calculated as follows: (1 × 200 + 1 × 300 + 1 × 100) × 0.000019 = USD 0.0114.
Online Client Count Fee
Counting rule for online clients
One producer or one consumer object counts as one online client.
Billing formula
If online clients exceed the free quota, the excess is billed hourly (partial hours rounded up):
Online client fee = Number of billable online clients × Unit price per client (USD/client/hour)
Free quota for online clients
|
Deployment architecture |
Capacity mode |
TPS specification |
Maximum online clients |
Number of Free Online Clients |
|
Shared |
Cumulative amount |
All |
5,000 |
500 |
|
Provisioned + Elastic |
[2000, 20,000] |
5,000 |
1,000 |
|
|
(20,000, 50,000] |
8,000 |
2,000 |
||
|
(50,000, 100,000] |
10,000 |
3,000 |
||
|
(100,000, 200,000] |
20,000 |
5,000 |
||
|
Dedicated |
Provisioned + Elastic |
5,000 |
3,000 |
2,000 |
|
10,000 |
6,000 |
4,000 |
||
|
15,000 |
8,000 |
6,000 |
||
|
[20,000, 50,000] |
10,000 |
8,000 |
||
|
(50,000, 100,000] |
20,000 |
10,000 |
||
|
(100,000, 200,000] |
40,000 |
20,000 |
||
|
(200,000, 300,000] |
80,000 |
40,000 |
||
|
(300,000, 500,000] |
100,000 |
50,000 |
||
|
(500,000, 1,000,000] |
200,000 |
100,000 |
Unit price
|
Region |
Unit Price (USD per unit per hour) |
|
All regions |
0.00003 |
Resource fee
Resources are the total number of topics and consumer groups. A resource fee applies when usage exceeds the free quota.
Billing formula
If resources exceed the free quota, the excess is billed hourly (partial hours rounded up):
Resource fee = Number of billable resources × Unit price per resource (USD/resource/hour)
Free quota for resources
|
Deployment architecture |
Maximum connections |
TPS specification |
Free resource quota (count) |
|
Shared |
By cumulative amount |
All |
100 |
|
Provisioned + Elastic |
All |
200 |
|
|
Dedicated |
Provisioned + Elastic |
[0, 10,000] |
300 |
|
(10,000, 100,000] |
500 |
||
|
(100,000, 200,000] |
1,000 |
||
|
(200,000, 300,000] |
1,500 |
||
|
(300,000, 500,000] |
2,000 |
||
|
(500,000, 1,000,000] |
3,000 |
Unit price
|
Region |
Billing Tiers |
Number of resources (exceeding the free quota) |
Unit price (USD/resource/hour) |
|
All regions |
Tier 1 |
[0, 500] |
0.00015 |
|
Tier 2 |
(500, 1000] |
0.000092 |
|
|
Tier 3 |
>1000 |
0.00006 |
Storage fee
ApsaraMQ for RocketMQ serverless instances are billed based on server-side message storage space and duration. Partial hours are rounded up.
Billing formula
Hourly storage fee = Used storage space (GB) × Unit price for storage (USD/GB/hour)
Unit price
|
Region |
Unit price for storage space (USD/GB/hour) |
|
China (Hangzhou), China (Shanghai), China (Shenzhen), China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Chengdu), China (Ulanqab), China (Heyuan), China (Guangzhou), China (Hong Kong), Singapore, Japan (Tokyo), Germany (Frankfurt), UK (London), US (Silicon Valley), US (Virginia), US (Atlanta), South Korea (Seoul), Thailand (Bangkok), Malaysia (Kuala Lumpur), Indonesia (Jakarta), Philippines (Manila) |
0.0002 |
|
UAE (Dubai) |
0.00036 |
Public network fee
ApsaraMQ for RocketMQ charges for outbound public network traffic when public network access is enabled.
No fee applies if public network access is disabled.
Billing formula
Hourly public network fee = Total outbound public network traffic (GB) × Unit price for traffic (USD/GB)
Unit price
|
Region |
Unit price for outbound public network traffic (USD/GB/hour) |
|
China (Hangzhou), China (Shanghai), China (Shenzhen), China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Chengdu), China (Ulanqab), China (Heyuan), China (Guangzhou), China (Hong Kong), Singapore, Japan (Tokyo), Germany (Frankfurt), UK (London), US (Silicon Valley), US (Virginia), UAE (Dubai), US (Atlanta), South Korea (Seoul), Thailand (Bangkok), Malaysia (Kuala Lumpur), Indonesia (Jakarta), Philippines (Manila) |
0.15 |
|
SAU (Riyadh - Partner Region) |
0.19 |