Choosing a Private Cloud Platform: CloudStack, OpenStack, VMware or KVM

Every private cloud project reaches the same fork within the first two weeks: which platform? The debate usually runs on features. It should run on operations, because five years from now the feature lists will have converged and the operational burden will not.

Here is how we frame the choice with clients, based on what each option demands from the team that has to live with it.

The four realistic options

Apache CloudStack. An open-source orchestration platform that turns KVM hypervisors into a multi-tenant cloud with a self-service portal, accounts, projects, usage records for billing, and a clean API. Its defining trait is operational simplicity: a small management plane, a well-understood database, and upgrades a two-person team can actually perform. This is why a large share of the world's independent hosting providers run on it.

OpenStack. The most capable and most complex of the open options. A collection of cooperating services — compute, networking, storage, identity, images and more — each with its own configuration and lifecycle. In return you get enormous flexibility: advanced networking, bare-metal provisioning, deep integration options. Telecoms and large enterprises with dedicated platform teams run it well. Small teams routinely drown in it.

VMware. Commercially supported, mature, familiar to almost every operations engineer on the market, with the strongest ecosystem of backup, DR and monitoring integrations. The trade-offs are licensing cost — which has shifted significantly under new ownership and should be checked against current terms at decision time, not assumed from memory — and vendor lock-in that compounds the longer you build on it.

Plain KVM with tooling. No cloud platform at all: libvirt, perhaps Proxmox or a thin management layer, scripts and configuration management. Fine for a static estate of a few dozen VMs run by the team that built it. It is not a multi-tenant cloud, and pretending it is one becomes painful the day a second customer, a billing requirement, or a self-service demand arrives.

Decide on these five questions

Who operates it, and how many of them are there? This outweighs everything else. OpenStack rewards a dedicated platform team and punishes anything less. CloudStack is deliberately operable by a small team. VMware lets you hire operational competence off the open market. If your realistic operations headcount is two or three people who also do other jobs, that fact alone eliminates options.

Is this multi-tenant? If you are hosting customers — separate accounts, quotas, usage-based billing, self-service — you need a platform where tenancy is a first-class concept. CloudStack and OpenStack were built for it. VMware can do it with additional products and cost. Plain KVM cannot, honestly.

What does billing need? Usage records are the raw material of a hosting business. CloudStack emits them natively per account. OpenStack has the machinery, but assembling reliable metering takes real work. If your business model is "sell VMs and invoice monthly," the platform's billing surface is a primary criterion, not an afterthought — and it drives the customer portal design too.

What is the exit cost? Open platforms on KVM keep your workloads in portable formats and your automation on open APIs. A proprietary stack means any future migration is a project in itself. Neither answer is wrong; the mistake is not pricing the exit at entry.

What hardware do you already own? Existing hardware often decides more than people admit. A rack of servers with local disks points toward one storage architecture; a SAN inheritance points toward another; a greenfield budget opens up distributed storage like Ceph, which pairs naturally with both CloudStack and OpenStack but brings its own operational discipline.

The pattern we see in practice

For service providers and businesses building a hosting operation with a lean team, CloudStack on KVM with Ceph or straightforward NFS storage is the configuration that keeps working years later: genuine multi-tenancy, native usage records, a portal customers understand, and an upgrade path that doesn't require a war room.

For large enterprises with an existing platform engineering function and complex networking requirements, OpenStack earns its complexity.

For organisations whose priority is commercial support and hiring ease, and whose finance team has signed off current licensing, VMware remains a defensible choice — with eyes open about lock-in.

And for a fixed internal estate with no tenancy requirement, skipping the cloud platform entirely is sometimes the honest answer. Not every virtualisation estate needs to be a cloud.

What a proper platform decision looks like

The deliverable isn't a preference — it's a design: tenant model, compute and storage sizing, network architecture, portal and billing integration, backup and DR approach, security baseline, and an operating model matched to your actual team. That package is what turns "we picked OpenStack" from a hope into a plan.

That's the shape of our private cloud engagements: platform selection on evidence, then full design, and implementation either by your team with our supervision or end to end. If you're at the fork right now, request an assessment and bring your constraints — team size, hardware, tenancy, billing. The right platform falls out of those four facts faster than out of any feature comparison.