The US Just Ordered Every Civilian Agency to Rip DeepSeek Out, Including Tools Built on It
Quick verdict
The Department of Homeland Security issued Order 2026-01, which tells every civilian federal agency to stop procuring DeepSeek and to remove it from their IT systems, including third-party tools that are built on DeepSeek underneath. National-security and classified systems are carved out, agencies have 60 days to file for exceptions, and there are interim logging rules while the removal happens. If you use DeepSeek as a private person or a company, nothing about this order touches you directly. But it hardens a line that has been forming all year, and it leaves one door open that matters a lot: the order is aimed at DeepSeek the hosted service, not DeepSeek the open weights.
What the order actually says
The directive, posted to the Federal Register, covers federal civilian executive-branch agencies. It does two things: it bars new procurement of DeepSeek products, and it requires agencies to find and remove DeepSeek already running in their systems, down to third-party services that embed a DeepSeek implementation without advertising it.
- The stated reasons are China-based infrastructure, Chinese legal-access risk, data collection and device fingerprinting, the chance that sensitive inputs get exfiltrated, and earlier vulnerabilities in DeepSeek's mobile app
- National-security systems and classified systems are excluded from the order
- Agencies can request an exception within 60 days, and until a system is cleaned up they have to apply monitoring and logging controls
Read plainly, this is a procurement and supply-chain action about one vendor's data handling, not a statement that the model itself is dangerous to run. That distinction is the whole game, and the people who actually deploy these models spotted it immediately.
The open-weight loophole
DeepSeek is open weights under an MIT license. The order can stop an agency from sending prompts to DeepSeek's own API, where the data leaves US soil, but it has a harder time with the weights, because those are already mirrored across Hugging Face and baked into countless setups. The sharpest point in the r/LocalLLM thread, which drew more than 1,100 comments, was exactly this: the security concern is who receives your prompts, your outputs and your logs, not where the math was trained. A US datacenter hosting the same DeepSeek weights could plausibly comply, because the data never touches Chinese infrastructure.
There is a catch on the other side of that argument. A NIST/CAISI evaluation found that political censorship persisted even in DeepSeek weights downloaded and run on NIST's own machines. Self-hosting fixes the data-exfiltration problem. It does not automatically strip behavior baked into the weights during training. So the honest read is that hosting location and model behavior are two separate questions, and the DHS order only answers the first one.
Why it matters if you run more than one model
Most people reading this are not a federal agency. The reason the order still matters is that it is the clearest sign yet that model access can flip on a policy memo. A year ago DeepSeek was the open-weight value leader almost everyone quietly leaned on as a price anchor. Now one arm of the US government has told its agencies to tear it out. The provider you depend on today can become the provider you are not allowed to touch tomorrow, and that can happen for reasons that have nothing to do with how good the model is.
The practical answer is the boring one: do not wire your work to a single model or a single provider. If you reach DeepSeek, Qwen, Claude and GPT from one place, a ban or a price hike on any one of them is an inconvenience, not a migration project. That is the entire case for an aggregator that lets you swap models without re-plumbing anything, and it gets stronger every time the politics around a model gets loud.
The pattern this fits
This is not happening in isolation. Two days before the DHS order, China floated its own rules in the opposite direction. We covered Beijing's draft export controls on big AI models, and the carve-out that lets already-open weights keep flowing. Put the two side by side and the shape is obvious: Washington is restricting what Chinese AI can run inside US systems, Beijing is sketching rules for what its best models can ship abroad, and open-weight users sit in the middle of both. The lesson from each capital is identical. Treat any one model as something that can be pulled, and build so that losing it costs you an afternoon, not a quarter.
Video: DHS orders DeepSeek removed from federal systems
Context on the order, what counts as a DeepSeek-based product, and the hosted-versus-open-weights distinction that decides who it really affects.
FAQ
Does this ban mean I cannot use DeepSeek anymore?
No. The order applies to federal civilian agencies and their procurement, not to private people or companies. You can still use DeepSeek, and if you want to run it next to other models without depending on any single one, see our guide to running multiple AI models in one app.
Why ban an open-source model at all?
The order targets DeepSeek the hosted service, where prompts and data travel to China-based infrastructure, rather than the open weights themselves. Commenters noted that the same weights hosted on US infrastructure could plausibly comply, because the security concern is who receives your data, not where the model was trained.
Does self-hosting DeepSeek remove the risk?
It removes the data-exfiltration risk, since nothing leaves your machine. It does not remove behavior trained into the weights. A NIST/CAISI evaluation found political censorship persisted even in self-hosted DeepSeek, so hosting location and model behavior are separate things to check.
How fast does this take effect?
Agencies have to stop new procurement now and begin removal, with a 60-day window to request exceptions and interim monitoring rules until systems are cleaned up. National-security and classified systems are excluded.
Sources
- Federal Register - DHS Order 2026-01 on removing DeepSeek from agency systems
- r/LocalLLM - The US is ordering every civilian agency to rip out DeepSeek, even tools built on it
- NIST/CAISI - evaluation of DeepSeek models, including censorship in self-hosted builds
- @kimmonismus - DHS ordering civilian agencies to remove DeepSeek and products built on it
Further reading
Try all the models mentioned in this article
Admix gives you GPT-5, Claude, Gemini, and 350+ AI models in one app. Compare responses side by side. Try it for 7 days for $1.99.
Try Admix for $1.99