---

Know it will boot. Before you power it on.

GuestKit reads a VM disk while the guest is off — qcow2, VMDK, VHDX, VHD, VDI or raw — through its own pure-Rust engine (NBD or loop mount). There is no appliance daemon and no "power it on and see". It scores first-boot probability 0–100, explains the blockers, and writes a reviewable fix plan.

Fixes are never implicit. Repairs go through a plan you can read, applied with backups and rollback, and the same score drives the CI gate, the signed Cutover Passport, and assured QEMU launch.

Boot-readiness scoring First-boot probability 0–100, the blockers explained, and a reviewable fix plan. The cutover problem	Offline repair Repairs go through a plan you can read, applied with backups and rollback. What you can do	Migration assurance The same score drives the CI gate, the signed Cutover Passport and assured QEMU launch. Quick start
Engine and formats A pure-Rust engine over qcow2, VMDK, VHDX, VHD, VDI and raw, through NBD or loop mount. Platform layout	Suite hand-offs Export with Transiva, convert and deploy with h2kvm, assure with GuestKit, operate on Zorvia or Zeus OS. Who does what	CLI, TUI, web, CI CLI, TUI, QEMU, Python, web console, in-guest agent and a GitHub Action. Run the web stack

---

60-second quick start

# v1.2.5 GitHub Release — crates.io `guestkit` is still 0.3.2
curl -fsSL -O https://github.com/zyvorai/guestkit/releases/download/v1.2.5/guestkit-1.2.5-linux-amd64.tar.gz

guestkit doctor vm.qcow2 --target proxmox --explain
guestkit migrate-plan vm.vmdk --target kvm --export plan.yaml
guestkit passport emit vm.qcow2 --target kvm -o passport.json
guestctl tui vm.qcow2           # Assurance · preview · export
guestkit-qemu plan vm.qcow2 --json   # assurance → QEMU definition

CI gate — same score, no CLI install step:

- uses: zyvorai/guestkit@v1
  with:
    disk: vm.qcow2
    target: kvm
    fail-below: '80'

Targets: kvm · proxmox · qemu · kubevirt · aws · azure · gcp · hyperv. Host needs: Linux with qemu-img, losetup, and qemu-nbd (mount/repair may need root).

Python (v1.1.0+), on PyPI: pip install zyvor-guestkit, then guestkit.run_doctor("vm.qcow2", target="kvm", explain=True). The full quick start, shrink and Python examples: docs/quick-start.md.

---

The cutover problem, solved offline

Every hypervisor exit fails the same way: you discover the disk was broken at 2am, in the cutover window, after power-on. GuestKit reads the disk while the guest is off, scores first-boot probability 0–100, and emits a reviewable fix plan.

  disk.qcow2 / .vmdk / .vhdx / .vhd / .vdi / .raw
                    │
                    ▼
         ┌──────────────────────┐
         │  Pure-Rust engine    │──►  doctor 0–100 + blockers
         │  NBD / loop mount    │──►  migrate-plan YAML
         └──────────────────────┘──►  Passport · repair · CI gate
                    │                 guestkit-qemu (assured launch)
      CLI · TUI · QEMU · Python · Web · Agent · GitHub Action

Export with Transiva (Apache-2.0) → convert & deploy with h2kvm (Zyvor Production License) → assure with GuestKit (Apache-2.0) → operate on Zorvia or Zeus OS. Run and manage VMs with FluxVM. Who does what · h2kvm integration

Why teams switch

Before GuestKit	With GuestKit
“Will it boot?” answered at power-on	Offline doctor score + root-cause chain
guestkit scripts and tribal knowledge	Structured plans, JSON/YAML, CI gates
Surprises on cutover weekend	Hypervisor-aware migrate-plan + day-0 packs
No audit trail MTV / virt-v2v can skip	Signed Cutover Passport
Migration order guessed by hand	fleet wave-plan — dependency-aware waves

The full comparison has four more rows.

---

Open source, Enterprise

Open source — free under Apache-2.0. This repo · personal, lab, and commercial production. Full offline doctor, migrate-plan, repair, fleet, policy · CLI · TUI · Python · self-hosted web/workers.

Enterprise — buy for programs. Same engine — not a locked doctor. Command Center · Portfolio · Assurance · Migration Factory · Passport Authority · OIDC / RBAC / audit · SLA · air-gap · hypervisor exit workshops.

Open source vs Enterprise · Full feature matrix · 30-day Enterprise trial · Pricing

Trial expired or want a guided evaluation? Book a demo or start a 30-day PoC — no email needed. sales@zyvor.dev remains as a fallback.

Documentation

Goal	Document
Docs site	zyvorai.github.io/guestkit
Docs home	docs/README.md · INDEX
DevOps runbooks	docs/devops
Feature guide	guestkit-user-feature-guide.md
h2kvm integration	h2kvm integration
QEMU / VirtIO runtime	qemu-runtime.md
Dump virsh → GuestKit	virsh-to-guestkit.md
Architecture	overview

The complete map, with the changelog and roadmap, is in docs/documentation-map.md.

Go deeper

• Gallery: console screenshots and demo videos — docs/gallery.md.
• Who does what: the suite split and the libvirt/virsh map — docs/who-does-what.md.
• h2kvm integration: docs/h2kvm-at-a-glance.md.
• What you can do: assure, plan, certify, repair, launch — docs/capabilities.md.
• Free web stack (GHCR): docs/web-stack-ghcr.md.
• Open source vs Enterprise: docs/oss-vs-enterprise.md.
• Platform layout: docs/platform-layout.md.
• Repository: docs/repository-layout.md.
• Prerequisites and build: docs/prerequisites-and-build.md; docs/ and this README are authoritative.

---

License

Commercial subscriptions and support: see docs/SUBSCRIPTION-MODEL.md.

Open source (Apache-2.0)

This repository is licensed under the Apache License, Version 2.0. You may use, modify, and run it for personal, lab, and commercial production use at no charge, subject to Apache-2.0 (preserve notices / NOTICE where required). See NOTICE and docs/legal/ where applicable.

Enterprise

Production support, SLAs, and Zyvor Enterprise products are licensed separately. Book a demo, start a 30-day PoC, or see zyvor.dev. Email sales@zyvor.dev as a fallback.