Required for the site to work (login, preferences, security). Always on.
Anthropic's supply chain exclusion: the Pentagon wins in appeals court
A US appeals court upholds, 2-1, the exclusion of Claude from work for the American military. What was decided, what is still open and what changes for Claude users in Europe.
A US federal appeals court has confirmed that the Pentagon can treat Anthropic, the company behind Claude, as a supply chain risk. The story passed 400 points and 700 comments on Hacker News.

What is confirmed
On 25 September 2026 the US Court of Appeals for the District of Columbia Circuit rejected, by two votes to one, Anthropic's petitions against the designation. Judge Gregory Katsas wrote the majority opinion, joined by Judge Neomi Rao. According to Katsas, the Department had "ample support" for concluding that the continued integration of Claude into its information systems, by the Department or its contractors, presented a statutorily covered national-security risk.
Judge Karen LeCraft Henderson dissented: in her view the law does not treat "a contractor's honest and upfront enforcement of restrictions" as the kind of risk that allows the government to exclude it. The dispute started with Anthropic's refusal to relax contract terms that bar the use of Claude for lethal autonomous warfare and mass surveillance of Americans. In March the Pentagon responded under a 2018 supply chain security law: the designation keeps the armed forces and their contractors from using Anthropic's models in defense work.
There are actually two designations, challenged in two different courts. In August, District Judge Rita Lin in San Francisco ruled against the government on the other one.
Why it matters to you
If you are a European SME or MSP using Claude, the designation concerns the US Department of Defense and those who work for it. If you supply software or services to customers in the US defense supply chain, though, it is worth asking whether they use Claude on those projects.
The broader lesson applies to everyone:
- Usage policies are part of the product: AI vendors can decide what their models may be used for, and those rules can change or clash with your customers' rules. Read them the way you read an SLA.
- Depending on a single model is a supply risk: An architecture that lets you switch models without rewriting your applications is insurance.
- Know where you use what: if you know which projects and customers depend on a given model, you can answer when someone asks.
If you want an AI strategy that does not hinge on a single vendor, you can find our approach on the artificial intelligence services page.
Sources: US Court of Appeals for the District of Columbia Circuit, US District Court for the Northern District of California, Hacker News discussion.