Alibaba Cloud China — partition and entity gates
Alibaba Cloud China site (aliyun.com) and International (alibabacloud.com) are separate account rails — not a region toggle. Product teams need entity verification, Mainland China regions, and ICP adjacency before public go-live.
Alibaba Cloud in Mainland China is an account-and-compliance partition — not a region you add to a global Aliyun mental model. The China website (aliyun.com) and the International website (alibabacloud.com) run separate accounts, billing, and filing rails. Your product team must clear entity / verification, Mainland China region placement, and ICP adjacency before public workloads are real. Treat this Guide as a decision map — not a self-serve handbook that finishes China cloud alone.
What Alibaba Cloud China means for product teams
Hard names your stack decision will use:
- Two websites, two account systems — Official China site vs International site docs state accounts, billing, and data are fully independent. You cannot convert a China Website account into an International account (or the reverse).
- China site registration floor — aliyun.com registration expects a mobile number from Mainland China, and identity verification is mandatory before purchasing or using cloud resources.
- International site is a different rail — alibabacloud.com registers with email plus a verified mobile outside Mainland China. Identity verification is required for specific scenarios such as purchasing resources in Mainland China.
- Mainland China regions ≠ Hong Kong — ECS documents list Mainland China regions such as Beijing (
cn-beijing), Shanghai (cn-shanghai), Hangzhou (cn-hangzhou), Shenzhen, and others, separately from China (Hong Kong) (cn-hongkong). ICP follows server location in Mainland China. - ICP adjacency for public content — Websites deployed in Mainland China that provide public services must complete ICP filing. Filing process and console paths differ between China and International sites; Chinese-language filing UX is the operational norm.
- Billing and legal entity split — China Website settlement is CNY (VAT-inclusive) with domestic payment methods; International settles primarily in USD. Contracting entities differ by site.
- Common myth — “Buy any Alibaba Cloud region labeled China and treat it like a global AZ.” Hong Kong placement, International-only accounts, and skipped ICP are the usual late surprises.
Vocabulary first. Next: what must be true before console work, then the path your architecture review needs.
What must be true before Aliyun console work
Missing any of these stops your product team before a stable China reference architecture — often before the first usable Mainland China payer path or public DNS cutover.
| Precondition | Why your process stalls |
|---|---|
| Partition verdict — Mainland China residency / regulator / domestic integration vs reachability-only | Teams that only need faster access to a global footprint waste cycles buying Mainland China rails they cannot operate |
Account rail chosen — China site (aliyun.com) vs International (alibabacloud.com) | Accounts cannot be converted; wrong rail forces re-registration and resource migration |
| Mainland China mobile + identity verification path (China site) or verified International identity for Mainland China purchase | Registration and purchase block without the verification model that site requires |
| PRC organizing entity or China landing partner for public ICP | Overseas enterprises without a Mainland China branch / representative-office path stall at filing entity materials |
| Region plan on Mainland China nodes — not Hong Kong-as-China | Hong Kong does not trigger Mainland China ICP and does not satisfy residency decisions that require Mainland China |
| ICP / public-publish plan aligned to the access provider | Without filing, public websites on Mainland China servers stay blocked or non-compliant |
| IaC and CI/CD scoped to the chosen account + endpoints | Global modules, artifact feeds, and IAM assumptions often break across site partitions |
Chinese-language consoles, real-name verification, and filing rails are part of this floor. Product teams usually cannot treat Alibaba Cloud China as a handbook finished from an overseas laptop alone.
From global Aliyun assumption to China-ready stack
| Stage | Decision / outcome |
|---|---|
| 1. Partition verdict | Confirm the workload must run in Mainland China (residency / regulator / domestic integration) — not “reach China users from International regions” alone |
| 2. Account rail | Choose China site vs International; plan for non-convertible accounts and separate billing |
| 3. Entity & verification | Lock Mainland China mobile / real-name (China site) or International identity for Mainland China purchase; confirm who holds the organizing entity for ICP |
| 4. Region plan | Place compute on Mainland China regions (Beijing / Shanghai / Hangzhou / Shenzhen…); do not treat Hong Kong as the Mainland China ICP path |
| 5. Deploy baseline | Redeploy IAM, networking, data stores, and pipelines on the chosen China-capable account and endpoints |
| 6. Filing adjacency | Align domain, DNS, and public publish with ICP / PSB before cutover |
| 7. Operate | Keep International and China stacks explicitly separate; support and fapiao / settlement follow the site you chose |
Why account, entity, and ICP failures cascade
Wrong website assumed interchangeable → re-platform mid-program. Official docs state the two sites cannot convert accounts. Architecture reviews that treat alibabacloud.com credentials as a China site console waste sprints until the payer rail is rebuilt.
International purchase without verification → Mainland China SKUs blocked. Identity verification is required to purchase or use Mainland China resources on the International rail. Teams that skip it discover the gate at checkout, not in the design doc.
Cloud ready, entity path missing → ICP never opens. Public sites on Mainland China servers need an organizing entity that filing administrations accept. Overseas enterprises without a Mainland China branch or permanent representative office stall on materials — see Alibaba Cloud’s overseas enterprise filing guidance.
Hong Kong mistaken for Mainland China → false “China done.” cn-hongkong is not a Mainland China region for ICP. Reachability experiments from Hong Kong do not clear Mainland China residency or filing gates.
Cloud ready, ICP ignored → public publish blocked. Buying ECS or CDN in Mainland China does not authorize customer-facing DNS cutover — see ICP filing and domain/DNS and ICP licence questions.
Global CI/CD pointed at the wrong site → deploy theater. Pipelines, artifact mirrors, and secrets built for one account system fail silently against the other until rebuilt for the chosen rail.
Control plane — China site vs International
| Dimension | China Website (aliyun.com) | International Website (alibabacloud.com) |
|---|---|---|
| Account registration | Mainland China mobile number | Email + verified mobile outside Mainland China |
| Identity verification | Mandatory before purchase / use | As needed — required for Mainland China purchase and similar scenarios |
| Account data location | Data centers in Mainland China | Data centers outside Mainland China |
| Billing | CNY, VAT-inclusive; Alipay / WeChat Pay / UnionPay / corporate transfer | USD (and other supported currencies); cards / PayPal / transfer by region |
| Account conversion | Not supported either direction | Not supported either direction |
| ICP filing UX | Primary China filing console path (Chinese-language) | Filing paths differ; docs recommend a China site account for easier management; International site does not support the same full filing application model |
| Mainland China compliance | Identity verification + ICP for public Mainland China sites | Same Mainland China regulations apply when you use Mainland China resources |
Source: China site vs International site, What is ICP filing, Identity verification overview.
Necessity: product teams cannot sign off a China architecture without choosing the account rail and verifying Mainland China purchase + filing paths — the table above is the hard-gate view, not a catalog dump.
What blocks product teams on Alibaba Cloud China
- Treating China as a global region toggle — billing, identity, and filing do not span the two websites.
- No Mainland China mobile / real-name path on the China site — registration and purchase stall without the verification floor.
- No PRC organizing entity for public ICP — overseas-only packs stall at filing materials even when ECS exists.
- Hong Kong-as-China shortcuts — residency and ICP decisions fail when only
cn-hongkongis in the diagram. - Buying cloud before ICP — public endpoints stay non-compliant until filing clears.
- Assuming International filing equals China site filing — Chinese-language consoles and China site accounts are the practical filing rail.
- Global-only CI/CD and artifact feeds — pipelines that cannot authenticate to the chosen site never become a China release train.
- Confusing reachability with residency — speeding access for China users to an International footprint is a different problem than running workloads inside Mainland China.
When Alibaba Cloud China fits
Choose Alibaba Cloud’s Mainland China rails when residency, regulator expectations, domestic integrations, or filing-provider choice require workloads inside Mainland China — and you can sustain a China-local operating model: the correct website account, verification, filing, and a region plan that does not pretend Hong Kong is Mainland China.
It is usually the wrong first answer when the problem is only reachability of a global footprint to China users. For side-by-side sovereign-cloud reads, see AWS China, Azure China, and Cloudflare China Network. For hosting and filing adjacency, see Host a website in Mainland China and ICP and PSB filing. For provider-neutral route selection, see How we choose providers without selling them or start a China Readiness Assessment.
Minimum diligence before sign-off: lock China site vs International; confirm identity verification for Mainland China purchase; place regions on Mainland China nodes when residency or ICP applies; confirm ICP status before public DNS cutover; scope IaC and CI/CD to the chosen account rail.
When you need a China landing partner for Alibaba Cloud
Most product teams exploring Mainland China entry need a China landing partner to open or operate the China account rail, complete real-name and entity materials, and align ICP / hosting with the same stack — not a longer console tutorial. Your team still owns product and architecture decisions; the partner path makes entity, verification, and filing rails executable when they are not already in-house.
What we can offer?
Alibaba Cloud China is an account-and-compliance partition — China site vs International rails, entity verification, Mainland China regions, and ICP adjacency — not a global region toggle. Chinaready helps your product team decide whether Aliyun China fits and what must be true before public go-live:
- China Readiness Assessment — Map whether residency forces Mainland China Alibaba Cloud vs International reachability, which account/entity rail you can execute, and which filing gates block the reference architecture.
- China Access Acceleration — Keep admin paths, dependencies, and hybrid links workable while International and China stacks stay explicitly separate.
- China Product Hosting — Place China-critical workloads on a Mainland China–operable stack where ICP/PSB and Alibaba Cloud endpoints describe one coherent publish path.
- Mobile App Distribution — Ship channel launches on their own gates while backend residency and China cloud choices stay consistent with the live product boundary.
Contact us when you need an Alibaba Cloud China vs International decision — account rail, entity verification, and filing adjacency — without treating China as a region checkbox.
References
- Alibaba Cloud — China site vs International site — account, billing, and compliance split; no account conversion
- Alibaba Cloud — identity verification overview — Mainland China purchase and verification gates
- Alibaba Cloud — register an account — registration notes for International accounts
- Alibaba Cloud — what is ICP filing — Mainland China server scope; International filing limits
- Alibaba Cloud — ICP filing for enterprises outside Mainland China — branch / representative-office materials
- Alibaba Cloud — ICP server and access information check — Mainland China server eligibility vs Hong Kong / overseas
- Alibaba Cloud — ECS regions and zones — Mainland China region IDs vs China (Hong Kong)
- AWS China — what works — Chinaready guide
- Azure China — what works — Chinaready guide
- Cloudflare China Network — Chinaready guide
- ICP and PSB filing for foreign companies — Chinaready guide
Frequently asked questions
Is Alibaba Cloud China just another region on my international alibabacloud.com account?
No. Official docs describe the China website (aliyun.com) and the International website (alibabacloud.com) as separate systems with independent accounts, billing, and compliance frameworks. Accounts cannot be converted between sites — you register on the rail that matches the operating model, then migrate resources if needed.
Can I buy Mainland China resources from an International account?
Often yes after identity verification for Mainland China purchase scenarios — but ICP filing, CNY settlement norms, and China-first product updates still differ from the China site. Using Mainland China resources requires local compliance (identity verification and ICP for public sites) regardless of which website you used to buy.
Do we need ICP filing to host a public site on Alibaba Cloud in Mainland China?
Yes for websites or apps whose servers sit in Mainland China and provide public services. ICP filing applies to Mainland China server location — China (Hong Kong) and other nodes outside Mainland China do not trigger the same ICP path. Cloud purchase alone does not clear the public publish gate.
Why do teams prefer an aliyun.com China site account for filing?
Alibaba Cloud documents that the International site does not support the full ICP / app filing application path the same way; the filing system is Chinese-language, and mobile filing expects a China site account. Official guidance recommends a China site account for easier filing management.
Is China (Hong Kong) a Mainland China region for ICP?
No. Hong Kong is outside Mainland China for ICP purposes. Hosting only in China (Hong Kong) does not satisfy Mainland China ICP requirements — and does not replace a Mainland China residency decision when regulators or domestic integrations require it.
Can product teams finish Alibaba Cloud China onboarding from a handbook alone?
Usually no. Separate account rails, Mainland China mobile / real-name verification, entity paths for ICP, Chinese-language filing consoles, and region placement stop most product teams before a stable China reference architecture. Use this Guide as a decision map; execute with Mainland China ops rails or a China landing partner.
