PolarDB for MySQL edge clusters use subscription billing. Your monthly cost is:
Total cost = compute nodes + storage space + backup storage (currently free)
The three billable items are explained below, along with expiration policy and renewal options.
Billing method
Subscription is the only supported billing method for PolarDB for MySQL edge clusters. Pay upfront when you create a cluster, selecting the resources you need. Longer subscription terms get larger discounts. This model suits stable, long-term workloads.
Billable items
Compute nodes
Prices below are per single compute node per month. Multiply by your node count to get the total compute cost.
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 |
| X86 (General-purpose) | polar.mysql.g1.small.c | 1 core, 2 GB | 2.77 |
| X86 (General-purpose) | polar.mysql.g2.small.c | 2 cores, 4 GB | 34.62 |
| X86 (General-purpose) | polar.mysql.g4.medium.c | 2 cores, 8 GB | 40.00 |
| X86 (General-purpose) | polar.mysql.g8.medium.c | 2 cores, 16 GB | 67.69 |
| X86 (General-purpose) | polar.mysql.g2.large.c | 4 cores, 8 GB | 69.23 |
| X86 (General-purpose) | polar.mysql.g4.large.c | 4 cores, 16 GB | 101.54 |
| X86 (General-purpose) | polar.mysql.g8.large.c | 4 cores, 32 GB | 135.38 |
| X86 (General-purpose) | polar.mysql.g2.xlarge.c | 8 cores, 16 GB | 159.23 |
| X86 (General-purpose) | polar.mysql.g4.xlarge.c | 8 cores, 32 GB | 204.62 |
| X86 (General-purpose) | polar.mysql.g8.xlarge.c | 8 cores, 64 GB | 270.77 |
| X86 (General-purpose) | polar.mysql.g2.2xlarge.c | 16 cores, 32 GB | 318.46 |
| X86 (General-purpose) | polar.mysql.g4.2xlarge.c | 16 cores, 64 GB | 409.23 |
| X86 (General-purpose) | polar.mysql.g8.2xlarge.c | 16 cores, 128 GB | 541.54 |
| X86 (Dedicated) | polar.mysql.x4.medium.c | 2 cores, 8 GB | 41.54 |
| X86 (Dedicated) | polar.mysql.x8.medium.c | 2 cores, 16 GB | 75.38 |
| X86 (Dedicated) | polar.mysql.x2.large.c | 4 cores, 8 GB | 93.08 |
| X86 (Dedicated) | polar.mysql.x4.large.c | 4 cores, 16 GB | 117.69 |
| X86 (Dedicated) | polar.mysql.x8.large.c | 4 cores, 32 GB | 150.77 |
| X86 (Dedicated) | polar.mysql.x2.xlarge.c | 8 cores, 16 GB | 184.62 |
| X86 (Dedicated) | polar.mysql.x4.xlarge.c | 8 cores, 32 GB | 233.85 |
| X86 (Dedicated) | polar.mysql.x8.xlarge.c | 8 cores, 64 GB | 296.92 |
| X86 (Dedicated) | polar.mysql.x2.2xlarge.c | 16 cores, 32 GB | 369.23 |
| X86 (Dedicated) | polar.mysql.x4.2xlarge.c | 16 cores, 64 GB | 461.54 |
| X86 (Dedicated) | polar.mysql.x8.2xlarge.c | 16 cores, 128 GB | 584.62 |
| X86 (Dedicated) | polar.mysql.x2.4xlarge.c | 32 cores, 64 GB | 727.69 |
| X86 (Dedicated) | polar.mysql.x4.4xlarge.c | 32 cores, 128 GB | 904.62 |
| X86 (Dedicated) | polar.mysql.x8.4xlarge.c | 32 cores, 256 GB | 1,170.77 |
| X86 (Dedicated) | polar.mysql.x4.8xlarge.c | 64 cores, 256 GB | 1,784.62 |
| X86 (Dedicated) | polar.mysql.x8.8xlarge.c | 64 cores, 512 GB | 2,289.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 |
| X86 (General-purpose) | polar.mysql.g1.small.c | 1 core, 2 GB | 5.23 |
| X86 (General-purpose) | polar.mysql.g2.small.c | 2 cores, 4 GB | 65.77 |
| X86 (General-purpose) | polar.mysql.g4.medium.c | 2 cores, 8 GB | 76.00 |
| X86 (General-purpose) | polar.mysql.g8.medium.c | 2 cores, 16 GB | 128.62 |
| X86 (General-purpose) | polar.mysql.g2.large.c | 4 cores, 8 GB | 131.54 |
| X86 (General-purpose) | polar.mysql.g4.large.c | 4 cores, 16 GB | 192.92 |
| X86 (General-purpose) | polar.mysql.g8.large.c | 4 cores, 32 GB | 257.23 |
| X86 (General-purpose) | polar.mysql.g2.xlarge.c | 8 cores, 16 GB | 302.62 |
| X86 (General-purpose) | polar.mysql.g4.xlarge.c | 8 cores, 32 GB | 388.77 |
| X86 (General-purpose) | polar.mysql.g8.xlarge.c | 8 cores, 64 GB | 514.46 |
| X86 (General-purpose) | polar.mysql.g2.2xlarge.c | 16 cores, 32 GB | 605.08 |
| X86 (General-purpose) | polar.mysql.g4.2xlarge.c | 16 cores, 64 GB | 777.54 |
| X86 (General-purpose) | polar.mysql.g8.2xlarge.c | 16 cores, 128 GB | 1,028.92 |
| X86 (Dedicated) | polar.mysql.x4.medium.c | 2 cores, 8 GB | 78.92 |
| X86 (Dedicated) | polar.mysql.x8.medium.c | 2 cores, 16 GB | 143.23 |
| X86 (Dedicated) | polar.mysql.x2.large.c | 4 cores, 8 GB | 176.92 |
| X86 (Dedicated) | polar.mysql.x4.large.c | 4 cores, 16 GB | 223.69 |
| X86 (Dedicated) | polar.mysql.x8.large.c | 4 cores, 32 GB | 286.46 |
| X86 (Dedicated) | polar.mysql.x2.xlarge.c | 8 cores, 16 GB | 350.77 |
| X86 (Dedicated) | polar.mysql.x4.xlarge.c | 8 cores, 32 GB | 444.31 |
| X86 (Dedicated) | polar.mysql.x8.xlarge.c | 8 cores, 64 GB | 564.15 |
| X86 (Dedicated) | polar.mysql.x2.2xlarge.c | 16 cores, 32 GB | 701.54 |
| X86 (Dedicated) | polar.mysql.x4.2xlarge.c | 16 cores, 64 GB | 876.92 |
| X86 (Dedicated) | polar.mysql.x8.2xlarge.c | 16 cores, 128 GB | 1,110.77 |
| X86 (Dedicated) | polar.mysql.x2.4xlarge.c | 32 cores, 64 GB | 1,382.62 |
| X86 (Dedicated) | polar.mysql.x4.4xlarge.c | 32 cores, 128 GB | 1,718.77 |
| X86 (Dedicated) | polar.mysql.x8.4xlarge.c | 32 cores, 256 GB | 2,224.46 |
| X86 (Dedicated) | polar.mysql.x4.8xlarge.c | 64 cores, 256 GB | 3,390.77 |
| X86 (Dedicated) | polar.mysql.x8.8xlarge.c | 64 cores, 512 GB | 4,349.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 |
| X86 (General-purpose) | polar.mysql.g1.small.c | 1 core, 2 GB | 4.71 |
| X86 (General-purpose) | polar.mysql.g2.small.c | 2 cores, 4 GB | 58.85 |
| X86 (General-purpose) | polar.mysql.g4.medium.c | 2 cores, 8 GB | 68.00 |
| X86 (General-purpose) | polar.mysql.g8.medium.c | 2 cores, 16 GB | 115.08 |
| X86 (General-purpose) | polar.mysql.g2.large.c | 4 cores, 8 GB | 117.69 |
| X86 (General-purpose) | polar.mysql.g4.large.c | 4 cores, 16 GB | 172.62 |
| X86 (General-purpose) | polar.mysql.g8.large.c | 4 cores, 32 GB | 230.15 |
| X86 (General-purpose) | polar.mysql.g2.xlarge.c | 8 cores, 16 GB | 270.69 |
| X86 (General-purpose) | polar.mysql.g4.xlarge.c | 8 cores, 32 GB | 347.85 |
| X86 (General-purpose) | polar.mysql.g8.xlarge.c | 8 cores, 64 GB | 460.31 |
| X86 (General-purpose) | polar.mysql.g2.2xlarge.c | 16 cores, 32 GB | 541.38 |
| X86 (General-purpose) | polar.mysql.g4.2xlarge.c | 16 cores, 64 GB | 695.69 |
| X86 (General-purpose) | polar.mysql.g8.2xlarge.c | 16 cores, 128 GB | 920.62 |
| X86 (Dedicated) | polar.mysql.x4.medium.c | 2 cores, 8 GB | 70.62 |
| X86 (Dedicated) | polar.mysql.x8.medium.c | 2 cores, 16 GB | 128.15 |
| X86 (Dedicated) | polar.mysql.x2.large.c | 4 cores, 8 GB | 158.23 |
| X86 (Dedicated) | polar.mysql.x4.large.c | 4 cores, 16 GB | 200.08 |
| X86 (Dedicated) | polar.mysql.x8.large.c | 4 cores, 32 GB | 256.31 |
| X86 (Dedicated) | polar.mysql.x2.xlarge.c | 8 cores, 16 GB | 313.85 |
| X86 (Dedicated) | polar.mysql.x4.xlarge.c | 8 cores, 32 GB | 397.54 |
| X86 (Dedicated) | polar.mysql.x8.xlarge.c | 8 cores, 64 GB | 504.77 |
| X86 (Dedicated) | polar.mysql.x2.2xlarge.c | 16 cores, 32 GB | 627.69 |
| X86 (Dedicated) | polar.mysql.x4.2xlarge.c | 16 cores, 64 GB | 784.62 |
| X86 (Dedicated) | polar.mysql.x8.2xlarge.c | 16 cores, 128 GB | 993.85 |
| X86 (Dedicated) | polar.mysql.x2.4xlarge.c | 32 cores, 64 GB | 1,237.08 |
| X86 (Dedicated) | polar.mysql.x4.4xlarge.c | 32 cores, 128 GB | 1,537.85 |
| X86 (Dedicated) | polar.mysql.x8.4xlarge.c | 32 cores, 256 GB | 1,990.31 |
| X86 (Dedicated) | polar.mysql.x4.8xlarge.c | 64 cores, 256 GB | 3,033.85 |
| X86 (Dedicated) | polar.mysql.x8.8xlarge.c | 64 cores, 512 GB | 3,891.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 |
| X86 (General-purpose) | polar.mysql.g1.small.c | 1 core, 2 GB | 5.23 |
| X86 (General-purpose) | polar.mysql.g2.small.c | 2 cores, 4 GB | 65.77 |
| X86 (General-purpose) | polar.mysql.g4.medium.c | 2 cores, 8 GB | 76.00 |
| X86 (General-purpose) | polar.mysql.g8.medium.c | 2 cores, 16 GB | 128.62 |
| X86 (General-purpose) | polar.mysql.g2.large.c | 4 cores, 8 GB | 131.54 |
| X86 (General-purpose) | polar.mysql.g4.large.c | 4 cores, 16 GB | 192.92 |
| X86 (General-purpose) | polar.mysql.g8.large.c | 4 cores, 32 GB | 257.23 |
| X86 (General-purpose) | polar.mysql.g2.xlarge.c | 8 cores, 16 GB | 302.62 |
| X86 (General-purpose) | polar.mysql.g4.xlarge.c | 8 cores, 32 GB | 388.77 |
| X86 (General-purpose) | polar.mysql.g8.xlarge.c | 8 cores, 64 GB | 514.46 |
| X86 (General-purpose) | polar.mysql.g2.2xlarge.c | 16 cores, 32 GB | 605.08 |
| X86 (General-purpose) | polar.mysql.g4.2xlarge.c | 16 cores, 64 GB | 777.54 |
| X86 (General-purpose) | polar.mysql.g8.2xlarge.c | 16 cores, 128 GB | 1,028.92 |
| X86 (Dedicated) | polar.mysql.x4.medium.c | 2 cores, 8 GB | 78.92 |
| X86 (Dedicated) | polar.mysql.x8.medium.c | 2 cores, 16 GB | 143.23 |
| X86 (Dedicated) | polar.mysql.x2.large.c | 4 cores, 8 GB | 176.92 |
| X86 (Dedicated) | polar.mysql.x4.large.c | 4 cores, 16 GB | 223.69 |
| X86 (Dedicated) | polar.mysql.x8.large.c | 4 cores, 32 GB | 286.46 |
| X86 (Dedicated) | polar.mysql.x2.xlarge.c | 8 cores, 16 GB | 350.77 |
| X86 (Dedicated) | polar.mysql.x4.xlarge.c | 8 cores, 32 GB | 444.31 |
| X86 (Dedicated) | polar.mysql.x8.xlarge.c | 8 cores, 64 GB | 564.15 |
| X86 (Dedicated) | polar.mysql.x2.2xlarge.c | 16 cores, 32 GB | 701.54 |
| X86 (Dedicated) | polar.mysql.x4.2xlarge.c | 16 cores, 64 GB | 876.92 |
| X86 (Dedicated) | polar.mysql.x8.2xlarge.c | 16 cores, 128 GB | 1,110.77 |
| X86 (Dedicated) | polar.mysql.x2.4xlarge.c | 32 cores, 64 GB | 1,382.62 |
| X86 (Dedicated) | polar.mysql.x4.4xlarge.c | 32 cores, 128 GB | 1,718.77 |
| X86 (Dedicated) | polar.mysql.x8.4xlarge.c | 32 cores, 256 GB | 2,224.46 |
| X86 (Dedicated) | polar.mysql.x4.8xlarge.c | 64 cores, 256 GB | 3,390.77 |
| X86 (Dedicated) | polar.mysql.x8.8xlarge.c | 64 cores, 512 GB | 4,349.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 | ||
Prices are per GB per month. The rate depends on the storage class and deployment mode.
| Storage class | Deployment mode | Haikou Telecom (USD/GB/month) | Macao (China) 2 (USD/GB/month) | Türkiye (Istanbul) 1 (USD/GB/month) | Vietnam (Hanoi) 3 (USD/GB/month) |
|---|---|---|---|---|---|
| ESSD PL0 | Dual-zone deployment (hot standby storage cluster enabled) | 0.12 | 0.12 | 0.22 | 0.12 |
| ESSD PL0 | Dual-zone deployment (hot standby storage and compute clusters enabled) | 0.12 | 0.12 | 0.22 | 0.12 |
| ESSD PL0 | Three-zone deployment (hot standby storage cluster and logger node enabled) | 0.12 | 0.12 | 0.22 | 0.12 |
| ESSD PL0 | 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 |
| ESSD PL1 | Dual-zone deployment (hot standby storage and compute clusters enabled) | 0.25 | 0.25 | 0.43 | 0.25 |
| ESSD PL1 | Three-zone deployment (hot standby storage cluster and logger node enabled) | 0.25 | 0.25 | 0.43 | 0.25 |
| ESSD PL1 | Single zone (hot standby storage cluster disabled) | 0.15 | 0.15 | 0.27 | 0.15 |
Backup storage
Backup storage is currently free of charge.
Billing example
Suppose you run a cluster in Haikou Telecom with two compute nodes (each polar.mysql.g2.large.c, 4 cores, 8 GB), 500 GB of ESSD PL0 storage in dual-zone deployment (hot standby storage cluster enabled), and rely on the free backup tier.
| Billable item | Calculation | Monthly cost |
|---|---|---|
| Compute nodes | 2 nodes x $69.23/node | $138.46 |
| Storage space | 500 GB x $0.12/GB | $60.00 |
| Backup storage | Free | $0.00 |
| Total | $198.46 |
Expiration
When a subscription cluster expires, it is immediately shut down, locked, and inaccessible. No fees are charged during this period. Renew before expiration to avoid any service interruption.
You have 8 days from the expiration date to renew before the cluster is permanently released. Alibaba Cloud sends a reminder by text message or email one day before release.
| Time | Cluster status | Fees | Recovery |
|---|---|---|---|
| On the expiration date | Shut down, locked, inaccessible | None | Manually renew to unlock |
| 8 days after expiration (7 days after shutdown) | Cluster released | Depends on backup policy | Restore from the cluster recycle bin (if applicable) |
After the cluster is released, what happens to your data depends on your backup policy:
Retain This Backup Set For Long-term (a Full Backup Is Performed Before Release) or Retain All Backup Sets For Long-term: Data is moved to the cluster recycle bin. Storage fees apply.
Delete All Backup Sets Immediately: The cluster is permanently released. Data cannot be recovered. No fees charged.
If the released cluster is in the cluster recycle bin, you can restore it from its backup sets.
Renewal
Renew your subscription cluster before it expires to prevent service interruptions or data loss. Two options are available: auto-renewal and manual renewal.
Auto-renewal
With auto-renewal enabled, the system renews the cluster automatically based on the original subscription duration. For example, a three-month subscription renews in three-month increments each cycle.
Deduction schedule: The renewal fee is deducted at 08:00, three days before the expiration date. If the deduction fails, the system retries on:
1 day before the expiration date
The expiration date
6 days after the expiration date
14 days after the expiration date
Keep your Alibaba Cloud account balance sufficient to avoid failed deductions. If you manually renew before an auto-deduction runs, the next auto-renewal date recalculates from the new expiration date. Auto-renewal takes effect the day after you enable it.
Enable auto-renewal
Select Auto-renewal when purchasing a subscription cluster.

Go to Expenses and Costs > Renewal. On the Manual or Nonrenewal tab, find the cluster and click Renew in the Actions column.
If you cannot find the cluster on the Manual or Nonrenewal tab, auto-renewal may already be enabled. Check the Auto tab.
Change the auto-renewal cycle
Go to Expenses and Costs > Renewal. On the Auto tab, find the cluster and click Edit Auto Renewal in the Actions column.
Disable auto-renewal
Go to Expenses and Costs > Renewal. On the Auto tab, find the cluster and click Enable Manual Renewal in the Actions column.
Manual renewal
Renew manually at any time before the cluster is released:
In the PolarDB for ENS console, find the cluster and choose More > Renew in the Actions column.
Go to Expenses and Costs > Renewal. On the Manual, Auto, or Nonrenewal tab, find the cluster and click Renew in the Actions column.