The "Fack" - Frequently Asked Questions

Here are the answers to some common questions about The EuroStack Directory Project and related initiatives, its principles, and its goals. If you have a question that isn't answered here, please feel free to contact us. If it's a good question, we might even add it to this FAQ!

We hope this FAQ clarifies the dynamic interplay of principles within The EuroStack Directory Project.

Q: Who did come up with the "Euro Stack" name?

A: The name "Euro Stack" was introduced during the "Toward European Digital Independence: Building the Euro Stack" that took place in September 2024 in Brussels.

We found the name catchy and concept intriguing, and we decided to expand on the original concepts developed during the conference, and adding our own vision and goals, specially around Open Source, since we believe it is a key component of the European digital sovereignty and it was not enough emphasized during the conference, in our opinion.

We also decided to DO something about it, and not just talk about it. "Everything already exists in Europe," as Euclidia motto says, so we created the EuroStack Directory Project (this website), to promote European digital solutions, and Open Source, and to help businesses and public administrations to find and adopt these solutions.

Q: The EuroStack Directory emphasizes both "European-made" solutions and "Open Source First." How do these two priorities work together, especially when excellent Open Source solutions might originate outside of Europe?

A: We recognize the immense value of Open Source software for achieving digital sovereignty, transparency, and innovation. "Open Source First" is a foundational principle. The emphasis on "European-made" within the EuroStack Directory Project (ESDP) and other initiatives (Euclidia, Cloudrepo...) is about fostering a thriving European digital ecosystem, which we believe should be grounded on Open Source technologies and interoperable services. We aim to:

• Prioritize and support European contributions to global Open Source projects: This strengthens European influence and ensures our values are embedded in widely used technologies.
• Cultivate European-led Open Source projects: This is crucial for strategic areas where we need to ensure complete control and independence.
• Embrace valuable Open Source solutions, regardless of origin, while actively working to increase European expertise and contributions: We recognize that the Open Source world is interconnected. We will leverage the best solutions available while simultaneously building our capacity to develop, maintain, and contribute to critical projects. The "European-made" label in the ESDP will evolve to encompass projects significantly driven or supported by European entities, even if they have global origins. We prefer Open Source solutions coming from outside of Europe to non-Open Source solutions coming from outside of Europe.

We see "European-made" and "Open Source First" as complementary. Our goal is a vibrant European Open Source ecosystem that both contributes to and benefits from the global Open Source movement and the European tech ecosystem.

Q: How can The EuroStack Directory reconcile "Vendor Neutrality" with its stated goals of "Strategic Investment" in European technologies and "Supporting SMEs"? Isn't there a risk of creating an unfair advantage for European companies?

A: The EuroStack Directory is committed to a competitive and open digital market, both within Europe and globally. "Vendor Neutrality" remains a key principle, especially in the context of interactions between European businesses. However, we also recognize the need to address the current imbalance in the global digital market, where some large, non-European tech companies benefit from significant advantages. These advantages often stem from:

• Market Power: Decades of market dominance have created monopolies or near-monopolies in certain sectors, making it difficult for new entrants to compete. This dominance has often been fueled by many anti-competitive practices that have been challenged and, in some cases, penalized by EU and US courts.
• Asymmetric Regulations and Subsidies: Differences in regulations and the availability of state aid in other countries, notably the US, can create an uneven playing field. This includes protectionist measures that favor domestic companies.
• Extraterritorial Laws: Laws like the US CLOUD Act create legal uncertainties and risks for European businesses relying on non-European providers.

Therefore, The EuroStack Directory Project's initiatives to support European companies, especially SMEs, are not about creating a general unfair advantage, but about counteracting the existing distortions in the market and creating a more level playing field globally. The focus is on:

• Strategic Investment: Targeted at areas critical for digital sovereignty where European capabilities need to be strengthened to reduce reliance on dominant non-European players.
• Supporting SMEs: Leveling the playing field for smaller European businesses to compete against larger, established players, both European and non-European, by fostering a more diverse and competitive market. This includes ensuring they have fair access to public procurement opportunities.
• Temporary Measures: Public procurement policies that initially disfavor non-European providers are a strategic, temporary measure. They aim to nurture a nascent European Open Source ecosystem capable of competing globally on its own merits. This will gradually shift towards emphasizing quality, innovation, and cost-effectiveness as the European ecosystem matures.

The real risk we aim to mitigate is creating an unfair advantage for some European companies over other European companies. We are committed to transparency, open competition, and merit-based selection processes within Europe to ensure a level playing field for all European businesses. Our ultimate goal is a thriving European digital ecosystem that can compete globally based on innovation, quality, and adherence to European values, without the need for long-term preferential treatment. We aim to grow the European digital ecosystem as a whole, and prevent situations where only a handful of European companies (the "European champions") would unduly benefit from this initiative.

We, at the EuroStack Directory Project and as a partner of The EuroStack Initiative, seek to create a fair and competitive digital market, both within Europe and globally, by addressing the current imbalances and ensuring that European companies have the opportunity to thrive based on their merits.

Q: The EuroStack Directory Project promotes both "Openness" and "Control." How can these seemingly oposing concepts be balanced in practice, particularly regarding critical infrastructure?

A: "Openness" and "Control" are both essential for a secure and trustworthy digital future. We believe they can be mutually reinforcing:

• Openness (in code, standards, and collaboration) fosters transparency, which is crucial for building trust and identifying vulnerabilities. It allows for broader scrutiny and contributions, leading to more secure and robust systems.
• Control over critical infrastructure ensures that Europe has the autonomy to make decisions that align with its values and strategic interests. It allows us to protect our data and systems from undue external influence.

The key is to define clear boundaries and implement mechanisms that ensure both openness and control where appropriate. For example, core infrastructure components might be developed under stricter control for security reasons, while still adhering to open standards and interfaces to ensure interoperability. We will strive for transparency even in areas where control is paramount, ensuring accountability and public trust.

Q: How does the "Public Money, Public Code" principle work in practice, and how does it relate to The EuroStack Directory Project's support for existing Open Source projects?

A: "Public Money, Public Code" is a principle, developed by the FSFE and endorsed by many European organisations, including The EuroStack Directory Project. It reflects our commitment to transparency, accountability, and maximizing the public benefit from public investment. It means that software developed with public funds for the public sector must be made publicly available under a Free and Open Source Software license.

Here's how it works:

• Requirement for Public Procurement: When public bodies procure software development services, they will be required to include clauses in their contracts mandating that the resulting code be released under an approved Open Source license (e.g., EUPL or other OSI-approved licenses).
• Direct Public Funding: When software development is directly funded by public grants or other mechanisms, the grant agreements will stipulate the same Open Source licensing requirement.
• Benefits: This approach ensures that:
  • Taxpayer money is used efficiently: Publicly funded code becomes a shared resource that can be reused and improved by others, avoiding duplication of effort and reducing costs.
  • Transparency and Accountability: Open Source code allows for public scrutiny, enhancing trust and enabling independent security audits.
  • Innovation is fostered: Open Source code creates a foundation for further development and innovation by a wider community, including businesses, researchers, and citizens.
  • Vendor Lock-in is avoided: Public bodies are not tied to specific vendors for maintenance and development, promoting competition and flexibility.

Relationship with Existing Open Source Projects:

"Public Money, Public Code" primarily applies to new software development funded by public money. It does not retroactively apply to existing Open Source projects developed without public funding. However, we recognize the strategic importance of many existing projects and intends to:

• Identify and Prioritize: We will identify existing Open Source projects that are critical to European digital sovereignty and prioritize them for support.
• Encourage Public Sector Contributions: Public bodies will be encouraged to contribute to these projects, either through code contributions, financial support, or other means. This strengthens the projects and aligns them with public sector needs. Public administrations will also be encouraged to migrate to existing Open Source solutions.
• Incorporate Existing Projects into the EuroStack: Where appropriate, existing, strategically important projects will be incorporated into the EuroStack framework, ensuring their continued development and integration with other components.
• Fund development of Open Source alternatives to widely used proprietary solutions, with the express intent of making them as good or better, in order to encourage migration to these solutions.

In summary, "Public Money, Public Code" is a forward-looking principle that ensures publicly funded software benefits the public. While it doesn't directly apply to existing projects developed without public funds, The EuroStack Directory Project recognizes their value and seeks to support and integrate them into a broader strategy for European digital sovereignty. The main idea is to make sure that, from now on, as much code as possible, developed for public administrations, with public money, is made available as Open Source.

Q: How will The EuroStack Directory Project balance the need for rapid progress with the comprehensive, long-term nature of building a truly sovereign digital infrastructure? How will it manage expectations, especially regarding the potential for initial higher costs or less feature-rich solutions from European providers?

A: The EuroStack Directory Project recognizes both the urgency of reducing reliance on non-European tech giants and the long-term nature of building a robust and sustainable digital infrastructure. A key realization is that Europe already possesses a wealth of innovative and mature Open Source solutions that can contribute significantly to digital sovereignty. This was already the focus of pionneering initiatives like Euclidia or the Cloudrepo directory project. The EuroStack Directory Project (ESDP) will play a crucial role in showcasing these existing solutions, demonstrating that we are not starting from scratch.

Here's how we will proceed:

• Highlight Existing European Excellence: The ESDP will act as a central repository, showcasing the vast array of high-quality Open Source software developed and maintained within Europe. This will immediately challenge the perception that European solutions are less mature or feature-rich. We will demonstrate that viable, and often superior, alternatives to non-European proprietary software already exist within our ecosystem.
• Adopt a Phased Approach: We will prioritize actions that can deliver tangible results in the short term, with a strong emphasis on promoting the adoption of readily available European Open Source solutions identified through the ESDP. Simultaneously, we will work on longer-term goals like fostering a more robust and interconnected European Open Source ecosystem.
• Clearly Communicate Our Roadmap and Milestones: We will be transparent about our goals, highlighting the immediate benefits of adopting existing European solutions while also outlining the longer-term vision for the EuroStack. This includes acknowledging that a transition period may involve some adjustments.
• Focus on Building a Strong Foundation: We will prioritize interoperability, security, and sustainability from the outset. The ESDP will help identify solutions that meet these criteria, ensuring that the EuroStack is built on a solid foundation of existing, proven technologies.
• Foster a Culture of Continuous Improvement: We will regularly evaluate our progress, adapt our strategy as needed, and embrace feedback from stakeholders. The ESDP will be a dynamic resource, constantly updated to reflect the latest developments and additions to the European Open Source landscape.

By showcasing the breadth and depth of existing European Open Source solutions through the ESDP, we are confident that we can accelerate the adoption of these solutions, achieve meaningful progress in the short term, and build a strong foundation for long-term digital sovereignty. The initial focus on readily available solutions will help manage expectations and demonstrate the immediate value proposition of the EuroStack Directory Project. We believe that investing in and promoting our existing European Open Source ecosystem is crucial for breaking dependence, ensuring a competitive, innovative, and resilient digital future, and fostering a sense of European pride and ownership in the digital realm.

Q: Digital Public Infrastructures (DPIs) are a crucial concept related to the Euro Stack and the broader discussion of digital sovereignty and governance. Here's a breakdown:

*A: DPIs are societal-scale, digital systems that provide essential functions and services to the public. They are analogous to physical public infrastructures like roads, electricity grids, or water systems, but exist in the digital realm. They are foundational platforms upon which other services and applications can be built. They have three main layers, starting with the technology, governed by a community and following rules.

Key Characteristics:

• Societal Scale: DPIs operate at a large scale, serving entire populations or significant segments thereof. They are not limited to individual organizations or small groups.
• Essential Functions: They provide fundamental services that are considered essential for participation in modern society and the economy.
• Public Good Orientation: DPIs are designed to serve the public interest, promoting inclusion, accessibility, and equitable access to services. While they can be built and operated by private entities, their purpose is to serve a public good.
• Interoperability: DPIs are designed to be interoperable, meaning they can connect and exchange data with other systems. This avoids silos and promotes the creation of a broader digital ecosystem.
• Openness and Standards: Ideally, DPIs are built on open standards and, often, open-source software. This promotes transparency, security, and avoids vendor lock-in. Openness also allows for innovation and the development of new services on top of the DPI.
• Governance Framework: DPIs require a robust governance framework to ensure accountability, security, privacy, and responsible use. This framework may involve government regulation, community oversight, or a combination of both.
• Modularity and Extensibility: Good DPIs are designed to be modular and extensible. This means they can be adapted to changing needs and new technologies can be integrated over time.
• Resilience: DPIs must be resilient to failures, attacks, and disruptions. This requires careful design, robust security measures, and redundancy.

Examples of DPIs (and potential DPIs):

• Digital Identity Systems: Secure and verifiable digital identities for citizens (e.g., Estonia's e-ID system, India's Aadhaar). This is a foundational DPI, allowing individuals to access online services securely.
• Payment Systems: Nationwide digital payment systems (e.g., India's UPI, Brazil's Pix). These facilitate secure and efficient financial transactions.
• Data Exchange Layers: Platforms for secure and privacy-preserving data sharing between government agencies, businesses, and citizens (e.g., Estonia's X-Road).
• Public Health Systems: Digital infrastructure for managing public health data, tracking disease outbreaks, and delivering healthcare services.
• Education Platforms: Online learning platforms and resources provided by governments for public education.
• E-Government Portals: Centralized portals for accessing government services online (e.g., applying for permits, paying taxes).
• Land registry: Systems for registering land titles and property ownership
• Open networks for commerce: Platforms where multiple sellers and service providers can provide the same service.

DPIs and the Euro Stack:

The Euro Stack, as envisionned by our initiative, and others, can be seen as a collection of potential DPIs, or at least as infrastructure that could support the development of European DPIs. The key components of the Euro Stack – cloud infrastructure, digital identity, payment systems, data platforms – all align with the concept of DPIs.

The emphasis on European control, open standards, and public good orientation within the Euro Stack discussion directly reflects the core principles of DPIs. The goal is to create digital infrastructures that are not controlled by a small number of private companies, but are instead designed to serve the public interest and promote European digital sovereignty.

Why DPIs are Important:

• Inclusion and Equity: DPIs can help ensure that all citizens have access to essential digital services, regardless of their socioeconomic status or location.
• Economic Growth: DPIs can foster innovation and economic growth by providing a platform for businesses to develop and deliver new services.
• Efficiency and Transparency: DPIs can improve the efficiency and transparency of government operations.
• Resilience and Security: Well-designed DPIs can enhance national resilience and security by reducing dependence on foreign providers and protecting critical infrastructure.
• Citizen Empowerment: DPIs can empower citizens by giving them greater control over their data and enabling them to participate more fully in the digital economy.
• Competition: DPIs can create a level playing field, fostering competition and avoiding monopolies in the digital space.

Where does the Concept of DPIs Come From?

• Public Utilities: The idea of essential public services, like water, electricity, and telecommunications, provided as utilities, is a historical precedent. DPIs are the digital equivalent of these traditional utilities.
• Internet as a Public Good: Early internet pioneers envisioned the internet as a global, open, and decentralized network for the public good. This vision contributed to the idea of shared digital infrastructure.
• Free / Open Source Software: The Free and Open Source Software movement, with its emphasis on collaborative development and shared access to code, laid the groundwork for the idea of open and interoperable digital infrastructures.
• Estonia: Estonia is often cited as a pioneer in developing digital public services and a digital society. Their X-Road data exchange layer, e-ID system, and other initiatives demonstrated the potential of interconnected digital government services. While they didn't use the term "DPI" explicitly, their approach was highly influential.
• India: India's experience with Aadhaar (a biometric digital identity system) and UPI (Unified Payments Interface) is a crucial example of DPIs at scale. These systems, though not without controversy, have had a transformative impact on financial inclusion and digital service delivery in India. The India Stack, a collection of APIs built around Aadhaar and UPI, is often considered a prime example of the DPI approach.
• The term "Digital Public Infrastructure" itself, and the more precise definition we use today, gained traction more recently (within the last decade). It reflects a growing recognition of the need for a more systematic and strategic approach to building and governing essential digital systems.
• Organizations like the World Bank, the United Nations, and the Digital Public Goods Alliance (DPGA) have helped to formalize the concept and promote DPIs as a key element of sustainable development.
• The G20 has also increasingly recognized the importance of DPIs for inclusive growth and resilience.

Additional Questions (with Short Answers)

How will you ensure that the ESDP doesn't become a static catalog but remains a dynamic resource that accurately reflects the rapidly evolving Open Source landscape?

A: The ESDP will be maintained through a combination of automated updates, community contributions, and active curation by a dedicated team, ensuring it remains current and reflects the latest developments in the European Open Source ecosystem. Regular reviews and updates to the inclusion criteria will also be conducted.

How will the EuroStack Directory Project address potential conflicts or competition between different European Open Source projects that aim to solve similar problems?

A: We will encourage collaboration and interoperability between projects, promoting a "coopetition" model where projects can both compete and cooperate. The ESDP provides transparent information about different solutions, allowing users to choose the best option for their needs. We will eventually promote the creation of a specific label attesting that a given solution follows the principles of the EuroStack Initiative.

Criteria will likely include factors such as the location of the project's governing body and development team, the origin of funding, etc. The focus will be on projects that are significantly driven by or substantially contribute to the European Open Source ecosystem. These criteria will be made public and reviewed periodically.

Cf. Drafting European Sovereignty Criteria for Software and Digital Systems for the current state or our reflection.

What metrics will be used to measure the success of your initiative beyond the number of solutions listed in the ESDP or the adoption of Open Source by public administrations?

A: Success will be measured by factors such as the growth of the European Open Source ecosystem, increased collaboration between projects, cost savings achieved by public administrations, improved digital sovereignty, and the level of citizen engagement with Open Source solutions. Qualitative factors will also be considered, such as user satisfaction and the perceived value of the ESDP.

How will the you ensure the long-term sustainability of the ESDP and other related projects, considering potential funding challenges and the need for ongoing maintenance and development?

A: We will explore diverse funding models, including public funding, membership fees, and contributions from the private sector. It will also promote the development of sustainable business models around European Open Source projects, for example through public procurement and strategic investment in dual licensing. It will also seek to establish partnerships with existing EU bodies and agencies.

How do you plan to address potential resistance from established software vendors, both European and non-European, who may see it as a threat to their business models?

A: We will will emphasize the benefits of Open Source for all stakeholders, including commercial vendors. It will highlight opportunities for collaboration and innovation within the EuroStack framework, and promote the development of new business models based on Open Source services and support. It will also stress that public procurement should be based on various criteria, including quality, security and cost, and not only on the type of license.

What role does the EuroStack Directory Project envision for itself in shaping the future development of Open Source software, beyond simply promoting existing solutions?

A: We aim to influence the direction of Open Source development by identifying strategic areas where European capabilities need to be strengthened, fostering collaboration on key projects, and promoting the adoption of European values and standards within the global Open Source community.

How will you address the risk of creating a "European bubble" that isolates itself from the global Open Source ecosystem, potentially missing out on valuable innovations and collaborations?

A: We will actively engage with the global Open Source community, promoting cross-border collaboration and knowledge sharing. The ESDP will include mechanisms for linking to relevant non-European projects, and we will encourage European developers to contribute to global projects.

How will you ensure that "strategic investment" in European technologies does not inadvertently lead to the creation of "white elephant" projects that are ultimately unsustainable or fail to meet the needs of users?

A: "Strategic investment" will be guided by clear criteria, including user needs, market analysis, and the potential for long-term sustainability. Besides, we do not plan to invest directly in projects, but rather to promote them and to help them find funding. The ESDP will include feedback mechanisms to ensure that listed projects are meeting user expectations and needs.