Digital sovereignty: Why open infrastructure matters
summary
Claims that “digital sovereignty” requires more than data residency and legal compliance: a funded sovereign cloud stack project maps four layers — legal dimension, freedom of choice, open technology (open source backed by the four opens: open communities, open design, open development, open source) and operational competence — and argues closed-source local clones of GCP/Azure don’t deliver sovereignty. Proposes building and sharing open operations knowledge, offers a white paper (German/English) and a booth reference for follow-up.
AI-written summary · about
chapters (5)
- 0:00Introduction to digital sovereignty
- 1:04Defining digital sovereignty
- 3:34Four layers of digital sovereignty
- 6:42Open communities and operations
- 9:57Call to action and conclusion
related talks
23mDigital sovereignty: Why open infrastructure matters
25mDigital Sovereignty - Why Open Infrastructure Matters
37mDigital Sovereignty Driving Open Source in Germany and Europe
40mSovereign by Design, Open by Default
40mDigital sovereignty - shaping regulatory responses to technological dominance
31mDigital sovereignty through open source – Europe's strategic opportunity
24mDigital sovereignty: definition and stakes for companies and devs
26mDigital sovereignty: between myth and reality How to arbitrate