Kyvenza is built on Apple’s Virtualization.framework, the same foundation Apple itself exposes for running macOS and Linux VMs on Apple Silicon. That means guests talk to the hypervisor through the CPU’s native virtualization extensions rather than through a translation layer, which is why cold-boot and disk-I/O numbers feel closer to a second Mac on your desk than to a traditional VM.
Around that foundation we own the surface the user actually touches: the VM library UI, snapshot and cloning logic, lifecycle controls, diagnostic bundle generation, license handling, and update plumbing. Keeping that surface narrow is deliberate — it is how a two-person studio ships a tool that feels considered rather than assembled.
Kyvenza is ARM-only by design. Intel Macs and x86 guests are out of scope; our time is better spent making the ARM-native experience excellent than chasing a matrix of architectures we cannot support well. Windows 11 on ARM was the one exception we spent 2.0 building, because it is ARM-native too — and it runs on a second engine kept deliberately separate from the Apple framework path.