The Infrastructure Stack Blueprint

Proxmox VE 9 vs VMware vSphere Foundation 9.1.Which hypervisor still makes sense after Broadcom's per-core shift?

Proxmox's per-socket cost is published and calculable, while VMware vSphere Foundation 9.1 is quote-only per core, so the decision hinges on how much VMware tooling you'd have to replace.

Proxmox VE 9 vs VMware vSphere Foundation 9.1: Hypervisor Blueprint

Architectural assessments verify vendor specs, licensing models, HA quorum requirements, and maintenance boundaries.

01 / Architectural stance

Recommended
stack architecture.

Architecture depends on workload & failover SLA

Choose Proxmox VE for new builds, homelabs, and small clusters where a published per-socket price and free ZFS/Ceph matter; keep VMware vSphere Foundation only if your operations depend on vCenter and vSAN and a real per-core quote fits budget. Proxmox's limitation is that support starts with 3 tickets a year at Basic and you own more of the integration work.

Verification standards & sources

02 / Workload sizing matrix

Match compute, storage & NIC topology to load.

Example build (our assumption, not a vendor spec): 1 socket, 8-16 cores, 64 GB RAM, ZFS mirror on two SSDs, 1-2x 2.5GbE NICs

Single-node homelab or edge box

Recommended stack: Proxmox VE (no subscription or Community tier)

The host is the whole failure domain, so HA doesn't apply; ZFS snapshots plus an off-box backup target matter more than clustering.

Example build (our assumption, not a vendor spec): 3 nodes, 2 sockets each, 256 GB RAM per node, Ceph on local NVMe, dedicated 10GbE storage network plus separate management links

Three-node small-business cluster

Recommended stack: Proxmox VE (Basic or Standard tier)

Cost is 6 sockets times the tier price; all nodes must share one subscription level, and losing one node should leave the cluster and Ceph quorum intact.

Keep current hosts and NIC layout; VVF includes 0.25 TiB raw vSAN per licensed core, before redundancy overhead

Existing VMware estate with vSAN and vCenter-dependent tooling

Recommended stack: VMware vSphere Foundation 9.1 (quote required)

Migration risk and retraining can outweigh license savings; confirm perpetual-to-subscription conversion before planning the 9.1 upgrade.

03 / Architectural comparison

HA, storage & operational trade-offs.

Architecture dimensionProxmox VE 9VMware vSphere FoundationOps implication
Licensing metricPer occupied CPU socket per yearPer core, minimum 16 cores per CPUDense CPUs cost the same on Proxmox but raise the VMware bill with every core.
Published priceEUR 120 to EUR 1,100 per socket per yearQuote requiredYou can budget Proxmox from the pricing page; VMware needs a partner quote before any TCO math.
Free usable tierYes, all features without subscriptionNoProxmox lets you pilot production-equivalent features before spending anything.
Included storageZFS and Ceph storage built in (Proxmox VE overview)vSAN at 0.25 TiB raw per licensed core (9.1)VMware storage growth beyond the entitlement means an add-on purchase; Proxmox growth means buying disks.
Current release9.2, released May 21, 20269.1 line (9.1.1 GA Sep 3, 2026)Docs written for Proxmox VE 8 or vSphere 8 are a release behind, so check every doc you read against the version you'll deploy.

04 / Environment fit

Cluster role &
deployment boundaries.

Illustrated Proxmox VE 9 shown on its own
Illustrated Proxmox VE 9 shown on its own

$0 community / €120 per socket subscription

Proxmox VE 9

Open-source KVM/LXC hypervisor with every feature free and optional per-socket support subscriptions. The current release is 9.2, out May 21, 2026, per Proxmox's roadmap. The trade-off is thinner vendor support at lower tiers and more DIY integration.

Production & lab fit
Homelabs, small businesses, and new clusters on high-core, low-socket servers that want ZFS or Ceph without storage licensing.
Avoid this stack when
Your operations, backup vendor, or compliance process is built around vCenter and vSAN, and retraining plus migration would cost more than the VMware renewal.
Illustrated VMware vSphere Foundation shown on its own
Illustrated VMware vSphere Foundation shown on its own

Per-core subscription

VMware vSphere Foundation

Broadcom's per-core subscription bundle for vCenter and vSAN estates. Broadcom's 9.1 licensing model enforces a minimum consumption rule of 16 cores per physical CPU, includes 0.25 TiB of vSAN raw capacity per licensed core, and publishes no list price here, so budget from a partner quote.

Production & lab fit
Existing VMware estates standardized on vCenter, vSAN, and VMware-certified third-party tooling that can absorb a per-core quote.
Avoid this stack when
You're building fresh, run high-core-count servers on a fixed budget, or hold perpetual licenses you don't want to convert to subscription.

05 / Operational realities

Engineering wins
& failure modes.

Illustrated a split image showing Proxmox VE 9 on one side and VMware vSphere Foundation on the other, highlighting contrasting dashboard layouts.
Illustrated a split image showing Proxmox VE 9 on one side and VMware vSphere Foundation on the other, highlighting contrasting dashboard layouts.

Proxmox VE 9

Operational strengths

  • All features usable at $0, without the Enterprise Repository or vendor support
  • Published per-socket pricing from EUR 120 per socket per year regardless of core count
  • ZFS and Ceph supported natively with no capacity entitlement
  • Multi-master clustering and zero-downtime live migration listed on the product page

Failure modes & overhead

  • Enterprise Repository requires a paid subscription
  • Every node in a cluster must use the same subscription level
  • Community tier has no support tickets; Basic includes only 3 per year
  • Standard-tier 24/7 support is scheduled for end of 2026 rather than available now

VMware vSphere Foundation

Operational strengths

  • Preserves existing vCenter workflows and integrates compute, storage virtualization, and VCF management services
  • Runs consumer VMs and containers side by side in a native Kubernetes runtime
  • 0.25 TiB raw vSAN capacity per licensed core, pooled across clusters
  • Starting with version 9.1, supports assigning licenses directly to ESX hosts or vSAN clusters as overrides

Failure modes & overhead

  • No published VVF list price was found, so budget from a partner quote
  • Minimum consumption rule of 16 cores per physical CPU even on smaller CPUs
  • Cost scales with cores, so dense CPUs raise the bill
  • Operates in evaluation mode for up to 90 days unless a valid license is assigned via VCF Operations
  • vSAN capacity beyond the entitlement requires purchasing add-on vSAN capacity

Implementation spec

Configuration & runbook architecture.

Review licensing limits, backup/quorum topology, and Day-2 upgrade maintenance before committing hardware.

If you’re starting fresh or run only a few hosts, Proxmox VE is the safer buy. Its cost is published and charged per socket, and every feature works at $0. Keep VMware vSphere Foundation only if your daily operations depend on vCenter and vSAN and a real per-core quote fits your budget. The biggest caveat is that this guide found no published VVF list price, so any VMware total without a quote is a guess.

This guide draws on vendor documentation and two independent analyses retrieved November 13, 2026. No lab testing or benchmarks were run.

Proxmox VE vs VMware vSphere: The Short Answer

Illustrated two laptops on a table, each displaying the short answer summary comparison of Proxmox VE 9 and VMware vSphere Foundation.
Illustrated two laptops on a table, each displaying the short answer summary comparison of Proxmox VE 9 and VMware vSphere Foundation.

The Proxmox VE vs VMware vSphere question splits cleanly by situation.

Your situationLean towardMain caveat
New homelab or single serverProxmox VE, no subscriptionNo vendor support without a paid tier
New 3-node small-business clusterProxmox VE, Basic or StandardAll nodes need the same tier
Existing VMware estate on vSAN and vCenterVMware vSphere Foundation 9.1Quote-only, cost scales with cores
Existing VMware estate, renewal loomingPilot Proxmox before renewing9.1 uses term-based subscription licensing
Windows-centric shopHyper-V / Azure LocalCore-based Windows licensing
Want a second free option to compareXCP-ngVerify its current docs yourself

Version Check: Proxmox VE 9.2 and vSphere Foundation 9.1

Illustrated a dual-monitor workstation showing Proxmox VE 9.2 release notes and VMware vSphere Foundation 9.1 documentation.
Illustrated a dual-monitor workstation showing Proxmox VE 9.2 release notes and VMware vSphere Foundation 9.1 documentation.

Proxmox VE 9.2 is the current release. It came out on May 21, 2026, according to the Proxmox VE roadmap, with an arm64 build following on August 5, 2026. Independent reporting from datazone.de also puts the current line at 9.x. If you still run 8.x, read our guide to Proxmox VE 8 end of life first.

On the VMware side, Broadcom’s vSphere Foundation overview describes VMware vSphere Foundation as an enterprise-grade workload platform providing intelligent operations management and hyperconverged infrastructure integrating compute and storage virtualization. It adds that VCF management services provide lifecycle management of VCF Operations and license server, plus log analysis, without the cloud management and integrated automation capabilities of VMware Cloud Foundation.

Separately, ecorpit.com’s alternatives roundup frames its comparison around vSphere 8 support ending; check end-of-support dates against Broadcom’s own lifecycle pages before you plan around them.

Does the version matter for this decision? Yes, mainly on the VMware side. The license format changed in 9.1, and vSAN allowances have differed between releases. Quoting one version’s numbers against another version’s product is the most common budgeting mistake here.

Licensing Mechanics: Per-Socket vs Per-Core

Illustrated two server CPUs with text overlays showing per-socket licensing for Proxmox VE and per-core licensing for VMware vSphere.
Illustrated two server CPUs with text overlays showing per-socket licensing for Proxmox VE and per-core licensing for VMware vSphere.

How Proxmox charges

Proxmox VE is fully functional without a subscription. Paid tiers add support and access to the Enterprise Repository. Every tier is priced per occupied physical CPU socket per year, no matter how many cores sit in that socket. That’s per the official pricing page.

TierPrice per socket per yearWhat you get
No subscription$0All features, no Enterprise Repository
CommunityEUR 120Stable updates, Enterprise Repository
BasicEUR 3703 tickets/year, 1 business day response, Proxmox Datacenter Manager
StandardEUR 55010 tickets/year, 4-hour response, remote SSH support, 24/7 support scheduled by end of 2026
PremiumEUR 1,100Unlimited tickets, 2-hour response, 24/7 support from October 19, 2026

The other rule that bites people is tier parity. Every node in a cluster must run the same subscription level. You can’t put Premium on the database node and Community on the rest.

How VMware vSphere Foundation charges

VMware vSphere Foundation is licensed per core via term-based subscriptions. Broadcom’s licensing overview explains that you purchase a term-based subscription and license your environment using the VCF Operations instance that manages it alongside the VCF Business Services console. Assigning a primary license to a vCenter instance automatically licenses connected product components, and starting with 9.1 you can also assign an override license directly to ESX hosts or vSAN clusters.

Licensed cores aren’t always physical cores. Broadcom’s licensing model documentation states that most products enforce a minimum consumption rule of 16 cores per physical CPU, so CPUs with fewer than 16 cores still consume 16 cores. A host with two 8-core CPUs uses 32 cores of license capacity (and 2 hosts with two 8-core CPUs each require 64 cores).

In 9.1, license files (license-<vcfOpsName><timestamp>.lic) downloaded from the VCF Business Services console are added to a license server and assigned in VCF Operations. After installation or upgrade from 8.x to 9.1, components run in evaluation mode for up to 90 days; if a valid license isn’t assigned within 90 days, ESX hosts disconnect from vCenter and new workloads cannot start.

Multiple subscriptions for the same product, unit of measure, and Site ID pool automatically into one default license, allowing capacity growth without juggling separate keys.

Total Cost of Ownership: One Number You Can Calculate, One You Can’t

Illustrated a side-by-side cost comparison chart displayed on a tablet and a laptop, showing calculable and uncalculable total cost of ownership.
Illustrated a side-by-side cost comparison chart displayed on a tablet and a laptop, showing calculable and uncalculable total cost of ownership.

Proxmox licensing cost is sockets times nodes times tier price. You can do it in a shell.

# Proxmox VE annual subscription cost
# Edit these three values for your cluster
NODES=3
SOCKETS_PER_NODE=2
TIER_EUR=120   # 120 Community, 370 Basic, 550 Standard, 1100 Premium
echo "$(( NODES * SOCKETS_PER_NODE * TIER_EUR )) EUR/year"

Expected output for the values above:

720 EUR/year

Swap TIER_EUR and the same 3-node, 6-socket cluster comes to EUR 2,220 on Basic. Standard is EUR 3,300, and Premium is EUR 6,600. Those numbers don’t move if you upgrade from 16-core to 64-core CPUs.

VMware’s number can’t be worked out from public sources. No source reviewed for this guide publishes a VVF per-core list price. The honest formula is licensed cores (at least 16 per CPU) times your quoted per-core rate, plus any vSAN capacity add-on. Get the quote, then plug it in.

Licensing is only part of TCO, on both sides. Budget for these too:

  • Backup software and storage. Proxmox Backup Server has its own per-server subscriptions, starting at €560 a year for Community. VMware shops usually pay a third-party backup vendor.
  • Migration labor. Converting VMs, rewriting automation, and retraining staff costs real hours. For an existing VMware estate, this line can exceed the license savings.
  • Hardware for storage. Ceph wants fast disks and a dedicated network. A 10GbE switch and enterprise SSDs belong in the Proxmox column if you go hyperconverged.
  • Power protection. A UPS for every cluster rack is cheap insurance against a split-brain after an outage, whichever hypervisor you pick.

Storage: ZFS and Ceph vs the VVF 9.1 vSAN Entitlement

Illustrated NAS storage arrays running ZFS and Ceph alongside a VMware vSAN setup in separate rack enclosures.
Illustrated NAS storage arrays running ZFS and Ceph alongside a VMware vSAN setup in separate rack enclosures.

Proxmox VE’s product overview lists HA clustering, live migration, and Ceph or ZFS storage. Its pricing page plans subscription costs by CPU socket, so neither adds a capacity charge. ZFS fits single nodes and small setups, with snapshots and replication. Ceph gives you distributed, clustered storage across nodes. Your capacity limit is the disks you buy.

VMware vSphere Foundation 9.1 includes vSAN, but it’s capped. Broadcom’s add-on licensing documentation states that a VMware vSphere Foundation license includes an entitlement of 0.25 tebibyte (TiB) of vSAN raw capacity per licensed core (so 48 licensed cores yield 12 TiBs, compared with 1 TiB per core in VMware Cloud Foundation). To expand beyond that total, you purchase vSAN add-on capacity.

Here’s what that means for the same 3-node cluster with two 32-core CPUs per host. Each CPU is above Broadcom’s 16-core minimum, so licensed cores equal physical cores here. With CPUs under 16 cores, use 16 per CPU instead.

# VVF 9.1 vSAN raw entitlement: 0.25 TiB per licensed core
NODES=3
SOCKETS_PER_NODE=2
CORES_PER_SOCKET=32
# Broadcom licenses at least 16 cores per CPU
LICENSED_PER_SOCKET=$(( CORES_PER_SOCKET < 16 ? 16 : CORES_PER_SOCKET ))
CORES=$(( NODES * SOCKETS_PER_NODE * LICENSED_PER_SOCKET ))
echo "${CORES} cores -> $(( CORES * 25 / 100 )) TiB raw vSAN entitlement"

Expected output:

192 cores -> 48 TiB raw vSAN entitlement

That 48 TiB is raw. Mirroring or erasure coding eats part of it before you store a single VM.

Don’t mix this up with older docs or VCF quotas. vSphere 8-era licensing used different vSAN allowances and VCF includes 1 TiB per core instead of 0.25 TiB, so check which release and product tier a reseller is quoting from. Broadcom’s licensing model page and add-on licensing guide walk through how primary cores and vSAN TiBs pool across subscriptions.

Live Migration and HA as Each Vendor Documents Them

Illustrated live migration and high availability status screens for Proxmox VE and VMware vSphere shown on two side-by-side monitors.
Illustrated live migration and high availability status screens for Proxmox VE and VMware vSphere shown on two side-by-side monitors.

Proxmox’s product overview lists zero-downtime live migration as a High Availability feature. It also lists multi-master clustering, so there’s no single management node to lose. Dynamic HA balancing uses real-time CRS scheduling. HA maintenance workflows preserve resource state. Proxmox’s pricing FAQ says high availability, live migration, clustering, and other features are available at every subscription level. The tiers differ in support entitlement and Enterprise Repository access, not features.

vSphere Foundation provides compute and storage virtualization alongside intelligent operations management and a native Kubernetes runtime. This guide didn’t verify version-specific vMotion, HA, or DRS limits for 9.1. If a specific migration need drives your decision, read the current vSphere 9.1 docs for it before signing.

Backup Architecture

Illustrated backup architecture diagrams for Proxmox VE and VMware vSphere displayed on printed sheets with a USB backup drive nearby.
Illustrated backup architecture diagrams for Proxmox VE and VMware vSphere displayed on printed sheets with a USB backup drive nearby.

Backup documentation wasn’t independently verified for this guide on either platform. Treat this section as an orientation map, and confirm the specifics against current docs.

On Proxmox, the companion product is Proxmox Backup Server. Its pricing page states that all plans include every Proxmox Backup Server feature and that subscriptions are priced per backup server. Paid support starts at €560 a year per server for Community, so budget it separately from the VE subscription.

On VMware, backup usually runs through third-party tools or VMware’s own data protection add-ons. If your backup vendor’s licensing is tied to VMware, switching hypervisors may mean switching backup products. That cost belongs in the TCO.

Networking and VLAN Trunking

Illustrated a 10GbE network switch with VLAN trunking ports connected to Proxmox and VMware servers in a rack.
Illustrated a 10GbE network switch with VLAN trunking ports connected to Proxmox and VMware servers in a rack.

Both platforms support VLAN-aware virtual networking. That’s as far as the sources reviewed here go. Version-specific trunking setup for the current Proxmox release and for VVF 9.1 wasn’t verified.

So you won’t find step-by-step VLAN instructions here. Read Proxmox’s current network admin guide and VMware’s 9.1 networking docs before you cable anything. Physically, plan separate links for management, VM traffic, and storage on any clustered build. Cat6 Ethernet cable is fine for 1GbE and 2.5GbE. Ceph and vSAN traffic expect dedicated 10GbE.

Workload Sizing and Failure Domains

Illustrated a whiteboard with workload sizing and failure domain diagrams drawn with colored markers in a conference room.
Illustrated a whiteboard with workload sizing and failure domain diagrams drawn with colored markers in a conference room.

The workload decides more than the logo does. Treat these as rough planning envelopes, since vendors don’t publish them as minimums.

Single node (homelab, edge, branch office). Think 1 socket, 8-16 cores, 64 GB RAM, and a ZFS mirror on two SSDs. The host is the entire failure domain. HA can’t help with one host, so off-box backups are your protection. Proxmox at $0 or EUR 120 a year is hard to argue with.

Three-node cluster (small business). Think 2 sockets per node and 256 GB RAM per node, with Ceph on local NVMe. Give storage its own 10GbE network. Losing one node should leave the cluster, and the storage, running on the other two. Proxmox Basic costs EUR 2,220 a year for this shape.

Existing VMware estate. Your failure domains already exist, along with your runbooks. Migration adds its own failure domain. A botched conversion weekend can cost more than a year of subscription. For many shops here, renewing VVF while piloting Proxmox on spare hardware is the low-risk path.

Who Should Buy, Wait, or Skip

Illustrated a decision flowchart printed sheet titled 'Who Should Buy, Wait, or Skip' laid on a desk with eyeglasses and a pen.
Illustrated a decision flowchart printed sheet titled ‘Who Should Buy, Wait, or Skip’ laid on a desk with eyeglasses and a pen.

Proxmox VE

Buy if you’re building new, running high-core CPUs on few sockets, or want Ceph without capacity metering.

Wait if Standard-tier 24/7 support matters to you. Proxmox lists it as scheduled by end of 2026. Premium’s 24/7 support started October 19, 2026, so it’s shipping now, at EUR 1,100 per socket.

Skip if your compliance, backup, or monitoring stack is VMware-certified and replacing it costs more than the renewal. Also skip it if you need more than 3 vendor tickets a year and won’t pay for Standard.

VMware vSphere Foundation

Keep it if vCenter workflows and vSAN are load-bearing in your operations. A per-core quote that fits your budget makes that case stronger.

Wait on the 9.1 upgrade if you hold perpetual licenses. Get the subscription conversion terms in writing first.

Skip it for greenfield builds and homelabs. You’d pay per core with no public price for a cluster that runs on Proxmox for EUR 720 a year. That’s hard to justify.

When XCP-ng Makes More Sense

Illustrated a laptop showing XCP-ng project website with alternative virtualization options compared against Proxmox and VMware.
Illustrated a laptop showing XCP-ng project website with alternative virtualization options compared against Proxmox and VMware.

XCP-ng is the other free, open-source hypervisor that comes up in every VMware exit plan. It’s a reasonable pick if you prefer its management model. It also works as a second free platform to pilot next to Proxmox.

This guide didn’t verify XCP-ng’s current version, feature list, or support pricing. Read docs.xcp-ng.org before committing. Run the same exercise as above with it. Can you calculate the total? Does storage carry a capacity cap? Who answers the phone at 3 a.m.?

Alternatives Worth Pricing Before You Renew

Illustrated the XCP-ng open-source hypervisor interface displayed on a laptop screen in a casual coworking space.
Illustrated the XCP-ng open-source hypervisor interface displayed on a laptop screen in a casual coworking space.

XCP-ng

A free, open-source hypervisor and the most direct Proxmox competitor for budget-driven VMware exits. Pilot it on spare hardware.

Its current version and support pricing weren’t verified for this guide. Confirm both on docs.xcp-ng.org before building a cost comparison.

Illustrated Nutanix NCI infrastructure dashboard on a monitor in a corporate server room with blade servers and network gear.
Illustrated Nutanix NCI infrastructure dashboard on a monitor in a corporate server room with blade servers and network gear.

Nutanix NCI

A commercial hyperconverged platform that ecorpit.com lists among VMware alternatives. It fits teams that want a single vendor for compute and storage.

Pricing is quote-based, much like VVF. You trade one opaque quote for another, so get both side by side.

Illustrated OpenShift Virtualization Engine management console on a large desktop monitor in a developer workspace with multiple monitors.
Illustrated OpenShift Virtualization Engine management console on a large desktop monitor in a developer workspace with multiple monitors.

OpenShift Virtualization Engine

A fit for organizations already standardized on Red Hat OpenShift. The same ecorpit.com analysis says it’s licensed per bare-metal node, rather than per core or per socket.

Skip it if you don’t already run OpenShift. Adopting a Kubernetes platform to host VMs is a big change for a pure virtualization shop.

Illustrated a Sangfor HCI appliance with front panel LEDs, dual CPU sockets, and rack mounting on a metal IT rack shelf.
Illustrated a Sangfor HCI appliance with front panel LEDs, dual CPU sockets, and rack mounting on a metal IT rack shelf.

Sangfor HCI

Another commercial hyperconverged option from the ecorpit.com list. Pricing is quote-based.

It’s worth a quote if you want vendor-backed HCI outside the Nutanix and VMware ecosystems.

Illustrated a Microsoft Hyper-V server node running on a 1U rack-mounted server with visible Ethernet ports and a nearby Azure Local management console on a laptop screen.
Illustrated a Microsoft Hyper-V server node running on a 1U rack-mounted server with visible Ethernet ports and a nearby Azure Local management console on a laptop screen.

Microsoft Hyper-V / Azure Local

The natural choice for Windows-centric shops. Licensing ties to Windows Server or Azure Local core-based metrics. That’s a third model, separate from Proxmox’s per-socket and VMware’s per-core schemes.

If you already license Windows Server Datacenter by core, Hyper-V may cost you little extra. Run the numbers against your existing agreement.

Illustrated a VMware Cloud Foundation hardware rack unit with integrated storage and compute modules in a large data center rack.
Illustrated a VMware Cloud Foundation hardware rack unit with integrated storage and compute modules in a large data center rack.

VMware Cloud Foundation

A broader VMware private-cloud bundle than VVF, so don’t treat it as a budget substitute.

It’s relevant only if you’re doubling down on VMware as a full private cloud rather than a hypervisor.

Compatibility and Licensing Checks Before You Commit

Illustrated a checklist of compatibility and licensing requirements printed out next to a server rack and a network switch.
Illustrated a checklist of compatibility and licensing requirements printed out next to a server rack and a network switch.

Proxmox cluster subscription parity

Proxmox requires every node in a cluster to use the same subscription level. Plan the tier for the whole cluster up front, per the pricing page.

Adding a node later means buying that tier for its sockets too. Factor growth into the first budget.

VMware perpetual-to-subscription conversion

If you hold older VMware 8.x licenses, confirm how they map to vSphere Foundation 9.1 subscriptions before you plan the move, since upgrading from 8.x enters a 90-day evaluation window until licensed in VCF Operations. Talk to Broadcom or a channel partner before you schedule the upgrade.

You download license files in the VCF Business Services console and assign them in VCF Operations. Make sure whoever owns the Broadcom portal account is part of the project.

vSAN entitlement by version

vSphere Foundation includes 0.25 TiB of vSAN raw capacity per licensed core, pooled across your vCenter environment, per Broadcom’s add-on licensing guide. Older releases and VCF (1 TiB per core) use different allowances.

Ask any reseller which version their figure comes from. A quote that mixes versions isn’t a valid basis for capacity planning.

Current Proxmox version

Proxmox VE 9.2 is current, per the Proxmox VE roadmap, so “VE 8” guides may describe older behavior. Download from proxmox.com.

Match every how-to you follow to the version you actually install. Repository names and defaults can shift between major releases.

Hardware compatibility

Proxmox VE installs on bare-metal 64-bit x86 servers, and the roadmap lists a 64-bit ARM (arm64) build of 9.2 released August 5, 2026. This guide didn’t verify minimum CPU, RAM, or storage requirements for the current release.

Before you buy or reuse servers for VVF, look up your exact servers and NICs in Broadcom’s current compatibility guide. That goes double for older hosts you plan to reuse.

The Decision Boundary

Illustrated a split-view computer monitor showing the decision boundary analysis data for Proxmox VE and VMware vSphere.
Illustrated a split-view computer monitor showing the decision boundary analysis data for Proxmox VE and VMware vSphere.

Use Proxmox VE if you’re building new, run dense CPUs on one or two sockets, or want ZFS and Ceph without metered capacity. At EUR 120 per socket on Community, a 3-node, 6-socket cluster costs EUR 720 a year. That price is right on the pricing page.

Stick with VMware vSphere Foundation if vCenter and vSAN are wired into your operations and your backup and monitoring vendors depend on them. Your per-core quote also has to fit. If you hold perpetual licenses, get the subscription terms before touching 9.1. Pilot Proxmox or XCP-ng on spare hardware while you wait.

TBRT Runbook Index

Related CLI runbooks & deployment guides.

Open our hands-on Linux, virtualization, and network administration guides.

Alternative topologies

Adjacent stacks
worth evaluating.

XCP-ng

Worth evaluating if you want another free open-source hypervisor and prefer its management model; confirm current version and support pricing on docs.xcp-ng.org first, since this guide didn't verify them.

Keep your current vSphere 8 hosts

If your existing licenses and support still cover you, stay put and run a Proxmox pilot instead of migrating under renewal pressure.

Microsoft Hyper-V / Azure Local

Choose it if you're Windows-centric and already license Windows Server or Azure Local by core.

OpenShift Virtualization Engine

Fits teams standardized on Red Hat OpenShift; independent reporting describes per-bare-metal-node licensing.

Nutanix NCI

Consider it for a commercial HCI replacement with vendor support, accepting quote-based pricing similar to VMware's.

Documentation rigor

Spec-verified architecture.

Grounded in upstream release notes & hardware docs

Built from Proxmox's official pricing, product, and roadmap pages, Broadcom's VMware Cloud Foundation 9.1 TechDocs pages (vSphere Foundation overview, licensing overview, licensing model, and add-on vSAN capacity), and the Proxmox Backup Server pricing page, plus two independent third-party analyses (datazone.de, ecorpit.com), retrieved November 13 and updated November 16, 2026. This is not a hands-on review. No lab testing, benchmarks, or measurements were performed.

Upstream & hardware specs

Official vendor docs & hardware listings.

Verify release support lifecycles, HCL entries, and current SKUs directly.

Proxmox

Proxmox VE 9

$0 community / €120 per socket subscription

Open at Proxmox
VMware

VMware vSphere Foundation

Per-core subscription

Open at Broadcom / VMware

Vendor, documentation, and direct storefront links without an affiliate program are non-affiliate references.