Operate every Proxmox environment from one control plane.
Keep the infrastructure where it is. Give the IT team one place to see capacity, govern access, establish private connectivity, and operate workloads across the estate.
Proxmox works well locally. The operating burden appears when the estate grows.
A cluster at headquarters becomes several clusters across offices, venues, or business units. Each environment has its own endpoint, credentials, inventory, network context, and operating habits. The problem is no longer virtualisation. It is estate-wide control.
From separate management islands to one operator surface.
Every environment is its own island.
- Operators sign into individual Proxmox interfaces.
- Inventory and capacity are reviewed location by location.
- Access and operational practices drift between teams.
- Private reachability is solved separately for every site.
The estate becomes one operating domain.
- Registered instances appear in one organisation inventory.
- Teams use Anchras roles, SSO/OIDC, and scoped API access.
- VM and Kubernetes workflows follow a consistent path.
- Tailscale or Headscale provides the private fabric between sites.
Bring an existing estate under control in four steps.
- 01
Register capacity
Install the lightweight Anchras agent on each supported Proxmox host. Existing infrastructure remains in place.
- 02
Connect the estate
Attach the customer tailnet, use Anchras-managed Tailscale, or use Anchras-hosted Headscale for private reachability.
- 03
Establish access
Map operators into organisations, teams, and roles. Keep provider and workload secrets sealed and scoped.
- 04
Standardise operations
Inspect health and capacity, provision VMs or Kubernetes, deploy applications, and retain the resulting audit trail.
A control plane above the hypervisors.
Anchras coordinates the work that spans environments while Proxmox continues to provide the virtualisation layer underneath.
Estate inventory
See registered instances, provider kind, region, health, hardware capacity, accelerator availability, and VM inventory in one organisation.
Central access model
Use organisation roles, teams, SSO/OIDC, scoped API keys, and KMS-backed secrets instead of distributing broad provider access.
Repeatable workload delivery
Create Proxmox-backed VMs, provision K3s or RKE2 clusters, and deliver curated or customer applications through consistent workflows.
Private network fabric
Give instances, clusters, applications, and operators private identities under the organisation's tailnet policy.
Automation and evidence
Work through the dashboard, CLI, OpenAPI surface, or Terraform resources, with operational and access changes recorded for review.
Anchras does not try to reproduce every Proxmox screen or provider-specific function. Proxmox remains the hypervisor and its native interface remains available for low-level administration. Anchras provides the organisation-wide inventory, policy, networking, workload, automation, and audit layer above it.
Built for estates that have outgrown node-by-node administration.
This blueprint fits multi-site businesses, internal infrastructure teams, managed-service environments, and organisations consolidating independently operated Proxmox capacity. It can begin with a few existing hosts and expand without forcing a greenfield replacement.