Newshot

How the European Commission rolled out Matrix to more than 40k staff

Original text(via Hacker News)

How the European Commission rolled out Matrix to more than 40,000 staff

How the European Commission rolled out Matrix to more than 40,000 staff
How the European Commission rolled out Matrix to more than 40,000 staff

The European Commission went from a Matrix proof of concept in December 2025 to a sovereign communication tool rolled out to every Commission laptop by September 2026. That tool, built on Matrix by Element ,and run by the Commission itself, now serves more than 40,000 users.

At Matrix Conference 2026, Diana Gheorghe, Head of Sector for Digital Workplace Communication and Collaboration Services, and Alexandru Vignide, Service Delivery Manager for the Commission's sovereign communication tool, told the story of how they got there. The pair were transparent about what got harder at scale, and how they dealt with it.

Sovereignty means more than where the servers sit

“Sovereignty” can have a different meaning for different people and organisations, so the Commission started by pinning down what it means for them. Their answer spans five dimensions: resilience and business continuity, vendor diversity, control over their data, ownership of the platform, and leverage in procurement - the ability to negotiate with, or walk away from, a supplier. That last one is easy to forget, and arguably the one that bites hardest when it's missing.

For internal communications specifically, the priorities were resilience, data ownership and, crucially, interoperability. That's what led them to Matrix: an open protocol whose value lies in letting separate systems talk to each other. They chose Element Server Suite Pro (ESS Pro), Element's enterprise distribution of Matrix, as a mature implementation, and decided to host, operate and architect the service under their own control.

Sovereign cloud hosting, familiar login, without federation (yet)

With the building blocks chosen, Alexandru walked through three architecture decisions.

Hosting. The service doesn't run in a Commission-owned data centre. Instead it runs with sovereign cloud providers selected through the sovereign hosting tender awarded earlier this year, in order to meet its sovereignty and hosting requirements. Sovereign doesn't have to mean building everything in-house; it means choosing who you depend on, and on what terms.

Identity. The deployment is integrated with EU Login, the sign-in staff already use every day. A new tool is easier to adopt when logging in feels familiar.

Federation. Connecting to Matrix servers outside the Commission is still under assessment. The technical side is being explored - there was a separate hands-on demo using non-production environments at the conference - but federation also needs governance, participation and structure, which takes longer to agree than a config change.

Nine months from proof of concept to every Commission laptop

The Commission started working with Matrix in summer 2025, or, as Alexandru put it, at last year's Matrix Conference. From there, things moved quickly:

  • December 2025: the architecture and engineering team delivered a proof of concept showing Matrix and Element were viable for the Commission. It earned a green light for a Commission-wide service, which Alexandru described as a nice Christmas present.
  • January to June 2026: the team built the production infrastructure, along with the hosting and operations needed to run it, and was ready by June.
  • Pilots: a laptop pilot covering both the desktop and web clients, followed by a mobile pilot through the Commission's mobile device management (MDM) platform.
  • July to September 2026: the laptop rollout to all Commission users, delivered in waves, was and completed in September.

The Commission is now exploring a mobile rollout, and what federation could look like.

Scaling to 40,000 users brought challenges

Rolling out to 40,000 people surfaces problems no pilot will. Alexandru described the four main ones his team ran into, and how they tackled each.

Finding colleagues across servers. The Commission runs several Synapse homeservers, and early on, people on different servers couldn't always find each other. The Commission's teams worked with Element to fix this, and now a plain user search finds anyone in the Commission, whichever server they're on.

Accounts that only appear after sign-up. The Commission chose user-led account creation rather than pre-provisioning every account. The catch is that you can't find a colleague who hasn't registered yet, which made the discovery problem above feel worse while adoption was still ramping up.

Live presence was switched off. As more users came on board, the load from live presence (the real-time “online/away” indicator) started to affect performance, so the team disabled it. They're now looking at a user status feature being developed with Element as the replacement.

Infrastructure had to learn to scale itself. Rolling out in waves over three months meant uneven, shifting demand, so the team tuned the infrastructure to adjust automatically.

Running through all of this was the balance between security and usability. Most of the hardening work was done with the Commission's security teams before the rollout, and continues through regular security reviews and continuous improvements. The team made sure that hardening didn't get in the way of everyday tasks like creating an account, recovering it or verifying a new device, and documented those steps clearly for staff. Feedback from tickets, internal forums and public channels is consolidated into prioritised goals for the Commission's own roadmap.

Element complements the Commission's toolset

The most common question, Diana said, is whether Element is meant to replace Microsoft Teams, or consumer apps like Signal and WhatsApp. The short answer: neither, directly. Element is positioned as an internal communication tool for specific use cases - secure communication among them - where the Commission's existing stack doesn't fully meet its needs. Teams bundles communication, collaboration and a whole platform behind it, so there's no one-to-one swap to be had.

That makes expectation-setting part of the job. People naturally compare workplace tools with the apps they use at home and go looking for feature-for-feature matches. Diana's view is that this mindset is something to address head-on in any organisational change: Element is a tool in its own right, with its own feature set, that the Commission and Element can evolve together.

Part of the goal is to bring work conversations onto a tool the Commission controls.

Federation goes beyond tech

The Commission has been interested in federation for a long time. The obvious starting point is other EU institutions, but it wouldn't stop there: the Commission also works closely with member states, governments and non-governmental organisations.

No decision has been made yet, and the Commission is taking it one step at a time. First comes the technical question of what the technology can actually 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 are handled.

The Commission's Takeaways

Alexandru ended the talk by sharing what the deployment had taught the Commission.

Sovereignty is operational. It depends on operational control and the trustworthiness of the whole chain of partners, not just on where the service is hosted.

Adoption depends on everyday usability. Discoverability, onboarding support and everything around the product shape whether people use it.

Interoperability needs more than technology. It also needs clear structure, participation and governance.

He also noted that introducing a new communication tool has been a journey, and still is. Along the way, the Commission has relied on trustworthy service providers, and he described the collaboration with Element as a success.

Thibault Martin
Thibault Martin

The text above was extracted automatically from the source page and may miss images, tables or code blocks. The original is authoritative.

Published by Hacker News
This site only summarises and aggregates; copyright stays with the original author. Headlines and summaries follow the source — where they differ, the original wins.
Read the original ↗