VMware Billing Software for Hosting Providers in 2026: What Still Works After Broadcom

Few hosting billing platforms still provision VMware in 2026. HostBill sells a maintained VMware Cloud Director module, WHMCS relies on third-party vSphere modules, and many providers bill VMware capacity with their own scripts against the vCenter or Cloud Director APIs. The larger question is upstream: Broadcom has moved VMware to subscription bundles and closed its cloud provider programme to all but invited partners, so many hosts are now billing a migration to Proxmox VE or KVM rather than a VMware platform.

How this was sourced. FluxBilling publishes this page and sells billing software for hosting providers. It has no VMware integration, so it is not one of the VMware options below; where it fits is in the move away. Vendor details were read from each vendor’s own pages on 20 October 2026. Statements about Broadcom’s partner programme come from Broadcom’s own announcements where they exist, and otherwise from The Register’s reporting, named as such.

What changed for VMware hosting providers?

Broadcom’s stated reasons, in its statement and an FAQ seen by The Register, are simplification and working more closely with a focused set of partners. European cloud trade body CISPE has opposed the changes. Our point here is narrower: if your VMware contract ends and is not renewed, what you bill for, and with what, changes too.

What does VMware billing software need to do?

Billing VMware is billing virtual machines, with two common shapes:

• Fixed VM plans. Each customer buys a VM of set vCPU, memory and disk on vSphere. The billing system creates it through vCenter, suspends it when an invoice goes unpaid and deletes it on cancellation. This is the VPS model.
• Virtual data centres. Through VMware Cloud Director, a customer gets an organisation and a virtual data centre with a pool of resources to carve up themselves. The bill follows the allocation (CPU, memory, storage, IP addresses, network rate limits) rather than individual VMs.

Either way the module has to provision, suspend and terminate, and the invoice has to match what is actually allocated.

Billing platforms that still integrate with VMware

If you are staying on VMware and selling virtual data centres, HostBill’s Cloud Director module is the maintained, ready-made option we found. If you sell fixed VMs from vCenter on WHMCS, the WGS module is the documented route. Either way, check the module against the exact vCenter or Cloud Director version you will run under your new Broadcom contract before you renew.

Moving off VMware: what the hypervisor side looks like

A common destination is Proxmox VE, which is open source and has a built-in importer. Proxmox’s own migration guide says the import wizard takes VMs from an ESXi host, and OVA or OVF files, and was tested with ESXi 6.5 to 8.0. The same guide lists the limits:

• Disks on VMware vSAN do not import directly; move them to other storage first.
• The state of a virtual TPM cannot be migrated, so have recovery keys ready for encrypted guests.
• VMs with snapshots import much more slowly.
• The ESXi API allows few connections, so run imports one after another rather than in parallel.

Proxmox VE subscriptions, which add the enterprise repository and support, cost €120, €370, €550 or €1,100 per CPU socket per year depending on the support level, as published on 20 October 2026. Other KVM-based panels sold to hosting providers include SolusVM 2, Virtualizor and VirtFusion. How the billing platforms compare for VPS businesses is covered in our guide to billing software for VPS and cloud hosting providers.

How to bill customers through a VMware migration

The technical move gets the planning; the billing is where customers notice mistakes. What we would check:

1. Map every VMware plan to a new product first. Same specification and price, or a deliberate change you announce. Customers should not discover a new price on the first invoice after the move.
2. Never bill twice for the overlap. While a VM exists on both platforms, only one service record should generate invoices. Move the service record, do not create a second one.
3. Keep the renewal date. Moving a service should not reset its billing cycle; if it must, credit the difference. Our guide to proration for mid-cycle changes covers the arithmetic.
4. Carry IP addresses and allocations across. If a customer keeps their addresses, the new platform’s IP records must show them as allocated before the old platform releases them.
5. Time it against your Broadcom term. If your commitment ends on a fixed date, work back from it, leaving time for customers who need a maintenance window of their own.
6. Tell customers what changes and what does not. Console access, snapshot rules and backup tools usually change; price, addresses and support contacts ideally do not. If the price does change, our notes on raising hosting prices without losing customers apply.

Where FluxBilling fits, and where it does not

FluxBilling cannot provision or bill VMware: there is no vSphere, ESXi or Cloud Director module and no ESXi import. If you are staying on VMware, use one of the options in the table above.

It fits the destination side of a move:

• Proxmox VE. The Proxmox plugin creates KVM VMs by cloning a cloud-init template, with power, VNC console, snapshots, password reset and CPU, memory and disk upgrades. It does not do LXC containers, and it is documented for Proxmox VE 7 and 8.
• SolusVM 2, Virtualizor and VirtFusion plugins provision, suspend, terminate, reinstall and power-manage VMs on those panels. Plugins are included on every tier with no node charge.
• Native KVM. FluxBilling’s own VPS module runs an agent on each KVM node, with IPv4 and IPv6 from its IPAM, live migration within a node group and hourly or monthly billing. It is charged per node, €6 a month ($7 for US accounts).
• Taking over a panel. If your VMs land on Proxmox VE, Virtualizor or SolusVM 2 first, the panel migration adopts running VMs in place without restarting them. Proxmox VMs convert to native KVM at their next power cycle. Clients are matched for review, not linked automatically, and backups, HA and Ceph-backed disks are not carried over.

Plainly, where it falls short: no VMware at all, no virtual data centre product of the Cloud Director kind, no VM backups in the native module (snapshots only), and it is pre-1.0 software. Plans start at €4.95 a month ($5.95 for US accounts) with a 14-day refund; see pricing or the live demo.

Frequently asked questions

Does WHMCS support VMware?

Not with a first-party module. VMware provisioning in WHMCS comes from third-party modules such as WGS’s VMware vSphere module, which on 20 October 2026 was at version 5.1.1 for WHMCS 9.0.8 and vCenter 8.x.

Which billing software works with VMware Cloud Director?

HostBill sells a maintained vCloud Director module that creates organisations and virtual data centres and charges on CPU, disk, IP and rate-limit allocation. Otherwise, providers connect their billing system to the Cloud Director API with their own code.

Can I still become a VMware Cloud Service Provider?

According to The Register’s January 2026 reporting, Broadcom has moved the programme to an invitation-only model with fewer authorised providers, and did not renew contracts for many existing partners after 26 January 2026. Check directly with Broadcom; from 1 November 2026, new VCSP contracts are VCSP Commit contracts managed in Broadcom’s Support Portal.

How do I migrate VMware VMs to Proxmox VE?

Add the ESXi host as an import source in Proxmox VE and use its import wizard, which Proxmox tested with ESXi 6.5 to 8.0. Move vSAN-backed disks to other storage first, run imports one at a time and plan for VMs with snapshots to take longer.

Is there free VMware billing software?

We found no maintained free option that provisions VMware. A free route means writing your own integration against the vCenter or Cloud Director API and an open source billing system.

Sources

• Broadcom — “Broadcom Completes Acquisition of VMware”, 22 November 2023, investors.broadcom.com.
• VMware — “VMware End Of Availability of Perpetual Licensing and SaaS Services”, blogs.vmware.com, 22 January 2024, read 20 October 2026.
• Broadcom — knowledge base article 456620, “Announcing important changes being made to the VCSP Program”, updated 21 September 2026, read 20 October 2026.
• The Register — “Broadcom ‘bulldozes’ VMware cloud partners as March deadline looms”, 31 January 2026, read 20 October 2026.
• HostBill — VMware vCloud Director product page and VMware 5 documentation, read 20 October 2026.
• WHMCS Global Services — VMware vSphere WHMCS module page, read 20 October 2026.
• Blesta — module documentation index, docs.blesta.com, read 20 October 2026.
• Proxmox — “Migrate to Proxmox VE”, pve.proxmox.com wiki, and Proxmox VE pricing page, read 20 October 2026.

VMware, vSphere, ESXi, vCenter, VMware Cloud Director, vSAN, VMware Cloud Foundation and VMware vSphere Foundation are trademarks of Broadcom. Proxmox, HostBill, WHMCS, Blesta, SolusVM, Virtualizor and VirtFusion are trademarks of their respective owners. FluxBilling is not affiliated with or endorsed by any of them. Third-party details are as published on the dates above and may have changed since.