omarchy-pool
v0.0.185
Sign in

For Omarchy users

Arch, Arch Linux ARM, Omarchy and Asahi packages, tested before they reach you

One host. Every package is verified against its project's key, stored once, and promoted through three rings on evidence — a real pacman, an ABI check, two green health checks — never on a promise.

Get started No account, no sign-up. Just your Omarchy.

From upstream to your machine

The full story, stage by stage →

Same packages, three levels of proof — and the lab beside them, where the factory's builds are installed by a real pacman before anyone decides. A ring that fails a health check rolls back on its own.

Arch Linuxcore · extra · multilibArch Linux ARMcore · extra · alarmOmarchythe OPR's edge channelAsahithe fork · asahi-alarmFactorybuilt here, by the poolPoolsignature-verifiedstored once on R2≤ 3 hedgefollows upstreamfor CI and developersreal pacman+ ABI + securityon both archesrcboth architecturesfor testerstwo green checksin a row · ≈ 6 hstablewhat you runrecommendedrolls back by itselfif a health check failslabtried, never promisedapprovedthe factory's builds, installed by a real pacman before anyone decides
Packages keep the signature of the project that built them; the only key you add signs the databases and what the factory builds.

Each ring is a complete, signed set of pacman databases over the same packages. The lab is the fourth: nothing there is promised or promoted.

Why the pool

Open source, in the open: every decision, build and rollback is on the record.

Verified, then signed

Every upstream package checked against its project's own key before it is stored.

Tested before you

A real pacman sync and an ABI check on x86_64 and aarch64, then two green health checks in rc.

Rolls back by itself

A promotion that fails its health check is undone before your next pacman -Syu.

Made by the community

Packages nobody ships come from contributors' recipes, rebuilt and approved by maintainers. Open source, on GitHub.

Bring a package →

One command, once per machine. What it does, how to switch rings, how to undo it →

Point pacman at a ring x86_64 · aarch64

copy

Then omarchy update — off Omarchy, sudo pacman -Syu. Read the script first →

Pool growth 7 days

bytes stored once, from the metrics snapshots

Security in stable now

open advisories matched against what stable serves

machines on the pool14 days

distinct addresses that fetched a ring database, once a day · no accounts, no cookies
Loading
the people, from what the pool recorded…

Share of what each upstream serves that edge already pins, on both architectures. The optional sources and the factory are not counted.

Made in the open

The pool is a project, not a service you rent. Everything it does is on the record.

The last things the pipeline didlive · every minute
loading…

Full journal →

The ringshead · last releases
loading…

Ring history, every release →