Docs

How RainServer is meant to work.

There is no build to document yet, so this page covers the rules the first release is built around. It grows with the product.

Supported systems

Planned · v1.0

Ubuntu and Debian are the first targets because we can test them properly. Rocky Linux and AlmaLinux will be listed once they have been validated — not before. x86_64 first, ARM64 after.

Install

Planned · v1.0

There is no installer yet. When there is, it will follow these rules:

Served over HTTPS with a published checksum and signature
Detects the distro and architecture and tells you what it is going to install before it does it
No hidden commands; the script is readable
One documented uninstall command that removes everything it added
Packages for apt and dnf where that is practical

Risk levels

Every finding and every action has one of these. The level decides how much RainServer asks before it runs anything.

SAFE	One confirmation for the group. The item list is one key away.
REVIEW	You open the category and confirm it on its own.
DANGER	Never automatic. Shows the impact; critical ones need the name typed.
MANUAL ONLY	RainServer will not run it. It explains the finding and leaves it to you.

Keyboard

The terminal app is keyboard first. Arrows or Tab to move, Enter to open. The footer always shows the keys that work on the current screen.

`S`	Scan
`R`	Review findings
`C`	Clean SAFE items
`F`	Fix selected
`U`	Security
`L`	Logs
`B`	Backups
`H`	Help
`Q`	Back / quit

Checks you can run today

RainServer is not magic. Most of its checks start from commands you already know — it runs them, reads the output together, and explains the result. Here are a few of them. They only read; none of them change anything.

Disk and inode use

df -h / /var && df -i /

How much space the systemd journal takes

journalctl --disk-usage

Space used by images, containers, volumes and build cache

docker system df

Units that are currently failed

systemctl --failed

What is listening, on which port, and which process owns it

ss -tulpn

The SSH settings that are actually in effect

sshd -T | grep -Ei '^(permitrootlogin|passwordauthentication)'

The first ten minutes

Planned

0–1 minCreate an account and start the 7-day trial.
1–2 minCopy the install command for your server.
2–3 minThe installer checks the system and shows what it will add.
3–5 minFirst scan: system, disk, services, security, Docker, backups.
5–6 minYou see the top three things worth your attention, not a hundred warnings.
6–8 minOpen Cleanup or Fix My Server and read the explanation and preview.
8–10 minConnect email or Telegram alerts and open the web dashboard.

Early access

Want to try it on a real server?

We are looking for a small group of people who run their own Linux servers to try the first builds and tell us what is wrong with them. Tell us how many servers you run and which distro. That is all we need.

Ubuntu and Debian first
Free while you are testing
Your feedback shapes v1.0

No newsletter. We write when there is a build you can install.