Public-sector Matrix deployments keep making the same argument from different countries. Germany's FITKO is building Neo for government-to-citizen exchange, with the SDKs published under EUPL-1.2. On September 14, France's ADULLACT and the Déclic network launched the Matrix Federation of Local Governments — messaging infrastructure for municipalities, run by municipalities.

The press release is the usual press release. The design choices underneath it are the part worth stealing, and so are the gaps.

What launched

The federation lets each local government or PDSO (public digital service operator) run its own Matrix homeserver while staying connected to a dedicated network of other public actors. Each organization picks its connection mode: own infrastructure with its own team, hosted by a regional PDSO, or outsourced to a provider. Four municipalities ran the pre-production phase; new members can join now. User-facing client is Element. The framing from ADULLACT's director: it's "a bit of a Tchap for the territories" — and the launch was covered by the French trade press as a sovereign alternative to WhatsApp for municipal staff.

The three choices that are actually copyable

1. Closed federation with trust levels, not an open public room. The network is restricted to identified public actors, with multiple trust levels that adapt connection conditions to each organization's technical and organizational guarantees, anchored in identity management and ProConnect authentication. This is the same architecture Tchap uses for state agents, applied to municipalities. It is a deliberate answer to a real operational question — a city clerk's working channel should not be one server-hop away from an anonymous account — and it is a design a fire district, a hospital network, or a school system can reuse: a federation scoped to a community of identified operators, not the whole internet.

2. A Long Term Support contract with Element. The federation signed a renewable LTS agreement with Element covering multi-year security update availability. The trade press reports this came out of months of negotiation so the contract would fit how French local governments actually procure. Whatever you think about Element specifically, the pattern is the point: an operator that cannot maintain its own stack converts "the upstream project will keep existing" from hope into a contractual obligation. That is the same bus-factor logic this site keeps applying to single-maintainer tools — the difference is that here a collective answers the bus factor, and there a paid contract does.

3. Interconnect with the state, don't merge with it. Tchap — the state agents' Matrix system — is not being replaced; the federation is planning interconnection with it, with technical requirements being worked out with DINUM, targeted for the end of the year. A municipality keeps its own server and its own directory and can still exchange with the prefecture. Federation as the unit of integration: the sovereign layer is per-organization, the interoperability is the network.

The gaps, stated plainly

  • The LTS contract is a single-vendor dependency. It buys update availability for years, not forever, and it is renewable, meaning it can lapse or get repriced. The honest reading: this is the public sector paying for maintainership — which is exactly the sustainability problem this site argues needs solving — done in the one way that works today for an organization that cannot patch Synapse itself.
  • The federation directory does not exist yet. Pre-production surfaced the need for a federated directory so users can find people across municipalities; it is on the roadmap, not shipped. A closed federation of identified actors with no shared directory is a list of servers, not yet a network.
  • Trust levels are a governance object, not a spec. The press material describes levels, not the criteria that assign them. When the criteria are published, that document will matter more than the launch release.

Why this one matters here

The audience question this site optimizes for is: what does a small organization actually do on Monday? For a community running its own chat — or deciding whether to keep renting a channel from a vendor — this launch is another datapoint in the same argument Germany's Neo made: the protocol is open, the federation can be scoped, and the operator question has more than one answer. A community that wants messaging it controls does not have to run an open-to-everyone server. It can run its own homeserver, join a federation of peers it can identify, buy LTS from whoever maintains its server software, and interconnect with other networks when the work justifies it. France's local governments just shipped all four moves in one design.

Sources: ADULLACT press release, September 14, 2026 (EN); ADULLACT announcement; Acteurs Publics, September 17, 2026; Smart City Mag, September 18, 2026; Banque des Territoires / Localtis, September 17, 2026.