Note:
Currently, Cloud Native Gateway supports allowlist-based new purchases only for microservices scenarios, that is, as the access layer for Polaris (North Star) services. New access is not supported in other scenarios. If you access the console in a scenario other than the above, you will be redirected to the Polaris (North Star) console. If you have a new purchase requirement, submit a ticket. This section primarily introduces the product editions and billing models of Cloud Native Gateway.
Product Edition
Editions are divided into Pro and Standard. The comparison between the two editions is as follows:
|
Scenario | Production environments | Production environments |
Node Specifications | Selectable node specifications | Selectable node specifications |
Node Count | Selectable node quantity | Selectable node quantity |
Instance type | Dedicated instance | Dedicated instance |
High availability | Multi-node DR | Multi-node DR |
Custom plugins | Supported | Supported |
Allows you to query logs. | Supported | Supported |
Monitoring and alarms | Supported | Supported |
Parameter configuration | Supported | Supported |
Node quantity change | Supported | Supported |
Kong Ingress Controller | Supported | Supported |
Cluster and group management | Supported | Supported |
Automatic node scaling | Supported | Not supported. |
CLS dashboard | Supported | Not supported. |
Billing Mode
Engine Instance Fees
Pay-as-you-go (postpaid) and yearly/monthly subscription (prepaid) are supported.
Pay-as-you-go: You can activate or terminate instances at any time and pay for the actual usage duration. The billing time is accurate to the hour. You do not need to pay for fees in advance, and the fees are settled every day, effectively preventing resource waste.
Yearly/monthly subscription: Fees are paid when an instance is created. This billing mode applies to long-term stable business scenarios and has lower fees than the pay-as-you-go mode.
The billing items of an engine instance include the engine node specification (CPU and memory) and the node quantity.
Pay-As-You-Go (Postpaid)
In postpaid mode, select the engine specification and the node quantity as required. Billing is performed by hour. When the usage duration is less than 1 hour, it is counted as 1 hour. Fees are settled every hour, and bills are issued every 24 hours. The fees are automatically deducted from the balance in your Tencent Cloud account.
Attention:
The pricing for the following engine specifications targets a single node. If multiple engine nodes are configured, multiply the fees by the appropriate multiple.
Billing formula: Engine instance fees = Unit price of the engine specification x Node quantity x Number of hours
Billing example: If you select a Standard edition engine with a 2-core 4GB specification, set the node quantity to 3, and run the instance for 2 hours, the total fee is 0.2 x 3 x 2 = USD 1.2.
After you purchase a pay-as-you-go instance, the system allocates related instance resources. Regardless of whether you use the instance and related resources, fees are settled by hour. If the instance is no longer required, release it to prevent fees from being generated continuously.
|
Standard Edition | 1-core 2 GB | 0.18 |
Standard Edition | 2-core 4 GB | 0.2 |
Standard Edition | 4-core 4 GB | 0.33 |
Standard Edition | 4-core 8 GB | 0.4 |
Standard Edition | 8-core 16 GB | 0.8 |
Standard Edition | 16-core 32 GB | 1.6 |
|
Pro Edition | 1-core 2 GB | 0.23 |
Pro Edition | 2-core 4 GB | 0.28 |
Pro Edition | 4-core 4 GB | 0.42 |
Pro Edition | 4-core 8 GB | 0.53 |
Pro Edition | 8-core 16 GB | 1.05 |
Pro Edition | 16-core 32 GB | 2.08 |
Yearly/Monthly Subscription (Prepaid)
In yearly/monthly subscription (prepaid) mode, select the engine specification and the node quantity as required. Billing is performed by month, and fees are automatically deducted from the balance in your Tencent Cloud account.
Note:
The pricing for the following engine specifications targets a single node. If multiple engine nodes are configured, multiply the fees by the appropriate multiple.
Billing formula: Engine instance fees = Unit price of the engine specification x Node quantity x Number of months
Billing example: If you select a Standard edition engine with a 2-core 4GB specification, set the node quantity to 3, and run the instance for 1 month, the total fee is 104.5 x 3 x 1 = USD 313.5.
|
Standard Edition | 1-core 2 GB | 91.75 |
Standard Edition | 2-core 4 GB | 104.5 |
Standard Edition | 4-core 4 GB | 167.75 |
Standard Edition | 4-core 8 GB | 209 |
Standard Edition | 8-core 16 GB | 418 |
Standard Edition | 16-core 32 GB | 836 |
|
Pro Edition | 1-core 2 GB | 119.28 |
Pro Edition | 2-core 4 GB | 135.75 |
Pro Edition | 4-core 4 GB | 218 |
Pro Edition | 4-core 8 GB | 271.75 |
Pro Edition | 8-core 16 GB | 543.25 |
Pro Edition | 16-core 32 GB | 1,086.8 |
Public Network Traffic Fees
Public network traffic fees can be billed in two modes: By Traffic Usage and By Hourly Bandwidth.
By Traffic Usage
By Traffic Usage mainly covers the downstream traffic, that is, the public network outbound traffic from the gateway to the client. The payment mode is postpaid, and fees are settled by hour.
Billing price
|
Singapore | 0.081 |
Jakarta, Seoul, Hong Kong (China) | 0.12 |
By Hourly Bandwidth
Billing price
Billing example: If you select the By Hourly Bandwidth billing mode and purchase a fixed bandwidth of 6 Mbps, the total fee is calculated as: 5 Mbps x USD 0.0064/Mbps/hour + (6 Mbps - 5 Mbps) x USD 0.0232/Mbps/hour = USD 0.0552/hour.
Supported Regions
The following table lists the regions supported by Cloud Native Gateway:
|
Asia Pacific (Hong Kong (China)) | ap-hongkong |
Asia Pacific (Singapore) | ap-singapore |
Asia Pacific (Seoul) | ap-seoul |
Asia Pacific (Jakarta) | ap-jakarta |