The conversation about digital sovereignty is no longer confined to European institutions or major regulatory debates. It also directly concerns those who design architectures, deploy infrastructure, integrate tools, develop software, or make technology decisions within their organizations. Because, in practice, technological sovereignty is not decided solely in parliaments or strategic plans: it is also determined by code, standards, interoperability, and the actual degree of dependence we accept every time we choose a technology.
In this context, discussing open source is not merely about a form of software licensing. It is about a cornerstone for building digital autonomy, adaptability, transparency, and resilience. That is why the DOK Summit has incorporated this debate as one of its key content areas: sovereignty and ethics, where open source emerges as a decisive factor for the technological autonomy of Europe and regions such as the Basque Country.
Technological sovereignty doesn’t mean doing everything on our own
It is worth starting by dispelling a common misconception. Technological sovereignty does not mean manufacturing everything locally or operating outside global innovation chains. According to the strategic narrative underlying DOK, it is rather about mastering the strategic capabilities that determine autonomy or dependence: systems architecture, hardware-software integration, security, scalability, cybersecurity, and the technology lifecycle.
In other words: it’s not about isolating oneself, but about retaining decision-making autonomy. It’s about being able to choose, evaluate, adapt, migrate, integrate, and evolve technology without getting trapped by black boxes, excessive dependencies, or closed models that dictate an organization’s future.
That nuance is important because it shifts the conversation from a symbolic framework to an operational one. The question is not just “what technology do we use,” but “how much real control do we have over it.”
Why open source is a key component
This is where open source takes on strategic value. Not because it is a magic solution or because everything must be open source, but because it creates conditions that are particularly valuable for digital autonomy.
The first is transparency. When a solution can be inspected, audited, and understood, we do not rely solely on the vendor’s promises. This is particularly relevant at a time when demands for compliance, security, and traceability are growing, and when regulation—as DOK’s own communication plan points out—has become a central concern for companies and institutions.
The second is interoperability. By design, the open-source ecosystem promotes connectivity between systems, code reuse, and the elimination of unnecessary barriers. For technical teams, this means one very specific thing: greater flexibility to build architectures that stand the test of time and less reliance on external decisions that are difficult to reverse.
The third is adaptability. When knowledge is more widely distributed and access to technology is less opaque, it becomes easier to refine tools, fix problems, expand functionality, or respond to specific contexts. That flexibility is essential at a time when competitiveness no longer depends solely on adopting technology, but on integrating it judiciously and turning it into a practical advantage.
Open Source, Ethics, and Autonomy: All Part of the Same Conversation
There is another reason why open source plays a central role in this debate: its connection to technological ethics. Not because open source is automatically ethical, but because it fosters conditions that promote more responsible governance: greater transparency, less opacity, more opportunities for scrutiny, and a stronger foundation for collaboration.
At a time marked by the expansion of artificial intelligence, cybersecurity, and new regulatory frameworks, ethics cannot be reduced to a generic manifesto. It must be capable of translating into practices, criteria, and technical decisions. And in this regard, open source offers a significant advantage: it allows for a more informed discussion of what a tool does, how it does it, and under what dependencies it operates.
It is no coincidence that the evolution of ESLE has expanded the concept of “open” beyond software to include open data, open hardware, open content and knowledge, and open innovation. This expansion aligns perfectly with the DOK Summit’s identity as the Digital Open Knowledge Summit and with its mission to connect digital transformation, sustainability, and open knowledge.
From Technology Adoption to Operational Sovereignty
One of the most interesting concepts highlighted in DOK’s strategic materials is the shift from simple technology adoption to operational sovereignty. For years, many organizations have competed by efficiently integrating external technologies. Today, that is no longer enough. The difference lies in the ability to decide how those technologies are integrated, based on what criteria, under what security conditions, and with what degree of future control.
For the technical community, this has very specific implications. It means that decisions regarding tools, technology stacks, standards, and deployment models are not neutral. They are also decisions about autonomy, auditability, and medium-term resilience.
From that perspective, open source is not merely a cultural legacy of LibreCon within DOK. As the communication plan itself states, it is the driving force behind a fundamental part of the event: the part that focuses on real tools, demos, community, and co-created solutions—not just marketing hype.
A conversation of particular relevance to the Basque Country
In the Basque Country, this debate also has a clear strategic dimension. The DOK Summit serves as a platform to strengthen the region’s competitiveness, link global challenges with local solutions, and foster an open, secure, and green digital transition. In this context, technological sovereignty is not a mere theoretical concept: it is essential for building industry, protecting critical capabilities, and securing a strong position in the new digital economy.
And that is where the open-source ecosystem has a lot to offer: not only as a technical community, but also as a culture of collaboration, knowledge transfer, and shared capacity building.
Looking at the code is also looking to the future
When we talk about digital sovereignty, open source, and open-source software, we are essentially talking about the kind of technological future we want to build. One that is more dependent, opaque, and rigid, or one that is more transparent, interoperable, and capable of fostering true autonomy.
The answer will not be black and white or one-size-fits-all. But it is becoming increasingly clear that the conversation matters. And that those who work closely with code, infrastructure, and technology architecture have a lot to contribute to it.
Technological sovereignty is not about isolating oneself, but about retaining decision-making power.
Open source provides transparency, interoperability, and flexibility.
For technical teams and the community, choosing open technologies also means choosing greater autonomy, greater auditability, and greater resilience in the medium term.