If an instance is billed based on the pay-as-you-go billing method, you are charged based on the number of resources that you use. In most cases, this billing method is suitable for testing or short-term scenarios in which the traffic fluctuates during peak hours. You are charged based on the number of resources that you use. Payments are settled on an hourly basis.

Formula

Billable items and their unit prices vary based on the instance type. For more information about billable items, see Overview.
  • Internet- and VPC-connected instances: Instances of this type can be accessed over the Internet or from a virtual private cloud (VPC).

    Total fee = (Unit price of Internet traffic + Unit price of a traffic specification + Unit price of a disk capacity × Disk capacity/100 + Unit price of a topic × Number of additional topics) × Number of hours

  • VPC-connected instances: Instances of this type can be accessed only from a VPC.

    Total fee = (Unit price of a traffic specification + Unit price of a disk capacity × Disk capacity/100 + Unit price of a topic × Number of additional topics) × Number of hours

Billing description

For the pay-as-you-go billing method, you are charged for the billable items, such as the traffic specification and disk capacity, that you specify when you create and deploy an instance.
  • Payments are settled on an hourly basis. The usage duration shorter than an hour is calculated as an hour.
  • Fees are calculated each hour and a bill is generated at intervals of 24 hours. The fees that are incurred on the previous day are deducted from your Alibaba Cloud account balance based on your bill generated on the current day.

After you purchase a pay-as-you-go Message Queue for Apache Kafka instance, the system allocates resources to your instance. For the pay-as-you-go billing method, the instance is billed based on the following formula: Total fee = Unit price of the instance × Service time. You are charged for the instance even if you do not use the instance. If you have questions about the billing, you can view the billing details. For more information, see View billing and usage details.

Billing

Note If the information provided in the following table is different from the information provided on the buy page in the console, the information on the buy page takes precedence.
  • Billing rules for Internet traffic
    The billing of Elastic IP Address is related to the BGP (Multi-ISP) line bandwidth, and the unit price varies slightly between regions.
    Table 1. Billing rules for Internet traffic
    Region Bandwidth unit price (USD per Mbit/s-day)
    1 Mbps 2 Mbps 3 Mbps 4 Mbps 5 Mbps 6 Mbit/s and higher (n indicates the bandwidth value)
    China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Ulanqab), China (Shenzhen), China (Heyuan), China (Guangzhou), China (Chengdu), Malaysia (Kuala Lumpur), China (Hong Kong), Singapore (Singapore), Indonesia (Jakarta), US (Virginia), and US (Silicon Valley), Germany (Frankfurt), UK (London), and Philippines (Manila) 0.14 0.28 0.43 0.57 0.71 0.71+(n-5)× 0.5
    China (Qingdao) 0.11 0.21 0.32 0.43 0.53 0.53+(n-5)× 0.46
    Japan (Tokyo) 0.17 0.34 0.51 0.68 0.85 0.85+(n-5)× 0.57
  • Billing rules for traffic specifications

    The billing rules for traffic specifications vary based on your instance edition. Standard Edition (High Write), Professional Edition (High Write), and Professional Edition (High Read) instances support different traffic specifications. The maximum traffic processed by a cluster and the number of topics in the cluster vary based on the traffic specification of the cluster. If the peak read/write traffic is high, a large number of topics are used and the fee incurred is high. The unit price of a traffic specification varies based on the region group to which your region belongs. For more information about region groups, see Region groups.

    For more information about the specifications of each instance edition, see Instance editions.

    • For more information about the billing of Standard Edition (High Write) instance traffic specifications, see Table 2.
    • For more information about the billing of traffic specifications for Pro Edition (High Write Edition) instances, see Table 3.
    • For more information about the billing of traffic specifications of Professional Edition (High Read Edition) instances, see Table 4.
    Table 2. Billing rules for traffic specifications of Standard Edition (High Write) instances
    Traffic specification Maximum read traffic of ENIs (MB/s) Maximum write traffic of ENIs (MB/s) Number of free topics Number of free partitions Unit price in region group 1 (USD/hour) Unit price in region group 2 (USD/hour) Unit price in region group 3 (USD/hour)
    alikafka.hw.2xlarge 3×20 3×20 50 400 0.335 0.470 0.420
    alikafka.hw.3xlarge 3×30 3×30 50 500 0.475 0.650 0.590
    alikafka.hw.6xlarge 3×60 3×60 80 600 0.655 0.880 0.790
    alikafka.hw.9xlarge 3×90 3×90 100 800 0.800 1.050 0.930
    alikafka.hw.12xlarge 3×120 3×120 150 900 0.960 1.250 1.100
    Table 3. Billing rules for traffic specifications of Professional Edition (High Write) instances
    Traffic specification Maximum read traffic of ENIs (MB/s) Maximum write traffic of ENIs (MB/s) Number of free topics Number of free partitions Unit price in region group 1 (USD/hour) Unit price in region group 2 (USD/hour) Unit price in region group 3 (USD/hour)
    alikafka.hw.2xlarge 3×20 3×20 50 1100 0.80 1.17 1.06
    alikafka.hw.3xlarge 3×30 3×30 50 1200 0.99 1.45 1.31
    alikafka.hw.6xlarge 3×60 3×60 80 1400 1.34 1.980 1.77
    alikafka.hw.9xlarge 3×90 3×90 100 1600 1.59 2.37 2.11
    alikafka.hw.12xlarge 3×120 3×120 150 1800 1.88 2.82 2.50
    alikafka.hw.16xlarge 3×160 3×160 180 2000 2.09 3.16 2.78
    alikafka.hw.20xlarge 3×200 3×200 200 2200 3.25 4.87 4.32
    alikafka.hw.25xlarge 3×250 3×250 250 2500 3.67 5.51 4.88
    alikafka.hw.30xlarge 3×300 3×300 300 3000 4.00 6.03 5.31
    alikafka.hw.60xlarge 3×600 3×600 450 4500 4.25 6.62 5.64
    alikafka.hw.80xlarge 3×800 3×800 500 5000 4.41 7.00 5.85
    alikafka.hw.100xlarge 3×1000 3×1000 600 6000 4.56 7.39 6.04
    alikafka.hw.120xlarge 3×1200 3×1200 700 7000 4.69 7.71 6.21
    alikafka.hw.150xlarge 3×1500 3×1500 800 8000 4.94 8.30 6.54
    alikafka.hw.180xlarge 3×1800 3×1800 900 9000 5.16 8.84 6.83
    alikafka.hw.200xlarge 3×2000 3×2000 1000 10000 5.34 9.29 7.05
    Table 4. Billing rules for traffic specifications of Professional Edition (High Read) instances
    Traffic specification Maximum read traffic of ENIs (MB/s) Maximum write traffic of ENIs (MB/s) Number of free topics Number of free partitions Unit price in region group 1 (USD/hour) Unit price in region group 2 (USD/hour) Unit price in region group 3 (USD/hour)
    alikafka.hw.2xlarge 50+2×10 10+2×10 50 1100 0.80 1.17 1.06
    alikafka.hw.3xlarge 75+2×15 15+2×15 50 1200 0.99 1.45 1.31
    alikafka.hw.6xlarge 150+2×30 30+2×30 80 1400 1.34 1.98 1.77
    alikafka.hw.9xlarge 180+2×45 45+2×45 100 1600 1.59 2.37 2.11
    alikafka.hw.12xlarge 240+2×60 60+2×60 150 1800 1.88 2.82 2.50
    alikafka.hw.16xlarge 240+2×80 80+2×80 180 2000 2.09 3.160 2.780
    alikafka.hw.20xlarge 300+2×100 100+2×100 200 2200 3.25 4.87 4.32
    alikafka.hw.25xlarge 375+2×125 125+2×125 250 2500 3.67 5.51 4.88
    alikafka.hw.30xlarge 450+2×150 150+2×150 300 3000 4.00 6.03 5.31
    alikafka.hw.60xlarge 900+2×300 300+2×300 450 4500 4.25 6.62 5.64
    alikafka.hw.80xlarge 1200+2×400 400+2×400 500 5000 4.41 7.00 5.85
    alikafka.hw.100xlarge 1500+2×500 500+2×500 600 6000 4.56 7.39 6.04
    alikafka.hw.120xlarge 1800+2×600 600+2×600 700 7000 4.69 7.71 6.21
    alikafka.hw.150xlarge 2250+2×750 750+2×750 800 8000 4.94 8.30 6.54
    alikafka.hw.180xlarge 2700+2×900 900+2×900 900 9000 5.16 8.84 6.83
    alikafka.hw.200xlarge 3000+2×1000 1000+2×1000 1000 10000 5.34 9.29 7.05
  • Billing rules for disk capacity

    The billing rules for a disk capacity vary based on the disk type. The unit price of a disk capacity varies based on the region group to which your region belongs. If the free disk capacity does not meet your business requirements, you can purchase the additional disk capacity by adjusting the value of the Disk Capacity parameter on the buy page to a larger value.

    Disk type Disk size (GB) Unit price in region group 1 (USD/hour) Unit price in region group 2 (USD/hour) Unit price in region group 3 (USD/hour)
    Ultra disk 100 0.01 0.02 0.02
    SSD 100 0.03 0.04 0.04
    Note
    • The disk cost of Professional Edition instances that store data in three replicas is approximately 60% lower than the disk cost of self-managed open source instances.
    • The minimum disk capacity is used to prevent issues such as rollback failures. Rollback failures occur when messages are not frequently deleted. If you want to reduce the minimum disk capacity in specific scenarios, submit a ticket.
  • Billing rules for additional topics

    If the number of free topics that are provided in the specification does not meet your business requirements, you must purchase more topics by adjusting the value of the Topics parameter on the buy page to a larger value. Sixteen partitions are added each time a topic is purchased. If the specified number of topics reaches the upper limit of the current traffic specification, we recommend that you select a higher traffic specification because a higher traffic specification corresponds to more topics. This helps reduce your costs. The unit price of each added topic varies based on the region group.

    Billable item Number of topics Unit price in region group 1 (USD/hour) Unit price in region group 2 (USD/hour) Unit price in region group 3 (USD/hour)
    Topic 1 0.02 0.02 0.02
    Note The default number of topics indicates the minimum number of topics that are supported for an instance. If you purchase a smaller number of topics than the minimum number of required topics, resources are allocated to the instance based on the minimum number of required topics. As a result, your costs cannot be reduced.
  • Region groups
    Table 5. Region groups
    Region group Region
    Region group 1 China (Hangzhou)
    China (Shanghai)
    China (Qingdao)
    China (Beijing)
    China (Zhangjiakou)
    China (Hohhot)
    China (Ulanqab)
    China (Shenzhen)
    China (Heyuan)
    China (Guangzhou)
    China (Chengdu)
    Region group 2 Hong Kong
    Singapore (Singapore)
    Japan (Tokyo)
    US (Virginia)
    US (Silicon Valley)
    Germany (Frankfurt)
    UK (London)
    Region group 3 Malaysia (Kuala Lumpur)
    India (Mumbai)
    Indonesia (Jakarta)
    Philippines (Manila)