Alibaba Cloud billing has two parts: billing items (what you pay for) and billing methods (how you pay).
Total cost = resource usage per billing item × unit price. Choose the right billing method to control your cloud costs.
Billing Methods
Alibaba Cloud offers pay-as-you-go and subscription billing. Subscription includes subscription instances, Savings Plans, and resource plans.
|
Billing Method |
Definition |
Features |
|
|
Pay-as-you-go |
Use resources first, then pay. Pay hourly or by the second. |
Flexible to use, release anytime. |
|
|
Subscription |
Subscription |
Prepaid, get stable service for a fixed period. |
Exclusive resources, more cost-effective than pay-as-you-go. |
|
Savings Plan |
Commit to a fixed-term spend for deeper discounts than pay-as-you-go. |
Offset costs for different instances under the same product. |
|
|
Resource plan |
Pre-purchase usage (storage, traffic) to offset pay-as-you-go costs. |
Directly offset resource usage. |
|
Pay-as-you-go
Pay-as-you-go charges by resource runtime, data volume, or request count. No upfront commitment required, but unit prices are higher.
Pay-as-you-go resources are billed per second, and billing details are generated hourly or daily. The monthly bill is issued on the 3rd of the following month.
Key considerations:
-
Hourly billing data may be delayed.
-
Billing stops when you release the resources.
-
When you release a primary instance, verify that associated resources (Elastic IP Addresses, snapshots) are also released. Use cost alerts and budget management tools to monitor expenses.
Subscription Instances
Prepay for a fixed duration at lower unit prices. Longer terms yield deeper discounts, with predictable costs and exclusive resource access.
Key considerations:
-
Resources stop and data is deleted upon expiration. Enable auto-renewal to avoid interruptions.
-
Refund amounts are calculated based on usage duration and applicable discounts.
Savings Plan
Commit to a minimum hourly spend for 1, 3, or 5 years to get discounted pay-as-you-go prices.
Deep discounts while preserving pay-as-you-go flexibility.
Key considerations:
-
Savings Plans do not support refunds. Confirm the offset scope before purchase.
-
You are charged the committed amount regardless of actual usage.
-
Usage exceeding the committed amount is billed at standard pay-as-you-go rates.
Resource Plans
A resource plan is a prepaid method that automatically offsets usage at prices lower than pay-as-you-go.
Two types:
-
Total volume: You define total usage at purchase. The allowance decreases over the validity period and resets to zero upon expiration.
-
Periodic usage: The allowance resets each period (hourly, daily, or monthly). Unused portions do not carry over.
Key considerations:
-
Allowances reset to zero upon expiration and cannot be carried over or extended.
-
Resource plans offset only specific products and billing items. Confirm the offset scope before purchase.
-
Some resource plans require specific conditions to take effect.
-
Cancellation support varies by product.
What are the differences between Savings Plans and resource plans?
A Savings Plan is spending-based: you commit hourly spend on compute resources (ECS, ECI, ApsaraDB RDS) without locking into specific instance types.
A resource plan is usage-based: you purchase a fixed quantity of storage or network resources (OSS storage plans, CDN data transfer plans) measured in gigabytes or offset counts.
Billing items
A billing item is the smallest metering unit for resources and services, each with its own metrics, billing cycle, and unit price.
Billing items are typically divided into two categories:
-
Basic billing items: Charges based on compute, storage, and network usage. Examples: instance type fees (ECS), storage fees (disks, OSS), data transfer fees (outbound Internet traffic, CDN), request fees (API calls), and compute fees (CPU/memory duration).
-
Value-added billing items: Fees for advanced capabilities such as image processing, transfer acceleration, and software subscriptions.
Billing items combine with billing methods to generate your bills. Final cost = usage of each billing item × unit price.
Choose a Billing Method
Choose a billing method based on your resource usage patterns.
Stable operations suit prepaid methods to lock in costs. Fluctuating operations suit pay-as-you-go for elasticity. Combine methods to balance cost and flexibility.
Stable Operations: Lock in Costs, Prefer Subscription Instances
Applies to long-running systems with fixed configurations (enterprise websites, core databases). Multi-year purchases receive higher discounts.
Elastic Operations: Flexible Cost Reduction, Recommend Savings Plans
Applies to scenarios with frequent configuration changes (iterating Internet applications, growing SaaS services). Balances discounts with upgrade/downgrade flexibility.
Fluctuating Operations: Elastic Response, Layered Cost Reduction
Applies to periodic load fluctuations (daytime peaks/nighttime lows, busy weekdays/idle weekends):
-
Base load: Use a Savings Plan to lock in costs.
-
Fluctuating portion: Use the pay-as-you-go method for on-demand scaling.
This balances cost optimization and resource efficiency, avoiding overpayment for peak loads or idle resources.
Burst Operations: Start and Stop on Demand, Zero Idle Costs
Applies to unpredictable traffic surges (sales promotions, marketing campaigns, hot spot events). Scale out before events and release resources immediately afterward — no prior planning, no idle costs.
Exploratory Operations: Flexible Experimentation, Pay on Demand
Applies to early-stage projects with uncertain usage (MVP validation, technology selection, POC testing):
-
Use pay-as-you-go. Start resources as needed, release when finished, and pay only for actual usage.
-
After validation, migrate to subscription instances or a Savings Plan for lower costs.
Storage and Data Transfer: Batch Purchase, Automatic Offset
Applies to stable, predictable usage (log storage, data backup, CDN data transfer). Estimate average monthly usage from historical consumption and purchase a matching resource plan. Offsets apply automatically.
Combination Usage Suggestions
In practice, most operations combine multiple billing methods:
-
Core stable load: Use subscription instances or a Savings Plan to lock in base costs.
-
Elastic scaling portion: Use the pay-as-you-go method to handle peak demands.
-
Storage and data transfer: Use resource plans for bulk purchases to get discounts.