01 The services
CN-01
Business VPN for China
Dedicated MPLS or IPSec lines with guaranteed bandwidth and a unique IP — not a shared consumer tunnel. Isolated resources, fast IP switching, monitored around the clock.
For: Teams that need reliable access to corporate systems, code hosts and model endpoints from inside the mainland.
CN-02
Website acceleration in China
Get a foreign-hosted site loading in seconds rather than tens of seconds for mainland visitors, through in-country CDN, routing and origin work.
For: Marketing sites, SaaS front-ends and documentation that mainland users currently abandon before first paint.
CN-03
ICP 备案 filing support
ICP filing and licence support — the prerequisite for hosting anything on mainland servers legally. We handle the paperwork loop with the provider and the MIIT.
For: Anyone who needs a mainland-hosted origin, which includes anyone who needs mainland-hosted inference.
CN-04
Cross-border connectivity
CEN, Express Connect, leased lines and VPC peering between mainland and global regions, with the compliance work that comes attached.
For: Multi-jurisdiction deployments where data has to move between mainland and global systems on a defined path.
CN-05
Salesforce in China
Making Salesforce usable for mainland-based teams — acceleration, routing and the integration work that makes the CRM stop timing out.
For: Sales organisations with mainland staff on a global Salesforce org.
02 Why it still matters
China is not another country. It is another internet.
Over ninety per cent of foreign websites are effectively unusable from the mainland — not blocked, just slow enough that people leave. Your CRM times out. Your docs do not load. Your CI cannot reach its registry. And now your product cannot reach the model it depends on.
None of that is solved by a consumer VPN or by moving a CDN origin. It is solved by in-country infrastructure, a filing, dedicated lines and someone who has done the paperwork loop before. We have been doing exactly that since 2017.
03 The new version of an old problem
Where is your model allowed to answer?
A mainland team using a US-hosted model API has all the latency problems of the last decade plus a data export question nobody in the room wants to own. The fix is structurally the same as it always was — put the thing that answers inside the border — and it has become considerably easier now that the strongest open-weight models are Chinese.
- Open-weight models can run on mainland capacity, close to mainland users and under mainland jurisdiction — which is either exactly what you need or exactly what you must avoid. Either way it should be a decision, not an accident.
- One control point per jurisdiction, so requests are answered on the side of the border that policy requires and the rule is enforced rather than remembered.
- Usage records kept in each region, so the audit trail exists on both sides without the records themselves crossing a border.
- Cross-border links for the traffic that legitimately has to move, on a designed and documented path rather than a tunnel somebody improvised.
04 Track record
We have been writing about this for nine years.
Most of what is published in English about AWS China ARNs, Alibaba Cloud CEN, mainland compliance and cross-border architecture, we wrote. It is all on the blog, free, and it is the reason most China clients arrive here already half-convinced.