← PolymerOS /downloads/

Choose your stability.
Or don't.

Four channels, honestly labeled. Three of them don't exist yet — we'd rather show you an empty shelf than a promise wearing a version number.

Stable · general users

For people who want their computer to simply work, every day, without an opinion about it. Signed by keys held by humans in separate jurisdictions, updated only when we'd run it on the machine that holds the family photos.

none yet — and we respect you too much to pretend otherwise

Beta · broad testing

For people who file good bug reports and enjoy being three months ahead of their friends. Feature-complete builds proving themselves before promotion.

none yet — Beta is earned, not declared

Alpha · early testing

For people who consider a boot loop a puzzle rather than a problem. New subsystems land here first, wearing their amber ring with pride.

none yet — the rings must be earned here too

Chaos · agentic chaos build

Built by autonomous agents, reviewed by a different intelligence, booted in a VM that cannot hurt anyone. Every build here survived its own test gauntlet — compile, boot, compartment checks, trust rings rendering — minutes before you clicked. It worked for the machines. Your hardware may have opinions. That's the deal: newest ideas, quarantine-violet ring, no promises beyond the checksum.

Apple Silicon · aarch64 M1/M2 Macs, 16K pages, live USB no build currently passing — the agents are on it
AMD64 · x86_64 commodity hardware, same compartment model no build currently passing — the agents are on it

No hardware harmed

Test-drive in QEMU first (we do)

Chaos and Alpha builds don't ask for your boot disk. Every download ships with polymer-qemu-run.sh — the same runner the build agents use to verify their own work. It boots the image in a VM with a persistent home disk, and in-guest updates track your channel exactly like a native install:

sha256sum -c SHA256SUMS      # trust, but verify
./polymer-qemu-run.sh .      # boots windowed; --display vnc for headless

What to expect: the guest runs comfortably in 4 GB of RAM (the default; --mem 8G if you'll open heavy compartments) plus a 20 GB persistent home disk created on first run. Graphics are software-rendered by default — fine for trying the desktop; on a Linux host with a GPU, virgl gives accelerated OpenGL inside the VM, and a native install on Apple Silicon gets the full GPU. KVM makes it feel native; without it, expect a patient boot.

Native installation stays a deliberate, separate act — and above Chaos, a signed one.

Every artifact ships with SHA256SUMS and a detached signature; verify before you boot. Chaos builds are signed with the development key (polymer-dev — fingerprints live in keys/ in the repository) — Stable will use production threshold keys that do not exist yet, on purpose. When a channel above says none, that is a feature.