Pengy, the PengyOS penguin

PengyOS

a Catbee project  ·  early release

A free, reproducible, verifiable Linux distribution built from source with Buildroot, for ordinary 64-bit PCs. Five editions, one build, signed updates that roll themselves back.

EARLY RELEASE

PengyOS is early. It's also comfortable enough to live on. The Desktop is a daily driver on Intel, AMD and NVIDIA machines: development, gaming, AI work and ordinary office tasks all happen on it, and its author has replaced Ubuntu on several of his own machines without feeling like he gave anything up. The honest gap is hardware — the more machines it meets, the more bugs turn up. Try it on a spare disk first. Download it here, and read the docs for how it works, everyday recipes and building it yourself.

# What is PengyOS?

Linux, built from source. PengyOS is assembled rather than derived: Buildroot builds every package from pinned sources against our own configuration, so there is no other distro hiding underneath it. It keeps the contracts everyone depends on — POSIX, ELF, systemd unit semantics, D-Bus, Wayland, freedesktop — and replaces only what earns replacement.

Assembled, not invented

Most of what a good system needs already exists upstream. The work is choosing it, integrating it, and occasionally replacing a piece — one component at a time, with the reasoning written down.

Reproducible by construction

Defined declaratively and built from source with Buildroot. 26.10.3's Core and Server came out byte for byte identical on two different build hosts.

Verifiable by construction

Every image carries a software bill of materials, and every release is signed. A change counts when a build, a boot and a behaviour test prove it, on a machine that didn't make it.

Maintained by a human–AI team, not a release cycle

An agent watches upstream releases and CVE feeds, drafts the change with its justification, builds it and runs the boot tests. A person signs the release key. The tooling has no code path that reaches the stable channel. How the loop works → And what came out of it, release by release: the PengyOS release log.

One base, three additive layers

        ┌──────────────────────────────────────────────┐
        │  DESKTOP   = Server + graphical stack + apps  │   the masterpiece
        ├──────────────────────────────────────────────┤
        │  SERVER    = Core  + remote-work + services   │   headless, comfortable
        ├──────────────────────────────────────────────┤
        │  CORE      = the shared, minimal, bootable base│   tiny, builds on it
        └──────────────────────────────────────────────┘
             (all three share one build engine + one verification layer)

Core is the exact base the other two are defined on, not a cut-down subset. A Desktop component may add; it may not contradict a Core decision.

# The Three Editions

Three editions, five images counting the NVIDIA versions of Server and Desktop. One build engine, one verification layer.

Core on metal

The base: systemd, key-only sshd, Python 3, nftables, chrony, storage tools and a broad firmware set. No editors, no containers, no GUI. Roughly 224 MB idle RAM.

real hardware · ~224 MB idle · reproducible

Server on metal

Core plus tmux, mosh, zsh, git, ripgrep, fd, bat and the rest of the comfort CLI; rootless podman; distrobox; a default-deny firewall; backup and metrics timers; and Pengy in a browser. Installs from its own USB stick and boots headless. The Server NVIDIA image adds CUDA, nvidia-smi and GPUs inside podman containers.

headless · real hardware · NVIDIA variant QEMU-tested

Desktop daily use

Server plus the whole COSMIC session behind a login screen: Wi-Fi, Bluetooth, PipeWire audio, printing, Xwayland and Vulkan, Flatpak from Flathub (Firefox, Chrome, Steam, Discord, VS Code), and 21 wallpapers. The Desktop NVIDIA image runs on an RTX 3060 Ti driving two 1440p monitors.

COSMIC · Wayland + Xwayland · PipeWire · Vulkan

What's in the base image (kernel, boot chain, init, the disk layout, provenance) and how software gets in: How PengyOS is put together.

# Screenshots

The Desktop edition, running on real hardware — COSMIC on Wayland, Flatpak apps, PipeWire audio, NVIDIA included. These are from an ordinary day's use, not a staged demo. There's more of it, including the apps that ship with the image, in the gallery.

The PengyOS Desktop: a COSMIC session with the app store open
The Desktop. A COSMIC session on Wayland with the app store open — Slack, Steam, VS Code, Spotify, GIMP and VLC are a click away through Flatpak and Flathub.
A PengyOS terminal window applying a live fix
The console. A live fix in progress: PipeWire audio defaults linked in, and a stale label cleared from the spare system slot — the kind of change the agent applies at runtime and then folds back into the build definition.

More screenshots and wallpapers →

# Status & What's Next

Every edition installs and boots, and installed machines update themselves from signed releases. The cadence is closer to a rolling release than an LTS — new builds land on the testing channel most nights — and that's on purpose. What's left is hardware coverage, workflows nobody has tried yet, and the bugs those turn up.

AreaStateDetail
Core boots on metal Installs, DHCP, key-only SSH, ~224 MB idle. Rebuilds byte for byte on a second host. Open: measured boot and in-place updates.
Server boots on metal Installs from its own USB stick and boots headless on real hardware. Server NVIDIA (new in 26.10.5) builds and boots in QEMU, and is next to be proven on a GPU server.
Desktop daily use Daily use on Intel and AMD laptops and mini PCs: login screen, audio, Bluetooth, printing, Flatpak apps and Steam games. It has replaced Ubuntu on several machines, and Desktop NVIDIA has run on an RTX 3060 Ti with two 1440p monitors since 26.10.7. Next: COSMIC from a Buildroot recipe rather than built on the host, accessibility and input methods, more hardware.
Downloads available Install images for all five editions, with signed checksums — see Downloads.
Updates working Signed releases over the air, with automatic fallback — the update feed, testing and stable channels.
Reproducible builds proven 26.10.3 built on two machines: Core and Server identical bit for bit. The Desktop matched apart from the host-built COSMIC set, which moves into Buildroot next.
Building on PengyOS works A whole build runs inside a container on a PengyOS Desktop. Core and Server came out identical to the same build on Ubuntu, so the distro can build itself.
Kernel & drivers upgrading On its first major kernel upgrade and its second major NVIDIA driver bump. Every edition is boot-checked in a VM, and the NVIDIA editions get run on a real card before they ship.
Hardware coverage the open work Stable on most of the hardware it has met, which is still a short list: Intel N100 mini PCs, Alder Lake and Kaby Lake laptops, a Ryzen 6800H, and RTX cards. Every new machine and workflow is where the next bug is hiding.
Maintenance loop running nightly Watches upstream releases, the kernel and CVE feeds, triages them with a local model, and since 2026-10-05 has built and published its own boot-checked images to the testing channel. Bug fixes and security fixes now arrive this way without anyone asking. Promoting a release to stable is still a person's decision.
Toolkit 76 tools Build, image, sign, verify, SBOM, QEMU harness, updater — each a tested project, all run by one gate.

# How It Maintains Itself

Upstream moves every week. PengyOS keeps up with a loop rather than a release cycle, and it's the same loop the rest of the fleet runs.

Observe → Propose → Build → Verify → Ratify (human)

Every evening the loop reads upstream releases, changelogs and CVE feeds for the pinned component set, triages what matters, batches the changes into one build, boots the result in a VM, and publishes it to the testing channel. It has no code path to the stable channel: promotion is a person's decision, made after the image has run on real hardware. The loop has been shipping its own releases since 2026-10-05.

It started out asking permission for everything. It now takes the routine work — security bumps, bug fixes, chasing a new upstream version — on its own, and stops for the calls that matter: what goes in the base image, what reaches the stable channel, anything that touches a signing key. Less of the day goes on minutiae, and the decisions still have a human behind them.

The loop in detail, the change tiers (what the agent may touch, what needs a signature), and the ten principles behind all of it: How PengyOS is put together.

# By the numbers

3
editions
76
tools
224 MB
Core idle RAM
1
command rebuild

To build it yourself: the build guide covers host setup, COSMIC, every edition, testing in a VM, and publishing your own signed updates. The short version is four commands on an Ubuntu 26.04 machine with KVM.

# Downloads

Write an image to a USB stick, start the computer from it, and install — or just try it.

Desktop

COSMIC for Intel and AMD graphics and most laptops. Starts a live desktop with the installer one click away.

Desktop NVIDIA

The same desktop with NVIDIA's driver, for Turing and newer cards (GTX 16, RTX 20 and after).

Server

Headless: SSH, containers, monitoring, backups and a firewall, with a console installer.

Server NVIDIA

The Server with NVIDIA's driver for GPU computing: CUDA, nvidia-smi and GPUs in containers. Same card range, Turing and newer.

Core

The minimal base for tinkerers — no installer, no updates yet.

⬇ Downloads & install guide

Every image is listed in a SHA256SUMS file signed with the PengyOS release key. Needs a 64-bit UEFI PC with Secure Boot turned off. Each image carries its own software bill of materials in /etc/pengyos/; a signed build attestation is planned.

# Documentation

Guides and recipes, tested on the current release. All docs →

📖
PUBLIC

Source repository and design documents

The repository is open: github.com/patw/pengyos, MIT licensed. It carries the README (why PengyOS exists), SPEC.md (every component choice and the alternative it beat), the use cases, the changelog, and the build tree the images come from.

# Steal this

The time for vibe-coded Linux distributions is here. One person and an agent that can work unattended for hours is enough to get an operating system out the door, and we'd rather that happened than not.

So if PengyOS isn't the distro you want, don't argue with it — copy it. SPEC.md is the whole design in one file: every component, why it was chosen, and what it beat. Start there, write your own principles, point an agent at the work, and keep one check it isn't allowed to edit. It's a big project. It's doable, and someone has to build the system you actually want.

github.com/patw/pengyos →

# Updates

Live at pengyos.catbee.ca/update, with a stable channel and a testing channel for new releases first.

📡
WORKING

How updates work

Each release is announced in a feed — subscribe in any feed reader for the release notes. Installed machines read the same feed (sudo pengyos-update apply), download the new system image for their edition, and check it against PengyOS's signing key before touching anything.

The new image is written to the spare system slot and tried on the next boot. If it doesn't come up cleanly, the machine falls back to the previous one by itself. Your files, accounts, Wi-Fi and apps live on a separate partition and are never touched.

🐣
WHILE YOU WAIT

Follow the project's neighbours

PengyOS is part of the Catbee family. The other projects in the network — Pengy, BotTalk, MooFile and TheWatcher — are shipping today.