Turn Proxmox into a hosting platform

Proxmox VE is an exceptional hypervisor. It is open-source, battle-tested, handles KVM virtual machines and LXC containers side by side, and ships with a competent web interface for the administrator who built the cluster. What it is not, and was never designed to be, is a hosting product. If you want to resell Proxmox VMs or offer managed containers to paying customers, you will quickly discover that the distance between "great hypervisor" and "sellable service" is larger than it looks.

What a Hypervisor Does Not Give You

Out of the box, Proxmox gives every user with an account access to the same administrative surface. There is no concept of a tenant who can only see their own guests, no enforced resource plans that suspend on expiry, no IP address management tied to guest provisioning, and no REST API with the clean envelope your billing system expects. You end up patching the gaps with shell scripts, manual tickets, and spreadsheets, which does not scale past a handful of customers and introduces audit risk at every step.

Closing those gaps is the difference between a lab and a product. Below are the four building blocks that matter most when you want to turn Proxmox into a real hosting platform.

1. A Customer Portal with Real Tenant Isolation

The first thing a tenant needs is a place to log in that shows them only their own servers. This sounds obvious, yet it requires every read and every action to be checked server-side against ownership, not just hidden in the UI. A UI check is cosmetic; a server-side ownership check is a security boundary.

A proper multi-tenant portal should also support SSH key management so customers can inject their own keys at provision time, and two-factor authentication (TOTP) so you can meet baseline compliance requirements without building auth infrastructure from scratch. Role-based access matters too: your support staff needs to be able to impersonate a customer to reproduce a problem without sharing credentials or losing the audit trail.

NexoVirt's customer portal handles all of this. Ownership is enforced on every request; admins can impersonate any customer for support; RBAC keeps the admin panel and the customer portal cleanly separated.

2. Resource Plans with Automatic Enforcement

Selling compute without limits is a support nightmare. Selling limits without enforcement is a billing problem. You need both: a named plan that defines the envelope, and a daemon that acts on violations without human intervention.

A useful plan primitive covers the obvious axes, CPU cores, RAM, disk, but also the ones that trip up new hosting operators: monthly traffic limit (inbound + outbound), runtime in days (subscription expiry), and a grace period before the guest is actually deleted. The enforcement logic then becomes deterministic: suspend on expiry or traffic overage, set a delete-at timestamp, auto-delete after grace, auto-resume suspended-for-traffic guests when the monthly counter resets.

This is the lifecycle that lets you offer a product with predictable margins. NexoVirt's Plans implement exactly this model: you define the plan once, assign it at guest creation, and the enforcement daemon handles the rest. No cron scripts, no manual interventions.

3. IP Address Management, NAT, and Port-Forwarding

Giving a guest a routable address is not automatic in Proxmox. You typically have a pool of IPs, a VLAN or bridge, and some iptables rules, all managed by hand. At scale this becomes untrackable.

A hosting-grade panel needs an IPAM layer: define IP zones (CIDR pools, IPv4 or IPv6), allocate the next free address at provision time, inject it as a static cloud-init ipconfig0, and release it on delete. It needs NAT so guests on a private bridge can reach the internet via MASQUERADE, and port-forwarding (DNAT) so you can expose a guest service on a specific public port without giving the guest a public IP at all.

NexoVirt covers all three layers. IP zones are defined in the panel, allocation and release are transactional, and NAT rules are applied to the host via the discovery agent, which validates every rule on the host side before touching iptables, and never flushes chains it did not create. The node management page also surfaces a read-only host firewall snapshot so you always know what is actually running.

4. A Clean REST API for Billing and Automation

The panel UI is for humans. Your billing system, provisioning automation, and monitoring integrations need an API. A clean one, not a wrapper around Proxmox's own API with all its complexity exposed.

NexoVirt's REST API uses bearer tokens, returns a consistent {success, data, error} envelope on every endpoint, and covers the full guest lifecycle: list, create, power actions, delete, as well as host and node inventory. You create tokens per integration under Settings, scope them as needed, and wire them into whatever billing or automation stack you already run. There is no built-in billing product; the API is the integration point.

Because NexoVirt is self-hosted, the API traffic never leaves your infrastructure. You keep your margin, your data, and your customer relationships.

Managing Multiple Hosts from One Panel

Most hosting operators grow beyond a single Proxmox node. NexoVirt manages multiple Proxmox hosts from one panel. The discovery agent imports existing infrastructure without reinstalling anything: it connects over SSH, registers the node, and begins collecting inventory snapshots. Guests that existed before NexoVirt was installed appear in the panel immediately. You can assign ownership, attach a plan, and bring them under the managed lifecycle without touching the guest itself.

From Hypervisor to Hosting Product

The gap between Proxmox and a sellable hosting service is not technical complexity. Proxmox handles the hard parts. The gap is the product layer: tenant isolation, enforced plans, address management, and a clean API surface. Each of those is a solved problem; what has been missing is a self-hosted panel that assembles them coherently without locking you into a SaaS vendor's margin and data policies.

NexoVirt is available now. Community Edition is free (up to 2 nodes). If you are a hosting provider, MSP, or homelab reseller evaluating whether to build this layer yourself or adopt something purpose-built, get started free and take a look. The documentation covers user management and tenant setup in detail, and the hosting providers page walks through a typical deployment.