Zoom China — keep HQ Zoom or remap meetings

Zoom China is Unavailable as Plan A for Mainland China meetings and Zoom SDK embed. Landscape labels Zoom SDK Unavailable (or extremely unstable): Zoom stopped offering direct Mainland China service, and there is no China data-center path. Keep Zoom for HQ / export-only. Remap China-facing meetings and any Zoom SDK in a product to Tencent Meeting or Feishu Meeting. This is the same Unavailable class — not a working Zoom China SKU. Microsoft Teams is a different verdict (Limited); pair, do not merge: Microsoft Teams in China.

What Zoom in China actually is

Hard names your stack decision will use:

• Zoom — Zoom Meetings for hosts and participants, plus developer embed: Meeting SDK (Zoom client inside your app or site) and Video SDK (custom session UI on Zoom media). Default infrastructure is Zoom’s global cloud — not a Mainland China termination you can treat as Plan A.
• Zoom China / zoom in China — That same product as seen from Mainland China. Landscape’s operating label is Unavailable: Zoom stopped offering direct Mainland China service; there is no China data-center path. A join that works from HQ is not a China launch.
• Two surfaces, one class — (1) Zoom China app / zoom meeting china for users who open Zoom. (2) Zoom SDK in a product. Same Unavailable class. Do not split them into “the app is blocked, the SDK is fine.”
• Usual remap — Tencent Meeting when the job sits in a WeCom ecosystem; Feishu Meeting when the job is Feishu docs, calendar, and knowledge capture (Feishu Meeting APIs). Landscape holds that shortlist — confirm SDK fit before production.
• Teams is a pair, not a merge — Microsoft Teams is Limited, not Unavailable. Keep-HQ-plus-China-suite is a Teams pattern. It does not make Zoom available. Depth: Microsoft Teams in China.
• Not a WeChat Official Account — A WeChat Official Account is a broadcast / menu channel. It is not the meeting SKU. WeChat marketing vs meetings is a different order: WeChat marketing in China.
• Not an acceleration SKU — Putting a CDN, “Zoom streaming,” or timeout-then-retry in front of Zoom does not create a China data-center path. Chatty real-time media still pays the border — same class as SaaS performance in China.

Vocabulary first. Next: what must be true before Zoom stays in scope at all.

What must be true before Zoom stays in scope

Missing a clear keep-vs-remap job stops your product team before another “make Zoom work in China” sprint is real work.

Precondition	Why your process stalls
Job locked — HQ / export-only vs ordinary Mainland China users on the meeting or SDK path	A Tencent / Feishu remap is staffed while Zoom could stay capped — or Zoom stays Plan A for China users
Surface named — Zoom China app / zoom meeting china vs Zoom Meeting SDK / Video SDK in a product	The app is remapped while the in-product SDK still calls Zoom, or the reverse
Honest join inventory — who hosts, who joins from Mainland China, which clients (desktop, mobile, in-app webview)	“We joined from HQ” still leaves China users on an Unavailable path
Remap named if China users are the job — Tencent Meeting (WeCom-ecosystem) vs Feishu Meeting (docs / knowledge job)	Teams pick both, or neither, and still call it a Zoom China launch
Mainland China vantage proof on join and SDK media — broadband + mobile; HQ laptop is not proof	Overseas QA “passes” while China users drop audio or never connect
WOA / WeChat channel ≠ meeting	An Official Account sprint is reported as the Zoom replacement

Product teams usually cannot treat “ship the same Zoom tenant globally” as the Mainland China plan. Naming keep vs remap is the floor. SKU orientation lives on Zoom SDK alternatives.

Keep Zoom capped or remap China meetings

Stage	Decision / outcome
1. Name the job	Ordinary Mainland China users on the meeting / SDK path, or HQ / export-only?
2. If HQ / export-only	Keep Zoom as a capped architecture. Do not market zoom meeting china as a China launch
3. If China users are the job	Rule Zoom (app and SDK) out as Plan A. Remap to Tencent Meeting or Feishu Meeting
4. Pick the remap	Tencent Meeting when WeCom / Tencent-docs gravity is the job; Feishu Meeting when Feishu docs, tasks, and knowledge capture are the job
5. Inventory both surfaces	Zoom China app and Zoom SDK embed. One leftover Zoom hop still fails the journey — SaaS performance in China
6. Prove from Mainland China	Broadband + mobile on join and in-app media (or China Network Diagnostics). HQ laptop is not proof
7. Cut over, then re-test	China-facing calendar, links, and SDK point at the remapped product. Keep Zoom residual off that path

Hard gate — keep capped vs remap

Necessity: confusing these two jobs wastes the quarter — either you underfund a China meeting stack, or you rip Zoom out of HQ when China users were never the critical path.

Job	Zoom role	What must already be true
HQ / export-only	Plan A, capped	China users are not the critical path; Zoom China limits are named
Ordinary Mainland China users	Not Plan A	Tencent Meeting or Feishu Meeting named; app and SDK remapped or dropped
In-product video (SDK)	Same Unavailable class	Meeting SDK / Video SDK treated as Zoom infrastructure, not a China SKU
“CDN the Zoom tenant”	Myth as Mainland China plan	Real-time media reachability from the user network — not an HTML cache

Hard gate — Zoom China app is not a China SKU

There is no working Zoom China product to buy for ordinary Mainland China users. A localized client name, a partner-era story, or a join that sometimes completes is still Unavailable as Plan A. Hong Kong / Tokyo / Singapore ≠ Mainland China.

Why Zoom join and Zoom SDK stall the same way

Engineering constraints you must design around:

Constraint	What breaks	What to do
No China data-center path	Landscape labels Zoom SDK Unavailable. Cross-border media has no in-country Zoom termination to fail over to.	Keep Zoom capped, or remap. Do not treat “try Zoom, then a China meeting app on timeout” as Plan A.
Direct Mainland China service stopped	New China-facing seats, billing, and support do not sit on a Zoom-operated Mainland China SKU.	Stop staffing a Zoom China commercial path. Fund Tencent Meeting or Feishu Meeting instead.
App and SDK share infrastructure	Meeting SDK uses the same global Zoom connection class as the client. Swapping the wrapper does not move media onshore.	Remap both surfaces. An in-app Zoom window is still Zoom.
HQ join ≠ China join	Hosts outside Mainland China start a meeting; China users join late, mute, or drop. Testers never see it.	Prove from Mainland China broadband and mobile. Same honesty as other overseas SaaS — SaaS performance in China.
Teams Limited pasted onto Zoom	Product copies a keep-HQ Teams pattern and reports Zoom as Limited.	Different verdict. Pair Microsoft Teams in China; do not merge.
WOA used as the meeting	Broadcasts and menus ship; live meetings still sit on Zoom.	Keep WeChat Official Account as a channel. Meetings remap separately.

A 200 on zoom.us ≠ Zoom China. A US/EU meeting with a China marketing calendar invite is still a capped overseas architecture.

HQ laptop QA → false confidence. Testers outside Mainland China never see the stall, so the ticket never opens.

SDK wrapper reported as a China meeting product → wrong stack. Meeting SDK inside your app is still Zoom media.

CDN without remap → partial win. Faster HTML around a join page does not move real-time audio and video onshore.

What stalls teams that treat Zoom as a China SKU

• Yes/no SKU thinking — Product treats “Does Zoom work?” as a geo toggle before keep vs remap is named. Landscape Unavailable is an operating signal, not a launch.
• Zoom China app as a secret SKU — A client download is confused with a China data-center product.
• SDK split from the app — Engineering remaps the meeting link and leaves Video SDK on Zoom, or the reverse.
• Teams playbook pasted on Zoom — Limited is copied onto an Unavailable product. Pair the Teams Guide; do not merge.
• WeChat Official Account as the meeting — Channel work is reported as the Zoom replacement.
• Acceleration as Plan A — A CDN or “optimize Zoom streaming” sprint is staffed while media still terminates on Zoom.
• HQ laptop QA — Green screenshots from outside Mainland China close the ticket.
• Hong Kong conflated with Mainland China — Regional join quality is reported as Zoom China launched.
• No owner for the remap — The fork stalls because nobody owns app vs SDK vs calendar vs in-product embed — only “make Zoom work in China.”

What “fixed” means: Mainland China users can complete the meetings and in-product video journeys you claim on Tencent Meeting or Feishu Meeting; Zoom is named and capped for HQ / export-only if it remains; Zoom SDK is gone from the China client path; WeChat Official Account is not counted as the meeting SKU; proof is from Mainland China broadband and mobile. Zoom with a China marketing claim is not fixed.

China landing partner when Zoom is still Plan A

Most product teams exploring Mainland China entry need a China landing partner once they stop treating Zoom as Plan A — to stand up Tencent Meeting or Feishu Meeting with the right WeCom or Feishu tenancy, remap Zoom SDK embed, run Mandarin admin consoles, and prove join quality from Mainland China broadband and mobile. Your team still owns whether Zoom stays for HQ / export-only, which meeting surfaces remap, and which residual overseas line to keep; the partner path makes that remap executable when those rails are not already in-house. Keeping a capped Zoom line for outside-Mainland China viewers does not remove the need for that China landing partner on the primary China path.

What we can offer?

Zoom China work for Mainland China is a keep-capped vs remap decision before any “keep the same Zoom tenant globally” sprint. Chinaready helps your product team cap Zoom where it belongs — or remap meetings and SDK onto rails that Mainland China users can actually join:

1. China Readiness Assessment — Decide whether Zoom stays capped for HQ / export-only, which Zoom China app vs Zoom SDK hops sit on the critical path, and whether Tencent Meeting or Feishu Meeting is the remap before a launch date.
2. China Access Acceleration — Keep China-facing join pages and leftover hosts reachable from Mainland China vantage so a remapped meeting product does not die on a Zoom link, SDK host, or overseas calendar asset.
3. China Product Hosting — Place the China-critical product that embeds meetings where entity consistency and a China-reachable origin stay coherent after Zoom SDK leaves that path.
4. Mobile App Distribution — Align any China app that still wraps Zoom Meeting SDK or Video SDK with the same remap — not mistake a global Zoom embed for a China meeting plan.

Contact us when you need a Zoom China keep-capped or remap path before you staff another Zoom-in-China sprint.