Appearance
The Zero-SSH Philosophy
Historically, managing a server meant one thing: opening Port 22 and establishing an SSH connection.
While SSH is a secure protocol in isolation, managing thousands of SSH keys across hundreds of servers and dozens of team members is an operational nightmare. It is also the primary vector for ransomware and unauthorized lateral network movement.
Why Legacy Cloud Panels are Vulnerable
Almost all competitor cloud panels operate on an Inbound SSH model.
- You give the cloud panel your server's root SSH key.
- The panel connects to your server via SSH over Port 22.
- It runs arbitrary bash scripts.
The Fatal Flaw: If the cloud panel's central database is ever compromised, the attacker immediately gains root SSH access to every single server owned by every single customer. It is a catastrophic single point of failure.
The RasnuOS Solution: Outbound Only
RasnuOS rejects the inbound model entirely. When you install the RasnuOS agent, it establishes a secure, outbound-only WebSocket and HTTP polling connection to the RasnuOS Control Plane.
- No Port 22 Required: You can (and should) completely block Port 22 on your firewall. RasnuOS does not need it.
- We Don't Have Your Keys: We physically do not possess your root passwords or SSH private keys.
- Immune to Central Breaches: Because the agent pulls commands from the control plane and verifies them cryptographically, a breach of our database does not give attackers direct access to your infrastructure. The agent will reject unauthorized, unsigned commands.
Replacing SSH for Daily Operations
If you disable SSH, how do you manage your server? RasnuOS replaces the need for SSH in 99% of daily operations:
- Deployments: Handled automatically by the agent.
- Log Reading: Streamed securely to your dashboard via the agent.
- Configuration Edits: Managed via the UI and pushed to the agent.
- Emergency Fixes: The AI AutoPilot diagnoses and heals services automatically, or you can use the built-in conversational UI to run targeted commands.