Providers¶
A provider is the connection between PteroCloud and the virtualization platform that runs your VMs. PteroCloud supports two provider types:
| Provider | Transport | Credential |
|---|---|---|
| Proxmox VE | HTTPS API to the PVE cluster | A least-privilege API token (user@realm!tokenid=secret). |
| Native KVM | Outbound HTTPS from the host to the panel | The pterocloud-agent and a per-node revocable credential. |
Both providers expose the same panel concepts (hypervisors, storage, networks, images, instances), so the rest of the documentation is provider-agnostic.
Proxmox¶
Native KVM¶
Native KVM maturity
The native agent's panel-side plumbing, enrollment, discovery and diagnostics are implemented. Live libvirt/QEMU binding has not been tested on hardware in this build. Treat Native KVM provisioning as a foundation, not a proven production path.
Provider list¶

Adding a provider¶

Admin → PteroCloud → Providers → Create registers a connection. Creating a connection deliberately does not auto-test it; use Test Connection on the form or the provider view.

Provider capabilities¶
A connection's discovered capabilities gate what the scheduler will place on it. Unknown capabilities are treated as unavailable, never assumed present. See Infrastructure.
Related¶
- Troubleshooting: Proxmox
- Troubleshooting: Native KVM
PC-PROV-###/PC-PVE-###/PC-KVM-###/PC-AGT-###in the error reference