Skip to content

vsfleet documentation

vsfleet inspects VMware vSphere inventory across named vCenter contexts. Use the terminal UI to browse live data, or the CLI to diagnose connections, capture assessments, and query stored history on Linux, macOS, or Windows.

vsfleet never powers VMs on or off, changes networks, provisions resources, manages snapshots, or deletes inventory objects. Estate-wide operations keep healthy results when another vCenter fails.

vsfleet demo command and startup animation, a connection form preview, VM details and timeline, network wiring and policies, vApp members, and estate-wide search

Start here

Install vsfleet, then try the sample estate:

vsfleet demo

The demo uses synthetic inventory and five in-memory history captures. It needs no vCenter, configuration, or credentials, makes no network connections, and writes no state. Screens are marked DEMO · SAMPLE DATA.

Task Guide
Install and connect your first vCenter Getting started
Browse live inventory and diagnose failures Terminal UI, Troubleshooting
Configure credentials, routes, and TLS Configuration
Find commands, filters, output formats, and exit codes CLI reference
Schedule captures in CI, systemd, Docker, or Kubernetes Recipes, Containers

Work with assessments

vsfleet capture run --all-contexts --label q3-audit
vsfleet export rvtools --file estate.xlsx

Captures are stored locally in SQLite. Queries and exports read captured evidence without contacting vCenter; missing collection coverage remains visible in the output.

Task Guide
Capture, compare, retain, and recover inventory history Assessments
Review health findings and orphan-disk evidence Health
Collect and interpret CPU and memory history Performance
Export XLSX/CSV or check RVTools file interoperability Exports
Review migration readiness and destination sizing Planning
Report on tags and custom attributes Metadata
Share a scoped or pseudonymized workbook Sharing
Capture license metadata without license keys Licensing

Contribute

Read Architecture for data flow and design boundaries, Testing for verification, and Synthetic testbed for offline UI development. Writing documentation explains where to put new material and how to keep it concise.

Releases · Source and issues · Contributing · Security

vsfleet is a personal open-source project, not an official Dell Technologies product, and is not sponsored, endorsed, or supported by Dell Technologies. Export interoperability was independently implemented without RVTools source code or non-public documentation. RVTools is a Dell Technologies product; references here describe export-file interoperability only.