Get started with NoWayOS

From an empty folder to seL4 booting in QEMU, then on a Raspberry Pi 5. Every command here runs in NoWayOS's dev container, so your machine needs very little.

Before you start. NoWayOS is in development and not ready for production: every API is provisional and will change. The repositories are being prepared for publication, so until they are public, cloning them needs access to the NoWayOS organisation on GitHub.

New to the words? The glossary explains each in a line or two.

Start here

Getting startedBuild NoWayOS's dev container and run its clickable demo, every frame checked, with no hardware and no seL4 knowledge needed.
Your first system in QEMUBoot seL4 in QEMU with one Rust protection domain, read the three files that define a system, watch seL4 stop a part that reaches too far, and click through the user interface.

Understand

How a system fits togetherProtection domains, capabilities and channels; the system description and its grants file; typed messages; input; faults, the supervisor and the fail-safe state; and building your own systems beside NoWayOS.

Build

Screens from ReactDesign screens in React and TSX, and let the Screen Compiler turn them into native Rust for NoWayOS at build time: the supported subset, the commands, and why it refuses rather than guesses.
Running on a Raspberry Pi 5What to buy, how to build and write the SD card, how to read and check the board's serial log, and how to run systems on the Pi 5 unattended or watch the user interface on its HDMI screen.

Check and contribute

Checks and evidenceWhat make ci runs and what each check shows, the ground rules every crate keeps, how to read an image's seL4 record and bill of materials, and how the gate stays fast.
Getting help and contributingWhere to ask a question, report a bug or a vulnerability, and how to propose a change to NoWayOS.