ApsaraMQ for RocketMQ non-Serverless series instances support two billing methods: subscription (prepaid) and pay-as-you-go (postpaid). Both methods share the same billable items but differ in how the computing specification fee is charged. Choose subscription for stable, long-running workloads, or pay-as-you-go for testing and short-term use.
Billing methods
The following table compares the two billing methods available for non-Serverless series instances.
| Billing method | Charging model | Best for |
| Subscription | Select a computing specification and pay upfront for a subscription period (in months). Other resources are billed based on actual usage. | Stable workloads with predictable, high traffic volume. |
| Pay-as-you-go | Select a computing specification. You are billed hourly for instance runtime. Other resources are billed based on actual usage. | Early-stage testing, short-term workloads, or traffic evaluation before committing to subscription. |
After testing, you can switch from pay-as-you-go to subscription billing. For more information, seeChange the billing method from pay-as-you-go to subscription.
Supported editions
The non-Serverless series includes the following editions. The edition you select determines the computing specification options and, in turn, affects the computing specification fee.
| Edition | Description |
| Standard Edition | Entry-level edition for development, testing, and small-scale production workloads. |
| Professional Edition | Mid-tier edition with enhanced performance and higher throughput for production workloads. |
| Enterprise Platinum Edition | Top-tier edition for mission-critical, large-scale production workloads requiring maximum performance and stability. |
For more information about edition differences and selection guidance, seeSelect a suitable edition.
Billable items
Non-Serverless series instances (subscription and pay-as-you-go) include the following billable items.
| Billable item | Charging model | Description |
| Computing specification fee for messaging | Subscription: prepaid monthly; Pay-as-you-go: postpaid hourly | The base cost for the instance's computing resources for message processing. |
| Storage fee | Postpaid based on actual usage | Charged based on the amount of message data stored. |
| Public network access fee | Postpaid based on actual usage | Charged when public network access is enabled. |
| Elastic TPS fee | Postpaid based on actual usage | Charged for TPS usage that exceeds the base specification. |
| Topic fee | Postpaid based on actual usage | Charged based on the number of topics created. This fee does not apply to 5.x instances. |
Billing cycle
Subscription instances — Billed at purchase time for the full subscription period. Other resource fees are settled hourly.
Pay-as-you-go instances — All fees are settled hourly. A bill is generated each hour after instance creation.
References
Pay-as-you-go instances can be converted to subscription. Subscription instances cannot be converted to pay-as-you-go. For more information, seeChange the billing method from pay-as-you-go to subscription.
After creating an instance, you can adjust the computing specification to match your actual business needs. For more information, seeUpgrade or downgrade instance configurations.
For a general introduction to billing across all series, seeBilling overview.
For information about Serverless series billing, seeBilling of Serverless series instances.