DocsICP FilingConsole
Documentation
Home Page Microservices Engine Product Overview Billing Cloud-native Gateway Billing for general-purpose instances

Billing for general-purpose instances

Updated at:
Copy as MD
Product
My Favorites

Learn about billing items, billing methods, and pricing for MSE Cloud Native Gateway general-purpose instances in Standard and Professional editions.

Billing

Standard Edition

  • Instance fees

    Calculated based on the unit price of the instance type and the number of nodes.

  • SLB fees

    When you purchase a Standard Edition instance, you can choose to purchase an NLB or SLB load balancer instance as the gateway entry point. The system automatically creates the instance. SLB fees are billed separately by the load balancer service and charged directly to your account. MSE does not charge SLB fees. For more information, see NLB Billing Overview or CLB Billing Overview.

Professional Edition

  • Instance fees

    Calculated based on the unit price of the instance type and the number of nodes.

    The Professional Edition provides more advanced features than the Standard Edition. For example, it integrates deeply with SLB and uses hardware-accelerated Gzip decompression, reducing network bandwidth costs by approximately 40% with minimal CPU overhead. This feature is available only for 8-core 16 GB and 16-core 32 GB instance types.

  • Internet traffic fees

    Internet traffic for Professional Edition instances is billed through Cloud Data Transfer (CDT). For more information, see CDT Public Bandwidth Pricing.

    Professional Edition instances have no bandwidth limit and no bandwidth cap. You do not select a bandwidth specification when you purchase or reconfigure a Professional Edition instance, so you do not need to reserve bandwidth for traffic peaks. Internet usage is billed based on the actual Internet traffic (data processing volume) that the instance generates, not on a bandwidth specification. As your traffic grows, the instance is not throttled by a bandwidth cap, but your Internet traffic fees increase accordingly.

  • Data processing fees

    When you create a gateway instance, you can select one of the following network types: Public, Private, or Public + Private. Data processing volume is billed separately for each network type. Within a billing period, the data processing volume equals the sum of request and response data.

    Region

    Network type

    Unit price (USD/GB/hour)

    Public cloud

    Public

    0.037

    Private

    0.049

    Financial cloud

    Public

    0.07

    Private

    0.093
    Billing formula

    • Public network: Hourly fee = Data processing volume × Unit price.

      For example, for a gateway instance that processes 5 GB of data in the first hour and 10 GB in the second, the total data processing fee is 0.037 * 5 + 0.037 * 10 = 0.555 USD.

    • Private network: Hourly fee = Data processing volume × Unit price.

      For example, for a gateway instance that processes 5 GB of data in the first hour and 10 GB in the second, the total data processing fee is 0.049 * 5 + 0.049 * 10 = 0.735 USD.

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.84 × 5 × 3 = 12.60 CNY.

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: 422 × 12 × 3 = 15,192 CNY.

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

    Note

    To 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: 422 × 3 × 1 + 2.2 (unit price of a 2-core 4 GiB elastic node) × 1 × 2 × 30 = 1,398 CNY.

Instance charges

Note

For current pricing, see the Product Purchase Page.

Region

Node specification

Pay-as-you-go price (CNY/hour)

Subscription price (CNY/month)

Elastic node price (CNY/hour)

Chinese mainland

2 Core 4 GiB

0.84

422

2.20

4 Core 8 GiB

1.68

844

4.40

8 Core 16 GiB

3.35

1688

8.77

16 Core 32 GiB

6.7

3376

17.55

  • China (Hong Kong)

  • Japan (Tokyo)

2 Core 4 GiB

1.26

633

3.30

4 Core 8 GiB

2.52

1266

6.60

8 Core 16 GiB

5.03

2532

13.17

16 Core 32 GiB

10.05

5064

26.32

  • Singapore

  • Indonesia (Jakarta)

  • Germany (Frankfurt)

2 Core 4 GiB

1.16

582

3.04

4 Core 8 GiB

2.32

1165

6.08

8 Core 16 GiB

4.62

2329

12.10

16 Core 32 GiB

9.25

4659

24.23

  • US (Virginia)

  • US (Silicon Valley)

2 Core 4 GiB

1.01

506

2.65

4 Core 8 GiB

2.02

1013

5.29

8 Core 16 GiB

4.02

2026

10.53

16 Core 32 GiB

8.04

4051

21.06

Malaysia (Kuala Lumpur)

2 Core 4 GiB

1.08

544

2.83

4 Core 8 GiB

2.17

1089

5.68

8 Core 16 GiB

4.32

2178

11.31

16 Core 32 GiB

8.64

4355

22.63

Finance Cloud and Government Cloud

2 Core 4 GiB

1.6

802

4.18

4 Core 8 GiB

3.2

1604

8.36

8 Core 16 GiB

6.37

3207

16.66

16 Core 32 GiB

12.73

6414

33.35

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)

private data transfer

pay-as-you-go

No

public data transfer

pay-as-you-go

No

gateway instance type

pay-as-you-go

Yes

Cloud Native Gateway (subscription)

gateway instance type

subscription

Yes

public data transfer

subscription

Yes

private data transfer

subscription

No

Cloud Native Gateway (elastic node)

gateway instance type

pay-as-you-go

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.

Previous：Cloud-native gateway capacity and performanceNext：Billing overview for serverless instances