Our take
Activeregular commits and releases- Activity
- 86
- Community
- 75
- Issues
- 76
- Pull requests
- 82
+380 stars in the last 30 days
- Merges more pull requests than 92% of the projects we track
- Releases more often than 89% of the projects we track
Microsandbox is an actively maintained local microVM runtime with a broad contributor base and rapid release and issue handling, but its beta status and host virtualization prerequisites make platform validation important.
Good fit if
- You need local hardware-isolated execution for agents, code, or automation rather than a remote sandbox service.
- Your target hosts support KVM, Apple Silicon virtualization, or WHP, and OCI images match your workflow.
- You want an actively developed project with multiple SDKs and CLI access, under Apache-2.0.
Look elsewhere if
- You need a mature, stability-guaranteed runtime, since the project explicitly describes itself as beta and warns of breaking changes and missing features.
- Your deployment hosts cannot enable the required virtualization backend.
- Your application requires a remote managed sandbox service rather than a local runtime.
All health signals
| Last commit | 2026-10-27 (today) |
|---|---|
| Commits, last 90 days | 100+ |
| Releases, last 12 months | 62 (latest v0.7.11, 2026-10-24) |
| Contributors | 73 (top contributor: 40% of commits) |
| Issues closed, last 90 days | 15+ (typically closed in 1 day) |
| Pull requests merged, last 90 days | 89 (typically merged in 0 days) |
| Project age | 2 years |
Checked on 2026-10-28 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
9,099Forks
523Change since Nov 16, 2026: +17 stars·+1 forks
Overview
Microsandbox is a Rust microVM runtime for running untrusted workloads in isolated, local virtual machines. It targets tasks such as AI agent execution, user-submitted code, plugins, and CI jobs, where a container alone may not provide the isolation boundary a team wants. The project acknowledges libkrun and smoltcp among the projects that made it possible.
It runs on Apple Silicon Macs, Linux hosts with KVM enabled, and Windows hosts with WHP enabled. You can use the msb CLI or embed sandbox creation and control in an application through SDKs for TypeScript, Rust, Python, Go, and Ruby. Unlike a remote sandbox service, the README describes the SDK as starting a microVM as a child process without requiring a server or long-running daemon.
Key Features
- Runs OCI-compatible images from registries such as Docker Hub and GHCR.
- Creates, executes, starts, stops, and removes named sandboxes through the
msbCLI. - Forks running sandboxes and saves or restores sandbox snapshots.
- Embeds sandbox lifecycle and command execution in supported language SDKs.
- Configures sandbox resources, network access, and scripts through a YAML file.
- Supports detached sandboxes for longer-running sessions.
- Provides agent skills and an MCP server for agent-driven sandbox management.
Use Cases
- AI agent developers can give coding or browser agents an isolated workspace for tool execution.
- Platform teams can run untrusted user code or plugins in microVMs on their own machines.
- CI maintainers can run jobs in disposable virtual machines rather than sharing a persistent environment.
- Developers can rehearse database migrations or process untrusted documents in a sandbox that can be discarded or restored.
What you need
Detected in the repository
- Rust (from Cargo.toml)
- Automated checks on GitHub Actions
License in plain words
Apache-2.0permissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the license, the NOTICE file and a note of your changes
- Share your changes: no
- Includes an explicit patent grant from the contributors:
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
Install the CLI on macOS or Linux and run an image:
curl -fsSL https://install.microsandbox.dev | sh
msb run ubuntu
For Windows installation, SDK setup, and usage details, see the README and documentation.
Alternatives
- zeroboot: Zeroboot uses copy-on-write Firecracker snapshots for fast code sandboxes, while Microsandbox is a general-purpose local microVM runtime.
- CubeSandbox: CubeSandbox is a self-hostable service with E2B SDK compatibility and multi-node deployment, while Microsandbox is a local runtime.
- OpenShell: OpenShell isolates AI agents with policies governing file, process, and network access, rather than providing a general-purpose microVM runtime.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| microsandbox | Rust | Apache-2.0 | 8.8k | Active |
| zeroboot | Rust | Apache-2.0 | 2.5k | Quiet |
| CubeSandbox | Go | Other | 12.8k | Active |
| OpenShell | Rust | Apache-2.0 | 15.5k | Active |
Considerations
The README labels the software beta and cautions that breaking changes, missing features, and rough edges are possible. It requires platform-specific virtualization support: Apple Silicon on macOS, KVM on Linux, or WHP on Windows. Its local, child-process model is useful for embedding, but is not a substitute for a remote sandbox platform when workloads must run elsewhere.
Found this useful?
Share it with someone who would like microsandbox.