Digital autonomy is a design choice.
For organisations that want to depend less on suppliers outside Europe, and want more insight into the software they rely on.
An own kernel and core code, with deliberate choices about outside dependencies.
Exceptions are reviewed, recorded, re-reviewed and get a phase-out plan.
Desktop, server and profile management from one maker, designed to fit.
EUZOS is in development. We only name what works and only hardware that was tested.
Control starts at the core.
EUZOS develops its own kernel and core code in Rust. Outside components only come in as a deliberate, recorded exception.
Kernel, drivers, network, TLS, desktop and apps are developed as one platform.
Rust, signed kernels and packages, and TLS 1.3 with post-quantum key exchange (X25519MLKEM768).
A new kernel first starts as a trial. If that fails, the machine starts the previous version by itself.
Data and drivers are updated without a new kernel; apps are separate, signed packages.
Chromium, Mesa and the Intel media driver are outside components. Every exception is recorded, re-reviewed and has a phase-out plan.
In development.
EUZOS has no general release yet. This is what works now, what is in progress and what is coming.
Works
- Own kernel and desktop with several screens
- Browser on Chromium with video on the GPU
- Mail with Microsoft 365 and IMAP
- Trial start and rollback of updates
- Sign in with phone or work account
In progress
- Password vault with passkeys
- Web server and DNS for EUZOS Server
- Calendar tied to the profile
- EUZOS Code, an own code editor
Coming
- More tested hardware
- A larger app catalogue
- First general release [TO FILL IN]
EUZOS