A distro with no nonsense in it.
Arch underneath for the software, KDE Plasma on top for the desktop, and a kernel tuned for the hardware you actually own. No desktop to pick, no bootloader quiz, no filesystem you have never heard of. The parts that usually cost you a weekend are done before you boot.
Scroll
The idea
A rolling release means software the week it ships, and no eighteen-month version upgrade that eats your machine. That part is genuinely better than what Ubuntu or Fedora offer, and the community has known it for years.
The cost is that a bad update, a half-finished command, or an unreviewed build script can leave you at a black screen, and the fix is written for people who already know how to chroot from a live USB. That is the whole barrier. It was never that Arch is hard.
SakuraOS keeps the model and removes the cliff.
What's in the box
Plus the parts built for SakuraOS itself, each one there so you can work, game or build without opening a terminal you didn't want to open.
Reads what you're about to run and stops the commands that break Arch systems: partial upgrades, removing the last kernel, force-removing glibc. Every check can be overridden; you just have to read the message first.
Ten short questions, each one saying what it will do rather than naming the thing it configures. It sets up the disk, the restore points, the boot menu and Secure Boot without asking you to understand any of them first, and shows you the work as it happens.
Updates handled for you, on a schedule you set, with a restore point taken first, and a plain-English list of what's actually changing.
One place for repository packages, Flatpaks and the AUR, with the source of every app stated plainly instead of buried.
Windows software runs through Wine, installed the first time you open something that needs it rather than sitting on the disk from the day you install. It is close to a gigabyte with its runtimes, so the switch in Settings turns it off again and takes the gigabyte with it. Most distributions offer only the installing half of that.
SakuraOS builds the CachyOS kernel, the scheduler work that makes an Arch desktop feel quick, and puts its own defaults on top: memory and writeback limits set for a desktop rather than a server, an I/O scheduler picked per drive, and compressed swap in RAM so a machine with 8 GB stays usable.
Try it
Every distribution says it is stable. Here is what actually happens on SakuraOS when an update goes wrong. No terminal, no live USB, no reinstall. This is the real recovery flow, not a mockup.
Terminal Assist
Not a locked-down system. You keep the key. It just won't let you turn it the wrong way without telling you what's on the other side.
The checks live inside pacman itself, so they apply whether the command came from a terminal, a script, an AUR helper or the app store. The shell layer on top is the friendly warning, not the guard.
Around fifty rules covering things known to break Arch systems. Not a filter on what you're allowed to learn, and every one of them names the exact override.
Updates
Falling months behind on a rolling release is more dangerous than updating often: one enormous transaction, unread manual steps, and known holes left open the whole time. So SakuraOS updates itself.
Everything from mainline Arch waits twenty-four hours before it reaches you. That window isn't a delay for its own sake. It's the time we use to install and restart every update on our own machines. Anything that breaks a boot gets pulled in that window instead of breaking yours.
A day is deliberately short. Hold packages back for weeks and you get the other problem: the AUR builds against current Arch, your system isn't current Arch, and everything you install from it starts failing. Twenty-four hours is long enough to catch a broken boot and short enough that the rest of Arch still fits together.
Nobody knows what libjxl is. So the list says: JPEG XL image support, needed by Dolphin, Gwenview, Firefox. An update you can actually consent to.
BTRFS took a restore point before it ran. Pick Recovery at the boot menu and you're back. It can be done by someone who has never heard of a chroot.
The AUR
The Arch User Repository is why you can install almost anything on Arch without hunting for a package. SakuraOS gets that, and it isn't hidden behind a config file or a wiki page.
It's off on a fresh install, because it's build scripts written by other users that nobody reviews, and you haven't agreed to that yet. Turning it on is one checkbox in Settings. Right there, no ceremony.
Off by default. One click away. Never hidden.
The AUR has been used to ship malware, and when it happens the packages, the files they drop and the services they install get published. SakuraOS checks what you have installed against every campaign on record, on a schedule and the moment a new one lands. Exact matches, not guesswork.
A scanner only knows about attacks somebody already reported, so it can't be the only thing standing there. Before a package builds you see what the script does, what changed since the version you last accepted, and the signals that matter: a maintainer who changed last week, a package adopted three days ago, a download that isn't coming from the project.
Between them: the scan catches what is known, and the review is how you catch what isn't yet. Anyone promising a single check that catches everything is selling you something. A build script is arbitrary code, and no tool can prove arbitrary code is safe.
Performance
SakuraOS uses the same kernel scheduling work as CachyOS, the tuning that made them the fastest Arch derivative on modern hardware. On a recent CPU you get every bit of it.
And if you don't have a recent CPU? Most distributions that chase performance quietly stop supporting you. There's one image, standard x86-64, and a first-generation i7 runs exactly the same one a Ryzen 9000 does. Nothing to work out before you download.
Fast on new hardware. Still works on old.
Hardware
| Graphics | Your card is detected during install and the right driver goes on: nvidia-open for RTX and GTX 16-series and newer, and for older GeForce cards the last driver NVIDIA ever shipped for them, which we rebuild and maintain ourselves because NVIDIA no longer will. AMD and Intel work out of the box. |
| Secure Boot | Set up during install, with keys generated on your machine. Most Arch-based distributions tell you to switch it off in firmware. That's where a lot of people quietly give up. |
| Memory | Compressed swap in RAM by default, so a laptop with 8 GB and a browser open stays usable instead of having something killed. |
| Older CPUs | Standard x86-64, so a first-generation i7 runs the same image a Ryzen 9000 does. No separate build to choose, nothing to work out before downloading. |
Privacy
Not minimised. Not anonymised. Not off by default. There is no telemetry in SakuraOS to switch off, because none was ever put in.
Your machine, your data, your business.
Plasma, the desktop SakuraOS uses, is made by KDE, and they can accept anonymous information about your hardware and which features you use, which is how they find bugs. The installer offers it, off by default, on a screen that says plainly what it is. It goes to KDE. It never comes to us.
Free and open source throughout: every package we build, the installer, and the whole build pipeline. Nothing here is locked down to keep you safe from yourself. You can read it, change it, or take it apart.
Get SakuraOS
No desktop edition, no gaming edition, no "which kernel" question. Setting it up takes about a minute.
SakuraOS is being built in the open. Nothing above is a promise about a future release except where it says.