A few days ago I posted VPS Pilot here, a self-hosted tool I’m building to monitor and manage my own VPSes. Thanks for the feedback last time. v0.5.0 is out now, and it handles backups too. Quick recap: a small Rust agent runs on each server and dials out to a hub over TLS, so no inbound ports are opened on the VPS. The hub is a single binary with SQLite and a built-in dashboard. Each project on a server has a config.vpspilot.json that declares what the agent is allowed to do with it. New in v0.5.0: the agent zips a project’s folders, env file and database dump (MySQL, Postgres or SQLite) on a schedule, or when you hit “Back up now”. It can upload each zip to S3-compatible storage (AWS, Linode, MinIO) and cleans up old ones after a retention period. What it already did: live CPU, memory and network charts, alerts to Discord, Slack and email, and running deploy commands from the project config, with history. How I’m building it: I plan and design everything and review every change, and AI coding agents write the code. I ship one theme per release. Next up is scheduled cron jobs, then Docker Compose support. It’s open source (AGPL-3.0), Linux only and pre-1.0. One question for you: if you run a VPS for your side projects, how do you back it up today? I’m trying to decide whether restore should become a one-click dashboard feature or stay a documented manual step. GitHub: https://github.com/sanda0/vps_pilot Docs: https://vpspilot.dev   submitted by   /u/sanda15 [link]   [comments]