A list of organizations and projects that use TunaOS in production, development, or evaluation.
If you or your organization is using TunaOS, we'd love to add you to this list! See the adoption call to self-identify in the public Show-and-tell Discussion, or submit a PR with the same consent details.
Evidence baseline (2026-08-14): 0 named production users and 2 named development/evaluation entries. The ecosystem table below records projects that TunaOS depends on, integrates with, or is inspired by; it is not evidence that those projects use TunaOS.
(None listed yet — see the adoption call and be the first!)
Both current entries are the project itself — the maintainer, and TunaOS's own CI. They are honest as dogfooding records and are not external adoption evidence; the adopters KPI in ADOPTION-METRICS.md counts external entries only, so these do not move it.
| Organization | Use Case | Variant(s) | Since |
|---|---|---|---|
| @hanthor (Project Maintainer) | Personal daily driver — development, testing, and dogfooding all variants | Yellowfin GNOME, Albacore GNOME, Skipjack KDE | 2026-04 |
| TunaOS Hive Agents | Automated CI/CD — build, test, and release pipeline runs on TunaOS infrastructure | Yellowfin GNOME, Albacore GNOME | 2026-05 |
These are not adopters. Every entry below is a project TunaOS builds on or consumes — base operating systems, desktop environments it packages, build services, registries. None of them are downstream of TunaOS, and none have a partnership with it; being listed here says only that TunaOS uses their work.
The section was previously headed "Ecosystem & Downstream Projects", which in a file that opens "organizations and projects that use TunaOS" reads as 24 adopters. That matters because this file is cited as adoption evidence in the DistroWatch (#1333) and CNCF (#1340) pitches — a reader checking it would find Debian, Fedora, KDE and elementary OS apparently listed as TunaOS adopters, and none of them have said any such thing.
Kept because the dependency map is genuinely useful; relabelled so it cannot be read as, or counted as, adoption.
| Project | What TunaOS uses it for | Link |
|---|---|---|
| Universal Blue | Upstream inspiration — TunaOS is a fork of Bluefin LTS | github.com/ublue-os |
| Bluefin | Direct upstream — bootc-based desktop foundation | github.com/ublue-os/bluefin-lts |
| AlmaLinux OS | Base OS — Albacore, Yellowfin variants built on AlmaLinux 10 / Kitten | almalinux.org |
| Fedora Project | Base OS — Bonito variant built on Fedora | fedoraproject.org |
| CentOS Stream | Base OS — Skipjack variant built on CentOS Stream 10 | centos.org |
| Homebrew | Package manager — baked into all images | brew.sh |
| Flathub | App distribution — pre-enabled in all images | flathub.org |
| BuildStream | Build tool — used by Tromsø (KDE) and XFCE Linux variants | buildstream.build |
| bootc-dev/bootc | Upstream bootc project — bootable container technology foundation (CNCF Sandbox) | github.com/bootc-dev/bootc |
| System76 / COSMIC | Desktop environment — COSMIC variant of TunaOS | github.com/pop-os/cosmic-epoch |
| KDE Community | Desktop environment — Tromsø variant built on KDE Plasma 6 | kde.org |
| XFCE Community | Desktop environment — XFCE Linux variant built on XFCE 4.20 | xfce.org |
| Project Bluefin (Dakota) | Reference implementation — Tromsø and XFCE Linux modeled on Dakota's BuildStream approach | github.com/projectbluefin/dakota |
| Debian | Base OS — Flounder / Flounder Sid variants built on Debian | debian.org |
| Gentoo | Base OS — Guppy variant built on Gentoo | gentoo.org |
| Arch Linux | Base OS — Marlin variant built on Arch Linux | archlinux.org |
| Ubuntu | Base OS — Ubuntu variant image | ubuntu.com |
| Niri | Desktop environment — scrollable-tiling Wayland compositor (Bonito variant) | github.com/YaLTeR/niri |
| elementary OS | Desktop environment — Pantheon desktop for the Gurnard (Ubuntu 24.04 LTS) variant | elementary.io |
| Fedora COPR | Package distribution (legacy/compatibility) — GNOME 49/50 backports for CentOS Stream 10 / Fedora bases; being retired in favor of the native RPM + Cloudflare R2 pipeline below | copr.fedorainfracloud.org |
| Cloudflare R2 | Package/artifact distribution — native EL10 RPM repository (GNOME 51 onward), ISOs, and boot screenshots | cloudflare.com/r2 |
| Tideforge | Build service — COSMIC packages built from source for the EL10 desktop cells | tideforge.org |
| GHCR | Image registry — all published TunaOS image flavors | github.com/orgs/tuna-os/packages |
| Asahi Linux | Hardware enablement — bootc-installer-asahi's payload layout is modeled on fedora-asahi/nixos-asahi conventions; targets M1/M2 Macs via Asahi's kernel/firmware work | github.com/AsahiLinux |
The fastest way to get added: open an issue using the adoption-request form — tell us your tier, variants, and use case, and we'll open the ADOPTERS.md entry for you.
Prefer to do it yourself? You can also open a PR directly:
- Add your entry to the Production Users or Development & Evaluation table
- Include the variant(s) you use and a brief description of your use case
- (Optional) Add any relevant links (blog posts, case studies, conference talks)
Questions? Reach out on Matrix or open a discussion.
Maintained by the TunaOS community. Last updated: 2026-08-11.