The order
Signed in July, Published in October — The Exception Window Closed First
The Department of Homeland Security signed Exclusion and Removal Order #2026-01 on July 24, 2026. It reached the Federal Register on October 20, 2026 under docket DHS-2026-0628, roughly three months later — and by the time it was public, the 60-day exception window had already closed on September 22.
How the order actually unfolded
Order signed
July 24, 2026
DHS Secretary Markwayne Mullin
Exception requests due
September 22, 2026
60 days from signature, filed with CISA
Public inspection filing
October 19, 2026
Notice 2026-21447, docket DHS-2026-0628
Federal Register publication
October 20, 2026
Full text of the exclusion and removal order
Prior agency actions
Jan 2025 onward
Pentagon network block, then Navy, NASA and other agency-level actions
The authority is a Federal Acquisition Security Council review under the Federal Acquisition Supply Chain Security Act, and the scope is all federal civilian executive branch agencies — roughly 430 departments, bureaus and independent agencies. Agencies can still ask CISA for a scope limitation, a delayed implementation, or an alternative safeguard, backed by a written mission-impact justification. But the character of the instrument has changed: this is exclusion from procurement, not guidance to administrators.
Mechanism
The Clause That Matters Is About Vendors, Not Models
DeepSeek's own application was never the prize. The operative language reaches all DeepSeek and DeepSeek-affiliate products and any third-party product or service built using DeepSeek implementations. That single phrase converts an endpoint cleanup into a disqualification criterion.
- Procurement eligibility, not just network blocking. A vendor that routes any agency workload to DeepSeek can be excluded from future awards, not merely disconnected today.
- Self-hosted weights still count. Running DeepSeek-V4 inside a federal enclave is a DeepSeek implementation, so the enclave does not launder the dependency.
- The exception menu is deliberately narrow: scope limitation, delayed implementation, or alternative safeguard — not a general waiver for commercial necessity.
- Removal is retroactive. Products already deployed have to come out of agency systems, which converts a procurement rule into a remediation and audit workload.
- The Chinese parent is named directly. The order excludes the parent entity Hangzhou DeepSeek Artificial Intelligence, which forecloses the affiliate-structures argument used in earlier telecom-era bans.
For a software company selling into government, this is a compliance cliff with a due date. Procurement officers now have to answer a question they never had to ask before: what is under the hood of the product being bid. That favors incumbents who can produce model-provenance attestations quickly and penalizes smaller vendors who route cheap tasks to a commodity API to hit a price point.
The prize
The Budget This Rule Governs Grew 966% in Two Years
The certified channel is arriving at exactly the moment it is worth the most. Analysis of 1,743 federal contracts between September 2023 and March 2026 found that funds obligated for AI rose from $675 million in 2024 to $7.2 billion in 2026, while total potential award value — including ceilings — rose from $4.6 billion to $91.8 billion.
Federal AI funds obligated, 2026
$7.2B
Up 966% from $675M in 2024
Potential award value, 2026
$91.8B
Up 1,912% from $4.6B in 2024
Defense Department share
98.9%
About $90.7B of the 2026 total
Firms holding one or two contracts
87%
Long tail of firms, thin share of value
Potential value of federal AI contract awards
Ceiling-inclusive award values across 1,743 tracked contracts, September 2023 to March 2026.
Unit: $ millions
2022
Baseline year
355
2024
Up almost 1,200% from 2022
4,600
2026
Defense Department is 98.9% of the total
91,800
That is the second-order effect of a blacklist: excluding one vendor hands every surviving supplier a certified channel into a budget that grew tenfold. The rule does not create federal AI demand. It decides which companies get to bid for demand that already exists.
| Vendor | Latest reported revenue | Gross margin | EV / trailing sales |
|---|---|---|---|
| Palantir | $1.94B, Q2 2026 | 84.7% | 71.9x |
| Accenture | $18.68B, Q4 FY2026 | 32.0% | 2.0x |
| Booz Allen Hamilton | $2.80B, Q1 FY2027 | 52.3% | 1.1x |
| UL Solutions | $816M, Q2 2026 | 51.1% | 4.7x |
The spread is the argument. The company selling proprietary software into federal mission systems trades at seventy times sales, while the company selling federal labor at scale trades at roughly one times sales and is currently shrinking. Procurement access is not what the market capitalizes. Proprietary margins on top of procurement access are.
The gap
The Token Share the Order Does Not Touch
Here is the part that does not fit the threat narrative. Chinese models were not a rounding error in Western AI development by the time Washington acted. They were carrying the majority of routed developer traffic.
Chinese models' share of tokens on OpenRouter
Share of tokens consumed on OpenRouter, by week, as reported September 26, 2026.
Unit: percent of tokens
February 2026, low week
6%
February 2026, high week
13%
Week of Sept 14, 2026, low
57%
Week of Sept 14, 2026, high
67%
- Routed volume itself has exploded: weekly token consumption on OpenRouter went from roughly 0.5 trillion in January 2025 to 126.2 trillion by September 2026.
- The CISA, NSA and FBI joint advisory of September 8, 2026 named six China-based labs — DeepSeek, Moonshot AI, Alibaba, MiniMax, StepFun and Z.AI — as running industrial-scale distillation against US frontier models.
- It says those labs extracted billions of tokens across millions of exchanges, with DeepSeek doing it since at least late 2024 against Claude, GPT, Gemini and Grok models.
- The advisory explicitly calls DeepSeek's widely quoted 5.6M training cost misleading, because it excludes the cost of the data acquired through distillation.
- Token share is not revenue share, and no one publishes the latter. OpenRouter discloses token counts only, and a commodity-priced API can win routed volume without winning the bill.
Second-order cost
The Advisory Makes Every Frontier Lab an Operating Cost
The September 8 advisory did something more durable than the ban. Its recommended mitigations sit inside the model providers' serving stack: subtly alter responses for suspected distillation attempts, apply differential privacy, reduce reasoning depth on flagged accounts, and do not tell the suspected distiller that anything changed.
Operationally, that tells every frontier lab to degrade output for accounts it cannot confidently identify. That is a recurring inference and engineering cost, borne by the highest-priced tier of usage, in exchange for protecting a capability lead that the same advisory argues is already being harvested at industrial scale. For Alphabet, whose capital spending ran at 37.5% of revenue in Q2 2026, an unpriced reliability tax on the premium tier is not a rounding error.
The read-through is uncomfortable for the winners. A certified-vendor channel solves who gets to sell to the government. It does nothing about whether the government's supplier keeps an advantage it can defend for another twelve months.
Response
Beijing Answered in Language. Washington Holds a Dated Vote on Testing.
China's response was framing, not escalation. Foreign Ministry spokeswoman Mao Ning said Beijing opposes overstretching the concept of national security and politicizing technology and trade issues, and the commerce ministry registered strong dissatisfaction. No countermeasure was announced against American suppliers.
The concrete action with a date on it is not Chinese. On October 29, 2026 the Federal Communications Commission votes on an order that would end recognition of every test lab in mainland China, after a transition ending December 1, 2028. This is the same security logic applied to a different bottleneck, and it has a clearer revenue trail than the AI order.
| Item | Figure |
|---|---|
| Share of US device testing done in China | 13% in 2007, over 82% by 2025 |
| Commission vote date | October 29, 2026 |
| Transition end date | December 1, 2028 |
| Share assumed shifting to US labs | 35% |
| Share assumed shifting to other partner economies | 65% |
| Industry-wide incremental annual cost | $79.3M, from year three |
| One-time familiarization cost | $23.6M |
| Quantified annual benefits | $20.2M |
| Five-year present value at 3% | $234.2M cost against $53.9M benefit |
The economics look poor on the FCC's own numbers, and that is precisely what makes it informative. A rule with a negative benefit-cost ratio, a two-year runway, and a fixed vote date is a real trade for the testing industry in a way that an open-ended model ban is not. The AI order has no comparable price tag because it has no disclosed enforcement cost.
Horizons
What Moves First, and What Compounds
In the next two quarters, watch solicitations. Contract language citing the exclusion by docket number will show up in requests for proposal, and the first material signal will be remediation and re-platforming task orders rather than new model awards. On October 29 the FCC vote either creates or kills a dated migration for device testing. And some agencies filed exception requests by September 22 that have not been disclosed; the denial rate is the cleanest available read on how binding the rule actually is.
Over one to three years, the durable question is whether exclusion becomes default. The precedent is already written: the Pentagon network block in January 2025, then agency-level bans, then Section 1532 of the fiscal 2026 defense authorization act signed December 18, 2025, then this order. Each step widened the definition from a device to a network to a supplier. The next widening would be from a named vendor to a country of origin, which is what a reciprocity response would look like from Beijing. The December 1, 2028 testing transition is the fixed point to anchor that timeline, because it forces the question in hardware before it is forced again in software.
Synthesis
The Ban Is Real, the Damage Is Small, the Second-Order Effect Is Not
Facts: the order is signed, it covers about 430 agencies, it reaches third-party products built on DeepSeek implementations, and it was published three months after agencies had to comply. DeepSeek's revenue is concentrated outside the United States, and its Western consumer and developer traction is now measured in routed tokens it still holds.
Inference: the instrument that matters is the certification requirement, not the exclusion. Every dollar of a $7.2 billion obligated federal AI budget now has to be bought from a vendor that can pass a provenance test, and that requirement will be copied by state and allied procurement long before it changes DeepSeek's income statement. The near-term winners are federal integrators and accredited testing labs; the losers are vendors whose margins depended on cheap commodity inference nobody could audit.
Where this is investable
- Q2 2026 revenue of $1.94B grew 92.8% year over year at 84.7% gross margin, and the exclusion order confirms its federal channel.
- At 71.9x trailing sales, the certified-vendor tailwind is already in the price, so the order changes narrative more than multiple.
- Days to quarters: solicitation language citing DHS-2026-0628 raises rivals' compliance cost. One to three years: watch whether federal revenue share is disclosed separately.
- Selected for an $821M War Data Platform integration task order in July 2026, the integrator is paid to re-platform work this order forces.
- $74.2B of trailing revenue gives it the bench to absorb re-platforming demand at a 32.0% gross margin.
- Days to quarters: remediation task orders referencing DeepSeek removal should appear in solicitations within one to two quarters.
- A certified-vendor list is a tailwind for the incumbent defense integrator, whose Q1 FY2027 revenue of $2.80B fell 4.2% year over year.
- Against that, Q1 FY2027 net income of $198M was down from $267M a year earlier.
- At 1.1x trailing sales with 2.9x net leverage, the market refuses to pay for federal services exposure, and this order does not change that.
- Days to quarters: the November FY2027 second-quarter print is the first clean read on whether federal bookings turn.
- Gemini is one of four labs that took up to $200M each from the Pentagon's AI office in July 2025, and a classified deployment agreement followed in April 2026.
- The September 8 advisory names Gemini among models extracted at scale and tells providers to degrade output for accounts they cannot identify, a recurring serving cost.
- Q2 2026 capital spending ran at 37.5% of revenue, so an unpriced reliability tax lands on a stretched base.
- One to three years: federal share of cloud revenue is not disclosed, so the captive-channel value cannot be sized from outside.
- Named in the September 8, 2026 joint advisory as a distiller of Claude and GPT-5 outputs, ahead of the DeepSeek exclusion order.
- With Chinese models at up to 67% of routed US tokens, procurement exclusion turns commercial reach into political liability outside the federal channel.
- Trailing enterprise value to sales of 1.8x leaves limited cushion if non-US buyers follow the US precedent.
- Alibaba discloses no US enterprise AI revenue, so the size of the channel the order closes is not measurable from outside the company.
- The FCC order would end recognition of mainland China test labs after December 1, 2028, with about 35% of shifted volume assumed to reach US labs.
- Q2 2026 gross margin of 51.1% on $816M of revenue leaves room to price that migration, but the whole industry absorbs only $79.3M a year.
- Binary catalyst: the October 29, 2026 vote decides whether the December 1, 2028 transition survives at all.
