I built RemotePower because I wanted to power devices on and off across my own infrastructure without depending on a cloud service or some vendor's phone-home dashboard. Everything I run is self-hosted, and remote power was the one annoying gap I kept working around with ssh scripts and cron hacks. So I wrote a proper tool for it. It's a polling-agent setup: clients phone home to a small server, so you don't have to expose anything inbound on the machines you're managing. The backend is deliberately boring on purpose — Python CGI behind nginx, flat JSON files for storage, no database to babysit. That makes it trivial to deploy on a cheap VPS or a box in your closet and easy to reason about when something breaks. There's a Linux agent that also does package enumeration, a CVE scan against OSV.dev, and a Prometheus /metrics endpoint if you want to graph it. It's still very much a personal project that grew, so I'm sure there are rough edges, and I'd genuinely like to hear where the design choices look wrong to people who run more than I do. The repo's here: github.com/tyxak/remotepower — happy to answer anything about how it's put together.

RemotePower

RemotePower – self-hosted remote power management

RemotePower – self-hosted remote power management