2 min readWHMCS
We run our hosting business on WHMCS, and like most companies that do, we keep hitting the same gap. WHMCS knows what a customer bought. The provider knows what machines exist. Neither one knows much about the other, so the map between them ends up living in a spreadsheet, a naming convention, or somebody's memory.
That is fine at five servers. At fifty it turns into quiet, expensive mistakes: capacity nobody accounted for, a service still pointing at a machine that was rebuilt last month, a cancellation that closes the invoice and leaves the VPS running. We got tired of reconciling it by hand, so we started building VPS Manager for WHMCS.
What we are building
VPS Manager is a central, WHMCS-oriented management layer for VPS infrastructure. The point is that the servers you actually have and the services you have sold become one set of records instead of two lists you compare on a Friday afternoon.
What we want it to do, once it is finished:
- keep visibility over VPS inventory and real available capacity
- tie infrastructure to WHMCS products and to individual customer services
- move more of the service-management workflow onto VPS automation rather than manual steps
- expose an appropriate set of white-label VPS controls to the customer
That is the target we are working toward, not a changelog. We are not going to publish a feature list for software that is still being written.
Where it actually is
VPS Manager is under active development and is not publicly available. There is no release date, no pricing, and nothing to buy.
Development is currently focused on the netcup WHMCS integration, which is the first connector we are building. netcup is not involved in this project and does not endorse, support or supply it. The connector is ours.
How we are approaching it
The architecture is provider-independent. netcup is the first connector, not the shape of the whole product, and nothing about the design assumes a single provider.
Beyond that, a few things we are not willing to trade away. Your infrastructure stays yours; a management layer should not quietly become the thing that owns your servers or your customer relationships. WHMCS integration should be tight, because the billing truth already lives there. The customer-facing side carries your brand. And it goes out when it behaves reliably in production, not when the feature list looks impressive.
What happens next
We will share more as VPS Manager reaches the next development milestones. There is no waitlist and no sign-up form, because we do not have anything to hand you yet.
If you want to follow it, keep an eye on this blog. And if you run a hosting company where WHMCS VPS management is a daily irritation too, we would like to hear how you handle it at the moment. Tell us.