// VCF JSON Builder

VCF JSON Builder

Build and validate your VCF deployment JSON in real time. Start fresh or import an existing spec — export a ready-to-run payload for the VCF Installer the moment you're done.

VCF 9.0.2 Real-time validation Dynamic ESX host list NSX 3-node cluster SDDC Manager VCF Operations Import existing JSON
Pre-flight spec builder. Generate and validate your deployment JSON before running the VCF Installer. Passwords are masked in the preview — the exported file contains the full payload.
Your data stays on your device. All information entered here — including passwords, IP addresses, and hostnames — is stored only in your browser. No data is sent to any VirtualBytes server.
Import existing JSON
Drop a VCF installer JSON file here or click to browse
— or —
Environment Planner
Enter your naming convention, domain, and IP scheme once — every hostname, VLAN, subnet, and port group is pre-filled automatically
Pre-fill all fields
Naming & Identity
Drives all names: datacenter, cluster, DVS, pool, instance
Appended to every FQDN
Prefix only — the tool appends the number and prefix, e.g. esx → esx01-m01, esx02-m01, …
Hosts
VCF requires a minimum of 4 for production, 3 for PoC
Applied to all build version fields
Networking — IP Ranges & VLANs
Gateway assumed at .1
Gateway assumed at .1
Gateway assumed at .1
Gateway assumed at .1
NSX host tunnel endpoints (.11–.40 pool)
Preview — what will be generated
Fill in the fields above to see a preview of what will be generated.
Passwords and SSL thumbprints are never generated — you must enter those manually
SDDC Instance name, workflow type, version
DNS & NTP Nameservers and time sources
Nameservers
NTP Servers
Cluster & Datacenter vSphere inventory names
CEIP Customer Experience Improvement Program
ESX Host Inventory 0 hosts configured
Retrieving the SSL Thumbprint
From your workstation:
openssl s_client -connect <hostname>:443 2>/dev/null | openssl x509 -fingerprint -sha256 -noout
From the ESX shell directly: openssl x509 -in /etc/vmware/ssl/rui.crt -fingerprint -sha256 -noout
Global Password Apply one password to all appliances at once
Set a single root/admin password that will be applied to vCenter, SDDC Manager, NSX Managers, VCF Operations, Fleet Management, and Collector. You can still override individual passwords after applying.
vCenter Server Deployment configuration and credentials
Credentials
SDDC Manager Management plane credentials
Credentials
Distributed Virtual Switch VDS name, uplinks, transport zones
vmnic → Uplink Mapping
NSX Uplink Teaming Policy
NSX Overlay Transport Zone
Network Segments VLAN IDs, subnets, gateways, port groups
NSX Manager Cluster 3-node cluster · hostname and credentials per node
Cluster VIP & Sizing
NSX Shared Credentials Root, admin, and audit passwords applied to all managers
TEP & Transport Overlay TEP pool, transport VLAN
TEP IP Range
Storage Type Select the principal storage for the management domain
ESA Options
VCF Operations 3-node cluster — master, replica, data
Fleet Management VCF Operations Fleet Management appliance
Operations Collector Remote collector appliance
VCF Operations Collector is always deployed as Small
VCF Automation Optional post-deployment component — requires successful VCF base deployment
Include VCF Automation in this deployment
VCF Automation has post-deployment prerequisites. It requires a completed and healthy VCF base deployment before it can be configured. Disable to exclude it from the JSON spec.
VCF Automation is deployed as a 3-node cluster on the VM Management network. Each node requires a dedicated IP address, plus one additional IP reserved for upgrades. All 4 IPs must be pre-allocated and reachable before deployment.
Used to name cluster nodes internally
Cluster Node IP Addresses
Primary cluster node
Secondary cluster node
Tertiary cluster node
Reserved for rolling upgrades — keep unused
Internal Cluster Network
Internal pod network — must not overlap any production range
Credentials
JSON Preview
Validation —
Done