Your servers, managed by CloudOps
Each host runs KVM. Power control over the BMC (iLO, iDRAC, IPMI) and hardware health in the console.
VMware alternative
Leave VMware.
Keep your servers.
CloudOps turns the servers you already own into a private cloud: virtual machines, Kubernetes, networks, load balancers, object storage and managed databases, all self-service from one console, a REST API and Terraform.
Runs on the open-source KVM hypervisor. Sign up with Google, or talk to us about your migration first.
- Open-source KVM, no hypervisor licence
- Self-service for your teams
- Console, API and Terraform
- Built and operated in the EU
Why teams are moving
VMware licensing changed. Your hardware didn't.
Since Broadcom bought VMware, perpetual licences have ended, products are sold in bundles, and many customers pay far more for the same hosts.
CloudOps gives the same servers a cloud-style control plane on open-source KVM, so you can renew less, or not at all, without buying new hardware.
What replaces what
Familiar building blocks, without the VMware stack.
One console, an API and Terraform
Create and manage VMs, networks and storage across all your hosts. Every change runs as a tracked, auditable job.
Networks and security groups
Private networks, security groups, load balancers, an encrypted overlay between hosts and site-to-site VPN.
Block and object storage
ZFS-backed block volumes with snapshots, and S3-compatible object storage.
Kubernetes clusters
Create Kubernetes clusters on your own hosts, or import the ones you already run, and add or remove nodes.
Images and network installs
Linux and Windows VM images, and unattended OS installs over PXE for bare metal and VMs.
How a move works
Start with one host, not a big-bang migration.
Add a first host
Free up one server and install it over the network, or import a Linux server you already run with a one-line command.
Recreate a workload
Build the VM from an image or a Terraform plan, attach volumes and networks, and test it next to the original.
Cut over and repeat
When it runs, switch the traffic, retire the VMware VM and move on to the next one, host by host.
Coming soon: import running VMs straight from ESXi, copying the disks without touching the source. Ask us for early access.
AI-ready, with guardrails
Let AI agents help run it, within limits you set.
CloudOps has a built-in MCP server. Connect Claude or another MCP assistant and it can read your servers, networks, storage and jobs and, if you allow it, create VMs and volumes.
Access stays off until an owner turns it on. You choose read only or safe changes, every tool call is recorded, and an agent can delete only what it created.
Questions before you switch
What to know before you switch.
Can I import my VMs straight from ESXi?
Not yet. Direct ESXi import is being built and is coming soon: it will read your VM inventory, copy the disks and recreate the VMs on CloudOps hosts without changing the source. Until then you rebuild workloads from images or with Terraform. Talk to us if you want early access.
Do I need new hardware?
No. CloudOps runs on standard servers. A host leaving ESXi is reinstalled with Linux and KVM, over the network if you like, and servers that already run Linux join with a one-line import.
Where does it run?
Your VMs and data stay on your servers. We host the control plane in the EU and operate under the GDPR; a US control plane is available on request.
Is it only VMs?
No. Besides VMs you get Kubernetes clusters, private networks, security groups, load balancers, block and object storage and, in preview, managed databases.
Plan your way off VMware.
Start with one host and one workload, and keep the rest running until you are ready.