Provider

Proxmox is the first provider supported by DevStation.

The goal is not to replace the Proxmox UI. DevStation sits above it: it reads the topology, prepares a change plan, orchestrates provisioning through the TUI and then uses the provisioned VMs as install targets for services.

Real-time status

Beyond the provisioning cycle, DevStation connects to the Proxmox API to query the real state of the environment: clusters, nodes, VMs, connectivity and basic usage signals. Those reads feed the TUI without forcing you to switch back to the web UI for every check.

Services on VMs

After VMs exist, a station registers services from blueprints. A standalone blueprint, such as k3s, targets specific VMs. A hosted blueprint, such as argocd, runs on top of an already registered service, for example k3s.server.

Flow

1. Store credentials in the local vault.
2. Model the cluster and nodes.
3. Define images and sizes.
4. Create virtual machines with free-form tags.
5. Run plan and apply through the TUI.
6. Create a station, register services from blueprints and install the selected subset.

Transparency

Change plans, decisions and executed steps stay visible. The tool automates the workflow, but does not hide the infrastructure: OpenTofu plan output, blueprint steps, execution logs and service status remain auditable.