What RainServer can see, and what it never will.
A server tool that runs as root has to be boring and predictable about security. This page is the model we are building to. It describes design commitments for a product that is not released yet.
What it can read
- System metrics: CPU, memory, disk, network, processes
- Service state and the systemd journal
- Package manager state (what is installed, what is pending)
- Docker state through the local socket, if Docker is installed
- Firewall, SSH and fail2ban configuration (read)
- Backup job results you point it at
What it never collects
- SSH private keys
- Passwords or password hashes
- Environment variables and application secrets
- Database contents
- Files in /home
- Anything the check does not need
The rules
No silent destructive actions
Anything that deletes, stops or changes something is shown to you first: the exact target, what will change, the risk, and whether it can be undone.
No arbitrary remote shell
The dashboard can request a fixed list of typed, versioned actions. Each one is checked against your policy and verified afterwards.
Everything is recorded
Every action keeps who asked for it, which policy allowed it, the target, the parameters and the result. The history cannot be edited from the dashboard.
Root, honestly
Some jobs need root. We will not pretend otherwise. We keep the always-running part minimal and make every elevated action visible, limited and logged.
Data handling
| Transport | TLS 1.2 or newer, certificates validated, no plain-text fallback. |
|---|---|
| Agent identity | Each server gets its own credential. You can revoke one server without touching the others. |
| Accounts | Short-lived access tokens with rotation. Two-factor login for the web dashboard is planned. |
| Storage | Cloud data encrypted at rest. Every query is scoped to your account and checked on the server side. |
| Logs | Tokens, and where it makes sense paths and user names, are redacted before anything leaves the server. |
| Updates | Signed releases and signed update metadata. The updater can roll back. |
| Payments | Stripe handles card data. We store a reference to your subscription, never card numbers. |
Security questions
Is RainServer an antivirus?
No. The security module checks configuration and posture: SSH, firewall, updates, open ports, permissions. It is not a malware scanner, an intrusion detection system or a replacement for a security team.
Do you have SOC 2 or ISO 27001?
No. We are a small team and we will not claim certifications we do not have. What we can do is publish how the product works and keep it inspectable.
Can the web dashboard run commands on my server?
Only actions from a fixed list, each with typed parameters, a preview and a policy check. There is no text box that sends shell commands to your server.
Report a security issue
Found something? Email security@raincleaner.eu. A person reads every report. Please give us a reasonable time to fix it before you publish.
Machine-readable contact: /.well-known/security.txt. Early access terms · Privacy · Terms
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.