Dominic Jainy is an IT professional with deep-rooted expertise in artificial intelligence, machine learning, and blockchain technology. With a career dedicated to understanding how complex digital systems can be harnessed across diverse sectors, Jainy has become a critical voice in the conversation surrounding technological independence. His insights are particularly timely as the European Union unveils a massive 29-page strategic framework designed to elevate open-source software to a cornerstone of regional sovereignty. By examining the intersection of collaborative development and public policy, Jainy provides a unique perspective on how the EU aims to dismantle external dependencies while fostering a more resilient, community-driven digital landscape. This interview explores the core themes of the EU Tech Sovereignty Package, from the reclassification of code as public infrastructure to the overhaul of procurement rules and the urgent need for sustainable funding models for the foundational tools that keep the modern world running.
Treating software code as public infrastructure like roads or bridges represents a major shift in how governments perceive their digital foundations. How does this analogy fundamentally change the way public agencies approach their technology investments?
The shift toward viewing code as public infrastructure is a profound conceptual change that moves us away from seeing software as a mere consumable product. When the EU dedicates nearly 30 pages to this topic, they are essentially arguing that the digital pathways we navigate daily deserve the same level of stewardship and public oversight as our physical highways. In the past, a public agency might have purchased a proprietary license and viewed the transaction as complete, but this new strategy suggests a preference for solutions where the code is “owned” by the community. By treating code like a bridge, the focus shifts to longevity, shared access, and the removal of restrictions that prevent multiple parties from utilizing the tool simultaneously. This means public agencies are being encouraged to prioritize software that meets functional requirements while remaining open for all to inspect and maintain, ensuring that the foundation of our digital society isn’t locked behind a private paywall.
The EU Tech Sovereignty Package is a broad effort to reduce reliance on external providers. How do these 29 pages of open-source strategy specifically serve as a practical path toward digital independence?
The EU is clearly feeling the weight of its dependence on technology providers based outside the region, particularly those that dominate critical digital infrastructure and data management. This 29-page strategy signals that community-driven development is no longer just a niche interest; it is a strategic asset for the bloc’s technological autonomy. By focusing on open source, the EU is attempting to regain control over its own software supply chains, ensuring that essential tools aren’t subject to the whims of foreign corporate interests or shifting geopolitical tides. The document outlines a vision where European institutions can audit, modify, and host their own software, effectively insulating themselves from sudden changes in service terms or the risk of foreign intelligence interference. This isn’t just about code; it’s about ensuring that the 27 member states have a digital “home” that they actually own and can defend.
Security is often cited as both a strength and a vulnerability of open-source software. How does the EU propose to harness the visibility of code to create a more secure digital environment?
There is a long-standing debate about whether open code is more vulnerable, but the EU’s stance is that visibility is a massive security advantage. When code remains open for anyone to examine, the number of eyes looking for weaknesses increases exponentially compared to closed, proprietary systems. To make this a reality, the policy recommends that European institutions adopt rigorous security audits of widely deployed libraries and establish dedicated funding streams to address vulnerabilities before they are exploited. They even propose creating “centers of excellence” where developers from across the member states can collaborate on hardening essential tools against emerging threats. It’s a move toward proactive defense, where the community works together to build a “fortress” out of transparency rather than relying on the “security through obscurity” model that proprietary vendors often use.
Traditional government procurement often creates a “vendor lock-in” that is difficult to escape. What specific changes to purchasing rules could help European small and medium-sized enterprises compete with global tech giants?
The current procurement landscape is heavily skewed toward large vendors who have the resources to navigate complex compliance documentation and maintain massive sales teams. The new framework aims to disrupt this by encouraging contracting authorities to evaluate the “total cost of ownership,” which includes the long-term expenses and risks associated with being stuck with a single provider. If two solutions offer comparable features, the preference should now go to the one that allows for modification, redistribution, and local hosting. This is a game-changer for European SMEs that build their business models on open platforms, as it allows them to compete on the quality and flexibility of their services rather than the size of their legal departments. It creates an environment where local innovation can flourish because the barrier to entry isn’t a proprietary license, but the ability to provide a high-quality, adaptable solution.
Integrating open-source concepts into education is a key part of this strategy. How will changing computer science curricula at the university level help sustain European technology over the coming decades?
Education is where the culture of tech sovereignty truly begins, and the EU is smart to advocate for the integration of open-source concepts into curricula at both the secondary and university levels. It’s not enough for students to just learn how to write code; they need to understand how to participate in public repositories, conduct effective peer reviews, and navigate the complexities of licensing obligations. By training the workforce to be comfortable in a collaborative, public-facing environment, the EU is building a talent pool that can sustain domestic projects for the long haul. This reduces the risk of talent flight to other regions and ensures that the next generation of developers sees themselves as contributors to a public good. It’s about moving beyond the “siloed” developer mentality and fostering a community-first approach that ensures the continuity of essential digital tools.
Many critical open-source projects rely on volunteer labor, which can be a point of failure. How do the EU’s proposed funding mechanisms address the sustainability of foundational digital building blocks?
The fragility of the “volunteer model” is a significant risk for projects that underpin everything from cryptography to web serving. The EU document addresses this by moving away from one-time grants in favor of multi-year support for foundational projects that the rest of the ecosystem depends on. Think of libraries like those used for container orchestration or secure communications; if a single maintainer leaves or an underfunded team burns out, the ripple effects can disrupt services across the entire continent. By stabilizing these building blocks with reliable, long-term funding from research programs and new sovereignty funds, the EU is essentially “buying insurance” for its digital infrastructure. It’s a recognition that if we treat code as a public utility, we must also be willing to pay for its upkeep, just as we would for a power grid or a water treatment plant.
The Open Source Initiative has raised concerns about the potential for “bureaucratic requirements” to stifle innovation. Where is the balance between quality assurance and the collaborative spirit of the community?
This is perhaps the most delicate part of the entire proposal, and the Open Source Initiative was right to voice caution. While certification schemes for software used in government systems are meant to ensure quality, they can easily become a nightmare for small, decentralized teams that don’t have the administrative staff to handle complex compliance. If the EU makes the process too burdensome, they risk alienating the very people who build the best tools. The key is to find a middle ground where quality is verified without crushing the voluntary nature of the participation. We need systems that are “lightweight” enough for a solo developer to navigate but robust enough for a government agency to trust. If the bureaucracy becomes the primary gatekeeper, the EU will simply find itself right back where it started: depending on large, proprietary vendors who are the only ones capable of jumping through all the hoops.
How does the concept of data sovereignty tie into the choice of software, particularly when it comes to the hosting of sensitive information?
Data sovereignty is often the “why” behind the shift to open source. European officials are deeply concerned that cloud services hosted in foreign jurisdictions expose sensitive data to foreign intelligence services or sudden, unfavorable policy shifts. Open-source alternatives are the solution to this because they allow governments and businesses to run identical software on servers located within EU borders, fully subject to local data protection laws. This 29-page document emphasizes projects that enable easy migration between different infrastructure providers, which prevents a new form of “cloud lock-in.” It’s about having the freedom to move your data and your tools wherever they are safest, ensuring that the “digital borders” of Europe are respected and that sensitive information remains under local control, regardless of what happens in the global geopolitical arena.
Interoperability is a major focus of this policy package. In what ways can open standards and protocols improve the daily lives of citizens interacting with government services?
When we talk about interoperability, we’re really talking about citizen choice and accessibility. By mandating open standards in areas like electronic identification and health record exchange, the EU is ensuring that citizens aren’t forced to use a specific vendor’s product just to interact with their own government. We’ve seen this work with the PEPPOL network for electronic invoicing, which relies on openly documented specifications that any supplier can use. For the average person, this means their health data can be shared securely between providers without technical friction, or they can use their digital ID across various services without worrying about compatibility. It levels the playing field for businesses too, as they can build tools that plug directly into the government’s digital ecosystem, fostering a diverse market where the best user experience wins, not the most dominant proprietary standard.
What is your forecast for the future of open-source adoption within the EU as these pilot programs begin to roll out?
I believe we are entering an era of “pragmatic sovereignty” where the EU will move beyond rhetoric into actual, ground-level implementation through these pilot programs. Over the next few years, I expect to see a surge in the creation of EU-wide Open Source Program Offices that will act as the nerve centers for this transition, sharing best practices and coordinating funding across all 27 member states. We will likely see some initial friction as procurement officers learn to evaluate community activity and license compatibility, but the geopolitical pressure to reduce external dependencies will keep the momentum alive. Ultimately, this shift will stimulate a new wave of European innovation, creating a more competitive and diverse technology market. The “29-page strategy” is just the beginning; the real success will be measured by how many critical systems are successfully migrated to open platforms, ensuring that the software underpinning modern European society is as transparent, resilient, and locally controlled as the very roads we drive on.