Does Vercel Work in China? ICP Filing, Visitor Data & the Compliant In-Country Layer

Vercel is one of the best platforms in the world to build and ship a web application, and nothing here asks you to leave it. Your app stays on Vercel — the same Git-driven deploys, the same framework support, the same global edge. This article is about the one thing a public, mainland-China audience adds on top of that: a presence that is licensed to operate inside China. That is a compliance question, and it is the half of “does Vercel work in China” that no amount of platform tuning answers — because it was never Vercel’s job to answer it.

The short version is a partnership, not a replacement. Vercel remains your origin and source of truth; 21YunBox sits in front of it as an ICP-filed, in-country entry for mainland visitors. Below is what Vercel itself documents about its network, the ICP door that a global edge structurally cannot hold, and the lawful way visitor data is handled at the border — in Vercel’s own words and China’s own law, so you can take it to counsel.

Vercel in China at a glance

What Vercel gives you globally

Vercel’s description of its own network is worth reading before anything else. Its CDN, in its words, “stores content and runs compute close to your users and data, reducing latency and improving performance,” and it does so from “126 Points of Presence in 94 cities across 51 countries,” backed by “19 compute-capable regions.” For a global audience this is close to ideal, and it is exactly why your application belongs on Vercel.

What that same list shows — plainly, on Vercel’s own page — is that the network is built to serve users from the outside in. The regions nearest the mainland are Hong Kong (hkg1), Tokyo (hnd1), Seoul (icn1) and Singapore (sin1); every one of them sits offshore from mainland China. Vercel is equally direct in its own China guidance: it “has no servers or CDN nodes in mainland China,” and “China’s network controls can block or throttle traffic to foreign domains, including Vercel’s .vercel.app subdomains.” Two of Vercel’s free first steps — “Replace the .vercel.app domain with your own custom domain” and “Reduce reliance on third-party scripts and services that may be blocked in China” — are worth doing on any stack. None of that, though, places your site inside China, which is where the next section begins.

The ICP door Vercel’s edge can’t hold

Serving a public website to people in mainland China turns on a permission that has nothing to do with performance: an ICP filing (备案). Under State Council Order No. 292 (Article 4) and MIIT Order No. 33, that filing attaches to a hosting resource physically inside the mainland and to a mainland legal entity — a foreign company with neither cannot file directly. Vercel reaches the same conclusion in its own words: “Hosting within China requires an ICP license and compliance with local requirements.”

This is where a global edge meets its natural boundary. Vercel even names the routes other teams take to get in-country: some improve access “by deploying a static mirror on infrastructure with more reliable routing into China,” and others “maintain a separate version of their site on local infrastructure within mainland China, which requires an ICP license and compliance with local regulations.” Both descriptions share one requirement — an ICP-filed presence inside the mainland — and that presence is not something Vercel’s own network includes, because it was never meant to. It is a licensing fact, not a shortcoming: the filing needs a licensed mainland host to attach to, and Vercel’s hosts are offshore.

The compliant in-country design

The lawful way to serve a public mainland audience is to put an ICP-filed, in-country entry in front of your Vercel origin — and to be deliberate about visitor data at that entry.

Here is the part teams most often have backwards. A mainland visitor’s real IP address is itself personal information under China’s Personal Information Protection Law. Carrying every visitor’s real client IP out of the mainland to an offshore origin is a cross-border transfer of personal information, which PIPL governs (Chapter III, Articles 38–43: notice, separate consent, and one permitted transfer mechanism — a CAC security assessment, the CAC standard contract, or certification; Article 40, with Cybersecurity Law Article 39 (formerly Article 37), adds an in-country storage duty for a critical information infrastructure operator or a large-volume handler).

So the compliant design does the opposite: it terminates mainland visitors at an in-country, ICP-filed entry and sends a single, fixed in-country IP to your Vercel origin, rather than forwarding each visitor’s real IP across the border. Your Vercel origin therefore sees one in-country address instead of every visitor’s own — and that is the lawful design working as intended, not a defect to engineer around. Whether a particular site must also store personal data inside the mainland depends on your role and data volumes, which is a question for counsel rather than a default.

Where 21YunBox fits — a compliant overlay that sits in front of Vercel

You keep building and shipping on Vercel exactly as you do today — same deploys, same origin, same global platform. 21YunBox adds the one piece a global edge structurally cannot: compliant, ICP-filed delivery from inside the mainland, placed in front of your existing Vercel origin — no rebuild, no second codebase, and no move off Vercel. Our China team maps which obligations apply to your entity and your data, handles the ICP filing, and stands up the in-country entry that serves your mainland audience while Vercel stays your source of truth.

Get a compliance assessment →

Related reading:

• What is the China ICP license, and how do you get one?
• Cross-border data transfers under PIPL