Still switching between vSphere Client and your cloud console? CloudVista syncs your full on-premises vCenter inventory — VMs, ESXi hosts, clusters, datastores — on the same dashboard as AWS, Azure, OCI, and GCP. No agents. No complex setup.
Start Free (Team Plan) View Live DemoThe cloud-first narrative is compelling, but reality is messier. Most organisations with more than 5 years of history still run significant workloads on-premises — often on VMware vSphere / vCenter environments that represent years of capital investment and are unlikely to be fully migrated to the cloud any time soon.
The result: infrastructure teams manage two completely separate worlds. The cloud side has visibility (AWS Cost Explorer, Azure Monitor, OCI Console). The on-premises side has the vSphere Client — a powerful tool, but completely disconnected from cloud operations.
CloudVista closes this gap. By connecting to vCenter with a read-only service account, your full on-premises vSphere inventory appears in the same dashboard as your cloud resources — same search, same filters, same health checks, same sync schedule. No separate tool, no manual exports.
CloudVista uses the VMware vSphere Web Services API (SOAP-based) — the same API that VMware's own management tools use. Connection is made from CloudVista's backend to your vCenter server over HTTPS on port 443.
Requirements:
What CloudVista does NOT require:
CloudVista syncs 10 VMware vSphere resource types:
All VMs — powered on, off, and suspended — with full configuration metadata.
Physical hosts with CPU, memory, version, and connection state.
HA / DRS configuration, aggregate capacity, host and VM count.
VMFS, NFS, and vSAN datastores with capacity and free space %.
vCenter datacenter objects as the top-level organisational unit.
DVS configuration and port group membership.
VLAN configuration, port binding, connected VMs.
CPU and memory reservations, limits, and shares.
Template inventory — OS, hardware configuration, library location.
Standard vSwitch port groups and VLAN assignments.
CloudVista collects detailed metadata for each vSphere resource type, surfaced in the inventory view and resource detail pages:
| Resource Type | Key Metadata Fields |
|---|---|
| Virtual Machine | Power state, vCPU count, memory (MB), guest OS, VMware Tools status, primary IP address, MAC addresses, host name, cluster, datastores, snapshot count, VM hardware version, disk size (GB), creation date |
| ESXi Host | Connection state (connected/disconnected/notResponding), power state, CPU model, CPU MHz, core count, thread count, memory (MB), ESXi version, ESXi build number, cluster membership, datacenter, VM count |
| Compute Cluster | HA enabled, DRS enabled, DRS mode (fully automated/partially automated/manual), total CPU MHz, total memory MB, host count, VM count, datacenter |
| Datastore | Datastore type (VMFS/NFS/vSAN), capacity (GB), free space (GB), free percentage, accessible status, URL/path, connected host count, VM count |
| Distributed Virtual Switch | DVS version, port group count, connected host count, uplink configuration |
CloudVista runs automatic health checks against vSphere resources on every sync, surfacing issues in the same health dashboard as your cloud provider resources.
Health check results feed into the unified health dashboard alongside cloud provider health checks — giving you a single view of what's unhealthy across your entire infrastructure.
Yes. CloudVista connects to your vCenter server via a read-only service account and syncs your full vSphere inventory — VMs, ESXi hosts, clusters, datastores, distributed virtual switches — on the same schedule as your cloud providers. No agent installation required.
CloudVista discovers: Virtual Machines, ESXi Hosts, Compute Clusters, Datastores, Distributed Virtual Switches, Distributed Port Groups, Datacenters, Resource Pools, VM Templates, and Standard Networks — 10 resource types in total.
Yes — CloudVista connects via the vCenter API. A vCenter server is required. Direct ESXi host connection without vCenter is not currently supported. vCenter 6.5 and later (including 7.x and 8.x) are supported.
VMware vSphere is available from the Team plan (£99/month) onwards. The free tier covers cloud providers (AWS, Azure, OCI, GCP) only.
VMware vSphere appears as a fifth platform in CloudVista alongside the cloud providers. Resources are displayed in the same inventory view, health checks run on the same schedule, and topology maps include on-premises resources. The main difference is that billing/cost data is estimated based on configurable on-premises cost rates rather than pulled from a provider billing API.
Yes — CloudVista's vSphere integration is compatible with vCenter Server 6.5, 6.7, 7.0, and 8.0. vSphere with Tanzu workload domains are discovered as standard compute resources. Kubernetes-specific Tanzu resources (pods, namespaces) are on the roadmap.
Stop running two separate tools for cloud and on-premises. CloudVista unifies your VMware vSphere environment with AWS, Azure, OCI, and GCP in one dashboard — set up in under 5 minutes.
Start Free — Team PlanAlso see: Multi-Cloud Inventory · Cloud Asset Inventory Guide · Pricing