A few days ago so decided to try it out. I installed to a harddrive as I haven’t always got consistent results using VM’s.
I usually manually partition drives EFI, Root and Home for installation but couldn’t make that happen when trying to install Kiro whether creating the partitions within the installer or before hand. Got a "Boost.Python error in job “bootloader” error at the end of installation both times.
I was able to install using the “Erase disk” option in Calamares with no issues which installs an EFI partition and another for both Root and Home. I didn’t try the “install along side” option.
There are multiple DE’s to choose from, I’m using KDE Plasma. I have installed dozens of the programs/software I use on EOS with no issues. So far, so good.
Kiro has it’s own repo (Nemesis) along with Core, Extra, Multilib and Chaotic-Aur installed. Seems very responsive and fast but that might be because I haven’t “bloated” it fully up yet ![]()
From the website here’s a few of statements about Kiro…
Questions, before you commit
Short answers to the things people ask before downloading.
Why Kiro instead of vanilla Arch?
Same Arch underneath, less assembly. Calamares replaces the wiki transcription, the repos save you from rebuilding common packages, and the defaults are opinionated so you can boot into a usable desktop in under an hour.
Who's behind Kiro, and who is it for?
Kiro is built by Erik Dubois — the creator of ArcoLinux, who has spent years building teaching-first, community-focused Arch distributions and documenting every step on YouTube — working with Claude AI (Anthropic) as his dev partner. It’s a one-developer-plus-AI project. For the past year Kiro has been his personal build: the exact system he runs every day, shared openly. From June 1, 2026 the focus shifts — the same opinionated foundation, now shaped for the people who use it (driven by what users actually need, not what the creator happens to like). Code lives on GitHub and the walkthroughs on YouTube — the everyday tutorials stay free forever, while the more advanced, deep-dive courses live in the members-only realm. See Community.
How is Kiro different from CachyOS, Garuda, EndeavourOS, or other Arch-based systems?
They’re all Arch-based, just with different priorities. CachyOS is performance-first — a custom scheduler and its own optimized repos. Garuda leans gaming, with heavy GUI theming. EndeavourOS stays deliberately close to upstream Arch with a light touch. Kiro ships comparable performance and hardening tuning — linux-cachyos by default with linux-zen alongside, sane defaults — while keeping the userland close to upstream Arch. It adds chaotic-aur for pre-built AUR binaries, its own nemesis_repo, the ArchLinux Tweak Tool, and AI-assisted development. Less gaming and ricing, more a curated, learnable Arch you can daily-drive.
Kiro ships ATT, which installs any of 13 desktops on demand:
- 7 tilers
Awesome · Bspwm · Chadwm · I3 · Leftwm · Ohmychadwm · Qtile - 6 full DEs
Budgie · Cinnamon · Gnome · Mate · Plasma · Xfce
Pick what fits, or install several and switch from your login screen.