Learn about billing items, billing methods, and pricing for MSE Cloud Native Gateway general-purpose instances in Standard and Professional editions.
Billing
Instance fees
Calculated based on the instance type unit price and the number of nodes.
SLB fees
When purchasing a Standard Edition instance, you can add an NLB or SLB load balancer instance as the gateway entry point. The system automatically creates the selected instance. The SLB instance is billed separately by the load balancer service, and the fees are charged directly to your account. MSE does not charge any fees for the SLB instance. For more information, see NLB billing overview or CLB billing overview.
Billing methods
The following billing methods are available for general-purpose instances:
|
Billing method |
Description |
Use cases |
|
pay-as-you-go (post-paid) |
You are billed hourly for the resources you consume. |
Ideal for workloads with fluctuating usage or for short-term needs. |
|
subscription (pre-paid) |
You pay in advance for a fixed period, such as monthly or annually. |
Ideal for workloads with stable usage and for long-term requirements. |
Billing cycles and formulas
Pay-as-you-go
-
Billing cycle
Billed hourly, with a bill generated every 24 hours. Charges are automatically deducted from your Alibaba Cloud account balance. The specific bill generation time may vary.
-
Billing formula
-
Billing example
For example, if you purchase a 2-core 4 GiB pay-as-you-go instance in the Chinese mainland with 3 nodes and run it for 5 hours, the total fee is: 0.136 × 5 × 3 = 2.04 USD.
Subscription
-
Billing cycle
Billed monthly. An annual subscription covers a 12-month period. Charges are automatically deducted from your Alibaba Cloud account balance. The specific bill generation time may vary.
-
Billing formula
-
Billing example
For example, if you purchase a 2-core 4 GiB subscription instance in the Chinese mainland with 3 nodes for a one-year term, the total fee is: 69 × 12 × 3 = 2,484 USD.
Auto scaling
Cloud-native Gateway general-purpose instances support auto scaling. You can configure a time window for auto scaling to handle business peaks. Elastic nodes created by auto scaling are billed separately on a pay-as-you-go basis. In your billing details, the product name for these nodes is Cloud-native Gateway (Elastic Node).
-
Billing formula
NoteTo calculate the fixed node fee, see Pay-as-you-go or Subscription.
To calculate the elastic node fee, see Pay-as-you-go. The unit price of an elastic node is higher than the pay-as-you-go unit price of a regular node. For more details, see Instance fees.
-
Billing example
For example, you purchase a 2-core 4 GiB subscription instance in the Chinese mainland with 3 nodes. You also configure the instance to scale out to 4 nodes every day from 20:00 to 22:00. This generates daily charges for one 2-core 4 GiB elastic node running for two hours.
The total monthly fee for this instance is: 69 × 3 × 1 + 0.341 (unit price of a 2-core 4 GiB elastic node) × 1 × 2 × 30 = 227.46 USD.
Instance charges
For current pricing, see the Product Purchase Page.
|
Region |
Node specification |
Pay-as-you-go price (USD/hour) |
Subscription price (USD/month) |
Elastic node price (USD/hour) |
|
Chinese mainland |
2 Core 4 GiB |
0.136 |
69 |
0.341 |
|
4 Core 8 GiB |
0.273 |
137 |
0.681 |
|
|
8 Core 16 GiB |
0.544 |
274 |
1.357 |
|
|
16 Core 32 GiB |
1.088 |
548 |
2.716 |
|
|
2 Core 4 GiB |
0.205 |
103 |
0.511 |
|
4 Core 8 GiB |
0.409 |
206 |
1.022 |
|
|
8 Core 16 GiB |
0.816 |
411 |
2.038 |
|
|
16 Core 32 GiB |
1.632 |
822 |
4.074 |
|
|
2 Core 4 GiB |
0.188 |
95 |
0.471 |
|
4 Core 8 GiB |
0.376 |
189 |
0.941 |
|
|
8 Core 16 GiB |
0.751 |
378 |
1.873 |
|
|
16 Core 32 GiB |
1.501 |
757 |
3.750 |
|
|
2 Core 4 GiB |
0.164 |
82 |
0.410 |
|
4 Core 8 GiB |
0.327 |
164 |
0.819 |
|
|
8 Core 16 GiB |
0.653 |
329 |
1.630 |
|
|
16 Core 32 GiB |
1.306 |
658 |
3.260 |
|
|
Malaysia (Kuala Lumpur) |
2 Core 4 GiB |
0.175 |
88 |
0.438 |
|
4 Core 8 GiB |
0.352 |
177 |
0.879 |
|
|
8 Core 16 GiB |
0.702 |
354 |
1.751 |
|
|
16 Core 32 GiB |
1.404 |
708 |
3.503 |
Tag-based cost allocation
Cloud Native Gateway general-purpose instances support attaching tags to enable split billing for your enterprise. For more information, see Using split billing by tag.
|
Product name |
Billable item |
Billing type |
Tag-based allocation |
|
Cloud Native Gateway (pay-as-you-go) |
gateway instance type |
pay-as-you-go |
Yes |
|
Cloud Native Gateway (subscription) |
gateway instance type |
subscription |
Yes |
Unsubscription
If you no longer need a Cloud Native Gateway instance, you can unsubscribe to stop incurring charges. For more information, see Unsubscribe from resources.