We're looking at digital sovereignty and wondering how far a non-US stack could go beyond a proof of concept. What would you use for endpoints, management, identity, security and collaboration, and where are the biggest gaps?
Can a European IT stack realistically replace the usual US tools?
Answers
A possible starting architecture is self-hosted Linux servers on Proxmox, Keycloak for identity, and Nextcloud alongside Rocket.Chat and Jitsi for collaboration. XCP-ng with Xen Orchestra is another virtualization option to evaluate.
That gets you a set of components, not a complete replacement for an integrated suite. Check how accounts and access flow between them, who will operate each service, and whether the meeting and chat administration features meet your governance needs. Email, spam filtering and endpoint management still need their own answers.
Reply to this answer
Start with the desktop applications, not the desktop OS. Linux options such as Zorin, Mint and Ubuntu are worth testing, but a browser-heavy workforce and one dependent on Windows-only applications are very different migrations.
Central management is the awkward bit. Look at Uyuni or baramundi for device management, and test identity and policy requirements rather than assuming Samba is a drop-in replacement for every Active Directory and Group Policy feature. Run the pilot against the actual software and settings users need.
Reply to this answer
I'd separate the goal of avoiding US technology from the goal of controlling your data. Hosting on premises or with infrastructure in Europe, keeping local copies, and checking whether you can export usable files may reduce dependency even if some US software remains.
Portable formats matter here. An export that loses editing features or only produces a converted document is not the same as being able to move the original work to another tool.
_r26~velourtoggle.5:
That distinction helps. We'll need to define whether the requirement is supplier origin, hosting location, data portability, or all three.
Reply to this answer
Don't leave security until the end of the pilot. ClamAV is one option to investigate, but antivirus scanning alone doesn't establish that you have a centrally manageable replacement for an endpoint security suite. Check deployment, policy control, reporting and response capabilities against your requirements.
Also price the less visible pieces, such as web application firewalls. A minimum monthly commitment can be a poor fit for a small organization even when the product itself looks suitable.
Reply to this answer
There is also a reasonable case for not replacing everything. The existing integrated suites are convenient, and assembling alternatives brings operational work and tradeoffs. A partial move, such as keeping on-premises identity and email while evaluating different client management, may be more practical than an all-or-nothing deadline.
That still leaves US technology in the stack, so it only works if the actual requirement allows it. Open source and self-hosted don't automatically mean every component was made in Europe either.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Ravik.3z:
For meetings and chat, compare Nextcloud Talk with separate tools rather than assuming either setup has all the room administration controls you need.