A customer self-service portal for your existing Proxmox cluster
Already running Proxmox VE? NexoVirt adopts your existing VMs and LXCs in place, no rebuild, no migration, and gives each customer a scoped portal for the servers you assign to them. Proxmox stays your backend; customers never see it.
Adopt what you already run
Most Proxmox portals assume the panel provisioned the VM in the first place, so bolting one onto a live cluster means reprovisioning working servers. That is not an option when customers are already on them.
NexoVirt is built the other way around: you point it at your existing nodes and it discovers your running VMs, containers, storage and networks and imports them into its inventory. Your guests keep running the whole time. You then assign each one to a customer, and they get a clean self-service portal, while the Proxmox configuration underneath stays exactly as it is.
From running cluster to customer portal
Four steps, and nothing gets reinstalled.
Add your hosts
Connect each Proxmox host. A one-time SSH step onboards a small host agent; the credential is discarded after.
Auto-discover guests
NexoVirt imports your existing VMs, LXCs, storage and networks. They keep running, no reinstall, no migration.
Assign ownership
Assign a VM or container to a customer, from the panel or the REST API. Keep internal guests admin-only.
Customer signs in
Power, in-browser console, SSH keys, 2FA and metrics, scoped to their servers. No Proxmox credentials, ever.
Proxmox self-service portals, compared
How the main options stack up 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 & port-forwarding | Built in | Yes | Add-ons | Basic | Limited |
| Plans / quotas | Yes, auto-enforced | Yes | Yes | Yes | Yes |
| Billing & invoicing | Via API / roadmap | No | Yes, full | No | Yes |
| Clean 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 | Enterprise | Depends on edition | Yes | DIY | Limited |
Comparison compiled from each project's public documentation and is a high-level guide, not an endorsement; verify current capabilities with each vendor before you decide. NexoVirt and P3 Portal are the two that treat adopting an existing cluster as a first-class feature. Choose WHMCS + ModulesGarden or Paymenter when you need built-in billing today.
What each customer gets
Every read and action is checked server-side against ownership before it reaches Proxmox, so a customer can only ever touch the guests you assigned them, never another tenant's, and never yours.
Two things to know upfront
Billing. NexoVirt is a control plane, not a billing engine (yet). If you charge customers, drive provisioning through the REST API and keep your billing in WHMCS, Blesta, FossBilling or your own tooling; the plans engine handles resource limits, expiry and suspension. Native billing is on the roadmap.
Licensing. Community Edition is free (up to 2 nodes) and ideal for evaluation, labs and internal infrastructure. Offering the customer portal to external paying customers, plus white-label and larger node counts, is part of Enterprise. See pricing.
A small host agent is installed on each Proxmox node over a one-time SSH step. It runs a fixed, validated set of jobs (never arbitrary commands) and can be removed in one click, leaving your Proxmox setup untouched.
Frequently asked questions
Free Community Edition
Point it at your existing cluster
Add a host, let NexoVirt adopt your running guests, and assign your first customer, without touching a single VM. Free up to 2 nodes.