Skip to content

Resources

LLM documentation index

A compact, LLM-friendly index of the mvm docs structure and high-signal pages.

mvm is a security-first local microVM runtime for building and running sandboxed workloads with signed plans, audited launches, and backend-specific snapshot recovery.

  • Installation: install the CLI and prerequisites.
  • Quick Start: first local run.
  • Python quickstart: current Python SDK runtime and declaration paths.
  • Node.js quickstart: current TypeScript SDK runtime and declaration paths.
  • Core concepts: runtime, builder VM, Workload IR, plans, policy, and cold mode.
  • Design principles: security-first DX principles.
  • Builder VM: host command, Linux build boundary, persistent builder personas.
  • Nix and OCI: Nix-first auditability and OCI compatibility.
  • Policy profiles: restrictive, standard, dev, permissive, host-share, env, and seccomp posture.
  • Secrets and credentials: reference-first credential delivery, grants, redaction, and retention rules.
  • Persistent workspaces: encrypted volumes, host-backed mounts, copy workflows, snapshots, and cleanup policy.
  • Audit and receipts: signed run receipts, audit chain checks, decision-provenance export (JSON and TIBET-JSON), PROV-O/Turtle export, metrics, and boot reports.
  • Workload output streaming: following stdout/stderr live and after exit, the verification model, the --stream filter, retention, and the three limits.
  • Observability and results: result correlation, logs, receipts, audit IDs, boot reports, metrics, and redaction rules.
  • Network egress policy: deny-first outbound grants for agents, services, package installs, and browser automation.
  • Agent tool contract: model-facing sandbox request/response schema, validation, redaction, and retention rules.
  • SDK overview: runtime lifecycle API versus decorator declaration API.
  • Runtime SDK: imperative lifecycle surface.
  • Runtime modes: record, plan, live, and static declaration execution modes.
  • SDK security model: host execution, guest execution, secrets, network, audit, and state retention.
  • Operations cookbook: current SDK calls, target helpers, and secure CLI fallbacks.
  • Decorator SDK: static workload declaration and Workload IR.
  • Declaration workflow: compile declarations, IR JSON, and runtime recordings into build artifacts.
  • Declaration cookbook: concrete Python and TypeScript declaration patterns for secure Nix-first workloads.
  • Sandbox types: general, code, browser, desktop, and builder sandbox patterns.
  • Lifecycle matrix: current CLI support, current SDK support, and runtime parity targets.
  • Errors & metrics: SDK result, error, metrics, and audit correlation targets.
  • SDK reference: language SDK status and parity target.
  • Python SDK: current and planned Python surface.
  • Node.js SDK: current and planned TypeScript surface.
  • Linux execution and macOS are current local targets.
  • Native Windows is future work tracked in mvm#428. WSL2 with nested /dev/kvm is the supported Windows-adjacent libkrun workload path.
  • Strong claims need Shipped/Preview/Planned/Not claimed status.
  • Runtime SDK lifecycle APIs are Partial until shared SDK tests cover the full lifecycle.
  • Persistent builder DX is Preview until top-level dev up and build behavior is proven.
  • OCI examples should use digest-pinned or clearly local/dev references.
  • Secret examples should use references or redacted example values, not plaintext credentials.