This topic describes the billing methods of Message Queue for Apache Kafka. You can select a billing method based on your business requirements.

Notice The connector feature of Message Queue for Apache Kafka is in public preview. This feature is independent of Message Queue for Apache Kafka instances. You are not charged on the Message Queue for Apache Kafka side when you use a connector to synchronize data between Message Queue for Apache Kafka and another Alibaba Cloud service. Alibaba Cloud does not provide a service level agreement (SLA) for the connector feature. For information about SLAs and pricing of other services that are required to use the connector feature, see the documentation of the related services.

Billing methods

Message Queue for Apache Kafka supports the following billing methods:

  • Subscription: You can use resources that are billed based on the subscription billing method only after you purchase the resources. This billing method is suitable for stable and long-term business scenarios.
  • Pay-as-you-go: If an instance uses the pay-as-you-go billing method, the instance is billed based on the number of resources that you use. In most cases, this billing method is used for testing or for short-term scenarios in which the traffic volume during peak hours is uncertain.
Note You can change the billing method of your instance only from pay-as-you-go to subscription. When you change the billing method, you cannot change the specifications of your instance. For more information, see Change the billing method from pay-as-you-go to subscription.

For a detailed description of each billing method, see the following topics.

  • Subscription
    Billing rules
    Instance renewal
  • Pay-as-you-go
    Billing rules
  • Other related topics
    Change the billing method from pay-as-you-go to subscription
    Set the notification policy for imminent overdue payments and instance release
    Overdue payments
    View billing and usage details
    Billing FAQ