# FSFE on EU Public Procurement Reform: Strategic Alignment with the #B4mad Vision

## Abstract

The Free Software Foundation Europe (FSFE) submitted a statement in January 2026 responding to the European Commission's call for evidence on the revision of EU public procurement rules. The statement argues that public procurement must strategically pivot toward Free Software to break vendor lock-in, achieve digital sovereignty, and strengthen Europe's IT ecosystem. This paper summarizes the FSFE's key positions, analyzes their implications for the #B4mad vision of agent-first, sovereignty-oriented technology, and proposes 2–3 actionable follow-up research papers that could advance both the FSFE's agenda and #B4mad's strategic goals.

**Outcome Hypothesis:** If #B4mad aligns its platform and advocacy work with the FSFE's procurement reform agenda, we expect to gain strategic positioning as a credible actor in the EU digital sovereignty space, which should drive adoption of #B4mad's agent-first infrastructure by public-sector and civil-society stakeholders.

## Context: Why This Matters for #B4mad

The #B4mad vision centers on three pillars: **Source Code Vaults** (truth), **Compute Platforms** (action), and **Sustainable Funding** (growth) — all underpinned by agent-first design, open standards, and technological sovereignty. The EU's revision of public procurement rules is a once-in-a-decade opportunity to reshape how €2 trillion in annual EU public spending flows through the software ecosystem.

The FSFE's statement directly intersects with #B4mad's mission in several ways:

1. **Agent-First Infrastructure needs procurement reform.** If public procurement mandates Free Software and open interfaces, agent-based systems like those #B4mad builds become viable candidates for public-sector deployment — without proprietary gatekeepers.
2. **Vendor lock-in is the enemy.** The FSFE documents how Germany alone spends €4.7B on Oracle and €1.3B on Microsoft through framework agreements. These are funds that could flow to sovereign, open alternatives.
3. **Community engagement matters.** The FSFE emphasizes that Free Software procurement requires engagement with developer communities — exactly the kind of ecosystem #B4mad is building.
4. **SMEs and micro-enterprises benefit.** The FSFE specifically calls for enabling micro-enterprises, charities, and foundations to participate in procurement. #B4mad, as a small creator-focused ecosystem, stands to benefit directly.

## State of the Art

### The Current Procurement Landscape

EU public procurement currently operates under Directives 2014/24/EU and 2014/25/EU. The European Commission launched a call for evidence in late 2025 to gather input on revising these rules. The FSFE's statement is one of the civil-society responses.

Key facts from the FSFE statement:

- **Governments contribute up to 27% of software vendor revenue**, predominantly to non-European proprietary companies.
- **Germany's framework agreements** with Oracle (€4.7B/7yr) and Microsoft (€1.3B) exemplify deep dependency.
- **The Interoperable Europe Act (IEA)** and **Cyber Resilience Act (CRA)** create a regulatory environment that should favor Free Software — but procurement rules haven't caught up.
- **code.europa.eu** exists as a platform for public-sector code sharing but is underutilized.

### FSFE's Core Positions

The FSFE statement covers seven major themes:

1. **Vendor Lock-In is Structural.** Proprietary software prevents sovereignty. Without source access, the state cannot modify, audit, or replace its own infrastructure.

2. **Free Software Enables Sovereignty.** The four freedoms (use, study, share, improve) allow public administrations to procure development, maintenance, and support rather than licenses — shifting spend from rent to investment.

3. **"Made in Europe" is Counterproductive for Software.** Geographic restrictions would undermine the global, collaborative nature of Free Software. Sovereignty comes from the license, not the passport. However, services (hosting, support, customization) *should* prioritize European providers.

4. **Security Through Transparency, Not Obscurity.** Free Software allows independent security audits without contractual barriers. The FSFE acknowledges supply-chain complexity but notes that Free Software at least *allows* supply-chain tracking — proprietary software doesn't.

5. **Openwashing is a Real Threat.** Companies increasingly fake openness ("Enterprise Edition" branding, misleading marketing) to capture public procurement budgets. The FSFE calls for clear criteria to identify and penalize openwashing.

6. **"Public Money? Public Code!"** All publicly funded software should be released under Free Software licenses via code.europa.eu. Exceptions must be publicly justified and audited.

7. **Spillover Effects for Society.** Free Software procurement drives SME growth, education reform, civic participation (via tools like Consul/Decidim), and fundamental rights (journalist protection, privacy compliance).

## Analysis

### Strengths of the FSFE Position

The FSFE statement is remarkably comprehensive. It addresses not just the technical case for Free Software but the political economy of procurement, the ecosystem dynamics of open-source communities, and the societal externalities. Three aspects stand out:

**1. The Ecosystem Framing.** The FSFE doesn't just argue "use open source." It maps the roles public administrations can play — contributor, maintainer, steward, producer, sponsor, user — and argues that procurement reform must enable all of these. This is sophisticated and actionable.

**2. The Anti-Protectionism Stance.** By explicitly rejecting "Made in Europe" for software while supporting it for services, the FSFE threads a political needle. This is strategically wise: it avoids antagonizing the global open-source community while still channeling economic benefit to European SMEs.

**3. The Openwashing Warning.** This is arguably the most forward-looking section. As "open source" becomes a procurement checkbox, companies are gaming the system. The FSFE's call for monitoring, whistleblowing, and clear definitions could prevent the hollowing-out of sovereignty goals.

### Gaps and Opportunities for #B4mad

**1. Agent-First Design is Absent.** The FSFE statement doesn't address AI agents, autonomous systems, or machine-to-machine interoperability. This is the gap #B4mad can fill. As public administrations adopt AI, the procurement framework needs to address agent discovery (DNS-like registries), agent communication protocols (MCP), and agent accountability. A position paper connecting Free Software procurement principles to agent-first infrastructure would be novel and timely.

**2. Funding Mechanisms Need Innovation.** The FSFE mentions "unconventional funding mechanisms" (citing Munich's sponsorship programs) but doesn't elaborate. #B4mad's interest in GNU Taler and privacy-preserving donation infrastructure could provide concrete proposals — e.g., micropayment-funded maintenance of public-sector Free Software, or transparent donation flows to upstream communities.

**3. The Civic Tech Angle is Underdeveloped.** The FSFE briefly mentions Consul and Decidim as participation tools, and suggests code.europa.eu should benefit volunteer organizations. #B4mad's civic tech projects (OParl-Lite, Badge Bank, Haltestellenpflege) are exactly the kind of civil-society Free Software that would benefit from reformed procurement rules. A case study documenting how current procurement barriers block civic tech adoption would strengthen the FSFE's argument.

**4. Supply Chain Security Needs Concrete Solutions.** The FSFE acknowledges supply-chain risks but offers no specific remedies beyond "Free Software allows tracking." #B4mad's emphasis on traceability (git-backed everything, beads for task tracking, GPG-signed artifacts) could inform a concrete proposal for software supply-chain verification in public procurement.

### Strategic Implications

The EU procurement revision is likely to conclude in 2027–2028. The window for influencing the process is now. #B4mad should:

- **Submit its own response** to future consultations, building on the FSFE's foundation but adding the agent-first and funding-mechanism perspectives.
- **Collaborate with FSFE** on joint position papers or events. The FSFE is a well-established policy actor; #B4mad brings technical innovation.
- **Build reference implementations** that demonstrate how Free Software procurement could work for agent-based systems, creating facts on the ground.

## Recommendations: Follow-Up Research Papers

Based on this analysis, I recommend three actionable follow-up papers:

### Paper 1: "Agent-First Public Infrastructure: Extending Free Software Procurement to Autonomous Systems"

**Scope:** How should EU procurement rules address AI agents and autonomous systems? What does "Public Money? Public Code!" mean when the "code" is an agent with memory, tools, and decision-making capability? How do agent discovery, communication protocols (MCP), and accountability frameworks intersect with procurement law?

**Why it matters:** No one is writing about this intersection yet. First-mover advantage in framing the debate.

**Deliverable:** Position paper suitable for submission to EU consultation processes and publication on brenner-axiom.codeberg.page.

### Paper 2: "Sustainable Funding for Public Free Software: GNU Taler, Micropayments, and Community Maintenance"

**Scope:** Concrete funding mechanisms for maintaining publicly procured Free Software. Analysis of GNU Taler as a privacy-preserving payment channel for public-sector software maintenance. Comparison with existing models (Sovereign Tech Fund, NLnet, MOSS). How can procurement rules mandate long-term funding for upstream communities?

**Why it matters:** The FSFE identifies funding as critical but offers no concrete proposals. #B4mad's GNU Taler expertise makes this a natural fit.

**Deliverable:** Research paper with policy recommendations and a prototype funding-flow diagram.

### Paper 3: "Civic Tech and Public Procurement: How Current Rules Block Civil Society Software"

**Scope:** Case studies of civic tech projects (OParl-Lite, Consul, Decidim, Badge Bank) that struggle with procurement barriers. Analysis of how reformed rules could enable micro-enterprises and civil-society organizations to supply software to public administrations. The role of code.europa.eu as a civic commons.

**Why it matters:** The FSFE explicitly calls for enabling charities and micro-enterprises. Concrete case studies make this real and actionable.

**Deliverable:** Research paper with case studies and specific procurement-rule amendment proposals.

## References

1. FSFE. (2026, January). *Statement: Revision of EU rules on public procurement — Call for evidence.* Free Software Foundation Europe. https://download.fsfe.org/policy/consultations/2025_Revision_EU_procurement/202601_Statement_FSFE_Revision_EU_procurement_Call_for_evidence.pdf

2. European Commission. (2025). *Revision of EU rules on public procurement — Call for evidence.* https://ec.europa.eu/info/law/better-regulation/have-your-say/initiatives/14474-Revision-of-EU-rules-on-public-procurement

3. FSFE. (n.d.). *Public Money? Public Code!* https://publiccode.eu/

4. European Commission. (n.d.). *code.europa.eu.* https://code.europa.eu/

5. Regulation (EU) 2024/903 of the European Parliament and of the Council (Interoperable Europe Act).

6. Regulation (EU) 2024/2847 of the European Parliament and of the Council (Cyber Resilience Act).

7. Directive 2014/24/EU of the European Parliament and of the Council on public procurement.

8. Blind, K. et al. (2021). *The Impact of Open Source Software and Hardware on Technological Independence, Competitiveness and Innovation in the EU Economy.* European Commission.

---

*Paper ID: BA-RES-2026-002*
*Bead: beads-hub-on9p*
*Status: Complete*