FAQ & Documentation

Frequently asked questions.

What teams ask most often before running an assessment.

Full documentation is further down

What is VIA?

VIA (Virtual Infrastructure Analyzer) is downloadable software for VMware infrastructure analysis. You import it as an OVA appliance into your own vSphere environment and run it yourself. The analysis runs entirely inside the appliance, inside your own infrastructure: your data never leaves your network and is never transmitted to MB Tools.

How do I get and install VIA?

You create an account on mbtools.ca. During closed beta, access is granted on approval. From your account, you download the OVA appliance and import it into your vCenter or a standalone ESXi host. A license key, delivered by email, activates the software (no license required up to 100 VMs). Everything runs on infrastructure you control.

Does my data leave my network?

No. VIA runs entirely locally, inside your network. No inventory, configuration, or performance data ever transits through MB Tools or any third party. The report is a file on your machine. See the Security page

Does VIA recommend a destination platform?

No, by design. No platform recommended, no commercial partnership or margin on any destination. See neutrality on Benefits

I'm not migrating, I just want to understand my environment. Is VIA for me?

Yes. VIA serves teams planning a migration just as much as teams staying and optimizing: infrastructure health, right-sizing, operational risks, application dependencies, lock-in detection. Visibility doesn't depend on your decision.

How much does it cost?

The product is currently in closed beta, and during the beta it is free for every participant, whatever the size of the estate. At version 1.0, it will stay free up to 100 VMs per vCenter; above that, a license will be required, with pricing to be disclosed at commercial launch.

What does closed beta mean for me?

The number of seats is limited and access is by request. Beta functionality is representative of the final product.

Can consultants and integrators use VIA at their clients?

Yes. VIA is used in client engagements under the client's license. A referral program with a discount code is in preparation for consultants and integrators, along with a broader partner program. Contact us for details.

How long does an analysis take?

Once the prerequisites are in place (network access, credentials, approvals), a complete assessment typically takes 2 to 3 hours, including the initial configuration. The software connects to vCenter with a read-only service account, collects the required data, scores each VM, and generates all deliverables automatically.

What are the prerequisites for an analysis?

On the technical side: a vSphere/vCenter environment, deploying the VIA appliance (OVA) into your vCenter, a read-only vCenter service account (enough for the L1 infrastructure collection), and network access (appliance to vCenter on 443, your workstation to the appliance on 8443). The optional in-guest passes (L2 and L3), which reach each VM via VMware Tools, additionally require guest credentials. On the organizational side: plan for the approvals and credential gathering your environment requires (deploying an appliance, creating the service account and guest access), which precede the run and vary by organization. Full details in the portal Getting Started guide.
Documentation

The documentation, at a glance.

Deployment guides, WebUI reference, reading the report, security and more. The full documentation lives in the portal, available after sign-in.

The documentation hub in the client portal.
The documentation hub in the client portal.

Guides grouped by theme and kept up to date. Here's the preview.

Open the documentation (portal)
Getting started
  • Getting startedOVA appliance import, read-only vCenter service account, first collection.
  • WebUI referenceThe guided steps: preflight, agentless L1 scan, in-UI configuration and test, L2/L3 scan, report generation.
Using VIA
  • Reading the report16 tabs, per-VM VMCS score, findings traced to their source, EOL crosswalk, component catalog.
  • DeliverablesThe 5 deliverables: HTML, PDF, Excel, architecture diagrams, CSV and JSON export.
  • AnonymizationThe anonymized report produced by default: fields removed, and how to validate the result.
Reference
  • API referenceThe appliance REST API: every web UI action is also available under /api/v1, to script the full workflow.
  • Diagnostic bundlesThe Support and Contribution bundles: exact contents, anonymization by purpose, and how to inspect them before sharing.
  • Third-party noticesThe open-source components embedded in the appliance and their licenses. Full transparency.
Security
  • Security & complianceRead-only access model, network footprint, credential handling, data collected, anonymization, audit log, decommissioning.
Help
  • TroubleshootingCommon connection, permission, and guest-scan issues, and how to resolve them.
  • FAQFrequently asked questions on deployment, collection, security, licensing, and report interpretation.