Run your VMs and desktops where your containers already live.

$ kubectl get vm -n desktops
NAME             AGE   STATUS    READY
win11-pool-014   21d   Running   True
win11-pool-015   21d   Running   True
cad-gpu-03       9d    Running   True

# drain a host — the guest keeps its session
$ virtctl migrate cad-gpu-03
VM cad-gpu-03 was scheduled to migrate

# requires ReadWriteMany storage (Ceph RWX)

VMs and containers, one platform — open, with no lock-in. A KubeVirt VM and a container run side by side on the identical cloud-native foundation as our Virtual Private Cloud and Dedicated Private Cloud. The only difference between tiers is the isolation and dedication of the compute beneath them — shared-hardware VPC nodes, or single-tenant bare-metal DPC nodes for regulated, high-security desktops and VMs. KubeVirt is an open-source CNCF project, so nothing about the platform traps you here: your VMs are declarative YAML and portable disk images, not a proprietary appliance format.

Virtual Desktop Infrastructure, on the same platform

A virtual desktop is just a VM with a display protocol and a connection broker in front of it. KubeVirt makes that desktop a Kubernetes object — so the same platform that runs your server VMs runs Windows and Linux desktops for your users, GPU-accelerated where the work demands it, on infrastructure that stays in the EU.

On the desktop broker and protocol, the honest version. KubeVirt provides the desktop VMs and console access; the user-facing connection broker and remote-display protocol (session brokering, gateway, client) is the piece to confirm for a production VDI rollout. We will tell you precisely what GRN provides versus what you bring or we contract as an add-on. Pending validation

Move running VMs without dropping the session

The operational test of any virtualisation platform is what happens on a Tuesday-night patch window. KubeVirt live-migrates a running guest off a host so you can drain it for maintenance — and reschedules VMs when a host fails. There is one hard requirement, and we state it plainly.

The requirement, stated up front. Live migration needs shared ReadWriteMany storage so the source and destination hosts both reach the VM's disk — this is a property of how QEMU/KVM migration works, not a GRN limitation. We satisfy it with Ceph RWX. VMs on local-NVMe boot disks cannot live-migrate; they HA-reschedule with a restart instead. Choose the storage class per workload and you choose the failure behaviour with it.

GPUs for desktops and compute VMs

Graphics and compute desktops need a real GPU, not a software framebuffer. KubeVirt exposes host GPUs to guests two ways — full passthrough for a dedicated card, or mediated devices (NVIDIA vGPU) to slice one physical GPU across several desktops. We state which we offer rather than implying both.

GPU node pools, stated honestly. GPU desktops and compute VMs schedule onto dedicated GPU node pools. The exact NVIDIA models, the choice between passthrough and licensed vGPU, and per-seat sizing depend on current hardware — tell us the workload and we will confirm what is available. Confirm GPU models

VM lifecycle, managed end to end

Day-2, addressed honestly. Host patching, KubeVirt upgrades and hardware replacement are ours, run with live migration so guests stay up where storage allows. Guest-OS patching, in-VM software and licensing stay yours — KubeVirt does not manage what runs inside the VM, and we will not pretend it does. Backups are only as good as their last successful restore, so we size and test them against the RPO/RTO you give us. Confirm cadence

On compliance, the honest version. The platform runs under EU-only data residency with a signed DPA and no US Cloud Act exposure — the substantive part of most regulated requirements, and a real advantage for desktops handling personal data. We will support PCI-DSS and HIPAA-aligned, NIS2-ready deployments on dedicated, isolated infrastructure — but we do not claim certifications we do not hold. Tell us your compliance scope and we will tell you precisely what we can and cannot attest to.

Your VMs, desktops and containers on top, KVM-enabled renewable-powered hosts at the bottom. Every layer is a named component you could reproduce on any KubeVirt cluster; none of it is a black box you can only run here.

Every layer uses standard, portable components — KubeVirt, Ceph, Multus, Velero — nothing proprietary you cannot reproduce on another Kubernetes cluster.

Items tagged for review are confirmed against a live cluster before publishing — we would rather leave a value open than print one we cannot stand behind.

Storage for virtual machines

Networking for virtual machines

Dual-stack IPv4 / IPv6 throughout. All storage classes are dynamically provisioned and expandable. Prices in EUR, ex VAT; 10% discount on annual commitment. Verify current rates on the pricing page before quoting.

Against the incumbents, on the axes that matter

An objective capability comparison against the major virtualisation platforms. Subjective claims ("faster", "simpler") are left out — only things you can check on a product page or in a licence agreement.

✓ yes · ~ partial · ✕ no. Compiled from public product & pricing pages, June 2026; vendor features and licensing change — verify before quoting.