Tencent Cloud¶
Summary
Tencent Cloud is the cloud platform of Tencent Holdings. It is the third-largest cloud infrastructure provider in mainland China (about 10% share in 2025, behind Alibaba Cloud and Huawei Cloud) and reported 66 availability zones across 23 regions on 2026-08-18. Its fastest international growth is in Southeast Asia (Singapore, Jakarta, Bangkok, and a new Johor region in Malaysia), the Middle East (Saudi Arabia), Japan, and Europe (Frankfurt). It offers the full IaaS/PaaS range. The services that stand out architecturally are CCN transit networking, the TDSQL database family, Anti-DDoS/EdgeOne edge security, and a multi-account stack of Tencent Cloud Organization (TCO), Identity Center, and the Control Center landing zone. This hub summarizes the platform. The linked pages hold the recipes, look-up tables, and design rationale.
Key Facts¶
| Attribute | Detail |
|---|---|
| Owner | Tencent Holdings (reported in the "FinTech and Business Services" segment) |
| Websites | tencentcloud.com (international) / cloud.tencent.com (mainland China). Separate sites, accounts, and pricing |
| Footprint | 66 AZs in 23 regions (2026-08-18). Up from 64 AZs in 22 regions (2026-03-02) |
| Latest Version (tooling) | Terraform provider tencentcloudstack/tencentcloud 1.83.33 (2026-09-21). tccli 3.1.174.1 (2026-09-24) |
| License / model | Proprietary commercial cloud. Pay-as-you-go, monthly subscription, and 95th-percentile network billing. CLI and SDKs are Apache-2.0, the Terraform provider is MPL-2.0 |
| IaC | Terraform tencentcloudstack/tencentcloud and landing-zone modules (tencentcloud-landing-zone-booster) |
| Multi-account | TCO (departments, SCPs, tag policies, resource sharing) + Identity Center (SAML 2.0, SCIM) + Control Center (landing zone, account factory) |
| Southeast Asia regions | Singapore, Jakarta (ap-jakarta, 3 AZs), Bangkok, Johor (2 AZs live 2026-08, third planned) |
| Market position | ~10% of mainland China cloud infrastructure (Omdia, Q4 2025). ~2% worldwide, 8th (Synergy, Q4 2024) |
Architecture at a Glance¶
The compact diagram shows how governance, networking, and workloads relate in a typical landing zone. The full diagrams are in Explanation.
flowchart LR
CIC["Identity Center<br/>SAML + SCIM"] --> TCO["TCO management account<br/>departments + SCPs"]
CC["Control Center<br/>landing zone"] --> TCO
TCO --> NETA["Network account<br/>CCN + DC gateway"]
TCO --> LOGA["Log archive account<br/>CloudAudit + COS/CLS"]
TCO --> WORK["Workload accounts<br/>VPC: CLB, CVM/TKE, CDB/TDSQL"]
WORK ---|"cross-account attach"| NETA
WORK -.->|"API events"| LOGA
NETA ---|"Direct Connect / VPN"| IDC["On-prem IDC"]
When It Fits¶
- Operating in mainland China, where Tencent has dense regions, finance-grade zones (Shanghai and Shenzhen finance zones), and MLPS compliance support, and you want one vendor for China and overseas.
- Southeast Asia and gaming/media workloads: game back ends, live streaming, and super-app patterns, which Tencent runs at scale internally (WeChat, WeChat Pay, games).
- Multi-cloud estates that need a Chinese provider alongside AWS, Azure, or Google Cloud.
- Less compelling when you need the broadest service catalogue, many regions outside Asia, or a large Western partner ecosystem.
Key Strengths¶
- Strong domestic footprint in China (Beijing, Shanghai, Guangzhou, Nanjing, Chengdu, Chongqing, plus finance zones)
- TDSQL: financial-grade distributed MySQL with strong sync replication (MAR). Tencent cites WeChat Pay-scale use (Tencent's TDSQL for MySQL product documentation states the service can sustain over 15 million QPS at peak: TDSQL for MySQL product PDF)
- CCN: managed transit network with automatic route learning, multiple route tables, MPLS-VPN isolation, and the first 5 Gbps of same-region bandwidth free
- Mature multi-account stack: TCO SCPs and tag policies, Identity Center with SCIM, and Control Center landing zones with an account factory
- Anti-DDoS Advanced (over 900 Gbps per node in China) and EdgeOne (Anycast edge security with a free plan)
- GAAP global acceleration (50+ nodes) for cross-border latency
- Expanding international footprint: Saudi Arabia (2025), Jakarta AZ-3 (2025), Frankfurt AZ-3 (Q2 2026), Johor Malaysia (2026-08), Osaka (announced for 2026)
Key Gaps (vs. AWS/Azure)¶
- Smaller footprint outside China and Asia (about 2% of the worldwide market)
- English documentation lags the Chinese docs. Some features and API parameter descriptions exist only in Chinese
- Smaller third-party ecosystem (marketplace, managed partner services)
- Inconsistent product naming (for example TDSQL-C was CynosDB, and the distributed TDSQL for MySQL uses the API
namespace
dcdb) - CloudAudit keeps only 90 days of event history natively. Long retention needs a tracking set to COS, CLS, or CKafka
- SDK region constants and third-party region lists lag new launches. Verify region IDs with
DescribeRegions
Licensing and Pricing¶
- Model: Pay-as-you-go (hourly), monthly/yearly subscription, and reserved-style discounts. Mainland China and international sites price separately.
- Network: CCN same-region bandwidth up to 5 Gbps is free. Cross-region traffic is billed by monthly 95th percentile with Platinum/Gold/Silver quality tiers. Hourly per-attachment and traffic-processing fees have applied since 2023-07-03. Cross-border (mainland China to overseas) links price separately. See Reference.
- Free tiers: Anti-DDoS Basic (2 Gbps), CloudAudit event history, EdgeOne Free plan.
- Tooling:
tccliand SDKs are Apache-2.0. The Terraform provider is MPL-2.0.
Recent Developments (2025-2026)¶
| Date | Development |
|---|---|
| 2025-02-10 | First Middle East region (Saudi Arabia) announced at LEAP 2025, two AZs, over USD 150M investment planned |
| 2025-04-15 | Osaka announced as Japan's third AZ, launch scheduled for 2026 |
| 2025 | Jakarta grows to three AZs |
| 2025-09-16 | Global Digital Ecosystem Summit: Agent Development Platform 3.0 available internationally, Hunyuan 3D models. Tencent said its overseas client base doubled in a year |
| 2025-12-10 | Terraform provider 1.82.44 adds Control Center account-factory baselines |
| 2026-03-02 | Frankfurt AZ-3 announced at MWC (customers from Q2 2026). Footprint 64 AZs / 22 regions |
| 2026-04-14 | Terraform provider 1.82.86 adds Config rules, compliance packs, and remediation |
| 2026-05-13 | Q1 2026 results: Business Services revenue up 20% YoY, driven by cloud and AI demand |
| 2026-08-18 | First Malaysian region in Johor. Two AZs live, a third planned. Footprint 66 AZs / 23 regions |
Alternatives and Comparisons¶
- Alibaba Cloud: the largest provider in mainland China, with a comparable multi-account and transit-network model (Resource Directory, CEN)
- AWS and Google Cloud: the hyperscalers most Tencent services map to (see the service-name mapping)
- Public Cloud Landing Zones: Tencent Cloud vs AWS vs Google Cloud vs Alibaba Cloud landing zones, hierarchy, network hubs and guardrails
- Infrastructure comparisons: all domain comparison pages
Topic Map¶
- How-to Guides: tccli and Terraform setup, organization and SCP setup, Identity Center, organization-wide audit, CCN hub, TKE, CDB, monitoring, troubleshooting
- Reference: tooling versions, region IDs, service-name mapping to AWS/GCP/Alibaba, TCO feature/API map, CAM policy elements, networking facts, security tiers, compliance facts
- Explanation: architecture patterns (single VPC, CCN, multi-account, multi-region, DR, perimeter, landing zone) and the security model
Related Topics¶
- Multi-Cloud Governance: identity federation, networking, and observability across providers, including Tencent CAM, DNSPod, and CLS
- Kubernetes: upstream concepts behind TKE
- Terraform and OpenTofu: the
tencentcloudprovider and the COS state backend
Sources¶
- Tencent Cloud Global Infrastructure
- Tencent Cloud Regions and Zones
- Frankfurt AZ-3 announcement (2026-03-02)
- Malaysia region announcement (2026-08-18)
- Saudi Arabia region announcement (2025-02)
- Osaka announcement (2025-04)
- Tencent global rollout of AI capabilities (2025-09-16)
- Tencent 2026 Q1 results
- Omdia: mainland China cloud spending Q4 2025
- Tencent Cloud Organization product page
- Tencent Cloud Organization (TCO), Thailand site
- Multi-Account Management
- TCO Identity Center introduction
- Control Center
- Tencent Cloud CAM Documentation
- Tencent Cloud VPC Documentation
- Tencent Cloud CCN Product Page
- CCN Billing Overview
- Tencent Cloud CLB Documentation
- CLB Cross-Region Binding 2.0
- TencentDB for MySQL (CDB)
- TDSQL for MySQL
- TDSQL-C Multi-AZ Overview
- COS Cross-Region Replication DR Architecture
- DTS Product Page
- GAAP Product Page
- CloudAudit Product Page
- Cloud Firewall Product Page
- Anti-DDoS Product Page
- WAF Product Page
- Tencent EdgeOne
- TKE Kubernetes version maintenance mechanism
- Tencent Cloud Compliance Center
- Tencent Cloud Products & Services Catalogue
- Terraform provider (tencentcloudstack/terraform-provider-tencentcloud)
- tccli (TencentCloud/tencentcloud-cli)
Questions¶
- How do TCO SCP condition keys and evaluation compare in detail with Alibaba Cloud Resource Directory control policies? (Allow-list model and inherited deny are confirmed, see Explanation.)
- Which Control Center landing-zone steps still have no API or Terraform equivalent? As of provider 1.83.33 only
the account-factory baseline is exposed as a
controlcenterresource. TCO, Identity Center, SCPs, and CCN are fully covered. - How does TDSQL strong-sync replication (MAR) behave above 50 ms RTT, and how does it compare with Alibaba PolarDB-X in a similar active-active topology?
- What are the region IDs and AZ counts for Saudi Arabia, Johor, and Osaka? Is Osaka live? Are Mumbai and Moscow still open to new customers?