Virtual machines on KVM
Linux and Windows VMs across your hosts, with power control over the BMC (iLO, iDRAC, IPMI) and hardware health in the console.
OpenStack alternative
A private cloud,
without running OpenStack.
CloudOps runs the control plane, so your team doesn't have to. Your own servers get virtual machines, Kubernetes, networks, load balancers, object storage and, in preview, managed databases, 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 move first.
- No control plane for you to run
- Self-service for your teams
- Console, API and Terraform
- Built and operated in the EU
Why teams are moving
OpenStack can do almost anything. Someone has to run it.
OpenStack is a broad, proven open-source cloud. It is also many separate services plus the message queue and databases behind them, with a new release every six months and upgrades to plan. Many teams end up dedicating engineers just to keep it healthy.
CloudOps takes that work off your team. We operate the control plane as a service and your servers run the workloads, so your engineers can spend their time on what runs on the cloud.
What replaces what
OpenStack projects, and what you use instead.
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 compute node 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 OpenStack instance and move on to the next one, host by host.
CloudOps has no OpenStack API and cannot import instances. Heat templates and OpenStack clients need replacing, usually with Terraform.
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 reuse my OpenStack tooling or import instances?
No. CloudOps does not offer the OpenStack APIs and cannot import instances, so Heat templates and scripts that call OpenStack need rewriting, usually in Terraform. You rebuild workloads from images and copy the data with your usual tools.
Do I need new hardware?
No. CloudOps runs on standard servers. A compute node leaving OpenStack gets a fresh Linux and KVM install, over the network if you like, and servers that already run plain Linux join with a one-line import.
Where does it run?
Your VMs and data stay on your servers. CloudOps is a managed service: we run the control plane in the EU under the GDPR, and you cannot install it yourself. A US control plane is available on request.
What would I give up?
CloudOps does not have live migration between hosts or automatic VM restart on another host, and you cannot extend it with your own services and drivers as you can with OpenStack. If you need those, or must run the control plane inside your own network, OpenStack remains the better fit.
Plan your move from OpenStack.
Start with one host and one workload, and keep the rest running until you are ready.
OpenStack is a trademark of the OpenInfra Foundation. CloudOps is not affiliated with or endorsed by the OpenInfra Foundation.