Overview

kvbox gives you a real virtual machine in seconds, with Docker-like commands. Every box has its own kernel, so it is a safe place to hand to an AI agent, deploy a website or an API, or try something you would not run on your laptop.

kvbox new                  # boot a fresh box
kvbox connect box1         # shell into it over SSH
kvbox exec box1 -- uname   # run one command, get its exit code back
kvbox rm box1              # and it is gone

What a box isCopy Anchor Link

A box is a Firecracker microVM: a small Linux VM with its own kernel, memory and disk. It boots in a few seconds from a shared base image, gets an IP and an SSH key for you, and reaches the internet. Compared with a container, nothing inside the box can see the host; compared with a cloud VM, it is up before you finish typing the next command.

What makes it differentCopy Anchor Link

• Snapshots of a running box. kvbox snapshots new freezes memory, CPU state and disk while the box keeps running. kvbox new --from <snapshot> starts a warm clone in well under a second, every process still running. See Snapshots.
• Three ways to put a box away. Stop it (files kept), pause it (RAM kept), or hibernate it (RAM written to disk, freed on the host). See Stop, pause, hibernate.
• One CLI, your host or the cloud. The same commands drive the server on the machine you are on, or, after kvbox login, boxes placed on hosts behind a control plane.
• Made for agents. Every command has --json, exec returns the command's exit code, and the docs are at /llms.txt. See Agents.

Next stepsCopy Anchor Link

• Install the CLI on your laptop.
• Quickstart: first box, first shell, first snapshot.
• Self-host: run boxes on your own Linux machine.