Name the features first — multi-tenant hosting, customer connectivity, payments and data flows pick the licence stack.
‘SaaS’ is not a MIIT licence category by itself. A China SaaS product may need ICP filing for the portal, one or more VATS items (for example online data processing), cloud/IDC partnerships, and PIPL/data overlays. Foreign ownership limits bite differently by catalogue item. This wiki is the mapping desk. Atomic VATS pages and cloud licensing sit beside it. Live ICP/VATS and cloud flagships remain deep guides.
4 questions before you choose the route.
This page identifies the right question and evidence. It does not determine the legal outcome on a reader’s facts.
What does the tenant actually use?
Features.
FeaturesWho provides infrastructure?
Self vs partner.
InfraWhich VATS items might apply?
Catalogue.
VATSCross-border data?
PIPL/CBDT overlays.
DataWorking rule: Map the regulated role before marketing or launch in China.
The signal ledger.
These facts move the question beyond a label and into a product, money-flow and control analysis.
Bring a compact evidence docket—not a pitch deck.
Give a compliance team or counsel the operating facts that reveal the perimeter.
Questions people ask before they build.
Short answers for orientation. The right result can change with the service model and current rules.
Is overseas SaaS sold into China licence-free?
Contracting offshore does not erase China telecom/data issues when you target China users or place infrastructure here.
Where are cloud flagships?
Keep /china-cloud-computing-law and /china-icp-vats-telecom-law.
Primary authorities
Reviewed sources support orientation, not a fact-specific assessment.