
#1 Do it all yourself?
Anyone who wants to be independent of individual IT providers must operate their own servers, applications, and infrastructure. However, digital sovereignty and full self-operation are not the same thing.
Rather, it's about being able to decide for oneself, how and where an application is run. This can be in your own data center, with a specialized hosting partner, or as Software as a Service.
Sovereignty arises when different operating models remain possible and a change is fundamentally feasible. We explore why freedom of choice plays a central role in this in the article "From Freedom of Choice to Digital Sovereignty".
Digital sovereignty, therefore, does not mean doing everything yourself. It means being able to make your own decisions.
#2 GDPR = Digital Sovereignty?
Data protection and digital sovereignty are closely linked, but they describe different requirements.
The GDPR specifically governs the protection of personal data and its processing. Digital sovereignty goes beyond that. A service can comply with data protection requirements and still create technical or economic dependencies.
The key factor is the interplay between software, architecture, data formats, interfaces, and the operating model. We explain the role that open source can play in this context in the article „Digital Sovereignty and the Role of Open Source“. Data protection is thus an important component of digital self-determination, but not its only prerequisite.
#3 European = automatically sovereign?
When it comes to digital sovereignty, the location where digital infrastructure is developed, operated, and controlled plays an important role. However, a European server location alone is not enough. Equally relevant is the jurisdiction to which a provider is subject. Under certain conditions, the U.S. CLOUD Act can also apply to data stored outside the United States. For more on this, see the article „Moving Away from the U.S. Cloud: Identifying European Alternatives to Google and Microsoft“.
Even having a European headquarters does not automatically make a solution self-sufficient. Open standards, documented interfaces, portable data, and independent operational and development capabilities help prevent long-term dependencies.
Digital sovereignty therefore does not mean isolation, but rather control over key digital infrastructures and the ability to act autonomously in the long term.
#4: Does vendor lock-in only occur when switching?
As long as a platform is working, dependence on a single provider often seems unproblematic. It often doesn't become apparent until prices or licensing terms change, features are removed, or a switch is planned.
However, vendor lock-in occurs much earlier. Even at the time of implementation, proprietary file formats, limited export options, manufacturer-specific interfaces, or tightly coupled applications can make it difficult to switch later on.
Processes, automation, and internal expertise can also be so tightly tailored to a particular platform that switching to another one becomes a major undertaking.
That is why an exit strategy should be part of the initial planning phase of an IT project: How can data be exported, applications replaced, and systems—if necessary—continued to be operated by another service provider?
Open standards, documented APIs, portable data formats, and interoperable systems ensure long-term flexibility. Read more in the article „Avoiding Vendor Lock-in: Open Source as a Risk Mitigation Strategy“.
#5 Is digital sovereignty primarily an IT issue?
Digital sovereignty is often associated with technical issues: What software is used? Where is the data stored? What interfaces are available?
However, the issue goes beyond that. The choice of digital solutions also affects procurement, costs, business processes, and long-term dependencies. Platforms that are difficult to replace can limit an organization’s flexibility for years.
Digital sovereignty is therefore not solely the responsibility of the IT department. Management, procurement, and line organizations should also consider what dependencies arise and how easily they can be resolved later on.
Questions regarding open standards, data portability, and the ability to switch providers should therefore be considered as early as the procurement phase. Ultimately, public solicitations determine how sustainably open source is used in Germany. "Anyone who wants to preserve and make effective use of OSS in the long term must ensure that vendors are evaluated not only on price, but also on quality, innovation, and sustainability. The B-criteria are proven, legally compliant, and can be used immediately in tenders. Let’s not allow „cuckoo vendors“ to destroy the OSS ecosystem; instead, let’s commit to sustainable OSS procurement—for a future-proof and sovereign IT landscape,“ urges Peer Heinlein. Learn more about this in the presentation „The Cuckoo in the Bidding Process – When the Bidder Loses to Itself.“

