Start in cloud.larvps.com, connect your VPS, then manage sites, DNS, SSL, and backups without turning the product into a maze.
$ Open cloud.larvps.com and click Add Server
▸ Register the VPS and generate the secure token
▸ Optional: run larvps system:preflight --short
$ bash /tmp/install.sh --token=*** --api=***
▸ Installing LarVPS agent...
▸ Starting systemd service...
✔ Server connected. Now continue in the Dashboard.
You've been there. We've been there. It's time to move on.
"Docker eats 500 MB RAM just to run a tiny WordPress site. My $5 VPS is already gasping for air."
"My bill exploded because simple app hosting turned into layers of overhead I never asked for."
"I just want the server connected and the sites handled cleanly without living in terminal commands all day."
One binary. One dashboard. One readable path.
Written in Go. Lightweight agent, low memory use, and a fast path from a clean VPS to a connected dashboard.
Users start in the dashboard, connect a server, wait for the heartbeat, then move into sites, DNS, SSL, and backups in the right order.
Ubuntu 22.04 and 24.04 are checked up front. Preflight can warn about RAM, disk, APT locks, DNS, outbound HTTPS, and UFW before install proceeds.
LarVPS should assist, verify, and guide. The user still owns the server, DNS, provider account, and production decisions. That is why the preferred path starts in the dashboard, while CLI remains a supporting step rather than the main experience.
Start free. Scale when you are ready. Cancel anytime.
For side projects
For professionals
For teams & agencies
Ubuntu 22.04 and 24.04 are the supported targets right now. The dashboard-led install flow can optionally run preflight first, then verifies again during install.
No. The intended user journey starts in cloud.larvps.com. CLI is only used as the install step the dashboard prepares for that VPS.
Yes. Use larvps system:preflight --short or --json if you want a clean machine-readable report.
No. The agent handles infrastructure and runtime actions. Operators still own source code, DNS, provider accounts, and production choices.
Start in the dashboard. Let it guide the server. Then move into sites.
$ Open cloud.larvps.com → Add Server → Copy install command
Open Dashboard