Subscription is a prepaid billing method suited for workloads with stable, predictable resource requirements. You pay upfront for a fixed term and use Hologres for that duration. The plan supports both upgrades and downgrades, so you can adjust capacity as your needs change.
Subscription fees cover compute and storage resources only. Advanced features — Serverless Computing, backup and recovery, and cross-region snapshot replication — are always billed on a pay-as-you-go basis, regardless of your subscription plan.
Billing rules
Subscription fee = (Compute resources × Unit price × Number of months) + (Storage × Unit price × Number of months)
For billing calculations, one month equals 30 days.
Example: 128 CUs of compute and 500 GB of storage for 6 months in Singapore: 128 × 31.970149 × 6 + 500 × 0.182090 × 6 = USD 25,099.344432
The following table lists unit prices by resource type and region.
| Resource type | Specification | Region | Unit price |
|---|---|---|---|
| Compute (General-purpose, read-only secondary instances) | Per CU/month (1 CU = 1 core 4 GB) | Singapore | USD 31.970149 |
| China (Hong Kong) | USD 30.194030 | ||
| US (Silicon Valley) | USD 29.432836 | ||
| US (Virginia) | USD 27.149254 | ||
| Malaysia (Kuala Lumpur) | USD 35.268657 | ||
| Japan (Tokyo) | USD 30.194030 | ||
| Indonesia (Jakarta) | USD 31.462687 | ||
| China (Hangzhou) | USD 25.373134 | ||
| China (Shanghai) | USD 25.373134 | ||
| China (Beijing) | USD 25.373134 | ||
| China (Shenzhen) | USD 25.373134 | ||
| China (Ulanqab) | USD 25.373134 | ||
| China (Zhangjiakou) | USD 25.567164 | ||
| Germany (Frankfurt) | USD 32.731343 | ||
| Reserved compute (compute group-based) | Per CU/month | Singapore | USD 31.970149 |
| China (Hong Kong) | USD 30.194030 | ||
| US (Silicon Valley) | USD 29.432836 | ||
| US (Virginia) | USD 27.149254 | ||
| Malaysia (Kuala Lumpur) | USD 35.268657 | ||
| Japan (Tokyo) | USD 30.194030 | ||
| Indonesia (Jakarta) | USD 31.462687 | ||
| China (Hangzhou) | USD 25.373134 | ||
| China (Shanghai) | USD 25.373134 | ||
| China (Beijing) | USD 25.373134 | ||
| China (Shenzhen) | USD 25.373134 | ||
| China (Ulanqab) | USD 25.373134 | ||
| China (Zhangjiakou) | USD 25.567164 | ||
| Germany (Frankfurt) | USD 32.731343 | ||
| Elastic compute (compute group instance, including scheduled and automatic elasticity) | Per CU/hour | Singapore | USD 0.066604 |
| China (Hong Kong) | USD 0.062904 | ||
| US (Silicon Valley) | USD 0.061318 | ||
| US (Virginia) | USD 0.056561 | ||
| Malaysia (Kuala Lumpur) | USD 0.073476 | ||
| Japan (Tokyo) | USD 0.062904 | ||
| Indonesia (Jakarta) | USD 0.065547 | ||
| China (Hangzhou) | USD 0.052861 | ||
| China (Shanghai) | USD 0.052861 | ||
| China (Beijing) | USD 0.052861 | ||
| China (Shenzhen) | USD 0.052861 | ||
| China (Ulanqab) | USD 0.052861 | ||
| China (Zhangjiakou) | USD 0.044932 | ||
| Germany (Frankfurt) | USD 0.068190 | ||
| Gateway resources (compute group-based) | Per node/month | Singapore | USD 63.940298 |
| China (Hong Kong) | USD 60.388060 | ||
| US (Silicon Valley) | USD 58.865672 | ||
| US (Virginia) | USD 54.298508 | ||
| Malaysia (Kuala Lumpur) | USD 70.537314 | ||
| Japan (Tokyo) | USD 60.388060 | ||
| Indonesia (Jakarta) | USD 62.925374 | ||
| China (Hangzhou) | USD 50.746268 | ||
| China (Shanghai) | USD 50.746268 | ||
| China (Beijing) | USD 50.746268 | ||
| China (Shenzhen) | USD 50.746268 | ||
| China (Ulanqab) | USD 50.746268 | ||
| China (Zhangjiakou) | USD 43.134328 | ||
| Germany (Frankfurt) | USD 65.462686 | ||
| Serverless Computing (General-purpose, compute group-based) | Per CU/hour, pay-as-you-go | China (Hangzhou) | USD 0.052866 |
| China (Shanghai) | USD 0.052866 | ||
| China (Beijing) | USD 0.052866 | ||
| China (Shenzhen) | USD 0.052866 | ||
| China (Ulanqab) | USD 0.052866 | ||
| China (Hong Kong) | USD 0.062904 | ||
| Singapore | USD 0.066604 | ||
| Indonesia (Jakarta) | USD 0.065547 | ||
| US (Virginia) | USD 0.056561 | ||
| Germany (Frankfurt) | USD 0.068190 | ||
| Standard storage (locally redundant storage) | Per GB/month | Singapore | USD 0.182090 |
| China (Hong Kong) | USD 0.174627 | ||
| US (Silicon Valley) | USD 0.171642 | ||
| US (Virginia) | USD 0.164179 | ||
| Malaysia (Kuala Lumpur) | USD 0.197015 | ||
| Japan (Tokyo) | USD 0.177612 | ||
| Indonesia (Jakarta) | USD 0.183582 | ||
| China (Hangzhou) | USD 0.149254 | ||
| China (Shanghai) | USD 0.149254 | ||
| China (Beijing) | USD 0.149254 | ||
| China (Shenzhen) | USD 0.149254 | ||
| China (Ulanqab) | USD 0.149254 | ||
| China (Zhangjiakou) | USD 0.126866 | ||
| Germany (Frankfurt) | USD 0.189552 | ||
| Standard storage (zone-redundant storage) | Per GB/month | China (Shenzhen) | USD 0.194030 |
| China (Beijing) | USD 0.194030 | ||
| China (Shanghai) | USD 0.027941 | ||
| China (Hong Kong) | USD 0.261941 | ||
| Singapore | USD 0.273135 | ||
| Infrequent Access storage (locally redundant storage) | Per GB/month | Singapore | USD 0.026221 |
| China (Hong Kong) | USD 0.025146 | ||
| US (Silicon Valley) | USD 0.024716 | ||
| US (Virginia) | USD 0.023642 | ||
| Malaysia (Kuala Lumpur) | USD 0.028370 | ||
| Japan (Tokyo) | USD 0.025576 | ||
| Indonesia (Jakarta) | USD 0.026436 | ||
| China (Hangzhou) | USD 0.021493 | ||
| China (Shanghai) | USD 0.021493 | ||
| China (Beijing) | USD 0.021493 | ||
| China (Shenzhen) | USD 0.021493 | ||
| China (Ulanqab) | USD 0.021493 | ||
| China (Zhangjiakou) | USD 0.018269 | ||
| Germany (Frankfurt) | USD 0.027296 | ||
| Infrequent Access storage (zone-redundant storage) | Per GB/month | China (Shenzhen) | USD 0.027941 |
| China (Beijing) | USD 0.027941 | ||
| China (Shanghai) | USD 0.027941 | ||
| China (Hong Kong) | USD 0.037719 | ||
| Singapore | USD 0.039332 | ||
| Backup set storage | Per GB/hour, pay-as-you-go | Singapore | USD 0.000055 |
| China (Hong Kong) | USD 0.000052 | ||
| US (Silicon Valley) | USD 0.000051 | ||
| US (Virginia) | USD 0.000049 | ||
| Malaysia (Kuala Lumpur) | USD 0.000059 | ||
| Japan (Tokyo) | USD 0.000053 | ||
| Indonesia (Jakarta) | USD 0.000055 | ||
| China (Hangzhou) | USD 0.000045 | ||
| China (Shanghai) | USD 0.000045 | ||
| China (Beijing) | USD 0.000045 | ||
| China (Shenzhen) | USD 0.000045 | ||
| China (Ulanqab) | USD 0.000045 | ||
| China (Zhangjiakou) | USD 0.000038 | ||
| Germany (Frankfurt) | USD 0.000057 | ||
| Network traffic (cross-region snapshot replication) | Per GB, pay-as-you-go | China (Hangzhou) | USD 0.0746 |
| China (Shanghai) | USD 0.0746 | ||
| China (Beijing) | USD 0.0746 | ||
| China (Shenzhen) | USD 0.0746 | ||
| China (Ulanqab) | USD 0.0746 | ||
| China (Hong Kong) | USD 0.08 | ||
| Singapore | USD 0.08 | ||
| Malaysia (Kuala Lumpur) | USD 0.08 |
Backup set storage and network traffic for cross-region snapshot replication are always billed on a pay-as-you-go basis. Backup set storage volume fluctuates based on the backup policy and the amount of differential data.
Lifecycle management
The following diagram shows the lifecycle of a subscription Hologres instance.
Instance expiration
When a subscription expires, Hologres immediately stops all services. To continue using the instance, renew it within 14 days. If you do not renew within this grace period, the instance is released — deleted from the console with all data permanently unrecoverable. No charges apply during the 14-day grace period.
If you request to unsubscribe, the instance is released immediately after the request is approved.
Overdue payment
If your Alibaba Cloud account has an overdue payment, the instance remains usable for 24 hours. If you pay within that window, service continues uninterrupted. If you do not pay within 24 hours, the instance is locked and inaccessible until the subscription term ends.
After the subscription expires:
-
If you settle the overdue payment within 14 days, service resumes.
-
If you do not pay within 14 days, the instance is released.
After the instance is released, business data is permanently deleted within 15 days and cannot be recovered.
Billing method conversion
You can change the billing method from pay-as-you-go to subscription. Changing from subscription to pay-as-you-go is not supported.
Upgrade
When your current configuration no longer meets your needs, upgrade to a larger configuration. The upgrade fee equals the cost of the new configuration for the remaining term minus the unused value of your original subscription.
Formulas:
| Variable | Formula |
|---|---|
| Paid amount (original) | Compute capacity × Months × Unit price + Storage capacity × Months × Unit price |
| Used amount (original) | Paid amount / Total purchased hours × Hours used |
| Remaining amount (original) | Paid amount - Used amount |
| Total payable (new) | Compute resources × Months × Unit price + Storage × Months × Unit price |
| Actual payable (new) | Total payable / Total purchased hours × Actual hours of use |
| Upgrade fee | Actual payable (new) - Remaining amount (original) |
Example:
On March 1, you purchase a 2-month subscription in Singapore: 64 CUs of compute and 300 GB of storage (expires April 30). On March 13, you upgrade to 128 CUs and 500 GB. The expiration date stays the same.
| Step | Calculation | Result |
|---|---|---|
| Paid amount (original) | 64 × 2 × 31.970149 + 300 × 2 × 0.182090 | USD 4,201.433072 |
| Total purchased hours | 2 months × 30 days × 24 hours | 1,440 hours |
| Hours used (March 1–13, 12 days) | 12 × 24 | 288 hours |
| Used amount | 4,201.433072 / 1,440 × 288 | USD 840.2866144 |
| Remaining amount | 4,201.433072 - 840.2866144 | USD 3,361.1464576 |
| Total payable (new) | 128 × 2 × 31.970149 + 500 × 2 × 0.182090 | USD 8,366.448144 |
| Actual hours of use (new, March 13–April 30, 48 days) | 48 × 24 | 1,152 hours |
| Actual payable (new) | 8,366.448144 / 1,440 × 1,152 | USD 6,693.1585152 |
| Upgrade fee | 6,693.1585152 - 3,361.1464576 | USD 3,332.0120576 |
This example illustrates the billing logic. The actual fee is subject to the bill.
Downgrade
When your instance is over-provisioned, downgrade to a smaller configuration to reduce costs. If the actual payable amount for the new configuration is less than the remaining value of your original subscription, the system refunds the difference.
Formulas:
| Variable | Formula |
|---|---|
| Paid amount (original) | Compute capacity × Months × Unit price + Storage capacity × Months × Unit price |
| Used amount (original) | Paid amount / Total purchased hours × Hours used |
| Remaining amount (original) | Paid amount - Used amount |
| Total payable (new) | Compute resources × Months × Unit price + Storage × Months × Unit price |
| Actual payable (new) | Total payable / Total purchased hours × Actual hours of use |
| Downgrade fee | Actual payable (new) - Remaining amount (original) |
A negative result means the system refunds the difference to your account.
Example:
On March 1, you purchase a 3-month subscription in Singapore: 128 CUs of compute and 500 GB of storage (expires May 31). On March 21, you downgrade to 64 CUs and 300 GB. The expiration date stays the same.
| Step | Calculation | Result |
|---|---|---|
| Paid amount (original) | 128 × 3 × 31.970149 + 500 × 3 × 0.182090 | USD 12,549.672216 |
| Total purchased hours | 3 months × 30 days × 24 hours | 2,160 hours |
| Hours used (March 1–21, 20 days) | 20 × 24 | 480 hours |
| Used amount | 12,549.672216 / 2,160 × 480 | USD 2,788.816 |
| Remaining amount | 12,549.672216 - 2,788.816 | USD 9,760.856216 |
| Total payable (new) | 64 × 3 × 31.970149 + 300 × 3 × 0.182090 | USD 6,302.149608 |
| Actual hours of use (new, March 21–May 31, 70 days) | 70 × 24 | 1,680 hours |
| Actual payable (new) | 6,302.149608 / 2,160 × 1,680 | USD 4,901.67192 |
| Downgrade fee | 4,901.67192 - 9,760.856216 | -USD 4,859.1843 |
| Refund | USD 4,859.1843 |
This example illustrates the billing logic. The actual fee is subject to the bill.
Notification mechanism
Hologres sends expiration and release reminders by text message, phone call, or email.
| Event | Reminder timing |
|---|---|
| Expiration reminders | 7 days, 3 days, and 1 day before expiration |
| Instance stop | Immediately upon expiration |
| Release reminders | 7 days, 3 days, and 1 day before release |
Example: For a 2-month subscription, you receive expiration reminders at 7, 3, and 1 day before the term ends. The instance stops immediately on the expiration date. If you do not renew, the system sends release reminders at 7, 3, and 1 day before the 14-day grace period ends, after which the instance is released.