ProxDash is a dashboard for a Proxmox fleet that fits on a phone. Connect it straight to a Proxmox VE cluster or node, a Backup Server, or a Datacenter Manager — in any mix — and to Portainer for the Docker guests inside them.
Proxmox's own interfaces were built for a desktop. ProxDash puts your whole fleet — PVE, PBS, and PDM alike — on a screen you can actually read at the kitchen table, and adds the things they leave out.
An Overview of cards you drag, hide, and configure in place — with separate layouts for phones and wide screens, a Compact mode, and a getting-started card that walks a fresh install through setup.
No account, no analytics, no developer in the path. Requests go from you to your servers. Self-signed certificates get pinned by fingerprint after you approve them, and there's no way to switch verification off.
Sign in with a PDM account and ProxDash has PDM mint an API token under it — Auditor for view-only, Administrator for control. A token can never do more than its user, and your password is used once and never stored.
Unreachable remotes, nodes offline, storage past a level or forecast to fill, failed or stale backups, unhealthy containers, newer images — over ntfy, Telegram, or web push, with a history of what cleared and how long it lasted.
Fleet, storage, backups, updates, and containers — read at a glance, controlled on purpose.
Fleet totals, top lists, storage, backups, updates, alerts — drag to reorder, hide what you don't need, and configure each card in place.
Two weeks of PDM's usage history become bytes-per-day and the date each volume fills — so the warning comes before the disk does.
Per PBS datastore and per PVE backup job: when the last backup succeeded and whether recent ones failed, from a week of task history.
Package updates waiting across every node — PDM itself included — and a warning when PDM's certificate has under a month left.
Link Docker guests to their Portainer environment: see stacks and containers, start/stop/restart them, and get honest image-update checks — digest-compared, pinned tags left alone.
Stop a stack cleanly before its guest, snapshot a guest, clean image layers — chained into scenes you can reverse, run on demand, or run on a weekday schedule.
ntfy, Telegram, and web push — all sent by your own server, with push keys it generates on first boot. Nobody else is in the path.
Every guest action, container action, and scene run lands in one history — including scheduled runs — and every task and container has a Log button.
The iOS app talks to your servers directly — no proxy needed — with a Face ID lock, a Home Screen widget, and card layouts that sync through your own iCloud.
The server ships behind Caddy, which terminates TLS and is the only thing listening — the API publishes no ports and can't be reached in plaintext at all. Five wrong passwords lock the account for fifteen minutes, tokens are encrypted at rest with a key derived from your secret, and certificate verification can't be turned off.
Put it behind Tailscale or a VPN and nothing needs to be exposed. Proxmox, dashboard — the name is exactly what it says.
You need Docker and a Proxmox server to point it at — PVE, PBS, or PDM. The stack is pasted into Portainer's editor — no compose file lives on the host.
ProxDash plus Caddy, with a secret key and the one account's username and password.
The single account is created on first boot, and only while no user exists.
Settings checks each certificate, shows its fingerprint for you to confirm, then mints a scoped token under your account.
Caddy issues a certificate from its own CA by default — your phone trusts it after a one-time step Settings walks through — or gets a publicly trusted one with a DNS provider token. Migrations run themselves into one SQLite file under /data.