VMware Satellite
Discover the virtual machines across your VMware vSphere and ESXi estate using the native govmomi integration — securely and read-only.
VMware vSphere / ESXi
VMware resources brought into the CMDB
- Virtual machines across vSphere & standalone ESXi
- Their identity, configuration & status
- Each VM rolled into the CMDB as a managed asset
- Performance metrics for those virtual machines
- On-premise and public-cloud VMware deployments
- Gathered via the native govmomi vSphere API integration — never the VMs directly
Deploy alongside your vSphere or ESXi server
Run the VMware Satellite as a Docker container or install it on any supported Linux host — ideally within the same network as your vSphere or ESXi server, so all data stays inside the customer’s network boundary.
Docker image
Pull the public CMDB-360 VMware Satellite image from Docker Hub and run it on any host that already has Docker installed.
Universal Installer
Install on any Oracle Linux 8/9 or Ubuntu 20.04/22.04 host (ARM or x86_64) with the graphical Installer or the non-interactive AutoInstaller for scripted setups.
We recommend deploying the Satellite within the same IP space as your vSphere or ESXi server so sensitive data stays inside the customer’s network boundary — though it can run anywhere that can reach vCenter/ESXi and has outbound access to the Base Station. Minimum footprint: 1 vCPU, 4 GB RAM, 10 GB disk. It needs outbound access to the vSphere API on 443/tcp and to the Base Station; no inbound ports are required.
A simple two-step setup
When you deploy with the Installer or AutoInstaller, configuration is handled for you. Otherwise the on-instance tools walk you through two steps.
1 · Connect to the Base Station
Using the AdminTool, point the Satellite at your MSP’s CMDB-360 Base Station with its URL and the unique access token issued for the Satellite. These are held in an encrypted config.yml, then services are restarted.
2 · Connect to VMware
Run the ConfigTool and enter your VMware host IP or FQDN and a read-only VMware user and password. The Satellite connects to vSphere or ESXi through the vSphere API using govmomi and begins discovery.
The Satellite needs only read-only access to VMware and must be able to reach the vSphere API on port 443/tcp. You can disable discovery of any resource type — or turn off the on-demand detail channel entirely — from the Satellite scheduler, so it only ever sees what you choose to expose.
How the VMware Satellite protects data
The VMware Satellite runs inside the customer’s network and never touches the virtual machines directly — it gathers details through the native govmomi vSphere API client and sends non-sensitive rosters to the CMDB-360 Base Station. Detailed information is streamed on demand and only while a user is viewing a record, so nothing proprietary is stored outside the environment.