All Products
Search
Document Center

PolarDB:Billing

Last Updated:Dec 09, 2025

This topic describes the billing methods, billable items, expiration, and renewal for PolarDB for MySQL edge clusters.

Billing method

PolarDB for MySQL edge clusters currently support only the subscription billing method.

Subscription: This is an upfront payment model. You select and pay in advance for resources with defined specifications when you create a cluster. The longer the subscription duration, the greater the discount. This model is suitable for scenarios with stable, long-term business needs.

Billable items

The billable items for PolarDB for MySQL edge clusters include compute nodes, storage space, and backup storage.

Compute nodes

The following tables show the pricing for a single compute node.

Haikou Telecom

CPU architecture

Specification code

CPU and memory

Price (USD/month)

X86 (General-purpose)

polar.mysql.g1.tiny.c

1 core, 1 GB

1.69

polar.mysql.g1.small.c

1 core, 2 GB

2.77

polar.mysql.g2.small.c

2 cores, 4 GB

34.62

polar.mysql.g4.medium.c

2 cores, 8 GB

40

polar.mysql.g8.medium.c

2 cores, 16 GB

67.69

polar.mysql.g2.large.c

4 cores, 8 GB

69.23

polar.mysql.g4.large.c

4 cores, 16 GB

101.54

polar.mysql.g8.large.c

4 cores, 32 GB

135.38

polar.mysql.g2.xlarge.c

8 cores, 16 GB

159.23

polar.mysql.g4.xlarge.c

8 cores, 32 GB

204.62

polar.mysql.g8.xlarge.c

8 cores, 64 GB

270.77

polar.mysql.g2.2xlarge.c

16 cores, 32 GB

318.46

polar.mysql.g4.2xlarge.c

16 cores, 64 GB

409.23

polar.mysql.g8.2xlarge.c

16 cores, 128 GB

541.54

X86 (Dedicated)

polar.mysql.x4.medium.c

2 cores, 8 GB

41.54

polar.mysql.x8.medium.c

2 cores, 16 GB

75.38

polar.mysql.x2.large.c

4 cores, 8 GB

93.08

polar.mysql.x4.large.c

4 cores, 16 GB

117.69

polar.mysql.x8.large.c

4 cores, 32 GB

150.77

polar.mysql.x2.xlarge.c

8 cores, 16 GB

184.62

polar.mysql.x4.xlarge.c

8 cores, 32 GB

233.85

polar.mysql.x8.xlarge.c

8 cores, 64 GB

296.92

polar.mysql.x2.2xlarge.c

16 cores, 32 GB

369.23

polar.mysql.x4.2xlarge.c

16 cores, 64 GB

461.54

polar.mysql.x8.2xlarge.c

16 cores, 128 GB

584.62

polar.mysql.x2.4xlarge.c

32 cores, 64 GB

727.69

polar.mysql.x4.4xlarge.c

32 cores, 128 GB

904.62

polar.mysql.x8.4xlarge.c

32 cores, 256 GB

1170.77

polar.mysql.x4.8xlarge.c

64 cores, 256 GB

1784.62

polar.mysql.x8.8xlarge.c

64 cores, 512 GB

2289.23

Macao (China) 2

CPU architecture

Specification code

CPU and memory

Price (USD/month)

X86 (General-purpose)

polar.mysql.g1.tiny.c

1 core, 1 GB

2.77

polar.mysql.g1.small.c

1 core, 2 GB

5.23

polar.mysql.g2.small.c

2 cores, 4 GB

65.77

polar.mysql.g4.medium.c

2 cores, 8 GB

76

polar.mysql.g8.medium.c

2 cores, 16 GB

128.62

polar.mysql.g2.large.c

4 cores, 8 GB

131.54

polar.mysql.g4.large.c

4 cores, 16 GB

192.92

polar.mysql.g8.large.c

4 cores, 32 GB

257.23

polar.mysql.g2.xlarge.c

8 cores, 16 GB

302.62

polar.mysql.g4.xlarge.c

8 cores, 32 GB

388.77

polar.mysql.g8.xlarge.c

8 cores, 64 GB

514.46

polar.mysql.g2.2xlarge.c

16 cores, 32 GB

605.08

polar.mysql.g4.2xlarge.c

16 cores, 64 GB

777.54

polar.mysql.g8.2xlarge.c

16 cores, 128 GB

1028.92

X86 (Dedicated)

polar.mysql.x4.medium.c

2 cores, 8 GB

78.92

polar.mysql.x8.medium.c

2 cores, 16 GB

143.23

polar.mysql.x2.large.c

4 cores, 8 GB

176.92

polar.mysql.x4.large.c

4 cores, 16 GB

223.69

polar.mysql.x8.large.c

4 cores, 32 GB

286.46

polar.mysql.x2.xlarge.c

8 cores, 16 GB

350.77

polar.mysql.x4.xlarge.c

8 cores, 32 GB

444.31

polar.mysql.x8.xlarge.c

8 cores, 64 GB

564.15

polar.mysql.x2.2xlarge.c

16 cores, 32 GB

701.54

polar.mysql.x4.2xlarge.c

16 cores, 64 GB

876.92

polar.mysql.x8.2xlarge.c

16 cores, 128 GB

1110.77

polar.mysql.x2.4xlarge.c

32 cores, 64 GB

1382.62

polar.mysql.x4.4xlarge.c

32 cores, 128 GB

1718.77

polar.mysql.x8.4xlarge.c

32 cores, 256 GB

2224.46

polar.mysql.x4.8xlarge.c

64 cores, 256 GB

3390.77

polar.mysql.x8.8xlarge.c

64 cores, 512 GB

4349.54

Türkiye (Istanbul) 1

CPU architecture

Specification code

CPU and memory

Price (USD/month)

X86 (General-purpose)

polar.mysql.g1.tiny.c

1 core, 1 GB

2.88

polar.mysql.g1.small.c

1 core, 2 GB

4.71

polar.mysql.g2.small.c

2 cores, 4 GB

58.85

polar.mysql.g4.medium.c

2 cores, 8 GB

68

polar.mysql.g8.medium.c

2 cores, 16 GB

115.08

polar.mysql.g2.large.c

4 cores, 8 GB

117.69

polar.mysql.g4.large.c

4 cores, 16 GB

172.62

polar.mysql.g8.large.c

4 cores, 32 GB

230.15

polar.mysql.g2.xlarge.c

8 cores, 16 GB

270.69

polar.mysql.g4.xlarge.c

8 cores, 32 GB

347.85

polar.mysql.g8.xlarge.c

8 cores, 64 GB

460.31

polar.mysql.g2.2xlarge.c

16 cores, 32 GB

541.38

polar.mysql.g4.2xlarge.c

16 cores, 64 GB

695.69

polar.mysql.g8.2xlarge.c

16 cores, 128 GB

920.62

X86 (Dedicated)

polar.mysql.x4.medium.c

2 cores, 8 GB

70.62

polar.mysql.x8.medium.c

2 cores, 16 GB

128.15

polar.mysql.x2.large.c

4 cores, 8 GB

158.23

polar.mysql.x4.large.c

4 cores, 16 GB

200.08

polar.mysql.x8.large.c

4 cores, 32 GB

256.31

polar.mysql.x2.xlarge.c

8 cores, 16 GB

313.85

polar.mysql.x4.xlarge.c

8 cores, 32 GB

397.54

polar.mysql.x8.xlarge.c

8 cores, 64 GB

504.77

polar.mysql.x2.2xlarge.c

16 cores, 32 GB

627.69

polar.mysql.x4.2xlarge.c

16 cores, 64 GB

784.62

polar.mysql.x8.2xlarge.c

16 cores, 128 GB

993.85

polar.mysql.x2.4xlarge.c

32 cores, 64 GB

1237.08

polar.mysql.x4.4xlarge.c

32 cores, 128 GB

1537.85

polar.mysql.x8.4xlarge.c

32 cores, 256 GB

1990.31

polar.mysql.x4.8xlarge.c

64 cores, 256 GB

3033.85

polar.mysql.x8.8xlarge.c

64 cores, 512 GB

3891.69

Vietnam (Hanoi) 3

CPU architecture

Specification code

CPU and memory

Price (USD/month)

X86 (General-purpose)

polar.mysql.g1.tiny.c

1 core, 1 GB

2.77

polar.mysql.g1.small.c

1 core, 2 GB

5.23

polar.mysql.g2.small.c

2 cores, 4 GB

65.77

polar.mysql.g4.medium.c

2 cores, 8 GB

76

polar.mysql.g8.medium.c

2 cores, 16 GB

128.62

polar.mysql.g2.large.c

4 cores, 8 GB

131.54

polar.mysql.g4.large.c

4 cores, 16 GB

192.92

polar.mysql.g8.large.c

4 cores, 32 GB

257.23

polar.mysql.g2.xlarge.c

8 cores, 16 GB

302.62

polar.mysql.g4.xlarge.c

8 cores, 32 GB

388.77

polar.mysql.g8.xlarge.c

8 cores, 64 GB

514.46

polar.mysql.g2.2xlarge.c

16 cores, 32 GB

605.08

polar.mysql.g4.2xlarge.c

16 cores, 64 GB

777.54

polar.mysql.g8.2xlarge.c

16 cores, 128 GB

1028.92

X86 (Dedicated)

polar.mysql.x4.medium.c

2 cores, 8 GB

78.92

polar.mysql.x8.medium.c

2 cores, 16 GB

143.23

polar.mysql.x2.large.c

4 cores, 8 GB

176.92

polar.mysql.x4.large.c

4 cores, 16 GB

223.69

polar.mysql.x8.large.c

4 cores, 32 GB

286.46

polar.mysql.x2.xlarge.c

8 cores, 16 GB

350.77

polar.mysql.x4.xlarge.c

8 cores, 32 GB

444.31

polar.mysql.x8.xlarge.c

8 cores, 64 GB

564.15

polar.mysql.x2.2xlarge.c

16 cores, 32 GB

701.54

polar.mysql.x4.2xlarge.c

16 cores, 64 GB

876.92

polar.mysql.x8.2xlarge.c

16 cores, 128 GB

1110.77

polar.mysql.x2.4xlarge.c

32 cores, 64 GB

1382.62

polar.mysql.x4.4xlarge.c

32 cores, 128 GB

1718.77

polar.mysql.x8.4xlarge.c

32 cores, 256 GB

2224.46

polar.mysql.x4.8xlarge.c

64 cores, 256 GB

3390.77

polar.mysql.x8.8xlarge.c

64 cores, 512 GB

4349.54

Storage space

Storage class

Price (USD/GB/month)

Haikou Telecom

Macao (China) 2

Türkiye (Istanbul) 1

Vietnam (Hanoi) 3

ESSD PL0

Dual-zone deployment (hot standby storage cluster enabled)

0.12

0.12

0.22

0.12

Dual-zone deployment (hot standby storage and compute clusters enabled)

Three-zone deployment (hot standby storage cluster and logger node enabled)

Single zone (hot standby storage cluster disabled)

0.08

0.08

0.13

0.08

ESSD PL1

Dual-zone deployment (hot standby storage cluster enabled)

0.25

0.25

0.43

0.25

Dual-zone deployment (hot standby storage and compute clusters enabled)

Three-zone deployment (hot standby storage cluster and logger node enabled)

Single zone (hot standby storage cluster disabled)

0.15

0.15

0.27

0.15

Backup storage

Backup storage for PolarDB for MySQL edge clusters is currently free of charge.

Expiration

To avoid service interruptions, manually renew your PolarDB for MySQL edge cluster or enable auto-renewal before it expires.

Time

Cluster status

Billing details

How to recover the cluster

On the expiration date

The cluster is shut down, locked, and inaccessible.

Compute nodes, storage space, and backup storage: No fees are charged.

To unlock the cluster, manually renew it.

8 days after expiration (7 days after shutdown)

The cluster is released.

Note

Alibaba Cloud sends you a reminder by text message or email one day before the cluster is released.

After the cluster is released, the data retention policy is as follows:

  • If your cluster's backup policy is set to Retain This Backup Set For Long-term (a Full Backup Is Performed Before Release) or Retain All Backup Sets For Long-term, the data is moved to the cluster recycle bin and you are charged accordingly.

  • If your cluster's backup policy is set to Delete All Backup Sets Immediately, the cluster is permanently released. The data is not retained and cannot be recovered. No fees are charged.

If a released cluster is in the cluster recycle bin, you can restore the cluster from its backup sets.

Renewal

Subscription clusters have an expiration date. If you do not renew a cluster before it expires, you may experience service interruptions or data loss. To continue using the cluster, you must renew it before it expires.

Notes

Type

Description

Auto-renewal

  • After you enable auto-renewal for a cluster, the system automatically renews the cluster based on the subscription duration. For example, if the subscription duration of your cluster is three months and auto-renewal is enabled, you are charged for a three-month subscription each time the subscription is automatically renewed.

  • The renewal fee is deducted at 08:00 three days before the expiration date of the cluster. If the deduction fails, the system attempts to deduct the renewal fee one day before the expiration date, on the expiration date, six days after the expiration date, and 14 days after the expiration date. Make sure that the balance of your Alibaba Cloud account is sufficient.

  • If you manually renew your cluster before the renewal fee is automatically deducted, the system calculates the next auto-renewal date based on the new expiration date.

  • Auto-renewal takes effect the next day after you enable it.

Manual renewal

  • Before a cluster expires, you can manually renew it to ensure service continuity.

  • If you want to use a cluster that has expired, you can manually renew it before it is released.

Auto-renewal

Enable auto-renewal

  • Select Auto-renewal when you purchase a subscription cluster.

    image

  • Go to the Expenses and Costs > Renewal page. On the Manual or Nonrenewal tab, find the cluster for which you want to enable auto-renewal and click Renew in the Actions column.

    Note

    If you cannot find the cluster, auto-renewal may already be enabled for the cluster. Check whether the cluster is on the Auto tab.

Change the auto-renewal cycle

Go to the Expenses and Costs > Renewal page. On the Auto tab, find the cluster that you want to manage and click Edit Auto Renewal in the Actions column.

Disable auto-renewal

Go to the Expenses and Costs > Renewal page. On the Auto tab, find the cluster that you want to manage and click Enable Manual Renewal in the Actions column.

Manual renewal

  • Go to the PolarDB for ENS console. Find the target cluster and in the Actions column, choose More > Renew.

  • You can go to the Expenses and Costs > Renewal page. On the Manual, Auto, or Nonrenewal tab, find the cluster that you want to renew and click Renew in the Actions column.