Why 21YunBox Pricing Contact Log in
Talk to an expert Test your site in China

Does SolarWinds Work in China? Self-Hosted vs SaaS Data Residency

SolarWinds splits two ways in China: the self-hosted platform installs behind your own firewall, so it can sit on in-country servers, while SolarWinds Observability SaaS stores your monitoring data in offshore regions — North America, Frankfurt and Australia, never the mainland. When that telemetry carries IP addresses, emails and computer names, sending it offshore is a PIPL cross-border transfer. A compliance-first look at which door fits.

Does SolarWinds work in China?

It depends which SolarWinds you run. The self-hosted platform installs behind your own firewall, so you can place it on in-country servers; SolarWinds Observability SaaS stores your monitoring data in offshore regions — North America, Frankfurt and Australia, never the mainland — and that telemetry is not anonymous.

SolarWinds's own documentation says the SaaS "is deployed across multiple data centers spanning various global regions and cloud providers," and lists four — none inside mainland China. Its privacy notice adds that the data your agents ship "may also include event logs, end user information (such as IP address, email address and computer name)." Send that from Chinese users to a SolarWinds region and you have made a cross-border transfer of personal information PIPL governs; keep it on a self-hosted install and SolarWinds says "the Customer is in control of their own product data," free to "decide how, where, and under which conditions their data is stored." Either way SolarWinds is a "processor," so the duty is yours. The table below is SolarWinds's own wording and the rule each path triggers.

This is a risk map, not a verdict — which path fits turns on your entity, your data and who your users are. Our China team can map your SaaS-versus-self-hosted exposure with you →

Compliance snapshot

  • ! SolarWinds Observability SaaS stores your data offshore — no region in mainland China
  • ✓ Self-hosted SolarWinds installs behind your firewall — it can sit on in-country servers
  • ! Monitoring data isn't anonymous — event logs carry IPs, emails and computer names
  • ! China telemetry sent to the SaaS is a PIPL cross-border transfer you're responsible for
  • ! No ICP attaches to SolarWinds — but the mainland app it monitors still needs one
Get a compliance assessment
We'll map SaaS vs self-hosted residency and your PIPL exposure with you

What Solarwinds's own documentation says about China

FactPrimary source
SolarWinds Observability SaaS runs only in offshore regions — none in mainland China. SolarWinds's own documentation states the SaaS "is deployed across multiple data centers spanning various global regions and cloud providers," and lists exactly four sites: a "North American AWS data center," a "North American Azure data center," a "European (Frankfurt) AWS data center" and an "Australia AWS data center." You pick one when you create an organization — by proximity or, in SolarWinds's words, "whether you prefer your data is hosted in AWS or Azure" — and the mainland is not on the list. SolarWinds Observability SaaS — Data centers and endpoint URIs (documentation.solarwinds.com), retrieved 2026-10-07
Your monitoring data isn't anonymous — and shipping it to a SolarWinds region is a cross-border transfer. SolarWinds states its Customer Data covers data from "the end points and other systems, tools, or devices that Customers manage or monitor," and "may also include event logs, end user information (such as IP address, email address and computer name)." Send that from Chinese users or systems to an offshore SolarWinds SaaS region and you have made a cross-border transfer of personal information under PIPL — notice, separate consent and a transfer mechanism (Articles 38–43). SolarWinds Privacy Notice (solarwinds.com/legal/privacy), retrieved 2026-10-07; PIPL Articles 38–43
Self-hosted SolarWinds can sit on in-country infrastructure — so the verdict is not a flat "no." SolarWinds describes Observability Self-Hosted (formerly Hybrid Cloud Observability) as a platform that "runs behind your firewall" "without moving sensitive operational data to a vendor-managed cloud." Its privacy notice adds that for an on-premises deployment "the Customer is in control of their own product data," and that "by keeping their software and product data on their infrastructure," customers "can decide how, where, and under which conditions their data is stored." Put those servers in the mainland and the monitoring data can stay there. SolarWinds — Observability Self-Hosted product page & Privacy Notice (solarwinds.com), retrieved 2026-10-07
SolarWinds is a "processor" — the compliance duty is yours, not SolarWinds's. For its SaaS products SolarWinds states "we are a 'processor' or 'service provider' for Customer Data," which "is owned and controlled by our Customers," and that "our Customers' respective privacy policies apply to and govern the processing of Customer Data, not this Privacy Policy." So the PIPL cross-border and data-localization calls sit with you: if you are a CIIO or large-volume handler, personal information collected in China must be stored in the mainland (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)). SolarWinds Privacy Notice (solarwinds.com/legal/privacy), retrieved 2026-10-07; PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)
No ICP filing attaches to SolarWinds itself — it does to the app you monitor. SolarWinds is backend monitoring; there is no public SolarWinds page your end users load, so ICP filing (ICP 备案, State Council Order No. 292 and MIIT Order No. 33) does not attach to SolarWinds in either its SaaS or self-hosted form. That obligation belongs to the mainland-facing website or application you point the agents at. SolarWinds's own exposure is residency, not licensing. SolarWinds product documentation (solarwinds.com), retrieved 2026-10-07; State Council Order No. 292; MIIT Order No. 33

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

For a mainland-China audience, the deciding question about SolarWinds is not how quickly its dashboards paint — it is where your monitoring data is allowed to live, and that answer splits by which SolarWinds you run. The self-hosted platform installs behind your own firewall, so you can put it on servers inside the mainland and keep the data there. SolarWinds Observability SaaS does the opposite: it stores what your agents ship in offshore regions — North America, Frankfurt and Australia — with no mainland-China site, and that telemetry is not anonymous. So the exposure is not reachability; it is residency, and it turns on the model you choose.

SolarWinds Observability SaaS documentation page titled Data centers and endpoint URIs, listing a North American AWS data center, a North American Azure data center, a European (Frankfurt) AWS data center and an Australia AWS data center — with no mainland-China data center
SolarWinds's own data-center documentation: SolarWinds Observability SaaS “is deployed across multiple data centers spanning various global regions and cloud providers” — a North American AWS site, a North American Azure site, a European (Frankfurt) AWS site and an Australia AWS site, none inside mainland China. Source: documentation.solarwinds.com/.../endpoints

SolarWinds in China at a glance

What decides it In SolarWinds's own terms
Where the SaaS runs Four data centers — a “North American AWS data center,” a “North American Azure data center,” a “European (Frankfurt) AWS data center” and an “Australia AWS data center.” You pick one when you create an organization. None is inside mainland China; the nearest, Australia, is still offshore.
The self-hosted option SolarWinds Observability Self-Hosted (formerly Hybrid Cloud Observability) “runs behind your firewall” “without moving sensitive operational data to a vendor-managed cloud” — so it can be installed on servers inside the mainland.
What it ingests Metrics, events, logs and traces from the systems you monitor. SolarWinds: its Customer Data “may also include event logs, end user information (such as IP address, email address and computer name)” — so the pipeline carries personal data.
Where your data sits SaaS: offshore, in your chosen region — a cross-border transfer PIPL governs. Self-hosted: on “their infrastructure,” where customers “decide how, where, and under which conditions their data is stored.”
ICP filing Not on SolarWinds — it is backend monitoring with no public page to file. The ICP obligation sits with the mainland-facing app you monitor, not the telemetry pipeline.

The SaaS stores your telemetry offshore — and it isn’t anonymous

Run SolarWinds Observability SaaS and the data your agents ship leaves for one of four data centers, none of them in mainland China. SolarWinds’s documentation is explicit: the SaaS “is deployed across multiple data centers spanning various global regions and cloud providers,” and the sites it lists are a North American AWS data center, a North American Azure data center, a European (Frankfurt) AWS data center and an Australia AWS data center. You choose one when you create an organization — by how close it is to you, or, SolarWinds says, “whether you prefer your data is hosted in AWS or Azure” — and the mainland is not on the menu.

That would be a latency footnote if the data were anonymous. It is not. SolarWinds states its Customer Data is drawn from “the end points and other systems, tools, or devices that Customers manage or monitor,” and “may also include event logs, end user information (such as IP address, email address and computer name).” The moment that telemetry describes Chinese users or systems and lands in an offshore region, you have made a cross-border transfer of personal information under China’s Personal Information Protection Law — and as the handler you must give notice, obtain separate consent, and clear one transfer mechanism (a CAC security assessment, the CAC standard contract, or certification) under Articles 38–43. SolarWinds does not carry that for you: for its SaaS it is, in its own words, a “processor,” and Customer Data “is owned and controlled by our Customers.”

Self-hosted is the door that can stay in-country

This is where SolarWinds differs from a cloud-only tool, and why the honest answer is not a flat no. SolarWinds Observability Self-Hosted — the product formerly called Hybrid Cloud Observability, built on the platform that grew out of Orion — is software you install and operate yourself. SolarWinds describes it as a platform that “runs behind your firewall” “without moving sensitive operational data to a vendor-managed cloud,” and its privacy notice confirms that for an on-premises deployment “the Customer is in control of their own product data.” Because “by keeping their software and product data on their infrastructure,” customers “can decide how, where, and under which conditions their data is stored,” putting those servers inside the mainland keeps the monitoring data in the mainland.

So the residency question does not disappear — it moves to you, and where you place the install decides whether a cross-border transfer happens at all. If you are a critical information infrastructure operator or a large-volume handler, personal information collected in China must be stored in the mainland (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)); a self-hosted deployment on in-country infrastructure can satisfy that duty, where the SaaS — with no mainland region to select — cannot.

SolarWinds needs no ICP — the app it watches does

It pays to be exact about which Chinese rule is in play here, because hanging the wrong one on SolarWinds obscures the real risk. ICP filing (ICP 备案, under State Council Order No. 292 and MIIT Order No. 33) governs public-facing websites and online services delivered to mainland visitors. SolarWinds is backend monitoring — there is no public SolarWinds page your end users load — so no ICP filing attaches to SolarWinds itself, in either its SaaS or self-hosted form. That obligation belongs to the mainland-facing website or application you point the agents at. The real question is not whether SolarWinds holds an ICP filing, but where the personal data inside your telemetry comes to rest — and for the SaaS, that is never the mainland.

This is a risk map, not a verdict — what counts as personal data in your telemetry, whether a localization duty bites, and which model fits all turn on what you monitor, how much you hold and who your users are, and they are worth settling with counsel before you rely on them.

Where 21YunBox fits — a compliant overlay, not a migration

You keep SolarWinds exactly as you run it today — whether that is the SaaS dashboards or the self-hosted platform behind your firewall, agents and alerts untouched. The one thing neither edition supplies is a lawful mainland footing for the application those agents watch, and that is what 21YunBox adds: compliant, ICP-filed delivery from inside the mainland, placed in front of your existing origin, with no rebuild and no second codebase. Our China team weighs what personal information your metrics, events, logs and traces actually carry, sets your PIPL cross-border and data-residency obligations against your entity and data volumes, and stands up the in-country delivery and storage a compliant China presence requires — all while your monitoring keeps reporting into SolarWinds.

Get a compliance assessment →


Related reading:

Frequently Asked Questions

Is SolarWinds Observability SaaS data stored in mainland China?

No. SolarWinds's own documentation lists four SaaS data centers — a North American AWS site, a North American Azure site, a European (Frankfurt) AWS site and an Australia AWS site — and you choose one when you create your organization. None is inside mainland China. So telemetry you send from Chinese systems to the SaaS is stored offshore, which turns it into a cross-border transfer of personal information under PIPL whenever that telemetry carries IP addresses, emails or computer names — and SolarWinds's own privacy notice confirms event logs can carry exactly those.

Can we run SolarWinds in China without a cross-border transfer?

Potentially — with the self-hosted product, not the SaaS. SolarWinds Observability Self-Hosted (formerly Hybrid Cloud Observability) "runs behind your firewall," and SolarWinds says that in an on-premises deployment "the Customer is in control of their own product data" and can "decide how, where, and under which conditions their data is stored." Install it on servers inside the mainland and the monitoring data can stay in-country. Treat the final call as one for counsel: whether a localization duty applies at all turns on your role (e.g. CIIO) and your data volumes.

Can 21YunBox help make our SolarWinds setup work in China?

Yes. Our China team can map which path fits — weighing your PIPL cross-border and data-residency exposure on the SaaS against a self-hosted, in-country deployment, for your entity, data volumes and users — and stand up the ICP-filed, in-country delivery the mainland-facing app you monitor requires, on top of the SolarWinds stack you already run. Get in touch to work through your specific case.

ARTICLES RELATED TO SOLARWINDS

CATEGORIES

WebOps

Make Your Site Work inside the Great Firewall of China

Enter your information, and our staff will assist you in getting a 21YunBox account for China.

Make Your Site Work Within the Great Firewall of China
Make Your Site Work Within the Great Firewall of China

By clicking 'Get Started', I also agree to 21YunBox's Terms of Service and Privacy Policy.