Guides · Article 50 · EU AI Act
Does the EU AI Act apply to open-source AI?
A common question from teams building on or releasing open-source models is whether the EU AI Act — and its Article 50 transparency obligations — applies to them at all. The honest answer is that it is nuanced and fact-specific. The Act treats some actors and uses differently, and how open-source release fits is not something to assume from memory. This guide frames the question without asserting a blanket exemption. It is informational only, not legal advice, and does not decide whether the Act applies to you.
Why 'open source' is not a simple on/off switch
It is tempting to treat 'open source' as an automatic carve-out from the whole Act. That is not a safe assumption. The Regulation contains detailed provisions about how different actors and situations are treated, and whether — and how — those touch a given open-source model, tool, or deployment depends on specifics: what you release, how it is made available, who uses it, and in what role. Rather than assert a specific open-source exemption from memory, the accurate position is that this is nuanced, and the details belong with qualified counsel who can read your facts against the current text.
How Article 50's transparency duties are framed
Article 50 itself frames its transparency obligations around roles and system types, not licence terms. Its duties attach to providers and deployers as described in the paragraphs:
- Article 50(1) — providers: ensure people are informed they are interacting with an AI system, subject to the 'obvious' exception.
- Article 50(2) — providers, including of general-purpose AI systems: mark synthetic audio, image, video, or text as artificially generated in a machine-readable format.
- Article 50(3) — deployers: inform people exposed to emotion-recognition or biometric-categorisation systems, and follow EU data-protection law.
- Article 50(4) — deployers: disclose deepfake image, audio, or video, and AI-generated text published to inform the public, as artificially generated or manipulated.
A practical way to approach it
Because whether you are a provider or deployer — and whether an obligation attaches — turns on the facts rather than on the model being open source, a useful first step is to map how you release or use the model and which Article 50 paragraph, if any, that role might engage. Treat that mapping as a conversation-starter with counsel, not a determination. Our free scope check walks through the four paragraphs and gives an automated, informational indication; it does not decide whether the Act, or any exemption, applies to your open-source work.
Common questions
Is open-source AI exempt from the EU AI Act?
There is no safe blanket answer. The Act treats some actors and uses differently, and whether open-source release changes your position is nuanced and fact-specific. We do not assert a specific open-source exemption here — confirm how the Act and any relevant provisions apply to your situation with qualified counsel.
See what may apply to your business
Answer seven quick questions for an automated, informational indication of which Article 50 obligations appear likely to apply — free, and not legal advice.