Containers, but actually isolated: microVMs you can spawn from code

What it does

Microsandbox is a Rust-based SDK and CLI for spinning up lightweight microVMs locally. It runs standard OCI container images (Docker Hub, GHCR, etc.) inside hardware-isolated VMs, booting in milliseconds as child processes. No server, no daemon, no root privileges — just a library call in Rust, Python, TypeScript, or Go.

The interesting bit

The “secrets that can’t leak” angle is the real architectural flex: cryptographic keys never enter the VM itself, so a compromised sandbox can’t exfiltrate them. That’s a meaningful difference from standard container runtimes where a kernel escape equals game over. The agent integration — via MCP server and “Agent Skills” — also signals where they think the demand is heading: AI agents that need to run untrusted code without trusting it.

Key highlights

• Sub-100ms boot times claimed for microVMs
• Hardware-level isolation via KVM (Linux) or Apple Silicon virtualization (macOS)
• OCI-compatible: runs existing container images without conversion
• Embeddable SDK in four languages; CLI optional
• Rootless operation, no long-running daemon
• Detached/long-running sandbox mode supported
• Explicit beta status with warning of breaking changes

Caveats

• Linux requires KVM; macOS requires Apple Silicon — no Intel Mac support mentioned
• Beta software: README explicitly warns of “breaking changes, missing features, and rough edges”
• First image pull is cold-start slow; only subsequent runs hit the cached fast path

Verdict

Worth evaluating if you’re building agentic tools or need stronger isolation than containers without the orchestration tax of full cloud VMs. Skip it if you need production stability today or run on older Intel Macs.