Test the restore.
Qualify the actual backend, snapshot and backup path. Check restored application data and retain the build, driver and upstream package versions used.
VICTOR RESOURCES / STATUS
A clear direction. An honest starting point.
Victor is in alpha (pre-1.0) and moving quickly. This page separates what ships from what still needs evidence and what is planned, so you can plan an evaluation around facts.
Alpha · Capability and evidence update: 19 October 2026 · Requirements vary by build01 / STATUS BOARD
Shipped, conditional, planned.#
Available means implemented in the Alpha product; it does not mean every backend, topology and failure mode is accepted. Planned work is not a current capability. Check your actual build and prerequisites.
Available 8
In the product today
- Victor virtualization and optional Kubernetes VMsInventory, lifecycle, consoles, templates, Classic and Victor views
- Placement, DRS, capacityRules, DRS modes, overcommit and change windows
- HA with fencingBMC, Ceph, NFS and watchdog fencing; admission control
- Backup and restoreCommunity full backups; Enterprise incremental, immutable, instant recovery
- Security & Compliance CenterNIST-mapped checks, signed evidence, audit chain
- Federation (Enterprise)Inventory, tasks, events, alarms and actions across sites
- AutomationAPI, victorctl, Terraform, Ansible, MCP
- Air-gap deliverySigned bundle, Zarf package, offline Host ISO
Validate first 7
Shipped, with limited evidence
- VMware sources and cold migrationProven against a vCenter simulator; real vCenter 7/8 and ESXi unverified
- virt-v2v and Windows migrationTested with stand-ins; Windows conversion not yet run end to end
- Hardware and multi-host operationInstalled single-host KVM testing is underway; broad hardware, physical failover and independent storage-domain acceptance remain open
- HA on shared storagePartly exercised on a three-member Ceph lab
- Federation over WANTested with simulated sites on one host
- OVN networks and NFS datastoresNested-lab or not yet lab-run
- SIEM formatsCEF and LEEF samples not yet validated in vendor parsers
Planned 8
Not available; no dates promised
- Warm migrationChanged-block pre-copy, migration reports, OVA/OVF import
- Migration plan wizardPlans are created with victorctl or Terraform today
- Cross-site VM moveUse backup and restore between sites for now
- Custom alarms and SNMPThe default alarm pack is tunable today
- Cloud service expansionFirst-class public/reserved IPs, rDNS, tenant DNS, customer-facing S3 and autoscaling
- Provider and regional operationsCommercial billing, payments, multi-region control and managed services
- Victor Cloud EnterpriseMany sites, approvals, budgets and billing
- UI translationsGerman, French, Spanish and Japanese
02 / HOW WE TEST
Evidence comes with a scope.#
Installed single-host tests exercise real KVM workloads and public interfaces. Nested KubeVirt labs and simulated scale runs add different evidence. A local pass does not prove physical failover, production scale, WAN behavior or a supported hardware matrix.
The vSphere bridge has a generated conformance suite against pinned versions of govc, PowerCLI, Packer and the Terraform vSphere provider.
| Result | Conditions |
|---|---|
| Change to UI p95 0.21–0.38 s at 5,000 VMs | Simulated engine, shared 16-vCPU node |
| ISO to Victor sign-in in about 3–4 minutes | Nested virtualization |
| Database failover back in 16–30 s | k3d, 13 waves, nothing sent twice |
| Bridge: 141 checks pass (Community), 227 (Enterprise) | Generated suite, pinned clients |
03 / DATA-SAFETY NOTES
Make recovery part of the evaluation.#
All products are Alpha. Use non-production workloads, the selected build’s known issues and a tested backup. These areas need explicit evidence:
Use independent hosts.
A nested cluster or two appliances on one machine cannot establish physical-host HA. Verify fencing, storage access and the observed recovery on the topology you intend to run.
Separate boot from conversion.
Successful Windows installation is different from converting an existing VMware guest. Verify the specific image, drivers, guest tools, disk growth and application behavior you need.
FAQ
Maturity questions.#
Should we run production on Victor today?
We do not recommend production workloads during Alpha. Start with representative hardware and non-critical workloads, using this page and the selected build’s documentation. We will tell you plainly what has and has not been proven for your scenario. #
How often does this page change?
Whenever a release changes an edition boundary, a status or a known issue. The reviewed revision is shown at the top. #
Can we see the plan?
The product plan and known issues are in the documentation repository, which may require access. Ask in a demo and we will walk through the parts that matter to you. #
NEXT STEP
Plan an evaluation with us.
We will help you pick the hardware, workloads and tests that answer your questions.