Install

Set the repository up once, then install any tool

A tool from this family is installed the way everything else on your machine is: pacman -S, apt install, dnf install. One command adds the repository, and after that upgrades arrive with the rest of your system updates.

Before you install

beta

The first releases are days old — 29 and 30 August 2026 — and the releases, the signing and the package repository pipeline were all rebuilt this week. Nothing here is settled yet, so read these three before running the commands below.

tui-tools changed meaning today. It used to be the metapackage that installed everything; it is now the launcher, and it carries an epoch (1:0.1.0) so that apt, dnf and pacman offer it over the older metapackage of the same name. An upgrade on a machine that already had it will replace the metapackage with the launcher.
tui-tools-all is the new install-everything package. If what you wanted was the whole family in one command, that is the name to ask for now.
The repository signing key may be rotated once more before 1.0. install.sh re-imports the current key each time it runs, so re-running it is the supported way through a rotation; a setup done by hand has to import the new key by hand.

Until the family is declared stable, package names, flags, keys and key bindings can change without a deprecation period. Pin the versions you depend on, and report what breaks.

Most tools are still beta. Stable, with keys, flags and --check JSON that change only in a major release: tui-cert since 1.0.0, tui-disk since 1.0.0, tui-systemd since 1.0.0, tui-tailscale since 1.0.0. What stable means.

One command, whichever distribution

works now

Detect the package manager and add the repository

$ curl -fsSL https://pkgs.tui.tools/install.sh | sh

Read it first

A family whose whole promise is preview before you rundoes not ask you to pipe a script into a shell without looking at it. The script prints every privileged command before running it, and --dry-run prints them without running anything.

curl -fsSL https://pkgs.tui.tools/install.sh -o install.sh and read it, or take the commands by hand from the section below — they are the same ones.

Or the static binary

works now

tui-cert v1.0.1 · linux/amd64

$ curl -fsSL https://github.com/tui-tools/tui-cert/releases/download/v1.0.1/tui-cert_1.0.1_linux_amd64.tar.gz | tar -xz tui-cert
  sudo install -m0755 tui-cert /usr/local/bin/tui-cert

tui-containers v0.2.2 · linux/amd64

$ curl -fsSL https://github.com/tui-tools/tui-containers/releases/download/v0.2.2/tui-containers_0.2.2_linux_amd64.tar.gz | tar -xz tui-containers
  sudo install -m0755 tui-containers /usr/local/bin/tui-containers

tui-cron v0.2.2 · linux/amd64

$ curl -fsSL https://github.com/tui-tools/tui-cron/releases/download/v0.2.2/tui-cron_0.2.2_linux_amd64.tar.gz | tar -xz tui-cron
  sudo install -m0755 tui-cron /usr/local/bin/tui-cron

tui-dc v0.2.2 · linux/amd64

$ curl -fsSL https://github.com/tui-tools/tui-dc/releases/download/v0.2.2/tui-dc_0.2.2_linux_amd64.tar.gz | tar -xz tui-dc
  sudo install -m0755 tui-dc /usr/local/bin/tui-dc

tui-disk v1.0.0 · linux/amd64

$ curl -fsSL https://github.com/tui-tools/tui-disk/releases/download/v1.0.0/tui-disk_1.0.0_linux_amd64.tar.gz | tar -xz tui-disk
  sudo install -m0755 tui-disk /usr/local/bin/tui-disk

tui-firewall v0.6.2 · linux/amd64

$ curl -fsSL https://github.com/tui-tools/tui-firewall/releases/download/v0.6.2/tui-firewall_0.6.2_linux_amd64.tar.gz | tar -xz tui-firewall
  sudo install -m0755 tui-firewall /usr/local/bin/tui-firewall

tui-logs v0.2.2 · linux/amd64

$ curl -fsSL https://github.com/tui-tools/tui-logs/releases/download/v0.2.2/tui-logs_0.2.2_linux_amd64.tar.gz | tar -xz tui-logs
  sudo install -m0755 tui-logs /usr/local/bin/tui-logs

tui-network v0.3.2 · linux/amd64

$ curl -fsSL https://github.com/tui-tools/tui-network/releases/download/v0.3.2/tui-network_0.3.2_linux_amd64.tar.gz | tar -xz tui-network
  sudo install -m0755 tui-network /usr/local/bin/tui-network

tui-router v0.4.0 · linux/amd64

$ curl -fsSL https://github.com/tui-tools/tui-router/releases/download/v0.4.0/tui-router_0.4.0_linux_amd64.tar.gz | tar -xz tui-router
  sudo install -m0755 tui-router /usr/local/bin/tui-router

tui-samba v0.2.2 · linux/amd64

$ curl -fsSL https://github.com/tui-tools/tui-samba/releases/download/v0.2.2/tui-samba_0.2.2_linux_amd64.tar.gz | tar -xz tui-samba
  sudo install -m0755 tui-samba /usr/local/bin/tui-samba

tui-secure v0.2.3 · linux/amd64

$ curl -fsSL https://github.com/tui-tools/tui-secure/releases/download/v0.2.3/tui-secure_0.2.3_linux_amd64.tar.gz | tar -xz tui-secure
  sudo install -m0755 tui-secure /usr/local/bin/tui-secure

tui-snapper v0.2.2 · linux/amd64

$ curl -fsSL https://github.com/tui-tools/tui-snapper/releases/download/v0.2.2/tui-snapper_0.2.2_linux_amd64.tar.gz | tar -xz tui-snapper
  sudo install -m0755 tui-snapper /usr/local/bin/tui-snapper

tui-ssh v0.2.2 · linux/amd64

$ curl -fsSL https://github.com/tui-tools/tui-ssh/releases/download/v0.2.2/tui-ssh_0.2.2_linux_amd64.tar.gz | tar -xz tui-ssh
  sudo install -m0755 tui-ssh /usr/local/bin/tui-ssh

tui-systemd v1.0.0 · linux/amd64

$ curl -fsSL https://github.com/tui-tools/tui-systemd/releases/download/v1.0.0/tui-systemd_1.0.0_linux_amd64.tar.gz | tar -xz tui-systemd
  sudo install -m0755 tui-systemd /usr/local/bin/tui-systemd

tui-tailscale v1.1.0 · linux/amd64

$ curl -fsSL https://github.com/tui-tools/tui-tailscale/releases/download/v1.1.0/tui-tailscale_1.1.0_linux_amd64.tar.gz | tar -xz tui-tailscale
  sudo install -m0755 tui-tailscale /usr/local/bin/tui-tailscale

tui-tools v0.3.2 · linux/amd64

$ curl -fsSL https://github.com/tui-tools/tui-tools/releases/download/v0.3.2/tui-tools_0.3.2_linux_amd64.tar.gz | tar -xz tui-tools
  sudo install -m0755 tui-tools /usr/local/bin/tui-tools

tui-traffic v0.1.2 · linux/amd64

$ curl -fsSL https://github.com/tui-tools/tui-traffic/releases/download/v0.1.2/tui-traffic_0.1.2_linux_amd64.tar.gz | tar -xz tui-traffic
  sudo install -m0755 tui-traffic /usr/local/bin/tui-traffic

tui-update v0.3.1 · linux/amd64

$ curl -fsSL https://github.com/tui-tools/tui-update/releases/download/v0.3.1/tui-update_0.3.1_linux_amd64.tar.gz | tar -xz tui-update
  sudo install -m0755 tui-update /usr/local/bin/tui-update

tui-users v0.2.2 · linux/amd64

$ curl -fsSL https://github.com/tui-tools/tui-users/releases/download/v0.2.2/tui-users_0.2.2_linux_amd64.tar.gz | tar -xz tui-users
  sudo install -m0755 tui-users /usr/local/bin/tui-users

tui-wireguard v0.5.2 · linux/amd64

$ curl -fsSL https://github.com/tui-tools/tui-wireguard/releases/download/v0.5.2/tui-wireguard_0.5.2_linux_amd64.tar.gz | tar -xz tui-wireguard
  sudo install -m0755 tui-wireguard /usr/local/bin/tui-wireguard

Other architectures

Every release ships linux/amd64 and linux/arm64. Each tool's page lists both, with the file sizes and the SHA-256 sums taken from the release's own checksums.txt.

No installer script runs on your machine, and the tools never check for updates: you upgrade by downloading a newer binary.

The setup, by hand

works now

What the one-liner does, spelled out. Three or four commands per distribution: import the signing key, point the package manager at the repository, refresh.

Arch Linux

Add the repository and its signing key

$ curl -fsSL -o /tmp/tui-tools.asc https://pkgs.tui.tools/pubkey.asc
  sudo pacman-key --add /tmp/tui-tools.asc
  sudo pacman-key --lsign-key \
    "$(gpg --show-keys --with-colons /tmp/tui-tools.asc | awk -F: '/^fpr:/{print $10; exit}')"
  printf '[tui-tools]\nServer = https://pkgs.tui.tools/arch/$arch\n' \
    | sudo tee -a /etc/pacman.conf
  sudo pacman -Sy

Then install any tool

$ sudo pacman -S tui-cert

One setup per machine. After it, every tool in the family is a pacman away, and upgrades come with the rest of your system updates.

Arch Linux (AUR)coming soon

Then install any toolcoming soon

$ paru -S tui-cert-bin

The AUR needs no setup beyond a helper such as paru or yay. No PKGBUILD is published yet; the signed repository above is the supported route on Arch.

Debian / Ubuntu

Add the repository and its signing key

$ sudo install -d -m 0755 /etc/apt/keyrings
  curl -fsSL https://pkgs.tui.tools/pubkey.asc \
    | sudo gpg --dearmor -o /etc/apt/keyrings/tui-tools.gpg
  echo "deb [signed-by=/etc/apt/keyrings/tui-tools.gpg] https://pkgs.tui.tools/deb stable main" \
    | sudo tee /etc/apt/sources.list.d/tui-tools.list
  sudo apt update

Then install any tool

$ sudo apt install tui-cert

One setup per machine. After it, every tool in the family is a apt away, and upgrades come with the rest of your system updates.

Fedora / RHEL

Add the repository and its signing key

$ sudo rpm --import https://pkgs.tui.tools/pubkey.asc
  sudo curl -fsSL -o /etc/yum.repos.d/tui-tools.repo https://pkgs.tui.tools/rpm/tui-tools.repo
  sudo dnf makecache

Then install any tool

$ sudo dnf install tui-cert

One setup per machine. After it, every tool in the family is a dnf away, and upgrades come with the rest of your system updates.

openSUSEcoming soon

Then install any toolcoming soon

$ sudo zypper install tui-cert

The rpm repository is the same one dnf uses, and it would very likely serve zypper unchanged. Nothing has verified that, so it is not claimed here.

Which releases we support

A tool is packaged and tested for a moving window of distributions, not forever. Knowing that window before you install is the difference between a machine that keeps getting upgrades and one that quietly falls off the edge of what the family keeps working.

Numbered releases

The two most recent stable releases of each, newest first. The older one is dropped when a third release ships and it falls out of the window.

Distribution	Supported	Previous
Ubuntu	`26.04 LTS`	`24.04 LTS`
Fedora	`43`	`42`
Debian	`13 (trixie)`	`12 (bookworm)`

Rolling releases

No release number to pin, so the commitment is the current state of the distribution on the day you install.

Omarchy Server — Rolling; the family tracks the current state of the distribution.

For a distribution that ships numbered releases, the family supports the two most recent stable releases and drops support for a release when it falls out of that window. A rolling distribution has no previous release to name, so support there means the current state of the distribution on the day you install. Older releases are not blocked and often work; they are simply outside what the family tests and commits to.

This is the promise: which releases the family keeps working on. It is not a claim that every tool has been run on every one of them. The proof of an actual test run is per tool — each tool's page lists the exact backend versions it passed against, taken from its own release.

Verify a download

Check an archive against the release's checksums.txt

$ curl -fsSLO https://github.com/tui-tools/tui-cert/releases/latest/download/checksums.txt
  sha256sum -c checksums.txt --ignore-missing

--ignore-missing checks only the files you actually downloaded. The command prints OK per file, and exits non-zero if anything does not match.

Signatures

The tarballs on a GitHub release are not signed; checksums.txt tells you one arrived intact, which is not the same as proving who built it.

The packages are. Every .deb, .rpm and .pkg.tar.zst in the repository is signed by one key, and so is each repository's index — the apt Release, the dnf repomd.xml, the pacman database. Your package manager checks all of it before installing, which is the real reason to prefer this route over a tarball. The key is at https://pkgs.tui.tools/pubkey.asc, and the security page has the rest.