web-01QEMU 201
●CPU3%Memory4.2 / 8 GBStorage31 / 64 GBAddress10.0.0.21
Self-hosted Proxmox control
Your infrastructure.
A better control surface.
Nimbus Direct turns Proxmox VE into a focused self-service experience for providers, teams, and customers—without agents, customer credentials, or per-customer resource pools.
The public demo is read-only, so you can explore safely without changing its shared data.
✓Proxmox API only
✓No node agent
✓Open source
MONDAY, AUGUST 19Virtual machines & containers
Connected securelymonitoringLXC 108
●CPU1%Memory1.8 / 4 GBStorage12 / 32 GBAddress10.0.0.28
All systems operationalLive resource status through the official API
OVERVIEWVM
Hello, Liam
Your infrastructure at a glance.
↯Running5 of 6▥Memory18 GB
web-01QEMU 201
●▦▤◴●
QEMU + LXCDirect assignments
RBACPer-resource permissions
API v1Integration ready
DockerStraightforward deployment
One platform, two perspectives
Powerful for operators. Clear for customers.
Nimbus keeps infrastructure operations and customer self-service in one deliberate, permission-aware experience.
FOR OPERATORS
Control without compromise
Connect clusters, create customers, assign individual guests, and operate everything from a single control center.
- Cluster inventory and live operations center
- Direct VM and container assignments
- Maintenance, alerts, email, and support tickets
- Security center, sessions, audit logs, and API keys
FOR CUSTOMERS
Everything needed. Nothing else.
Customers see only their assigned infrastructure and only the tools explicitly permitted by the operator.
- Status, usage, addresses, charts, and tasks
- Permission-aware power and console controls
- Snapshots, ISO files, and safe one-time boot
- Notifications, maintenance notices, and support
Nimbus Direct Panel
A complete control plane for self-hosted infrastructure
Built around the official Proxmox API, Nimbus adds the customer, policy, security, and operational layers a provider needs.
Direct assignment
Assign any existing QEMU VM or LXC container to a customer—even across nodes and clusters. No Proxmox pool per customer.
Server-side authorization
Every action is checked against Nimbus assignments and permissions before Proxmox is contacted.
Hybrid console
Use termproxy for terminals and noVNC for graphical guests through short-lived, narrowly scoped console sessions.
Operations & maintenance
Monitor nodes and storage, track Proxmox tasks, schedule maintenance windows, and temporarily lock risky customer actions.
Account security
Passkeys, TOTP 2FA, recovery codes, session control, invitations, rate limits, security alerts, and detailed audit trails.
API & integrations
Versioned mobile and integration APIs with user-managed keys, grouped scopes, resource restrictions, expiry, and revocation.
Designed around separation
Proxmox stays private. Nimbus becomes the front door.
Proxmox VE
Nimbus uses one least-privilege API service account. Nothing is installed on your nodes.
Nimbus Direct
Assignments, permissions, users, sessions, tasks, and audits live in Nimbus's own database.
Web & mobile users
Users receive a focused Nimbus account—not Proxmox credentials—and see only authorized resources.
AVAILABLE NOW ON THE APP STORE
Nimbus Direct for iPhone
Your infrastructure, always within reach.
The native companion app brings the most important Nimbus workflows to iPhone with a secure, fast, and genuinely mobile interface.
✓Overview, metrics & activity
✓Power, snapshots & ISO tools
✓Secure termproxy & noVNC console
✓Face ID app lock & notifications
✓Support tickets on the go
✓English, German & adaptive themes
Download the app, enter your provider's public HTTPS Nimbus address, and sign in with your existing Nimbus account. No Proxmox login is ever entered into the app.
Deploy the panel
From GitHub to your server in four steps.
Nimbus Direct runs as a hardened Docker service and stores its application database in a persistent Docker volume.
✓Docker + Compose✓Proxmox VE over HTTPS✓A least-privilege API token✓A public HTTPS hostname
Clone Nimbus Direct
Download the current source from the official repository and enter its folder.
git clone https://github.com/eurosatofficial/nimbus-direct.git
cd nimbus-directConfigure the environment
Create your local environment file, generate a strong application secret, and complete the production values.
cp .env.example .env
openssl rand -base64 48Place your Proxmox root CA at secrets/pve-root-ca.pem when the API uses a private certificate authority.
Build, initialize, and start
Use both Compose files so Nimbus can reach the internal Proxmox address while retaining the certificate hostname.
!
Always include both Compose files.The panel publishes only 4173:4173. Omitting compose.internal.yaml can break Proxmox-backed detail routes.
docker compose \
-f compose.yaml \
-f compose.internal.yaml \
build --pull panel
docker compose \
-f compose.yaml \
-f compose.internal.yaml \
run --rm panel node scripts/setup.mjs
docker compose \
-f compose.yaml \
-f compose.internal.yaml \
up -d --build --force-recreate panelConnect Proxmox and assign resources
Put Nimbus behind an HTTPS reverse proxy, sign in, add the cluster, synchronize inventory, and assign individual resources.
Good to know
Built for real self-hosted environments.
Does Nimbus install anything on Proxmox?
No. Nimbus communicates exclusively through the official Proxmox VE API.
Do I need a Proxmox pool for every customer?
No. Nimbus stores direct customer-to-resource assignments in its own database.
Where is the Nimbus database stored?
The standard Docker deployment stores Nimbus data in the persistent nimbus-data volume.
Can customers access Proxmox directly?
No. Customers authenticate to Nimbus and never receive Proxmox credentials.
Is the iPhone app available now?
Yes. Nimbus Direct is available on the App Store.
Is Nimbus Direct open source?
Yes. The panel is published on GitHub under the MIT License.
Ready to begin?
Give your Proxmox infrastructure a better front door.
Explore the public read-only demo or deploy Nimbus Direct and connect your own cluster.