Article

Alibaba Cloud vs Tencent Cloud for Foreign Companies: How to Choose

September 28, 2026

You have decided on mainland hosting to fix your China performance problem. The next question is which provider: Alibaba Cloud vs Tencent Cloud. Both Alibaba Cloud and Tencent Cloud serve the same fundamental purpose — in-country origin servers and China-tuned CDN — but they differ in filing workflow, regional coverage, ecosystem depth, and English-language support.

This article gives you a five-criteria decision framework. It does not declare a winner. The right choice depends on your stack, your entity structure, and where your users sit. We implement on both.

Why the provider choice matters less than the hosting decision

Before the criteria, a framing point. The reason your site is slow in China is the cross-border hop — data traveling from overseas datacenters through congested international links to China ISPs. Mainland hosting on Alibaba Cloud or Tencent Cloud eliminates that hop by placing your origin on the same networks as your visitors. A China-tuned CDN on top cuts time-to-first-byte from seconds to under one second with proper configuration. Both providers deliver this outcome. The provider decision is about how you get there — workflow, lock-in, and operational fit — not whether you get there. Spend your energy on the hosting decision first. The provider selection follows.

The five criteria for foreign companies: Alibaba Cloud vs Tencent Cloud

1. ICP filing support and workflow

Mainland hosting on either provider triggers the ICP filing obligation. The filing runs through the provider's portal — you submit server, domain, and entity information, and the provider forwards it through the regulatory review chain.

On Alibaba Cloud, you submit your information, then the provider runs an initial review with phone verification (1–2 business days). MIIT (Ministry of Industry and Information Technology) SMS verification follows within 24 hours. Provincial communications administration review comes next, within 20 working days. Once approved, the filing number is issued, and the public-security (police) filing follows. The filing service itself is free. One important constraint: the Alibaba Cloud International site does not support ICP filing — filers must use an Alibaba Cloud China site (aliyun.com) account, or the GoChina ICP Filing Assistant. The CDN domain and account checklist covers what this gate means for CDN acceleration domains. Unfiled domains resolving to mainland Alibaba servers are blocked by Alibaba's monitoring, and an existing filing from another provider must add Alibaba Cloud as a service provider.

On Tencent Cloud, the filing follows the same MIIT regulatory measures. You prepare your domain, purchase filing-eligible Tencent Cloud resources, and submit through the provider's filing system via PC portal or Tencent mini-program. Documented flows cover first filing, access filing (transferring an existing filing in), new-service additions, modification, and cancellation — including MIIT SMS verification and subsequent public-security filing. Unfiled sites may not provide services in the PRC, and false filing information leads to site closure and filing revocation.

The practical difference: both portals handle the same regulatory pipeline. The choice point is which provider's portal your entity can file through — which connects directly to criterion 2.

2. Entity-type and business-category acceptance

Your provider must accept your entity type and business category for ICP filing. This is the gate that determines whether you can file at all.

For foreign-owned companies, the filing entity is typically a WFOE (Wholly Foreign-Owned Enterprise). Not every business category qualifies, and the acceptable categories vary by province. Before you commit to a provider, confirm that your entity structure and business scope can pass filing review on that provider's portal. This is a pre-flight check, not something you discover mid-application. Our ICP filing & compliance service covers the entity-readiness phase in detail.

3. Region and network coverage in mainland China

Both providers operate multiple mainland regions, but the footprint differs.

Alibaba Cloud's mainland regions (as of September 2026) include Beijing (12 availability zones), Shanghai (12), Hangzhou (8), Shenzhen (6), Qingdao (2), Zhangjiakou (3), Hohhot (2), Ulanqab, and Wuhan Local Region (1). Globally, ECS is available across 29 regions.

Tencent Cloud's mainland regions include Beijing (6 availability zones), Shanghai (7), Nanjing (3), Guangzhou (5), Chengdu (2), Chongqing (1), and Zhongwei (1), plus dedicated financial-institutions zones in Beijing, Shanghai, and Shenzhen.

For most foreign companies, the decision-relevant question is not which provider has more regions in absolute terms, but whether your target user base sits close to one provider's datacenter geography. If your visitors concentrate in the Pearl River Delta, Guangzhou or Shenzhen matters. If they cluster around the Yangtze Delta, Shanghai and Hangzhou matter. Both providers cover the major population centers. Whichever region you lean toward, validate the choice with real measurements from inside China before committing — the procedure is in how to test your website from China.

4. Ecosystem lock-in and stack fit

Each provider has proprietary services that create switching costs once you build on them.

Alibaba Cloud's lock-in surface includes OSS (object storage with 12-nines durability and 99.995% availability, positioned as a data-lake foundation) and MaxCompute, a proprietary cloud-native big data computing service (formerly ODPS) for SaaS data warehousing.

Tencent Cloud's proprietary stack includes TDSQL and TDSQL-C (self-developed cloud-native relational databases, with TDSQL-C MySQL-compatible), CKafka (managed Kafka-compatible message queue), COS (object storage), and SCF (serverless functions). Tencent also offers a dedicated WeChat ecosystem category, including Mini Program acceleration — WeChat-native security and acceleration for mini-programs, H5, and apps.

The WeChat ecosystem angle is the differentiator for brands building mini-programs or WeChat-native commerce (see our WeChat ecosystem service). If your China strategy runs through WeChat, Tencent's native integration is a structural advantage. If your stack is data-heavy — large-scale analytics, data warehousing — Alibaba's MaxCompute ecosystem may fit better. For standard web hosting with CDN, neither provider's proprietary services create meaningful lock-in. You are running compute and storage that map to standard patterns.

5. English-language documentation, console, and support

Your operations team needs to manage the China infrastructure in a language they can work in.

Alibaba Cloud operates alibabacloud.com as its English international portal, with English documentation, console, Contact Sales, an AI assistant, and USD-denominated support tiers (Basic free, Developer, Business, Enterprise).

Tencent Cloud publishes English documentation at intl.cloud.tencent.com — the Regions & Zones and CVM billing guides are natively in English. Verify console language and support coverage for your specific account type before committing.

Alibaba Cloud publishes ECS pricing on subscription (monthly/yearly) and pay-as-you-go models, with resource packages for committed workloads plus preemptible and reserved instance options. Its published ECS SLA is 99.975% for single-instance and 99.995% for multi-zone same-region deployments, with OSS at 99.995%. For Tencent Cloud, review the provider's published billing and SLA documentation for current commitments before you commit. For the entry-tier cost layer — bundles vs pay-as-you-go with the published price anchors on both vendors — see what mainland China hosting actually costs.

Decision framework: which criteria to weight first (Alibaba Cloud vs Tencent Cloud)

The criteria above do not carry equal weight for every company. Here is the order we recommend:

1. Start with entity readiness. If your entity type or business category cannot pass filing on a given provider's portal, that provider is off the table regardless of its technical merits. Criterion 2 is a gate, not a preference.
2. Then match stack to ecosystem. If your China product runs through WeChat mini-programs, Tencent's native integration shifts from convenient to architectural. If your analytics workload is the primary China use case, evaluate MaxCompute against your data pipeline requirements.
3. Then check region proximity. For most foreign brand sites, any major region works. The question becomes relevant when your visitor geography clusters near a specific city or when you need multi-zone redundancy in a particular area.
4. Then evaluate English support. Both providers offer English documentation and international portals. The difference is in support tier structure and pricing — relevant for teams that need responsive English-language incident support.

The provider choice is a Phase 2 decision in the ICP filing process. Phase 1 — entity readiness — determines what is possible before you evaluate what is preferable. See our ICP filing timeline for the full phase breakdown.

Provider fit by workload: scenario → provider matrix

The five criteria above describe what to evaluate. This table maps common workload patterns to the provider whose platform strengths align with each one. The rows map to the criteria themselves — ecosystem fit (criterion 4), entity acceptance (criterion 2), and region proximity (criterion 3). Performance is not a differentiator: with mainland origin plus CDN and proper tuning, both providers deliver time-to-first-byte under one second.

How to decide: the verification-first doctrine

The decision framework above orders the criteria by weight. Here is the execution sequence — the order you actually run the checks in, so that each step either confirms the choice or eliminates it before you spend money on resources.

1. Entity and category gate. Check both provider portals. Confirm that your entity type and business category can pass ICP filing on each one. If only one accepts your structure, the provider decision is settled at criterion 2.
2. Region vs visitor geography. Map where your China users sit, then apply the criterion 3 test: which provider’s mainland regions sit closest to your visitor base.
3. Four measurements, per-carrier, never averaged. Run the four measurements against each provider’s region: first-render time and TTFB from a mainland connection, blocked third-party dependencies, DNS resolution location, and CDN edge presence. Test each carrier line separately — Telecom, Unicom, Mobile — and never average across carriers.
4. Ten-point readiness checklist as the Phase 1 map. Run the China readiness diagnostic. Items 1–6 surface performance problems (slow renders, offshore origin, offshore CDN edge, external DNS, blocked embeds, timed-out endpoints). Items 9–10 are compliance gates (ICP filing status, mainland entity readiness). A yes on any of those eight items tells you what to fix before the provider choice becomes relevant.
5. Cost anchors last. Only after the gate, the geography, the measurements, and the readiness checklist converge on a provider does the cost layer become the tiebreaker — the next section maps it.

Validate the choice with real measurements from inside China before you purchase resources — not after.

The cost layer in one view

Entry-tier hosting on both providers splits into two paths: bundled application servers (subscription-only, fixed resource envelope) and full elastic compute (subscription or pay-as-you-go). The full price-anchor comparison — including worked examples and the three-use-case decision matrix — lives in the hosting cost article. A scenario worksheet there tabulates three-month costs from those documented examples.

Two structural points to flag here, because they affect the provider decision:

• The account split. Both providers’ international consoles exclude mainland deployment. Alibaba Cloud’s international portal does not support ICP filing. Tencent’s international Lighthouse list covers Hong Kong and non-mainland regions only. Mainland hosting on either provider means a China-site account and CNY pricing.
• The filing is free; the calendar is not. Neither provider charges for the ICP filing service itself. The real cost is 2–4 weeks of calendar time before any mainland go-live — plan that window into your launch schedule regardless of which provider you choose.

Beyond the server: traffic overage, CDN billing, and HTTPS certificates are separate line items on both providers. The hosting-cost article covers each one.

Switching costs: what’s actually portable

If you build on a provider’s proprietary services, those services become the switching cost. The lock-in inventory from criterion 4 tells you which services create it:

• Alibaba Cloud: OSS (object storage, data-lake foundation) and MaxCompute (proprietary big-data computing for SaaS data warehousing).
• Tencent Cloud: TDSQL and TDSQL-C (self-developed relational databases), CKafka (managed message queue), COS (object storage), SCF (serverless functions), and the WeChat ecosystem category including Mini Program acceleration.

For standard compute and storage — virtual machines, generic object storage, standard CDN — the portability surface is large. These workloads map to patterns that run on either provider without fundamental re-architecture.

One compliance-specific switching cost: an existing ICP filing from another provider must add Alibaba Cloud as a service provider; Tencent documents an access-filing flow for transferring an existing filing in. Either way the filing does not move automatically — plan the filing update alongside any infrastructure migration, inside the typical 2–4 week filing calendar. The safe-order sequence — access filing first, remove the old association only after — is the provider-switch checklist.

Frequently asked questions

More questions? See the full articles index and the FAQ hub.

Next steps

Choosing between Alibaba Cloud and Tencent Cloud is one decision in a larger China infrastructure plan. Our mainland hosting and CDN service covers provider selection, deployment, and CDN tuning as a single engagement.

If you want to discuss your specific stack, entity structure, and visitor geography, reach out at hello@chinagateway.pro. We will map the decision against your constraints.