Nexaplane · Proxmox integration
Nexaplane is a multi-tenant cloud orchestration and billing platform for Proxmox Virtual Environment. It runs as one container beside your clusters and drives them over the PVE API — nothing installed on your hypervisors, nothing patched, and a Proxmox upgrade stays an ordinary Proxmox upgrade. On top, it adds what Proxmox does not ship: tenancy, per-tenant networking, self-service provisioning, metered billing and a white-label portal.
Architecture
Shallow where it touches your infrastructure, deep where it touches your business. Everything Nexaplane asks of Proxmox goes through the API Proxmox already publishes; everything your customers see is Nexaplane’s own.
| Integrates with | Proxmox Virtual Environment, over its REST API |
|---|---|
| Installed on hypervisors | Nothing. No agent, no patched package, no repository of ours on any node |
| Where Nexaplane runs | A single lightweight container, inside your management cluster or outside your fleet entirely |
| Workloads | Virtual machines and LXC containers |
| Storage | Your ZFS, Ceph and LVM pools, presented to customers as tiers you name |
| Guests | Cloud images with SSH keys and network configuration injected at create. Windows guests with UEFI and TPM 2.0 |
| Migration | Live, same-cluster, cross-cluster and cross-datacenter, with progress and bandwidth control |
| Scope | Several clusters and standalone nodes, across sites, under one console |
| Existing workloads | Left alone. Nexaplane attaches to the fleet you run rather than replacing it |
| Read-only mode | Nexaplane keeps monitoring a datacenter while making no changes to it |
| Licensing | Per fleet, not per tenant or per customer |
The PVE API
Proxmox is a very good hypervisor manager, and Nexaplane uses it as one. These are the operations sent to your cluster.
Compute
Storage
Movement
The other half
None of this is asked of your hypervisors. It is what turns a fleet into a product.
Tenancy
Every tenant gets an isolated network and a real virtual router of their own — NAT, firewall, VPN, DHCP and DNS — with BGP, OSPF, WireGuard and IKEv2 where their network needs them. Dual-stack IPv4 and IPv6 throughout, load balancers with automatic TLS certificates, and high-availability pairs for both.
Commerce
Plans, quotas, taxes and invoicing are inside the platform. Every resource is metered by the hour, Stripe and PayPal are handled natively, prepaid credits and post-paid invoicing both work, and an account with a zero balance suspends on its own. The MSPs reselling you get a wholesale and a retail price on every line, and invoice their own customers under their own name.
The customer’s side
A self-service portal carrying your logo, product name, colours and support address — and your resellers’ on top of that. Sixteen languages, chosen per person rather than per installation, with Arabic laid out right to left.
Backups you can prove
Policy-driven backups with retention and integrity verification, self-service restore for customers, and recovery rehearsals: a real backup restored into an isolated network, booted, confirmed to have answered, then destroyed. You are left with a date and a boot time instead of an assumption.
Products from hardware
GPUs found across the fleet, grouped by model and turned into sellable flavours with their own capacity and quota weight. Storage tiers you define. Cross-datacenter interconnects sold as a service.
Accountability
An audit trail of every action, per user, and a fleet-wide console showing cluster health, capacity and every customer action in one place — plus the read-only mode for nights when you are working on the fabric yourself.
Scale
A Nexaplane install is not scoped to a cluster. It manages several Proxmox clusters and standalone nodes at once, across datacenters, from one console — which is what makes a second site an expansion rather than a second platform to operate. Tenants can hold networks in more than one of them and reach between them over interconnects, and cross-datacenter disaster recovery is granted as a per-account entitlement rather than being a property of the whole installation.
Licensing follows the same shape: Nexaplane is licensed per fleet, by hypervisor count, not per tenant and not per customer. Adding customers to a cluster you already run costs nothing more.
Developer first
There is no second-class API. Provisioning fleets, changing network rules, wiring billing into your CRM — the same documented REST endpoints the console itself calls.
POST /api/v1/instances
curl -X POST https://cloud.example.com/api/v1/instances \
-H "Authorization: Bearer np_live_9a8b..." \
-H "Content-Type: application/json" \
-d '{
"name": "web-node-01",
"plan": "np-compute-4",
"image": "ubuntu-24.04-lts",
"region": "ca-central-1",
"network": "tenant-prod",
"billing": { "type": "hourly" }
}'
Note what the request does not contain: a node name, a storage identifier, a VMID. Your customers — and your own automation — work in plans, images, regions and networks, and Nexaplane resolves those onto the Proxmox fleet. That indirection is the integration. It is also what lets a VM move between nodes, clusters and datacenters without anything a customer holds becoming wrong.
Adopting it
Nexaplane attaches to the fleet you already operate. Existing virtual machines keep running as they are, on the storage they are on, managed the way you manage them today — and the tenant-facing platform is built beside them. There is no cut-over weekend, no rebuild of the cluster, and no moment where the thing paying your bills depends on something you have not run before.
If you run the edge as well, NuajProtect filters hostile traffic before it reaches the hypervisors, and you can sell that protection as a tier of your own — margin rather than a referral. It is licensed separately and is not included with Nexaplane.
Questions
Next
Point it at real nodes. Ask us for a walkthrough, or for a trial on your own cluster.