Gids voor de samenleving

Open-Source Exemptions in the EU AI Act

The EU AI Act contains limited exclusions and exemptions for free and open-source software and models, but “open source” is not a blanket exemption.

  • 3 minuten lezen
  • Laatst bijgewerkt
Op deze pagina3 minuten lezen
  1. Overzicht
  2. Diepe duik
  3. Strategische impact
  4. The Future of Open-Source Exemptions in the EU AI Act
  5. Implementatie in de echte wereld
  6. Risico's en vangrails
  7. Implementatie routekaart
  8. Blijf verkennen
  9. Veelgestelde vragen

Overzicht

High-risk systems, prohibited practices, certain transparency duties, and systemic-risk model obligations can still apply.

Diepe duik

Article 2(12) excludes certain free and open-source AI systems from the Regulation only where they are released under qualifying licences and are not placed on the market or put into service as high-risk systems, prohibited practices, or systems subject to specified transparency obligations. This provision is limited: it does not mean that every open-source project falls outside the Act, and it does not remove duties that may attach when another actor integrates a component into a regulated product or use. The Act has a separate, narrower rule for providers of general-purpose AI models. Some documentation and downstream-information obligations in Article 53(1)(a) and (b) do not apply when model parameters, including weights, architecture information, and usage information are publicly available under a free and open-source licence. The exemption does not cover the copyright-policy and training-content-summary duties in Article 53(1)(c) and (d). It also does not apply to a GPAI model presenting systemic risk; the systemic-risk obligations remain relevant. “Free” licensing is not the only condition. Public availability and what is actually released matter. A model card alone is not the weights; a source-code repository may not include model parameters. The legal treatment can also differ between a model and an AI system built using that model. Commercial distribution does not always erase every open-source provision, but monetized components and service arrangements can affect whether a condition is met. Read the relevant article and recitals rather than relying on a project’s label. Regulation 2026/1744 also amended Article 25(4): its written-information and assistance agreement duty does not apply to third parties publicly providing tools, services, processes, or components (but not GPAI models) under a free and open-source licence. This narrow exception does not exempt the integrated high-risk system provider; track each component and role separately.

Strategische impact

Risico en veiligheid

Catastrofale en alledaagse schade door AI hangt af van wie de risico's begrijpt en wie kan handelen.

Duidelijkere beslissingen

Publieke en professionele geletterdheid bepalen of een krachtig veiligheidsbeleid politiek mogelijk is.

Door de hype heen snijden

Duidelijke verklaringen verminderen de kans op hypes, laboratorium-PR en vaag ethisch theater.

The Future of Open-Source Exemptions in the EU AI Act

Open and collaborative AI development will continue to evolve, and the AI Act itself changed through Regulation 2026/1744. The Commission’s implementation materials and consolidated EUR-Lex text should be checked before relying on an exception. Maintain versioned release records, especially when new monetization, hosted inference, support services, or downstream features are added. A change in the package can alter both legal classification and who carries a duty. Review the licence and package contents when a project adds hosted inference, proprietary weights, or a downstream integration.

Implementatie in de echte wereld

A project releases weights and architecture under an open licence but separately checks whether systemic-risk duties apply.

A company integrates an open model into a CV-ranking service and assesses the resulting system’s high-risk purpose.

A maintainer documents paid hosting and support separately from the free code release.

A model provider keeps copyright-policy and training-content-summary work in scope despite a limited transparency exemption.

Risico's en vangrails

  • Existentieel risico behandelen als sciencefiction, terwijl capaciteiten zich vermenigvuldigen.

  • De veiligheid van oppervlakteproducten verwarren met uitlijning onder hoge autonomie.

  • Hierdoor blijven niet-Engelstalige en niet-deskundige doelgroepen alleen bronnen van lage kwaliteit over.

Implementatie routekaart

  1. Afzonderlijke risico's voor productschade, misbruik en verlies van controle/verkeerde uitlijning.

  2. Vraag welk bewijs uw kijk op tijdlijnen en ernst zou veranderen.

  3. Geef de voorkeur aan primaire bronnen en concrete evaluaties boven marketingclaims.

  4. Identificeer één actiepad: carrière, beleid, financiering of vaardigheden – niet alleen bewustwording.

Blijf verkennen

Free newsletter

Get the daily AI briefing

Three verified AI stories every weekday morning, written in plain English. Free forever, no ads.

One email each weekday. Unsubscribe in one click. We never sell or share your address.

Test yourself

Take the Open-Source Exemptions in the EU AI Act quiz

Instant feedback on every answer, and a shareable certificate with a verifiable ID once you pass a course.

Quiz starten

Support free AI education. AI Understanding is a 501(c)(3) nonprofit — no ads, no paywall, ever. Make a donation

Veelgestelde vragen

What is Open-Source Exemptions in the EU AI Act?

The EU AI Act contains limited exclusions and exemptions for free and open-source software and models, but “open source” is not a blanket exemption. High-risk systems, prohibited practices, certain transparency duties, and systemic-risk model obligations can still apply.

Does an open-source label exempt every AI Act obligation?

The provisions are conditional and differ by system and model duties.

Does releasing a base model under an open licence decide whether a hiring product is high-risk?

A model and an AI system are distinct objects under the Act.

Which release facts should a maintainer document?

A component-level record supports a precise scope assessment.

Why check the consolidated Regulation after the Digital Omnibus?

The amendments affect current statutory text and interpretation.