A Proxmox self-service portal for your existing cluster
You can add a customer self-service portal to a running Proxmox cluster without rebuilding a single VM. NexoVirt adopts your existing VMs and LXC containers in place and gives each customer a scoped portal for the servers you assign. Proxmox stays your backend, and customers never see it.
How do you go from a running cluster to a customer portal?
Most portals expect to provision every VM themselves. NexoVirt works the other way round: four steps, and nothing is reinstalled.
-
Add your hosts
Connect each Proxmox host. A one-time SSH step installs a small host agent, and the credential is discarded afterwards.
-
Discover the guests
NexoVirt imports your existing VMs, LXCs, storage and networks. They keep running the whole time.
-
Assign ownership
Assign a VM or container to a customer from the panel or the REST API. Internal guests stay admin-only.
-
The customer signs in
Power, an in-browser console, SSH keys, 2FA and metrics, scoped to their servers. No Proxmox credentials, ever.
Which Proxmox self-service portals can adopt a running cluster?
How the main options compare for putting a customer portal on an already-running Proxmox cluster.
| Capability | NexoVirt | P3 Portal | WHMCS + ModulesGarden | PVMSS | Paymenter |
|---|---|---|---|---|---|
| Adopt existing (running) VMs | Yes, core use case | Yes | Yes, import into a product | Limited | Unclear |
| KVM / QEMU | Yes | Yes | Yes | Yes | Yes |
| LXC containers | Yes | Yes | Yes | Varies | Not yet |
| Customer self-service portal | Yes | Yes | Yes, via WHMCS | Yes, basic | Yes, simpler |
| IPAM, NAT and port forwarding | Built in | Yes | Add-ons | Basic | Limited |
| Plans / quotas | Yes, auto-enforced | Yes | Yes | Yes | Yes |
| Billing and invoicing | Yes, built-in shop or via API | No | Yes, full | No | Yes |
| REST API | Yes | Yes | WHMCS / module APIs | Yes | Yes |
| Self-hosted | Yes | Yes | Yes | Yes | Yes |
| Open source | No | Depends on edition | No | Yes | Core only |
| White-label | Paid plans | Depends on edition | Yes | DIY | Limited |
Compiled from each project's public documentation as a high-level guide, not an endorsement. Verify current capabilities with each vendor before you decide. NexoVirt and P3 Portal treat adopting an existing cluster as a first-class feature. Choose WHMCS + ModulesGarden or Paymenter when you need built-in billing today.
What does each customer get?
A clean portal for the servers you assigned, checked on the server against ownership before anything reaches Proxmox.
- Start, stop, shut down, reboot and reinstall
- In-browser console (xterm.js serial and noVNC), proxied, no Proxmox access
- SSH key management and root password reset
- Live CPU, RAM, disk and network metrics
- Their allocated IPv4 and IPv6 addresses
- TOTP two-factor authentication and an activity log
Three things to know upfront
So nothing surprises you after the install.
-
Billing built in or through the API
The built-in shop takes Stripe and PayPal payments and writes VAT invoices. Or keep WHMCS, Blesta, FossBilling or your own tooling and drive provisioning through the REST API.
-
Free on 2 nodes, then flat plans
Community Edition includes the customer portal on up to 2 nodes. Larger clusters, white-label and team features come with paid plans from €29/month, never per VM or customer.
-
A small, removable agent
The host agent runs a fixed, validated set of jobs (never arbitrary commands) and can be removed in one click, leaving Proxmox untouched.
Existing cluster FAQ
Can I add a customer portal to an existing Proxmox cluster without rebuilding my VMs?
Yes. NexoVirt is designed to adopt a running Proxmox environment. Point it at your nodes and it discovers your existing VMs, LXCs, storage and networks and imports them into its inventory while they keep running, with no reinstall and no migration.
How do I assign an existing VM or container to a customer?
Pick the guest and set its owner, from the panel or the REST API. Ownership is enforced server-side on every read and action, so a customer only ever sees and controls the guests you assigned to them, never anyone else's.
Do customers get Proxmox credentials or access to the Proxmox web UI?
No. Customers use a scoped self-service portal only: power controls, an in-browser console (proxied through NexoVirt), SSH keys, 2FA and metrics. They never receive Proxmox credentials and never touch the Proxmox GUI.
How does NexoVirt compare to P3 Portal, WHMCS + ModulesGarden, PVMSS or Paymenter?
NexoVirt and P3 Portal both adopt existing guests and are Proxmox-native control planes without built-in billing. WHMCS + ModulesGarden adds full billing and can import a VM into a product, at the cost of a commercial billing stack. PVMSS is open-source and VM-focused; Paymenter is billing-first but currently KVM-only. See the comparison table above.
What about billing?
NexoVirt is a control plane, not a billing system yet. Provision through its REST API and wire it to WHMCS, Blesta, FossBilling or your own scripts; the plans engine handles resource limits, expiry and suspension. A native billing integration is on the roadmap.
Is the customer portal included in the free edition?
Yes. The Community Edition (free, up to 2 Proxmox nodes) includes the customer portal. Paid plans add more nodes, white-label branding and team features; they are flat monthly plans, never priced per VM or per customer.
Start running NexoVirt today
Free for homelabs with unlimited VMs on up to 2 nodes. Running a hosting business? Upgrade in place when you grow, no migration.