Alibaba Cloud has no customer tiers — only how you buy changes the price. Three official discounts, two signup barriers.
Ask "how do I get an Alibaba Cloud discount" and the most common wrong answer is to go hunting for a customer tier or an enterprise agreement.
Alibaba Cloud International has no customer tier — everyone sees the same price. Only two things change your effective rate: how you buy it and who settles the bill.
This page covers the first (the three official routes and how to combine them); the channel side is on Alibaba Cloud discounts and reseller pricing. Seeing all five side by side makes the differences sharper — which ones lock the spec and which do not — see cloud discount mechanisms compared.
First, correct one assumption: there is no customer tier
People arriving from other clouds tend to assume "spend enough and you can negotiate". On Alibaba Cloud International that does not hold: the listed price is identical for everyone, and there is no automatic tier that kicks in past a spend threshold.
What does change the rate is how you buy. That is also why people conclude the discounts are hard to get — they are looking for a road that does not exist (negotiation) and missing the three that do (term, commitment, interruptibility).
The key difference from AWS: AWS Reserved Instances are "commitment plus locked instance family and region"; Alibaba Cloud subscription is "term" — one, three or five years, with the unit price falling as the term lengthens. Different units of measurement, so different judgement — importing the AWS "compute your steady baseline" routine verbatim will have you optimising the wrong variable.
If you are choosing between providers, how the five price things is on which of the five clouds to choose.
Three official discounts, all trading term or interruptibility for price
There are exactly three official discounts. Start by seeing what each one gives up:
| Route | What you give up | What you get | Refundable |
|---|---|---|---|
| Subscription (annual billing) | A block of time bought upfront (1/3/5 years) | Unit price falls with the term — the most direct route | Non-refundable on expiry |
| Savings Plans | A committed hourly spend | Discount on pay-as-you-go, without locking a spec | Commitment must be met |
| Preemptible instances | Accepting reclamation | Lowest price | Notice a few minutes before reclaim, then interruption |
In one line: subscription buys time, Savings Plans buy an amount, preemptible buys interruptibility. They trade different things, so the question is not "which discounts most" but "which can I give up".
That is also why they combine: giving up different things means no conflict.
Subscription: one, three or five years
The most used and most mis-bought route. The logic is plain: the longer you buy, the lower the unit price. But "how much lower" and "is it worth it" are different questions.
| Term | Unit price | Risk |
|---|---|---|
| 1 year | Discounted, least of the three | Shortest lock-in; cheapest to abandon if the shape changes |
| 3 years | Deeper discount | Locked three years: region moves, architecture changes and shrinking all carried |
| 5 years | Deepest discount | Locked five years — only for systems whose shape is entirely settled |
The judgement is not the discount rate but these three questions:
- Will this machine still exist in a year? If unsure, buy one year. The extra discount does not cover one write-off.
- Will the spec change? Subscription is tied to a specific spec. Upgrading usually means buying again or paying the difference — it does not follow automatically.
- Will the region change? As on other clouds, this kind of subscription is normally region-bound.
⛔ "Non-refundable" is the hard constraint: once bought, unused subscription time is not refunded. So buy one year first and decide about three next year — trading a year of real data for next year's certainty is far cheaper than gambling long-term upfront.
The same logic as AWS Reserved Instances (commit only the baseline; batching costs nothing) is set out in how to buy AWS Reserved Instances — different products, but "reversible first, irreversible last" is universal.
Savings Plans: commit an amount, not a spec
Savings Plans work like this: commit to an hourly spend and receive a discount on pay-as-you-go usage. The key difference from subscription is that they do not lock a specific spec — you commit money, not a machine.
- Good for: a workload with a real baseline whose spec will change (upgrades, moves between instance families).
- Bad for: an early stage where usage still swings wildly and there is no baseline yet. Committing an amount you cannot consume is waste.
- Versus subscription: they do not conflict. A common pattern is subscription for the steady baseline, Savings Plans for the elastic remainder.
How to size the commitment: same thinking as on AWS — commit the steady baseline, not peak or average. Lay the last few months of spend out by day and find the part that occurs every single day; that is the committable number.
One caveat: unconsumed commitment within the period is generally not refunded. The cost of over-buying here is the same as over-committing on term.
Preemptible instances: cheapest, but reclaimed
Preemptible instances use reclaimable spare capacity — the lowest price, in exchange for a few minutes' notice before reclamation and interruption.
| Dimension | Preemptible | Subscription / Savings Plans |
|---|---|---|
| Price | Lowest | Mid (commitment for discount) |
| Interruption | Yes, a few minutes' notice | No |
| Good for | Batch, testing, retryable jobs | Long-running steady services |
There is only one test: if it is interrupted, is re-running acceptable? If yes, use it — if not, do not. Do not run a database primary, anything with an external SLA, or jobs that need a human to recover.
The AWS equivalent: preemptible ≈ AWS Spot, and the mechanics are nearly identical. So the boundaries worked out on the AWS side carry over — four kinds that fit and three that must not are in AWS Spot Instances: how much they save.
Combining them: reversible first, irreversible last
Stack the three in this order, on the principle of do what needs no commitment before what does:
- Step 1 (zero risk): clean up idle resources and re-tier storage. Unused instances, unattached disks, cold data sitting on a hot tier — clear these first and the baseline drops visibly.
- Step 2 (stoppable any time): move interruptible work to preemptible. Batch, testing and offline compute go first; none of it needs a commitment.
- Step 3 (small reversible exposure): Savings Plans over the elastic baseline. Commit an amount, not a spec, so a shape change is survivable.
- Step 4 (irreversible): subscription for the steady state. By now the earlier steps have told you what the steady state actually is. Reverse the order and you lock in a wrong number.
| Order | Action | Cost |
|---|---|---|
| 1 | Clean-up / storage tiering | None, do it any time |
| 2 | Preemptible for interruptible work | Interruption risk (manageable) |
| 3 | Savings Plans over the elastic baseline | Committed amount, no spec lock |
| 4 | Subscription for the steady state | Locks the term, non-refundable |
There is a fifth step, and it does not conflict with the other four: provision and settle through a reseller. The first four lower the unit price Alibaba Cloud bills; the channel lowers what you actually pay. Different layers, both apply. Mechanism on Alibaba Cloud discounts and reseller pricing.
Two barriers: a non-mainland phone number and GPU quotas
These two are specific to Alibaba Cloud International and unavoidable when buying direct. Plenty of people stall here and conclude the discounts are unavailable, when in fact they never got past registration.
| Barrier | What it looks like | How to get past it |
|---|---|---|
| Non-mainland phone number | International signup requires email plus a phone number from outside mainland China | Channel-assisted provisioning removes this step |
| Card binding trips risk control | Certain cards are blocked when binding | Change card, or settle through a channel (does not depend on your card) |
| Very low GPU quota on new accounts | New accounts start with little GPU quota and must file a ticket to request more | Channels can usually assist with the quota request |
⛔ The GPU quota point is routinely underestimated: if you need GPUs (inference, training, rendering), the tiny default quota on a new account is a genuine blocker, and tickets take time to approve. If the project has a deadline, arrange this early — not on the day you need to scale.
Worth noting too: outside audio and video, Alibaba Cloud International is often the pick for e-commerce, gaming and containerised backends in overseas builds. How the five differ by scenario is on which of the five clouds to choose.
Common questions
Does Alibaba Cloud have an enterprise or volume discount?
There is no customer tier — everyone sees the same price. What changes the rate is how you buy (subscription / Savings Plans / preemptible) and who settles (reseller). If you are looking for "spend X and get an automatic discount", that does not exist; effort spent on picking the right term and clearing idle resources pays far more reliably.
Is a three-year subscription worth it?
Only if the machine's shape is fixed for three years — spec, region and whether you still need it. Non-refundable is the hard constraint. The safe route is one year first, then decide about longer terms once real data confirms the steady state. The extra discount rarely covers a single write-off.
Can Savings Plans and subscription be used together?
Yes, and it is common: subscription locks the steady baseline (deeper discount), Savings Plans cover the elastic part whose spec may change (no spec lock). They give up different things, so they do not conflict. Work out the baseline before deciding how much of each to buy.
Are preemptible instances suitable for databases?
No. They get reclaimed with a few minutes' notice, and interrupting a database primary means interrupted writes and a failover — far more expensive than the saving. Preemptible suits batch, testing, offline compute and retryable jobs; the test is whether re-running after an interruption is acceptable. See AWS Spot Instances.
Do I really need a non-mainland phone number?
Alibaba Cloud International requires email plus verification via a phone number from outside mainland China — one of the barriers to buying direct. If that stalls you, channel-assisted provisioning is the usual answer. A channel's value is not only price; it is getting registration and settlement to actually work. See Alibaba Cloud discounts and reseller pricing.
Do official and reseller discounts conflict?
No — different layers. Official discounts (subscription / Savings Plans / preemptible) lower the unit price on the Alibaba Cloud bill; a reseller discount lowers what you actually settle. Both apply at once; it is not either/or. Mechanism on Alibaba Cloud discounts and reseller pricing.