Proxmox VE VPS Provisioning Module for WHMCS
Sell KVM VPS and LXC containers from your own Proxmox VE clusters, with IP pools, hardware packages and a full customer control panel.
What does the Proxmox module do?
It connects WHMCS to one or more Proxmox VE clusters through the Proxmox API, using an API token, and turns each paid order into a running VPS. It comes in two parts. The server module handles provisioning and the customer's control panel. The admin addon is where you add clusters, sync nodes, ISOs and templates, fill IP pools with gateway, netmask and VLAN, and build hardware packages. In WHMCS it appears as WHMCSPilot Proxmox.
Provisioning runs as a background task, started by the module in a separate PHP process, and the customer sees its progress on the service page. A slow template clone or OS install therefore never holds up checkout or the WHMCS cron.
How do packages and build-your-own plans work?
A hardware package sets the virtualization type (KVM or LXC), cores, sockets, RAM, disk, storage pool, network bridge, BIOS mode, CPU type and the default ISO or cloud image template, plus a backup limit. You link a package to a WHMCS product. For plans where the customer chooses the size, add configurable options named Cores, RAM, Disk, IP, Operating System and Node. The module reads them at checkout, overrides the package with the customer's choices, assigns the number of IPs they paid for and installs the image they picked.
When a package can be placed on several clusters, the module picks the one with the most free RAM or free storage, depending on the strategy you set, and only uses clusters that still have enough free IPs in the pool.
What can customers do?
| Area | Client area actions |
|---|---|
| Power | Power on, force stop, reboot |
| Console | Browser console (noVNC) opened from the service page |
| Access | SSH details, plus a downloadable SSH command file or RDP file for Windows |
| Operating system | Reinstall from the OS library, mount or eject ISOs, change the boot order |
| Backups | Create and restore backups; the oldest is removed once the package limit is reached |
| Settings | BIOS or UEFI, display driver, QEMU guest agent, password change through Cloud-Init |
| Monitoring | CPU, RAM and network graphs over 1 hour, 24 hours or 7 days |
| Upgrades | More cores, RAM or disk through the WHMCS upgrade page |
Admins get power and console buttons on the service, live stats, an IP manager and an activity log of actions per service. The interface ships in ten languages, with a language manager in the addon and right-to-left layout for languages such as Arabic.
Who is it for?
Hosting companies that own or rent servers, run Proxmox VE on them and want to sell VPS plans under their own brand, with WHMCS handling billing and customers managing their own machines instead of filing tickets.
What do you need, and what are the limits?
Requirements: WHMCS 8.x (confirmed at purchase), PHP 8.0 or newer with the CLI and the exec function available for the background worker, Proxmox VE 7.0 or newer with an API token and port 8006 reachable from WHMCS, and IP addresses with gateway and netmask for the pool.
Limits: disks can only grow, because Proxmox cannot shrink virtual disks; changing the OS from an ISO is for KVM machines, while LXC containers are reinstalled instead. You supply and run the Proxmox hardware, storage and network, and the module needs its license key activated in the addon.
It costs $249 once for a lifetime license with twelve months of updates and support, an instant download and license key, and a seven-day refund window.
Key features
- KVM virtual machines and LXC containers on Proxmox VE
- Multiple clusters with automatic choice by free RAM or storage
- IP pools with gateway, netmask and VLAN, freed on termination
- Hardware packages built from ISOs or cloud image templates
- Build-your-own plans from Cores, RAM, Disk, IP, OS and Node options
- Background provisioning with progress shown to the customer
- Power controls and browser noVNC console
- OS reinstall, ISO mounting and boot order changes
- Backups with restore and a per-package backup limit
- Ten interface languages with a language manager
Why customers buy this module
- →Turn your own Proxmox servers into a self-service VPS product
- →New orders land on the cluster with the most room, without manual placement
- →Customers reinstall, restore and reboot on their own, which cuts support tickets
- →IP addresses are tracked and returned to the pool when a service ends
Frequently asked questions
Does the module support both KVM and LXC?
<p>Yes. Each hardware package sets the virtualization type, so you can sell KVM virtual machines and LXC containers from the same install. KVM machines can boot from an ISO or be cloned from a template with Cloud-Init. LXC containers are created from container templates, and to change their OS the customer reinstalls rather than mounting an ISO.</p>
Can customers choose their own CPU, RAM and disk at checkout?
<p>Yes. Add configurable options named Cores, RAM, Disk, IP, Operating System and Node to the product. The module reads them at checkout, overrides the base package with the customer's choices, assigns the number of IPs they bought and installs the operating system they selected. Disk sizes can be raised later but never lowered.</p>
How are IP addresses handled?
<p>You add IP addresses to a pool in the addon, with gateway, netmask and an optional VLAN. The module assigns the next free address, or several when the customer buys extra IPs, and writes them on the WHMCS service. When the service is terminated, the addresses go back into the pool for the next order.</p>
Technical specifications
- WHMCS
- 8.x (confirmed at purchase)
- PHP
- 8.0+
- Proxmox VE
- 7.0 or newer, API token, port 8006
- Virtualization
- KVM (QEMU) and LXC
- Components
- Server module and admin addon
- License
- Lifetime, 1 year of updates and support included
- Delivery
- Instant download and license key
- Refund window
- 7 days