Inspect the API in action.
For Proxmox, use a UEFI OVMF machine with Q35. Use the current signed x86-64 installer, a supported virtual disk path, and a management interface you can reach from your client.
Verify the installer →Evaluation path
Start with a disposable virtual machine if you want to inspect the control plane, or use dedicated hardware when you are ready to evaluate storage, networking, and device paths.
Choose an evaluation path
Cix is alpha software. Keep the first evaluation disposable, preserve console access, and read the current installation boundaries before writing a real disk.
For Proxmox, use a UEFI OVMF machine with Q35. Use the current signed x86-64 installer, a supported virtual disk path, and a management interface you can reach from your client.
Verify the installer →Use a machine with UEFI, console access, documented storage, and a management interface. The installer writes the target disk; treat the installation as destructive to existing data.
Review installation boundaries →After installation, confirm health from a client, inspect boot identity, and create the first image, network, and container through the same API used by the CLI and dashboard.
Run the quickstart →Check the workload, hardware, storage, and recovery boundaries that matter to you. Cix does not claim VM isolation, broad hardware certification, or production readiness yet.
Review current boundaries →Before you commit
A successful boot proves that this image runs on this target. It does not prove every device, workload, or production requirement.