Quick Answer: The European Commission Matrix rollout moved from a proof of concept in December 2025 to every Commission laptop by September 2026. The tool is built on Matrix by Element, hosted with sovereign cloud providers, and run by the Commission itself. It now serves more than 40,000 users.
Plenty of organisations say they want sovereignty over their communications. Few actually run it. The European Commission Matrix rollout is one of the clearest recent examples of doing it at scale. A proof of concept became a Commission-wide service in nine months, and the team has been unusually open about what broke along the way. As Element reported from The Matrix Conference 2026, the lessons apply well beyond Brussels.
Sovereignty Is Five Decisions, Not One
Most people hear "sovereign" and think about server locations. The Commission started somewhere else. Before choosing any technology, its team defined sovereignty across five dimensions:
- Resilience and business continuity
- Vendor diversity
- Control over data
- Ownership of the platform
- Leverage in procurement, meaning the ability to negotiate with a supplier or walk away from one
The last item is the one most organisations skip. Without it, you can own your data and still be locked into a vendor whose terms you can't change. Procurement leverage is what keeps the other four dimensions real over a contract's lifetime.
Here's the practical takeaway: write your own list of dimensions before you open a tender. Score each candidate against it. If a vendor can't tell you what happens to your negotiating position in year four, that's a finding, not a footnote.
Sovereignty also doesn't mean building everything yourself. As the Commission's team put it, it means choosing who you depend on, and on what terms. That distinction matters for any team trying to build digital sovereignty for governments without a government-sized engineering budget.
Why Interoperability Pushed the Choice Toward Matrix
For internal communications, the Commission's priorities were resilience, data ownership and interoperability. Interoperability is what pointed them to Matrix. Matrix is an open protocol, and its value comes from letting separate systems talk to each other. A closed product can be secure and well designed and still trap you.
The team chose Element Server Suite Pro (ESS Pro), Element's enterprise distribution of Matrix, as a mature implementation. They then decided to host, operate and architect the service under their own control. This is the counter-intuitive part. Most organisations treat a managed SaaS product as the low-risk option. For the Commission, operating the service was the way to keep the leverage described above.
There's a real trade-off. Running your own stack means your team owns the on-call rota, the upgrades and the security posture. It's a cost you accept in exchange for control. Organisations without a dedicated platform team should price that cost honestly before copying this model.
Three Architecture Decisions That Shaped the Service
The team made three decisions that define how the service works today:
- Hosting. The service doesn't run in a Commission-owned data centre. It runs with sovereign cloud providers selected through a sovereign hosting tender awarded earlier in 2026. That tender was the way to meet the Commission's sovereignty and hosting requirements without building facilities from scratch.
- Identity. The deployment integrates with EU Login, the sign-in staff already use every day. This is a small decision with an outsized effect. A new tool is easier to adopt when logging in feels familiar, and it avoids creating a second set of credentials to manage.
- Federation. Connecting to Matrix servers outside the Commission is still under assessment. The technical side is being explored, including a hands-on demo at the conference using non-production environments. But federation also needs governance, participation and structure. Agreeing those takes longer than a configuration change.
Most people stop at the first two and assume federation will follow quickly. It won't. Federation is where the technology meets policy, and policy moves at its own pace.
Nine Months From Proof of Concept to Every Laptop
The Commission began working with Matrix in summer 2025. The timeline that followed was fast for a public institution:
December 2025. The architecture and engineering team delivered a proof of concept showing that Matrix and Element were viable for the Commission. It earned a green light for a Commission-wide service. Alexandru Vignide, the service delivery manager, described it as a nice Christmas present.
January to June 2026. The team built production infrastructure, along with the hosting and operations needed to run it. It was ready by June.
Pilots. A laptop pilot covered both desktop and web clients. A mobile pilot followed through the Commission's mobile device management (MDM) platform.
July to September 2026. The laptop rollout reached all Commission users in waves and finished in September.
Two things stand out. First, the pilots tested the clients before the scale-up, not the server. Second, the waves gave the team a controlled way to watch demand grow. That second point becomes important in the next section.
Four Problems That Only Appeared at 40,000 Users
Rolling out to 40,000 people surfaces problems no pilot will. The team hit four, and each one is a useful warning for anyone planning a similar rollout.
Colleagues couldn't always find each other
The Commission runs several Synapse homeservers. Early on, people on different servers couldn't always find one another. The teams worked with Element to fix this. A plain user search now finds anyone in the Commission, whichever server they're on. If you run multiple homeservers, test cross-server discovery in your pilot. Don't assume it works because single-server discovery does.
Accounts only appear after sign-up
The Commission chose user-led account creation rather than pre-provisioning every account. That's a reasonable privacy and adoption choice. The catch is that you can't find a colleague who hasn't registered yet. While adoption was still ramping up, this made the discovery problem feel much worse than it was. Here's the failure mode to plan for: early adopters see an empty directory, conclude the tool is broken, and stop using it before the network effect kicks in.
Live presence had to go
As more users came on board, the load from live presence (the real-time online and away indicator) started to affect performance. The team disabled it. They're now working with Element on a user status feature as the replacement. The lesson is that features which feel lightweight in a pilot can become expensive at scale. Presence is a good example of a feature that scales with the number of connections, not the number of messages.
Infrastructure had to scale itself
Rolling out in waves over three months meant demand was uneven and kept shifting. Manual capacity planning couldn't keep up. The team tuned the infrastructure to adjust automatically. If your rollout will be staged, ask whether your infrastructure can handle a moving target, not just a peak.
Running through all four problems was the balance between security and usability. Most of the hardening was done with the Commission's security teams before the rollout, and it continues through regular security reviews. The team also made sure hardening didn't block everyday tasks such as creating an account, recovering it or verifying a new device. They documented those steps clearly for staff. Verification prompts, for example, are where security friction usually turns into support tickets. Feedback from tickets, internal forums and public channels is now consolidated into prioritised goals for the Commission's roadmap.
Element Doesn't Replace Teams. It Fills Gaps.
The most common question the Commission gets is whether Element is meant to replace Microsoft Teams or consumer apps like Signal and WhatsApp. Diana Gheorghe, Head of Sector for Digital Workplace Communication and Collaboration Services, gave a direct answer: neither, directly.
Element is positioned as an internal communication tool for specific use cases, including secure communication, where the existing stack doesn't fully meet the Commission's needs. The table below shows how the three options differ in role and control.
| Option | Role in the Commission's stack | Who operates it | Matrix interoperability |
|---|---|---|---|
| Microsoft Teams | Bundled communication, collaboration and platform | Microsoft-operated cloud service | None |
| Element (Matrix) | Targeted internal comms for specific use cases | Commission-operated on sovereign cloud | Native; federation under assessment |
| Signal / WhatsApp | Personal messaging apps | Vendor-operated, outside employer control | None |
Teams bundles a whole platform, so there's no one-to-one swap. Expectation-setting is part of any change like this. People naturally compare workplace tools with the apps they use at home and look for feature-for-feature matches. Diana's view is that this mindset needs to be addressed head-on. Element is a tool in its own right, with its own feature set, and it will evolve alongside the Commission.
Federation raises the same question at a larger scale. The Commission has long been interested in it, starting with other EU institutions. It would then extend to member states, governments and non-governmental organisations. No decision has been made. The order matters. First comes the technical question of what the technology can do, because, as Diana put it, there's no point writing policies technology can't deliver. Then comes governance: who the partners would be, on what terms, with what scope, and how security and privacy would be handled. That sequence is one of the most transferable lessons in the whole story.
Frequently Asked Questions
what is the European Commission Matrix rollout?
The European Commission Matrix rollout is the Commission's program to deploy a sovereign internal communication tool built on the Matrix open protocol and Element Server Suite Pro. The Commission runs the service on sovereign cloud providers, integrates it with EU Login, and now serves more than 40,000 users. Laptop rollout to all Commission users finished in September 2026.
how long did the European Commission take to roll out Matrix?
The Commission went from a proof of concept in December 2025 to a Commission-wide laptop rollout completed in September 2026. That's roughly nine months. Production infrastructure was ready by June 2026, after which pilots covered desktop, web and mobile clients before the staged rollout began.
why did the European Commission choose Matrix?
The Commission chose Matrix because its priorities were resilience, data ownership and interoperability. Matrix is an open protocol designed so separate systems can communicate, which avoids lock-in to a single vendor. The Commission then chose Element Server Suite Pro as a mature implementation and decided to host and operate the service itself.
why isn't federation enabled yet?
Federation is still under assessment because it needs governance as well as technology. The Commission must first confirm what the technology can deliver, then decide on partners, terms, scope, security and privacy. Agreeing those elements takes longer than a configuration change, so the Commission is moving one step at a time.
how do you avoid discovery problems when rolling out Matrix to thousands of employees?
Test cross-server user search during your pilot if you run multiple homeservers, since the Commission had to fix this with Element. If you use user-led account creation, expect an empty directory early on. Communicate that clearly so early adopters don't abandon the tool before enough colleagues have registered.
Take the Lesson Into Your Own Rollout
The single most useful takeaway is that sovereignty is operational. It depends on who controls the platform, how you negotiate, and whether the people using it actually adopt it. This week, write your own five sovereignty dimensions, score your current communication tools against them, and note the weakest one. Pass this article to whoever owns your procurement terms, because the European Commission Matrix rollout shows that the contract is part of the architecture.