Digital sovereignty is moving from policy papers to practical infrastructure. Switzerland's latest open-source initiative offers Canada an interesting example of what that can look like.

For years, discussions about digital sovereignty have often sounded theoretical.

Where is government data stored? Who controls the infrastructure? What happens when essential public services depend heavily on technology supplied by companies headquartered in another country? And perhaps most importantly: could a government continue operating if access to one of those platforms were suddenly disrupted?

Switzerland has decided that these questions deserve more than discussion.

On September 2, 2026, the Swiss Federal Chancellery announced that it is moving ahead with a program to create a digitally sovereign workplace based on open-source software. Beginning at the end of 2027, approximately 3,000 federal employees are expected to have access to the new environment for core office functions.

The decision follows a government feasibility study examining whether everyday federal office work could be performed using open-source technology.

Its basic conclusion?

Yes.

And Canada should be watching.

This isn't simply about replacing Microsoft

Some coverage of the announcement has portrayed Switzerland as abandoning Microsoft 365.

That's not quite what's happening.

The Swiss government currently relies heavily on Microsoft technology, and the new open-source workplace is initially intended to operate alongside Microsoft 365, rather than immediately replacing it. Switzerland will use the experience to determine what a larger implementation would cost and whether expanding the system makes sense.

That distinction matters.

Digital sovereignty doesn't necessarily mean refusing to use technology from foreign companies.

It means avoiding a situation in which there is no viable alternative.

A government should know that if a critical commercial service becomes unavailable—whether because of a technical failure, cybersecurity incident, contractual dispute, geopolitical development or other crisis—it still has the ability to operate.

Switzerland is effectively asking:

Do we have an exit strategy?

That's a question every government increasingly needs to answer.

What does the open-source workplace actually contain?

The Swiss proof-of-concept is known as BOSS — Büroautomation mit Open-Source-Software, or office automation using open-source software.

Rather than attempting to build an entire productivity ecosystem from scratch, Switzerland tested existing open-source technologies through openDesk, a workplace platform developed under Germany's Centre for Digital Sovereignty.

The technologies evaluated include:

  • Collabora Online for documents, spreadsheets and presentations
  • Open-Xchange for email, calendars, contacts and tasks
  • Nextcloud for file storage
  • OpenProject for project management
  • XWiki for knowledge management
  • Jitsi-based technology for audio and video conferencing
  • Element for messaging and chat
  • Univention for identity and access management

The Swiss government says these technologies are being assessed for usability, practicality, scalability and security.

This is one of the most interesting aspects of the project.

There is no single piece of software attempting to become a Microsoft 365 clone. Instead, interoperable open-source components can provide different parts of the workplace environment.

That modularity is one of open source's greatest strengths.

The test wasn't perfect — and that's important

Open source advocacy shouldn't require pretending that every open-source solution is automatically superior to a proprietary one.

Switzerland's experiment found limitations.

The feasibility study concluded that normal core office processes could generally be supported, but areas such as larger-scale video conferencing still required additional work. The government also recognized that moving an organization with deeply integrated Microsoft applications away from that ecosystem would be complex.

That's exactly why pilots like this are valuable.

You don't discover those limitations by writing another strategy document.

You discover them by putting the software in front of actual employees and asking them to do their jobs.

Switzerland's approach is therefore refreshingly pragmatic:

Test it. Measure it. Find the weaknesses. Improve them. Then decide whether to expand it.

That's very different from announcing an ideological ban on proprietary software.

Digital sovereignty is also about resilience

There's another important part of the Swiss government's reasoning that can easily get lost in the Microsoft-versus-open-source discussion.

This is about business continuity.

The Federal Chancellery explicitly describes the ability to maintain critical business processes during a crisis as one of the objectives of the project. Its feasibility study also examines an eventual Microsoft 365 exit strategy.

Imagine applying the same principle to electricity.

No government would intentionally design critical infrastructure so that a single external provider represented the only possible source of power, with no contingency plan.

Yet governments increasingly depend upon a relatively small number of technology platforms for communications, documents, authentication, collaboration, cloud computing and data storage.

Those systems have become infrastructure.

And infrastructure requires redundancy.

Open source can provide something particularly valuable in that environment: the ability to operate technology without being permanently tied to one vendor's permission, licensing model or product roadmap.

Canada is already asking some of the same questions

This is where the Swiss story becomes particularly relevant to Canada.

The Government of Canada has already formally recognized digital sovereignty as an issue.

Its federal digital-sovereignty framework defines the concept as Canada's ability to exercise autonomy over government digital assets and services and to manage and protect systems, data and information regardless of where the underlying technologies are developed, hosted or supported.

The framework specifically identifies issues including jurisdictional complexity, reliance on global suppliers, cybersecurity risks and institutional control.

Shared Services Canada's 2026–27 Departmental Plan goes further.

Digital sovereignty is listed as one of SSC's key priorities, alongside modernization and transformation. The department says Canada needs to protect citizen data, explore Canadian markets, maintain continuity of government operations and reduce risks created by dependence on foreign-hosted services.

SSC is also pursuing Canadian sovereign AI and compute capabilities and says it intends to work with Canadian cloud providers to increase Canada's domestic cloud footprint.

So Canada clearly understands the issue.

The interesting question is what comes next.

Canada doesn't need to “dump Microsoft”

That shouldn't be the lesson Canada takes from Switzerland.

Microsoft, Google, Amazon and other global technology companies provide enormously capable platforms. Canadian governments use them because those platforms solve real problems at enormous scale.

The question isn't whether those companies are good or bad.

The question is whether strategic dependence on any single supplier is healthy.

Canada could begin with the same relatively modest question Switzerland asked:

Could a portion of the federal public service perform its essential office work entirely on an open-source platform if it had to?

We don't need to speculate.

Test it.

Choose several thousand users across different departments. Build a Canadian-hosted open-source workplace. Test documents, email, calendars, videoconferencing, collaboration, identity management and file storage.

Then measure the results.

How reliable is it?

What doesn't work?

What does it cost?

What skills would government need internally?

Which proprietary formats or integrations create migration problems?

How easily could government data move between platforms?

And perhaps most importantly:

Could Canada keep operating if one major commercial platform suddenly wasn't available?

Those answers would be enormously valuable regardless of whether Canada ultimately changed a single Microsoft licence.

Open source changes the negotiating position

There's another benefit that receives less attention.

Having a credible alternative changes the relationship between customer and supplier.

If replacing a technology platform is practically impossible, the customer has limited leverage over future pricing, licensing conditions and product changes.

An alternative doesn't have to replace the incumbent system to provide value.

It simply has to be credible enough that replacement is possible.

That's true in business.

It's even more important when the customer is a national government.

Open standards and interoperable systems can therefore provide strategic value even in environments where proprietary and open-source technologies continue to coexist.

This is also an economic opportunity

Canada's digital-sovereignty conversation shouldn't stop at government procurement.

Public investment in open technologies can help create domestic expertise.

Instead of directing every technology dollar toward licensing products developed elsewhere, governments can also invest in Canadian companies, developers, infrastructure providers and open-source communities capable of deploying, securing and supporting these systems.

That doesn't mean choosing Canadian or open-source technology regardless of quality.

Procurement still needs to demand reliability, security, accessibility and value for taxpayers.

But open-source procurement can create an important difference.

Money spent improving an open platform can produce technology that remains available for others to inspect, improve and reuse.

A solution developed for one government department can potentially benefit municipalities, universities, schools, non-profits and businesses.

That creates an ecosystem rather than simply another subscription.

Sovereignty isn't isolation

There is an important distinction here.

Digital sovereignty should not mean technological nationalism.

Canada benefits enormously from international collaboration. Open source itself is perhaps the clearest demonstration of that principle: developers from different countries, organizations and companies collaborate on technology used around the world.

Digital sovereignty means retaining choice and control.

It means ensuring Canadian institutions can determine where sensitive information resides.

It means understanding who has legal jurisdiction over infrastructure.

It means using open standards that allow information to move between systems.

It means maintaining enough domestic expertise to operate critical technology.

And it means ensuring that government has an alternative when circumstances change.

Those principles don't isolate Canada from the world.

They make Canada a more resilient participant in it.

Switzerland is conducting an experiment worth watching

The Swiss initiative may succeed.

It may encounter significant difficulties.

Some applications may prove easy to replace while others remain deeply dependent on proprietary ecosystems.

That's precisely why the project matters.

Switzerland isn't assuming that open source can replace its existing environment.

It's finding out.

Canada should consider doing the same.

The Government of Canada has already acknowledged digital sovereignty as a strategic priority. It recognizes the importance of resilience, domestic capability and maintaining control over critical systems.

The next logical step is practical experimentation.

Not because Canada should abandon Microsoft.

Not because every government computer needs Linux tomorrow.

And not because proprietary software has no place in government.

But because a sovereign country should understand its technological dependencies—and know what its alternatives are.

Digital sovereignty begins with having a choice.

And open source gives governments something increasingly valuable:

the ability to make one.