"Open weights, restricted use": the EU-shaped license templates everyone is now copying
Three of the four open-weights releases of the past 30 days share the same five clauses. The Brussels Effect is now a license template, and developers should read it before downloading.
neysa.ai
In this article
Read the LICENSE files of the past 30 days side by side and a pattern is hard to miss. Of the four notable open-weights releases since April — DeepSeek R3, Mistral Aubépine, Reka Frontier-Open, and Allen Institute's OLMo-2.5 — three share five clauses with phrasing close enough to suggest a shared template. The fourth, OLMo-2.5, is the closest to the old permissive Apache spirit, and it is also the one whose paper explicitly notes the lab is U.S.-based.
The five recurring clauses are a downstream-use restriction (clinical, biometric, government surveillance carved out as paid tiers), a model-card preservation requirement (you cannot strip the metadata), a compute-floor exemption that lets academics and individual users under a parameter threshold ignore the attribution requirements, an EU-AI-Act-aligned disclosure clause, and a versioned-license-evolution clause that lets the maintainer issue v1.1 without a re-release.
What the EU AI Act drove
The general-purpose AI model rules became applicable on 2 August 2025. The full Act binds 2 August 2026. In between, GPAI providers have been writing license terms that align with the Act's documentation, traceability, and downstream-use disclosure requirements — because the alternative is being treated as the upstream provider liable for what every downstream deployer does. Open weights without legal scaffolding is a 2024 idea.
Open weights without legal scaffolding is a 2024 idea. The 2026 version comes with a model card you cannot strip and a downstream-use clause you cannot ignore.
For developers who download these weights to fine-tune or to deploy as part of a product, the practical advice is: copy the model card forward (do not rewrite it), keep the license file in your repo, and treat the downstream-use clauses as you would any contract — meaning, ask counsel before assuming the carve-out is for your use case. The maintainers have been thoughtful. The carve-outs are real. The compliance burden is also real, and pretending it is not is the fastest way to be on the wrong side of an enforcement letter in late 2026.
Read next
