One-command connect
The whyconnect container opens a single encrypted outbound link.
Cloud Servers & VMsGA
Connect physical and virtual Linux servers to the whycloud console with one Docker command and run them like a cloud provider — no inbound ports, no data leaving your network.
| Server | CPU | Status |
|---|---|---|
| tehran-db-01 | 24% | Online |
| tehran-app-02 | 64% | Online |
| tabriz-edge-01 | 12% | Online |
| shiraz-backup-01 | — | Approve |
HOW IT WORKS
The console generates a docker run command with a one-time token; run it on any Linux server.
The server fingerprint appears in the console and an admin approves it.
Enable Shell, Logs, Install and Updates individually.
Monitoring, upgrades, security scans and a web terminal from one console.
Capabilities
The whyconnect container opens a single encrypted outbound link.
Shell access behind its own permission, audited and revocable.
CPU, memory, disk and network with a 30-minute trend.
Package upgrades only inside maintenance windows.
Isolated Trivy on the same host with severity reports.
Every operation with time, duration, status and user.
USE CASES
Dozens of physical and virtual servers across sites, one console and one audit trail.
Servers from several providers, managed the same way.
No separate monitoring stack or access tooling to maintain.
No inbound ports; every shell session is logged and revocable.
| whycloud | Scattered tools | |
|---|---|---|
| Adding a server | One command, under 5 minutes | Install several tools |
| Shell access | Web, permissioned, audited | Open SSH, scattered keys |
| Monitoring | Built in, no extra stack | Manual Prometheus/Grafana |
| Package upgrades | Maintenance window + approval | Scripts and cron |
| Inbound ports | 0 | 22 plus monitoring ports |
ON-PREMISE FIRST
No migration and no lock-in; whycloud brings the management layer to the infrastructure you already own.
OPERATIONS
Updates, security scans and monitoring from one console with a live operations queue.
FAQ
No. Servers stay where they are; only the lightweight agent runs on them.
Linux distributions with Docker; Ubuntu and Debian have the deepest coverage.
No. The connection is outbound-only over HTTPS.
With a per-agent permission that admins can revoke at any moment.
The agent is a small Go binary that typically uses a few tens of megabytes of memory.
The server keeps running; once connectivity returns the agent reconnects and status catches up.
Yes. Each agent identity can be revoked on its own and open shell sessions are closed.
Create an account and connect your first server in under five minutes.