Skip to content
@NoWayOS

NoWayOS

Single Purpose OS. A computer with nothing else to do.
NoWayOS

Single Purpose OS

A computer with nothing else to do.

No browser. No desktop. No shell. No OS login. Just one job, built from only the code it needs, sealed in compartments on the seL4 microkernel and written in Rust.

Start here

The quickest way to begin is the starter: a small application on NoWayOS that is ready to run and to change. It has two screens written in React, about sixty lines of Rust that join them, and a seL4 system to boot it on. You need no Rust and no seL4 knowledge to start.

git clone https://github.com/NoWayOS/starter.git my-app
cd my-app
make setup        # once: fetches NoWayOS and the Screen Compiler, builds the dev container
make dev          # your application at http://localhost:8017/, following your edits
make qemu VNC=1   # the same application, booted on seL4 in QEMU

Change a screen and save. It is checked, converted to Rust, rebuilt and showing again about a second later, on the screen you were on. You need git, GNU Make and Podman, and nothing else: the Rust toolchains, seL4's Microkit SDK and QEMU are inside the dev container, pinned to exact versions.

Start your own application has every step.

Purpose is built in. Everything else is left out.

A Single Purpose OS is built for one device's one job, rather than built to run anything and then locked down to one thing. Three things make it one:

  • Built for one job. The device image holds its application, the drivers that application uses and the kernel. Nothing another job might need is there: no browser, desktop, shell, package manager or user account.
  • Sealed inside. Each part (the screen, the input, the network, the application) runs in a compartment of its own and reaches only what it was granted. A fault in one part is designed to stay there.
  • Shows its working. It comes with the evidence of what is inside and what each part may do: every grant written down, every component listed, and checks anyone can run.

Not kiosk mode, which locks a general-purpose system to one app and leaves everything else in place. Not a single-user OS, which limits who uses a computer, not what is in it.

You love React. So do we.

Write your screens in React. The Screen Compiler turns them into native Rust components that run directly on NoWayOS: no browser, no JavaScript, no web page to attack.

Exact or nothing. It converts its subset exactly and refuses anything else with the file, line and column. It never guesses.

It began with the places that can't afford a bad day

We didn't set out to write an operating system. We set out to protect a few very important devices: the controls that keep power flowing and water clean, the gateways that carry their data out, the terminals in the control room. Every one of them had one job. Every one ran an operating system built to do thousands.

So we asked the opposite question: what if the device held only its one job? We started from seL4, wrote everything of ours above it in Rust, sealed each part in a compartment of its own and left out everything else. Then we wrote down the evidence, so nobody has to take our word for it.

Then we looked around. Nearly every dedicated device has one job. What began as armour for critical infrastructure turned out to be a better way to build all of them.

When everything depends on it, give it one job.

The projects

Project What it is Licence
NoWayOS The Single Purpose OS. Protection-domain patterns on seL4 and Microkit, typed messages, drivers, networking and a native user interface. MIT OR Apache-2.0
Screen Compiler Design in React. Ship native Rust. No browser on the device. MIT
Showcase Secure applications you can run on a Raspberry Pi. MIT OR Apache-2.0
Defence Agent The gates every contribution must pass, out of reach of the pull request. MIT OR Apache-2.0

All four are open source, and so is the starter (MIT OR Apache-2.0). Clone them, build them and check every line for yourself.

Where it stands

In development and not ready for production. It runs in QEMU and on the Raspberry Pi 5; NXP i.MX8 is the intended production hardware.

seL4 has machine-checked proofs of correctness and security for specific configurations. NoWayOS uses seL4's mixed-criticality configuration, whose AArch64 proofs are in progress, so no NoWayOS image is inside seL4's completed proofs today.

To report a vulnerability, please write privately, as each repository's SECURITY.md describes, and not in a public issue.

Find out more

www.nowayos.com · Developer guides · How it works · Security and evidence · Journal · Glossary · Questions

NoWayOS is sponsored by Adappt.ai.

Pinned Loading

  1. nowayos nowayos Public

    The Single Purpose OS: your Rust application, with only the drivers it uses, built onto the seL4 microkernel. No browser, shell or package manager to exploit.

    Rust 48

  2. starter starter Public template

    Start your own application on NoWayOS: two screens in React, sixty lines of Rust and a seL4 system to boot it on. Clone it, make setup, make dev.

    Rust

  3. showcase showcase Public

    Secure kiosks on NoWayOS: visitor sign-in, service desk and pay-at-the-pump examples that run on a Raspberry Pi 5 and forget each person when the session ends.

    Rust

  4. screen-compiler screen-compiler Public

    Design in React, ship native Rust. Converts a subset of TSX into Rust UI code for NoWayOS at build time, so the device has no browser or JavaScript.

    Rust

  5. defence-agent defence-agent Public

    The security gates every contribution to NoWayOS must pass, kept out of reach of the pull request, and the agent that runs them.

    Python

Repositories

Showing 6 of 6 repositories

People

This organization has no public members. You must be a member to see who’s a part of this organization.

Top languages

Loading…

Most used topics

Loading…