Digital sovereignty is often discussed badly.
One side presents it as technological isolation: every country building its own cloud, its own models, its own chips, and perhaps its own version of the internet.
The other side dismisses it as protectionism promoted by people who do not understand global technology markets.
Both interpretations miss the operational question.
Digital sovereignty is not about rejecting foreign technology.
It is about understanding what happens when technology essential to your organisation is controlled by someone else.
Can prices change without meaningful negotiation?
Can access be withdrawn?
Can data be moved elsewhere?
Can the service be replaced?
Can the organisation continue operating during a geopolitical, commercial, legal, or technical disruption?
Does anyone internally still understand the system?
These are not nationalist questions.
They are questions of governance and resilience.
A Swiss company can use an American cloud provider and still make sovereign architectural decisions. A European organisation can purchase an Asian technology product without surrendering control. Open-source software can strengthen sovereignty, but self-hosting badly documented systems does not automatically create it.
Sovereignty is not determined by the flag displayed on the supplier’s headquarters.
It is determined by the options retained by the customer.
Those options include contractual rights, data portability, interoperability, internal competence, transparent interfaces, replaceable components, and credible exit paths.
Complete independence is neither realistic nor desirable. Modern technology is built through international supply chains, research communities, standards, and markets.
The objective is not independence from everyone.
It is freedom from dependencies that cannot be governed.
That requires prioritisation. Not every newsletter platform, analytics tool, or office application deserves a national strategy. But systems involving critical infrastructure, public administration, healthcare, finance, identity, communications, and strategically important data deserve more scrutiny.
Digital sovereignty begins when an organisation can state clearly:
What must remain under our control?
Which dependencies are acceptable?
What would failure cost us?
How quickly could we leave?
What capabilities must we retain internally?
That is not a slogan.
It is architecture.
It is procurement.
It is risk management.
And increasingly, it is responsible leadership.