Author: heise.de

Executive Summary

The Scientific Service of the Federal Parliament has published an expert opinion that refutes a widespread legal misconception: German authorities are permitted to specifically require open source software in public procurement. The experts demonstrate that a restriction to free software under certain conditions – such as IT security requirements, interoperability, or strategic further development – is legally and economically permissible. The expert opinion refers to recent judgments by the European Court of Justice that prohibit vendor lock-in situations. The Open Source Business Alliance sees this as an important signal against persistent uncertainties still present in government agencies.

People

Topics

  • Public procurement law and open source
  • Digital sovereignty
  • IT security and vendor lock-in
  • Budget allocation law

Clarus Lead

The expert opinion dispels a stubborn myth that has hampered German authorities until now: the assumption that open source requirements in public procurement are impermissible under competition law is factually false. At the same time, the decision creates pressure to act – because the European Court of Justice has prohibited direct awards to individual manufacturers in 2025 if the authority itself created dependency through initial procurement. This means the strategic choice of open source is not only permitted, but in many cases legally required.

Detailed Summary

The expert opinion differentiates public procurement law into two layers: Above EU threshold values, European competition procurement law applies with its principle of product neutrality – yet the expert opinion permits exceptions here as well. A restriction to open source is accordingly lawful if an objective, contract-related reason exists: IT security, interoperability with existing systems, or the intention to independently develop software. The contracting authority must document such reasons and be able to prove them. While the addition "or equivalent" will be customary – if it is demonstrated that no equivalent proprietary alternative exists, the authority may rely solely on free software.

Below the threshold values, national budget allocation law takes precedence, which prioritizes cost-effectiveness and economy. Since open source reduces licensing costs in the long term and minimizes migration expenses, these budget principles may even require a preference for free software. The ECJ also prohibited in 2025 the practice of direct follow-up contracts (maintenance, updates) without public tender if the original manufacturer holds exclusive copyrights. This case law forces authorities to plan foresightfully at the time of initial procurement and avoid "self-inflicted exclusivity situations" – another argument for open source. Some federal states like Thuringia have already incorporated these findings into laws; at the federal level, corresponding regulation is still lacking.

Key Statements

  • Open source procurement is permissible under clearly defined conditions (IT security, interoperability, strategic independent development) and is not discriminatory under public procurement law
  • The ECJ prohibited vendor lock-in practices in 2025 and obligates authorities to plan foresightfully already at the time of initial procurement
  • Below EU threshold values, budget efficiency may even legally require a preference for open source
  • The Open Source Business Alliance sees the expert opinion as a signal against erroneous legal interpretations that have hitherto created uncertainty among authorities

Critical Questions

  1. Evidence Quality: Does the Federal Parliament expert opinion explicitly reference the cited ECJ rulings from January 2025, or is it prospective legal interpretation? How reliable is the parallel between vendor lock-in prohibitions and open source approval?

  2. Conflicts of Interest: The Open Source Business Alliance welcomes the expert opinion – can an industry organization that commercially represents open source be regarded as an independent expert regarding its consequences?

  3. Causality and Alternatives: Are the stated prerequisites (IT security, interoperability) empirically verifiable, or do they remain interpretively open? What criteria prevent every procurement from being justified using one of these terms?

  4. Implementability: The expert opinion demands burden of proof and documentation from the contracting authority – what resources and competencies do small authorities need to prove that "no proprietary alternative exists"? Does this threaten a new form of bureaucracy?

  5. Causality – Budget Principles: Does the text claim that open source "typically" minimizes licensing costs – does this apply equally to migration expenses, training, and technical support, which are often underestimated?

  6. Risks and Side Effects: Can authorities that commit to open source be held liable for license violations or security flaws in free software if proprietary alternatives offer comparable indemnification guarantees?

  7. Scope of Application: Does the expert opinion also cover IT security authorities and intelligence agencies, or are there exceptions for sensitive areas where product neutrality sets strict limits?

Bibliography

Primary Source: Federal Parliament Expert Opinion: Authorities May Require Open Source in Public Procurement – Heise News, Author: Stefan Krempl

Supplementary Sources:

  1. European Court of Justice – Rulings on Vendor Lock-in (January 2025)
  2. Open Source Business Alliance (OSBA) – Statement on Federal Parliament Expert Opinion

Verification Status: ✓ 2025

This text was created with the assistance of an AI model. Editorial responsibility: clarus.news | Fact-checking: 2025