Atlas vs the stock Proxmox UI: a layer, not a replacement
The fairest way to describe Atlas: the Proxmox web UI is good at the everyday middle, and Atlas adds the layer above it, relationships, guidance and safety, without replacing or forking anything. This page draws the line honestly.
Where the line runs
The stock UI is dependable for lifecycle work: create a VM, resize a disk, watch a task. Proxmox earned its reputation with it, and Atlas does not pretend otherwise.
What the stock UI does not carry is the connective tissue: how guests, bridges, pools and disks relate; what a risky change will touch; who did what afterwards. Those live in the admin’s head, in the shell and in scattered logs.
Atlas is that missing layer: topology as a first-class view, risky work as guided flows with impact shown, an audit trail, and a sentinel watching health. The PVE UI stays; the days it cannot carry get a home.
Where each surface fits
The honest division of labor looks like this:
Quick VM lifecycle work: both fit; the stock UI does it fine, Atlas does it with topology context.
Storage layout days, pools and datasets: Atlas, with wizard flows and a flow map instead of shell sessions.
Network change days: Atlas, with impact shown first and a way back if the change cuts the connection.
Update days: Atlas, with effect groups, a snapshot first and a guarded boot.
The after-incident question of who did what: Atlas, with the audit trail.
Anything Atlas does not cover yet: the stock UI and the shell are right there, untouched.
What the layer adds
The same host, one level more sight.
Topology as the home screen
The host is drawn as a living map of guests, bridges, pools and disks. The stock UI's tree becomes a picture.
Guided risky operations
Storage, network, update and restore days run as checked step-by-step flows instead of a text field and courage.
Impact before apply
Critical changes list affected resources and ask for confirmation first; the stock UI applies whatever was typed.
An audit trail
Critical actions are recorded with actor, action, time and result, kept twice on the host.
A built-in sentinel
Watch runs scheduled health checks and mails critical findings; there is no separate monitoring stack to assemble.
Nothing taken away
No fork, no lock-in: the PVE UI, the API and the shell keep working exactly as before, Atlas rides alongside.
Frequently asked
- Does Atlas replace the Proxmox web UI?
- No. It runs alongside as a layer. Anything better done in the stock UI stays exactly where it was.
- Does Atlas modify Proxmox?
- No fork, no patched packages. Atlas manages standard Proxmox through its own service on the host; remove it and Proxmox is untouched.
- Why not just the stock UI plus the shell?
- That is exactly what most admins do today, and it works until the risky days. This comparison is about those days: topology, impact, guided flows and audit are the difference.
- Is Atlas open source?
- The agent that runs with root privileges is open under AGPL and can be audited. The interface and product layer are commercial; the commercial layer never runs as root.
- Does it work with existing setups?
- Yes. Atlas reads the host as it is: existing guests, pools, bridges and jobs appear on the map without migration or reconfiguration.
- What happens if I uninstall it?
- Proxmox continues as if Atlas was never there. The layer adds; it does not entangle.
- How does Atlas differ from Proxmox Datacenter Manager?
- Two different layers, not rivals. Datacenter Manager gathers separate Proxmox installations into a single view. Atlas is the operations and safety layer that runs on the host itself: it shows in advance what a change will touch, the dependency chain that runs from storage to virtual machine, and the real impact of an update. Atlas's federation direction comes from the same place; the real value is being able to see independent hosts in separate locations, which Proxmox cannot join into one cluster, under a single roof. The more places Proxmox runs, the more Atlas means, which is why we stand on the same side.
- Is Atlas an alternative Proxmox UI?
- Atlas is not an alternative Proxmox UI but a layer added on top of it. The Proxmox web interface stays exactly as it is and can be used at any time; Atlas does not try to take its place. People looking for a better interface for Proxmox usually find that what was missing is not a screen but context: what depends on what, where a change will land, and where the way back stops.
Related entries
- What the Proxmox web interface does well, and where you end up opening a second screen The native interface is not the weak part of Proxmox. It is precise, complete and honest. The friction is in one specific place: questions whose answer lives across several screens at once.