Toplum REHBERİ

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 dakika okuma
  • Son güncelleme
Bu sayfada3 dakika okuma
  1. Genel Bakış
  2. Derin Dalış
  3. Stratejik Etki
  4. The Future of Open-Source Exemptions in the EU AI Act
  5. Gerçek Dünya Uygulaması
  6. Riskler ve Korkuluklar
  7. Uygulama Yol Haritası
  8. Keşfetmeye Devam Edin
  9. Sık sorulan sorular

Genel Bakış

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

Derin Dalış

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.

Stratejik Etki

Risk ve güvenlik

Yıkıcı ve günlük yapay zeka zararları, kimin riskleri anladığı ve kimin harekete geçebileceğine bağlıdır.

Daha net kararlar

Kamu ve profesyonel okuryazarlık, güçlü bir güvenlik politikasının politik olarak mümkün olup olmadığını şekillendirir.

Heyecanı aşmak

Açık açıklamalar abartılı reklamların, laboratuvar halkla ilişkiler uygulamalarının ve belirsiz etik tiyatrosunun etkisi altına girmeyi azaltır.

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.

Gerçek Dünya Uygulaması

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.

Riskler ve Korkuluklar

  • Yetenekleri artırırken varoluşsal riski bilim kurgu olarak ele almak.

  • Yüzey ürün güvenliğini yüksek özerklik altında hizalamayla karıştırmak.

  • İngilizce olmayan ve uzman olmayan izleyici kitlesini yalnızca düşük kaliteli kaynaklarla bırakmak.

Uygulama Yol Haritası

  1. Ürün zararları, yanlış kullanım ve kontrol kaybı/yanlış hizalama risklerini ayırın.

  2. Hangi kanıtların zaman çizelgeleri ve ciddiyet konusundaki görüşünüzü değiştireceğini sorun.

  3. Pazarlama iddiaları yerine birincil kaynakları ve somut değerlendirmeleri tercih edin.

  4. Tek bir eylem yolu belirleyin: kariyer, politika, finansman veya beceriler; yalnızca farkındalık değil.

Keşfetmeye Devam Edin

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.

Testi başlat

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

Sık sorulan sorular

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.