Pre-alpha · not launched No bootable image yet. Nothing to download.

SingularityOS

An open-source, memory-safe desktop operating system — built for the AI era.

A friendly downstream of Redox OS, the Rust microkernel. What makes SingOS different is not the code. It is who is allowed to write it, and how it gets checked.

The gap

Personal computing runs on two proprietary operating systems. Linux is a magnificent server kernel wearing a desktop as a costume, and it is forty years of C. Redox OS proved that a modern microkernel desktop OS can be written in Rust from the ground up — and then, in March 2026, it decided that the single largest new source of engineering capacity in human history is not welcome.

We think that is a mistake, and one we can fix without disrespecting the people who made it. Redox is MIT-licensed. Its authors chose that license so others could build on their work. We are doing exactly that.

The bet

AI contribution is not the risk. Unverified contribution is. Every serious project has always had a contributor it did not fully trust: the drive-by patch, the new volunteer, the well-meaning expert in the wrong subsystem. The answer was never to ban them. It was review, tests, and a process scaled to the blast radius of the change. AI makes the volume higher and bad code more plausible. So the process must be stronger, not closed.

The pipeline is the product. Code is cheap now; trust is not. Our most important artifact is not the kernel — it is the pipeline that decides what gets in: boot tests, fuzzing, Miri, Clippy, hardware matrices, required test evidence, disclosure, and human sign-off tiered by subsystem. If that pipeline is good, the OS will be good. If it is not, no policy will save us.

A community of humans directing AI agents, under a verification process designed for exactly that, can build and maintain a desktop operating system faster and more safely than either humans alone or agents alone. We are going to find out.

Scope

What this is

  • A desktop OS for a laptop on a desk, not a rack in a data center
  • A downstream that tracks, credits, and never misrepresents upstream Redox
  • A project where every change — human or machine — is signed for by a human
  • MIT-licensed, like Redox

What this is not

  • Not a Linux distribution
  • Not a Redox hostile takeover, rename, or “Redox but with AI”
  • Not a research OS — it has to ship
  • Not a place where “the AI wrote it” is an excuse

Where it stands

  1. Nov 2026
    Foundationnow
    Founding documents, the contribution policy, the org, and the rules — written before anyone is invited.
  2. Dec – Jan 2027
    First light
    A rebranded, reproducible image produced by our own CI and boot-tested every night.
  3. Feb – Mar 2027
    Launch
    Open the doors. Moderation, the RFC process, and the first external contributions landed correctly.
  4. Q2 2027 →
    Sustain
    A hardware lab, maintainers who are not the founder, and a 0.1 that installs on real laptops.

Dates are targets from a 2026-11-04 start, not promises. Each phase has an exit criterion; we don't move on until it is met.

Read the rules

There is nothing to install and nothing to join yet. There is a great deal to read, and the policy is the part worth arguing with.

  • The repository Everything below lives here. Watch it — that is the announcement channel until there is a blog.
  • AI contribution policy The heart of the project. Disclosure, tiers, and what gets a pull request closed.
  • Manifesto Why this exists, at length.
  • Roadmap The phases above, with their checklists and exit criteria.
  • Discussions Open. Expect slow replies; there is one of us.
  • Report a vulnerability Private advisories are enabled on every repository.