At the Matrix Conference, European government and defense deployments showed why digital sovereignty increasingly depends on federation, open standards, sustainable ecosystems, and, above all, adoption.
Digital sovereignty discussions often start with a familiar question: Where is my data hosted? But the Matrix Conference in Malmö highlighted a much broader issue. Sovereignty also depends on who controls the communications architecture, how organizations collaborate across organizational boundaries, and whether users actually adopt the sovereign alternatives available to them. The takeaway for technology leaders is simple: deploying sovereign technology does not create sovereignty by itself.
Federation Is Emerging As A Sovereignty Architecture
Matrix provides an interesting model because federation allows organizations to operate their own infrastructure while still communicating across organizational boundaries. European public-sector initiatives presented at the conference illustrate the direction of travel. Luxembourg’s Luxchat4Gov has reached approximately 14,000 accounts and is now exploring how to scale toward a broader national sovereign ecosystem. Other government organizations are pursuing Matrix-based collaboration and contributing to a wider ecosystem rather than building isolated national platforms. One speaker captured the architectural direction particularly well: “The future of (sovereign) communication is federation.”
This matters because it also implies that sovereignty does not necessarily require isolation. In fact, isolation can undermine the value of communications technology. Federation offers organizations another option: maintain control over infrastructure, policies, security, and identities while preserving interoperability with trusted communities. Think of sovereignty less as a wall and more as a set of controlled boundaries.
Open Standards Turn Sovereignty Into A Collective Effort
The conference demonstrated why open standards matter beyond avoiding vendor lock-in. Government organizations using the same underlying standard can collaborate on security, interoperability, post-quantum cryptography, and other capabilities rather than solving every problem independently. Germany’s BSI was described as favoring federated and decentralized architectures, with cryptography playing an important role in its requirements. But open source introduces its own economic challenge. As one discussion emphasized, maintainer work must be funded separately from product features. Governments cannot expect strategically important open-source infrastructure to sustain itself simply because the code is available. Technology leaders should therefore evaluate sovereignty across the entire ecosystem: governance, maintainers, standards, skills, funding, and long-term community health.
The Hardest Problem May Be Adoption
A additional valuable lesson came from a Matrix-based messenger deployment within a NATO environment. The organization expected network effects to accelerate adoption. Instead, voluntary adoption stalled. The barriers were familiar: employees did not want another application on personal devices; onboarding and key management created friction; accreditation slowed deployment; and incumbent tools such as Signal already benefited from established contact networks. What changed adoption? Not better technology.
The most successful interventions were local human advocates, leadership support, and clearly defined communities where use became effectively non-optional. In one project where the platform was the required communications channel, adoption accelerated dramatically and generated millions of messages. That is an important lesson for CIOs introducing sovereign alternatives to established collaboration platforms: network effects do not automatically work in your favor. Incumbents already own them.
Minimum Viable Sovereignty Beats Maximum Sovereignty
The Matrix discussions reinforces an important principle for sovereignty strategies: organizations should not wait until every dependency has been eliminated. Federation enables something closer to an “onion rings” model. Organizations can progressively establish stronger sovereignty boundaries around particularly sensitive users, workloads, communities, or interactions while maintaining interoperability where appropriate. That aligns closely with the concept of Minimum Viable Sovereignty: identify the minimum controls required to manage unacceptable dependency and geopolitical risk, then apply stronger sovereignty where the risk justifies it.
Technology leaders should therefore ask four questions:
- Which communications genuinely require sovereign control?
- Where can federation preserve interoperability without sacrificing required control?
- Who will fund and sustain the underlying open source ecosystem?
- How will we create sufficient adoption for the alternative to become useful?
The lesson from Malmö is that sovereign communications are technically possible. Making them operationally viable at scale will be harder. And that may ultimately determine whether Europe’s sovereign technology ambitions scale beyond individual government projects.