Three products, one way of working

kcore is a hypervisor you run from files. Vault keeps backups an attacker cannot delete. Provisioning turns racked servers into nodes. Each is licensed and versioned on its own.

kcore hypervisor

The platform. Cloud Hypervisor on NixOS, a controller, a node agent on every host, and kctl. You describe VMs, networks, storage, and updates in YAML or Terraform and apply them.

Open core. The community ISO is free. Signed ISOs, the update channel, and support are priced per physical CPU socket. Pricing, features, what is new in 0.7.0.

kcore Vault

A backup appliance on its own machine. It pulls disk extents from the cluster, encrypts and signs them, and keeps them until a retention date that can be extended but never shortened. An offsite copy goes to an S3 bucket with Object Lock.

Built for the case where someone has an admin password or root on a hypervisor node. The nodes hold no credentials for the repository.

Vault overview · operator guide · ransomware resistance

kcore Provisioning

Bare-metal automation through the BMC. It reads hardware over Redfish, boots kcoreOS by UEFI HTTP boot, sets BIOS and RAID, checks every disk, issues node certificates, and runs DHCP and DNS for the networks it owns.

Use it to bring up a rack without a keyboard or a USB stick, or to rebuild a node after a failed disk.

Provisioning overview · operator guide

Which one do you need

You wantStart with
Replace VMware or Proxmox with something you can version-controlkcore hypervisor
Backups that survive a compromised admin accountkcore hypervisor and Vault
Ten or more servers racked and wired, nothing installedProvisioning, then the hypervisor
A whole site from bare metal to protected VMsAll three

Vault and Provisioning have their own release numbers. Vault 0.1.x and Provisioning 0.1.0 are documented against kcore 0.7.0. Prices for both are by quote.