Hosting in China: ICP Licensing, Local Infrastructure, and What Enterprises Get Wrong
China is one of the few markets where the infrastructure decision comes before the launch decision, not after it. A product that works well in Europe or North America can arrive in China slow, partly broken, or legally unable to run on local servers at all. None of that is visible during development, which is why so many enterprises find out in the final weeks before go-live.
This post covers what ICP registration actually is, how hosting in China differs from hosting elsewhere, and the mistakes we see most often when enterprises plan a China launch. It is written for business and technology leaders who need to understand the shape of the problem before they commit budget and timelines.
What ICP Actually Means
ICP stands for Internet Content Provider. In practice, the term covers two different things, and confusing them is the first mistake many teams make.
ICP filing (often called ICP registration, or bei'an in Chinese) is a registration with the Ministry of Industry and Information Technology, handled through the provincial communications authority. It is required for informational websites and apps that are hosted on servers inside mainland China. Once approved, the filing number has to be displayed on the site, usually in the footer.
The ICP commercial licence is a separate authorisation for services that make money online, such as e-commerce, paid subscriptions or online payments. It carries stricter requirements than a filing, takes longer to obtain, and an ICP filing is generally a prerequisite for it. Foreign ownership restrictions can also come into play depending on the type of service.
The practical rule is simple. If your site or application is hosted on servers inside mainland China, it needs an ICP filing. If it takes payments or sells services, you will probably need the commercial licence as well. If it is hosted outside mainland China, the ICP requirement does not apply to the hosting, but you accept the performance trade-offs covered below.
There is also a follow-on registration with the local public security authority, which is expected within a set period after the site goes live. Teams that treat the ICP number as the finish line often miss this step.
Mistake 1: Assuming a Foreign Company Can Apply Directly
This is the one that catches the most enterprises off guard. A foreign company with no legal presence in China generally cannot file for ICP registration in its own name. The filing is made by a Chinese legal entity, which means a subsidiary, a joint venture or an arrangement with a licensed local partner.
For a company that has not yet decided how it will operate in China, this changes the order of work. The entity question has to be settled before the infrastructure question can be. Organisations that plan the technical launch first and the corporate structure second tend to lose months in the gap.
Mistake 2: Underestimating the Timeline
Commonly cited estimates put an ICP filing at a few weeks to two months from a clean submission, and a commercial licence at several months. Those numbers assume the paperwork is complete and consistent. In practice, filings are delayed by mismatches between the company name, the domain registration details and the contact information on file, and by corrections requested during review.
Timelines and requirements also change. Provincial authorities apply the rules with some variation, and requirements have tightened over the years. Any plan that depends on a specific approval date should be validated with a licensed local partner rather than taken from a blog post, including this one.
The planning point is simple: treat the ICP process as a critical-path item from the first week of a China programme, not as a task to schedule near launch.
Mistake 3: Believing Hosting Outside China Is a Free Workaround
Many teams look at the ICP process, see the effort involved, and decide to serve Chinese users from servers in Hong Kong, Singapore or elsewhere in the region. This avoids the filing requirement, and for some low-stakes content sites it is a reasonable choice.
For a product that depends on performance and reliability, it usually disappoints. Traffic between mainland China and the rest of the world crosses international gateways that add latency, introduce packet loss and behave inconsistently at different times of day. A page that loads in under a second from a mainland server can take several seconds from an offshore one, and the variation is as damaging as the average. Users do not report this. They leave.
Search visibility is a second cost. Sites without a filing, or hosted offshore, are generally disadvantaged in mainland search results compared with locally hosted sites.
Mistake 4: Treating the ICP Number as the Whole Job
Even with a valid filing and mainland hosting, performance is not automatic. China's network is made up of large carriers with separate backbones, and traffic moving between them can be slow. A single hosting location rarely serves the whole country well.
This is where content delivery infrastructure matters. A CDN with local presence close to users, across carriers and regions, is what turns a legally compliant site into one that actually loads quickly. Providers that advertise China coverage differ widely in what they mean by it. The questions worth asking are whether the nodes sit inside mainland China, how many carriers and regions they cover, and whether the provider operates within the licensing framework rather than around it.
Mistake 5: Forgetting About Third-Party Dependencies
A site that is fast and filed can still break in the browser because of what it loads from elsewhere. Many commonly used services are slow or unreliable from within China, including some analytics scripts, embedded video, web fonts, maps, and social login buttons.
The failure mode is subtle. The page itself loads, but it hangs waiting for a blocked third-party script, or an interface element does not render. Teams often only discover this when someone in China tests the real product, because developers outside China never see it.
The fix is a dependency audit before launch. Every external resource a page calls should be reviewed
and replaced with a locally available alternative or served from local infrastructure where it matters.
Mistake 6: Ignoring Data Rules Until the Launch Review
China's cybersecurity and data protection laws, including the Personal Information Protection Law, set conditions on how personal data is collected, stored, and transferred out of the country. For any product that handles user accounts, payments, or behavioural data, these rules affect architecture decisions: where data is stored, whether it can be sent to a global analytics platform, and what consent mechanisms are needed.
These questions are far cheaper to answer during design than during a pre-launch compliance review. Legal counsel with China experience should be involved when the data flows are first drawn, not when the product is finished.
A Practical Sequence for a China Launch
Enterprises that handle China well tend to follow roughly the same order.
Decide the entity structure first. Settle whether the launch will run through a subsidiary, a joint venture or a licensed local partner, because everything else depends on it.
Start ICP work immediately. Run it in parallel with product work, with a named owner and a contingency for corrections.
Design the data flows for local rules. Map where personal data goes, and involve China-experienced legal advice early.
Audit third-party dependencies. Test the real product from inside China on multiple carriers, not just from a VPN or an office elsewhere.
Put local delivery infrastructure in place. Use a CDN with genuine mainland presence so the filed site is also a fast one.
Plan for operations after launch. Monitoring, incident response and change management need to cover China's conditions, including the filing details that have to stay current.
Where Dygital9 Fits
China is one part of a broader pattern we see in global expansion: infrastructure has to be in place before users arrive, and it has to respect local conditions. Dygital9 operates 1,700+ CDN Points of Presence across 34+ countries and 5 continents, running 24/7 and built to operate within local data laws. For enterprises planning a China launch, that means the infrastructure conversation can start early, alongside the entity and licensing questions rather than after them.
The common thread in every market that is hard to enter is the same. The enterprises that succeed ask the infrastructure and compliance questions before the product is built, not after the first launch review.
Comments