Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Accounts, quota & billing

vrtmv bills one price per distinct migrated instance, per year. Analysis is generous — only real migrations count, and re-migrating the same VM never bills twice.

On-Demand is $799 per instance a year, Pro $599 (bought 10 at a time) and Fleet $399 (100 at a time). Each price covers the migration, its signed parity attestation, and ongoing monitoring. There is no separate one-time fee.

What is billable

A usage event is billable-eligible only when all hold:

  • its kind is migration (preflight and readiness checks are always free);
  • the target is not a free target (api.free_target, which is currently empty — every target bills);
  • the account is not on an unlimited plan.

Billing counts distinct VMs by fingerprint, so re-migrating the same VM does not bill twice.

The waterfall

Each account’s position is computed as a waterfall:

  1. Free quota — a number of billable instances included at no charge (10 by default).
  2. Annual subscription — beyond the free quota, each instance is billed at the account’s tier rate, per year, as a single subscription whose quantity tracks the instance count.

GET /v1/account returns this summary — free quota, billable instances, paid instances, the per-instance annual rate and the annual total — which is what an account page renders.

Prepaid credits were retired on 2026-08-07 along with the one-time migration fee, since a credit pre-bought a per-migration charge that no longer exists. The credits_* fields remain in the API response for compatibility and report zero. The ledger is preserved and closed: no new grants can be created. To comp an account, its free quota is raised instead.

Enforcement

  • A non-paying account whose free quota is exhausted is refused a new billable migration with 402 Payment Required.
  • A paying account soft-overages into invoiced on-demand usage rather than being blocked.
  • An absolute hard cap applies to every non-unlimited account: once it reaches the per-account VM limit, further billable migrations are hard-blocked with 402 until the limit is raised. Unlimited accounts (negotiated large estates) are exempt.

Feasibility checks (preflight, readiness) are never gated.

Data boundary

Metering carries only a one-way VM fingerprint and the release pair — never host identity or workload data. See Security posture.