RemotePower – self-hosted fleet monitoring with built-in vulnerability scanning RemotePower, a self-hosted fleet monitoring platform with built-in vulnerability scanning, has been released. The tool combines monitoring, alerting, CMDB, documentation with RAG search, CVE scanning, patching, and remote management into a single control plane for Linux fleets, with optional AI integration. It uses push-based agents with no inbound ports and can be set up in five minutes. The all-in-one, Swiss-army-knife control plane for your Linux fleet — and your homelab. Monitoring with alerting, a CMDB, documentation with RAG search, CVE scanning, patching and remote management in one self-hosted place — with AI woven through all of it optional . Web dashboard, push-based agents, no inbound ports. Set it up in five minutes. Live demo https://demoremote.tvipper.com · Install /tyxak/remotepower/blob/main/docs/install.md · Features /tyxak/remotepower/blob/main/docs/features.md · Wiki https://github.com/tyxak/remotepower/wiki · Discussions https://github.com/tyxak/remotepower/discussions One tool instead of six. Most teams stitch together a monitor, a CMDB, a wiki, a vulnerability scanner, a patch tool and an SSH jump box. RemotePower is the Swiss-army-knife that does all of it from a single host you control — monitoring & alerting , an asset CMDB , documentation with RAG search over your own fleet, CVE scanning , patching , and remote management — and it's heavily bound to AI as an option : bring your own model local Ollama/LocalAI or a cloud provider and ask questions answered from your infrastructure, or leave it off entirely. Everything stays self-hosted. A web dashboard that manages your Linux machines and Windows, kind of without opening firewall ports on them. Each host runs a small Python agent that polls the central server every 60 seconds — outbound HTTPS only. Enrolment is a 6-digit PIN, like pairing a console controller. Deliberately small and readable : nginx + Python CGI + flat JSON files — about 60,000 lines of server Python, one HTML file, one CSS file and a handful of hand-written JS files. No external database, no Node.js, no Redis, no Kubernetes, no build step, no bundler, no framework — you can read every line. The whole /var/lib/remotepower/ directory backs up with tar . Tested on real homelabs running 5–50 devices, fine up to a few hundred — and for larger or write-heavy fleets you can switch to an optional embedded SQLite backend, or scale all the way to PostgreSQL failover + read replicas , load-balanced app nodes and relay satellites for segmented networks. That's an advanced, heavy-fleet track — most installs never touch it. See docs/scaling.md . Server — one command, HTTPS out of the box: Docker recommended . Self-signed HTTPS on first boot; the one-time admin password is printed to docker logs remotepower . docker compose up -d Or bare-metal: a single wizard installs nginx + the app + TLS + admin. You never edit an nginx file — it writes the vhost and certificate for you. git clone https://github.com/tyxak/remotepower && cd remotepower sudo bash install.sh Open the printed URL and log in. HTTPS is automatic — a self-signed CA by default agents pin it , or a real Let's Encrypt cert when you give a public domain. No cert wrangling, no nginx editing. Add a device — one line, nothing to configure: In the dashboard, Add device → Quick install command , then on the target host: wget -qO- "https://your-server/install?t=