RegumatrixBeta
GuidesPathfinderAI RightsFreeAbout
Sign inGet Started Free

Reference

  • All Articles
  • Official Text ↗

Compliance Guides

  • Compliance Timeline
  • High-Risk Checklist
  • Healthcare AI
  • HR & Recruitment
  • Financial Services
  • GPAI / Foundation Models
  • View all guides →

Product

  • Risk Pathfinder
  • AI Rights Check
  • Get Started Free
  • About
  • Feedback
  • Contact

Legal

  • Privacy Policy
  • Terms

Regumatrix — AI compliance powered by Regulation (EU) 2024/1689

This tool is informational only and does not constitute legal advice.

Grounded in Regulation (EU) 2024/1689 · verified 4 Apr 2026
HomeComplianceOpen-Source AI
GPAI — Article 53(2)In force since August 2025

Open-Source AI and the EU AI Act: What's Exempt and What Isn't

The EU AI Act gives open-source GPAI model providers a partial exemption from the standard documentation and disclosure requirements. But the exemption is conditional, partial, and completely removed if your model crosses the systemic risk threshold.

The exemption has three limits — all three matter

First, it only works if four specific conditions are satisfied. Second, it exempts only two of the four Article 53 obligations — the other two apply to every GPAI provider regardless. Third, it disappears entirely for any model with systemic risk. Art 53(2)

Not sure whether your open-source model qualifies for the exemption? Regumatrix checks your model against Article 53(2) and returns your exact obligation set — including whether systemic risk rules apply — in 30 seconds. Check your model free →

The four conditions for the open-source exemption

Article 53(2) sets out four requirements that must all be satisfied at the same time. Miss one condition and the exemption does not apply. Art 53(2)

1

Released under a free and open-source licence

The model must be released under a licence that qualifies as free and open-source. Restrictive licences — such as those that limit commercial use, require purchase of a separate commercial licence, or restrict modification — do not satisfy this condition.

2

Licence allows access, usage, modification, and distribution

The licence must explicitly permit all four of these activities: accessing the model, using it, modifying it, and distributing it. A licence that permits use but restricts redistribution of modified versions does not qualify.

3

Weights are publicly available

The model parameters — specifically the weights — must be made publicly available. A model whose architecture is published but whose weights are kept private (sometimes called 'open architecture, closed weights') does not qualify for the exemption.

4

Architecture and usage information are publicly available

In addition to the weights, information on the model architecture and on model usage must also be made publicly available. If any of these three categories of information (weights, architecture, usage) are withheld, the exemption does not apply.

What exactly does the exemption remove?

Article 53(1) sets out four obligations for all GPAI providers. The exemption removes two of them. The other two apply to every provider — including open-source ones.

ObligationOpen-source exemption
(a) Technical documentationAnnex XI — for AI Office on request✓ Exempt (if all 4 conditions met)
(b) Downstream provider informationAnnex XII — for integrators building on your model✓ Exempt (if all 4 conditions met)
(c) Copyright compliance policyMust identify and respect rights reservations under Art 4(3) of Directive 2019/790✗ Always applies — no exemption
(d) Public training data summaryPublished using AI Office template✗ Always applies — no exemption

The exemption disappears for systemic risk models

Article 53(2) ends with an explicit carve-out: "This exception shall not apply to general-purpose AI models with systemic risks."

If your open-weights model was trained using more than 10²⁵ floating-point operations, or the Commission designates it as systemic risk on capability grounds, the full Article 53 obligation set applies — including the Annex XI technical documentation and Annex XII downstream information obligations — plus all four additional Article 55 obligations: adversarial testing, Union-level risk assessment, incident reporting, and cybersecurity. Art 53(2)Art 55

Non-EU providers: authorised representative obligation also exempt

Providers established outside the EU must normally appoint a written mandate authorised representative inside the EU before placing a GPAI model on the Union market (Article 54(1)). Article 54(6) removes this obligation for open-source GPAI providers — but with the same carve-out: the exemption is explicitly removed for open-source models that have systemic risk.

A US-based open-weights provider whose model crosses the 10²⁵ FLOPs threshold must appoint an EU-established authorised representative before placing the model on the Union market. Art 54(6)

Obligations that the open-source status never touches

The exemption exists inside Chapter V — GPAI obligations. It does not affect any other part of the EU AI Act. In particular:

  • High-risk AI system obligations (Arts 9–15) — if a downstream provider integrates your model into a high-risk AI system, they are responsible for those obligations. The open-source status of your model is irrelevant to their compliance.
  • Prohibited practice bans (Art 5) — the Art 5 prohibitions apply based on what a system does, not how its model was licensed. An open-source social scoring system is still prohibited.
  • Copyright compliance (Art 53(1)(c)) — publishing weights does not affect the obligation to have a policy to comply with EU copyright law and respect text-and-data mining opt-outs.
  • Training data summary (Art 53(1)(d)) — public release of the model does not substitute for the AI Office template training data summary, which must be published separately.

No changes are proposed under COM(2025) 836 or COM(2025) 837 for this topic.

Four situations where open-source providers discover the exemption does not apply to them

  • ·Using a licence that restricts commercial use or modification — does not qualify as free and open-source under Art 53(2)
  • ·Publishing the architecture but keeping the weights private — no weights = no exemption
  • ·Training compute is at or approaching 10²⁵ FLOPs — systemic risk classification removes the exemption in full
  • ·Assuming open-source release means no copyright or training data transparency obligations — two obligations always remain
Check your GPAI model's obligation set →

Frequently asked questions

Does releasing my model under a free licence automatically trigger the open-source exemption?

No — a free licence is necessary but not sufficient. Article 53(2) requires that all four conditions are met simultaneously: the model is released under a free and open-source licence; the licence allows access, usage, modification, and distribution; and the model parameters (weights), architecture information, and usage information are all made publicly available. If your licence restricts commercial use, or if you do not publish the weights, the exemption does not apply.

Does the open-source exemption remove all Article 53 obligations?

No. The exemption in Article 53(2) only removes the obligations in Article 53(1)(a) — the Annex XI technical documentation — and Article 53(1)(b) — the Annex XII downstream provider information package. Two obligations remain regardless of open-source status: Article 53(1)(c) — you must have a policy to comply with EU copyright law and respect rights reservations — and Article 53(1)(d) — you must publish a sufficiently detailed training data summary using the AI Office template.

I run an open-weights model. What happens if it reaches the 10²⁵ FLOPs threshold?

The exemption is explicitly disapplied for GPAI models with systemic risk. Article 53(2) states that the exception 'shall not apply to general-purpose AI models with systemic risks.' If your open-weights model crosses the 10²⁵ FLOPs compute threshold — or is designated by the Commission on capability criteria — all Article 53 obligations apply in full, plus all four Article 55 systemic risk obligations: adversarial testing, Union-level risk assessment, incident reporting to the AI Office, and cybersecurity for the model and infrastructure.

Does a non-EU open-source provider need to appoint an EU representative?

Not if the model qualifies for the open-source exemption. Article 54(6) removes the authorised representative requirement for open-source GPAI providers, mirroring the Article 53(2) exemption. However — exactly as with Art 53(2) — this exemption is also removed if the model has systemic risk. A non-EU provider of a systemic risk open-weights model must still appoint an EU-established authorised representative before placing the model on the Union market.

Does open-source release affect obligations if my model is integrated into a high-risk AI system?

The open-source exemption applies to your obligations as the GPAI model provider. It does not affect the obligations of a downstream provider who integrates your GPAI model into a high-risk AI system. That downstream provider must comply with Articles 9–15 regardless of whether the underlying model is open-source. As the GPAI provider, you are not responsible for downstream high-risk deployments — but you should consider what information downstream providers need to meet their own obligations, even though you are exempt from Annex XII.

Related guides

GPAI model obligations overviewGPAI systemic risk obligationsAI provider obligationsEU AI Act fines & penaltiesCOM(2025) 836 — what changesEU AI Act for SMEs & startups

Does your open-source model qualify for the exemption?

Regumatrix checks your GPAI model against the Article 53(2) conditions, verifies whether the systemic risk carve-out applies, and returns your exact obligation set — showing which requirements you are exempt from and which remain. Full cited report in around 30 seconds.

  • Open-source exemption conditions — pass/fail for each of the four
  • Systemic risk check — compute threshold and Annex XIII criteria
  • Which Art 53 obligations remain regardless of open-source status
  • Authorised representative check for non-EU providers
  • Full report with Article citations — no credit card, ~30 seconds
Get your free compliance report →GPAI overview