Ground Control is a web console for virtual machines across Proxmox VE and Xen Orchestra. Instead of jumping between multiple panels, operators use one dashboard to check health, restart machines, and open terminals.
My role
Lead Architect & Engineer
I designed and built the system from prototypes in 2025 through handover in 2026:
- Built the FastAPI backend with task workers and PostgreSQL.
- Built the Vue 3 frontend for search and inventory tables.
- Created an adapter layer to map hypervisor APIs to common actions.
- Added resource graphs over WebSockets and browser terminals with noVNC.
- Wrote runbooks and handed the platform to the operations team.
Why I built this
Managing multiple hypervisors is tedious. Rebooting a server means remembering which cluster hosts it and logging into that panel. Different interfaces make routine maintenance slow.
Ground Control adds a management layer across those systems. It queries hypervisor APIs and syncs inventory in the background, giving operators one dashboard for routine tasks.
Pluggable provider architecture
The system needed to stay independent of the underlying hypervisor. Teams often run Proxmox in some environments and Xen in others, or migrate over time.
Ground Control handles this with an adapter pattern:
- Lifecycle interface: Each driver implements basic actions to read state, trigger reboots, and fetch inventory.
- Capabilities: Platforms support different features. Drivers declare what they support (such as snapshots or serial consoles), and the UI enables those buttons.
- Shared model: Search, permissions, and audit logs only use normalized records. Supporting a new hypervisor means writing one driver, without changing API routes or pages.
- Drivers: Shipped with drivers for Proxmox VE (REST API) and Xen Orchestra (JSON-RPC over WebSockets).
Architecture
Technical trade-offs and alternatives
Teams managing multiple hypervisors usually consider three options:
- Vendor panels (Proxmox VE, Xen Orchestra) work well on one cluster. Across clusters, operators need separate logins and lack a shared activity log.
- Cloud platforms (OpenStack) offer orchestration, but require daemons on each node and message brokers to maintain. The operational cost is high for small to mid-sized setups.
- Infrastructure as Code (Terraform) works well for provisioning. It is not built for day-to-day tasks like watching metrics or opening consoles.
Ground Control acts as a proxy. It uses existing hypervisor APIs for daily operations without installing software on the servers.
Agentless
Ground Control uses existing REST and JSON-RPC APIs. Leaving host machines untouched prevents upgrade friction and avoids background daemons on hypervisors.
Day-2 operations
Instead of replacing provisioning tools, Ground Control focuses on daily upkeep: cluster-wide search, CPU metrics, and browser shells for troubleshooting.
Central access
Instead of sharing root accounts across web panels, teams use one dashboard with role permissions, quotas, and audit logs.
Management console
The interface uses dark mode and keyboard navigation for maintenance tasks.

Workload inventory
Operators can search and manage virtual machines across clusters without checking where each runs.

Quotas and self-service
Teams can check compute and storage usage against assigned quotas and request capacity when needed.

Telemetry and web console
Operators can view resource graphs and open terminal sessions in the browser.

Project status
Ground Control was built in 2025 and handed to the operations team in early 2026.