Talky: communications you own, for the year governments stopped renting theirs

On 18 August, Bloomberg reported that China’s Ministry of State Security has told state-linked bodies to strip a customised Windows 10 from their machines — pulling forward a retirement that was not due until February 2027. The story ran as a US–China headline, but the quieter version of it has been running in Europe all year. In January, France named a date: by 2027, its 2.5 million civil servants stop using Teams, Zoom, Webex and GoTo, and move to Visio — built with French firms, hosted on a French sovereign cloud. Denmark’s Digital Ministry spent last year walking off Microsoft Office onto LibreOffice. Schleswig-Holstein made LibreOffice the binding standard for its administration in December, two months after moving forty thousand mailboxes off Exchange. And in the Netherlands, The Hague blocked an American takeover of the Dutch cloud provider Solvinity in May, while Defence builds a sovereign cloud with KPN and Thales. Different governments, different politics, one shared conclusion: the assumption that everyone’s workday runs on the same rented foreign stack is ending. And when a government ranks what to take back first, communications sits at the top of the list.

Communications is where sovereignty bites first

There is a reason France started with the meeting, not the spreadsheet. A meeting is the most personal-data-dense hour of the workday — voices, faces, screen contents, the documents shared in the room — and it happens live, which means it happens wherever the platform is, under whatever law reaches that platform. That last part is not hypothetical: under the US CLOUD Act, a US-owned provider can face lawful requests for data even when it sits in an “EU region” — the point Microsoft conceded under oath to the French Senate in June 2025, and the reason “sovereign region” labels reduce exposure without removing the legal vector. France’s own stated rationale for Visio was security and control over where the conversation lives. Add the ordinary dependency costs — terms that drift, prices that change, features that appear and vanish on someone else’s roadmap — and the daily meeting turns out to be the sharpest instance of a general problem: the more essential the tool, the more it matters who decides.

The exit is real. It is also honest to say it is slow

We would be selling you something false if we described this as a stampede. Denmark’s ministry moved its office suite and kept Windows — the early “Denmark drops Microsoft” headlines were corrected. Schleswig-Holstein’s binding standard covers about 80% of workstations, with the tax administration deliberately excluded. Visio, after more than a year of testing, counts some forty thousand users against a target of 2.5 million. And the incumbent is not standing still: Microsoft has spent the year expanding sovereign-cloud commitments and loosening the bundling that ties Teams to the rest of the suite — real concessions, won precisely because the pressure is real. What has durably changed is not the market share; it is the question set. Public-sector procurement across Europe now asks, in writing: where does it run, whose law reaches it, can it run isolated, who holds the identity layer and the keys, and what does leaving cost. Those questions do not have good answers from inside a rented suite — which is the point of asking them.

Where Talky stands

Talky is our sovereign communications workspace, and it is built as an answer sheet to exactly those five questions. It is a real workspace, not just a meeting screen: video conferencing in three room types, messaging and DMs, an ArpBoard whiteboard, calendar, notes, file sharing, screen share and recording — on web, iOS, Android and desktop, so the whole of a team’s daily communication lives in one place. Session control is built in rather than bolted on: AES-256 encryption, a lobby and room-lock so nobody enters a meeting you did not admit them to, and role-based access control over who can do what. And the sovereign part is literal, not a label: Talky deploys on-premises or fully isolated, behind your own SSO, inside your own perimeter — so “where does the meeting live” has the one-word answer the procurement form is looking for.

• Video conferencing in 3 room types, messaging and DMs
• ArpBoard whiteboard, calendar, notes and file sharing
• Screen share and recording
• AES-256, lobby and room-lock, role-based access control
• On-prem or isolated deployment — web, iOS, Android and desktop

What we will not claim

Three honest limits, as usual. First, self-hosting is not a free lunch: a perimeter you own is a perimeter you must run, and uptime, patching and backups become your responsibility — for some teams a well-run European-hosted service is the right trade, and pretending otherwise would be marketing. Second, Beijing’s exit is not Europe’s: China is removing foreign software to tighten state control, Europe’s moves are about jurisdiction over its citizens’ data — we cite the same week’s news as evidence that the single-stack default is over everywhere, not as one story. Third, sovereignty is not isolationism. Denmark kept Windows; Kiel kept its tax systems; the point of owning your communications is not to leave everything, it is to hold the option to leave — because an exit is only cheap if you engineered for it before the day you needed it.

A rented meeting room can change its price, its terms and even its law overnight. The sovereign question was never “which suite is best” — it is “who decides”.

For Dutch and European teams, this is the home story of 2026. The Hague blocked the Solvinity takeover in May, Defence is building its own cloud with KPN and Thales, and the Tweede Kamer wants at least 30% of government cloud with Dutch or European providers by 2029. The GDPR layer was always there — a recording of identifiable people’s voices and faces is personal data, wherever it is processed — but what changed this year is that “where does the meeting live” became a procurement question with dates attached. Talky answers it inside your perimeter: on-prem or isolated, behind your own SSO, engineered for the GDPR from its first line — from Arpanet BV. Book a demo, or contact us and we will scope it with you.