Know where a VM fits
VM/host groups and rules, DRS from manual to fully automated, and overcommit ratios with headroom you set.
Placement & DRSVICTOR / HYPERVISOR PLATFORM ALPHACOMMUNITY + ENTERPRISE
Your hypervisor. Under control.
Victor is a KVM-based hypervisor platform built for enterprise workloads. Run Linux and Windows virtual machines, protect your data and manage your infrastructure from one console.
Victor is in alpha and actively being built. We are looking for hardware partners and teams who want to test it. Screens are from a simulated Victor Enterprise estate.
VIRTUAL MACHINE / SUMMARYVICTOR ENTERPRISE
How Victor fits together.
VICTOR / ENTERPRISE / CLOUD01 / VIRTUALIZATION
Run the workloads.
Provision Linux and Windows VMs. Set CPU, memory, storage and networking, then manage the complete VM lifecycle.
COMPUTE · STORAGE · NETWORKING02 / CONTROLOperate the estate.
Inventory, placement, DRS, HA, capacity, tasks and permissions in one operator view.
PLACEMENT · HA · TASKS03 / ASSURANCEKnow what happened.
Backups, a hash-chained audit log and signed evidence help teams prepare for failure and inspect the result.
RECOVERY · EVIDENCE04 / SELF-SERVICEGive teams their cloud.
Publish images, sizes and networks. Teams provision through Victor Cloud’s portal, API and automation.
PROJECTS · OFFERINGS · APIThe foundation stays complete. Capabilities depend on edition and configuration.Choose an install path
A DAY IN THE CONSOLE
Follow one VM from inventory to evidence.#
Select a stage. Each one shows the real screen and the specifics behind it. Edition differences are called out where they first matter.
Find it
Start from one tree of datacenters, KVM clusters, KubeVirt pools, hosts, datastores and networks. Search or run a command from anywhere with the palette.
- KVM virtual machines and KubeVirt VMs in one inventory.
- Stable IDs and permissions on every object; tags, folders and notes on VMs.
- Export the inventory as an RVTools-style spreadsheet.
Create it
The new-VM wizard places the workload, applies a template or ISO, sets hardware and cloud-init, and shows the exact call it will send before it runs.
- UEFI with Secure Boot by default on KVM clusters.
- IP addresses allocated from IPAM pools on create.
- The same request is available through the API, victorctl and Terraform.
Run it
Power, console, snapshots, live migration, hardware changes and scheduled tasks live on the VM, with recent tasks a click away (docked below in the Classic view).
- Graphical and serial browser consoles, where supported by the backend.
- Hot-add vCPUs and memory where the engine supports it.
- Victor Guest Tools report guest OS, addresses and heartbeat.
Place it
Placement rules, DRS and capacity settings decide where a VM fits. A migration dialog shows each destination’s demand and any rule it would break.
- Keep-together, separate, must and should rules.
- DRS modes from off to fully automated, with a threshold.
- CPU and memory overcommit per cluster; provisioning limits and warnings per datastore.
Protect it
On KVM clusters, HA fences a failed host before restarting its VMs elsewhere. Scheduled backups put restore points on the VM itself.
- Fencing by BMC (Redfish or IPMI), Ceph blocklist, Linux NFS export or watchdog.
- Full scheduled backups to S3, NFS, a directory or SFTP in Community.
- Enterprise adds incremental, encrypted, verified and immutable points.
Prove it
Every VM operation is a task and every change is an audit event. The Security & Compliance Center scores posture and exports a signed evidence package.
- Hash-chained audit log with signed checkpoints.
- Checks mapped to NIST SP 800-53 controls. Not a certification.
- Evidence verifies offline with victorctl.
FAMILIAR ON DAY ONE
Keep the layout your team knows. Or don’t.#
Victor ships two console presentations of the same product. Classic follows the vSphere Client layout. Victor is roomier and brand-forward. Each person can choose, in light or dark.
ONE CONSOLE, TWO PRESENTATIONS
Both views and both themes are in Community. Administrators set the default view; each person can pick their own view from the account menu and their theme from the top menu.
DAY TO DAY
The work of running an estate, together.#
Decisions and their results stay in the same place, from placement and capacity to a failed task and the reason it stopped.
Fence, then restart
On KVM clusters, HA fences a failed host (BMC power-off, a storage-write fence or a watchdog reset) before restarting its VMs elsewhere, in priority order.
HA and fencingHonor change windows
Maintenance windows and change freezes refuse disruptive actions outside policy. Users with the override privilege can override, giving a reason that is audited.
Change managementRestore from the VM
Scheduled full backups with retention, restored in place or as a new VM on any cluster. Enterprise adds incremental, encrypted and immutable points, and instant recovery on KVM clusters.
Backup & recoverySee it as it happens
Tasks, events, alarms and performance history kept for 13 months (charts cover up to 7 days today), with a health advisor and syslog, webhook, email or Loki forwarding.
See the monitoring screensSame work, through code
An OpenAPI-described API, victorctl, a Terraform provider, an Ansible collection and an opt-in MCP server, all under the same permissions.
API & automationA PATH FROM VMWARE
Move on your schedule.#
Assess an RVTools export offline or scan vCenter, map networks and storage in a plan, and cold-migrate with BIOS UUID, instance UUID and MAC addresses kept. Community moves one Linux VM per call; Enterprise adds waves, virt-v2v conversion, test boots, cutover and rollback. Windows conversion and real-vCenter exports still need validation.
The vSphere API bridge lets govc, PowerCLI and Terraform scripts keep reading and powering VMs during the transition. Write operations are Enterprise.
See the migration pathMIGRATION PLANSVICTOR ENTERPRISE
ON YOUR SHORTLIST
Choose the comparison that matters.#
Different platforms solve different problems. Start with your operating model, then compare the work your team needs to do.
Victor vs VMware vSphere
Compare Victor and VMware vSphere for enterprise VM operations, availability, protection, automation and migration. Start with the workloads and operational requirements of your estate.
Compare approachesVictor vs Proxmox VE
Compare two KVM-based virtualization platforms: VM operations, availability, storage, backup, automation and self-service cloud.
Compare approachesVictor Cloud vs Hetzner & DigitalOcean
Compare Victor Cloud’s self-service cloud software with provider-operated public clouds. Review servers, storage, networking, automation and who operates the underlying infrastructure.
Compare approachesOPEN CORE
A complete foundation. More for demanding estates.#
Community includes the engines, VM lifecycle, HA, DRS, backup, basic migration, the Security & Compliance Center, air-gap delivery and the API. Enterprise adds what multi-site operations, large VMware exits and regulated environments need.
Run one site, with no host caps.
- KVM and KubeVirt, inventory and VM lifecycle
- HA with fencing, DRS, placement rules and capacity
- Scheduled full backups and restore
- Assessment, plans and single-VM cold migration
- Security & Compliance Center and audit chain
- API, victorctl, Terraform, Ansible and MCP
Scale out, move faster, prove more.
- Federation across independent sites
- Migration waves, virt-v2v, test boot, cutover and rollback
- vSphere bridge write operations
- Incremental, encrypted, immutable backup; instant recovery on KVM clusters
- CAC/PIV, fail-closed audit, DoD preset, Splunk HEC
- OSCAL and STIG exports, signed FIPS-mode builds
STRAIGHT ANSWERS
Questions evaluators ask first.#
What kind of hypervisor platform is Victor?
Victor is a KVM-based virtualization platform. KVM is a Type 1, bare-metal hypervisor integrated into the Linux kernel. Victor brings together host and VM management, storage, networking, availability, backup and automation. Install Victor Host on your servers, or choose a supported deployment for existing infrastructure. Kubernetes VM management is available as an optional capability. #
Can we try it without buying anything?
Yes. Victor Community is Apache-2.0 and complete for one site, with no host or cluster caps. Install the Host ISO, the appliance or the Helm chart. Enterprise workflows are shown in a guided demo. #
Will our VMware automation keep working?
Supported calls will. The vSphere bridge answers selected SOAP and REST calls from govc, PowerCLI, pyVmomi, Ansible and Terraform. Community covers reads and power operations; Enterprise adds documented writes such as clone, reconfigure and snapshot. It is a migration aid, not full vSphere API compatibility. #
Is warm migration available?
Not yet. The current path is cold migration. Warm pre-copy with changed-block tracking, OVA/OVF import and adopt-in-place are planned. Migration has been tested against a vCenter simulator, so validate against your own vCenter before planning a production window. #
How mature is it?
Victor is in alpha and actively being built. It is not yet recommended for production. Performance figures in the docs come from simulated and nested labs, not production hardware. The status page lists what ships, what is conditional and what is planned, and the early access page explains how to test it with us. #
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.