Does VMware vSphere Work in China? Self-Hosted, So ICP & Data Residency Are Yours
VMware vSphere (now a Broadcom product) is software you install on your own servers, so you can run it inside mainland China and keep data in-country — but the ICP filing and PIPL data-residency posture shift to you, not the vendor. A compliance-first look at the self-host case.
Does VMware vSphere work in China?
Yes — and unlike most of these questions, this is not a flat no. VMware vSphere (now a Broadcom product) is software you install on your own servers, so you can run it inside mainland China and keep your data there. What vSphere does not do is carry the compliance work for you — the ICP filing and the data-residency posture move onto you.
In Broadcom's own licensing an "Instance" is "a single installation of the Software on a physical server or Virtual Machine," and a customer "must not … use or deploy the Software on any Cloud Services" — this is software you deploy, not a service someone hosts offshore. So where it runs is your decision: put the hosts in the mainland and personal data can stay in-country, but any public website those VMs serve still needs an ICP filing you obtain, and any personal information a workload moves out of the mainland is a cross-border transfer PIPL governs. The table below is Broadcom's own wording and the rule each choice triggers.
This is a risk map, not a verdict — whether you need an ICP filing, in-country storage, or both turns on what you serve, how much personal data you hold, and who your users are. Our China team can map your exposure with you →
Compliance snapshot
- ✓ vSphere is software you run on your own servers — you can deploy the hosts in mainland China
- ✓ Keep the hosts in-country and your data can stay in the mainland
- ! The ICP filing for any public site those VMs serve is yours to obtain
- ! Personal data a workload sends offshore is a PIPL cross-border transfer
- ! vSphere gives you the servers, not the ICP filing or compliant in-country delivery
What Vmware Vsphere's own documentation says about China
| Fact | Primary source |
|---|---|
| vSphere is software you install on your own servers, not a service someone hosts for you. In Broadcom's own licensing an "Instance" is "a single installation of the Software on a physical server or Virtual Machine," and a customer "must not … use or deploy the Software on any Cloud Services." So where vSphere runs — and therefore where your data sits — is your decision, not the vendor's: unlike an offshore SaaS, nothing in the product pushes your users' data across a border. | Broadcom — VMware vSphere Standard, Specific Program Documentation (ftpdocs.broadcom.com), retrieved 2026-10-07 |
| Because the hosts are yours, you can keep Chinese users' data in the mainland — the residency posture is yours to set. vSphere runs wherever you place the hardware, so deploying the servers inside mainland China can satisfy the data-localization duty that falls on critical information infrastructure operators and large-volume handlers (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)). Run the same workloads offshore and that advantage disappears — the software does not decide residency, your deployment does. | Broadcom — VMware vSphere Standard SPD (ftpdocs.broadcom.com), retrieved 2026-10-07; PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37) |
| The ICP filing for any public site those VMs serve is still yours to obtain. Broadcom's terms let a customer "use the Software to deliver Internally Developed Applications as a service to a third party via an internal or external network" — which makes you the operator of that service. A public-facing website delivered to mainland visitors turns on an ICP filing tied to a mainland hosting resource (State Council Order No. 292; MIIT Order No. 33), and vSphere supplies the server, not the filing. | Broadcom — VMware vSphere Standard SPD (ftpdocs.broadcom.com), retrieved 2026-10-07; State Council Order No. 292; MIIT Order No. 33 |
| vSphere is now a Broadcom product, and what it hands you is infrastructure — not a China compliance position. The license is issued by "the Broadcom entity," and vCenter Server provides "centralized management capabilities to any licensed VMware by Broadcom infrastructure environments." It is your infrastructure to run; the ICP filing, the PIPL transfer mechanism and the in-country public delivery a lawful mainland presence needs all sit outside the software, with you. | Broadcom — VMware vSphere Standard SPD (VMware by Broadcom; ftpdocs.broadcom.com), retrieved 2026-10-07 |
Sources verified by the 21YunBox compliance team on 2026-10-07.
For a mainland-China audience, VMware vSphere raises a different question than a hosted service does. vSphere — the virtualization and private-cloud software that VMware, now part of Broadcom, licenses for you to install and run on your own servers — is not something you reach across the border; it is something you operate. So the deciding issue is not whether a foreign endpoint loads. It is who carries the compliance work once those servers are yours: the ICP filing for anything public they serve, and the data-residency posture for the personal information your workloads hold. The honest answer is that vSphere can be run compliantly inside the mainland — because you choose where the hardware sits — but the licensing and data obligations do not ship with the software; they come with you.
VMware vSphere in China at a glance
| What decides it | In Broadcom's own terms |
|---|---|
| Where it runs | On hardware you control. vSphere is software you install — an “Instance” is “a single installation of the Software on a physical server or Virtual Machine,” and the license bars deploying it “on any Cloud Services.” You pick the servers, and they can sit inside mainland China. |
| Who sets data residency | You do. Because the hosts are yours, personal data lives wherever you place them; nothing in vSphere forces it across a border. Keep the servers in-country and the data can stay in the mainland. |
| Serving the public | A public website those VMs serve needs an ICP filing tied to a mainland hosting resource (State Council Order No. 292; MIIT Order No. 33). vSphere provides the server; the filing is yours to obtain. |
| Cross-border data | Any personal information a workload moves out of the mainland is a cross-border transfer under PIPL (Articles 38–43); the localization duty for CIIOs and large-volume handlers (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)) is met only if the hosts stay in-country. |
| Is it reachable? | You run the hosts, so reachability follows where you deploy them — offshore servers are reached across the border like any foreign origin, in-country servers are local. Either way, compliance turns on licensing and data posture, not on whether an endpoint loads. |
Software you run, not a service you reach
vSphere is the virtualization layer enterprises build private clouds on: the ESXi hypervisor installed on each physical server, with vCenter Server providing “centralized management capabilities to any licensed VMware by Broadcom infrastructure environments.” Broadcom’s licensing makes the deployment model explicit — an “Instance” is “a single installation of the Software on a physical server or Virtual Machine,” and a customer “must not … use or deploy the Software on any Cloud Services.” In other words, this is software you put on hardware you control, not an endpoint hosted for you somewhere offshore. That single fact is what separates vSphere from a foreign SaaS: with a SaaS, the vendor’s region decides where your data lives; with vSphere, you decide, because the servers are yours — and they can sit inside mainland China.
The compliance work doesn’t disappear — it moves to you
Running your own servers takes the vendor’s location out of the equation, but it does not take away China’s two gates; it hands them to you. A public-facing website served to mainland visitors turns on an ICP filing (ICP 备案) under State Council Order No. 292 and MIIT Order No. 33, attached to a mainland hosting resource — and Broadcom’s terms, which let you “use the Software to deliver Internally Developed Applications as a service to a third party via an internal or external network,” make you the operator who must hold that filing. Separately, the personal information your workloads collect from Chinese users is governed by China’s Personal Information Protection Law: move it out of the mainland and you have a cross-border transfer requiring notice, separate consent and a transfer mechanism (Articles 38–43); hold it as a critical information infrastructure operator or at large volume and it must be stored in the mainland (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)). vSphere gives you the freedom to meet both — it does not meet them for you.
Running the hosts in mainland China: what it settles, and what it doesn’t
Deploy your ESXi hosts inside the mainland and two things fall into place: your users’ data can stay in-country, and the servers are reached locally rather than across the border. What is still open is the paperwork and the delivery. You, as operator, must obtain the ICP filing for any public site those VMs serve; any workload that still calls an offshore service puts personal data back across the border under PIPL; and standing up lawful, in-country public delivery in front of those hosts is operational work the hypervisor does not perform. So “we run vSphere” answers the hardware question honestly — yes, you can be in-country — while leaving the licensing and delivery questions exactly where China’s law puts them: with the operator.
This is a risk map, not a verdict: whether you need an ICP filing, in-country storage, or both depends on what you serve, how much personal data you hold, and who your users are — worth settling with counsel before you build.
Where 21YunBox fits — a compliant overlay, not a migration
You keep running vSphere exactly where you run it today. We add the pieces the hypervisor was never meant to supply: compliant, ICP-filed delivery from inside the mainland, set in front of your existing vSphere origin — no rebuild, no second codebase, and no move off your own servers. Our China team maps your ICP and data-residency obligations against your entity, your workloads and your data volumes, then stands up the in-country delivery a lawful public presence needs, while your virtualized estate stays precisely where you built it.
Related reading:
Frequently Asked Questions
Can we just run vSphere on servers in mainland China and be compliant?
You can run it in-country — that settles where the software and the data sit, which is the part an offshore service cannot offer. But compliance is not only location. A public-facing site those VMs serve needs an ICP filing tied to a mainland hosting resource (State Council Order No. 292; MIIT Order No. 33), and any personal data that leaves the mainland is a cross-border transfer under PIPL. vSphere gives you the hardware freedom; the filings and transfer mechanisms are yours. Treat it as a risk to map with counsel, not a box the software ticks.
Does moving to vSphere remove our China data-residency problem?
Only if you deploy the hosts inside the mainland. vSphere imposes no offshore region — in Broadcom's words an "Instance" is "a single installation of the Software on a physical server," and that server sits wherever you put it. Place the servers in mainland China and personal data can stay in-country (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)). Run them offshore and you are back to a cross-border transfer under PIPL. The software does not decide residency; your deployment does.
Can 21YunBox help make our vSphere setup work in China?
Yes. Our China team can map which obligations apply — assessing your PIPL cross-border and data-residency exposure for your entity, workloads and data volumes — and stand up the ICP-filed, in-country delivery a compliant public presence requires, in front of the vSphere estate you already run. Get in touch to work through your specific case.
