Skip to main content
Open Source Project

Argo OS

A custom Gentoo distribution built for performance, stability, and sanity

Three months, 200+ hours, and one existential crisis with Qt6 later -- this is what emerged.

4,728 Binary Packages
70+ Build Cores
2 min Rollback Time
38 Chapters

What is Argo OS?

Argo OS is what happens when you get tired of waiting 6 hours for Firefox to compile. It's a custom Gentoo-based distribution designed to rival:

  • CachyOS for gaming performance
  • Fedora/Debian for security
  • openSUSE for stability and snapshot protection

The difference? Argo OS compiles everything once on a build server, then deploys binary packages everywhere. Updates take minutes instead of hours. And if something breaks? Roll back in 2 minutes via Btrfs snapshots.

Build Swarm
70+ cores compiling packages
Binary Repository
4,728 pre-built packages
Desktop
VM
Server
Pull packages, never compile

System Hardware

The daily-driver machine running Argo OS. Proof that you don't need new hardware to run a fast system.

CPU Intel i7-4790K @ 4.00GHz 4 cores, 8 threads -- released Q2 2014
GPU NVIDIA RTX 4070 Ti 12GB GDDR6X
RAM 32GB DDR3 Dual-channel, 1600MHz
Storage 1TB NVMe Btrfs with snapshots
Init System OpenRC Not systemd -- by choice
Desktop KDE Plasma 6 + Hyprland Dual WM -- stacking and tiling

Argo OS runs on a 12-year-old CPU. Performance comes from compilation optimization, not brute force hardware.

Filesystem Layout

Btrfs subvolume structure designed for independent rollbacks and snapshot efficiency.

@ / snapshotted Root filesystem
@home /home snapshotted separately User data and configs
@snapshots /.snapshots snapshot storage Snapshot storage location
@var-cache /var/cache excluded Package downloads, distfiles
@var-log /var/log excluded System logs

Why This Matters

Independent rollbacks -- Root and home can be rolled back separately. Break a system update? Roll back / without touching your documents.
No snapshot bloat -- /var/cache is excluded so package downloads (hundreds of MB per update) don't inflate every snapshot.
Logs survive rollbacks -- /var/log is excluded so you can still read what went wrong after rolling back the root filesystem.
Snapper integration -- Automatic pre/post snapshots on every emerge operation. Boot into any previous snapshot from GRUB.

Core Design Principles

01

Compile Once, Deploy Everywhere

Binary package distribution from build servers. Your workstation never touches a compiler.

02

Snapshot Protection

Btrfs with automatic snapshots before and after every package operation. Rollback in 2 minutes.

03

Performance First

Optimized compilation with CPU-specific flags. No distribution compromises for compatibility.

04

Version Controlled

All configurations tracked in Git. Rebuild the entire system from source if needed.

05

Reproducible

Anyone should be able to build identical systems. Documentation is the product.

06

Cloud-Integrated

Automated backups and distributed storage. Your configs are never truly lost.

The Journey

Three months of building, breaking, and rebuilding. Here's how Argo OS evolved.

October 2025

The VM Foundation

Built Gentoo in a VM. KDE Plasma, Firefox, the whole stack. 40 hours of compilation. Then the package database corrupted.

Lesson: ext4 has no snapshots. That was a problem.
November 2025

The Btrfs Migration

Rebuilt everything on Btrfs with Snapper. openSUSE's snapshot model, but on Gentoo. First successful rollback test: 2 minutes including reboot.

Lesson: Snapshots aren't optional. They're infrastructure.
November 2025

Binary Package Distribution

Set up a binhost server. Compile once, deploy everywhere. Updates went from 6 hours to 15 minutes. Game changer.

Lesson: Life's too short to compile Qt twice.
December 2025

The Desktop Setup

KDE Plasma 6. Hyprland for tiling. NVIDIA drivers that actually work. The dream setup that took 3 weeks of dependency resolution.

Lesson: Qt6 and KDE Plasma are codependent. Never update one without the other.
January 2026

The Build Swarm

One binhost wasn't enough. Built a distributed compilation system: 5 drones, 70+ cores, packages built in parallel across multiple machines.

Lesson: Distributed builds are addictive. Also complex.
Now

Production Ready

Daily driver for work and gaming. 4,728 packages. Self-healing build infrastructure. Faster updates than Arch.

Current focus: Documentation, golden images, and maybe -- maybe -- getting someone else to use it.

Technology Stack

Core System

Gentoo Linux Base distribution
OpenRC Init system (no systemd)
Btrfs Filesystem with snapshots
Snapper Snapshot management

Desktop

KDE Plasma 6 Primary desktop
Hyprland Wayland tiling WM
NVIDIA 550+ Proprietary drivers
PipeWire Audio stack

Infrastructure

Build Swarm Distributed compilation
SSH Binhost Package distribution
Tailscale Mesh VPN
rclone Cloud backup

Tooling

apkg Hybrid package manager
Nix Userland packages
Home Manager Dotfile management
Git Config versioning

Key Features

90% Faster Updates

Binary packages mean updates in minutes, not hours. Firefox installs in 30 seconds instead of 4 hours.

2-Minute Rollback

Automatic snapshots before every package operation. Broke something? Boot into a previous snapshot from GRUB.

Distributed Builds

70+ CPU cores across 5 machines compiling packages in parallel. Build the entire system from scratch in hours, not days.

No Compromises

Every package compiled with your exact CPU flags. No distribution-level compatibility compromises.

VM Portable

Deploy a complete system to a new VM in 15 minutes. Golden images for rapid testing and development.

Documented Obsessively

Every decision, every disaster, every solution -- documented. The journey is the product.

How It Compares

An honest comparison. The point is not that Argo OS wins every category -- it's that Gentoo's customization plus binary packages removes the traditional tradeoff between optimization and convenience.

Feature Argo OS CachyOS Arch Fedora NixOS
Package optimization Per-CPU flags CachyOS patches Generic x86_64 Generic Generic
Update time Minutes (binary) Minutes Minutes Minutes Minutes
Rollback 2 min (Btrfs) Limited No built-in No built-in Yes (generations)
Init system OpenRC systemd systemd systemd systemd
Package count 4,700+ Arch repos Arch repos 60K+ 80K+
USE flags Full control No No No Nix options
Learning curve High Medium Medium Low Very High

Every distro makes tradeoffs. Argo OS trades learning curve and initial setup time for per-CPU optimization, full USE flag control, and snapshot-based rollbacks -- without the multi-hour compile times that usually come with Gentoo.

By the Numbers

4,728
Binary Packages Available
1,682
Packages Installed
264
World Set Packages
70+
Build Cores
200+
Hours of Development
38
Documented Chapters
10
Tech Deep Dives
5
Build Drones

Explore More

Blog Series Index

The complete Argo OS documentation -- from the first VM to production infrastructure. Start with Part 1 and work through, or jump to a deep dive.

Getting Started

Argo OS is not a downloadable ISO. It's a documented approach to building your own optimized Gentoo system. The value is in the process, the decisions, and the lessons learned.

1
Read the blog series Start with Part 1: Building Argo OS to understand the design decisions and architecture.
2
Fork the configs from GitHub Portage configs, USE flags, kernel config, OpenRC service setup -- all version controlled and documented.
3
Set up a Gentoo VM with Btrfs Use the Btrfs & Snapper deep dive for the subvolume layout. Get snapshots working before anything else.
4
Configure a binhost Set up Portage binary hosting or deploy a Build Swarm for distributed compilation.
5
Deploy binary packages Point your workstation at the binhost. Updates in minutes. Never compile locally again.