Sell VPS and cloud services on the Proxmox cluster you already run. Self-service customer panel, billing integrations, VPC networking on Proxmox SDN, snapshots, backups, live migration, and a full automation API.
Built for Proxmox VE 9 · Runs alongside KVM nodes · No cluster rebuild required
Proxmox gives you clustering, storage, and the VM lifecycle. Everything between your cluster and a paying customer is on you. That is the part Hypervisor.io does.
Every user lands in the same datacenter view. There is no safe way to hand a customer a login and let them manage only their own VMs.
Isolated customer accounts with their own instances, networks, backups, and API keys. Team sub-users with role-based permissions.
There is no product catalogue, no plans, no billing. Selling VPS means scripting the API yourself and reconciling payments by hand.
WHMCS, Blesta, HostBill, and Paymenter modules, plus built-in hourly billing with credits and auto-suspend. Order to running VM, hands-off.
Reinstalls, consoles, firewall changes, backup restores: every routine request becomes a ticket your team resolves in the Proxmox UI.
Customers reinstall, snapshot, restore, open consoles, and manage firewalls themselves - scoped to their own resources, audited, and rate-limited.
No reinstall, no migration weekend. Point the panel at your Proxmox API endpoint and it takes it from there.
Add your Proxmox VE API endpoint and token. The panel discovers nodes, storages, and networks automatically.
One command per node installs the lightweight agent that powers browser consoles and per-instance bandwidth metering. Install state is tracked per node, with retries surfaced in the panel.
Attach images and instance plans, connect billing, and take orders. Deploys restore from pre-built templates for fast, repeatable provisioning.
An error-first dashboard raises node issues - failed installs, unreachable agents, metering gaps - instead of hiding them in logs.
The panel manages only the instances it provisions. Whatever else runs on the cluster stays out of scope.
Provisioning modules with SSO. Order, suspend, upgrade, and terminate flow straight through to the cluster.
Credit-based hourly billing with multi-currency support, location-based pricing, and automatic suspend and resume on balance.
Sell a pool of CPU, RAM, and storage. Customers create and destroy instances inside their quota, self-service.
Per-instance traffic accounting on Proxmox nodes, including VPC traffic, feeding quotas and overage policy.
Three billing models, one cluster. Plug Proxmox capacity into the billing system you already run, meter it hourly like a public cloud, or sell prepaid resource pools - without writing glue code against the Proxmox API.
Billing integrations in depthThe operations customers expect from a cloud, running natively on Proxmox VE primitives.
Named VM snapshots with create, roll back, and delete - from the customer panel or the API, tracked as tasks with live progress.
Backup jobs on schedules you define, full-image restore, and single-file recovery: browse a backup and download individual files without restoring the whole VM.
Move running instances between Proxmox nodes with a precheck that validates the target before anything moves.
Browser-based VNC through the Proxmox console proxy, plus a Web SSH terminal that reaches instances on public IPs and inside VPCs.
Images build once into backup archives and restore into each new VM - fast provisioning that stays node-aware on your storage.
Guest agent IP reporting and instance tags synced with the cluster, so the panel and Proxmox stay consistent both ways.
Customer-facing private networking built on Proxmox VE's own SDN stack - EVPN zones with VXLAN overlays - not a bolted-on network layer your cluster does not understand.
Customers create isolated private networks from the panel. Each VPC maps to an EVPN zone and VRF on the cluster, provisioned automatically.
Reusable rule sets with IP sets, synced to Proxmox firewalls per node. Change detection skips no-op syncs, and reconciliation runs in parallel across nodes.
The Web SSH proxy routes through the VPC's VRF, so customers get a terminal on private-only instances without a bastion.
resource "iaas_instance" "web" { location_id = data.iaas_location.nyc.id plan_id = data.iaas_plan.small.id image_id = data.iaas_image.ubuntu.id ssh_keys = [iaas_ssh_key.deploy.id] hostname = "web-01" display_name = "Web 01" }
Everything the panel does on your cluster is driven by the same REST API you get: instances, snapshots, backups, migration, VPCs, security groups. On top of it sit an OpenTofu / Terraform provider and an MCP server, kept in lockstep with the API on every release.
The questions operators ask before putting a panel in front of their cluster.
Not out of the box. Proxmox VE is a hypervisor and cluster manager: its permission system is built for administrators, not for customers who should only ever see their own virtual machines. Hypervisor.io adds the multi-tenant layer on top - isolated customer accounts, a self-service panel, quotas, billing, and API access - while Proxmox keeps doing what it does best underneath.
Yes. Hypervisor.io turns a Proxmox VE cluster into a sellable VPS and cloud product. Connect your billing system through the WHMCS, Blesta, HostBill, or Paymenter modules, or use the built-in hourly billing with credit balances and auto-suspend. Customers order, get a VM provisioned on your cluster automatically, and manage it themselves from the customer panel.
The integration is built and tested against Proxmox VE 9. It talks to your cluster over the standard Proxmox API using an API token, plus a lightweight node agent that is installed with a single command per node.
No. You link an existing cluster: the panel discovers your nodes and storages, and only manages the instances it provisions. Existing virtual machines on the cluster are left untouched and are excluded from cleanup scans.
Provisioning modules stop at create, suspend, and terminate. Hypervisor.io is a full cloud platform on top of your cluster: VPC private networking on Proxmox SDN, security groups, snapshots and scheduled backups with file-level restore, live migration, browser consoles, bandwidth metering, a REST API, an OpenTofu / Terraform provider, and an MCP server for AI agents - alongside the billing integrations.
Yes. Proxmox VE clusters and standalone KVM hypervisors are managed from the same panel, with the same plans, images, billing, and customer experience. You can adopt Proxmox gradually without splitting your infrastructure across two systems.
Link your cluster, install nodes with one command, and start selling VPS with the billing system you already use.