Hologres supports two billing methods: Pay-as-you-go and Subscription. This document describes the Pay-as-you-go method, which charges you only for the compute and storage resources you actually use, billed hourly with no upfront commitment.
Billing model
Pay-as-you-go bills are generated and settled every hour. After each billing cycle, the system automatically deducts the fee from your Alibaba Cloud account balance.
Billable items are divided into three categories:
|
Category |
Billable item |
Unit |
Notes |
|
Compute |
Compute resources |
USD/CU/hour |
1 CU = 1 core and 4 GB memory. Billed while instance is active. No charge while manually paused or suspended. |
|
Storage |
Standard storage (LRS/ZRS) |
USD/GB/hour |
Billed on actual data volume. Charges continue while instance is manually paused. |
|
Infrequent Access storage (LRS/ZRS) |
USD/GB/hour |
Lower-cost tier for data accessed infrequently. |
|
|
Backup snapshot storage |
USD/GB/hour |
Billed separately. Stop periodic backups and delete snapshots to avoid this charge. |
|
|
Network |
Cross-region snapshot replication traffic |
USD/GB |
Applies only when cross-region snapshot replication is enabled. |
Instance lifecycle
A Pay-as-you-go instance moves through four states:
|
State |
How it is entered |
Compute charges |
Storage charges |
How to exit |
|
Active |
Instance activated |
Yes |
Yes |
Manually pause, or overdue balance triggers suspension |
|
Manually paused |
User pauses instance in console |
No |
Yes |
User resumes instance |
|
Suspended (overdue) |
Overdue balance reaches 1,000 USD and automatic deduction fails for 15 days |
No |
No |
Pay the overdue balance |
|
Released |
No payment received within 14 days of suspension |
— |
— |
Cannot exit; all data is permanently deleted |
When your overdue balance reaches 1,000 USD and the system cannot collect payment, your instance is suspended on day 15. If the balance remains unpaid for 14 days after suspension, the instance is automatically released and all data is permanently deleted and unrecoverable. Keep your account balance positive to avoid service interruption.
Manual pause and resume
You can pause a Pay-as-you-go instance at any time from the Hologres console. While paused:
-
Compute charges stop immediately.
-
Storage charges continue, because your data remains in the instance.
To resume, click Resume in the console. The system requests compute resources from the availability zone. If resources are temporarily unavailable, an inventory shortage error is returned — submit a ticket to resolve this.
-
When you manually resume an instance, the system must request compute resources again. If the compute resources in the current zone are out of stock, an "inventory shortage" error occurs. To resolve this issue, you can submit a ticket.
-
Hologres supports switching between the Pay-as-you-go and Subscription billing methods.
Pricing
The fees for the Pay-as-you-go billing method for Hologres are calculated as follows:
Compute pricing
Compute resources are billed hourly based on the number of CUs allocated to the instance. 1 CU = 1 core and 4 GB memory. The same price applies to general-purpose instances and read-only secondary instances.
|
Region |
Price (USD/CU/hour) |
Singapore |
0.066604 |
China (Hong Kong) |
0.062904 |
US (Silicon Valley) |
0.061318 |
US (Virginia) |
0.056561 |
Malaysia (Kuala Lumpur) |
0.073476 |
Japan (Tokyo) |
0.062904 |
Indonesia (Jakarta) |
0.065547 |
China (Hangzhou) |
0.052861 |
China (Shanghai) |
0.052861 |
China (Beijing) |
0.052861 |
China (Shenzhen) |
0.052861 |
China (Ulanqab) |
0.052861 |
China (Chengdu) |
0.052861 |
China (Zhangjiakou) |
0.044932 |
Germany (Frankfurt) |
0.068190 |
UAE (Dubai) |
0.084269 |
Storage pricing
Storage is billed hourly based on actual data volume. Hologres offers four storage tiers; choose the tier that matches your redundancy requirements and access frequency.
Standard Storage — Locally Redundant (LRS)
Data is stored with local redundancy within a single availability zone. This is the standard tier for active workloads.
|
Region |
Price (USD/GB/hour) |
Singapore | 0.000379 |
China (Hong Kong) | 0.000364 |
US (Silicon Valley) | 0.000358 |
US (Virginia) | 0.000342 |
Malaysia (Kuala Lumpur) | 0.000410 |
Japan (Tokyo) | 0.000370 |
Indonesia (Jakarta) | 0.000382 |
China (Hangzhou) | 0.000311 |
China (Shanghai) | 0.000311 |
China (Beijing) | 0.000311 |
China (Shenzhen) | 0.000311 |
China (Ulanqab) | 0.000311 |
China (Chengdu) | 0.000311 |
China (Zhangjiakou) | 0.000264 |
Germany (Frankfurt) | 0.000395 |
UAE (Dubai) | 0.000622 |
Standard Storage — Zone-Redundant (ZRS)
Data is replicated across multiple availability zones for higher durability. Available in select regions.
|
Region |
Price (USD/GB/hour) |
China (Shenzhen) | 0.000404 |
Singapore | 0.000569 |
Infrequent Access Storage — Locally Redundant (LRS)
Lower-cost storage for data that is accessed infrequently. Uses local redundancy.
|
Region |
Price (USD/GB/hour) |
Singapore | 0.000055 |
China (Hong Kong) | 0.000052 |
US (Silicon Valley) | 0.000051 |
US (Virginia) | 0.000049 |
Malaysia (Kuala Lumpur) | 0.000059 |
Japan (Tokyo) | 0.000053 |
Indonesia (Jakarta) | 0.000055 |
China (Hangzhou) | 0.000045 |
China (Shanghai) | 0.000045 |
China (Beijing) | 0.000045 |
China (Shenzhen) | 0.000045 |
China (Ulanqab) | 0.000045 |
China (Chengdu) | 0.000045 |
China (Zhangjiakou) | 0.000038 |
Germany (Frankfurt) | 0.000057 |
UAE (Dubai) | 0.000090 |
Infrequent Access Storage — Zone-Redundant (ZRS)
Lower-cost storage with cross-zone redundancy for infrequently accessed data. Available in select regions.
|
Region |
Price (USD/GB/hour) |
China (Shenzhen) | 0.000059 |
Singapore | 0.000083 |
Network pricing
Cross-region snapshot replication incurs a network traffic fee based on the volume of data transferred. To stop this charge, disable cross-region snapshot replication.
|
Region |
Price (USD/GB) |
China (Hangzhou) | 0.0746 |
China (Shanghai) | 0.0746 |
China (Beijing) | 0.0746 |
China (Shenzhen) | 0.0746 |
China (Ulanqab) | 0.0746 |
China (Chengdu) | 0.0746 |
China (Hong Kong) | 0.08 |
Singapore | 0.08 |
Malaysia (Kuala Lumpur) | 0.08 |
Worked example
An instance with 64 CUs of compute and 100 GB of stored data running for one hour in Singapore:
-
Compute: 0.066604 USD/CU/hour × 64 CUs × 1 hour = 4.262656 USD
-
Storage: 0.000379 USD/GB/hour × 100 GB × 1 hour = 0.037900 USD
-
Total: 4.300556 USD
Overdue payment and notifications
If your account has an overdue balance below 1,000 USD, your instance remains available but bill generation is paused. When the overdue balance reaches 1,000 USD, the system attempts an automatic deduction. If the deduction fails, the suspension countdown begins.
The system notifies you by text message and email at each stage:
|
Billing method |
Suspension reminders (after failed deduction) |
Suspension |
Release reminders (after suspension) |
|
Pay-as-you-go |
7 days before suspension |
Suspended on day 15 after the failed deduction |
7 days before release |
|
3 days before suspension |
3 days before release |
||
|
1 day before suspension |
1 day before release |
Example: You purchase a Hologres instance and select Pay-as-you-go. Fees are settled hourly and automatically deducted from your account. If the accumulated overdue balance reaches 1,000 USD and a deduction fails, the system sends suspension reminders at 7 days, 3 days, and 1 day before the suspension date. If no payment is made, the instance is suspended on day 15. If the balance remains unpaid for 14 days after suspension, the instance is automatically released and all data is permanently deleted.
Important notes
-
Billing starts immediately after an instance is activated.
-
Storage charges continue during manual pause. Pausing stops compute charges, but storage fees accrue as long as data exists in the instance.
-
Data deletion is irreversible. Whether triggered by manual deletion or automatic release after suspension, all instance data is permanently deleted and cannot be recovered. Back up critical data regularly.
-
Overdue balance handling. Overdue balances below 1,000 USD pause bill generation but do not suspend the instance. The suspension countdown starts only after the overdue amount reaches 1,000 USD and the automatic deduction fails.