bhatti — Own your metal: Machines on demand

bhatti attempts to solve the age-old friction between the isolation of Virtual Machines and the speed of containers. By allowing users to deploy Linux VMs on their own hardware with a focus on nearly instantaneous resume times, it positions itself as a local alternative to serverless micro-VM architectures. The core value proposition is the ability to freeze not just the disk, but the memory and in-flight TCP state, allowing a developer to snap a 'known good' state and return to it without the boot-time overhead usually associated with KVM or VMware. From a product standpoint, the CLI-first approach is correct. The `bhatti create` and `bhatti snapshot` workflow targets the 'disposable infrastructure' mindset, making it ideal for CI/CD runners or isolated sandbox testing where state persistence is required but boot latency is unacceptable. The technical challenge here is the snapshotting overhead; while the resume is fast, the initial capture of memory and network state can be resource-intensive depending on the VM size. Strength lies in its sovereignty—running on your own metal removes the 'cloud tax' and latency of remote providers. However, the reliance on a curl-to-bash installation script is a bit archaic for a tool targeting security-conscious system administrators. The real test for bhatti will be its stability under heavy I/O loads and how it handles network state synchronization upon resume across different physical interfaces. This is a tool for the 'homelab' power user and the cloud engineer building private infrastructure. If you are tired of the overhead of full virtualization but find Docker's shared kernel too permissive for your security model, bhatti provides a compelling middle ground.