This topic describes the billable items, billing method, billing cycle, and pricing for Cloud Native Gateway serverless instances.
Billable items
The billable items for Cloud Native Gateway are the fees for managed gateway instances. Cloud Native Gateway uses SLB as the ingress to meet the requirements of different gateway environments. You can associate one or more public or private network SLBs with a gateway instance based on your business requirements. The fees for the SLB that MSE purchases on your behalf based on the specifications you select are directly charged to your account. MSE does not charge SLB fees.
Billing method
Pay-As-You-Go: You are charged based on actual usage. This model is ideal for fluctuating service traffic.
Billing cycle
Pay-As-You-Go serverless instances are billed hourly. At the beginning of each hour, the system calculates and deducts the fees for the previous hour's usage from your Alibaba Cloud account. The actual billing time may vary.
Instance pricing
A serverless instance is billed based on a tiered cumulative pricing model according to the total number of requests received during a billing cycle. Costs are calculated in units of 10,000 requests, and the price per unit varies by tier, as shown in the following table.
-
Even if an instance receives no service traffic (zero requests) after creation, it incurs a minimum charge of CNY 0.135 per hour.
-
The system rounds up the total hourly requests to the nearest 10,000. For example, 30,100 requests in an hour are billed as 40,000 requests.
|
Region |
Cumulative hourly requests |
Unit price (CNY/hour) |
|
China (mainland) |
0 - 10,000 (inclusive) |
0.135 |
|
10,001 - 100,000 (inclusive) |
0.1 |
|
|
100,001 - 500,000 (inclusive) |
0.015 |
|
|
Over 500,000 |
0.003 |
Billing example
If your gateway request volume varies, your hourly costs will also vary. For example, assume you use a Cloud Native Gateway serverless instance for two hours, and the total number of requests is 875,000:
-
Assume the total number of requests in the first hour is 50,000.
-
For the first 10,000 requests, the price is CNY 0.135 per 10,000 requests. Cost: 1 × 0.135 = CNY 0.135.
-
For the next 40,000 requests (from 10,001 to 50,000), the price is CNY 0.1 per 10,000 requests. Cost: (5 - 1) × 0.1 = CNY 0.4.
The total cost for the first hour is the sum of these amounts: 1 × 0.135 + (5 - 1) × 0.1 = CNY 0.535.
-
-
Assume the total number of requests in the second hour is 825,000.
-
For the first 10,000 requests, the price is CNY 0.135 per 10,000 requests. Cost: 1 × 0.135 = CNY 0.135.
-
For the next 90,000 requests (from 10,001 to 100,000), the price is CNY 0.1 per 10,000 requests. Cost: (10 - 1) × 0.1 = CNY 0.9.
-
For the next 400,000 requests (from 100,001 to 500,000), the price is CNY 0.015 per 10,000 requests. Cost: (50 - 10) × 0.015 = CNY 0.6.
-
For the remaining 325,000 requests (from 500,001 to 825,000), the number of requests is rounded up to the nearest 10,000, which is 330,000. The cost is 33 × 0.003 = CNY 0.099.
The total cost for the second hour is the sum of these amounts: 1 × 0.135 + (10 - 1) × 0.1 + (50 - 10) × 0.015 + 33 × 0.003 = CNY 1.734.
-
The total cost for the two hours is CNY 2.269.
Price reference
The following table shows the hourly price and calculation method for different request volumes.
To estimate your monthly cost for a consistent request volume, use this formula: Monthly price = Hourly price × 24 × 30.
|
Total hourly requests |
Hourly price (CNY) |
Calculation |
|
10,000 |
0.135 |
1 × 0.135 |
|
50,000 |
0.535 |
1 × 0.135 + (5 - 1) × 0.1 |
|
200,000 |
1.185 |
1 × 0.135 + (10 - 1) × 0.1 + (20 - 10) × 0.015 |
|
500,000 |
1.635 |
1 × 0.135 + (10 - 1) × 0.1 + (50 - 10) × 0.015 |
|
1,000,000 |
1.785 |
1 × 0.135 + (10 - 1) × 0.1 + (50 - 10) × 0.015 + (100 - 50) × 0.003 |
Related documentation
To stop incurring charges, release your Cloud Native Gateway instance when it is no longer needed. For more information, see release resources.
Container resource monitoring quotas
After you enable Kubernetes resource monitoring, a single Cloud Native Gateway serverless instance supports the following maximum Kubernetes cluster resource quotas. If your resource count approaches or exceeds these limits, we recommend monitoring your capacity usage or submitting a ticket to request a quota increase.
|
Resource type |
Quota limit |
|
Number of domains |
250 |
|
Number of services |
500 |
|
Number of routes |
500 |
|
Number of Ingresses |
750 |
|
Number of endpoints |
1,250 |