About RackBrief
A reference for people running a server at home. Every fact here says which release it applies to, carries the date it was checked, and links to the maker so you can check it yourself.
Why this exists
Home server software ships numbered releases, and the answers change between them. A setting that worked in one version is renamed in the next; an upgrade that is routine on one processor locks you out on another. The makers do publish all of this, in release notes written for people who already know the system. Everyone else ends up in a forum thread from three years ago that was true at the time.
So this site does one job: take what the makers publish, check it, date it, stamp it with the release it belongs to, and write it in plain words.
What we do not do
- We do not test hardware or claim hands-on experience we have not had. Where a figure comes from a maker's own page, we say so and link it.
- We do not invent numbers. If a maker does not state a requirement, the table says "not stated" rather than filling the gap with a guess.
- We do not hide disagreement. When two sources give different answers, you see both and which one we think is right.
- We do not let a page go stale quietly. Each one carries the date it was last checked and the release it was checked against.
Who runs it
RackBrief is a small independent publisher in the United Kingdom. It is not owned by, paid by or affiliated with Proxmox, iXsystems, Lime Technology or any other maker named on this site. Product names appear only to identify the software.
We use software, including AI tools, to help gather, check and write up this material. Every figure is tied to a source you can open, and the editorial policy sets out the checks in full.
How the site is funded
By advertising, and in future possibly by affiliate links, which would always be labelled at the top of any page carrying them. Neither affects what the data says or which software we recommend.
Corrections
If something here is wrong, or true of one release and not the one you are on, tell us and we will fix it and re-date the page. See the contact page.