# Vrtmv Documentation > Audit-grade Linux migration and parity attestation — capabilities, commands, and concepts. The pages of https://docs.vrtmv.com, in the order of its navigation. Each link is the page's HTML; the note after it is the page's first sentence. ## Start here - [Introduction](https://docs.vrtmv.com/): **Vrtmv reverse-engineers Linux VMs from disk images and produces Ansible roles that rebuild an equivalent workload on a modern target OS — with a signed parity report as output.** ## Concepts - [Architecture](https://docs.vrtmv.com/concepts/architecture.html): Vrtmv is a **client–server** system with three parts. - [The Translation Index](https://docs.vrtmv.com/concepts/translation-index.html): The Translation Index is the curated PostgreSQL database that turns "what is installed on this CentOS 7 box" into "what to install, and how to configure it, on Rocky 9". - [Parity Attestation](https://docs.vrtmv.com/concepts/attestation.html): Attestation is what separates Vrtmv from a package-renaming script. - [Provenance & Confidence](https://docs.vrtmv.com/concepts/provenance-and-confidence.html): Every assertion Vrtmv makes is traceable and graded. ## Guide - [Installation](https://docs.vrtmv.com/guide/installation.html): `vrtmv` is a single self-contained binary. - [Authentication](https://docs.vrtmv.com/guide/authentication.html): Translation lookups (`resolve`, `translate`, `config-paths`, `migrate`, `inventory --resolve`, `readiness`) authenticate to the Vrtmv API with a per-account bearer token. - [Sources: image, root, SSH](https://docs.vrtmv.com/guide/sources.html): Every extraction command (`inventory`, `drift`, `migrate`, and `readiness` per line) accepts a source three ways. - [Quickstart](https://docs.vrtmv.com/guide/quickstart.html): This walks from a cold CentOS 7 image to a migration plan for Rocky 9. - [Use vrtmv with AI](https://docs.vrtmv.com/guide/ai.html): An AI assistant or coding agent can work with vrtmv through the Model Context Protocol (MCP). - [Send findings and questions](https://docs.vrtmv.com/guide/feedback.html): Your account has a channel to the vrtmv engineers. ## Commands - [Commands overview](https://docs.vrtmv.com/commands/overview.html): `vrtmv` is a single binary with these subcommands. - [assess](https://docs.vrtmv.com/commands/assess.html): A first look at a source: its format, OS release, package count, services, and the config and accounts a migration would carry. - [inventory](https://docs.vrtmv.com/commands/inventory.html): Extract the distribution and installed packages from a source. - [resolve](https://docs.vrtmv.com/commands/resolve.html): Map native package names to canonical slugs for a given release, directly against the API. - [translate](https://docs.vrtmv.com/commands/translate.html): Fetch the current translation for canonical packages, from a source release to a target release. - [config-paths](https://docs.vrtmv.com/commands/config-paths.html): Fetch config-path relocation rules for canonical packages, source release → target release. - [drift](https://docs.vrtmv.com/commands/drift.html): Classify `/etc` into the files that actually encode this workload versus vendor-shipped defaults and host-specific noise. - [data](https://docs.vrtmv.com/commands/data.html): Migrate the **payload** — the application data that no package owns and translation therefore cannot carry: uploads, document roots, `/opt` application trees, database files. - [probe](https://docs.vrtmv.com/commands/probe.html): Ask the source a question whose answer depends on its data, and keep the answer so that `verify` can ask a container the same question and compare. - [migrate](https://docs.vrtmv.com/commands/migrate.html): The full pipeline: inventory → resolve → translate → evaluate conditionals → emit an Ansible role plus a JSON attestation. - [verify](https://docs.vrtmv.com/commands/verify.html): Prove a rebuilt target carries what `migrate` promised, against the attestation that run wrote. - [attest-image](https://docs.vrtmv.com/commands/attest-image.html): Check an image you built against the migrate attestation, and sign a statement about that exact image. - [license](https://docs.vrtmv.com/commands/license.html): Seat one or more hosts against your account by fingerprint alone — the lightweight, first-class way to claim instance seats. - [identity](https://docs.vrtmv.com/commands/identity.html): Write an operator instance stamp, `/etc/vrtmv/instance-id`, so a host has its own billing identity. - [cve-scan](https://docs.vrtmv.com/commands/cve-scan.html): Match a source's installed packages against known vendor advisories for its detected release, narrow to the CVEs that are genuinely still unpatched (`installed_version < fixed_version`, using the same family-aware comparator the translation engine uses), and report them. - [patch](https://docs.vrtmv.com/commands/patch.html): Render an Ansible role that bumps exactly the packages a `cve-scan` found still vulnerable to their vendor-fixed version, staying on the same release — no cross-distro translation. - [run](https://docs.vrtmv.com/commands/run.html): `migrate` and `data plan` stay plan-only: they write an Ansible role and attested runbooks, and a human applies them. - [deploy](https://docs.vrtmv.com/commands/deploy.html): Deploy a workload to a namespace on an OpenShift or Kubernetes cluster — either a KubeVirt **VirtualMachine** or a **Deployment + Service**. - [readiness](https://docs.vrtmv.com/commands/readiness.html): Scan many sources and emit an aggregated fleet migration-readiness report. - [remediate](https://docs.vrtmv.com/commands/remediate.html): Walk the refusal clusters in a `readiness` report and record decisions into a resolutions store. - [cluster-migrate](https://docs.vrtmv.com/commands/cluster-migrate.html): Cluster many sources by measured similarity and emit a per-host variance report. - [cluster-verify](https://docs.vrtmv.com/commands/cluster-verify.html): Verify a rebuilt fleet once per class, then borrow the verdict. - [coupled-migrate](https://docs.vrtmv.com/commands/coupled-migrate.html): Treat N coupled nodes as one migration subject. - [container-fleet](https://docs.vrtmv.com/commands/container-fleet.html): Emit one Containerfile per workload for many hosts from a single manifest. - [ui](https://docs.vrtmv.com/commands/ui.html): Launch a local migrate client for a one-shot migrate / preflight from a browser. - [panel](https://docs.vrtmv.com/commands/panel.html): Launch a local operator panel for the assess → plan → verify loop. - [mcp](https://docs.vrtmv.com/commands/mcp.html): Speak Model Context Protocol on stdio so an agent on this host can collaborate with vrtmv. - [auth](https://docs.vrtmv.com/commands/auth.html): Store, show, or clear the local API credentials so the CLI, GUI, and `vrtmv mcp` authenticate without environment variables. ## The Vrtmv API - [API overview](https://docs.vrtmv.com/api/overview.html): The Vrtmv API (`vrtmv-api`) is the authenticated service the client talks to. - [Endpoints](https://docs.vrtmv.com/api/endpoints.html): All routes are under `/v1`. - [Accounts, quota & billing](https://docs.vrtmv.com/api/accounts-and-billing.html): vrtmv bills **one price per distinct instance, per year**. ## Reference - [Supported targets](https://docs.vrtmv.com/reference/targets.html): `migrate` and `readiness` take a target as a compact spec — a distribution name followed by a major version, with no separator. - [Container base images](https://docs.vrtmv.com/reference/container-base-images.html): When `migrate --format container` emits a `Containerfile`, the `FROM` line is not a guess. - [Container output: scope, checks and base images](https://docs.vrtmv.com/reference/container-output.html): `vrtmv migrate --format container` writes a `Containerfile` for one workload taken from a source host. - [Containerize as-is: --preserve](https://docs.vrtmv.com/reference/containerize-as-is.html): `vrtmv migrate --format container` builds an image by installing the target distribution's packages. - [Scripts and agents](https://docs.vrtmv.com/reference/scripting.html): What a script, a CI job or an AI agent driving `vrtmv` can rely on: JSON on stdout, no prompt it cannot answer, and an exit code that says what happened. - [Security posture](https://docs.vrtmv.com/reference/security.html): Vrtmv is built for regulated environments. - [The beta channel (retired)](https://docs.vrtmv.com/reference/beta-channel.html): Vrtmv retired the beta channel on 2 October 2026.