Skip to content

LLM documentation index

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

  • 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.
  • Windows is future work tracked in mvm#428.
  • 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.