Does Sauce Labs Work in China? Data Residency, ICP & Cross-Border Rules

A Sauce Labs test run executes your app build and test code, and stores each run's screenshots, videos and logs, on its hosted cloud in the US, EU or APAC — no mainland-China region, not self-hosted. For China users that is offshore data under PIPL; an in-country grid is the lever.

By the 21YunBox Compliance Team · Reviewed 2026-10-13 · Verified against Sauce Labs's own documentation

Does Sauce Labs work in China?

Sauce Labs is reachable from China, but that was never the real question — when you run a test on Sauce Labs, your application build, your test code, your (often production-like) test data, and the screenshots, videos and logs of each run execute on and are stored in Sauce Labs' own data centers abroad. Sauce Labs is a hosted test cloud: its documentation says the data center you pick determines “the location of the servers where your tests are run” and “where related artifacts are stored,” and its regions are US West, US East, EU Central and Asia South — there is no mainland-China region, and it is not a self-hosted product. So for a China-facing app, your proprietary build and any personal information inside your fixtures and recordings leave the country the moment a run starts — a PIPL cross-border transfer, with a data-localization duty an offshore-only cloud cannot meet.

Making the cloud merely reachable does not move any of that in-country, and it does not create the transfer basis PIPL requires. The lawful path is to keep the browser-and-device grid and the test execution inside the mainland: 21YunBox stands up a self-hosted, in-country test grid — an open-source Selenium/Appium grid or self-hosted runners in your own in-country CI — so your application build, test data and run artifacts stay resident, with only what is lawful to export sent offshore. We never use or suggest circumvention of any kind. Treat the specifics as a risk to confirm with counsel.

What Sauce Labs's own documentation says about China

Fact	Primary source
Sauce Labs runs your tests on servers in a data center you select, and stores the run artifacts there. Its documentation states the data center you use “determines: The location of the servers where your tests are run” and “Where related artifacts are stored,” and lists the region options as US West 1, US East 4, EU Central 1 and Asia South 2 — no mainland-China region appears.	Sauce Labs Docs, “Data Center Endpoints” (docs.saucelabs.com), retrieved 2026-10-13
Sauce Labs is a hosted cloud that runs and maintains the test infrastructure for you. Sauce Labs describes a “cloud-based continuous testing platform” and states: “We support and maintain your test infrastructure in the cloud so you don't have to.” Execution happens on Sauce Labs' infrastructure, not on servers you run, so your application build, test data and recordings sit wherever that cloud is hosted.	Sauce Labs, “Cross Browser Testing” (saucelabs.com), retrieved 2026-10-13
Sending a mainland user's personal data offshore to run a test is a regulated cross-border transfer. Test fixtures and run recordings routinely carry personal information — names, emails and account records rendered on screen. Under PIPL (Articles 38–40), exporting it requires notice, a separate consent distinct from the service agreement, and a transfer mechanism: a CAC security assessment, the CAC standard contract, or certification.	Personal Information Protection Law of the PRC, Articles 38–40 — 21YunBox cross-border overview, retrieved 2026-10-13
For a critical information infrastructure operator, mainland-collected personal data must stay in China. China's Cybersecurity Law, Article 39 (formerly Article 37), requires in-country storage of personal information and important data collected and generated in the mainland by a CII operator — a residency duty an offshore-only test cloud with no mainland-China region cannot satisfy.	Cybersecurity Law of the PRC, Article 39 (formerly Article 37) — 21YunBox overview, retrieved 2026-10-13

Sources verified by the 21YunBox compliance team on 2026-10-13.

Ask whether Sauce Labs “works” in mainland China and the honest answer does not start with whether the dashboard opens from Shanghai. A test run is not a page view: it exercises your application build — your proprietary front-end and back-end code — runs your test code, feeds in test data and fixtures that are routinely production-like (real-looking names, emails and payment fields, sometimes copies of real records), and produces artifacts: the screenshots and video recordings that capture your app rendering that data, plus the console and network logs. Sauce Labs is a hosted test cloud, so all of that is uploaded to and executed on Sauce Labs’ own servers abroad. Whether the run can reach Sauce Labs is the least of what you are deciding; where your build, your fixtures and your recordings live while the run happens is the decision.

Sauce Labs documentation page stating that the data center you use determines the location of the servers where your tests are run and where related artifacts are stored, with region options listed as US West 1, US East 4, EU Central 1 and Asia South 2 and no mainland-China region — Sauce Labs' own documentation ties the test run to a chosen data center: “The data center you use with Sauce Labs determines: The location of the servers where your tests are run” and “Where related artifacts are stored.” The region options it lists are US West 1, US East 4, EU Central 1 and Asia South 2 — there is no mainland-China region. Source: docs.saucelabs.com — Data Center Endpoints

Sauce Labs in China at a glance

What decides it	In Sauce Labs' own terms
Where it runs	A hosted cloud. Sauce Labs says “We support and maintain your test infrastructure in the cloud so you don't have to,” and its docs state the data center you use “determines: The location of the servers where your tests are run.” The run executes on Sauce Labs' servers, not on hardware you control.
Which regions	Sauce Labs' documented data centers are US West 1, US East 4, EU Central 1 and Asia South 2. No region is inside mainland China, and switching from one offshore region to another (US to EU) never makes the data resident in China.
What rides along	Each run carries your application build and your test code, and feeds in fixtures that are routinely production-like — real-looking names, emails and payment fields, sometimes copies of real records — so personal information travels inside the test data itself.
What the run leaves behind	Artifacts. Sauce Labs' docs state the data center also determines “Where related artifacts are stored” — the screenshots and videos that record your app rendering that data, plus console and network logs. Those recordings are held in the offshore data center.
A self-hosted, in-country option?	Sauce Labs is a hosted service with no mainland-China region and no first-party self-hosted edition you can run inside the mainland. Keeping execution in-country therefore means running the grid yourself, not reconfiguring Sauce Labs. Confirm current options with Sauce Labs before relying on one.
Is it reachable?	Whether the Sauce Labs cloud opens cleanly for a mainland network is a delivery question — separate from, and lesser than, whether you are cleared to execute your build and hold this test data and these recordings offshore at all.

Where Sauce Labs runs — and that settles the first question

Sauce Labs is hosted software, and it names where the work happens. It describes a “cloud-based continuous testing platform” and tells customers “We support and maintain your test infrastructure in the cloud so you don’t have to.” Its documentation is just as explicit about location: the data center you use “determines: The location of the servers where your tests are run” and “Where related artifacts are stored,” with the region options listed as US West 1, US East 4, EU Central 1 and Asia South 2. There is no mainland-China region. So wherever your engineers sit, the moment a run starts your application build is executed, and your test data and recordings are stored, on servers outside the mainland. That single fact decides the compliance question before reachability is ever measured: this is not about whether the dashboard paints in Shanghai, it is about your code and your data leaving the country the instant a test runs.

The second half a reachability probe never sees — your build, your data, your recordings

A connectivity check stops at “can the run start.” It cannot see the three things that actually cross the border. First, your application build — proprietary source compiled into the app under test — is uploaded to and executed on Sauce Labs’ offshore servers. Second, your test data and fixtures, which in real pipelines mirror production: names, emails, phone numbers and payment fields, sometimes seeded from real records, all of it personal information once it describes people in China. Third, the artifacts — Sauce Labs stores the screenshots and videos of each run, which capture your app rendering exactly that data, alongside console and network logs that can contain tokens, identifiers and payloads. When people in China are in your test data, moving it out of the country to run the test engages the Personal Information Protection Law: notice, a separate consent, and one cleared cross-border transfer mechanism (a CAC security assessment, the CAC standard contract, or certification), under PIPL Articles 13/23 and 38–40. If you are a critical information infrastructure operator, personal information and important data collected in the mainland must be stored there (Cybersecurity Law Article 39 (formerly Article 37)) — a residency requirement an offshore-only test cloud cannot satisfy. A competitor’s “it loads fine from China” chart shows none of this.

Why a reachability check misses all of this

A test that only asks “does the Sauce Labs cloud respond from Shanghai?” measures the wrong thing. It cannot see that your application build is executed on servers in the US, EU or APAC, it cannot see the personal information riding inside your fixtures, and it cannot see that the screenshots, videos and logs of each run are stored in those same offshore data centers. Making the cloud merely reachable does not move any of the regulated data in-country, and it does not create the transfer basis PIPL requires — nor the ICP filing a China-facing app needs on top. Reaching Sauce Labs and being cleared to execute your build and hold your users’ data offshore are two different tests, and only one of them shows up on a latency chart.

Where 21YunBox fits — map, localize, deliver

We do not ask you to abandon your test suite. We add the layer a hosted, offshore test cloud cannot. Map: we inventory which of your test runs carry proprietary application code, which fixtures hold production-like or real personal data, and where the execution and the screenshots, videos and logs actually live — separating the offshore hosted-cloud runs from what you can run yourself. Localize: we keep the browser and device grid and the test execution inside the mainland — a self-hosted open-source Selenium/Appium grid, or self-hosted runners in your own in-country CI — so your application build, your test data and your run artifacts stay resident, and only what is lawful to export is sent abroad. Deliver: 21YunBox stands up that compliant, in-country test grid in front of (or in place of) the offshore cloud, with your existing scripts running unchanged — no rebuild, no second codebase. 21YunBox never uses or suggests circumvention of any kind.

This is a risk map, not a verdict: whether you owe notice and consent, a transfer mechanism, in-country storage, an ICP filing, or some combination depends on your entity, your data volumes and what your fixtures and recordings carry — worth settling with counsel before you point China-facing testing at an offshore cloud.

Get a compliance assessment →

Related reading:

Frequently Asked Questions

Does Sauce Labs work in China?

It is reachable, but reachability is not the deciding question. When you run a test on Sauce Labs, your application build, your test code, your (often production-like) test data and the screenshots, videos and logs of each run execute on and are stored in Sauce Labs' hosted cloud — US West, US East, EU Central or Asia South, with no mainland-China region and no self-hosted edition. For a China-facing app that puts your proprietary build and any personal data in your fixtures and recordings offshore, which engages PIPL cross-border and data-localization rules. The fix is not to make the cloud reachable; it is to keep the test grid and execution in-country. Confirm your exact obligations with counsel.

Why isn't "the test can reach Sauce Labs" enough?

Because a reachability check only asks whether the run can start — it never sees where your application build, your test fixtures and your run recordings live while and after the test executes. On a hosted test cloud those sit on the vendor's offshore servers by design. The regulated questions are whether the personal data in your fixtures and the app data captured in screenshots and videos may leave China at all, whether you have notice, a separate consent and a transfer mechanism, and whether an in-country storage duty applies. None of that shows up on a latency chart.

How can I keep test execution in-country while keeping my suite, and what does 21YunBox do?

Run the browser-and-device grid inside the mainland rather than on an offshore cloud. 21YunBox maps which of your test runs carry proprietary code or personal-data-bearing fixtures and where their artifacts land, then stands up a self-hosted, in-country test grid — an open-source Selenium/Appium grid or self-hosted runners in your own in-country CI — so the application build, test data and recordings stay resident, with only what is lawful to export sent offshore. Your existing test scripts keep working, with no rebuild. We never use or suggest circumvention of any kind. Get in touch to map your case.