vSphere vs ESXi vs vCenter: What Each One Does

This is the reference our VMware vSphere support team uses to explain the naming: vSphere, ESXi, and vCenter are three different things that VMware documentation and licensing use inconsistently. This page defines each one, shows how they fit together, lists current versions and lifecycle dates, and covers what changed in the editions after the Broadcom acquisition.

vSphere vs ESXi vs vCenter: definitions

The short version: ESXi is the engine, vCenter is the control tower, and vSphere is the name on the box. When someone says "we run vSphere," they mean ESXi hosts managed by vCenter under a vSphere license.

How ESXi and vCenter fit together

A single ESXi host works standalone. You install it on a server, connect to its Host Client web interface, and create VMs — no vCenter required. This is a common setup for a lab, a branch office, or a single-application server.

vCenter becomes involved when there is more than one host. It inventories the hosts, pools their capacity into clusters, and coordinates the features a single host cannot provide on its own:

• vMotion — live migration of a running VM between hosts
• High Availability (HA) — automatic VM restart on a surviving host after a host failure
• Distributed Resource Scheduler (DRS) — automated VM placement and load balancing across a cluster
• Distributed switches — network configuration managed centrally rather than per host
• Lifecycle Manager — coordinated patching and upgrades across all hosts

Each ESXi host runs an agent (vpxa) that vCenter communicates with. If vCenter goes down, the hosts and their VMs keep running — you lose central management and DRS, not workloads. HA restart also continues to function, because HA logic runs on the hosts themselves once configured.

Current versions

Two vSphere generations are in general support as of August 2026:

Version 9.0 shipped on June 17, 2025 as part of VMware vSphere Foundation 9.0 and VMware Cloud Foundation 9.0. Two naming changes arrived with it: the hypervisor is called ESX again (dropping the "i" that distinguished the thin ESXi from the old ESX with its service console, retired in 2010 — history on Wikipedia's VMware ESX entry), and version numbers across ESX, vCenter, and VCF are unified at 9.x. Details are in Broadcom's vSphere with VCF 9.0 FAQ and the VCF 9.0 release notes on Broadcom TechDocs. A full build-by-build list is in our ESXi versions reference.

Editions after the Broadcom restructure

The edition lineup that existed for over a decade — vSphere Standard and vSphere Enterprise Plus as perpetual licenses — is gone. After Broadcom acquired VMware in late 2023, the portfolio was cut to subscription bundles:

The practical consequence: an organization that only wants the hypervisor and vCenter now buys VVF at minimum, and vSphere 9.0 features are only delivered through VVF 9.0 or VCF 9.0. Environments on vSphere 8 with legacy Standard or Enterprise Plus subscriptions can run them until term end, but renewal paths lead to the VVF/VCF bundles. This pricing shift is the main reason migration assessments off VMware have become routine work; our note on VMware licensing changes covers the cost mechanics.

Lifecycle dates to plan around

• October 2, 2025 — vSphere 7.0 end of general support (passed). Remaining 7.x estates are running unpatched.
• October 11, 2027 — vSphere 8.0 end of general support. This is the deadline that forces a decision: move to VCF/VVF 9.x subscriptions, or migrate off the platform.
• October 11, 2029 — vSphere 8.0 end of technical guidance (no patches after 2027; guidance-only assistance until this date).

Because vSphere 8 is the last generation obtainable under the legacy editions, the 2027 date is effectively also the end of the pre-Broadcom licensing model for supported production use.

When you need vCenter and when standalone ESXi is enough

Standalone ESXi is sufficient when:

• One host, or a small number of hosts that do not need to act as a cluster
• VM downtime during host maintenance is acceptable (no vMotion without vCenter)
• Manual per-host patching via the command line or Host Client is workable
• No requirement for HA restart, DRS balancing, or centralized alarms

vCenter is required when:

• Two or more hosts should behave as one resource pool
• VMs must survive a host failure automatically (HA) or move without downtime (vMotion)
• vSAN, distributed switches, host profiles, or Lifecycle Manager image-based patching are in scope
• Backup software, monitoring, or automation integrates via the vCenter API — most enterprise tooling assumes vCenter, not raw host endpoints

Under the current bundles this is less of a buying decision than it used to be: VVF and VCF both include vCenter, so the question is architectural (do you deploy it) rather than commercial (do you license it). For larger estates, platform design questions — cluster sizing, vSAN vs external storage, stretched clusters — fall under our virtualization infrastructure support practice.

FAQ

Is vSphere the same as ESXi?

No. ESXi is the hypervisor installed on the physical server. vSphere is the commercial suite that contains ESXi and vCenter. Every vSphere deployment contains ESXi; ESXi can exist without the rest of vSphere.

Is vCenter a hypervisor?

No. vCenter runs no VMs itself. It is a management appliance — itself a VM — that controls ESXi hosts and provides cluster features.

What happened to the ESXi name?

With version 9.0 (June 2025), Broadcom renamed ESXi back to ESX and aligned version numbers across ESX, vCenter, and VMware Cloud Foundation at 9.x. Documentation for 8.x and earlier continues to say ESXi.

Can I still buy vSphere Standard or Enterprise Plus?

No. Both legacy editions have been withdrawn from sale (vSphere Standard end of sale was July 31, 2025), and vSphere 9.0 was never released under them. New purchases are VMware vSphere Foundation (VVF) or VMware Cloud Foundation (VCF) subscriptions.

Is vSphere 7 still supported?

No. General support ended October 2, 2025. vSphere 8.0 remains in general support until October 11, 2027.