In design. Proofs under way.

A space to create.

sutraOS is Linux for small, distributed workgroups of makers. It explains itself, it can undo anything it did, and then it gets out of your way.

The wallpaper follows your day. It is a setting, off until you turn it on. What you work in never changes colour.

A drawing of the design, not a screenshot. The files and maps are invented, and Fold and Geister, in the dock, are apps that do not run on sutraOS.

The whole system is built to keep two promises.

Everything else in the design exists to keep these two. The system never surprises you.

1

It explains itself.

Ask why about anything on the machine. The answer names a cause and shows its evidence. When the records do not connect, it says what is not known.

An illustration. The first version of why answers four questions, and has been run against real records on the Dell.

How why works

2

It can undo anything it did.

Every system change lands in a timeline. Undo puts back only what that change touched, so the work you did afterwards stays where it is.

  • Today 14:02You installed Blender
  • Today 09:15The system updated itself
  • Friday 18:40You let Blender reach the network

An illustration. Entries stay undoable for 30 days unless you change the number.

How undo works

Built for small workgroups of makers.

Creators, builders, maintainers and designers who work apart and ship together. Each of them gets the same calm, coherent machine.

First release

One person, one laptop.

Small and finished.

Stage 2

Your machines, together.

Sharing between your machines, sync and remote access.

Stage 3

More power, shared.

The workstation, and work spread across your machines.

The stages are a plan with no dates. Nothing has shipped.

Five rules decide everything else.

  1. 01

    Explain itself

    Every behaviour can be traced to a cause with why.

  2. 02

    Undo anything

    Every change lands in a timeline and can be reversed.

  3. 03

    Coherence over choice

    One toolkit, one compositor, one set of guidelines, enforced.

  4. 04

    Honest limits

    Each supported machine has a published list of what works. Numbers are targets until measured.

  5. 05

    One owner with taste

    Most pieces exist in Linux already. What was missing is one owner who decides, tests and says no.

Where it stands.

As of 16 November 2026. Each idea that could sink the design gets a small proof before anything is built on it.

See each step
The design
Written
Proof 1, the undo timeline
Yes, with conditionsRun in a virtual machine
Proof 2, why
Round one: yes, with conditionsRound two, on a real machine, not started
Proof 3, surviving a graphics reset
Yes for the whole graphics chip; no for one hung appRun on the Dell
Proof 4, text rendering
Yes, with conditions
Proof 5, sleep on the PC laptop
Round one: yes, with one conditionRun on the Dell; the overnight round is still to run
why, first version in Rust
Written, answers four questions
A system you can install
Not yet

Follow the build.

Each step is written down as it happens: what ran, on which machine, and what failed.