Self-service control for the servers you rent out on Proxmox
vcontrol gives each of your hosting clients a scoped dashboard for their own servers — power actions, snapshots, backups, and firewall rules — while you keep full admin control and nothing new to install on your Proxmox nodes.
web-01
Ubuntu 24.04
db-02
PostgreSQL
backup-worker
Debian 12
Built on
- Talks only to the Proxmox VE REST API
- Nothing installed on your Proxmox nodes
- Argon2id password hashing
- Multi-tenant isolation enforced on every request
Every rented server becomes a support ticket
Without a client-facing portal, even routine actions route through you.
Clients email you to reboot a VM
Every routine action becomes a support ticket, even the ones a client could safely do themselves.
No visibility into what a server is doing
Clients can't see task history, snapshot state, or firewall rules without asking you first.
Proxmox's own UI isn't built for clients
It exposes the whole cluster — not a safe, scoped view of just the servers one client rents.
Everything a client needs, scoped to what they own
Each feature below is real, working software — not a mockup.
Power and lifecycle
Start, shut down, and reboot rented servers, with every action recorded as a real task and audit entry.
Snapshots and backups
Clients create, restore, and delete their own snapshots and backups, with retention policies and protection flags admins control.
Firewall rules and logs
A scoped rule editor and log viewer per server, without exposing cluster-wide firewall configuration.
Admin client management
Create clients, attach existing Proxmox inventory, assign plans and quotas, and manage per-client users.
Live in three steps
- 1
Connect
Point vcontrol at your Proxmox VE cluster's REST API with a scoped API token.
- 2
Attach inventory
Attach existing VMs to the clients who rent them, or create new clients with their own resource pool.
- 3
Hand clients the portal
Clients sign in and manage exactly the servers scoped to them — nothing else in your cluster.
Built with tenant isolation as a first-class requirement
A client can never see, and never gets a permission error that confirms, another client's server. Requests for a server outside a client's scope return a plain 404, matching OWASP API1 (Broken Object Level Authorization) guidance.
- Argon2id password hashing
- Two-factor authentication (TOTP + backup codes)
- Scoped, tested cross-tenant isolation
- SOC 2 — Roadmap
Give your clients a real self-service portal for their Proxmox servers
Talk to us about running vcontrol in front of your own Proxmox VE cluster.