Knowing where your data resides is essential, but it is not enough to guarantee true sovereignty. Real freedom means being able to move or migrate it without technical constraints or financial penalties. Data ownership, not just location, is the true measure of digital sovereignty.
What is data ownership and why does it go beyond location?
During the last SUSECON in Prague, a statement was made that I fully agree with: “Portability is a fundamental need”.
This statement follows constant and growing concerns regarding vendor lock-in and the related search for virtualization alternatives. Yes, because beyond the needs for cost optimization and innovation, one of the fundamental drivers in the IT and cloud sector is becoming the freedom to move, and I don't just mean geographically.
Because data can be physically located in Italy, protected by ISO 27001 certifications, compliant with GDPR, and have appropriate confidentiality measures in place, but is this really enough to evaluate an infrastructure or cloud provider?
A fundamental variable, in my opinion, is understanding how difficult it will be to move away from a specific provider in the future and under what conditions.
And that is exactly what I mean by data ownership: the ability to know the security perimeter of the data itself, to be able to decide on changes to it, and, at any time, to know exactly the resource effort required to move it to another provider.
A difference that draws a line between "my data is safe" and "the data is MINE and stays safe based on who I entrust it to."
This does not mean that ownership should limit business innovation or data accessibility. The typical approach to these uncomfortable topics, much like with security, is often to close off in order to protect oneself. But closing off is not the same as having control. A concrete example: using artificial intelligence "wisely," by consciously evaluating where and how data is processed, is a much more solid choice than avoiding it out of fear, thereby missing out on a real competitive opportunity. The same applies to data ownership.
The four signs of a cloud that truly gives you control
An infrastructure designed for ownership, rather than lock-in, can be recognized by verifiable elements:
- The real impact of managed services on interoperability and data access. Managed services provide a high level of abstraction, and that is precisely the point: the more you delegate, the less visibility you have into how and where your data is actually handled. They are convenient, but once you adopt them, the room for maneuver largely shifts into the provider's hands;
- Open formats, such as virtual machine images, storage, and configurations that can be exported in industry-recognized standards, rather than proprietary formats readable only by that specific provider;
- APIs and management interfaces that allow for independent access to resource provisioning and exporting, without depending on provider intervention;
- Exit without hidden costs: no hidden penalties disguised as data egress fees.
If even one of these four signals is missing, the sovereignty the provider promises is only valid until you try to test it.

Because "data is in Italy" is just the first step, certainly not the finish line.
Localization answers a legal question: under which jurisdiction is my data processed? This is a fundamental topic, which we have already discussed in depth in our article on digital sovereignty and sovereign cloud and in our analysis of non-EU data transfer risks for MSPs and software houses.
But there is a second, equally concrete question that this answer doesn't cover: if I decide to switch tomorrow, how much will it cost me and how long will it take?
An infrastructure that passes the first test but fails the second offers only half-sovereignty: you are protected from external jurisdictions, but you remain locked into your current provider.
Localization is necessary, but the ability to move is what’s decisive.
The three classic pillars of digital sovereignty, namely Data Sovereignty, Operational Sovereignty, and Software & Cloud Sovereignty, they define where data is located and who can access it. However, they do not define how easy it is to leave when you decide it is time to do so.
And, in my opinion, this is not an accessory element, but rather the proof that makes the other three real. A provider that fully respects localization and governance, but builds a closed architecture, achieves the same practical result as a proprietary vendor: the customer remains tied down, simply for different reasons. On one hand, jurisdiction; on the other, product engineering.
What the Data Act says about portability and how it translates into a competitive advantage
The Data Act, the European regulation that came into force to govern the access and use of data generated by digital devices and services, introduces specific obligations for interoperability and portability for cloud providers, with the stated goal of reducing technological lock-in in the European market.
For an Italian company, this means that portability is no longer just a best practice but is becoming a regulatory requirement. Those who build their infrastructure on open standards do not have to chase compliance when rules become stricter: they are already compliant by design. It is a competitive advantage even before it is a legal obligation.
How to recognize infrastructure built to give you freedom, not to lock you in
First of all, it’s not just a technical detail, but a strategic choice: building infrastructure on open standards means, by definition, never being able to hold a customer captive due to a lack of alternatives. It is the difference between a provider that convinces you to stay and one that doesn't need to.
And it is also the reason why we developed our console to be independent of any proprietary technology, aggregating our own solutions and third-party ones based on the principles just discussed.
Services like OpenStack as a Service, combined with Kubernetes solutions, offer infrastructure management models based on data ownership and customer control: no proprietary virtual machine formats, open-source integration APIs, ready to build resilient, portable, and compliant infrastructure.
Check how truly portable your current infrastructure is. Talk to those who have already guided dozens of migrations to a cloud built on open standards.

