XerisOS boots straight from UEFI into its own kernel — no Linux, no hypervisor, no vendor runtime. It draws its own desktop, drives its own hardware, and runs an unmodified build of Chrome by speaking Linux at the syscall boundary rather than shipping one.
The hard part was never drawing a window. It was everything a real application assumes exists underneath it — threads, futexes, epoll, shared memory, sockets, a compositor, a filesystem that survives power loss. XerisOS implements that surface itself, then proves it by running software that was never written for it.
UEFI hands control to XerisOS directly. A/B slots with automatic rollback mean a bad update costs a reboot, not a reinstall.
NVMe, AHCI, xHCI and USB storage, Ethernet, Wi-Fi and Intel HD Audio drivers written in-house against the real specifications.
A Wayland compositor inside the kernel — applications hand it pixel buffers and it puts them on the glass. No X11, no display server process.
Chrome is not recompiled for XerisOS. The binary is the same ELF a Linux machine runs. XerisOS
implements the syscalls it makes — mmap, futex, epoll,
memfd_create, sendmsg with SCM_RIGHTS — and answers them honestly.
When the browser asks for shared memory to draw into, it gets real shared memory.
A language model that loads from local storage and answers on the CPU it boots on. No account, no API key, no request leaving the device. The OS also speaks: a formant synthesiser generates speech from phonemes rather than shipping recorded audio.
Full Chrome, composited by the kernel.
Browse, rename, open by type.
Editing with crash-safe autosave.
A real shell over the FAT volume.
Write and build without leaving the OS.
An embedded JavaScript engine.
Decode and play locally.
A voxel world, as a loadable module.
Every layer between your hardware and your work is a layer that can watch you. XerisOS removes them.