# VMS > A full Ubuntu virtual machine for each AI agent. Each sandbox has root, Docker, systemd, and its own kernel, disk, name, and URL. - Isolation: A full virtual machine with its own kernel, on QEMU and KVM. - Snapshots: Each minute, the sandbox saves its changed files. A stopped sandbox keeps its data for 30 days. - Region: Vint Hill, Virginia, in the United States. - Billing: By the second, from the moment a sandbox runs. Starts are free, and a stopped sandbox has no usage charge. - Price: $0.034 an hour for 4 vCPU and 8 GiB of RAM. Plans from $20 a month. ## Sizes - `small`: 2 vCPU, 4 GiB RAM, $0.017 an hour - `medium`: 4 vCPU, 8 GiB RAM, $0.034 an hour - `large`: 8 vCPU, 16 GiB RAM, $0.068 an hour - `xlarge`: 16 vCPU, 32 GiB RAM, $0.136 an hour ## Docs - [Docs llms.txt](https://vms.dev/docs/llms.txt): a link to each docs page - [Docs llms-full.txt](https://vms.dev/docs/llms-full.txt): the full text of all docs pages in one file - [Quickstart](https://vms.dev/docs/quickstart): create a workspace and an API key - [auth.md](https://vms.dev/auth.md): how an agent registers by itself ## Comparisons - [VMS vs E2B: full virtual machines or Firecracker microVMs](https://vms.dev/en/compare/vms-vs-e2b): VMS gives each sandbox a full virtual machine that keeps its files when it stops. E2B runs Firecracker microVMs that pause with their memory. - [VMS vs Daytona: virtual machines or containers](https://vms.dev/en/compare/vms-vs-daytona): VMS gives each sandbox a full virtual machine. Daytona starts with containers and adds virtual machine classes. - [VMS vs Modal: full virtual machines or gVisor sandboxes](https://vms.dev/en/compare/vms-vs-modal): VMS runs each sandbox in a full virtual machine. Modal runs gVisor sandboxes, with a virtual machine runtime for Docker. - [VMS vs Vercel Sandbox: billed by running time or by active CPU](https://vms.dev/en/compare/vms-vs-vercel-sandbox): VMS gives each sandbox a full virtual machine, billed by the second. Vercel Sandbox runs Firecracker microVMs and bills active CPU. - [VMS vs boat: the same full virtual machines, for less](https://vms.dev/en/compare/vms-vs-boat): Both give each sandbox a full Ubuntu virtual machine. VMS costs less, bills only while a sandbox runs, and gives free starts, free seats, and a 14-day trial. ## Use cases - [Sandboxes for coding agents](https://vms.dev/en/use-cases/coding-agents): Give each coding agent a full Ubuntu virtual machine where it can install packages, run tests, and start servers. - [Sandboxes for agent evals](https://vms.dev/en/use-cases/agent-evals): Run each eval task in a clean sandbox from one template. Fork many runs from the same state. - [Sandboxes for long-running agents](https://vms.dev/en/use-cases/background-agents): Stop a sandbox while the agent waits. It starts again with the same files, name, and URL. ## Definitions - [AI sandbox](https://vms.dev/en/definitions/ai-sandbox): An AI sandbox is an isolated computer where an AI agent runs code. Code in the sandbox cannot reach the host or other sandboxes. - [microVM](https://vms.dev/en/definitions/microvm): A microVM is a virtual machine with a small set of devices. It boots fast and uses little memory, but it has fewer features than a full virtual machine. - [KVM](https://vms.dev/en/definitions/kvm): KVM (Kernel-based Virtual Machine) is a part of the Linux kernel. It lets a program run virtual machines directly on the CPU. - [Disk snapshot](https://vms.dev/en/definitions/disk-snapshot): A disk snapshot is the saved disk of a machine at one time. A new machine can start from it, with the same files.