Up and running in three steps

From a fresh install to handing customers their own portal.

  1. 1

    Connect a host

    Point NexoVirt at an existing, running Proxmox VE host, freshly installed or already in production. A discovery agent SSHes in, scans the setup, and imports your existing VMs, containers, storage and networks.

  2. 2

    Manage everything

    Create, reinstall, power and console into guests, watch live metrics, and automate with the REST API.

  3. 3

    Hand over a portal

    Give customers a slim, role-scoped portal for only the guests they own, without the Proxmox learning curve.

Architecture

How NexoVirt fits together

The Panel drives your Proxmox node and the agent, and together they run and provision every guest.

NexoVirt Panel
Control plane
Admin UI
manage every host
REST API
automate it all
Customer portal
self-service tenants
2FA & RBAC
secure, scoped access
PVE Node
Proxmox host
Panel calls: PVE API over HTTPS
Runs: your VMs & containers
nexovirt-agent
On every node
Panel calls: provisioning · networking
Drives: guests on the host
VMs & containers
Run by the node · provisioned by the agent
web-01 #101 running LXC
IP: 10.20.0.11
db-01 #102 running VM
IP: 10.20.0.12
cache-1 #103 running LXC
IP: 10.20.0.13

A closer look

What each step actually looks like in the panel.

panel.nexovirt.com · Add & onboard a host
Add & onboard a host in the NexoVirt panel
Step 1

Add & onboard a host

Point NexoVirt at a Proxmox host, fresh or already in production. A one-time SSH bootstrap installs a lightweight agent and pins the host key; the root credential is discarded the moment onboarding finishes.

  • Works with already-running nodes: nothing is reinstalled.
  • Credentials are encrypted at rest; a per-host SSH key is generated and stored securely.
  • A version-pinned agent keeps each host healthy, with one-click updates.
panel.nexovirt.com · Adopt your running guests
Adopt your running guests in the NexoVirt panel
Step 2

Adopt your running guests

The discovery agent scans the node and imports your existing VMs, containers, storage and networks into one panel-wide list, across every host you’ve added.

  • OS, IP, cores, memory and storage detected for every guest.
  • No host-switching: everything you run is in a single searchable list.
  • DB-backed, so the list opens instantly even if a host is briefly unreachable.
panel.nexovirt.com · Provision & manage
Provision & manage in the NexoVirt panel
Step 3

Provision & manage

Create VMs and containers with a step-by-step wizard, then manage each guest from a KVM-style control panel: live charts, an in-browser console, snapshots, backups and reinstall.

  • Create from a plan or custom specs, an OS template, and DHCP or a static IP.
  • Async provisioning returns instantly while a worker does the real work.
  • Live CPU/RAM/disk charts, a serial/noVNC console, and one-click power actions.
panel.nexovirt.com · Hand customers a portal
Hand customers a portal in the NexoVirt panel
Step 4

Hand customers a portal

Assign guest ownership and your customers get a slim, role-scoped portal for only the servers they own, without the Proxmox learning curve. Plans and enforcement make reselling automatic.

  • Customers get a console, SSH keys and 2FA, scoped to their own guests.
  • Plans bundle resources, traffic and expiry; enforcement suspends or resumes automatically.
  • Branded email keeps customers informed on the events that matter.
panel.nexovirt.com · Automate everything
Automate everything in the NexoVirt panel
Step 5

Automate everything

Drive NexoVirt as code. A clean REST API and an OpenTofu/Terraform provider, plus alerting and email, tie it all together.

  • Token-authenticated REST API with a consistent envelope and in-app docs.
  • Manage guests declaratively with the Terraform provider.
  • Alerting via inbox, email and webhooks keeps you ahead of problems.

Under the hood

The mechanics behind the panel: how NexoVirt actually talks to Proxmox.

Discovery & inventory

When you add a host, a lightweight agent SSHes in once, scans the node, and imports your existing VMs, containers, storage and networks. Nothing is reinstalled and nothing is migrated: NexoVirt reads what is already there.

From then on a collector records a snapshot only when a resource actually changes, carrying the last-known IP forward for offline guests. Every page (dashboard, guest list, node views, network map) reads this database, so it opens instantly and keeps working with an "as of" timestamp even when a host is briefly unreachable.

Async provisioning

Create, reinstall, delete and power actions return immediately. The panel writes an optimistic status, queues a job, and a worker runs the real Proxmox call before a targeted refresh swaps in the live state. You never sit on a spinner waiting for Proxmox to finish.

QEMU guests are built from a cloud-init OS-template library: a base image plus native cloud-init for users, SSH keys, IP and more. The qemu-guest-agent snippet is delivered through the host agent, and images are downloaded on demand and cleaned up after use, so nothing lingers on your storage.

Networking, IPAM & firewall

Define IPv4 or IPv6 zones and the panel does the subnet math: it enumerates the CIDR and allocates the next free address transactionally, so the create wizard can hand a guest a static IP or leave it on DHCP.

Give private guests internet access with MASQUERADE and expose them with DNAT port-forwards, applied through a dedicated, fail-closed agent ruleset that only ever touches its own chains and never flushes Proxmox or built-in rules. The panel also reads iptables, nftables, ufw, firewalld and pve-firewall and normalises them into one readable rule model with a NAT map.

Multi-tenant portal & reselling

Assign a guest an owner and that customer gets a slim, role-scoped portal for only the servers they own. Every portal read and action re-checks ownership on the server, so a customer can never reach a guest that is not theirs.

Plans bundle cores, memory, disk, traffic and expiry, and an optional daemon enforces them: suspend on expiry or over-limit, auto-delete after a grace period, auto-resume on the monthly reset. Enterprise adds a reseller hierarchy with per-reseller quotas and white-label branding, so you can hand partners their own slice.

Automation & integration

Everything in the UI is available over a clean REST API: token authentication with per-token IP allow-lists, rate limits and host scoping, a consistent response envelope, and in-app documentation. The full guest lifecycle is drivable end to end.

Manage NexoVirt as code with the OpenTofu / Terraform provider, and wire it into your stack with outbound event webhooks (event to templated JSON to HTTP, signed and retried) and rule-based alerting to an in-panel inbox, email, Discord and Google Chat.

Frequently asked questions

No. NexoVirt sits on top of your existing Proxmox VE hosts. A discovery agent connects over SSH and imports your running VMs, containers, storage and networks into one panel. Nothing is reinstalled and your Proxmox nodes keep running exactly as they are.

No. NexoVirt manages Proxmox through its API and a small on-host agent; it does not replace the Proxmox web UI or reconfigure the hypervisor. You can keep using the Proxmox UI alongside it, and removing NexoVirt leaves the host untouched.

The agent is a lightweight helper installed once over SSH during onboarding. It handles host-side tasks the API cannot do directly, such as staging cloud images, writing cloud-init snippets and applying NAT rules. It communicates over an authenticated job queue and can be removed at any time from the Hosts page.

When you create, reinstall, delete or power a guest, NexoVirt enqueues the job and returns immediately with an optimistic status, then a background worker runs the real Proxmox call and refreshes inventory. You watch progress on a live page instead of waiting on a blocked request, and the guest never flips to an unknown state mid-operation.

Every read and every action in the customer portal is re-checked against guest ownership on the server, so a customer can only ever see or control the servers assigned to them. A single Proxmox cluster safely serves many tenants, and the console proxies through your own origin so Proxmox credentials never reach the browser.

Free Community Edition

Self-hosted, on your infrastructure

Be first to run NexoVirt

Start managing all your Proxmox hosts from one panel.