A real Linux boundary
Run an independent kernel in KVM, install normal packages, and use an unmodified ext4 filesystem. The Guest never receives platform storage credentials.
Cats gives every workspace a real Linux microVM with durable disks and a stable identity. Work at full speed, let it sleep when idle, and wake it without rebuilding your environment.
$ cats login signed in · workspace acme-dev $ cats create dev creating durable RootDisk… starting guest… ready $ cats exec dev -- git status On branch main nothing to commit, working tree clean idle → suspended · work preserved
A Cat is a long-lived Linux microVM, not a disposable container session. Its name and disk outlive any one host.
Run an independent kernel in KVM, install normal packages, and use an unmodified ext4 filesystem. The Guest never receives platform storage credentials.
Running, Suspended, Warm, and Cold are distinct states. Fast host-bound resume is available, and every failed fast restore converges to a clean Cold start.
Successful FLUSH operations publish to durable remote storage. Local NVMe is a cache, while fencing keeps every PersistentDisk single-writer in V1.
Choose the right balance between wake speed, preserved process state, and complete host independence.
vCPU executes, memory is resident, disks keep publishing durable generations, and endpoints can serve traffic.
Full computevCPUs pause and process state stays on the original host. The VMM and host affinity remain for the shortest resume path.
Process state keptThe VMM exits after a host-local snapshot. Runtime RSS becomes zero, but restore still uses the original healthy host.
Local snapshotAll host runtime resources are released. A new host can boot from the last durable disk generation.
Host independentCats keeps the user-facing promise narrow and testable: a successful durable FLUSH survives permanent host loss.
The Guest sees virtio block devices and ordinary ext4—never object-store APIs or metadata credentials.
The block engine tracks dirty logical chunks. It does not upload an entire sparse virtual disk to commit a small working set.
Every attachment has a fencing epoch. A host that returns after a partition cannot publish over a newer writer.
Destroying a Cat removes its RootDisk; a detached PersistentDisk remains available until you explicitly delete it.
Follow the quickstart, create a durable workspace, run a command, and understand exactly what happens when it sleeps.