TriOS is a Debian-based operating system designed for users who want a clean, smooth, and ready-to-use Linux experience. It ships with Debian’s full standard repositories and driver packages (including non-free firmware) to ensure maximum hardware compatibility.
TriOS is based on Debian 13 “Trixie”, which is expected to receive:
- Full security support until August 2028 (expected)
- Long Term Support (LTS) until August 2030 (planned)
Bookworm-based releases and later Forky-based releases are being considered.
For more details, see the official Debian release and support timeline.
I wanted a Linux distribution that was:
- Minimal – like Lubuntu, keeping the system lightweight and efficient.
- Smooth – like Linux Mint, with polish and usability right out of the box.
- Tailored to my workflow – focused on game development, gaming, and creative studio work.
I’ve yet to find a distro that offers a well-balanced system that’s easy to set up, stays out of the way, and supports both everyday use and demanding workloads.
I used to rely on Linux Mint for this, but its growing abstraction layers have made everyday use feel sluggish and unnecessarily complicated.
Most distributions either prioritize developers or everyday users, but what if you optimized for both?
That’s why I made TriOS.
- Debian-based
- KDE Plasma desktop environment (minimal configuration, ready to customize)
- Includes tools to install drivers for AMD, Intel, and NVIDIA hardware
- Smooth, polished experience right out of the box
- Stable if used correctly
Note: TriOS is currently in pre-beta. It’s functional and mostly stable in testing, but I don’t recommend using it as your primary daily driver just yet. Things are still evolving rapidly.
TriOS is built to run on a wide range of hardware, so most computers can run it without issues. However, for the best experience, especially when gaming or developing, stronger hardware is recommended.
| Component | Minimum Specification | Example Hardware |
|---|---|---|
| CPU | Dual-core 64-bit processor | Intel Core i3-6100, AMD FX-6300, or newer |
| GPU | Integrated or low-end discrete GPU capable of running KDE | Intel HD Graphics 530, AMD Radeon R5, NVIDIA GT 710 |
| RAM | 2–4 GB | 4 GB strongly recommended |
| Storage | 32 GB (SSD or HDD) | SSD highly recommended for speed and reliability |
| Display | 1366×768 or higher | Any modern 720p+ display |
| Network | Internet connection required for installation | Ethernet or supported Wi-Fi adapter |
| Component | Recommended Specification | Example Hardware |
|---|---|---|
| CPU | Quad-core or higher, modern 64-bit architecture | Intel Core i5-12400, AMD Ryzen 5 5600, or newer |
| GPU | Mid-to-high tier GPU suitable for gaming or development | NVIDIA GTX 1660 Ti / RTX 3060, AMD RX 6600 XT, Intel Arc A580 |
| RAM | 8–16 GB | 16 GB ideal for development workloads |
| Storage | 512 GB+ SSD | NVMe SSD preferred for fastest performance |
| Display | 1920×1080 (Full HD) or higher | 1080p or 1440p recommended for workstation use |
| Network | Broadband connection | Useful for updates, Steam, and package downloads |
TriOS will run smoothly on older or modest systems, but for a fluid KDE experience and creative workloads, modern midrange hardware or better is encouraged.
TriOS version names follow a simple and consistent format:
[Debian Release Number] [TriOS Codename]
For example:
13 Bepis → Planned beta release (current dev and prod branch)
13 Tenna → Planned first stable release (not in use)
Future versions will continue this naming pattern, aligning with each major Debian release and a unique TriOS codename for clarity and identity.
For TriOS development, you can see surface-level progress on the Trello board.
TriOS itself (custom scripts, configs, and branding) is licensed under the MIT License.
Please note:
- The operating system includes software packages from Debian, each under their own respective licenses.
- Proprietary drivers and firmware are included as-is under their redistribution terms, consistent with Debian’s non-free-firmware policy.
- For full license information, see
/usr/share/doc/*/copyrightwithin the installed system.
TriOS is built for amd64. Future builds may also be available for i386 (32-bit) and arm64. However, support for i386 is becoming increasingly limited upstream. TriOS hasn’t been tested on arm64 or i386 yet, but if you’re feeling brave, you can always build it yourself.
You must have a working internet connection when installing TriOS.
The full release of 13 Bepis is not available just yet. The current production ISO is a test release. There is no recommended "stable" release yet.
Please see the Secure Boot Notice section if you plan to run TriOS on physical hardware.
Important: The official TriOS Updater (once released) will not support updating from non-production builds. If you’re running a nightly or dev build, you’ll need to manually reinstall the production version to continue receiving official updates.
Before installing, always verify your ISO with the provided checksum.
Before installing TriOS, please disable Secure Boot in your system’s BIOS or UEFI settings.
TriOS includes non-free firmware and proprietary drivers that require Secure Boot to be turned off to function properly. If Secure Boot remains enabled, the installer may fail to boot, or certain drivers (especially NVIDIA and AMD GPU drivers) may not load correctly.
TriOS includes basic kernel signing support, but it may not work reliably under Secure Boot, so disabling it is strongly recommended.
To disable Secure Boot:
- Reboot your computer and enter the BIOS/UEFI setup (usually by pressing
Del,F2, orEscduring startup). - Locate the Secure Boot option under Boot, Security, or Authentication settings.
- Set Secure Boot to Disabled.
- Save changes and reboot.
After installation, leave it disabled if possible.
I spent way too much time getting this automatic build system to work for your convenience.
But hey, if you want to take the hard road and rebuild it yourself just because you can, who am I to stop you? Go ahead. I won’t judge (much).
The Docker container lives in the builder/ directory. It’s a standard container setup.
The build-trios.sh script only works if you’re running it as root and the repo is cloned to the root user’s home directory.
(This requirement is due to Debian Live Build permissions; running under a non-root user with sudo may work if configured correctly.)
If you want additional customization, bind volumes to the TriOS and TriOS_Output directories.
TriOS should be a copy of the repo, and TriOS_Output should be an empty folder.
If you’re developing for TriOS, I recommend using a separate copy of the repo rather than your working one. Pull requests containing generated build artifacts or temporary configurations will be rejected.
When compiling, the branch you use depends on your purpose:
- If you want to test the latest changes or peek in on developer status, use the dev branch. (Or you could, y'know, use the already compiled build.)
- If you don't trust me and just want the production system but built by yourself, use the prod branch.
- If you want to run TriOS with your own modifications, use your own directory, whatever that may be.
Boot the ISO in a VM or from a USB stick to verify functionality before distributing it. But seriously, please test your builds before telling other people they’re safe to use.