ONCRIX.
A capability-based microkernel operating system written from scratch in Rust — memory-safe, #![no_std], and POSIX-compatible at the edges.
# build the microkernel for bare metal $ cargo build -p oncrix-kernel --target x86_64-unknown-none Compiling oncrix-mm, oncrix-vfs, oncrix-ipc, oncrix-syscall … Finished `release` profile in 11.2s $ cargo clippy --workspace -- -D warnings No issues found. # zero-warning policy across all crates
What is ONCRIX
A real, independent operating system
ONCRIX is not a Linux fork or a UNIX clone. It is an original microkernel built from the ground up in Rust, where the kernel does as little as possible — scheduling, memory, and IPC — and everything else runs as an isolated, user-space service.
Microkernel design
A minimal trusted computing base, user-space drivers and services, and IPC as the spine of the system.
Read more →Security by construction
Capability-based access control, privilege separation, Rust memory safety, and continuous adversarial auditing.
Read more →Where it stands
Builds for bare-metal x86_64, boots in QEMU, runs a POSIX-style userland — and keeps growing.
Read more →Core design goals
Four principles, no compromises
Every line of ONCRIX is written against the same four goals — enforced by Rust's type system and a minimal trusted computing base.
Stable
Rust memory safety, no undefined behavior, and graceful panic handling.
Secure
Capability-based access control, privilege separation, and a minimal TCB.
Extensible
Modular microkernel — user-space drivers and services, plugin architecture.
Fast
Zero-cost abstractions, lock-free structures, efficient IPC, minimal context switches.
The workspace
Ten focused crates
A clean separation of concerns — architecture-specific code stays behind the HAL, kernel-space crates depend only on core and alloc.
Built in the open
The source, the design docs, and the full history are public.