Good to knowSupply chain

The US government orders federal civilian agencies to remove DeepSeek, and tools built on it

A notice published on 20 Oct 2026 in the Federal Register records a Homeland Security order to exclude DeepSeek products from federal civilian purchases and to remove them from agency systems, including third-party services built on DeepSeek. It is not a ban on private use. Who should care, and what to check in your own stack.

How urgent

Good to know

Who is affected

Teams that sell to US federal civilian agencies, or that build on DeepSeek models or on services that use them. The order does not restrict private or consumer use

What to do

If you sell to US federal agencies, find out whether your product, your vendors or your AI gateway use DeepSeek. Everyone else: know which models your tools call

Published 3 Nov 2026 · Sources last checked 3 Nov 2026No. 41 / 87

What happened

On 20 October 2026 the US Federal Register published a notice of order from the Department of Homeland Security about DeepSeek, the Chinese AI developer. According to the notice, the order does two things for federal civilian agencies:

  • Exclude information technology products and services developed by Hangzhou DeepSeek Artificial Intelligence Co., Ltd, including its affiliated entities, from their purchases.
  • Remove all DeepSeek and DeepSeek-affiliate products from their information technology, together with third-party products and services built using DeepSeek implementations.

The notice names as its legal basis the Federal Acquisition Supply ChainSupply chain attack An attack that reaches you through something you already trust and install, such as a code package, a tool or a provider. Tap again to open the glossary Security Act of 2018 and says the order followed a review of a recommendation by the Federal Acquisition Security Council and related evidence. It gives no further reasons.

This is two weeks old and we did not cover it before. We add it now because it touches a question many small teams skip: which AI models sit behind the tools you use.

What it does not say

  • It applies to federal civilian agencies, in their purchases and their systems. BleepingComputer's report says it is not a general ban on private or consumer use, and we found nothing in the notice that restricts private use.
  • The notice's text does not set out exceptions, deadlines for removal, or duties for contractors. BleepingComputer reports that agencies must remove covered products immediately or ask for an exception within 60 days, and that CISA will approve or deny exceptions in writing. We could not check that in the notice, because the signed order itself appears only as image attachments that we could not read.
  • We do not know how the order treats an open-weights model, a model whose files anyone can download and run, when a third party delivers it. The notice does not say.

Why it matters if you build with AI

Many AI tools do not run one model: they route your request to whichever provider is cheapest or fastest. If you sell software to US federal agencies, or plan to, the reference to "third-party products and services built using DeepSeek implementations" means a vendor or a gateway behind your product could matter, even if you never chose DeepSeek yourself. That reading is ours; we did not find official guidance on how far it reaches.

For everyone else, the lesson is general: know which models and which providers your tools call, and where your data goes. BleepingComputer says the stated concerns include possible access by the Chinese government to DeepSeek infrastructure and the collection of personal information. These are concerns reported in the press, not findings we checked.

What to do

This is our reading of the notice and one press report; it is not legal advice.

  1. If you sell to US federal civilian agencies, or want to, ask your legal contact whether the order affects you, and list every model, API and AI gateway your product uses.
  2. Check your AI gateway and tool settings. If a service lets you choose providers or picks one for you, see whether DeepSeek models can be selected or used by default, and switch that off where it does not fit your customers.
  3. Keep a list of the models your product calls, and of the providers that host them. Update it when you change a tool.
  4. Do not assume a ban where there is none. If you do not sell to federal agencies, the order does not tell you to stop using anything. What you use is your own risk decision.
  5. Vet new AI tools before you add them. Our tool-vetting checklist helps with the questions to ask.

What we could not confirm

We read the Federal Register notice and one press report, BleepingComputer. We could not read the signed order itself, which the notice includes only as images, or DHS's own statement. Two other pages (a law firm's summary and a DHS news page) did not open for us. The details about the 60-day exception window and CISA's role come only from BleepingComputer. We do not know how agencies are applying the order, how it treats open-weights models or services that route between models, or whether more guidance exists. We have not tested any DeepSeek product.

Comments

No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.

    We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.

    Sources and verification

    We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.

    Spotted a mistake? Email [email protected] and we will correct it and note the change.

    Get the free runbooks

    One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

    Send me the runbooks