Proxmox, without handing over a password.

Add a Proxmox node

Run the usual install line on each node. The agent notices Proxmox VE on its own machine, and the node appears under Hosts like any host, and in the Proxmox area.

• Supported: Proxmox VE 8.4 or later in the 8 line, and Proxmox VE 9. A node outside that range is listed under Not supported, with the reason.
• No credentials to hand over. The agent runs on the node and reads Proxmox's own tools there, with fixed commands. There is no Proxmox user, password or API token to give BasePit.
• Clusters are recognised by the nodes themselves. Nodes that report the same cluster form one cluster in BasePit; a single node is a cluster of one. The cluster's identity is derived on the node and its key never leaves it. A cluster that two organisations try to add is refused in both.
• The agent reads guests, nodes and storage every 30 seconds, backups and power tasks every 60 seconds, and the node's facts every 5 minutes, and sends each part again only when it changes.

What you see

What you can do

• Power: start, shut down, stop (asked first) and restart a guest.
• Snapshots: take one, roll back to one, delete one.
• Delete any guest by typing its name. Proxmox's protection flag is honoured and never cleared.
• A guest's action runs only through the agent on the node where the guest runs.
• Every action is a fixed command, recorded in Activity.

Terminals and screens

On a node whose agent was installed with --allow-terminal:

• A container's terminal, through pct enter.
• A VM's screen in the browser, through qm vncproxy. The agent makes a one-time password for each screen and answers Proxmox's VNC check itself, so no password is ever offered to the browser or leaves the node.
• Only for a guest running on that node. Recorded when it opens and closes, and never a byte of what is typed or shown.

Make a host

Make a host on Proxmox creates a new VM or container with BasePit's agent already inside. It joins as a host, ready for your apps.

1. Where: a node whose agent is connected, a storage for its disk, and the network bridge its card sits on (it asks for an address by DHCP).
2. From: a known image, Ubuntu 24.04 LTS or Debian 13, as a VM or a container, downloaded and checked by BasePit. Or your own template: a VM template with a cloud-init drive, or a container template on the node's storage.
3. Size, then a name. The name is also the new host's name in BasePit.
4. Review. Nothing is made until you press Make the host.

• The new guest gets a one-time token as a private file: in a VM's start-up file, on a storage that accepts start-up files, or pushed into a container. It never appears in a process list, and the start-up file is deleted once the guest joins.
• It joins without waiting for approval: the person who made it is the approval. From then on it counts as one of your hosts.
• If it has not joined 15 minutes after it started, it is marked failed with the reason, and left on Proxmox for you to look at. BasePit never deletes a guest on its own.
• Deleting a made guest also revokes its host.

On Proxmox VE before 9.1, Make a host makes VMs only.

Alerts and access

• Four alert types: a guest that stopped when nobody stopped it, storage over 90 %, a backup that failed, and a cluster that lost quorum. None is switched on by itself; you choose.
• Quiet a whole cluster, a node or a single guest.
• Four levels of access (read, operate, manage, terminal) within the existing roles. Every row is scoped by its node, so access rules on hosts narrow the Proxmox area too.
• A Proxmox node counts as a host. What that costs.

What BasePit never does

• Ask for a Proxmox password or API token.
• Update or reboot a Proxmox node.
• Delete a guest on its own, or clear a guest's protection.
• Create or change backup jobs: backups are read-only.