---
name: proxmox-hosting-platform
description: Design, provision, inspect, and troubleshoot Proxmox VE, Proxmox Backup Server, KVM, cloud-init, templates, clusters, storage, networks, snapshots, backups, and hosting-product workflows. Use for KVM shops, VPS lifecycle automation, capacity planning, tenant isolation, provisioning plans, backup validation, migration, and integrations with billing, IPAM, DNS, monitoring, and Coolify.
compatibility: Read-only inspection may use a restricted Proxmox token. Provisioning, power, storage, migration, restore, and deletion actions require separate scoped credentials and explicit approval.
license: Apache-2.0
---

# Proxmox hosting platform

Treat virtualization, networking, storage, identity, billing and customer communication as one lifecycle with separate trust boundaries.

## Provisioning workflow

1. Validate the paid order or authorized internal request.
2. Resolve product limits: CPU type, cores, memory, disk, bandwidth, backup, region and lifecycle policy.
3. Check cluster capacity, storage health, quorum and maintenance state.
4. Reserve IP addresses, prefixes, VLAN/VXLAN identifiers and DNS names through the source of truth.
5. Select an approved immutable template and cloud-init profile.
6. Generate a dry-run plan containing node, VMID, storage, network, firewall, metadata and rollback.
7. Create the guest with an idempotency key or order identifier.
8. Apply credentials through a secret-delivery channel; never return private keys or passwords through MCP.
9. Start the guest only after configuration validation.
10. Register monitoring, backups, billing identifiers and ownership metadata.
11. Verify reachability, guest agent, DNS, time, storage and backup policy.

## Operational domains

- cluster and node health;
- CPU, memory, storage and network capacity;
- VM and container lifecycle;
- templates and cloud-init;
- Ceph, ZFS, LVM and directory storage;
- SDN, bridges, VLAN, VXLAN and firewall rules;
- snapshots, replication and backup jobs;
- migrations and maintenance evacuation;
- Proxmox Backup Server restore points;
- customer suspension, reactivation and termination.

## Permission separation

Use independent gates for `read`, `provision`, `power`, `network`, `storage`, `backup-restore`, `migration` and `destructive`. A general operations deployment must not hold deletion rights.

## Safety rules

- Never select a node only by free RAM; include CPU pressure, storage latency, replication and failure domains.
- Never delete a guest solely from a billing webhook. Re-read account, resource mapping and retention policy.
- Never overwrite a disk or restore point without an exact resource identifier and confirmation.
- Snapshot is not backup. Verify independent restore points.
- Test cloud-init images after updates before making them default.
- Preserve customer data according to the configured retention period.

## Output

Return the requested lifecycle action, affected cluster/node/guest identifiers, capacity evidence, network and storage plan, capability gate, dry-run result, verification checks, rollback, backup state and remaining manual steps.