The European Commission moved from a Matrix proof of concept in December 2025 to a sovereign internal communication tool installed on every Commission laptop by September 2026. The service is built on Matrix by Element but run by the Commission itself, and it now serves more than 40,000 users. The rollout was described at Matrix Conference 2026 by Diana Gheorghe, head of sector for digital workplace communication services, and Alexandru Vignide, service delivery manager.
What sovereignty means in practice
The Commission first defined what it means by sovereignty, a term that means different things to different people. Its definition covers five areas: resilience and business continuity, vendor diversity, control over data, ownership of the platform, and the ability to negotiate with suppliers, including the option to change them. The last point is often overlooked, yet its absence is usually the most damaging.

Image: behance.net — https://www.behance.net/gallery/187870439/MATRIX-Logo-Brand-Identity-Guidelines
For internal communication the priorities were resilience, data ownership and above all interoperability. That is what pointed the Commission to Matrix, an open protocol whose value lies in letting separate systems talk to each other. It adopted Element Server Suite Pro as a mature implementation, but chose to host, operate and design the service itself.
Sovereign hosting, familiar login, federation still pending
Vignide outlined three architectural decisions. The service does not run in a Commission data centre but with sovereign cloud providers chosen through a hosting tender awarded earlier this year. Sovereignty, in this sense, does not mean building everything in-house, but choosing whom to depend on and on what terms.
Sign-in is integrated with EU Login, which staff already use daily, since a new tool is adopted more readily when logging in feels familiar. Connecting to Matrix servers outside the Commission is still under assessment: the technical side is being explored, and a demonstration on non-production environments was shown at the conference, but federation also requires governance, participation and structure, which take longer than a configuration change.
From proof of concept to laptops in nine months

Image: element.io — https://element.io
The Commission began working with Matrix in summer 2025. According to the account, the December 2025 proof of concept showed that Matrix and Element were viable for the institution, earning approval for a Commission-wide service. Between January and June 2026 the team built the production infrastructure, with the hosting and operations needed to run it, ready by June. Two pilots followed, one on laptops covering desktop and web clients, and one on mobile devices through the Commission's device management platform. From July to September the laptop rollout reached all users in waves, completing in September. A mobile rollout and the shape of federation are now being explored.
Scaling to 40,000 users surfaced problems
Rolling out to 40,000 people exposes issues no pilot reveals. The team identified four main ones.
The first concerned finding colleagues across servers: the Commission runs several Synapse homeservers, and early on users on different servers could not always find each other. Working with Element, the teams fixed this, and a plain user search now finds anyone in the Commission regardless of server.
The second came from letting users create their own accounts rather than provisioning them in advance. As a result, colleagues who had not yet registered could not be found, which made the previous problem worse while adoption was still growing.
The third was live presence, the online or away indicator. As more users joined, its load began to affect performance, so it was switched off. A user status feature being developed with Element is intended to replace it.
The fourth concerned infrastructure, which had to adjust itself: rolling out in waves over three months meant uneven, shifting demand, so the system was tuned to adapt automatically.

Image: matrix.org — https://matrix.org/
Underlying all of this was the balance between security and usability. Most hardening was agreed with the Commission's security teams before the rollout and continues through regular reviews. The team aimed to ensure that protections did not complicate everyday tasks such as creating, recovering or verifying an account on a new device, and documented those steps clearly for staff. Feedback from tickets, internal forums and public channels feeds into prioritised goals for the institution's roadmap.
Element complements rather than replaces
The most frequent question, Gheorghe said, is whether Element is meant to replace Microsoft Teams or consumer apps such as Signal and WhatsApp. The answer is no, not directly. Element is positioned as an internal communication tool for specific use cases, including secure communication, where the existing stack does not fully meet needs. Teams bundles communication, collaboration and a whole platform, so there is no like-for-like swap.
Managing expectations is therefore part of the work. People naturally compare workplace tools with apps they use at home and look for feature-by-feature matches. Gheorghe argued this must be addressed openly in any organisational change: Element is a tool with its own feature set, which the Commission and Element can develop together. Part of the aim is to move work conversations onto a tool the institution controls.
Federation goes beyond technology
The Commission has long been interested in federation. The obvious starting point is other EU institutions, but the scope could extend to member states, governments and non-governmental organisations.
No decision has been taken, and the institution is moving step by step. First comes the technical question of what the technology can actually do, because policies cannot be written for capabilities that do not exist. Then comes governance: who the partners would be, on what terms, with what scope, and how security and privacy would be handled.
The Commission's lessons
Vignide closed by listing what the deployment taught the institution. Sovereignty is operational: it depends on day-to-day control and the trustworthiness of the whole chain of partners, not only on where the service is hosted. Adoption depends on everyday usability: being discoverable, onboarding support and everything around the product determine whether people use it. Interoperability needs more than technology: it requires clear structure, participation and governance.
Vignide added that introducing a new communication tool has been, and remains, a journey, and that the Commission has relied on trustworthy service providers, describing the collaboration with Element as a success.

No comments yet. Be the first!