A self-hosted scheduler that keeps your Proxmox Backup Server powered off — and wakes it only when it's time to back up.
Open-source · AGPL-3.0 · runs on ~512 MB RAM
This is the real UI — open the live demo →
The container creates its own config on first boot — you finish setup in the browser.
# pull & run — Docker grabs the image from Docker Hub docker run -d --name joulenap \ --restart unless-stopped \ --network host \ -e TZ=Etc/UTC \ -v /opt/joulenap/data:/app/data \ catubba/joulenap:latest # → open http://<your-ip>:8080 and run the setup wizard
Joulenap owns its own schedule and drives the whole cycle over the Proxmox APIs — nothing on your PVE host is modified.
Sends a Wake-on-LAN packet to the sleeping PBS.
Polls until the PBS is reachable, with retries.
Runs vzdump for the guests you picked, to PBS.
Applies retention and garbage-collects the datastore.
SSHes a clean shutdown once the run succeeds.
Pings you on success or failure — your channel.
Pick the time, enable or disable, and see the next and last run at a glance.
Wakes the PBS itself, waits for it to be ready, and retries on a timeout.
Toggle which CTs and VMs to back up — all, or include/exclude lists, resolved live at backup time.
Keep last/daily/weekly/monthly/yearly, garbage collection, and optional verify — while awake.
Telegram, ntfy, email, Discord and 100+ more via Apprise — on success or failure.
Watch real vzdump/GC output stream, run a backup any time — or stop a stuck job, cancelled on the Proxmox side too.
Every run broken down into steps — wake, backup, GC, verify — with durations, outcomes and logs.
Status on Homepage, Homarr, Dashy or Glance via a read-only API, plus Prometheus metrics for Grafana. Scraping never wakes the PBS.
No outbound requests, self-hosted fonts, update check strictly opt-in. English + Italian, dark & light, works on your phone.
A dedicated PBS box is the right way to keep backups on separate hardware — the 3-2-1 rule. But leaving it running around the clock burns power for nothing, and Proxmox's built-in schedules assume the target is always reachable, so they can't drive a wake-then-sleep cycle.
Joulenap fills that gap: a joule saved, while your backup server takes a nap. 💤
Illustrative — actual savings depend on your backup window & hardware.