A small kernel
Ring 0 keeps only what has to be there: scheduling, virtual memory, interrupts, IPC and capabilities. Everything else runs in user space.
Version 0.19 · x86-64 · Rust no_std
AriCodeOS is a microkernel built in Rust with no Linux, BSD or any other kernel underneath. It boots through UEFI, gives each program only the capabilities it needs and runs storage, network and USB drivers as ordinary processes. From scratch means compared, not copied: where an established library measured better, as rustls or wasmi did, it is adopted (ADR 0063).
Small kernel. Independent processes.
Inside the system
Isolation has a visible result. This real boot-test excerpt shows a failed driver restarting and an unauthorised memory read being stopped.
[ INFO] AriBoot 0.9.0 (AriCodeOS UEFI loader)
[ INFO] slots: booting from slot A (image version 1)
[ INFO] ExitBootServices -> AriKernel
AriCodeOS booting...
[INFO ] vmm: own tables active, W^X on the image
[INFO ] smp: 4 CPUs online (3 of 3 APs started)
[INFO ] iommu: one domain per process with IOVA = physical
[INFO ] user: process 1 'init' created
[WARN ] user: process 3 'kernel_read' killed: #PF read
AriInit: crashy_driver crashed, restarting
AriInit: crashy_driver restarted successfully
ari>Design
AriCodeOS keeps legacy out, moves privileges out of ring 0 and treats security as a property of the architecture rather than a layer added at the end.
Ring 0 keeps only what has to be there: scheduling, virtual memory, interrupts, IPC and capabilities. Everything else runs in user space.
Having an identity does not imply having access. A program can only touch a file, a device or the network if it holds a handle that allows it.
virtio, xHCI, USB storage and the Realtek network card run as ring 3 processes. When one crashes, init restarts it and the kernel keeps running.
Rust no_std in the kernel, loader, drivers and services. Every unsafe block has to be justified, and W^X and NX are enforced from the first page table.
Signed system images in A/B slots. The new slot is tried, confirmed by init or rolled back, and user data survives the rollback.
UEFI only, 64-bit only: no BIOS, no ISA, no full POSIX. Old software may run on top one day; it will never define the kernel.
Architecture
Native programs · WebAssembly modules · future compatibility environments
aricode-rt · Capability API · manifests · sandbox
AriFS · network · compositor · supervisor · sshd
virtio-blk · virtio-net · virtio-input · xHCI · USB HID · USB storage · Realtek r8169
scheduler · virtual memory · IPC · interrupts · capabilities · SMP
x86-64 · UEFI · ACPI · APIC · PCIe · IOMMU
Status
Every capability is backed by scenarios that boot the system in QEMU on each test run. Since 0.9, the core of it also runs on a 2012 laptop.
The shell, the USB stick as system disk and wired networking; since 0.10, SSH, HTTPS and updates over the network, since 0.11, USB 2.0, since 0.14, updates straight from GitHub, since 0.18, the desktop, and since 0.19, the panel’s own resolution and the GPU’s engine.
Ring 3 processes, handles with rights and revocation, IPC with handle transfer and a sandbox per manifest.
AriFS with CRC32, an atomic replacement journal and end-to-end flush, tested with cuts injected in the middle of writes.
Up to four CPUs with IPIs and TLB shootdown; Intel VT-d with one translation domain per driver.
A toolkit of its own, menus, dialogs, a bar with a clock and a dock, and windows resized by their edges; five signed applications, each with a capability of its own, on top of the base system.
Signed driver packages, designed but not built; USB hubs and sticks plugged in after boot; on the Tiger Lake Lenovo, the new power-off and a DMA fault still to check; and ADR 0041, awaiting a decision.
Releases
Each version closes a group of roadmap phases, is tagged in git and goes through an audit.
21 Nov 2026 · 0.19.0
A desktop worth the name (ADR 0078), the first steps onto the reference laptop’s GPU (ADR 0080, 0083, 0086) and what a second laptop, a Tiger Lake Lenovo, taught. Ten architecture decisions and eight incidents; the whole suite passed with 1 and 4 CPUs, and the development build it comes from ran on the reference laptop.
Release notes5 Nov 2026 · 0.18.0
Every machine runs one base system, and the desktop is installed on top of it by the owner who wants it (ADR 0074). Six architecture decisions and one incident; the whole suite passed with 1 and 4 CPUs, and the desktop ran on the reference laptop with its PS/2 keyboard and touchpad.
Release notes2 Nov 2026 · 0.17.0
The owner gave “from scratch” its meaning: study the established implementations and their failures, measure ours against them for compatibility and for how fast the system runs, and keep the winner (ADR 0063). Each subsystem was compared on its own branch, with its measurements in an ADR and an independent audit: nine architecture decisions and six incidents.
Release notesTry it in Docker or on a laptop you do not use and tell us what happened. A hardware report, a star or a question: every bit helps, and it only takes a free GitHub account.