Get started

Proxmox VE · infrastructure · $29 one-off

The cluster console that asks first.

Nodes, guests, quorum and storage inside QuoxCORE, with lifecycle actions in the same view. Watching is always on. When an agent wants to start, stop or clone a VM, a human gets asked.

QuoxCORE · NOC · Proxmox tab quorum ok
quorum ok · 3 of 3 votes3 nodes · 7 guests · storage 64% used

node-a cpu 31%

vm 101 · api-prodrunning
vm 102 · db-prodrunning

node-b cpu 18%

vm 103 · stagingrunning
ct 204 · web-runnerstopped

node-c cpu 44%

vm 105 · ci-workerrunning
vm 109 · scratchstopped
ct 210 · cacherunning
Illustrative data. On your install the board is fed by your own Proxmox VE cluster over its API.

In plain words

What it is, where it lives, when to reach for it

What is it
A plugin for the QuoxCORE dashboard that manages the VMs and containers in your Proxmox VE cluster.
Where do I use it
On the Proxmox tab in the dashboard's NOC panel, connected to your own cluster's API.
When would I use it
When you want to check node health or restart a VM without opening the Proxmox web console.
How do I use it
Buy it once in the store for $29, then an org admin installs it; risky VM actions wait for human approval.

QuoxCORE is the free, self-hosted platform underneath this. What is QuoxCORE

Natural language

Just say it to CommanderQ.

Every capability on this page is a sentence away, not a form. Say it in plain English inside QuoxCORE chat and CommanderQ resolves it to the right action, at the right permission tier.

You → CommanderQ

“Hey CommanderQ, use my ubuntu clone to build a new VM on the staging server.”

vm.create · staging · from template ubuntu-clone · a write bigger than start/stop, so it's gated · sent to the HITL inbox

The safety model

Power, ranked by how much it can hurt.

Everything the plugin can do sits on one rail. The further right, the more the platform demands before it happens.

The deep behind this page is the cluster itself: a basin of light for each node, your guests orbiting inside, and every action crossing the dark with an evidence trail behind it.

One payment, one licence key pasted into Settings, and the Proxmox tab appears in the NOC panel. No subscription, no per-node fee, ever.

Read · always on

Watch

Cluster overview, quorum status, node health and uptime, with real-time CPU, memory and disk for every guest.

monitoring never needs permission

Write · logged

Act

Lifecycle actions run from the board. Stop and reboot are classed destructive and logged as such, every time.

vm.start · vm.stop · vm.reboot

Gated · approval

Approve

VM lifecycle actions, clones and snapshots made by an agent wait in the HITL inbox until a human approves (or an org admin standing grant covers them), from the first minute after install.

vm.clone · vm.snapshot · vm lifecycle

Freeze · E-STOP

Stop the agent

There is no Proxmox-specific kill switch. The platform-wide E-STOP and DEFCON controls apply to the HYPERION agent that drives these actions.

platform controls

Every write is logged through the platform's audit pipeline and witnessed on the WARD chain, the same record your auditors verify. How Quox governance works →

Or just say it

You → Q

“Hey Q, take a snapshot of nw-ops-console-01 and take a full backup to PBS.”

snapshot taken · nw-ops-console-01 · full backup queued to PBS · a logged write, not a gated one · receipt on WARD

What you get

Six capabilities, one tab.

The whole cluster surface lands in QuoxCORE's NOC panel, where your agents and your monitoring already live.

Cluster

Full overview with quorum status, node health and uptime at a glance.

Guests

VMs and LXC containers listed together, with start, stop and reboot from the same view.

Resources

Real-time CPU, memory and disk per guest, so capacity questions have answers early.

Snapshots

Create snapshots across the cluster, with agent-made snapshots behind the approval gate.

Storage

Pool visibility, usage and capacity flags before they become incidents.

Checks

Schedulable checks from the Proxmox tab, on the cadence you choose.

Doctor

Ask why a VM is slow and get the likely cause, the evidence behind it and a suggested fix. Read-only: it looks, it never changes anything.

Lanes

Pre-approve a lane once: one node, a VMID range, a name prefix and an expiry. HYPERION then clones, boots, runs and destroys throwaway VMs inside it, every command witnessed, revocable at any time.

REQUIRES a Proxmox VE cluster with API access · ROUTE /monitoring/proxmox

The Proxmox tab

The board that lands in your NOC panel.

Nodes, guests, quorum and storage in one view, with the lifecycle actions in the same place you're already watching.

How it installs

The first five minutes.

No download, no daemon, no migration. A licence key unlocks the tab inside your existing QuoxCORE install.

  1. 0:00

    Buy

    $29 in the store. One payment, yours for good, no renewal.

  2. 0:02

    Paste the key

    Drop the licence key into Settings. The Proxmox tab appears in the NOC panel.

  3. 0:04

    Connect the cluster

    Add an API token for your Proxmox VE cluster.

  4. 0:05

    First poll

    Nodes and guests fill the board, and the safety rail is already armed.

FROM MINUTE ONE agent-made VM actions, clones and snapshots are approval-gated, before you ever touch them.

Pricing

The whole bill, itemised.

Plugins are one-off purchases, not subscriptions. Everything a subscription would have kept charging you sits at zero, permanently.

Read the docs →

Proxmox VE · the invoice, forever

Licence · one payment$29
Renewal, ever$0
Per-node fee$0
Per-seat fee$0
Total, for good$29

requires QuoxCORE 1.0+ · requires a Proxmox VE cluster with API access · licence: commercial · version 1.0.0