Keep workloads placed and available
Rules, DRS, overcommit, fencing, admission control, restart priority and change windows.
Placement & HAVICTOR PRODUCT / PLATFORM
Your enterprise virtualization platform.
Run your virtual machines with compute, storage and networking managed together. Victor brings provisioning, availability, protection, monitoring and access control into one operating experience, with APIs for the workflows your team automates.
Alpha · Community unless marked · Runtime and topology prerequisites apply01 / PRODUCT AREAS
Everything a VM needs, in one place.#
Select an area to see the real screen and the specifics. Operations, protection, security and automation have their own pages.
Inventory
Datacenters, KVM clusters, KubeVirt pools, hosts, VMs, datastores, networks and folders in one tree with four views: hosts and clusters, VMs and templates, storage, and networking.
- Stable object IDs that are never reused.
- Permissions on every object; tags, folders and notes on VMs.
- RVTools-style export to XLSX or CSV, limited to what the caller may see.
VM lifecycle
Create from a template or ISO, power, suspend, snapshot, clone, live-migrate, relocate storage, edit hardware, boot once and delete. Every VM operation is a durable task.
- Disk snapshots quiesced through guest tools, or memory snapshots on KVM clusters.
- Hot-add vCPU and memory where the engine supports it.
- Linked clones on supported datastore drivers (off by default).
Console & guest
Open a graphical or serial console in the browser. Victor Guest Tools, a signed offline ISO of VirtIO drivers and agents, report the guest OS, addresses and heartbeat.
- SPICE on KVM clusters, VNC on KubeVirt, serial on both.
- One-time, session-bound console tickets; console use is audited.
- Tools status: running, not running, outdated or not installed.
Templates & media
Publish a VM as a template, keep golden images in the library, and upload ISOs with resumable uploads.
- Templates are the engine’s own images: image aliases on KVM clusters, CDI DataSources on KubeVirt.
- Media library for installer ISOs.
- Cloud-init for Linux customization.
Networking & IPAM
Bridge, macvlan (VLAN) and OVN networks on KVM clusters, Multus networks on KubeVirt, IP pools with transactional allocation, and network ACLs as per-VM firewalls.
- IP addresses allocated on create, with conflict detection.
- ACLs on bridge and OVN networks of KVM clusters; refused on KubeVirt.
- No distributed switches, NetBox or Infoblox sync today.
Storage
Datastores are storage pools on KVM clusters or Kubernetes storage classes on KubeVirt. Move a VM’s disks between them, live where the engine can.
- Directory, ZFS, btrfs, LVM thin, Ceph and shared LVM on KVM clusters.
- Ceph setup on Victor Hosts from three hosts.
- NFS datastores through shared LVM or the NFS CSI driver.
Monitoring
Performance history kept for 13 months (charts cover up to 7 days today), 17 default alarm definitions, events, a health advisor and forwarding to your tools.
- Webhook, email, syslog (CEF, LEEF, JSON) and Grafana Loki.
- Splunk HEC forwarding in Enterprise.
- Custom alarm definitions and SNMP are planned.
02 / TASKS AND REFUSALS
Every change is a task you can follow.#
Inventory changes go through one action interface. Each becomes a durable task with steps and progress that survives a control-plane failover, and each is recorded in the audit log.
When an action cannot run, Victor says why: a maintenance window, a placement rule, insufficient headroom or an engine limit. You can override a change window by giving a reason, which is audited too.
- Retries with the same request ID return the original task
- Recent tasks docked at the bottom in the Classic view, behind a Tasks button in the Victor view
- Watch tasks live through the API
EVENTSVICTOR ENTERPRISE
03 / GO DEEPER
Pick the part you need to trust.#
Back up and restore
Targets, jobs and restore points in Community; incremental, encrypted, immutable and instant recovery in Enterprise.
Backup & recoveryControl and prove access
Roles, SSO, two-factor, a hash-chained audit log and the Security & Compliance Center.
Security & complianceDrive it from code
API, victorctl, Terraform, Ansible and MCP, under the same permissions as the console.
API & automationKnow what owns what
victord, PostgreSQL, the engines, Victor Host and the appliance.
ArchitectureSee all 46 screens
Filter by area and switch between the Classic and Victor console views.
Product tour04 / FAQ
A few useful distinctions.#
Does every action work the same on both engines?
No, and Victor does not pretend otherwise. Each engine reports its capabilities. Network ACLs, and the Enterprise test boots and instant recovery, work on KVM clusters only today; KubeVirt gets VNC consoles and Multus networks. A refused action names the engine limit. #
Is there a content library like vCenter’s?
Victor has templates and a media library for ISOs. There is no separate Content Library product, and the vSphere bridge maps content-library reads to Victor templates and images. #
Can I change a VM’s memory while it runs?
You can add vCPUs and memory on both engines where supported. Lowering memory needs a power-off on both. #
Is there a hardware compatibility list?
No formal list. Any x86-64 or arm64 server that Linux KVM runs on can be a host. Victor Host needs an x86-64-v2 machine with hardware virtualization, 2 cores, 8 GB of memory and a 64 GB disk at minimum. #
NEXT STEP
See Victor with your environment in mind.
Tell us what you run today. We will show you the workflows that matter to your team.