By the Linux Association of Canada

For years, digital sovereignty has largely been discussed as a policy objective: governments should maintain control over their data, reduce strategic technological dependencies, improve resilience, and ensure that essential digital services remain available regardless of geopolitical or commercial disruption.

Europe is increasingly moving beyond that discussion.

The Netherlands is developing a government digital workplace built around Linux, open-source software, open standards and infrastructure designed specifically to reduce technological dependency. Germany continues to expand its open-source government workplace ecosystem through openDesk. France is developing its own sovereign collaboration technologies through La Suite.

These are not isolated experiments anymore.

They are increasingly becoming pieces of a broader European approach to digital sovereignty—one in which open source is becoming part of the infrastructure governments consider necessary to maintain genuine technological choice.

Canada should be paying attention.

The Netherlands Builds an Autonomous Government Workplace

The Dutch initiative is called DAWO — Digitaal Autonome Werkomgeving Overheid, or Digital Autonomous Government Work Environment.

Developed under the Netherlands' Ministry of the Interior and Kingdom Relations, DAWO is intended to provide an interoperable and digitally autonomous foundation for government workplaces.

Importantly, DAWO is not simply a Linux desktop.

Its architecture includes an operating system, device management and orchestration, identity and access management, cloud infrastructure, artificial intelligence and collaboration software.

At the desktop level, the project has developed DAWO-NixOS, an implementation based on the NixOS Linux distribution. A parallel development path based on Fedora Kinoite is also being investigated.

The project describes itself not as a single product or closed software suite, but as an open blueprint whose components can be independently developed, inspected and replaced.

That distinction matters.

Digital sovereignty does not necessarily mean that a government must build every component itself.

It means maintaining the ability to understand, operate, replace and control those components.

Open source makes that considerably more achievable.

From Experiment to Government Pilot

The Netherlands is already putting the idea into practice.

Amsterdam, Ede, Zaanstad and ’s-Hertogenbosch are participating in a pilot alongside the Association of Netherlands Municipalities and the Dutch national government.

Government employees are testing Linux-based laptops together with MijnBureau, an open-source collaboration environment incorporating technologies connected with projects including Nextcloud, France's La Suite and Germany's openDesk.

The pilot is expected to continue through the end of 2026, collecting practical experience and identifying where the environment needs further development before broader deployment.

This is therefore not an announcement that the Netherlands has suddenly replaced Windows throughout government.

Something more interesting is happening.

The Dutch government is testing whether it can create a viable alternative.

And having an alternative is at the heart of technological sovereignty.

Germany Is Building Too

The Netherlands is not working in isolation.

Germany has been developing openDesk, an open-source office and collaboration environment designed for public administration through the Centre for Digital Sovereignty of the Public Administration, known as ZenDiS.

Development continues to move toward operational deployment.

On September 23, ZenDiS announced a partner program allowing cloud providers and IT service companies to provide openDesk Enterprise services.

Six days later, on September 29, Germany's Bundesdruckerei Group and ZenDiS announced a strategic partnership focused on sovereign IT infrastructure, operating models, open-source technologies and further development of openDesk for security-sensitive government environments.

These developments demonstrate an important evolution.

Open source is not merely being discussed as a less expensive alternative to commercial software.

It is increasingly being treated as strategic digital infrastructure.

And Canada?

Canada has begun asking many of the same questions.

The Government of Canada's Digital Sovereignty Framework defines digital sovereignty as the government's ability to exercise autonomy over its digital infrastructure, data and intellectual property and to make independent decisions regardless of where technologies are developed, hosted or supported.

The framework also recognizes something particularly important: digital sovereignty extends beyond simply determining where data is stored.

It includes operational resilience, supply chains, system integrity and institutional control.

And open source appears explicitly in that discussion.

The federal framework says future work will examine how open-source solutions can responsibly support government service delivery, transparency, interoperability and continuity of operations. It also discusses reducing reliance on proprietary technologies, using vendor-neutral formats and maintaining environments controlled by the Government of Canada.

That is significant.

Because the central question surrounding digital sovereignty isn't whether foreign technology is inherently bad.

It isn't.

The question is whether Canada retains meaningful choices.

Sovereignty Is About Choice

A country does not become digitally sovereign simply by moving a server into a Canadian data centre.

If the operating systems, cloud platforms, identity systems, collaboration tools, document formats and administrative infrastructure underneath those services remain dependent upon technologies that cannot realistically be replaced, sovereignty remains limited.

True resilience requires options.

Can a government migrate its data?

Can it change providers?

Can it inspect critical software?

Can systems communicate through documented standards?

Can another organization maintain the technology if the original supplier disappears?

Can essential services continue operating if commercial, political or geopolitical circumstances suddenly change?

These are not theoretical questions anymore.

Governments themselves are beginning to ask them.

Canada's Digital Sovereignty Framework specifically identifies global supply chains, service interruptions, deplatforming, foreign jurisdictions and vendor concentration among the risks that government must consider.

Open source cannot eliminate those risks.

But it can provide governments with something extraordinarily valuable:

an exit strategy.

Canada and Germany Are Already Talking

There is another reason the European developments should matter to Canada.

Canada and Germany launched the Sovereign Technology Alliance in February 2026 to strengthen cooperation around sovereign technology and reduce strategic technological dependencies.

The first meeting of its co-chairs took place in Montréal this September.

The two countries are working toward expanding the alliance to additional trusted partners, with cooperation focused initially on areas including sovereign artificial intelligence, digital infrastructure and advanced technologies.

At the same time, Canada is beginning to make investments in open technologies closer to home.

At ALL IN 2026, Mila, Mozilla and Hypertec announced plans for a Canadian-led open-source AI consortium intended to make advanced AI technology more accessible while providing organizations with greater choice and control over their technology and data.

These are encouraging developments.

But digital sovereignty cannot stop at artificial intelligence.

The operating systems, cloud infrastructure, identity platforms, office environments, communications systems and software development ecosystems underneath AI are equally important.

Canada Does Not Need to Copy Europe

Canada does not need a Canadian version of every European project.

Nor should digital sovereignty become an excuse for technological isolationism.

Modern computing depends on international collaboration.

Linux itself may be the greatest demonstration of that principle: thousands of companies, governments, organizations and individuals around the world collaboratively maintaining technology that none of them exclusively controls.

That is precisely why open source and digital sovereignty complement each other so well.

Sovereignty does not require isolation.

It requires agency.

Canada should be able to choose proprietary technology when it represents the best solution.

It should also have the technical expertise, infrastructure, open standards and open-source alternatives necessary to choose something else.

Without alternatives, choice becomes theoretical.

Canada Already Has the Foundations

Canada does not need to begin from zero.

We have universities and colleges producing skilled technology professionals.

We have Canadian hosting and infrastructure providers.

We have cybersecurity expertise.

We have open-source developers and communities distributed across the country.

We have companies building products and services around Linux, Kubernetes, cloud infrastructure and open technologies.

And importantly, federal technology policy already recognizes open source.

The Government of Canada's Enterprise Architecture Framework instructs organizations to consider reusable open-source solutions and to contribute improvements back to open-source communities.

What Canada needs now is to connect these pieces.

Government procurement, education, workforce development, Canadian technology companies and the open-source community should not operate as separate conversations.

Digital sovereignty requires an ecosystem.

The Opportunity for Canada

Imagine a Canadian public-sector technology ecosystem in which government systems increasingly use open standards and portable data formats.

Where Canadian companies can provide support and hosting for government open-source infrastructure.

Where colleges and universities teach technologies actually being deployed in sovereign government environments.

Where students can examine and contribute to the same software used by public institutions.

Where government investment in software can produce code that municipalities, provinces, schools, nonprofits and Canadian businesses can reuse.

And where Canadian governments maintain credible alternatives when negotiating with the world's largest technology companies.

That is not about removing Microsoft, Google, Amazon or any other company from Canada.

It is about ensuring Canada never reaches a position where replacing any one supplier becomes practically impossible.

Competition requires alternatives.

Resilience requires alternatives.

Sovereignty requires alternatives.

Europe Is Building. Canada Should Build Too.

The most important lesson from the Netherlands may not ultimately be NixOS.

It may not be DAWO, openDesk or La Suite either.

The important lesson is that governments are beginning to treat digital independence as something that must be engineered, not merely declared.

Infrastructure must be built.

Standards must be adopted.

Skills must be developed.

Communities must be supported.

Alternatives must exist before they are urgently needed.

Canada has already recognized digital sovereignty as a national concern. It is working with Germany on sovereign technology. It is investing in Canadian AI infrastructure and open-source AI initiatives. And its own federal framework acknowledges the potential role of open-source technologies in maintaining interoperability and continuity.

The next question is therefore no longer whether Canada should discuss digital sovereignty.

It is much simpler:

What are we going to build?

The Linux Association of Canada promotes Linux, open-source software, open standards and the development of Canadian open-technology skills and communities.