A dedicated backup server is the right way to keep copies on separate hardware, and a strangely expensive one to leave humming in the corner for a job that runs twenty minutes a night. Joulenap lets that machine sleep: at the scheduled hour it sends a Wake-on-LAN packet to your Proxmox Backup Server, waits until the API answers, runs the backup, applies retention, runs garbage collection and verification if you asked for them, then powers the box back down or suspends it for network cards that only wake from sleep. You describe your setup as routes: which hosts back up to which backup server, on what schedule, keeping how many copies, with guests as everything on a host or an explicit list. Fan several hosts into one server nightly, or copy one backup server to another across town for an off-site second copy with its own retention. A second route kind starts nothing at all: your Proxmox hosts keep their own schedules while Joulenap simply wakes the box, watches their tasks, and switches it off when they go quiet. Watch live task output, stop a run mid-flight if you must, and get results through Apprise, Telegram, ntfy, Discord or email per route. Status widgets feed Homepage, Homarr, Dashy and Glance, and a Prometheus endpoint lets Grafana alert you when a guest stops being backed up. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.