The software does not become paid. Buying support is optional and does not change your right to use VMBook free of charge for personal, educational or commercial work.
Deployment and architecture
We can help inventory existing Windows, Linux and macOS computers; identify QEMU, Hyper-V, WSL, libvirt, ESXi and Proxmox ownership; design trusted management paths; and introduce VMBook without forcing an immediate platform migration.
Virtual machine migration
Migration support can cover VMDK, VDI, VHD/VHDX, qcow2 and raw images; firmware and controller mapping; test boots; rollback planning; and validation with application owners. Conversion is performed on copies, with the source preserved until acceptance.
Remote sites, homelabs and data centers
Engagements may include site and host organization, VPN or management-network planning, headless services, certificate verification, backup routes, BMC/Redfish assessment and recovery drills. Work is scoped to the capabilities actually tested in the customer environment.
Integration and custom development
If VMBook needs to fit an existing workflow, we can evaluate API integration, import tools, reporting, packaging, provider support and purpose-built automation. Custom work does not automatically become part of the public VMBook release; ownership, delivery, maintenance and confidentiality must be stated in the service agreement.
Training and operational support
Training can focus on visible QEMU commands, image chains, snapshots versus backups, Windows 11 coexistence with Hyper-V and WSL2, remote-host trust, cross-architecture guests and recovery procedures. Ongoing assistance can be arranged separately when response times, hours or service levels need to be guaranteed.
How an engagement begins
- Describe the hosts, hypervisors, machine count and desired outcome.
- Identify data sensitivity, access rules, downtime and recovery requirements.
- We define scope, deliverables, exclusions, schedule and price in writing.
- Work begins only after both sides accept the separate service agreement.
Contact
Email [email protected] with the subject “Professional services.” Do not send passwords, private keys, tokens or confidential VM images in the first message.

