The short version: a hypervisor and a container engine are built in, and they are built on standards you already know.
Yes. A KVM hypervisor is built into the platform. You can create and run virtual machines on day one — no separate hypervisor to buy, install, or license.
Yes. K3s — a lightweight Kubernetes — is built in. You can deploy container workloads straight away, on the same nodes as your virtual machines.
KVM is the Linux kernel's own hypervisor. It is open, mature, and runs on almost any server. There is nothing to license, performance is strong, and the virtual machines you already run move over without surprises.
We build on it because it is proven and everywhere — not because it is new.
K3s is a small, fully conformant Kubernetes. It is light enough to run at the edge and capable enough for the core. Because it is real Kubernetes, your existing manifests, Helm charts, and tools work without changes.
We chose it for a small footprint and a standard your team already knows.
No. Both are part of the platform and managed from the same portal. You do not assemble them yourself, and there are no separate licences to track.
Yes. Virtual machines and containers run side by side on the same nodes, under one portal and one set of controls. Use whichever fits the workload.
Yes. K3s is conformant Kubernetes, so standard manifests, Helm charts, and command-line tools work the same as they do anywhere else.
Standard x86-64 and arm64 hardware, and the major clouds. The same platform runs from a single server at the edge, to a cluster in the core, to a virtual machine in the cloud.