Tested so far
Installed single-host KVM workloads, Linux and Windows test workflows, nested Kubernetes/KubeVirt labs, and simulated scale tests. Migration has been exercised against a vCenter simulator.
VICTOR RESOURCES / EARLY ACCESS
Victor is in alpha. Build it with us.
We are actively building Victor and looking for two kinds of partners: hardware partners who can help validate it on real servers, storage and networks, and customers who want to test it on their workloads when it is ready.
Alpha · actively in development · not yet for production01 / WHAT ALPHA MEANS
Real software, early evidence.#
Victor runs today: the console, both engines, placement, HA, backup, migration tooling, the vSphere bridge and the Security & Compliance Center all exist in code and are covered by automated tests. Installed single-host KVM testing now complements the simulated and nested labs. Broad hardware coverage, physical multi-host acceptance and production-estate evidence are still open.
Releases are pre-1.0 prereleases. Interfaces can still change between builds, and we do not recommend running production workloads on Victor yet.
See the full status and known limitsNot yet tested
Broad hardware qualification, independent physical multi-host failure and migration, BMC fencing on real hardware, Ceph and SAN at production scale, real vCenter 7 and 8 exports, Windows guest conversion end to end, and federation over real WAN links.
Why that matters to you
The fastest way to close those gaps is on real equipment with real workloads. That is what we are asking partners for.
02 / HARDWARE PARTNERS
Help us prove Victor on real equipment.#
We are looking for server, storage, networking and GPU vendors, resellers and integrators who can provide or host equipment for validation, and work with us on the results.
Host validation
Victor Host installs on x86-64-v2 servers with hardware virtualization. We want to run it across real platforms, firmware and BMCs, including Redfish and IPMI fencing.
Shared storage
Ceph, NFS and SAN through shared LVM are where HA, live migration and fencing are hardest. We want to validate them on production-class storage.
Networks and WAN
Bridge, VLAN and OVN networks on real switching, and federation between sites over real links.
Passthrough
GPU and device passthrough on current accelerators, with placement and maintenance behaviour checked on real hosts.
Victor has no hardware compatibility list today. Validation results from partner hardware are how one will start.
03 / EARLY CUSTOMERS
Test it on your workloads when it is ready.#
We are looking for teams who want to evaluate Victor in a lab or non-production environment and tell us what works and what does not.
Teams planning to leave vSphere
Run the offline assessment on an RVTools export, then move representative VMs from a real vCenter in a lab. Your vCenter versions, guest mix and scripts are exactly the evidence we need.
The current migration pathSites with no internet path
Install from the signed air-gap bundle, review the evidence package with your assessors and tell us what your control set needs that Victor does not show yet.
Public sector and air gapKVM and KubeVirt together
Run classic KVM VMs and KubeVirt VMs side by side under one set of permissions, placement rules and automation, and push on the edges.
How it fits together04 / HOW IT WORKS
Simple, and honest about the stage.#
Tell us who you are and what you would like to test. We will follow up to talk through fit, the current build and what a useful test looks like for your environment.
Sending the form stores your request for the team. It does not create an account, start a trial or commit you to anything.
- Tell us about your environment
Hardware, storage, networks, current platform and what you want to prove.
- Agree a test plan
A small, specific scope: install, a failed host, a restore, a migration of representative VMs.
- Run it together
On your equipment or in your lab, with a direct line to the people building Victor.
- Share what you found
Results feed the known-issues list, the status page and, for hardware partners, the start of a compatibility list.
FAQ
Early access questions.#
Can we run production on Victor today?
We do not recommend it. Victor is in alpha: broad hardware, physical multi-host and real-vCenter acceptance remain open, and interfaces may still change. Use a lab or non-production environment. #
Is there a cost to join early access?
Victor Community is Apache-2.0. Talk to us about Enterprise features for a test; nothing on this page commits you to a purchase. #
Where do we get builds?
Prereleases are built with their source revision and checksums recorded. The source repositories and release downloads are not public yet, so we will arrange access as part of early access. #
When will Victor reach 1.0?
We have not set a date. The status page lists what still needs evidence; partner testing is how those items close. #