Instelligence

For MSPs

Proxmox for Managed Service Providers

Proxmox for MSPs running hosted platforms, private clouds for clients and SMB office sites, with licensing that doesn't climb as you add customers.

Most Australian MSPs we work with do some mix of three things: run a hosted platform that their customers' workloads live on, design and deliver private platforms that the customer owns and operates themselves, and stand up small Proxmox deployments at SMB and branch-office sites. Broadcom's VMware pricing made all of this harder. Proxmox handles each of them on one platform.

The three jobs MSPs do

1. Managed hosted platforms

Customer workloads running on the MSP's hardware, in the MSP's racks (or in colo), managed end-to-end. Customers don't see the hypervisor; they see "their VMs". The platform serves many customers, but the MSP's engineering team handles onboarding, change requests and capacity. Proxmox VE gives you Ceph for shared storage, native backup via PBS, and HA without per-customer licence multipliers.

2. Private platforms for the customer

Customer-owned hardware in the customer's site (or their colo), designed and built by you, operated by you under a managed services contract. The customer wants a private cloud without becoming a virtualisation team. You deliver the platform plus the monitoring, patching, backup verification, and incident response around it. Proxmox licensing is predictable, so customer conversations are about the service rather than the next renewal.

3. SMB and office deployments

Smaller installs at SMB head offices, branch sites, retail locations and manufacturing floors: typically 2–4 nodes of commodity hardware running a handful of VMs for file, print, AD and POS. VMware's licensing minimums make these sites economically unworkable now. Proxmox's per-socket pricing scales down cleanly, and PBS gives you tested backups without an extra vendor.

What changed with Broadcom

  • Per-core licensing with minimums. The 16-core/socket and 72-core/order floors hit small per-customer sites disproportionately. A 4-core branch-office host bills as 16, and any order bills at least 72 cores even if your customer has 16.
  • VCSP terminated. The per-VM, usage-billed model for service providers ended in 2024. Its replacement is commercial subscriptions priced for enterprise IT, which don't suit businesses that sell infrastructure as a service. (If you're moving from hosting into self-service IaaS, see our CSP page.)
  • Suite uplifts forced. VCF bundles vSphere, vSAN, NSX, Aria, and VKS (vSphere Kubernetes Service, formerly Tanzu) under one per-core subscription. You pay for the whole stack whether your customers use it or not.
  • Mid-cycle price moves. List per-core pricing went from US$350 to US$400 partway through what was effectively a forced migration window, so there is little reason to expect pricing to stay put.

What an MSP needs from a platform

  • Per-environment cost predictability. Whether it's a 3-node cluster at a head office or a 12-node hosted platform, the bill scales with hardware rather than with how many VMs you run.
  • Operational consistency across sites. Same tooling, same patching workflow, same backup verification process whether you're managing 3 sites or 30.
  • Reliable backup with proof of recovery. Customers ask for evidence; PBS gives you per-customer verified restores without an extra backup vendor.
  • Hardware freedom. Reuse what's already in the rack, run on whatever's cost-effective at the next refresh, no HCL gating from the platform vendor.
  • A vendor that won't change the model under you. Your service pricing shouldn't depend on what a supplier decides at the next renewal.

Why Proxmox fits all three jobs

  • Per-socket subscription, no minimums. SMB sites with low core counts cost the same per socket as dense hosted platforms, and there is no 72-core order floor.
  • Single platform, single skillset. Same Proxmox VE on a 2-node SMB office and a 12-node hosted platform. Your engineers don't context-switch between tiers.
  • Proxmox Backup Server. Free, deduplicated, encrypted and immutable-capable, with per-customer retention policies and restore tests. It comes with the platform rather than as a separate invoice.
  • Native multi-tenant primitives. Resource pools, role-based access, VLAN/VXLAN isolation, per-customer storage pools. You don't need a third-party portal to keep customers' resources separated.
  • Linux-native operations. Your engineers use standard Linux tooling for everything: Ansible, Terraform, Prometheus, Loki, or whatever your existing stack uses. There are no vCenter-only special cases.

What the numbers look like for an MSP

Illustrative scenario

40 VMware hosts. 400 customer VMs. US$448k a year in VCF licensing.

A worked example, built from environments of this size, of a provider moving its customer-facing platform from VMware Cloud Foundation to Proxmox VE and Ceph in phased batches, with every cost shown at list price and at Broadcom's discounted 3-year commit pricing.

Read the scenario →

Illustrative scenario based on real-world environments, not a named client.

What an MSP engagement looks like

  1. Discovery call. A senior engineer walks through your current service mix, customer profile, hardware estate, and renewal timing.
  2. Assessment. Inventory of platforms, sites, and contracts. Output: a written report on what migrates cleanly, what needs redesign, and a realistic timeline that aligns with your customer maintenance windows.
  3. Target architecture. Proxmox cluster designs for each platform type (hosted, customer-private, SMB/office), with shared operational tooling across them.
  4. Pilot site. Move a non-critical platform or office first to validate runbooks before the bigger customer-facing migrations.
  5. Batched migration. Per-customer cutovers scheduled into your existing maintenance windows. Customer-by-customer comms supported by us if needed.
  6. Operational handover (or co-managed). Documentation, runbooks, knowledge transfer. Optional ongoing managed services if you'd rather we run it.

Thinking about self-service IaaS?

If your next step is moving from MSP-managed hosting into self-service IaaS (customer onboarding via API, billing as a product, tenant portals), that's a different conversation. We've written it up separately: Proxmox for Cloud Service Providers.

Already running Proxmox, or about to?

Once the platform decision is made, the work shifts to building and running it well. Our MSP & CSP platform consultancy covers hosting platform design, retained senior-engineer hours for architecture, design and upgrade planning, and the migrations that move your customers onto it.

"Instelligence brought strong technical insight and moved at the pace we needed. The engagement was efficient, well-communicated, and handled with a clear understanding of both the commercial and technical requirements. It made transacting Proxmox subscriptions for our customer simple and low-risk."
TH

Tony Heywood

Managing Director, Prodo Technology

Talk to us

Discovery calls are free and run by an engineer. Tell us what your platform mix looks like and where the renewal pressure is, and we'll give you a realistic picture of what moving to Proxmox looks like across your customer base.

Book a discovery call See savings vs VCF