# nanoVM > Documentation for nanoVM — fast, isolated microVM sandboxes by LithosAI. - [nanoVM](https://docs.nanovm.dev.lithosai.cloud/index.md): Run your code in fast, isolated microVM sandboxes behind a plain HTTP/JSON API and a Python SDK. - [Sandbox launch guide](https://docs.nanovm.dev.lithosai.cloud/launch.md): First run, pilot limits, image expectations, recovery behavior, and support. - [nanoVM for coding agents](https://docs.nanovm.dev.lithosai.cloud/coding-agents.md): The shortest path from an API key to running code in an isolated microVM — skill install, SDK patterns, MCP tools. - [Run commands](https://docs.nanovm.dev.lithosai.cloud/guides/run-commands.md): Shell strings, argv form, persistent sessions, and background work — plus the real limits, exactly where they bite. - [Work with files](https://docs.nanovm.dev.lithosai.cloud/guides/files.md): Read, write, list, and move files in a sandbox — and when to move bulk data another way. - [Serve something](https://docs.nanovm.dev.lithosai.cloud/guides/serve.md): Expose a port on a public HTTPS URL. - [Save, restore, fork](https://docs.nanovm.dev.lithosai.cloud/guides/save-restore.md): Checkpoint memory + disk, restore into new sandboxes, and fork live copies for parallel work. - [Control cost](https://docs.nanovm.dev.lithosai.cloud/guides/lifecycle.md): Idle sleep is automatic; archive when you're done for days. Usually the right move is nothing. - [See what's happening](https://docs.nanovm.dev.lithosai.cloud/guides/observability.md): Every sandbox keeps its own paper trail — events, console logs, utilization metrics, and an org audit log. No setup. - [Use your own image](https://docs.nanovm.dev.lithosai.cloud/guides/images.md): Any OCI image, private registries, pre-built templates, and the full-VM runtime. - [How it thinks](https://docs.nanovm.dev.lithosai.cloud/concepts.md): Sandboxes, images and templates, runtimes, shapes, rest states, and the durability rules. - [Python SDK](https://docs.nanovm.dev.lithosai.cloud/reference/sdk.md): The whole surface is twelve names — one operation per job, arguments select behavior. Everything else is an alias. - [HTTP API](https://docs.nanovm.dev.lithosai.cloud/reference/http-api.md): Every route, the sandbox object, snapshots, exports, templates, registries, usage, and every status code. - [Limits & behaviors](https://docs.nanovm.dev.lithosai.cloud/reference/limits.md): Every hard limit, what happens at the bound, and the platform behaviors worth knowing.