Virtualization (VMs)

Contrixt reads your virtual machines from Proxmox, VMware vCenter and Hyper-V and values them with chargeback prices you set yourself — e.g. €1 per core per month. On-premises resources get a price tag and flow into the application costs.

Chargeback prices

Per connection you define three prices:

Price	Unit
Price per CPU core	€ per core / month
Price per GB RAM	€ per GB RAM / month
Price per GB disk	€ per GB disk / month

Monthly cost of a VM = cores × core price + RAM × RAM price + disk × disk price.

Connecting Proxmox

What you need: an API token with read permissions in Proxmox (the PVEAuditor role is sufficient).

1. Open Administration → Integrations → Proxmox — the wizard shows how to create the token.
2. Enter the Proxmox URL (e.g. https://pve.company.local:8006), API token ID and token secret; for self-signed certificates, enable Accept self-signed certificate.
3. Set the chargeback prices, save, and click Sync now.

Connecting VMware vCenter

What you need: a user with a read-only role in vCenter; Contrixt reads the VM list via the vCenter REST API.

1. Open Administration → Integrations → VMware.
2. Enter the vCenter URL (e.g. https://vcenter.company.local), username and password (option for self-signed certificates available).
3. Set the chargeback prices, save, and click Sync now.

Connecting Hyper-V (push model)

Hyper-V hosts are rarely reachable from the internet — so here a small PowerShell script pushes the VM data to Contrixt:

1. Create the Hyper-V connection in the wizard — you receive an ingest token (visible only once) and the ready-made PowerShell script.
2. Set up the script on the host (or a management server) as a scheduled task, e.g. daily.
3. The script reports name, cores, RAM, disk and state of every VM; Contrixt values them with the chargeback prices.

Rotate token generates a new token at any time — the old one becomes invalid.

Access through the bridge

If your Proxmox or vCenter API is not publicly reachable (typical for on-premises environments behind the company firewall), route the connection through a Contrixt Bridge — a small agent in your network that communicates strictly outbound over port 443. No inbound firewall rule is required.

You choose this in the connection form's Access field group:

• Direct (the cloud reaches the API) — the default when the API is publicly reachable.
• via bridge: <name> — routes the requests through the chosen bridge; the (online) / (offline) suffix shows its current status.

If no bridge has been set up for the tenant yet, a link takes you straight to the setup. See Contrixt Bridge for all details.

How to check that everything works

After the sync, the Virtual machines table lists every VM with cores, RAM, disk, state and cost/month; the last sync time is shown above it. If VMs are missing, check the read permissions of the account or the scheduled task of the Hyper-V script.

Assignment to applications

• Automatic via tag: if a VM carries a tag matching an app tag, it is assigned to the application automatically on sync.
• Manual: assign VMs directly via Map in the VM table or in the application's detail view.

Unassigned VMs remain visibly listed so nothing slips through.