Lime Technology announced Unraid 8 on 17 August 2026, and the headline change is not a feature. It is the floor the whole thing stands on. After roughly two decades on Slackware, Unraid is moving to Fedora, built on uCore from the Universal Blue project.
The framing matters before anything else: this is an announcement, not a release. There is no download, no build number, no ship date. The official post is blunt about it. “We’re not rushing this one, it’ll ship when it’s ready.”
What Unraid 8 actually is today
Nothing you can install. The rollout described in the announcement runs in stages, and the first one has not opened to the public yet.
- Community developers get access first, so plugins can be updated ahead of everyone else.
- A closed beta follows.
- Then an open beta on the usual Unraid release channels.
- Then release candidates.
There is a waitlist for the beta, and that is the only thing an Unraid 7 user can act on right now. The upgrade path has not been documented either: no migration guide, and no word on what happens to an existing array or a current plugin set.
Slackware out, Fedora in
Unraid has run on Slackware since the beginning. The reason given for leaving is practical: ship security patches faster and give users more control over the base system. Vulnerabilities are found faster than ever now, in ordinary packages and in the kernel itself, and a small team maintaining its own distro layer is a slow way to answer that.
uCore, the Universal Blue image Unraid 8 builds on, is an image-based Fedora variant. Tom Mortensen, who created Unraid, framed the choice around a property the OS already had:
Unraid has always been a so-called immutable OS. However you modify your server, if you go in there, you type the wrong command, you delete all the files from your root, you still could just reboot and you’re back to the virgin release. And that’s a big reason why we’ve chosen Fedora [uCore].
Tom Mortensen, creator of Unraid
What Lime Technology says the new base buys:
- A far larger standardized base than a hand-maintained Slackware install.
- Better hardware support out of the box.
- The ability to lean on the Fedora community rather than carrying everything in-house.
- Clean separation between the base OS and the Unraid layer on top.
- The option to run the very latest kernel on brand new hardware, while everyone else stays on a stable long-term kernel.
- Security-only patches that ship faster.
That kernel option matters if you have ever bought a NAS motherboard or network card that shipped before Linux support caught up. Today you wait for Unraid. Under the new model you could opt into a newer kernel yourself without dragging everyone else along.
Docker Compose, built in
Compose support is coming to Unraid natively, wired into the Community Apps template system rather than bolted on beside it. Compose templates sit next to existing apps in the same list, so there is no bouncing between a Compose view and a Docker view.
Lime Technology credits the community directly here. Compose plugins have existed for Unraid for years, and the announcement says that community work is what the official implementation is modeled on. Anyone already running one should recognize the shape of it.
Backups, plugin permissions, and one interface
Three other pieces were announced. A backup solution is being built into the product, targeting the cloud, an S3 bucket, or another Unraid server, with snapshots and full restores handled by Unraid rather than by a plugin you found and configured yourself.
Plugins get a permissions system. Before installing one, you see exactly what it is allowed to touch, and you decide. A developer SDK for plugin authors ships alongside it.
The interface is being made consistent across the ecosystem: the OS, your account, purchasing, key management, and a new Community Apps site at ca.unraid.net. The example given is saving an app from your phone and installing it later from the server.
Nothing taken away
A rewrite this size raises an obvious worry, and Lime Technology addressed it under that exact heading. The advanced capabilities stay: NIC bridging, VLANs, the networking controls power users depend on, all meant to be easier to find rather than harder to reach. The phrase used is “lower the floor, raise the ceiling.” The rule that has not changed in twenty years: don’t lose your data.
Twenty years of context
Unraid started in 2005, when Mortensen, then working in enterprise storage, was digitizing his DVD collection onto cheap white-label drives that kept dying. He wanted redundancy without rebuilding a RAID array from scratch, so he reworked the Linux MD driver into the parity-protected array Unraid still uses.
Version 5 brought the plugin system and the Dynamix interface from community developer Ronald, who has since died and is remembered in the announcement. Version 6 added Docker, virtual machines and Community Apps, built by the member known as Squid. Version 7 added full ZFS. Lime Technology calls Unraid 8 its biggest overhaul since version 6, and the company is still independent at around 30 people. The longer story is in our history of Unraid.
If you run Unraid 7 today
Do nothing. That is the honest answer, and it will stay the honest answer for a while.
Your array keeps working. Your plugins keep working. No release date, no documented migration, and the first stage of the rollout targets plugin developers rather than users. If you maintain a plugin, this is your cue to pay attention: the base system underneath you is changing distro. Everyone else: join the beta waitlist if you want early access, and otherwise carry on.
One comparison worth noting: building on a mainstream Linux distribution is what Unraid’s main competitors already do. TrueNAS and Proxmox VE both sit on Debian. Unraid was the outlier maintaining its own Slackware base, and after Unraid 8 it will not be.
The full announcement is on the official Lime Technology blog, and Mortensen and product director Eli went through the details in part two of the Uncast Show interview.