Compute operations
Management paths for Proxmox virtual machines and Linux containers.
Infrastructure management software
Homelab
Control Plane
An API-first FastAPI system I built to issue real management operations, observe their progress, and provide a safer interface to Proxmox compute and hosted services.
01 · Problem
Operations were scattered across layers
Running virtual machines, containers, Linux services, game servers, backups, and monitoring meant moving between infrastructure consoles and service-specific tools. Common operations needed one controlled path without hiding the state of the underlying systems.
This is operational software: user actions cross an API boundary, call infrastructure or service integrations, and affect actual workloads.
I built the FastAPI control plane, Proxmox API integration, VM and LXC management, Linux service operations, Minecraft server management, backup controls, task monitoring, role-based access, RCON integration, and the deployment and testing workflow.
Service operations
Common Linux and Minecraft service actions exposed through consistent application boundaries.
Access and feedback
Role-based capabilities and task visibility around actions that can change running systems.
Operational signals
Prometheus and Grafana complement control-plane state with infrastructure monitoring.
The control plane creates a deliberate boundary between a user and systems with very different APIs and operational behavior.
Request path — no private addresses or host details shown
Clients
BrowserOperator interface
API clientStructured requests
FastAPI control plane
Role checksControl permitted actions
Operation routingNormalize service boundaries
Task monitoringExpose operation state
Integrations → resources
Proxmox APIVMs + LXCs
Linux servicesHosted workloads
RCONMinecraft servers
Backup operationsProtected state
PrometheusMetrics
GrafanaVisibility
01Request
02Authorize
03Execute
04Observe
API-first boundary
Infrastructure and service operations are represented as application capabilities rather than direct access to each underlying system.
Keep task state visible
Infrastructure actions are not treated like instant UI changes. Task monitoring keeps the operator informed about work performed by integrated systems.
Separate capabilities by role
Role-based access limits which operations a user can initiate instead of treating every authenticated user as an infrastructure administrator.
Use the right control surface
Proxmox API calls manage compute, service integrations manage hosted workloads, and RCON provides game-server-specific control without collapsing those boundaries.
Pair control with observation
Prometheus and Grafana provide operational context beyond whether a command was accepted.
A control plane has to account for authorization, partial availability, long-running infrastructure tasks, and services with different management interfaces.
The deployment and testing workflow supports changes to software that operates persistent Linux services and running workloads. The portfolio intentionally describes the boundaries without publishing credentials, tokens, private addresses, hostnames, or detailed network topology.
The source and infrastructure are private. The diagram shows system responsibilities, not sensitive implementation or network details.
06 · Engineering result
Software as an operational interface.
The project brings backend development and infrastructure engineering together: API design, authorization, third-party integrations, task visibility, service control, monitoring, deployment, and responsibility for the systems on the other side of every action.