Skip to content
PolyVirt

The assessment is free. It stays free.

All 48 checks, the wave plan and every export, with no account and no upload. Paid tiers are planned and not built — this page says what they would cover, and what would have to be true for them to be worth paying for.

What you get today

Free, and not a trial of anything

The analyser parses your export in your own browser. We never receive the file, so there is no storage to pay for and nothing to meter. That is why this is free rather than free-for-now: there is no cost we are absorbing until you convert.

  • All 48 checks

    43 of them run against a complete RVTools 4.x export. The rest are listed with the reason they cannot.

  • Unlimited runs

    No account, no per-seat limit, no cap on environments.

  • The full wave plan

    Every VM placed in a migration wave, blockers grouped by the decision they need.

  • CSV and JSON export

    Per-VM and complete, for the client deliverable.

  • Commercial use

    Including inside work you bill for.

  • No upload, ever

    Verifiable in your network tab, or with the tab disconnected.

Try it free

Planned, not built

What a paid tier would be for

None of this exists yet. It is written here in the conditional because that is the honest tense for it — there is no waiting list, no beta, and no price.

  • Multi-environment comparison

    One view across every estate you look after, so a consultancy or an MSP can see all of them at once rather than one report at a time.

  • Scheduled re-assessment

    The same export run again on a schedule, with the difference called out — what was remediated, what regressed, what appeared since last month.

  • vCenter-connected checks

    A read-only collector run against vCenter directly, which reaches the four checks below that no RVTools export can answer.

The four checks an export cannot answer

What a vCenter connection would add

These are already in the report. Every run lists them under “checks that did not run”, with the reason, because a check that could not run is not a check that passed. They are the clearest thing a paid tier would fix, and the same list is on the checks reference for free.

  • Blocker

    vGPU and GPU passthrough

    RVTools exports no PCI passthrough or vGPU profile data on any sheet. A GPU-attached VM is a genuine migration blocker, and an export cannot see one.

    vgpu_or_gpu_passthrough · would read VirtualMachine.config.hardware.device

  • Medium

    USB, serial and parallel passthrough

    There is no USB, serial or parallel port sheet in an export, so host-attached devices are invisible.

    device_passthrough · would read config.hardware.device

  • Low

    DRS affinity rule membership

    Cluster-level DRS settings are in vCluster, but which VMs an affinity rule actually names is not exported.

    drs_rules_present · would read ClusterComputeResource.configurationEx.rule

  • Low

    Custom NUMA topology

    No NUMA node count is exported. vCPU.Sockets is a different thing, and using it would be inventing a check rather than running one.

    custom_numa_topology · would read config.extraConfig numa.* keys

Design partners

What the paid tiers are actually waiting on

Not engineering time. Evidence. A wave plan is only worth something if it matches what an experienced person would have sequenced by hand, and we cannot check that from synthetic estates — the sample on this site is generated, and we say so on the page that offers it.

So: a small number of design partners, and an exchange with obligations on both sides rather than a waiting list.

What you do

  • Send one sanitised RVTools export from an engagement you have actually scoped.
  • Read the wave plan it produces and tell us where it is wrong — which findings you would have raised differently, and which VMs you would have sequenced elsewhere.
  • One call a month while the paid tiers are being built. Thirty minutes.

What you get

  • The paid tiers free for a year from the day they exist.
  • The checks your environments need get built before the ones they do not.
  • Your name stays out of everything unless you ask otherwise. We are after the correction, not a logo.

Who this is for

People who scope VMware migrations for a living — consultants, MSP engineers, and infrastructure teams moving an estate they are personally accountable for. If you have never had to defend a wave plan to someone whose weekend depends on it, this is not aimed at you, and the free analyser is the whole product as far as you are concerned.

Email us about it

Goes to hello@polyvirt.com. There is no form here and no address is collected anywhere on this site — if you write to us, we have your address because you sent us mail.

FAQ

Questions about cost

Is the risk assessment going to start charging later?

No. The analysis you can run today stays free, including commercially. It runs entirely in your browser on your machine, so it costs us nothing per run — there is no bill for us to pass on. Paid tiers, when they exist, will be for work that needs a server: storing your uploads to compare over time, and connecting to vCenter.

What do the paid tiers cost?

We do not know yet, and quoting a number for something unbuilt is how this page went wrong the first time. It will be published here before anything is charged for.

Do I need an account?

No, and there is no form on this site to create one. The analyser takes a file and gives you a report. Nothing is uploaded and no address is collected anywhere.

What does “sanitised” mean for a design-partner export?

Whatever your client agreement requires. RVTools exports carry VM names, hostnames, IP addresses and annotations. Rename or strip anything you cannot share — the checks read configuration, not identity, so an export with every name replaced still produces the same findings.

Can I use the free reports in client deliverables?

Yes. Use them internally, share them with your clients, put them in your own documentation. There is no per-seat limit and no cap on how many environments you analyse.