1. All dimensions of digital sovereignty of platforms must be pursued!

1. data sovereigntyControl over the sharing of data and metadata, compliance with the GDPR
2. provider interchangeability: Multiple providers offering the same open interfaces and meeting the same strong technical standards make it easy for users to switch.
3. Technical excellence: Open-source code developed openly (four opens) for the entire infrastructure stack
4. Competence and transparencyOperational experience is shared transparently, enabling medium-sized companies to successfully operate (and consolidate) their own infrastructure.

2. Data sovereignty should not be confused with digital sovereignty.

1. Many proprietary offerings disguise their offerings as digitally sovereign, but at best offer data sovereignty. The term „sovereign-washing“ comes to mind, as compliance with the requirements of the GDPR and similar regulations is part of digital sovereignty, one of its dimensions, but not its only one.
2. A platform that is not based on open standards and does not have open APIs offers neither the possibility to switch providers, nor federation, nor the option to operate a cloud yourself, but is completely dependent on the long-term availability of the sole provider.
3. Proprietary cloud platforms that are operated on-premises or in local data centres that do not belong to the platform provider are still dependent on updates and continuity from the sole provider.

3. Creation one European hyperscalers („Cloud Airbus“) is none A worthy goal!

1. With only one EU hyperscaler, the dependencies would be just as strong as with the existing (US/CN) hyperscalers; we would once again have a monopoly.
2. Even if legal access were somewhat better and there were slightly more value creation in Europe, a monopoly would probably not deliver the quality, innovation and cost efficiency that would be desirable.
3. European providers have a better chance of success if they work together on standards and even basic technologies and are willing to exist in an ecosystem of providers that compete with each other further up the value chain.

4. European industry is strong and resilient because it is highly distributed and specialised (with many small and medium-sized enterprises). We must structure the Germany/EuroStack in line with this strength!

1. However, this model is disadvantageous for platform markets due to network effects and favours „the winner takes it all“ outcomes.
2. This disadvantage can be overcome through cooperation on standardisation by creating a network of highly interoperable clouds.
   • This requires meaningful open standards and strong, highly qualified standards management in the joint interoperability standards group.
3. Open source enables collaboration in joint implementation and also in innovation.
4. Open Operations enables collaboration in building operational capabilities (to address the shortage of skilled personnel).

5. We don't need to wait until another initiative is completed; we can start today with what we have!

• Most open-source cloud providers use very similar technology.
• Every relevant cloud provider offers a managed Kubernetes platform.
• Nevertheless, each individual cloud provider differs in its APIs and interfaces to such an extent that uniform and consistent expectation management is difficult.
• The Sovereign Cloud Stack (SCS) standards ensure interoperability and federation between them, thereby delivering on the promise of provider switching capabilities.
• Especially for new offerings, the SCS project provides a complete, openly developed open source reference implementation that is used productively by more than half a dozen operators of public, community and private clouds. The standards are met by providers who use most of them, as well as by providers who do not use them (or use them only to a limited extent).
• The IPCEI-CIS, 8ra, NeoNephos and other initiatives can certainly combine SCS standards and SCS technologies and build on them to develop the next generation in the future.
• openDesk also integrates existing, proven open source solutions into a comprehensive workplace solution. Although it still needs to be expanded, it is already a proven and powerful solution.
• SCS and openDesk work well together and are a good starting point for the core of a successful EuroStack / GermanStack.
• With openCode, ZenDiS has launched an important platform – now it is up to the ecosystem to follow suit and ensure that it gains the necessary acceptance.
• Other OSS components (such as those from the international GovStack initiative) can also contribute to this.

6. Not every company that talks about supporting digital sovereignty may have the best interests of European citizens and businesses at heart.

• Some do not even have a comprehensive understanding of the concept of digital sovereignty.
• As digital sovereignty has become a hot topic, there is a lot of marketing going on to attract large companies; we are seeing a lot of noise and „sovereign-washing“.
• There are companies and non-profit organisations that have been working on solutions for years and are consistently committed to solutions that truly empower their users to become less dependent on individual providers. We should place more trust in them than in the new „advocates“ of digital sovereignty (even if the latter are larger) and put them at the centre of a cloud network.

7. Regulation, project financing and procurement must be coordinated in order to be effective!

• Public money, public code: Software developed with public funds should be open source so that it can be trusted, reused, adapted and maintained, resulting in greater cost efficiency and control.
• Regulation is only as effective as the compliant solutions available; project financing can help to create compliant solutions. This has no negative impact on competition if the solutions are open.
• Even though technical requirements must be the top priority in procurement, the findings from funded projects and the availability of solutions resulting from them must not be ignored. Some non-functional requirements relating to security or sovereignty may also be non-negotiable.
• The public sector's purchasing power is considerable and should contribute to the economic viability of sovereign solutions in order to ensure sustainable availability.

8. Technological innovation is iterative and requires intensive and open exchange between regulation and standardisation, technology development, validation and operation!

• What is needed is not a waterfall concept, but cross-functional teams with a strong learning culture. Innovation is not possible if you cannot tolerate mistakes and failures. Innovation requires a willingness to take risks and explore different paths.
• Design and architecture should be inspired by experiments with minimally viable products.