What Happened

On October 16, 2026, China’s Ministry of Commerce and Ministry of Science and Technology issued Announcement No. 48, proposing outbound export controls on AI technologies. Yahoo reported on October 18 that it is the first time Beijing has proposed such controls. The draft catalogue lists 40 technologies, 23 of them in the AI stack, including large language models, AI agents, computing clusters and chip design methods.

According to that report, 14 technologies would be prohibited from export and 26 restricted behind licensing. Model weights and source code are covered above set thresholds, and AI agents are covered when designed for sensitive environments such as national defense and critical information infrastructure. The interim measure took effect October 16, and the final catalogue is open to public consultation until November 15, 2026.

Open-source and academic publications are excluded, and API and SaaS access is exempt, so providers can keep serving global customers through cloud interfaces. The controls target things like on-premise redistribution of model weights and self-hosted deployment of advanced Chinese agents.

Three Takeaways for Small Businesses

  • Know which AI vendors sit under your workflows. The report advises builders to assess their reliance on Chinese-developed model weights. List every AI tool you use and who makes the model behind it.
  • Prefer API access over self-hosting for now. API and SaaS access is exempt, while self-hosted deployment of advanced models is where the controls point. If you run a model on your own servers, check where its weights come from.
  • Avoid single-vendor lock-in. Rules are still open to consultation until November 15 and may change. Keep your prompts, data and workflows portable so you can switch providers without rebuilding.
Intinya

AI policy now moves faster than most small business tool stacks. The safest setup is one you can move between providers.

What To Do This Week

Write down each AI tool in your business, the model behind it, and whether you use it through an API or host it yourself. Mark any that would be hard to replace, and note a backup option for each.