Proxmox VE 7.x and 8.x are the tested targets. The app uses standard REST endpoints (/api2/json/...) that have been stable for years. If something breaks on a specific minor release, file it on support.
Both. The app queries /cluster/resources which returns all nodes, VMs, containers, and storages. Single-node installs look the same as a one-node cluster.
No. ProxmoxVue talks directly to your Proxmox server's REST API. No account with us, no cloud relay, no third-party signup. Your iPad is the client, your Proxmox is the server. That's it.
Three ways, pick what matches your setup:
Username + password + realm — same as the Proxmox web UI. Use PAM, PVE, LDAP, or AD.
OIDC — if your realm is Authentik, Keycloak, or any other OpenID Connect provider, the app opens your browser for the login and catches the callback. You need to allow proxmoxvue-auth://callback as a redirect URI in your provider.
API Token — classic scoped tokens. Toggle "Use API-token instead" in the add-host screen.
Yes. Flip the "Accept self-signed TLS" toggle when adding the host. The app disables certificate validation for that host only — other hosts are still validated.
In the iOS Keychain, which is:
— encrypted at rest by the OS,
— only accessible when the device is unlocked,
— never synced to iCloud,
— scoped to this app only.
OIDC session tickets are held in memory only — never persisted. A fresh browser login is required if the ticket expires.
The iPhone market has several Proxmox apps. The iPad doesn't. We thought that was a gap worth filling: a proper three-column split view, long-press context menus, big tap targets — a touch-native tool designed for the size, not a phone UI stretched to 11 inches. An iPhone companion is on the roadmap (push notifications, widgets, quick actions) but won't ship as a full management tool.
No. The Proxmox web UI on a desktop is good enough; a Mac app would add too little to justify the build cost.
Not at this time. We may reconsider later.
See the support page — we read everything.