---
title: "Why I built my own panel for Proxmox | Nucez Software"
url: https://nucez.com/en/blog/proxmox-panel-warum
lang: en
description: "Multiple Proxmox hosts mean multiple logins, a clunky API and a lot of manual work. How that turned into NexoVirt."
alternate_de: https://nucez.com/blog/proxmox-panel-warum
---

# Why I built my own panel for Proxmox

By [Bjarne Fomferra](https://nucez.com/en/about) · 18.06.2026

Proxmox VE is a solid piece of software. It does exactly what it was built for: virtualization on a host or in a cluster. But as soon as multiple clusters are involved, day-to-day work gets tedious.

## [The problem starts with the second host](https://nucez.com/en/projects/nexovirt)

With the first host you don't notice anything. With the second you open a second tab. By the fourth you have a bookmarks bar full of web interfaces, four sessions that expire at different speeds, and no shared view of utilization, backups or free addresses.

On top of that there's the API. It's complete, but it's not pleasant. If you want to automate provisioning, you end up writing your own intermediate layer. At some point I had exactly that intermediate layer lying around three times, in varying quality.

## [What I wanted instead](https://nucez.com/en/projects/nexovirt)

The requirements were short:

- One interface for all hosts, regardless of cluster
- An API you can understand in an afternoon
- Customers can see their own servers, but only their own
- Plans, quotas and expiry should be enforced automatically
- No changes to the existing Proxmox installation

The last point was the most important. A panel that requires a reinstall is worthless in live operation.

## [How it runs today](https://nucez.com/en/projects/nexovirt)

NexoVirt connects via SSH to a lightweight agent and reads out the state of the nodes. The interface shows guests, storage, networks and backups across all clusters. All actions run asynchronously, so the interface doesn't block while a clone is running in the background.

The REST API covers the complete lifecycle. If you like, you can run the panel purely as a view and control everything through automation.

What it has turned into is described in detail on the [project page](https://nucez.com/en/projects/nexovirt).

[Back to the blog](https://nucez.com/en/blog)

Author Bjarne Fomferra IT specialist for application development, owner of Nucez Software

In short

Multiple Proxmox hosts mean multiple logins, a clunky API and a lot of manual work. How that turned into NexoVirt.

Questions about your project?

Send me a short message, I usually reply within one business day.

---

Nucez Software, Bjarne Fomferra, Enger (Germany). Contact: info@nucez.de, https://nucez.com/en/anfrage