Proxmox VE billing that builds the VM when the invoice is paid
Connect a Proxmox VE 7 or 8 node with an API token. A paid order clones one of your cloud-init templates, sizes it to the product, waits for Proxmox to finish each task and starts the VM. The customer gets power controls, a console and snapshots in the client area; an overdue invoice powers the VM off, and termination deletes it with its disks.
The plugin is free. Your plan is the only bill.
The Proxmox VE plugin is listed at no charge on the FluxBilling marketplace and installs on every tier. Plans are priced by the clients you bill, and by bare-metal servers if you sell those. There is no per-VM or per-node charge for machines this plugin manages.
Proxmox VE stays exactly as it is. The plugin talks to its API with a token you create, and works with or without a Proxmox subscription.
- Plugin price
- Free
- Available on
- Every tier
- Proxmox versions
- VE 7 and VE 8
- Authentication
- API token
- Guests
- KVM virtual machines
- Plugin version
- 1.4
What happens between “Pay” and a running VM
Proxmox does its work as background tasks. The plugin waits for each one to finish before moving on, so a half-cloned VM is never handed to a customer.
- 01OrderThe customer picks the product and a hostname at checkout. The invoice is created and paid like any other.
- 02VMID and nodeThe plugin asks Proxmox for the next free VMID and uses the node set on the product, or the default node from the plugin settings.
- 03Clone the templateThe product’s cloud-init template is cloned: a full, independent copy onto the storage you chose, or a linked clone when the template sits on shared or snapshot-capable storage.
- 04Wait for ProxmoxThe clone runs as a Proxmox task. The plugin polls it every few seconds until it reports success, and stops with a named error if it fails.
- 05Apply the planCores, memory, the cloud-init user and password, IP configuration and DNS servers are written to the new VM, and the boot disk is grown to the size on the product.
- 06Start and checkThe VM is started and its state verified. Its address appears in the client area as soon as the QEMU guest agent inside the VM reports it.
What the customer can do with a Proxmox VM
The service page is drawn from the plugin, so every button maps to something Proxmox can actually do.
Staff side. Staff see the same page plus the Proxmox details — node, VMID and the template it was cloned from — and can reset the root password through cloud-init, force a stop, and manage snapshots on the customer’s behalf.
One product, one template, one size
Each product you sell points at a template and carries its own sizing. Two products can share a template and differ only in cores, memory and disk.
| Setting | What it decides |
|---|---|
| Node | The Proxmox node new VMs are created on. Empty uses the plugin’s default node. |
| Template VM | The cloud-init template cloned for each order, picked from the templates the node reports. |
| CPU cores / Memory | The vCPU count and RAM, in MB, applied after the clone. |
| Disk (GB) and boot disk device | The size the boot disk is grown to — never smaller than the template’s — and which disk that is, usually scsi0 or virtio0. |
| Target storage | Where the cloned disks go. Full clones only; empty keeps the template’s storage. |
| Network bridge | Overrides the template’s bridge. Empty keeps the template’s network as it is. |
| Full clone | On: an independent copy, the recommended setting. Off: a linked clone, faster, but the template must sit on shared or snapshot-capable storage. |
| IP configuration and DNS | The cloud-init ipconfig for the VM — ip=dhcp, or a static address and gateway — plus optional DNS servers. |
| cloud-init user | The login cloud-init creates. Empty keeps the image default. |
| Start on node boot / name prefix | Whether the VM starts when the node boots, and an optional prefix for VM names in Proxmox. |
Connect a Proxmox node in five steps
- 01Make a templateBuild a cloud-init VM image with the QEMU guest agent installed and convert it with qm template. The guest agent is how the plugin learns the VM’s address.
- 02Create an API tokenIn Proxmox: Datacenter → Permissions → API Tokens. Either untick Privilege Separation, or grant the token VM.*, Datastore.AllocateSpace and Sys.Audit.
- 03Install the pluginInstall Proxmox VE Provider from the marketplace in your FluxBilling admin panel. It is free.
- 04Enter the connectionHost, API port, token ID, token secret and a default node — the fields on the right.
- 05Build a product and test itPick the node, template and size on a product, then place one test order before you sell it.
- Proxmox hostHostname or IP of the Proxmox VE server — no https:// and no port.
- API portThe web and API port, 8006 unless you changed it.
- API token IDIn the form user@realm!tokenname, for example root@pam!fluxbilling.
- API token secretThe UUID Proxmox shows once, when the token is created.
- Default nodeThe node name used when a product does not name one.
The invoice drives the VM
| When | The plugin |
|---|---|
| Invoice paid | Provisions the VM as described above. |
| Overdue past your grace period | Suspends: the VM is powered off. Its disks and configuration are untouched. |
| Paid after suspension | Unsuspends: the VM is started again. |
| Upgraded | Applies the new plan’s cores and memory, and grows the boot disk if the new plan is larger. A disk is never shrunk. |
| Terminated | Force-stops the VM, then deletes it and its disks, and waits for Proxmox to confirm. |
Grace periods, reminders and the order in which renewals, payments and suspensions run are platform settings shared by every service — see Billing and Provisioning.
What it does not do
- KVM virtual machines only. LXC containers are not provisioned by this plugin.
- Built for Proxmox VE 7 and 8. Proxmox VE 9 is not on the plugin’s supported list yet.
- Addresses are not drawn from FluxBilling’s IPAM. The VM takes the product’s cloud-init ipconfig — DHCP on your bridge is the usual choice — and the plugin reads the address back from the guest agent.
- Disks only grow. Moving to a plan with a smaller disk changes cores and memory and leaves the disk as it is.
- Linked clones need the template on shared or snapshot-capable storage; on local storage, use full clones.
Or bring the Proxmox machines into FluxBilling’s own VPS module
The plugin keeps Proxmox VE in charge of your virtual machines. If you would rather run KVM without a separate panel, FluxBilling’s VPS module manages the hypervisors directly through its own agent, and VPS Panel Migration adopts the VMs already running on a Proxmox VE node — they keep running throughout, and nothing is stopped or rebuilt.
That path is priced per node rather than free, and it is a bigger decision than installing a plugin. Most operators start with the plugin.
How the VPS module worksProxmox VE and FluxBilling, answered
- Is there a Proxmox billing panel that does not need WHMCS?
- Yes. FluxBilling is the billing system, the client area and the provisioning in one product, so the Proxmox plugin connects straight to it — there is no WHMCS module to buy or maintain in between.
- What does the Proxmox plugin cost?
- Nothing. It is listed free on the FluxBilling marketplace and installs on every tier. You pay for your FluxBilling plan, which is priced by the clients you bill — not by virtual machines.
- Which Proxmox VE versions are supported?
- Proxmox VE 7 and 8, over the standard API on port 8006 with an API token. Version 9 is not on the plugin’s supported list yet.
- Can customers use the console and take snapshots?
- Yes. The client area has power controls, a browser console, and snapshot create, restore and delete. Restores and deletes ask for confirmation first.
- How are IP addresses assigned?
- Through cloud-init, from the ipconfig on the product — usually DHCP on the bridge the VM is attached to. The plugin reads the resulting address from the QEMU guest agent and shows it in the client area. It does not allocate from FluxBilling’s IPAM.
- What happens when a customer does not pay?
- Once the invoice passes your grace period the VM is powered off, with its disks left intact. Paying starts it again. Termination deletes the VM and its disks.
Proxmox and Proxmox VE are trademarks of Proxmox Server Solutions GmbH. FluxBilling is not affiliated with or endorsed by its owner; the name is used only to say which software the plugin connects to. Plugin facts read from plugin version 1.4, September 2026.
Around the Proxmox plugin
- All pluginsPayment gateways, hypervisor panels, game panels and notifications — every one free on the marketplace.
- VPS moduleKVM on your own machines without a third-party panel, with live migration and IPAM.
- ProvisioningHow a paid order becomes a running service, for every provider.
- VirtFusion pluginThe other KVM panel operators most often pair with a billing system.
- Billing software for VPS providersHypervisor coverage, resize and proration, and suspension that reaches the hypervisor.
- PricingTiers from Lite to Business, and the 14-day refund.
Try it on your own data. Refund inside 14 days if it’s not the fit.
Pick a tier and provision a tenant in under two minutes — isolated K3s namespace, your own database, the full product. If FluxBilling isn’t the right fit inside 14 days, open a ticket and we’ll refund the subscription. No sales call, no qualification gate. Want to look around first? The live demo opens the admin and client panels with sample data, no signup.
- 01.< 1 minPick a tierLite from €4.95/mo. Upgrade later, no migration.
- 02.< 2 minProvision the tenantIsolated K3s namespace + your own PostgreSQL database. Full product, your data.
- 03.d0 — d14Refund inside 14 daysNot the fit? Open a ticket within 14 days and we refund the subscription. No questions, no qualification gate.